Last modified by Mengting Qiu on 2025/06/04 18:42

From version 240.1
edited by Dilisi S
on 2025/01/19 19:00
Change comment: Jan 19 - Fixed typos
To version 233.1
edited by Dilisi S
on 2024/12/17 04:56
Change comment: Uploaded new attachment "lt-22222-l-dashboard.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -124,12 +124,12 @@
124 124  
125 125  (% border="1" cellspacing="3" style="width:510px" %)
126 126  |(% style="background-color:#4f81bd; color:white; width:94px" %)**Model**|(% style="background-color:#4f81bd; color:white; width:172px" %)**Photo**|(% style="background-color:#4f81bd; color:white; width:244px" %)**Description**
127 -|(% style="width:94px" %)**LT-33222-L**|(% style="width:172px" %)(((
127 +|(% style="width:94px" %)**LT-22222-L**|(% style="width:172px" %)(((
128 128  (% style="text-align:center" %)
129 129  [[image:lt33222-l.jpg||height="110" width="95"]]
130 130  )))|(% style="width:256px" %)(((
131 -* 3 x Digital Input (Bi-direction)
132 -* 3 x Digital Output
131 +* 2 x Digital Input (Bi-direction)
132 +* 2 x Digital Output
133 133  * 2 x Relay Output (5A@250VAC / 30VDC)
134 134  * 2 x 0~~20mA Analog Input (res:0.01mA)
135 135  * 2 x 0~~30V Analog Input (res:0.01v)
... ... @@ -151,7 +151,7 @@
151 151  == 2.2 Terminals ==
152 152  
153 153  
154 -The  LT-22222-L has two screw terminal blocks. The upper screw terminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals.
154 +The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals.
155 155  
156 156  **Upper screw terminal block (from left to right):**
157 157  
... ... @@ -201,7 +201,7 @@
201 201  == 3.1 Prerequisites ==
202 202  
203 203  
204 -The LT-22222-L comes with device registration information such as DevEUI, AppEUI, and AppKey which allows you to register it with a LoRaWAN network. This registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference.
204 +The LT-22222-L comes with device registration information such as DevEUI, AppEUI, and AppKey that allows you to register it with a LoRaWAN network. These registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference.
205 205  
206 206  [[image:image-20230425173427-2.png||height="246" width="530"]]
207 207  
... ... @@ -241,6 +241,7 @@
241 241  * Go to your application's page and click on the **End devices** in the left menu.
242 242  * On the End devices page, click on **+ Register end device**. Two registration options are available:
243 243  
244 +
244 244  ==== 3.2.1.1 Using the LoRaWAN Device Repository ====
245 245  
246 246  
... ... @@ -261,19 +261,12 @@
261 261  ** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network'.
262 262  ** In the **DevEUI** field, enter the **DevEUI**.
263 263  ** In the **AppKey** field, enter the **AppKey.**
264 -** In the **End device ID** field, enter a unique name for your LT-22222-L within this application.
265 +** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
265 265  ** Under **After registration**, select the **View registered end device** option.
266 -** Click **Register end device** button.
267 267  
268 268  [[image:lt-22222-l-dev-repo-reg-p2.png]]
269 269  
270 270  
271 -* You will be navigated to the **Device overview** page.
272 -
273 -
274 -[[image:lt-22222-device-overview.png]]
275 -
276 -
277 277  ==== 3.2.1.2 Adding device manually ====
278 278  
279 279  
... ... @@ -309,7 +309,7 @@
309 309  === 3.2.2 Joining ===
310 310  
311 311  
312 -On the end device's page (in this case, lt-22222-l), click on **Live data** tab. The Live data panel for your device will display. Initially, it is blank.
306 +On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
313 313  
314 314  Now power on your LT-22222-L. The **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** The Things Stack network server. The **TX LED** will be on for **5 seconds** after joining the network. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server.
315 315  
... ... @@ -320,14 +320,14 @@
320 320  === 3.2.3 Uplinks ===
321 321  
322 322  
323 -After successfully joining, the device will send its first **uplink data message** to The Things Stack application it belongs to (in this example, it is **dragino-docs**). When the LT-22222-L sends an uplink message to the server, the **TX LED** turns on for **1 second**. By default, you will receive an uplink data message from the device every 10 minutes.
317 +After successfully joining, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**). When the LT-22222-L sends an uplink message to the server, the **TX LED** turns on for **1 second**. By default, you will receive an uplink data message from the device every 10 minutes.
324 324  
325 -Click on one of the **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the **decode_payload {}** JSON object.
319 +Click on one of a **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the decode_payload {} JSON object.
326 326  
327 327  [[image:lt-22222-ul-payload-decoded.png]]
328 328  
329 329  
330 -If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **Applications > [your application] > End devices** > [**your end device]** > **Payload formatters** > **Uplink**. Then select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
324 +If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **Applications > your application > End devices** > **your end device** > **Payload formatters** > **Uplink**. Then  select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
331 331  
332 332  {{info}}
333 333  The Things Stack provides two levels of payload formatters: application level and device level. The device-level payload formatters **override **the application-level payload formatters.
... ... @@ -336,7 +336,7 @@
336 336  [[image:lt-22222-ul-payload-fmt.png]]
337 337  
338 338  
339 -We have written a payload formatter that resolves some decoding issues present in The Things Stack Device Repository payload formatter. You can add it under the **Custom JavaScript formatter**. It can be found [[here>>https://github.com/dragino/dragino-end-node-decoder/blob/main/LT22222-L/v1.6_decoder_ttn%20.txt]]:
333 +We also have a payload formatter that resolves some decoding issues present in the Device Repository formatter. You can add it under the Custom JavaScript formatter. It can be found [[here>>https://github.com/dragino/dragino-end-node-decoder/blob/main/LT22222-L/v1.6_decoder_ttn%20.txt]]:
340 340  
341 341  (% class="wikigeneratedid" %)
342 342  [[image:lt-22222-l-js-custom-payload-formatter.png]]
... ... @@ -345,7 +345,7 @@
345 345  === 3.2.4 Downlinks ===
346 346  
347 347  
348 -When the LT-22222-L receives a downlink message from the LoRaWAN Network Server, the **RX LED** turns on for **1 second**.
342 +When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
349 349  
350 350  
351 351  == 3.3 Working Modes and Uplink Payload formats ==
... ... @@ -733,7 +733,7 @@
733 733  
734 734  AT+AVLIM=3000,6000,0,2000 (triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V)
735 735  
736 -AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage is lower than 5V. Use 0 for parameters that are not in use)
730 +AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage lower than 5V. Use 0 for parameters that are not in use)
737 737  
738 738  
739 739  (% style="color:#4f81bd" %)**Trigger based on current**:
... ... @@ -789,7 +789,7 @@
789 789  
790 790  (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:**
791 791  
792 -MOD6 Payload: a total of 11 bytes
786 +MOD6 Payload: total of 11 bytes
793 793  
794 794  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
795 795  |(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:69px" %)**1**|(% style="background-color:#4f81bd; color:white; width:69px" %)**1**|(% style="background-color:#4f81bd; color:white; width:109px" %)**1**|(% style="background-color:#4f81bd; color:white; width:49px" %)**6**|(% style="background-color:#4f81bd; color:white; width:109px" %)**1**|(% style="background-color:#4f81bd; color:white; width:50px" %)**1**
... ... @@ -803,7 +803,7 @@
803 803  MOD(6)
804 804  )))
805 805  
806 -(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Total 1 byte as below.
800 +(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
807 807  
808 808  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
809 809  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
... ... @@ -832,7 +832,7 @@
832 832  10100000: This means the system is configured to use the triggers AV1_LOW and AV2_LOW.
833 833  
834 834  
835 -(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is triggered. Total 1 byte as below.
829 +(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
836 836  
837 837  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
838 838  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
... ... @@ -861,7 +861,7 @@
861 861  10000000: The uplink is triggered by AV1_LOW, indicating that the voltage is too low.
862 862  
863 863  
864 -(% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is triggered. Total 1 byte as below.
858 +(% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
865 865  
866 866  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
867 867  |(% style="width:50px" %)**bit 7**|(% style="width:50px" %)**bit 6**|(% style="width:50px" %)**bit 5**|(% style="width:50px" %)**bit 4**|(% style="width:90px" %)**bit 3**|(% style="width:80px" %)**bit 2**|(% style="width:90px" %)**bit 1**|(% style="width:95px" %)**bit 0**
... ... @@ -871,7 +871,7 @@
871 871  
872 872  **Example:**
873 873  
874 -00000111: This means both DI1 and DI2 triggers are enabled, and this packet is triggered by DI1.
868 +00000111: This means both DI1 and DI2 triggers are enabled, and this packet is trigger by DI1.
875 875  
876 876  00000101: This means both DI1 and DI2 triggers are enabled.
877 877  
... ... @@ -882,7 +882,7 @@
882 882  
883 883  **AB 06**
884 884  
885 -When the device receives this command, it will send the MOD6 payload.
879 +When device receives this command, it will send the MOD6 payload.
886 886  
887 887  
888 888  === 3.3.7 Payload Decoder ===
... ... @@ -903,7 +903,7 @@
903 903  
904 904  (((
905 905  (((
906 -There are two types of commands:
900 +There are two tytes of commands:
907 907  )))
908 908  )))
909 909  
... ... @@ -915,7 +915,7 @@
915 915  
916 916  
917 917  (((
918 -These are available for each sensor and include actions such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]s.
912 +These are available for each sensors and include actions such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]s.
919 919  
920 920  
921 921  )))
... ... @@ -1106,7 +1106,7 @@
1106 1106  |(% style="width:95px" %)**Example**|(% style="width:403px" %)(((
1107 1107  AB 06
1108 1108  
1109 -Uplink the trigger settings.
1103 +Uplinks the trigger settings.
1110 1110  )))
1111 1111  
1112 1112  ==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ====
... ... @@ -1335,7 +1335,7 @@
1335 1335  )))
1336 1336  |(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1337 1337  
1338 -==== 3.4.2.11 Trigger – Set the minimum interval ====
1332 +==== 3.4.2.11 Trigger – Set minimum interval ====
1339 1339  
1340 1340  
1341 1341  Sets the AV and AC trigger minimum interval. The device won't respond to a second trigger within this set time after the first trigger.
... ... @@ -1473,7 +1473,7 @@
1473 1473  
1474 1474  (% style="color:red" %)**Note: **
1475 1475  
1476 - Since firmware v1.6.0, the latch time supports 4 bytes or 2 bytes
1470 + Since firmware v1.6.0, the latch time support 4 bytes or 2 bytes
1477 1477  
1478 1478   Before firmware v1.6.0, the latch time only supported 2 bytes.
1479 1479  
... ... @@ -1498,67 +1498,56 @@
1498 1498  
1499 1499  **A9 00 11 01 00 07 D0**
1500 1500  
1501 -DO1 pin takes no action, DO2 pin is set to low, and DO3 pin is set to high. This lasts for 2 seconds, after which the DO1 pin takes no action, the DO2 pin is set to high, and the DO3 pin is set to low.
1495 +DO1 pin takes no action, DO2 pin is set to low, and DO3 pin is set to high. This lasts for 2 seconds, after which DO1 pin takes no action, DO2 pin is set to high, and DO3 pin is set to low.
1502 1502  )))
1503 1503  
1498 +
1504 1504  ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
1505 1505  
1506 1506  
1507 -(% style="color:#037691" %)**AT Command:**
1502 +* (% style="color:#037691" %)**AT Command:**
1508 1508  
1509 -There is no AT Command to control the Relay Output.
1504 +There is no AT Command to control the Relay Output
1510 1510  
1511 1511  
1512 -(% style="color:#037691" %)**Downlink Payload**
1507 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
1513 1513  
1514 -(% border="2" style="width:500px" %)
1515 -|(% style="width:113px" %)**Prefix**|(% style="width:384px" %)0x03
1516 -|(% style="width:113px" %)**Parameters**|(% style="width:384px" %)(((
1517 -**RO1_status** : 1 byte in hex
1509 +(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Sets RO1/RO2 output
1518 1518  
1519 -00: Close
1520 1520  
1521 -01: Open
1512 +(((
1513 +If the payload is 0x030100, it means setting RO1 to close and RO2 to open.
1514 +)))
1522 1522  
1523 -11: No action
1516 +(((
1517 +00: Close ,  01: Open , 11: No action
1524 1524  
1525 -
1526 -**RO2_status** : 1 byte in hex
1527 -
1528 -00: Close
1529 -
1530 -01: Open
1531 -
1532 -11: No action
1519 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %)
1520 +|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**RO1**|(% style="background-color:#4f81bd; color:white" %)**RO2**
1521 +|03  00  11|Open|No Action
1522 +|03  01  11|Close|No Action
1523 +|03  11  00|No Action|Open
1524 +|03  11  01|No Action|Close
1525 +|03  00  00|Open|Open
1526 +|03  01  01|Close|Close
1527 +|03  01  00|Close|Open
1528 +|03  00  01|Open|Close
1533 1533  )))
1534 -|(% style="width:113px" %)**Payload format**|(% style="width:384px" %)<prefix><RO1_status><RO2_status>
1535 -|(% style="width:113px" %)**Example**|(% style="width:384px" %)(((
1536 -(% border="2" %)
1537 -|=Payload|=RO1|=RO2
1538 -|03  00  11|Open|No action
1539 -|03  01  11|Close|No action
1540 -|03 11  00|No action|Open
1541 -|03 11 10|No action|Close
1542 -|03 00 00|Open|Open
1543 -|03 01 01|Close|Close
1544 -|03 01 00|Close|Open
1545 -|03 00 01|Open|Close
1546 1546  
1547 -(% style="color:red" %)**The device will transmit an uplink packet if the downlink payload is executed successfully.**
1548 -)))
1531 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1549 1549  
1533 +
1550 1550  ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
1551 1551  
1552 1552  
1553 1553  Controls the relay output time.
1554 1554  
1539 +* (% style="color:#037691" %)**AT Command:**
1555 1555  
1556 -(% style="color:#037691" %)**AT Command:**
1557 -
1558 1558  There is no AT Command to control the Relay Output
1559 1559  
1560 1560  
1561 -(% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1544 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1562 1562  
1563 1563  (% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
1564 1564  
... ... @@ -1569,9 +1569,9 @@
1569 1569  
1570 1570  (% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode
1571 1571  
1572 -01: Relays will change back to their original state after a timeout.
1555 +01: Relays will change back to their original state after timeout.
1573 1573  
1574 -00: Relays will change to the inverter state after a timeout.
1557 +00: Relays will change to the inverter state after timeout.
1575 1575  
1576 1576  
1577 1577  (% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status:
... ... @@ -1600,7 +1600,7 @@
1600 1600  
1601 1601  **2. 05 01 10 07 D0**
1602 1602  
1603 -Relay1 will change to NC, Relay2 will change to NO, lasting 2 seconds, and then both will revert to their original state.
1586 +Relay1 will change to NC, Relay2 will change to NO, lasting 2 seconds, then both will revert to their original state.
1604 1604  
1605 1605  **3. 05 00 01 07 D0**
1606 1606  
... ... @@ -1631,7 +1631,7 @@
1631 1631  
1632 1632  **1**: higher than
1633 1633  
1634 -if you leave the logic parameter blank, it is considered 0
1617 +if you leave logic parameter blank, it is considered 0
1635 1635  )))
1636 1636  |(% style="width:137px" %)**Examples**|(% style="width:361px" %)(((
1637 1637  AT+VOLMAX=20000
... ... @@ -1662,7 +1662,7 @@
1662 1662  
1663 1663  **1**: higher than
1664 1664  
1665 -if you leave the logic parameter blank, it is considered 1 (higher than)
1648 +if you leave logic parameter blank, it is considered 1 (higher than)
1666 1666  )))
1667 1667  |(% style="width:140px" %)**Example**|(% style="width:358px" %)(((
1668 1668  A5 **4E 20**
... ... @@ -1926,7 +1926,7 @@
1926 1926  ==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ====
1927 1927  
1928 1928  
1929 -This command controls the behavior of the node when the combined size of the MAC commands (MACANS) from the server and the payload exceed the allowed byte limit for the current data rate (DR). The command provides two modes: one enables splitting the data into batches to ensure compliance with the byte limit, while the other prioritizes the payload and ignores the MACANS in cases of overflow.
1912 +This command controls the behavior of the node when the combined size of the MAC commands (MACANS) from the server and the payload exceeds the allowed byte limit for the current data rate (DR). The command provides two modes: one enables splitting the data into batches to ensure compliance with the byte limit, while the other prioritizes the payload and ignores the MACANS in cases of overflow.
1930 1930  
1931 1931  (% style="color:#037691" %)**AT Command**
1932 1932  
... ... @@ -1995,15 +1995,15 @@
1995 1995  There is no downlink option available for this feature.
1996 1996  
1997 1997  
1998 -==== 3.4.2.26 Query firmware version, frequency band, subband, and TDC time ====
1981 +==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
1999 1999  
2000 2000  
2001 -This command is used to query key information about the device, including its firmware version, frequency band, subband, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device.
1984 +This command is used to query key information about the device, including its firmware version, frequency band, sub band, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device.
2002 2002  
2003 2003  * (((
2004 2004  (% style="color:#037691" %)**Downlink Payload**(%%)**:**
2005 2005  
2006 -(% style="color:blue" %)**26 01  ** (%%) ~/~/  The downlink payload 26 01 is used to query the device's firmware version, frequency band, subband, and TDC time.
1989 +(% style="color:blue" %)**26 01  ** (%%) ~/~/  The downlink payload 26 01 is used to query the device's firmware version, frequency band, sub band, and TDC time.
2007 2007  
2008 2008  
2009 2009  
... ... @@ -2058,7 +2058,7 @@
2058 2058  * Ensure the following options are turned on.
2059 2059  ** Enable integration
2060 2060  ** Debug mode
2061 -** Allow creating devices or assets
2044 +** Allow create devices or assets
2062 2062  * Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
2063 2063  
2064 2064  [[image:thingseye-io-step-2.png]]
... ... @@ -2133,7 +2133,7 @@
2133 2133  [[image:thingseye-events.png]]
2134 2134  
2135 2135  
2136 -* To view the **JSON payload** of a message, click on the **three dots (...)** in the **Message** column of the desired message.
2119 +* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
2137 2137  
2138 2138  [[image:thingseye-json.png]]
2139 2139  
... ... @@ -2144,16 +2144,12 @@
2144 2144  If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
2145 2145  
2146 2146  
2147 -==== 3.5.2.4 Viewing sensor data on a dashboard ====
2130 +==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
2148 2148  
2149 2149  
2150 -You can create a dashboard with ThingsEye to visualize the sensor data coming from the LT-22222-L. The following image shows a dashboard created for the LT-22222-L. See **Creating a dashboard** in ThingsEye documentation for more information.
2133 +This will be added soon.
2151 2151  
2152 2152  
2153 -
2154 -[[image:lt-22222-l-dashboard.png]]
2155 -
2156 -
2157 2157  == 3.6 Interface Details ==
2158 2158  
2159 2159  === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
... ... @@ -2368,7 +2368,7 @@
2368 2368  == 3.7 LED Indicators ==
2369 2369  
2370 2370  
2371 -The table below lists the behaviour of LED indicators for each port function.
2350 +The table below lists the behavior of LED indicators for each port function.
2372 2372  
2373 2373  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
2374 2374  |(% style="background-color:#4f81bd; color:white; width:50px" %)**LEDs**|(% style="background-color:#4f81bd; color:white; width:460px" %)**Feature**
... ... @@ -2375,11 +2375,11 @@
2375 2375  |**PWR**|Always on when there is power
2376 2376  |**TX**|(((
2377 2377  (((
2378 -Device booting: TX blinks 5 times.
2357 +Device boot: TX blinks 5 times.
2379 2379  )))
2380 2380  
2381 2381  (((
2382 -Successful network joins: TX remains ON for 5 seconds.
2361 +Successful network join: TX remains ON for 5 seconds.
2383 2383  )))
2384 2384  
2385 2385  (((
... ... @@ -2463,13 +2463,13 @@
2463 2463  * ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)
2464 2464  * ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)
2465 2465  * ##**AT+CLASS**##: Get or set the Device Class
2466 -* ##**AT+JOIN**##: Join Network
2445 +* ##**AT+JOIN**##: Join network
2467 2467  * ##**AT+NJS**##: Get OTAA Join Status
2468 2468  * ##**AT+SENDB**##: Send hexadecimal data along with the application port
2469 2469  * ##**AT+SEND**##: Send text data along with the application port
2470 -* ##**AT+RECVB**##: Print the last received data in binary format (with hexadecimal values)
2471 -* ##**AT+RECV**##: Print the last received data in raw format
2472 -* ##**AT+VER**##: Get the current image version and Frequency Band
2449 +* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)
2450 +* ##**AT+RECV**##: Print last received data in raw format
2451 +* ##**AT+VER**##: Get current image version and Frequency Band
2473 2473  * ##**AT+CFM**##: Get or Set the confirmation mode (0-1)
2474 2474  * ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)
2475 2475  * ##**AT+SNR**##: Get the SNR of the last received packet
... ... @@ -2497,7 +2497,7 @@
2497 2497  )))
2498 2498  
2499 2499  (((
2500 -(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT command access**##
2479 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**##
2501 2501  )))
2502 2502  
2503 2503  (((
... ... @@ -2505,7 +2505,7 @@
2505 2505  )))
2506 2506  
2507 2507  (((
2508 -(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT command access**##
2487 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**##
2509 2509  )))
2510 2510  
2511 2511  (((
... ... @@ -2536,7 +2536,7 @@
2536 2536  
2537 2537  
2538 2538  (((
2539 -(% style="background-color:#dcdcdc" %)**123456**(%%)  ~/~/ Enter the password to enable AT commands access
2518 +(% style="background-color:#dcdcdc" %)**123456**(%%)  ~/~/ Enter password to enable AT commands access
2540 2540  )))
2541 2541  )))
2542 2542  
... ... @@ -2545,7 +2545,7 @@
2545 2545  )))
2546 2546  
2547 2547  (((
2548 -(% style="background-color:#dcdcdc" %)** 123456**(%%)  ~/~/ Enter the password to enable AT command access
2527 +(% style="background-color:#dcdcdc" %)** 123456**(%%)  ~/~/ Enter password to enable AT commands access
2549 2549  )))
2550 2550  
2551 2551  (((
... ... @@ -2627,7 +2627,7 @@
2627 2627  == 5.1 Counting how many objects pass through the flow line ==
2628 2628  
2629 2629  
2630 -See [[How to set up to setup counting for objects passing through the flow line>>How to set up to count objects pass in flow line]].
2609 +See [[How to set up to setup counting for objects passing through the flow line>>How to set up to count objects pass in flow line]]?
2631 2631  
2632 2632  
2633 2633  = 6. FAQ =
... ... @@ -2697,13 +2697,13 @@
2697 2697  )))
2698 2698  
2699 2699  (((
2700 -You can follow the introductions on [[how to upgrade the image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloading, select the required image file.
2679 +You can follow the introductions on [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloading, select the required image file.
2701 2701  )))
2702 2702  
2703 2703  (((
2704 2704  
2705 2705  
2706 -== 6.3 How to set up LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
2685 +== 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
2707 2707  
2708 2708  
2709 2709  )))
... ... @@ -2805,9 +2805,9 @@
2805 2805  * If the device is not properly shut down and is directly powered off.
2806 2806  * It will default to a power-off state.
2807 2807  * In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
2808 -* After a restart, the status before the power failure will be read from Flash.
2787 +* After a restart, the status before the power failure will be read from flash.
2809 2809  
2810 -== 6.8 Can I set up LT-22222-L as an NC (Normally Closed) relay? ==
2789 +== 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
2811 2811  
2812 2812  
2813 2813  The LT-22222-L's built-in relay is Normally Open (NO). You can use an external relay to achieve a Normally Closed (NC) configuration. The circuit diagram is shown below: