Changes for page LT-22222-L -- LoRa I/O Controller User Manual
Last modified by Mengting Qiu on 2025/06/04 18:42
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 5 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.pradeeka - Content
-
... ... @@ -54,10 +54,8 @@ 54 54 (% class="wikigeneratedid" %) 55 55 [[image:lorawan-nw.jpg||height="354" width="900"]] 56 56 57 - 58 58 == 1.2 Specifications == 59 59 60 - 61 61 (% style="color:#037691" %)**Hardware System:** 62 62 63 63 * STM32L072xxxx MCU ... ... @@ -118,13 +118,11 @@ 118 118 119 119 == 1.5 Hardware Variants == 120 120 121 - 122 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) 123 -|(% 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** 124 -|(% style="width:94px" %)**LT-22222-L**|(% style="width:172px" %)((( 125 -(% style="text-align:center" %) 126 -[[image:lt33222-l.jpg||height="116" width="100"]] 127 -)))|(% style="width:256px" %)((( 119 +(% style="width:524px" %) 120 +|(% style="width:94px" %)**Model**|(% style="width:98px" %)**Photo**|(% style="width:329px" %)**Description** 121 +|(% style="width:94px" %)**LT33222-L**|(% style="width:98px" %)((( 122 + 123 +)))|(% style="width:329px" %)((( 128 128 * 2 x Digital Input (Bi-direction) 129 129 * 2 x Digital Output 130 130 * 2 x Relay Output (5A@250VAC / 30VDC) ... ... @@ -178,7 +178,7 @@ 178 178 The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s **positive wire** to the **VIN** and the **negative wire** to the **GND** screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered. 179 179 180 180 {{warning}} 181 -**We recommend that you power on the LT-22222-L after adding its registration information to theLoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.**177 +**We recommend that you power on the LT-22222-L after configuring its registration information with a LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.** 182 182 {{/warning}} 183 183 184 184 ... ... @@ -241,7 +241,7 @@ 241 241 *** **Profile (Region)**: Select the region that matches your device. 242 242 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 243 243 244 -[[image:lt-22222-l-dev-repo-reg-p1.png]] 240 +[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]] 245 245 246 246 247 247 * Register end device page continued... ... ... @@ -251,7 +251,7 @@ 251 251 ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. 252 252 ** Under **After registration**, select the **View registered end device** option. 253 253 254 -[[image:lt-22222-l-dev-repo-reg-p2.png]] 250 +[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]] 255 255 256 256 257 257 ==== 3.2.2.3 Adding device manually ==== ... ... @@ -265,7 +265,7 @@ 265 265 ** Select the option **Over the air activation (OTAA)** under the **Activation mode.** 266 266 ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list. 267 267 268 -[[image:lt-22222-l-manually-p1.png]] 264 +[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]] 269 269 270 270 271 271 * Register end device page continued... ... ... @@ -276,13 +276,13 @@ 276 276 ** Under **After registration**, select the **View registered end device** option. 277 277 ** Click the **Register end device** button. 278 278 279 -[[image:lt-22222-l-manually-p2.png]] 275 +[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]] 280 280 281 281 282 282 You will be navigated to the **Device overview** page. 283 283 284 284 285 -[[image:lt-22222-device-overview.png]] 281 +[[image:lt-22222-device-overview.png||height="625" width="1000"]] 286 286 287 287 288 288 ==== 3.2.2.4 Joining ==== ... ... @@ -292,10 +292,9 @@ 292 292 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. 293 293 294 294 295 -[[image:lt-22222- l-joining.png]]291 +[[image:lt-22222-join-network.png||height="625" width="1000"]] 296 296 297 297 298 - 299 299 ==== 3.2.2.5 Uplinks ==== 300 300 301 301 ... ... @@ -312,15 +312,9 @@ 312 312 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. 313 313 {{/info}} 314 314 315 -[[image:lt-22222-ul-payload-fmt.png]] 310 +[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]] 316 316 317 317 318 -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]]: 319 - 320 -(% class="wikigeneratedid" %) 321 -[[image:lt-22222-l-js-custom-payload-formatter.png]] 322 - 323 - 324 324 ==== 3.2.2.6 Downlinks ==== 325 325 326 326 When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**. ... ... @@ -609,11 +609,11 @@ 609 609 610 610 (% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)** 611 611 612 -(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If theAVI1 voltageishigher than VOLMAX (20000mV =20V),thecounter increasesby1)**601 +(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 613 613 614 -(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If theAVI1 voltageislower than VOLMAX (20000mV =20V), counter increasesby1)**603 +(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)** 615 615 616 -(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If theAVI1 voltageishigher than VOLMAX (20000mV =20V), counter increasesby1)**605 +(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 617 617 ))) 618 618 619 619 ... ... @@ -732,9 +732,9 @@ 732 732 733 733 (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:** 734 734 735 - **Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**724 +Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 736 736 737 - **Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4726 +Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4 738 738 739 739 AA: Type Code for this downlink Command: 740 740 ... ... @@ -763,7 +763,7 @@ 763 763 764 764 MOD6 Payload: total of 11 bytes 765 765 766 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)755 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 767 767 |(% 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** 768 768 |Value|((( 769 769 TRI_A FLAG ... ... @@ -777,7 +777,7 @@ 777 777 778 778 (% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below 779 779 780 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)769 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 781 781 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 782 782 |((( 783 783 AV1_LOW ... ... @@ -801,12 +801,12 @@ 801 801 802 802 **Example:** 803 803 804 -10100000: This means the systemis configuredto use the triggersAV1_LOW and AV2_LOW.793 +10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW 805 805 806 806 807 807 (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below 808 808 809 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)798 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 810 810 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 811 811 |((( 812 812 AV1_LOW ... ... @@ -830,31 +830,31 @@ 830 830 831 831 **Example:** 832 832 833 -10000000: The uplink is triggered by AV1_LOW,indicatingthatthe voltage is too low.822 +10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low. 834 834 835 835 836 836 (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below 837 837 838 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)839 -|(% style="width:4 0px" %)**bit 7**|(% style="width:40px" %)**bit 6**|(% style="width:40px" %)**bit 5**|(% style="width:40px" %)**bit 4**|(% style="width:90px" %)**bit 3**|(% style="width:80px" %)**bit 2**|(% style="width:90px" %)**bit 1**|(% style="width:80px" %)**bit 0**827 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:674px" %) 828 +|(% style="width:64px" %)**bit 7**|(% style="width:68px" %)**bit 6**|(% style="width:63px" %)**bit 5**|(% style="width:66px" %)**bit 4**|(% style="width:109px" %)**bit 3**|(% style="width:93px" %)**bit 2**|(% style="width:109px" %)**bit 1**|(% style="width:99px" %)**bit 0** 840 840 |(% style="width:64px" %)N/A|(% style="width:68px" %)N/A|(% style="width:63px" %)N/A|(% style="width:66px" %)N/A|(% style="width:109px" %)DI2_STATUS|(% style="width:93px" %)DI2_FLAG|(% style="width:109px" %)DI1_STATUS|(% style="width:99px" %)DI1_FLAG 841 841 842 -* Each bit shows which status has been triggered on this uplink. 831 +* Each bits shows which status has been triggered on this uplink. 843 843 844 844 **Example:** 845 845 846 -00000111: This means both DI1 and DI2 triggersare enabled,and this packet is trigger by DI1.835 +00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1. 847 847 848 -00000101: This means both DI1 and DI2 triggersare enabled.837 +00000101: Means both DI1 and DI2 trigger are enabled. 849 849 850 850 851 -(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable d. 0x00: MOD6 is disabled.840 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable. 852 852 853 -Downlink command to poll /requestMOD6 status:842 +Downlink command to poll MOD6 status: 854 854 855 855 **AB 06** 856 856 857 -When device receivesthis command, it will send the MOD6 payload.846 +When device got this command, it will send the MOD6 payload. 858 858 859 859 860 860 === 3.3.7 Payload Decoder === ... ... @@ -901,15 +901,8 @@ 901 901 902 902 (% border="2" style="width:500px" %) 903 903 |**Command**|AT+TDC=<time> 904 -|**Parameters**|**time **: uplink interval in milliseconds 905 -|**Get**|AT+TDC=? 906 -|**Response**|((( 907 -current uplink interval 908 - 909 -OK 910 -))) 911 -|**Set**|AT+TDC=<time> 912 -|**Response**|OK 893 +|**Response**| 894 +|**Parameters**|**time** : uplink interval is in **milliseconds** 913 913 |**Example**|((( 914 914 AT+TDC=30000 915 915 ... ... @@ -925,7 +925,7 @@ 925 925 |**Parameters**|((( 926 926 **prefix** : 0x01 927 927 928 -**time** : uplink interval in **seconds**, represented by **3 bytes** in **hexadecimal**. 910 +**time** : uplink interval is in **seconds**, represented by **3 bytes** in **hexadecimal**. 929 929 ))) 930 930 |**Example**|((( 931 931 01 **00 00 1E** ... ... @@ -946,7 +946,8 @@ 946 946 (% style="color:#037691" %)**AT command** 947 947 948 948 (% border="2" style="width:500px" %) 949 -|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MOD=<working_mode> 931 +|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE=<working_mode> 932 +|(% style="width:97px" %)**Response**|(% style="width:413px" %) 950 950 |(% style="width:97px" %)**Parameters**|(% style="width:413px" %)((( 951 951 **working_mode** : 952 952 ... ... @@ -962,18 +962,6 @@ 962 962 963 963 6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5 964 964 ))) 965 -|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=? 966 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)((( 967 -Current working mode 968 - 969 -OK 970 -))) 971 -|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode> 972 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)((( 973 -Attention:Take effect after ATZ 974 - 975 -OK 976 -))) 977 977 |(% style="width:97px" %)**Example**|(% style="width:413px" %)((( 978 978 AT+MOD=2 979 979 ... ... @@ -996,7 +996,7 @@ 996 996 Sets the device to working mode 2 (Double DI Counting + DO + RO) 997 997 ))) 998 998 999 -==== 3.4.2.3 Requestan uplinkfrom the device====970 +==== 3.4.2.3 Poll an uplink ==== 1000 1000 1001 1001 Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode. 1002 1002 ... ... @@ -1052,9 +1052,9 @@ 1052 1052 Enable trigger mode for the current working mode 1053 1053 ))) 1054 1054 1055 -==== 3.4.2.5 Requesttrigger settings ====1026 +==== 3.4.2.5 Poll trigger settings ==== 1056 1056 1057 - Requeststhe trigger settings.1028 +Polls the trigger settings. 1058 1058 1059 1059 (% style="color:#037691" %)**AT Command:** 1060 1060 ... ... @@ -1361,11 +1361,11 @@ 1361 1361 ((( 1362 1362 01: Low, 00: High, 11: No action 1363 1363 1364 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:383px" %)1365 -|(% style="background-color:#4f81bd; color:white ; width:126px" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white; width:85px" %)**DO1**|(% style="background-color:#4f81bd; color:white; width:86px" %)**DO2**|(% style="background-color:#4f81bd; color:white; width:86px" %)**DO3**1366 -| (% style="width:126px" %)02 01 00 11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action1367 -| (% style="width:126px" %)02 00 11 01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low1368 -| (% style="width:126px" %)02 11 01 00|(% style="width:85px" %)No Action|(% style="width:86px" %)Low|(% style="width:86px" %)High1335 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 1336 +|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**DO1**|(% style="background-color:#4f81bd; color:white" %)**DO2**|(% style="background-color:#4f81bd; color:white" %)**DO3** 1337 +|02 01 00 11|Low|High|No Action 1338 +|02 00 11 01|High|No Action|Low 1339 +|02 11 01 00|No Action|Low|High 1369 1369 ))) 1370 1370 1371 1371 ((( ... ... @@ -1384,23 +1384,25 @@ 1384 1384 1385 1385 * (% style="color:#037691" %)**AT Command** 1386 1386 1387 -There is no AT command to controlthe digitaloutput.1358 +There is no AT Command to control Digital Output 1388 1388 1389 1389 1390 1390 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)** 1391 1391 1392 -(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Set sDO1/DO2/DO3 outputswith time control1363 +(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Set DO1/DO2/DO3 output with time control 1393 1393 1365 + 1394 1394 This is to control the digital output time of DO pin. Include four bytes: 1395 1395 1396 -(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)1368 +(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9) 1397 1397 1398 -(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode1370 +(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode 1399 1399 1400 -**01:** DO pins revert to their original state after the timeout. 1401 -**00:** DO pins switch to an inverted state after the timeout. 1372 +01: DO pins will change back to original state after timeout. 1402 1402 1374 +00: DO pins will change to an inverter state after timeout 1403 1403 1376 + 1404 1404 (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status: 1405 1405 1406 1406 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) ... ... @@ -1409,7 +1409,7 @@ 1409 1409 |0x00|DO1 set to high 1410 1410 |0x11|DO1 NO Action 1411 1411 1412 -(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:1385 +(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status: 1413 1413 1414 1414 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1415 1415 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1417,7 +1417,7 @@ 1417 1417 |0x00|DO2 set to high 1418 1418 |0x11|DO2 NO Action 1419 1419 1420 -(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:1393 +(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status: 1421 1421 1422 1422 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1423 1423 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1425,7 +1425,7 @@ 1425 1425 |0x00|DO3 set to high 1426 1426 |0x11|DO3 NO Action 1427 1427 1428 -(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms)1401 +(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms) 1429 1429 1430 1430 1431 1431 (% style="color:red" %)**Note: ** ... ... @@ -1434,7 +1434,7 @@ 1434 1434 1435 1435 Before firmware v1.6.0, the latch time only supported 2 bytes. 1436 1436 1437 -(% style="color:red" %)** Thedevice will uplinka packet if the downlink code executes successfully.**1410 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.** 1438 1438 1439 1439 1440 1440 **Example payload:** ... ... @@ -1461,16 +1461,16 @@ 1461 1461 1462 1462 * (% style="color:#037691" %)**AT Command:** 1463 1463 1464 -There is no AT Command to control theRelay Output1437 +There is no AT Command to control Relay Output 1465 1465 1466 1466 1467 1467 * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):** 1468 1468 1469 -(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set sRO1/RO2 output1442 +(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set RO1/RO2 output 1470 1470 1471 1471 1472 1472 ((( 1473 -If thepayload is 0x030100, it means setting RO1 to close and RO2 to open.1446 +If payload is 0x030100, it means setting RO1 to close and RO2 to open. 1474 1474 ))) 1475 1475 1476 1476 ((( ... ... @@ -1488,7 +1488,7 @@ 1488 1488 |03 00 01|Open|Close 1489 1489 ))) 1490 1490 1491 -(% style="color:red" %)** Thedevice will uplinka packet ifthedownlink code executes successfully.**1464 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1492 1492 1493 1493 1494 1494 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== ... ... @@ -1497,19 +1497,19 @@ 1497 1497 1498 1498 * (% style="color:#037691" %)**AT Command:** 1499 1499 1500 -There is no AT Command to control theRelay Output1473 +There is no AT Command to control Relay Output 1501 1501 1502 1502 1503 1503 * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):** 1504 1504 1505 -(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set sRO1/RO2 relayswith time control1478 +(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set RO1/RO2 relay with time control 1506 1506 1507 1507 1508 -This control sthe relay output timeandincludes4bytes:1481 +This is to control the relay output time. It includes four bytes: 1509 1509 1510 -(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)1483 +(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05) 1511 1511 1512 -(% style="color:#4f81bd" %)**Second byte1485 +(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode 1513 1513 1514 1514 01: Relays will change back to their original state after timeout. 1515 1515 ... ... @@ -1516,12 +1516,12 @@ 1516 1516 00: Relays will change to the inverter state after timeout. 1517 1517 1518 1518 1519 -(% style="color:#4f81bd" %)**Third byte1492 +(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status: 1520 1520 1521 1521 [[image:image-20221008095908-1.png||height="364" width="564"]] 1522 1522 1523 1523 1524 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes1497 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms 1525 1525 1526 1526 1527 1527 (% style="color:red" %)**Note:** ... ... @@ -1531,7 +1531,7 @@ 1531 1531 Before firmware v1.6.0, the latch time only supported 2 bytes. 1532 1532 1533 1533 1534 -(% style="color:red" %)** Thedevice will uplinka packet if the downlink code executes successfully.**1507 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.** 1535 1535 1536 1536 1537 1537 **Example payload:** ... ... @@ -1690,7 +1690,7 @@ 1690 1690 ))) 1691 1691 |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01** 1692 1692 1693 -==== 3.4.2.19 Counting ~-~- Set SavingIntervalfor 'CountingResult'====1666 +==== 3.4.2.19 Counting ~-~- Change counting mode to save time ==== 1694 1694 1695 1695 This command allows you to configure the device to save its counting result to internal flash memory at specified intervals. By setting a save time, the device will periodically store the counting data to prevent loss in case of power failure. The save interval can be adjusted to suit your requirements, with a minimum value of 30 seconds. 1696 1696 ... ... @@ -1721,7 +1721,7 @@ 1721 1721 Sets the device to save its counting results to the memory every 60 seconds. 1722 1722 ))) 1723 1723 1724 -==== 3.4.2.20 Reset save dROandDO states====1697 +==== 3.4.2.20 Reset save RO DO state ==== 1725 1725 1726 1726 This command allows you to reset the saved relay output (RO) and digital output (DO) states when the device joins the network. By configuring this setting, you can control whether the device should retain or reset the relay states after a reset and rejoin to the network. 1727 1727 ... ... @@ -1747,6 +1747,7 @@ 1747 1747 After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network. 1748 1748 ))) 1749 1749 1723 + 1750 1750 (% style="color:#037691" %)**Downlink Payload** 1751 1751 1752 1752 (% border="2" style="width:500px" %) ... ... @@ -1908,13 +1908,13 @@ 1908 1908 1909 1909 ==== 3.4.2.25 Copy downlink to uplink ==== 1910 1910 1911 -This command enables the device to immediately uplink the payloadof a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100.1885 +This command enables the device to immediately uplink the content of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100. 1912 1912 1913 -(% style="color:#037691" %)**AT Command**(%%)**:** 1887 +* (% style="color:#037691" %)**AT Command**(%%)**:** 1914 1914 1915 -(% style="color:blue" %)**AT+RPL=5** (%%) ~/~/ After receiving adownlinkpayloadfrom the server, thedevicewill immediately uplinkthe payload back to the serverusingport number 100.1889 +(% style="color:blue" %)**AT+RPL=5** (%%) ~/~/ After receiving the package from the server, it will immediately upload the content of the package to the server, the port number is 100. 1916 1916 1917 -Example:**aa xx xx xx xx** ~/~/ **aa**indicates whether the configuration has changed: **00** meansYES,and **01** meansNO. **xx xx xx xx**are the bytesuplinked back.1891 +Example:**aa xx xx xx xx** ~/~/ aa indicates whether the configuration has changed, 00 is yes, 01 is no; xx xx xx xx are the bytes sent. 1918 1918 1919 1919 1920 1920 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173747-6.png?width=1124&height=165&rev=1.1||alt="image-20220823173747-6.png"]] ... ... @@ -1921,16 +1921,28 @@ 1921 1921 1922 1922 For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77. 1923 1923 1924 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]] 1898 +(% border="2" style="width:500px" %) 1899 +|(% style="width:122px" %)**Command**|(% style="width:376px" %)((( 1900 +AT+RPL=5 1925 1925 1926 -For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. 1902 +After receiving a downlink packet from the server, the node immediately uplinks the content of the packet back to the server using port number 100. 1903 +))) 1904 +|(% style="width:122px" %)**Example**|(% style="width:376px" %)((( 1905 +Downlink: 1927 1927 1907 +01 00 02 58 1928 1928 1929 - (% style="color:#037691" %)**DownlinkPayload**(%%)**:**1909 +Uplink: 1930 1930 1931 -There is no downlink option available for this feature. 1911 +01 01 00 02 58 1912 +))) 1932 1932 1914 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]] 1933 1933 1916 +For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. 1917 + 1918 + 1919 + 1934 1934 ==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ==== 1935 1935 1936 1936 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. ... ... @@ -1966,7 +1966,7 @@ 1966 1966 The username and password (API key) you created here are required in the next section. 1967 1967 {{/info}} 1968 1968 1969 -[[image:tts-mqtt-integration.png]] 1955 +[[image:tts-mqtt-integration.png||height="625" width="1000"]] 1970 1970 1971 1971 === 3.5.2 Configuring ThingsEye.io === 1972 1972 ... ... @@ -1976,7 +1976,7 @@ 1976 1976 * Under the **Integrations center**, click **Integrations**. 1977 1977 * Click the **Add integration** button (the button with the **+** symbol). 1978 1978 1979 -[[image:thingseye-io-step-1.png]] 1965 +[[image:thingseye-io-step-1.png||height="625" width="1000"]] 1980 1980 1981 1981 1982 1982 On the **Add integration** window, configure the following: ... ... @@ -1991,7 +1991,7 @@ 1991 1991 ** Allow create devices or assets 1992 1992 * Click the **Next** button. you will be navigated to the **Uplink data converter** tab. 1993 1993 1994 -[[image:thingseye-io-step-2.png]] 1980 +[[image:thingseye-io-step-2.png||height="625" width="1000"]] 1995 1995 1996 1996 1997 1997 **Uplink data converter:** ... ... @@ -2002,7 +2002,7 @@ 2002 2002 * Paste the uplink decoder function into the text area (first, delete the default code). The demo uplink decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Uplink_Converter.js]]. 2003 2003 * Click the **Next** button. You will be navigated to the **Downlink data converter **tab. 2004 2004 2005 -[[image:thingseye-io-step-3.png]] 1991 +[[image:thingseye-io-step-3.png||height="625" width="1000"]] 2006 2006 2007 2007 2008 2008 **Downlink data converter (this is an optional step):** ... ... @@ -2013,7 +2013,7 @@ 2013 2013 * Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Downlink_Converter.js]]. 2014 2014 * Click the **Next** button. You will be navigated to the **Connection** tab. 2015 2015 2016 -[[image:thingseye-io-step-4.png]] 2002 +[[image:thingseye-io-step-4.png||height="625" width="1000"]] 2017 2017 2018 2018 2019 2019 **Connection:** ... ... @@ -2028,13 +2028,13 @@ 2028 2028 2029 2029 * Click the **Add** button. 2030 2030 2031 -[[image:thingseye-io-step-5.png]] 2017 +[[image:thingseye-io-step-5.png||height="625" width="1000"]] 2032 2032 2033 2033 2034 2034 Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings and correct any errors. 2035 2035 2036 2036 2037 -[[image:thingseye.io_integrationsCenter_integrations.png]] 2023 +[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]] 2038 2038 2039 2039 2040 2040 ==== 3.5.2.1 Viewing integration details ==== ... ... @@ -2041,7 +2041,7 @@ 2041 2041 2042 2042 Click on your integration from the list. The **Integration details** window will appear with the **Details **tab selected. The **Details **tab shows all the settings you have provided for this integration. 2043 2043 2044 -[[image:integration-details.png]] 2030 +[[image:integration-details.png||height="686" width="1000"]] 2045 2045 2046 2046 2047 2047 If you want to edit the settings you have provided, click on the **Toggle edit mode** button. Once you have done click on the **Apply changes **button. ... ... @@ -2057,12 +2057,12 @@ 2057 2057 * Select **Debug **from the **Event type** dropdown. 2058 2058 * Select the** time frame** from the **time window**. 2059 2059 2060 -[[image:thingseye-events.png]] 2046 +[[image:thingseye-events.png||height="686" width="1000"]] 2061 2061 2062 2062 2063 2063 * To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message. 2064 2064 2065 -[[image:thingseye-json.png]] 2051 +[[image:thingseye-json.png||width="1000"]] 2066 2066 2067 2067 2068 2068 ==== **3.5.2.3 Deleting an integration** ==== ... ... @@ -2080,7 +2080,7 @@ 2080 2080 === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) === 2081 2081 2082 2082 2083 -Supports **NPN-type**sensors.2069 +Supports NPN-type sensors. 2084 2084 2085 2085 [[image:1653356991268-289.png]] 2086 2086 ... ... @@ -2202,15 +2202,15 @@ 2202 2202 ))) 2203 2203 2204 2204 2205 -(% style="color:blue" %)**Example aDry Contact sensor2191 +(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor 2206 2206 2207 -From the DI port circuit above, activating the photocoupler requires a voltage difference between the DI+ and DI- ports. However, the Dry Contact sensor is a passive component and cannot provide this voltage difference on its own.2193 +From the DI port circuit above, you can see that activating the photocoupler requires a voltage difference between the DI+ and DI- ports. However, the Dry Contact sensor is a passive component and cannot provide this voltage difference. 2208 2208 2209 -To detect a Dry Contact, you can supply a power source to one of thepinsof the Dry Contact.Areference circuit diagramis shown below.2195 +To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram. 2210 2210 2211 2211 [[image:image-20230616235145-1.png]] 2212 2212 2213 -(% style="color:blue" %)**Example 2199 +(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector 2214 2214 2215 2215 [[image:image-20240219115718-1.png]] 2216 2216 ... ... @@ -2286,7 +2286,7 @@ 2286 2286 [[image:image-20220524100215-10.png||height="382" width="723"]] 2287 2287 2288 2288 2289 -== 3.7 LED Indicators == 2275 +== 3.7 LEDs Indicators == 2290 2290 2291 2291 The table below lists the behavior of LED indicators for each port function. 2292 2292 ... ... @@ -2325,14 +2325,13 @@ 2325 2325 == 4.1 Connecting the LT-22222-L to a PC == 2326 2326 2327 2327 ((( 2328 -You can use a USB-to-TTL adapter /converteralong with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below.2314 +You can use a USB-to-TTL adapter along with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below. 2329 2329 2330 -[[image:usb-ttl-audio-jack-connection.jpg]] 2331 - 2332 - 2316 +[[image:usb-ttl-programming.png]] 2333 2333 ))) 2334 2334 2335 2335 2320 + 2336 2336 ((( 2337 2337 On the PC, you need to set the (% style="color:#4f81bd" %)**serial tool **(%%)(such as [[PuTTY>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]] or [[SecureCRT>>https://www.vandyke.com/cgi-bin/releases.php?product=securecrt]]) to a baud rate of (% style="color:green" %)**9600**(%%) to access the serial console of LT-22222-L. Access to AT commands is disabled by default, and a password (default: (% style="color:green" %)**123456**)(%%) must be entered to enable AT command access, as shown below: 2338 2338 ))) ... ... @@ -2362,39 +2362,39 @@ 2362 2362 * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey) 2363 2363 * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI) 2364 2364 * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON) 2365 -* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)2366 -* **##AT+DR##**: Get or set the Data Rate. (0-7 corresponding to DR_X)2367 -* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing2368 -* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)2369 -* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency2370 -* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)2371 -* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms2372 -* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms2373 -* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms2374 -* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms2375 -* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)2376 -* ##**AT+NWKID**##: Get or set the Network ID2377 -* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)2378 -* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)2379 -* ##**AT+CLASS**##: Get or set the Device Class2380 -* ##**AT+JOIN**##: Join network2381 -* ##**AT+NJS**##: Get OTAA Join Status2382 -* ##**AT+SENDB**##: Send hexadecimal data along with the application port2383 -* ##**AT+SEND**##: Send text data along with the application port2384 -* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)2385 -* ##**AT+RECV**##: Print last received data in raw format2386 -* ##**AT+VER**##: Get current image version and Frequency Band2387 -* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)2388 -* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)2389 -* ##**AT+SNR**##: Get the SNR of the last received packet2390 -* ##**AT+RSSI**##: Get the RSSI of the last received packet2391 -* ##**AT+TDC**##: Get or set the application data transmission interval in ms2392 -* ##**AT+PORT**##: Get or set the application port2393 -* ##**AT+DISAT**##: Disable AT commands2394 -* ##**AT+PWORD**##: Set password, max 9 digits2395 -* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode2396 -* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN4702397 -* ##**AT+CFG**##: Print all settings2350 +* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification) 2351 +* AT+DR: Get or set the Data Rate. (0-7 corresponding to DR_X) 2352 +* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing 2353 +* AT+PNM: Get or set the public network mode. (0: off, 1: on) 2354 +* AT+RX2FQ: Get or set the Rx2 window frequency 2355 +* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X) 2356 +* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms 2357 +* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms 2358 +* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms 2359 +* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms 2360 +* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA) 2361 +* AT+NWKID: Get or set the Network ID 2362 +* AT+FCU: Get or set the Frame Counter Uplink (FCntUp) 2363 +* AT+FCD: Get or set the Frame Counter Downlink (FCntDown) 2364 +* AT+CLASS: Get or set the Device Class 2365 +* AT+JOIN: Join network 2366 +* AT+NJS: Get OTAA Join Status 2367 +* AT+SENDB: Send hexadecimal data along with the application port 2368 +* AT+SEND: Send text data along with the application port 2369 +* AT+RECVB: Print last received data in binary format (with hexadecimal values) 2370 +* AT+RECV: Print last received data in raw format 2371 +* AT+VER: Get current image version and Frequency Band 2372 +* AT+CFM: Get or Set the confirmation mode (0-1) 2373 +* AT+CFS: Get confirmation status of the last AT+SEND (0-1) 2374 +* AT+SNR: Get the SNR of the last received packet 2375 +* AT+RSSI: Get the RSSI of the last received packet 2376 +* AT+TDC: Get or set the application data transmission interval in ms 2377 +* AT+PORT: Get or set the application port 2378 +* AT+DISAT: Disable AT commands 2379 +* AT+PWORD: Set password, max 9 digits 2380 +* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode 2381 +* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470 2382 +* AT+CFG: Print all settings 2398 2398 ))) 2399 2399 2400 2400 ... ... @@ -2559,7 +2559,7 @@ 2559 2559 You will need the following things before proceeding: 2560 2560 2561 2561 * 3.5mm programming cable (included with the LT-22222-L as an additional accessory) 2562 -* USB to TTL adapter /converter2547 +* USB to TTL adapter 2563 2563 * Download and install the [[STM32 Flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]]. (replaced by STM32CubeProgrammer) 2564 2564 * Download the latest firmware image from [[LT-22222-L firmware image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]]. Check the file name of the firmware to find the correct region. 2565 2565 ... ... @@ -2569,7 +2569,7 @@ 2569 2569 2570 2570 Below is the hardware setup for uploading a firmware image to the LT-22222-L: 2571 2571 2572 -[[image:usb-ttl- audio-jack-connection.jpg]]2557 +[[image:usb-ttl-programming.png]] 2573 2573 2574 2574 2575 2575
- Screenshot 2024-12-08 193946.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -32.4 KB - Content
- lt-22222-l-joining.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -301.9 KB - Content
- lt-22222-l-js-custom-payload-formatter.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -453.9 KB - Content
- lt33222-l.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.3 KB - Content
- usb-ttl-audio-jack-connection.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -394.4 KB - Content