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: 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**840 -|(% style="width:4 9px" %)N/A|(% style="width:53px" %)N/A|(% style="width:53px" %)N/A|(% style="width:55px" %)N/A|(% style="width:99px" %)DI2_STATUS|(% style="width:83px" %)DI2_FLAG|(% style="width:98px" %)DI1_STATUS|(% style="width:85px" %)DI1_FLAG827 +(% 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** 829 +|(% 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 === ... ... @@ -868,7 +868,6 @@ 868 868 869 869 == 3.4 Configure LT-22222-L via AT Commands or Downlinks == 870 870 871 - 872 872 ((( 873 873 You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks. 874 874 ))) ... ... @@ -883,25 +883,19 @@ 883 883 884 884 * (% style="color:blue" %)**Sensor-related commands**(%%): 885 885 886 - 887 887 === 3.4.1 Common commands === 888 888 889 - 890 890 ((( 891 891 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. 892 - 893 - 894 894 ))) 895 895 896 896 === 3.4.2 Sensor-related commands === 897 897 898 - 899 899 These commands are specially designed for the LT-22222-L. Commands can be sent to the device using options such as an AT command or a LoRaWAN downlink payload. 900 900 901 901 902 902 ==== 3.4.2.1 Set Transmit/Uplink Interval ==== 903 903 904 - 905 905 Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes. 906 906 907 907 (% style="color:#037691" %)**AT command** ... ... @@ -908,15 +908,8 @@ 908 908 909 909 (% border="2" style="width:500px" %) 910 910 |**Command**|AT+TDC=<time> 911 -|**Parameters**|**time **: uplink interval in milliseconds 912 -|**Get**|AT+TDC=? 913 -|**Response**|((( 914 -current uplink interval 915 - 916 -OK 917 -))) 918 -|**Set**|AT+TDC=<time> 919 -|**Response**|OK 893 +|**Response**| 894 +|**Parameters**|**time** : uplink interval is in **milliseconds** 920 920 |**Example**|((( 921 921 AT+TDC=30000 922 922 ... ... @@ -932,7 +932,7 @@ 932 932 |**Parameters**|((( 933 933 **prefix** : 0x01 934 934 935 -**time** : uplink interval in **seconds**, represented by **3 bytes** in **hexadecimal**. 910 +**time** : uplink interval is in **seconds**, represented by **3 bytes** in **hexadecimal**. 936 936 ))) 937 937 |**Example**|((( 938 938 01 **00 00 1E** ... ... @@ -948,13 +948,13 @@ 948 948 949 949 ==== 3.4.2.2 Set the Working Mode (AT+MOD) ==== 950 950 951 - 952 952 Sets the working mode. 953 953 954 954 (% style="color:#037691" %)**AT command** 955 955 956 956 (% border="2" style="width:500px" %) 957 -|(% 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" %) 958 958 |(% style="width:97px" %)**Parameters**|(% style="width:413px" %)((( 959 959 **working_mode** : 960 960 ... ... @@ -970,18 +970,6 @@ 970 970 971 971 6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5 972 972 ))) 973 -|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=? 974 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)((( 975 -Current working mode 976 - 977 -OK 978 -))) 979 -|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode> 980 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)((( 981 -Attention:Take effect after ATZ 982 - 983 -OK 984 -))) 985 985 |(% style="width:97px" %)**Example**|(% style="width:413px" %)((( 986 986 AT+MOD=2 987 987 ... ... @@ -1004,10 +1004,8 @@ 1004 1004 Sets the device to working mode 2 (Double DI Counting + DO + RO) 1005 1005 ))) 1006 1006 970 +==== 3.4.2.3 Poll an uplink ==== 1007 1007 1008 -==== 3.4.2.3 Request an uplink from the device ==== 1009 - 1010 - 1011 1011 Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode. 1012 1012 1013 1013 (% style="color:#037691" %)**AT command** ... ... @@ -1025,10 +1025,8 @@ 1025 1025 Requests an uplink from LT-22222-L. 1026 1026 ))) 1027 1027 1028 - 1029 1029 ==== 3.4.2.4 Enable/Disable Trigger Mode ==== 1030 1030 1031 - 1032 1032 Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]). 1033 1033 1034 1034 (% style="color:#037691" %)**AT Command** ... ... @@ -1064,12 +1064,10 @@ 1064 1064 Enable trigger mode for the current working mode 1065 1065 ))) 1066 1066 1026 +==== 3.4.2.5 Poll trigger settings ==== 1067 1067 1068 - ====3.4.2.5 Requesttrigger settings====1028 +Polls the trigger settings. 1069 1069 1070 - 1071 -Requests the trigger settings. 1072 - 1073 1073 (% style="color:#037691" %)**AT Command:** 1074 1074 1075 1075 There is no AT Command available for this feature. ... ... @@ -1085,10 +1085,8 @@ 1085 1085 Uplinks the trigger settings. 1086 1086 ))) 1087 1087 1088 - 1089 1089 ==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ==== 1090 1090 1091 - 1092 1092 Enable or disable DI1/DI2/DI3 as a trigger. 1093 1093 1094 1094 (% style="color:#037691" %)**AT Command** ... ... @@ -1141,12 +1141,11 @@ 1141 1141 Enable DI1 trigger, disable DI2 trigger 1142 1142 ))) 1143 1143 1144 - 1145 1145 ==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ==== 1146 1146 1147 - 1148 1148 Sets DI1 or DI3 (for LT-33222-L) as a trigger. 1149 1149 1103 + 1150 1150 (% style="color:#037691" %)**AT Command** 1151 1151 1152 1152 (% border="2" style="width:500px" %) ... ... @@ -1181,12 +1181,11 @@ 1181 1181 Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms. 1182 1182 ))) 1183 1183 1184 - 1185 1185 ==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ==== 1186 1186 1187 - 1188 1188 Sets DI2 as a trigger. 1189 1189 1142 + 1190 1190 (% style="color:#037691" %)**AT Command** 1191 1191 1192 1192 (% border="2" style="width:500px" %) ... ... @@ -1216,10 +1216,8 @@ 1216 1216 ))) 1217 1217 |(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64** 1218 1218 1219 - 1220 1220 ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ==== 1221 1221 1222 - 1223 1223 Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1224 1224 1225 1225 (% style="color:#037691" %)**AT Command** ... ... @@ -1267,10 +1267,8 @@ 1267 1267 ))) 1268 1268 |(% style="width:104px" %)Note|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1269 1269 1270 - 1271 1271 ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ==== 1272 1272 1273 - 1274 1274 Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1275 1275 1276 1276 (% style="color:#037691" %)**AT Command** ... ... @@ -1316,10 +1316,8 @@ 1316 1316 ))) 1317 1317 |(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1318 1318 1319 - 1320 1320 ==== 3.4.2.11 Trigger – Set minimum interval ==== 1321 1321 1322 - 1323 1323 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. 1324 1324 1325 1325 (% style="color:#037691" %)**AT Command** ... ... @@ -1353,10 +1353,8 @@ 1353 1353 ))) 1354 1354 |(% style="width:112px" %)Note|(% style="width:386px" %)(% style="color:red" %)**The time must be greater than 5 minutes.** 1355 1355 1356 - 1357 1357 ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ==== 1358 1358 1359 - 1360 1360 Controls the digital outputs DO1, DO2, and DO3 1361 1361 1362 1362 (% style="color:#037691" %)**AT Command** ... ... @@ -1387,11 +1387,11 @@ 1387 1387 ((( 1388 1388 01: Low, 00: High, 11: No action 1389 1389 1390 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:383px" %)1391 -|(% 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**1392 -| (% style="width:126px" %)02 01 00 11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action1393 -| (% style="width:126px" %)02 00 11 01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low1394 -| (% 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 1395 1395 ))) 1396 1396 1397 1397 ((( ... ... @@ -1405,29 +1405,30 @@ 1405 1405 ))) 1406 1406 ))) 1407 1407 1408 - 1409 1409 ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ==== 1410 1410 1411 1411 1412 1412 * (% style="color:#037691" %)**AT Command** 1413 1413 1414 -There is no AT command to controlthe digitaloutput.1358 +There is no AT Command to control Digital Output 1415 1415 1416 1416 1417 1417 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)** 1418 1418 1419 -(% 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 1420 1420 1365 + 1421 1421 This is to control the digital output time of DO pin. Include four bytes: 1422 1422 1423 -(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)1368 +(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9) 1424 1424 1425 -(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode1370 +(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode 1426 1426 1427 -**01:** DO pins revert to their original state after the timeout. 1428 -**00:** DO pins switch to an inverted state after the timeout. 1372 +01: DO pins will change back to original state after timeout. 1429 1429 1374 +00: DO pins will change to an inverter state after timeout 1430 1430 1376 + 1431 1431 (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status: 1432 1432 1433 1433 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) ... ... @@ -1436,7 +1436,7 @@ 1436 1436 |0x00|DO1 set to high 1437 1437 |0x11|DO1 NO Action 1438 1438 1439 -(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:1385 +(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status: 1440 1440 1441 1441 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1442 1442 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1444,7 +1444,7 @@ 1444 1444 |0x00|DO2 set to high 1445 1445 |0x11|DO2 NO Action 1446 1446 1447 -(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:1393 +(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status: 1448 1448 1449 1449 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1450 1450 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1452,7 +1452,7 @@ 1452 1452 |0x00|DO3 set to high 1453 1453 |0x11|DO3 NO Action 1454 1454 1455 -(% 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) 1456 1456 1457 1457 1458 1458 (% style="color:red" %)**Note: ** ... ... @@ -1461,7 +1461,7 @@ 1461 1461 1462 1462 Before firmware v1.6.0, the latch time only supported 2 bytes. 1463 1463 1464 -(% 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.** 1465 1465 1466 1466 1467 1467 **Example payload:** ... ... @@ -1488,16 +1488,16 @@ 1488 1488 1489 1489 * (% style="color:#037691" %)**AT Command:** 1490 1490 1491 -There is no AT Command to control theRelay Output1437 +There is no AT Command to control Relay Output 1492 1492 1493 1493 1494 1494 * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):** 1495 1495 1496 -(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set sRO1/RO2 output1442 +(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set RO1/RO2 output 1497 1497 1498 1498 1499 1499 ((( 1500 -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. 1501 1501 ))) 1502 1502 1503 1503 ((( ... ... @@ -1515,29 +1515,28 @@ 1515 1515 |03 00 01|Open|Close 1516 1516 ))) 1517 1517 1518 -(% 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.** 1519 1519 1520 1520 1521 1521 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== 1522 1522 1523 - 1524 1524 Controls the relay output time. 1525 1525 1526 1526 * (% style="color:#037691" %)**AT Command:** 1527 1527 1528 -There is no AT Command to control theRelay Output1473 +There is no AT Command to control Relay Output 1529 1529 1530 1530 1531 1531 * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):** 1532 1532 1533 -(% 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 1534 1534 1535 1535 1536 -This control sthe relay output timeandincludes4bytes:1481 +This is to control the relay output time. It includes four bytes: 1537 1537 1538 -(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)1483 +(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05) 1539 1539 1540 -(% style="color:#4f81bd" %)**Second byte1485 +(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode 1541 1541 1542 1542 01: Relays will change back to their original state after timeout. 1543 1543 ... ... @@ -1544,12 +1544,12 @@ 1544 1544 00: Relays will change to the inverter state after timeout. 1545 1545 1546 1546 1547 -(% style="color:#4f81bd" %)**Third byte1492 +(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status: 1548 1548 1549 1549 [[image:image-20221008095908-1.png||height="364" width="564"]] 1550 1550 1551 1551 1552 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes1497 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms 1553 1553 1554 1554 1555 1555 (% style="color:red" %)**Note:** ... ... @@ -1559,7 +1559,7 @@ 1559 1559 Before firmware v1.6.0, the latch time only supported 2 bytes. 1560 1560 1561 1561 1562 -(% 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.** 1563 1563 1564 1564 1565 1565 **Example payload:** ... ... @@ -1718,10 +1718,8 @@ 1718 1718 ))) 1719 1719 |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01** 1720 1720 1666 +==== 3.4.2.19 Counting ~-~- Change counting mode to save time ==== 1721 1721 1722 -==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ==== 1723 - 1724 - 1725 1725 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. 1726 1726 1727 1727 (% style="color:#037691" %)**AT Command** ... ... @@ -1751,10 +1751,8 @@ 1751 1751 Sets the device to save its counting results to the memory every 60 seconds. 1752 1752 ))) 1753 1753 1697 +==== 3.4.2.20 Reset save RO DO state ==== 1754 1754 1755 -==== 3.4.2.20 Reset saved RO and DO states ==== 1756 - 1757 - 1758 1758 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. 1759 1759 1760 1760 (% style="color:#037691" %)**AT Command** ... ... @@ -1779,6 +1779,7 @@ 1779 1779 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. 1780 1780 ))) 1781 1781 1723 + 1782 1782 (% style="color:#037691" %)**Downlink Payload** 1783 1783 1784 1784 (% border="2" style="width:500px" %) ... ... @@ -1802,10 +1802,8 @@ 1802 1802 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. 1803 1803 ))) 1804 1804 1805 - 1806 1806 ==== 3.4.2.21 Encrypted payload ==== 1807 1807 1808 - 1809 1809 This command allows you to configure whether the device should upload data in an encrypted format or in plaintext. By default, the device encrypts the payload before uploading. You can toggle this setting to either upload encrypted data or transmit it without encryption. 1810 1810 1811 1811 (% style="color:#037691" %)**AT Command:** ... ... @@ -1835,7 +1835,6 @@ 1835 1835 1836 1836 ==== 3.4.2.22 Get sensor value ==== 1837 1837 1838 - 1839 1839 This command allows you to retrieve and optionally uplink sensor readings through the serial port. 1840 1840 1841 1841 (% style="color:#037691" %)**AT Command** ... ... @@ -1865,7 +1865,6 @@ 1865 1865 1866 1866 ==== 3.4.2.23 Resetting the downlink packet count ==== 1867 1867 1868 - 1869 1869 This command manages how the node handles mismatched downlink packet counts. It offers two modes: one disables the reception of further downlink packets if discrepancies occur, while the other resets the downlink packet count to align with the server, ensuring continued communication. 1870 1870 1871 1871 (% style="color:#037691" %)**AT Command** ... ... @@ -1942,36 +1942,45 @@ 1942 1942 Set DISMACANS=1 1943 1943 ))) 1944 1944 1945 - 1946 1946 ==== 3.4.2.25 Copy downlink to uplink ==== 1947 1947 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. 1948 1948 1949 - Thiscommandenableshe device to immediatelyuplink thepayload of a received downlink packet back tothe server.Thecommandallows for quick data replication from downlink to uplink, with a fixed port number of 100.1887 +* (% style="color:#037691" %)**AT Command**(%%)**:** 1950 1950 1951 -(% style="color: #037691" %)**ATCommand**(%%)**:**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. 1952 1952 1953 - (% style="color:blue" %)**AT+RPL=5**(%%)~/~/Afterreceivingadownlink payloadfromtherver,thedevice will immediately uplinkthe payloadback to the serverusingportnumber100.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. 1954 1954 1955 -Example:**aa xx xx xx xx** ~/~/ **aa** indicates whether the configuration has changed: **00** means YES, and **01** means NO. **xx xx xx xx** are the bytes uplinked back. 1956 1956 1957 - 1958 1958 [[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"]] 1959 1959 1960 1960 For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77. 1961 1961 1962 -[[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 1963 1963 1964 -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: 1965 1965 1907 +01 00 02 58 1966 1966 1967 - (% style="color:#037691" %)**DownlinkPayload**(%%)**:**1909 +Uplink: 1968 1968 1969 -There is no downlink option available for this feature. 1911 +01 01 00 02 58 1912 +))) 1970 1970 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"]] 1971 1971 1972 - ====3.4.2.26Queryfirmwareversion,frequency band,subband,andTDCtime====1916 +For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. 1973 1973 1974 1974 1919 + 1920 +==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ==== 1921 + 1975 1975 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. 1976 1976 1977 1977 * ((( ... ... @@ -1990,13 +1990,10 @@ 1990 1990 1991 1991 == 3.5 Integrating with ThingsEye.io == 1992 1992 1993 - 1994 1994 The Things Stack application supports integration with ThingsEye.io. Once integrated, ThingsEye.io acts as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic. 1995 1995 1996 - 1997 1997 === 3.5.1 Configuring The Things Stack === 1998 1998 1999 - 2000 2000 We use The Things Stack Sandbox in this example: 2001 2001 2002 2002 * In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added. ... ... @@ -2008,12 +2008,10 @@ 2008 2008 The username and password (API key) you created here are required in the next section. 2009 2009 {{/info}} 2010 2010 2011 -[[image:tts-mqtt-integration.png]] 1955 +[[image:tts-mqtt-integration.png||height="625" width="1000"]] 2012 2012 2013 - 2014 2014 === 3.5.2 Configuring ThingsEye.io === 2015 2015 2016 - 2017 2017 The ThingsEye.io IoT platform is not open for self-registration at the moment. If you are interested in testing the platform, please send your project information to admin@thingseye.io, and we will create an account for you. 2018 2018 2019 2019 * Login to your [[ThingsEye.io >>https://thingseye.io]]account. ... ... @@ -2020,7 +2020,7 @@ 2020 2020 * Under the **Integrations center**, click **Integrations**. 2021 2021 * Click the **Add integration** button (the button with the **+** symbol). 2022 2022 2023 -[[image:thingseye-io-step-1.png]] 1965 +[[image:thingseye-io-step-1.png||height="625" width="1000"]] 2024 2024 2025 2025 2026 2026 On the **Add integration** window, configure the following: ... ... @@ -2035,7 +2035,7 @@ 2035 2035 ** Allow create devices or assets 2036 2036 * Click the **Next** button. you will be navigated to the **Uplink data converter** tab. 2037 2037 2038 -[[image:thingseye-io-step-2.png]] 1980 +[[image:thingseye-io-step-2.png||height="625" width="1000"]] 2039 2039 2040 2040 2041 2041 **Uplink data converter:** ... ... @@ -2046,7 +2046,7 @@ 2046 2046 * 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]]. 2047 2047 * Click the **Next** button. You will be navigated to the **Downlink data converter **tab. 2048 2048 2049 -[[image:thingseye-io-step-3.png]] 1991 +[[image:thingseye-io-step-3.png||height="625" width="1000"]] 2050 2050 2051 2051 2052 2052 **Downlink data converter (this is an optional step):** ... ... @@ -2057,7 +2057,7 @@ 2057 2057 * 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]]. 2058 2058 * Click the **Next** button. You will be navigated to the **Connection** tab. 2059 2059 2060 -[[image:thingseye-io-step-4.png]] 2002 +[[image:thingseye-io-step-4.png||height="625" width="1000"]] 2061 2061 2062 2062 2063 2063 **Connection:** ... ... @@ -2072,21 +2072,20 @@ 2072 2072 2073 2073 * Click the **Add** button. 2074 2074 2075 -[[image:thingseye-io-step-5.png]] 2017 +[[image:thingseye-io-step-5.png||height="625" width="1000"]] 2076 2076 2077 2077 2078 2078 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. 2079 2079 2080 2080 2081 -[[image:thingseye.io_integrationsCenter_integrations.png]] 2023 +[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]] 2082 2082 2083 2083 2084 2084 ==== 3.5.2.1 Viewing integration details ==== 2085 2085 2086 - 2087 2087 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. 2088 2088 2089 -[[image:integration-details.png]] 2030 +[[image:integration-details.png||height="686" width="1000"]] 2090 2090 2091 2091 2092 2092 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. ... ... @@ -2095,32 +2095,28 @@ 2095 2095 See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]]. 2096 2096 {{/info}} 2097 2097 2039 +==== **3.5.2.2 Viewing events** ==== 2098 2098 2099 -==== 3.5.2.2 Viewing events ==== 2100 - 2101 - 2102 2102 The **Events **tab displays all the uplink messages from the LT-22222-L. 2103 2103 2104 2104 * Select **Debug **from the **Event type** dropdown. 2105 2105 * Select the** time frame** from the **time window**. 2106 2106 2107 -[[image:thingseye-events.png]] 2046 +[[image:thingseye-events.png||height="686" width="1000"]] 2108 2108 2109 2109 2110 2110 * To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message. 2111 2111 2112 -[[image:thingseye-json.png]] 2051 +[[image:thingseye-json.png||width="1000"]] 2113 2113 2114 2114 2115 -==== 3.5.2.3 Deleting an integration ==== 2054 +==== **3.5.2.3 Deleting an integration** ==== 2116 2116 2117 - 2118 2118 If you want to delete an integration, click the **Delete integratio**n button on the Integrations page. 2119 2119 2120 2120 2121 2121 ==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ==== 2122 2122 2123 - 2124 2124 This will be added soon. 2125 2125 2126 2126 ... ... @@ -2129,7 +2129,7 @@ 2129 2129 === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) === 2130 2130 2131 2131 2132 -Supports **NPN-type**sensors.2069 +Supports NPN-type sensors. 2133 2133 2134 2134 [[image:1653356991268-289.png]] 2135 2135 ... ... @@ -2251,15 +2251,15 @@ 2251 2251 ))) 2252 2252 2253 2253 2254 -(% style="color:blue" %)**Example aDry Contact sensor2191 +(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor 2255 2255 2256 -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. 2257 2257 2258 -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. 2259 2259 2260 2260 [[image:image-20230616235145-1.png]] 2261 2261 2262 -(% style="color:blue" %)**Example 2199 +(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector 2263 2263 2264 2264 [[image:image-20240219115718-1.png]] 2265 2265 ... ... @@ -2335,7 +2335,7 @@ 2335 2335 [[image:image-20220524100215-10.png||height="382" width="723"]] 2336 2336 2337 2337 2338 -== 3.7 LED Indicators == 2275 +== 3.7 LEDs Indicators == 2339 2339 2340 2340 The table below lists the behavior of LED indicators for each port function. 2341 2341 ... ... @@ -2374,14 +2374,13 @@ 2374 2374 == 4.1 Connecting the LT-22222-L to a PC == 2375 2375 2376 2376 ((( 2377 -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. 2378 2378 2379 -[[image:usb-ttl-audio-jack-connection.jpg]] 2380 - 2381 - 2316 +[[image:usb-ttl-programming.png]] 2382 2382 ))) 2383 2383 2384 2384 2320 + 2385 2385 ((( 2386 2386 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: 2387 2387 ))) ... ... @@ -2411,39 +2411,39 @@ 2411 2411 * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey) 2412 2412 * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI) 2413 2413 * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON) 2414 -* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)2415 -* **##AT+DR##**: Get or set the Data Rate. (0-7 corresponding to DR_X)2416 -* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing2417 -* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)2418 -* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency2419 -* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)2420 -* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms2421 -* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms2422 -* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms2423 -* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms2424 -* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)2425 -* ##**AT+NWKID**##: Get or set the Network ID2426 -* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)2427 -* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)2428 -* ##**AT+CLASS**##: Get or set the Device Class2429 -* ##**AT+JOIN**##: Join network2430 -* ##**AT+NJS**##: Get OTAA Join Status2431 -* ##**AT+SENDB**##: Send hexadecimal data along with the application port2432 -* ##**AT+SEND**##: Send text data along with the application port2433 -* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)2434 -* ##**AT+RECV**##: Print last received data in raw format2435 -* ##**AT+VER**##: Get current image version and Frequency Band2436 -* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)2437 -* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)2438 -* ##**AT+SNR**##: Get the SNR of the last received packet2439 -* ##**AT+RSSI**##: Get the RSSI of the last received packet2440 -* ##**AT+TDC**##: Get or set the application data transmission interval in ms2441 -* ##**AT+PORT**##: Get or set the application port2442 -* ##**AT+DISAT**##: Disable AT commands2443 -* ##**AT+PWORD**##: Set password, max 9 digits2444 -* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode2445 -* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN4702446 -* ##**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 2447 2447 ))) 2448 2448 2449 2449 ... ... @@ -2608,7 +2608,7 @@ 2608 2608 You will need the following things before proceeding: 2609 2609 2610 2610 * 3.5mm programming cable (included with the LT-22222-L as an additional accessory) 2611 -* USB to TTL adapter /converter2547 +* USB to TTL adapter 2612 2612 * 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) 2613 2613 * 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. 2614 2614 ... ... @@ -2618,7 +2618,7 @@ 2618 2618 2619 2619 Below is the hardware setup for uploading a firmware image to the LT-22222-L: 2620 2620 2621 -[[image:usb-ttl- audio-jack-connection.jpg]]2557 +[[image:usb-ttl-programming.png]] 2622 2622 2623 2623 2624 2624
- 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