Skip to Content
Last modified by Mengting Qiu on 2025/06/04 18:42
From version 218.1
edited by Dilisi S
on 2024/11/25 01:50
Change comment: Uploaded new attachment "lt-22222-l-joining.png", version {1}
To version 230.11
edited by Xiaoling
on 2024/12/09 10:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.pradeeka
1 +XWiki.Xiaoling
Content
... ... @@ -54,8 +54,10 @@
54 54  (% class="wikigeneratedid" %)
55 55  [[image:lorawan-nw.jpg||height="354" width="900"]]
56 56  
57 +
57 57  == 1.2 Specifications ==
58 58  
60 +
59 59  (% style="color:#037691" %)**Hardware System:**
60 60  
61 61  * STM32L072xxxx MCU
... ... @@ -116,11 +116,13 @@
116 116  
117 117  == 1.5 Hardware Variants ==
118 118  
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" %)(((
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" %)(((
124 124  * 2 x Digital Input (Bi-direction)
125 125  * 2 x Digital Output
126 126  * 2 x Relay Output (5A@250VAC / 30VDC)
... ... @@ -174,7 +174,7 @@
174 174  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.
175 175  
176 176  {{warning}}
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.**
181 +**We recommend that you power on the LT-22222-L after adding its registration information to the LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.**
178 178  {{/warning}}
179 179  
180 180  
... ... @@ -237,7 +237,7 @@
237 237  *** **Profile (Region)**: Select the region that matches your device.
238 238  ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
239 239  
240 -[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
244 +[[image:lt-22222-l-dev-repo-reg-p1.png]]
241 241  
242 242  
243 243  * Register end device page continued...
... ... @@ -247,7 +247,7 @@
247 247  ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
248 248  ** Under **After registration**, select the **View registered end device** option.
249 249  
250 -[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
254 +[[image:lt-22222-l-dev-repo-reg-p2.png]]
251 251  
252 252  
253 253  ==== 3.2.2.3 Adding device manually ====
... ... @@ -261,7 +261,7 @@
261 261  ** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
262 262  ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
263 263  
264 -[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
268 +[[image:lt-22222-l-manually-p1.png]]
265 265  
266 266  
267 267  * Register end device page continued...
... ... @@ -272,13 +272,13 @@
272 272  ** Under **After registration**, select the **View registered end device** option.
273 273  ** Click the **Register end device** button.
274 274  
275 -[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
279 +[[image:lt-22222-l-manually-p2.png]]
276 276  
277 277  
278 278  You will be navigated to the **Device overview** page.
279 279  
280 280  
281 -[[image:lt-22222-device-overview.png||height="625" width="1000"]]
285 +[[image:lt-22222-device-overview.png]]
282 282  
283 283  
284 284  ==== 3.2.2.4 Joining ====
... ... @@ -288,9 +288,10 @@
288 288  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.
289 289  
290 290  
291 -[[image:lt-22222-join-network.png||height="625" width="1000"]]
295 +[[image:lt-22222-l-joining.png]]
292 292  
293 293  
298 +
294 294  ==== 3.2.2.5 Uplinks ====
295 295  
296 296  
... ... @@ -307,9 +307,15 @@
307 307  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.
308 308  {{/info}}
309 309  
310 -[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
315 +[[image:lt-22222-ul-payload-fmt.png]]
311 311  
312 312  
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 +
313 313  ==== 3.2.2.6 Downlinks ====
314 314  
315 315  When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
... ... @@ -598,11 +598,11 @@
598 598  
599 599  (% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)**
600 600  
601 -(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
612 +(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), the counter increases by 1)**
602 602  
603 -(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
614 +(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If the AVI1 voltage is lower than VOLMAX (20000mV =20V), counter increases by 1)**
604 604  
605 -(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
616 +(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), counter increases by 1)**
606 606  )))
607 607  
608 608  
... ... @@ -721,9 +721,9 @@
721 721  
722 722  (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
723 723  
724 -Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
735 +**Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
725 725  
726 -Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
737 +**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
727 727  
728 728   AA: Type Code for this downlink Command:
729 729  
... ... @@ -752,7 +752,7 @@
752 752  
753 753  MOD6 Payload: total of 11 bytes
754 754  
755 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
766 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
756 756  |(% 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**
757 757  |Value|(((
758 758  TRI_A FLAG
... ... @@ -766,7 +766,7 @@
766 766  
767 767  (% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
768 768  
769 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
780 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
770 770  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
771 771  |(((
772 772  AV1_LOW
... ... @@ -790,12 +790,12 @@
790 790  
791 791  **Example:**
792 792  
793 -10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW
804 +10100000: This means the system is configured to use the triggers AV1_LOW and AV2_LOW.
794 794  
795 795  
796 796  (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
797 797  
798 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
809 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
799 799  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
800 800  |(((
801 801  AV1_LOW
... ... @@ -819,31 +819,31 @@
819 819  
820 820  **Example:**
821 821  
822 -10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.
833 +10000000: The uplink is triggered by AV1_LOW, indicating that the voltage is too low.
823 823  
824 824  
825 825  (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
826 826  
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**
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
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:49px" %)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_FLAG
830 830  
831 -* Each bits shows which status has been triggered on this uplink.
842 +* Each bit shows which status has been triggered on this uplink.
832 832  
833 833  **Example:**
834 834  
835 -00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
846 +00000111: This means both DI1 and DI2 triggers are enabled, and this packet is trigger by DI1.
836 836  
837 -00000101: Means both DI1 and DI2 trigger are enabled.
848 +00000101: This means both DI1 and DI2 triggers are enabled.
838 838  
839 839  
840 -(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable.
851 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled.
841 841  
842 -Downlink command to poll MOD6 status:
853 +Downlink command to poll/request MOD6 status:
843 843  
844 844  **AB 06**
845 845  
846 -When device got this command, it will send the MOD6 payload.
857 +When device receives this command, it will send the MOD6 payload.
847 847  
848 848  
849 849  === 3.3.7 Payload Decoder ===
... ... @@ -857,6 +857,7 @@
857 857  
858 858  == 3.4 ​Configure LT-22222-L via AT Commands or Downlinks ==
859 859  
871 +
860 860  (((
861 861  You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks.
862 862  )))
... ... @@ -871,19 +871,25 @@
871 871  
872 872  * (% style="color:blue" %)**Sensor-related commands**(%%):
873 873  
886 +
874 874  === 3.4.1 Common commands ===
875 875  
889 +
876 876  (((
877 877  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 +
878 878  )))
879 879  
880 880  === 3.4.2 Sensor-related commands ===
881 881  
898 +
882 882  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.
883 883  
884 884  
885 885  ==== 3.4.2.1 Set Transmit/Uplink Interval ====
886 886  
904 +
887 887  Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
888 888  
889 889  (% style="color:#037691" %)**AT command**
... ... @@ -890,8 +890,15 @@
890 890  
891 891  (% border="2" style="width:500px" %)
892 892  |**Command**|AT+TDC=<time>
893 -|**Response**|
894 -|**Parameters**|**time** : uplink interval is in **milliseconds**
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
895 895  |**Example**|(((
896 896  AT+TDC=30000
897 897  
... ... @@ -907,7 +907,7 @@
907 907  |**Parameters**|(((
908 908  **prefix** : 0x01
909 909  
910 -**time** : uplink interval is in **seconds**, represented by **3  bytes** in **hexadecimal**.
935 +**time** : uplink interval in **seconds**, represented by **3  bytes** in **hexadecimal**.
911 911  )))
912 912  |**Example**|(((
913 913  01 **00 00 1E**
... ... @@ -923,13 +923,13 @@
923 923  
924 924  ==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
925 925  
951 +
926 926  Sets the working mode.
927 927  
928 928  (% style="color:#037691" %)**AT command**
929 929  
930 930  (% border="2" style="width:500px" %)
931 -|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE=<working_mode>
932 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)
957 +|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MOD=<working_mode>
933 933  |(% style="width:97px" %)**Parameters**|(% style="width:413px" %)(((
934 934  **working_mode** :
935 935  
... ... @@ -945,6 +945,18 @@
945 945  
946 946  6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5
947 947  )))
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 +)))
948 948  |(% style="width:97px" %)**Example**|(% style="width:413px" %)(((
949 949  AT+MOD=2
950 950  
... ... @@ -967,8 +967,10 @@
967 967  Sets the device to working mode 2 (Double DI Counting + DO + RO)
968 968  )))
969 969  
970 -==== 3.4.2.3 Poll an uplink ====
971 971  
1008 +==== 3.4.2.3 Request an uplink from the device ====
1009 +
1010 +
972 972  Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.
973 973  
974 974  (% style="color:#037691" %)**AT command**
... ... @@ -986,8 +986,10 @@
986 986  Requests an uplink from LT-22222-L.
987 987  )))
988 988  
1028 +
989 989  ==== 3.4.2.4 Enable/Disable Trigger Mode ====
990 990  
1031 +
991 991  Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
992 992  
993 993  (% style="color:#037691" %)**AT Command**
... ... @@ -1023,10 +1023,12 @@
1023 1023  Enable trigger mode for the current working mode
1024 1024  )))
1025 1025  
1026 -==== 3.4.2.5 Poll trigger settings ====
1027 1027  
1028 -Polls the trigger settings.
1068 +==== 3.4.2.5 Request trigger settings ====
1029 1029  
1070 +
1071 +Requests the trigger settings.
1072 +
1030 1030  (% style="color:#037691" %)**AT Command:**
1031 1031  
1032 1032  There is no AT Command available for this feature.
... ... @@ -1042,8 +1042,10 @@
1042 1042  Uplinks the trigger settings.
1043 1043  )))
1044 1044  
1088 +
1045 1045  ==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ====
1046 1046  
1091 +
1047 1047  Enable or disable DI1/DI2/DI3 as a trigger.
1048 1048  
1049 1049  (% style="color:#037691" %)**AT Command**
... ... @@ -1096,11 +1096,12 @@
1096 1096  Enable DI1 trigger, disable DI2 trigger
1097 1097  )))
1098 1098  
1144 +
1099 1099  ==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ====
1100 1100  
1147 +
1101 1101  Sets DI1 or DI3 (for LT-33222-L) as a trigger.
1102 1102  
1103 -
1104 1104  (% style="color:#037691" %)**AT Command**
1105 1105  
1106 1106  (% border="2" style="width:500px" %)
... ... @@ -1135,11 +1135,12 @@
1135 1135  Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms.
1136 1136  )))
1137 1137  
1184 +
1138 1138  ==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
1139 1139  
1187 +
1140 1140  Sets DI2 as a trigger.
1141 1141  
1142 -
1143 1143  (% style="color:#037691" %)**AT Command**
1144 1144  
1145 1145  (% border="2" style="width:500px" %)
... ... @@ -1169,8 +1169,10 @@
1169 1169  )))
1170 1170  |(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64**
1171 1171  
1219 +
1172 1172  ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
1173 1173  
1222 +
1174 1174  Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1175 1175  
1176 1176  (% style="color:#037691" %)**AT Command**
... ... @@ -1218,8 +1218,10 @@
1218 1218  )))
1219 1219  |(% style="width:104px" %)Note|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1220 1220  
1270 +
1221 1221  ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
1222 1222  
1273 +
1223 1223  Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1224 1224  
1225 1225  (% style="color:#037691" %)**AT Command**
... ... @@ -1265,8 +1265,10 @@
1265 1265  )))
1266 1266  |(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1267 1267  
1319 +
1268 1268  ==== 3.4.2.11 Trigger – Set minimum interval ====
1269 1269  
1322 +
1270 1270  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.
1271 1271  
1272 1272  (% style="color:#037691" %)**AT Command**
... ... @@ -1300,8 +1300,10 @@
1300 1300  )))
1301 1301  |(% style="width:112px" %)Note|(% style="width:386px" %)(% style="color:red" %)**The time must be greater than 5 minutes.**
1302 1302  
1356 +
1303 1303  ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
1304 1304  
1359 +
1305 1305  Controls the digital outputs DO1, DO2, and DO3
1306 1306  
1307 1307  (% style="color:#037691" %)**AT Command**
... ... @@ -1332,11 +1332,11 @@
1332 1332  (((
1333 1333  01: Low,  00: High,  11: No action
1334 1334  
1335 -(% 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
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 Action
1393 +|(% style="width:126px" %)02  00  11  01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low
1394 +|(% style="width:126px" %)02  11  01  00|(% style="width:85px" %)No Action|(% style="width:86px" %)Low|(% style="width:86px" %)High
1340 1340  )))
1341 1341  
1342 1342  (((
... ... @@ -1350,30 +1350,29 @@
1350 1350  )))
1351 1351  )))
1352 1352  
1408 +
1353 1353  ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
1354 1354  
1355 1355  
1356 1356  * (% style="color:#037691" %)**AT Command**
1357 1357  
1358 -There is no AT Command to control Digital Output
1414 +There is no AT command to control the digital output.
1359 1359  
1360 1360  
1361 1361  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
1362 1362  
1363 -(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Set DO1/DO2/DO3 output with time control
1419 +(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control
1364 1364  
1365 -
1366 1366  This is to control the digital output time of DO pin. Include four bytes:
1367 1367  
1368 -(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
1423 +(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)
1369 1369  
1370 -(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode
1425 +(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode
1371 1371  
1372 -01: DO pins will change back to original state after timeout.
1427 +**01:** DO pins revert to their original state after the timeout.
1428 +**00:** DO pins switch to an inverted state after the timeout.
1373 1373  
1374 -00: DO pins will change to an inverter state after timeout 
1375 1375  
1376 -
1377 1377  (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
1378 1378  
1379 1379  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
... ... @@ -1382,7 +1382,7 @@
1382 1382  |0x00|DO1 set to high
1383 1383  |0x11|DO1 NO Action
1384 1384  
1385 -(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:
1439 +(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:
1386 1386  
1387 1387  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1388 1388  |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
... ... @@ -1390,7 +1390,7 @@
1390 1390  |0x00|DO2 set to high
1391 1391  |0x11|DO2 NO Action
1392 1392  
1393 -(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:
1447 +(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:
1394 1394  
1395 1395  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1396 1396  |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
... ... @@ -1398,7 +1398,7 @@
1398 1398  |0x00|DO3 set to high
1399 1399  |0x11|DO3 NO Action
1400 1400  
1401 -(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)
1455 +(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms)
1402 1402  
1403 1403  
1404 1404  (% style="color:red" %)**Note: **
... ... @@ -1407,7 +1407,7 @@
1407 1407  
1408 1408   Before firmware v1.6.0, the latch time only supported 2 bytes.
1409 1409  
1410 -(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1464 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1411 1411  
1412 1412  
1413 1413  **Example payload:**
... ... @@ -1434,16 +1434,16 @@
1434 1434  
1435 1435  * (% style="color:#037691" %)**AT Command:**
1436 1436  
1437 -There is no AT Command to control Relay Output
1491 +There is no AT Command to control the Relay Output
1438 1438  
1439 1439  
1440 1440  * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
1441 1441  
1442 -(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Set RO1/RO2 output
1496 +(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Sets RO1/RO2 output
1443 1443  
1444 1444  
1445 1445  (((
1446 -If payload is 0x030100, it means setting RO1 to close and RO2 to open.
1500 +If the payload is 0x030100, it means setting RO1 to close and RO2 to open.
1447 1447  )))
1448 1448  
1449 1449  (((
... ... @@ -1461,28 +1461,29 @@
1461 1461  |03  00  01|Open|Close
1462 1462  )))
1463 1463  
1464 -(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
1518 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1465 1465  
1466 1466  
1467 1467  ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
1468 1468  
1523 +
1469 1469  Controls the relay output time.
1470 1470  
1471 1471  * (% style="color:#037691" %)**AT Command:**
1472 1472  
1473 -There is no AT Command to control Relay Output
1528 +There is no AT Command to control the Relay Output
1474 1474  
1475 1475  
1476 1476  * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1477 1477  
1478 -(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Set RO1/RO2 relay with time control
1533 +(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
1479 1479  
1480 1480  
1481 -This is to control the relay output time. It includes four bytes:
1536 +This controls the relay output time and includes 4 bytes:
1482 1482  
1483 -(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
1538 +(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)
1484 1484  
1485 -(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
1540 +(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode
1486 1486  
1487 1487  01: Relays will change back to their original state after timeout.
1488 1488  
... ... @@ -1489,12 +1489,12 @@
1489 1489  00: Relays will change to the inverter state after timeout.
1490 1490  
1491 1491  
1492 -(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
1547 +(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status:
1493 1493  
1494 1494  [[image:image-20221008095908-1.png||height="364" width="564"]]
1495 1495  
1496 1496  
1497 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms
1552 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes (cc)**(%%): Latching time. Unit: ms
1498 1498  
1499 1499  
1500 1500  (% style="color:red" %)**Note:**
... ... @@ -1504,7 +1504,7 @@
1504 1504   Before firmware v1.6.0, the latch time only supported 2 bytes.
1505 1505  
1506 1506  
1507 -(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1562 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1508 1508  
1509 1509  
1510 1510  **Example payload:**
... ... @@ -1663,8 +1663,10 @@
1663 1663  )))
1664 1664  |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
1665 1665  
1666 -==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1667 1667  
1722 +==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ====
1723 +
1724 +
1668 1668  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.
1669 1669  
1670 1670  (% style="color:#037691" %)**AT Command**
... ... @@ -1694,8 +1694,10 @@
1694 1694  Sets the device to save its counting results to the memory every 60 seconds.
1695 1695  )))
1696 1696  
1697 -==== 3.4.2.20 Reset save RO DO state ====
1698 1698  
1755 +==== 3.4.2.20 Reset saved RO and DO states ====
1756 +
1757 +
1699 1699  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.
1700 1700  
1701 1701  (% style="color:#037691" %)**AT Command**
... ... @@ -1743,8 +1743,10 @@
1743 1743  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.
1744 1744  )))
1745 1745  
1805 +
1746 1746  ==== 3.4.2.21 Encrypted payload ====
1747 1747  
1808 +
1748 1748  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.
1749 1749  
1750 1750  (% style="color:#037691" %)**AT Command:**
... ... @@ -1774,6 +1774,7 @@
1774 1774  
1775 1775  ==== 3.4.2.22 Get sensor value ====
1776 1776  
1838 +
1777 1777  This command allows you to retrieve and optionally uplink sensor readings through the serial port.
1778 1778  
1779 1779  (% style="color:#037691" %)**AT Command**
... ... @@ -1803,6 +1803,7 @@
1803 1803  
1804 1804  ==== 3.4.2.23 Resetting the downlink packet count ====
1805 1805  
1868 +
1806 1806  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.
1807 1807  
1808 1808  (% style="color:#037691" %)**AT Command**
... ... @@ -1879,45 +1879,36 @@
1879 1879  Set DISMACANS=1
1880 1880  )))
1881 1881  
1945 +
1882 1882  ==== 3.4.2.25 Copy downlink to uplink ====
1883 1883  
1884 -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.
1885 1885  
1886 -* (% style="color:#037691" %)**AT Command**(%%)**:**
1949 +This command enables the device to immediately uplink the payload 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.
1887 1887  
1888 -(% 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.
1951 +(% style="color:#037691" %)**AT Command**(%%)**:**
1889 1889  
1890 -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.
1953 +(% style="color:blue" %)**AT+RPL=5**   (%%) ~/~/ After receiving a downlink payload from the server, the device will immediately uplink the payload back to the server using port number 100.
1891 1891  
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.
1892 1892  
1957 +
1893 1893  [[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"]]
1894 1894  
1895 1895  For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
1896 1896  
1897 -(% border="2" style="width:500px" %)
1898 -|(% style="width:122px" %)**Command**|(% style="width:376px" %)(((
1899 -AT+RPL=5
1900 -
1901 -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.
1902 -)))
1903 -|(% style="width:122px" %)**Example**|(% style="width:376px" %)(((
1904 -Downlink:
1905 -
1906 -01 00 02 58
1907 -
1908 -Uplink:
1909 -
1910 -01 01 00 02 58
1911 -)))
1912 -
1913 1913  [[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"]]
1914 1914  
1915 1915  For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
1916 1916  
1917 1917  
1967 +(% style="color:#037691" %)**Downlink Payload**(%%)**:**
1918 1918  
1969 +There is no downlink option available for this feature.
1970 +
1971 +
1919 1919  ==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
1920 1920  
1974 +
1921 1921  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.
1922 1922  
1923 1923  * (((
... ... @@ -1936,10 +1936,13 @@
1936 1936  
1937 1937  == 3.5 Integrating with ThingsEye.io ==
1938 1938  
1993 +
1939 1939  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.
1940 1940  
1996 +
1941 1941  === 3.5.1 Configuring The Things Stack ===
1942 1942  
1999 +
1943 1943  We use The Things Stack Sandbox in this example:
1944 1944  
1945 1945  * In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
... ... @@ -1951,10 +1951,12 @@
1951 1951  The username and  password (API key) you created here are required in the next section.
1952 1952  {{/info}}
1953 1953  
1954 -[[image:tts-mqtt-integration.png||height="625" width="1000"]]
2011 +[[image:tts-mqtt-integration.png]]
1955 1955  
2013 +
1956 1956  === 3.5.2 Configuring ThingsEye.io ===
1957 1957  
2016 +
1958 1958  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.
1959 1959  
1960 1960  * Login to your [[ThingsEye.io >>https://thingseye.io]]account.
... ... @@ -1961,7 +1961,7 @@
1961 1961  * Under the **Integrations center**, click **Integrations**.
1962 1962  * Click the **Add integration** button (the button with the **+** symbol).
1963 1963  
1964 -[[image:thingseye-io-step-1.png||height="625" width="1000"]]
2023 +[[image:thingseye-io-step-1.png]]
1965 1965  
1966 1966  
1967 1967  On the **Add integration** window, configure the following:
... ... @@ -1976,7 +1976,7 @@
1976 1976  ** Allow create devices or assets
1977 1977  * Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
1978 1978  
1979 -[[image:thingseye-io-step-2.png||height="625" width="1000"]]
2038 +[[image:thingseye-io-step-2.png]]
1980 1980  
1981 1981  
1982 1982  **Uplink data converter:**
... ... @@ -1987,7 +1987,7 @@
1987 1987  * 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]].
1988 1988  * Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
1989 1989  
1990 -[[image:thingseye-io-step-3.png||height="625" width="1000"]]
2049 +[[image:thingseye-io-step-3.png]]
1991 1991  
1992 1992  
1993 1993  **Downlink data converter (this is an optional step):**
... ... @@ -1998,7 +1998,7 @@
1998 1998  * 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]].
1999 1999  * Click the **Next** button. You will be navigated to the **Connection** tab.
2000 2000  
2001 -[[image:thingseye-io-step-4.png||height="625" width="1000"]]
2060 +[[image:thingseye-io-step-4.png]]
2002 2002  
2003 2003  
2004 2004  **Connection:**
... ... @@ -2013,20 +2013,21 @@
2013 2013  
2014 2014  * Click the **Add** button.
2015 2015  
2016 -[[image:thingseye-io-step-5.png||height="625" width="1000"]]
2075 +[[image:thingseye-io-step-5.png]]
2017 2017  
2018 2018  
2019 2019  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.
2020 2020  
2021 2021  
2022 -[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
2081 +[[image:thingseye.io_integrationsCenter_integrations.png]]
2023 2023  
2024 2024  
2025 2025  ==== 3.5.2.1 Viewing integration details ====
2026 2026  
2086 +
2027 2027  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.
2028 2028  
2029 -[[image:integration-details.png||height="686" width="1000"]]
2089 +[[image:integration-details.png]]
2030 2030  
2031 2031  
2032 2032  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.
... ... @@ -2035,28 +2035,32 @@
2035 2035  See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
2036 2036  {{/info}}
2037 2037  
2038 -==== **3.5.2.2 Viewing events** ====
2039 2039  
2099 +==== 3.5.2.2 Viewing events ====
2100 +
2101 +
2040 2040  The **Events **tab displays all the uplink messages from the LT-22222-L.
2041 2041  
2042 2042  * Select **Debug **from the **Event type** dropdown.
2043 2043  * Select the** time frame** from the **time window**.
2044 2044  
2045 -[[image:thingseye-events.png||height="686" width="1000"]]
2107 +[[image:thingseye-events.png]]
2046 2046  
2047 2047  
2048 2048  * To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
2049 2049  
2050 -[[image:thingseye-json.png||width="1000"]]
2112 +[[image:thingseye-json.png]]
2051 2051  
2052 2052  
2053 -==== **3.5.2.3 Deleting an integration** ====
2115 +==== 3.5.2.3 Deleting an integration ====
2054 2054  
2117 +
2055 2055  If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
2056 2056  
2057 2057  
2058 2058  ==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
2059 2059  
2123 +
2060 2060  This will be added soon.
2061 2061  
2062 2062  
... ... @@ -2065,7 +2065,7 @@
2065 2065  === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
2066 2066  
2067 2067  
2068 -Supports** NPN-type **sensors.
2132 +Supports** NPN-type **sensors.
2069 2069  
2070 2070  [[image:1653356991268-289.png]]
2071 2071  
lt-22222-l-joining.png
Size
... ... @@ -1,1 +1,1 @@
1 -274.1 KB
1 +301.9 KB
Content
Screenshot 2024-12-08 193946.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +32.4 KB
Content
lt-22222-l-js-custom-payload-formatter.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +453.9 KB
Content
lt33222-l.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +31.3 KB
Content