Skip to Content
Last modified by Mengting Qiu on 2025/06/04 18:42
From version 230.12
edited by Xiaoling
on 2024/12/09 10:15
Change comment: There is no comment for this version
To version 215.1
edited by Dilisi S
on 2024/11/24 05:05
Change comment: fix formatting

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.pradeeka
Content
... ... @@ -21,7 +21,6 @@
21 21  
22 22  == 1.1 What is the LT-22222-L I/O Controller? ==
23 23  
24 -
25 25  (((
26 26  (((
27 27  {{info}}
... ... @@ -55,10 +55,8 @@
55 55  (% class="wikigeneratedid" %)
56 56  [[image:lorawan-nw.jpg||height="354" width="900"]]
57 57  
58 -
59 59  == 1.2 Specifications ==
60 60  
61 -
62 62  (% style="color:#037691" %)**Hardware System:**
63 63  
64 64  * STM32L072xxxx MCU
... ... @@ -98,11 +98,8 @@
98 98  * Automatic RF Sense and CAD with ultra-fast AFC.
99 99  * Packet engine up to 256 bytes with CRC.
100 100  
101 -
102 -
103 103  == 1.3 Features ==
104 104  
105 -
106 106  * LoRaWAN Class A & Class C modes
107 107  * Optional Customized LoRa Protocol
108 108  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
... ... @@ -111,11 +111,8 @@
111 111  * Firmware upgradable via program port
112 112  * Counting
113 113  
114 -
115 -
116 116  == 1.4 Applications ==
117 117  
118 -
119 119  * Smart buildings & home automation
120 120  * Logistics and supply chain management
121 121  * Smart metering
... ... @@ -123,17 +123,13 @@
123 123  * Smart cities
124 124  * Smart factory
125 125  
126 -
127 -
128 128  == 1.5 Hardware Variants ==
129 129  
130 -
131 -(% border="1" cellspacing="3" style="width:510px" %)
132 -|(% 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**
133 -|(% style="width:94px" %)**LT-22222-L**|(% style="width:172px" %)(((
134 -(% style="text-align:center" %)
135 -[[image:lt33222-l.jpg||height="116" width="100"]]
136 -)))|(% 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" %)(((
137 137  * 2 x Digital Input (Bi-direction)
138 138  * 2 x Digital Output
139 139  * 2 x Relay Output (5A@250VAC / 30VDC)
... ... @@ -187,7 +187,7 @@
187 187  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.
188 188  
189 189  {{warning}}
190 -**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.**
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.**
191 191  {{/warning}}
192 192  
193 193  
... ... @@ -250,7 +250,7 @@
250 250  *** **Profile (Region)**: Select the region that matches your device.
251 251  ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
252 252  
253 -[[image:lt-22222-l-dev-repo-reg-p1.png]]
240 +[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
254 254  
255 255  
256 256  * Register end device page continued...
... ... @@ -260,7 +260,7 @@
260 260  ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
261 261  ** Under **After registration**, select the **View registered end device** option.
262 262  
263 -[[image:lt-22222-l-dev-repo-reg-p2.png]]
250 +[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
264 264  
265 265  
266 266  ==== 3.2.2.3 Adding device manually ====
... ... @@ -274,7 +274,7 @@
274 274  ** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
275 275  ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
276 276  
277 -[[image:lt-22222-l-manually-p1.png]]
264 +[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
278 278  
279 279  
280 280  * Register end device page continued...
... ... @@ -285,13 +285,13 @@
285 285  ** Under **After registration**, select the **View registered end device** option.
286 286  ** Click the **Register end device** button.
287 287  
288 -[[image:lt-22222-l-manually-p2.png]]
275 +[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
289 289  
290 290  
291 291  You will be navigated to the **Device overview** page.
292 292  
293 293  
294 -[[image:lt-22222-device-overview.png]]
281 +[[image:lt-22222-device-overview.png||height="625" width="1000"]]
295 295  
296 296  
297 297  ==== 3.2.2.4 Joining ====
... ... @@ -301,10 +301,9 @@
301 301  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.
302 302  
303 303  
304 -[[image:lt-22222-l-joining.png]]
291 +[[image:lt-22222-join-network.png||height="625" width="1000"]]
305 305  
306 306  
307 -
308 308  ==== 3.2.2.5 Uplinks ====
309 309  
310 310  
... ... @@ -321,15 +321,9 @@
321 321  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.
322 322  {{/info}}
323 323  
324 -[[image:lt-22222-ul-payload-fmt.png]]
310 +[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
325 325  
326 326  
327 -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]]:
328 -
329 -(% class="wikigeneratedid" %)
330 -[[image:lt-22222-l-js-custom-payload-formatter.png]]
331 -
332 -
333 333  ==== 3.2.2.6 Downlinks ====
334 334  
335 335  When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
... ... @@ -618,11 +618,11 @@
618 618  
619 619  (% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)**
620 620  
621 -(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), the counter increases by 1)**
601 +(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
622 622  
623 -(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If the AVI1 voltage is lower than VOLMAX (20000mV =20V), counter increases by 1)**
603 +(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
624 624  
625 -(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), counter increases by 1)**
605 +(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
626 626  )))
627 627  
628 628  
... ... @@ -741,9 +741,9 @@
741 741  
742 742  (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
743 743  
744 -**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**
745 745  
746 -**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
726 +Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
747 747  
748 748   AA: Type Code for this downlink Command:
749 749  
... ... @@ -772,7 +772,7 @@
772 772  
773 773  MOD6 Payload: total of 11 bytes
774 774  
775 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
755 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
776 776  |(% 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**
777 777  |Value|(((
778 778  TRI_A FLAG
... ... @@ -786,7 +786,7 @@
786 786  
787 787  (% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
788 788  
789 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
769 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
790 790  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
791 791  |(((
792 792  AV1_LOW
... ... @@ -810,12 +810,12 @@
810 810  
811 811  **Example:**
812 812  
813 -10100000: This means the system is configured to use the triggers AV1_LOW and AV2_LOW.
793 +10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW
814 814  
815 815  
816 816  (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
817 817  
818 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
798 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
819 819  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
820 820  |(((
821 821  AV1_LOW
... ... @@ -839,31 +839,31 @@
839 839  
840 840  **Example:**
841 841  
842 -10000000: The uplink is triggered by AV1_LOW, indicating that the voltage is too low.
822 +10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.
843 843  
844 844  
845 845  (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
846 846  
847 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
848 -|(% 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**
849 -|(% 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
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
850 850  
851 -* Each bit shows which status has been triggered on this uplink.
831 +* Each bits shows which status has been triggered on this uplink.
852 852  
853 853  **Example:**
854 854  
855 -00000111: This means both DI1 and DI2 triggers are 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.
856 856  
857 -00000101: This means both DI1 and DI2 triggers are enabled.
837 +00000101: Means both DI1 and DI2 trigger are enabled.
858 858  
859 859  
860 -(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled.
840 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable.
861 861  
862 -Downlink command to poll/request MOD6 status:
842 +Downlink command to poll MOD6 status:
863 863  
864 864  **AB 06**
865 865  
866 -When device receives this command, it will send the MOD6 payload.
846 +When device got this command, it will send the MOD6 payload.
867 867  
868 868  
869 869  === 3.3.7 Payload Decoder ===
... ... @@ -877,7 +877,6 @@
877 877  
878 878  == 3.4 ​Configure LT-22222-L via AT Commands or Downlinks ==
879 879  
880 -
881 881  (((
882 882  You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks.
883 883  )))
... ... @@ -892,25 +892,19 @@
892 892  
893 893  * (% style="color:blue" %)**Sensor-related commands**(%%):
894 894  
895 -
896 896  === 3.4.1 Common commands ===
897 897  
898 -
899 899  (((
900 900  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.
901 -
902 -
903 903  )))
904 904  
905 905  === 3.4.2 Sensor-related commands ===
906 906  
907 -
908 908  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.
909 909  
910 910  
911 911  ==== 3.4.2.1 Set Transmit/Uplink Interval ====
912 912  
913 -
914 914  Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
915 915  
916 916  (% style="color:#037691" %)**AT command**
... ... @@ -917,15 +917,8 @@
917 917  
918 918  (% border="2" style="width:500px" %)
919 919  |**Command**|AT+TDC=<time>
920 -|**Parameters**|**time **: uplink interval in milliseconds
921 -|**Get**|AT+TDC=?
922 -|**Response**|(((
923 -current uplink interval
924 -
925 -OK
926 -)))
927 -|**Set**|AT+TDC=<time>
928 -|**Response**|OK
893 +|**Response**|
894 +|**Parameters**|**time** : uplink interval is in **milliseconds**
929 929  |**Example**|(((
930 930  AT+TDC=30000
931 931  
... ... @@ -941,7 +941,7 @@
941 941  |**Parameters**|(((
942 942  **prefix** : 0x01
943 943  
944 -**time** : uplink interval in **seconds**, represented by **3  bytes** in **hexadecimal**.
910 +**time** : uplink interval is in **seconds**, represented by **3  bytes** in **hexadecimal**.
945 945  )))
946 946  |**Example**|(((
947 947  01 **00 00 1E**
... ... @@ -957,13 +957,13 @@
957 957  
958 958  ==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
959 959  
960 -
961 961  Sets the working mode.
962 962  
963 963  (% style="color:#037691" %)**AT command**
964 964  
965 965  (% border="2" style="width:500px" %)
966 -|(% 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" %)
967 967  |(% style="width:97px" %)**Parameters**|(% style="width:413px" %)(((
968 968  **working_mode** :
969 969  
... ... @@ -979,18 +979,6 @@
979 979  
980 980  6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5
981 981  )))
982 -|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=?
983 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
984 -Current working mode
985 -
986 -OK
987 -)))
988 -|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode>
989 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
990 -Attention:Take effect after ATZ
991 -
992 -OK
993 -)))
994 994  |(% style="width:97px" %)**Example**|(% style="width:413px" %)(((
995 995  AT+MOD=2
996 996  
... ... @@ -1013,10 +1013,8 @@
1013 1013  Sets the device to working mode 2 (Double DI Counting + DO + RO)
1014 1014  )))
1015 1015  
970 +==== 3.4.2.3 Poll an uplink ====
1016 1016  
1017 -==== 3.4.2.3 Request an uplink from the device ====
1018 -
1019 -
1020 1020  Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.
1021 1021  
1022 1022  (% style="color:#037691" %)**AT command**
... ... @@ -1034,10 +1034,8 @@
1034 1034  Requests an uplink from LT-22222-L.
1035 1035  )))
1036 1036  
1037 -
1038 1038  ==== 3.4.2.4 Enable/Disable Trigger Mode ====
1039 1039  
1040 -
1041 1041  Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
1042 1042  
1043 1043  (% style="color:#037691" %)**AT Command**
... ... @@ -1073,12 +1073,10 @@
1073 1073  Enable trigger mode for the current working mode
1074 1074  )))
1075 1075  
1026 +==== 3.4.2.5 Poll trigger settings ====
1076 1076  
1077 -==== 3.4.2.5 Request trigger settings ====
1028 +Polls the trigger settings.
1078 1078  
1079 -
1080 -Requests the trigger settings.
1081 -
1082 1082  (% style="color:#037691" %)**AT Command:**
1083 1083  
1084 1084  There is no AT Command available for this feature.
... ... @@ -1094,10 +1094,8 @@
1094 1094  Uplinks the trigger settings.
1095 1095  )))
1096 1096  
1097 -
1098 1098  ==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ====
1099 1099  
1100 -
1101 1101  Enable or disable DI1/DI2/DI3 as a trigger.
1102 1102  
1103 1103  (% style="color:#037691" %)**AT Command**
... ... @@ -1150,12 +1150,11 @@
1150 1150  Enable DI1 trigger, disable DI2 trigger
1151 1151  )))
1152 1152  
1153 -
1154 1154  ==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ====
1155 1155  
1156 -
1157 1157  Sets DI1 or DI3 (for LT-33222-L) as a trigger.
1158 1158  
1103 +
1159 1159  (% style="color:#037691" %)**AT Command**
1160 1160  
1161 1161  (% border="2" style="width:500px" %)
... ... @@ -1190,12 +1190,11 @@
1190 1190  Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms.
1191 1191  )))
1192 1192  
1193 -
1194 1194  ==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
1195 1195  
1196 -
1197 1197  Sets DI2 as a trigger.
1198 1198  
1142 +
1199 1199  (% style="color:#037691" %)**AT Command**
1200 1200  
1201 1201  (% border="2" style="width:500px" %)
... ... @@ -1225,10 +1225,8 @@
1225 1225  )))
1226 1226  |(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64**
1227 1227  
1228 -
1229 1229  ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
1230 1230  
1231 -
1232 1232  Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1233 1233  
1234 1234  (% style="color:#037691" %)**AT Command**
... ... @@ -1276,10 +1276,8 @@
1276 1276  )))
1277 1277  |(% style="width:104px" %)Note|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1278 1278  
1279 -
1280 1280  ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
1281 1281  
1282 -
1283 1283  Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1284 1284  
1285 1285  (% style="color:#037691" %)**AT Command**
... ... @@ -1325,10 +1325,8 @@
1325 1325  )))
1326 1326  |(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1327 1327  
1328 -
1329 1329  ==== 3.4.2.11 Trigger – Set minimum interval ====
1330 1330  
1331 -
1332 1332  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.
1333 1333  
1334 1334  (% style="color:#037691" %)**AT Command**
... ... @@ -1362,10 +1362,8 @@
1362 1362  )))
1363 1363  |(% style="width:112px" %)Note|(% style="width:386px" %)(% style="color:red" %)**The time must be greater than 5 minutes.**
1364 1364  
1365 -
1366 1366  ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
1367 1367  
1368 -
1369 1369  Controls the digital outputs DO1, DO2, and DO3
1370 1370  
1371 1371  (% style="color:#037691" %)**AT Command**
... ... @@ -1396,11 +1396,11 @@
1396 1396  (((
1397 1397  01: Low,  00: High,  11: No action
1398 1398  
1399 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:383px" %)
1400 -|(% 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**
1401 -|(% style="width:126px" %)02  01  00  11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action
1402 -|(% style="width:126px" %)02  00  11  01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low
1403 -|(% style="width:126px" %)02  11  01  00|(% style="width:85px" %)No Action|(% style="width:86px" %)Low|(% style="width:86px" %)High
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
1404 1404  )))
1405 1405  
1406 1406  (((
... ... @@ -1414,29 +1414,30 @@
1414 1414  )))
1415 1415  )))
1416 1416  
1417 -
1418 1418  ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
1419 1419  
1420 1420  
1421 1421  * (% style="color:#037691" %)**AT Command**
1422 1422  
1423 -There is no AT command to control the digital output.
1358 +There is no AT Command to control Digital Output
1424 1424  
1425 1425  
1426 1426  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
1427 1427  
1428 -(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control
1363 +(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Set DO1/DO2/DO3 output with time control
1429 1429  
1365 +
1430 1430  This is to control the digital output time of DO pin. Include four bytes:
1431 1431  
1432 -(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)
1368 +(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
1433 1433  
1434 -(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode
1370 +(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode
1435 1435  
1436 -**01:** DO pins revert to their original state after the timeout.
1437 -**00:** DO pins switch to an inverted state after the timeout.
1372 +01: DO pins will change back to original state after timeout.
1438 1438  
1374 +00: DO pins will change to an inverter state after timeout 
1439 1439  
1376 +
1440 1440  (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
1441 1441  
1442 1442  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
... ... @@ -1445,7 +1445,7 @@
1445 1445  |0x00|DO1 set to high
1446 1446  |0x11|DO1 NO Action
1447 1447  
1448 -(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:
1385 +(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:
1449 1449  
1450 1450  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1451 1451  |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
... ... @@ -1453,7 +1453,7 @@
1453 1453  |0x00|DO2 set to high
1454 1454  |0x11|DO2 NO Action
1455 1455  
1456 -(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:
1393 +(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:
1457 1457  
1458 1458  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1459 1459  |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
... ... @@ -1461,7 +1461,7 @@
1461 1461  |0x00|DO3 set to high
1462 1462  |0x11|DO3 NO Action
1463 1463  
1464 -(% 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)
1465 1465  
1466 1466  
1467 1467  (% style="color:red" %)**Note: **
... ... @@ -1470,7 +1470,7 @@
1470 1470  
1471 1471   Before firmware v1.6.0, the latch time only supported 2 bytes.
1472 1472  
1473 -(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1410 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1474 1474  
1475 1475  
1476 1476  **Example payload:**
... ... @@ -1497,16 +1497,16 @@
1497 1497  
1498 1498  * (% style="color:#037691" %)**AT Command:**
1499 1499  
1500 -There is no AT Command to control the Relay Output
1437 +There is no AT Command to control Relay Output
1501 1501  
1502 1502  
1503 1503  * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
1504 1504  
1505 -(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Sets RO1/RO2 output
1442 +(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Set RO1/RO2 output
1506 1506  
1507 1507  
1508 1508  (((
1509 -If the payload 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.
1510 1510  )))
1511 1511  
1512 1512  (((
... ... @@ -1524,29 +1524,28 @@
1524 1524  |03  00  01|Open|Close
1525 1525  )))
1526 1526  
1527 -(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1464 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
1528 1528  
1529 1529  
1530 1530  ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
1531 1531  
1532 -
1533 1533  Controls the relay output time.
1534 1534  
1535 1535  * (% style="color:#037691" %)**AT Command:**
1536 1536  
1537 -There is no AT Command to control the Relay Output
1473 +There is no AT Command to control Relay Output
1538 1538  
1539 1539  
1540 1540  * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1541 1541  
1542 -(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
1478 +(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Set RO1/RO2 relay with time control
1543 1543  
1544 1544  
1545 -This controls the relay output time and includes 4 bytes:
1481 +This is to control the relay output time. It includes four bytes:
1546 1546  
1547 -(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)
1483 +(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
1548 1548  
1549 -(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode
1485 +(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
1550 1550  
1551 1551  01: Relays will change back to their original state after timeout.
1552 1552  
... ... @@ -1553,12 +1553,12 @@
1553 1553  00: Relays will change to the inverter state after timeout.
1554 1554  
1555 1555  
1556 -(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status:
1492 +(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
1557 1557  
1558 1558  [[image:image-20221008095908-1.png||height="364" width="564"]]
1559 1559  
1560 1560  
1561 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes (cc)**(%%): Latching time. Unit: ms
1497 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms
1562 1562  
1563 1563  
1564 1564  (% style="color:red" %)**Note:**
... ... @@ -1568,7 +1568,7 @@
1568 1568   Before firmware v1.6.0, the latch time only supported 2 bytes.
1569 1569  
1570 1570  
1571 -(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1507 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1572 1572  
1573 1573  
1574 1574  **Example payload:**
... ... @@ -1727,10 +1727,8 @@
1727 1727  )))
1728 1728  |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
1729 1729  
1666 +==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1730 1730  
1731 -==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ====
1732 -
1733 -
1734 1734  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.
1735 1735  
1736 1736  (% style="color:#037691" %)**AT Command**
... ... @@ -1760,10 +1760,8 @@
1760 1760  Sets the device to save its counting results to the memory every 60 seconds.
1761 1761  )))
1762 1762  
1697 +==== 3.4.2.20 Reset save RO DO state ====
1763 1763  
1764 -==== 3.4.2.20 Reset saved RO and DO states ====
1765 -
1766 -
1767 1767  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.
1768 1768  
1769 1769  (% style="color:#037691" %)**AT Command**
... ... @@ -1788,6 +1788,7 @@
1788 1788  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.
1789 1789  )))
1790 1790  
1723 +
1791 1791  (% style="color:#037691" %)**Downlink Payload**
1792 1792  
1793 1793  (% border="2" style="width:500px" %)
... ... @@ -1811,10 +1811,8 @@
1811 1811  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.
1812 1812  )))
1813 1813  
1814 -
1815 1815  ==== 3.4.2.21 Encrypted payload ====
1816 1816  
1817 -
1818 1818  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.
1819 1819  
1820 1820  (% style="color:#037691" %)**AT Command:**
... ... @@ -1844,7 +1844,6 @@
1844 1844  
1845 1845  ==== 3.4.2.22 Get sensor value ====
1846 1846  
1847 -
1848 1848  This command allows you to retrieve and optionally uplink sensor readings through the serial port.
1849 1849  
1850 1850  (% style="color:#037691" %)**AT Command**
... ... @@ -1874,7 +1874,6 @@
1874 1874  
1875 1875  ==== 3.4.2.23 Resetting the downlink packet count ====
1876 1876  
1877 -
1878 1878  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.
1879 1879  
1880 1880  (% style="color:#037691" %)**AT Command**
... ... @@ -1951,36 +1951,45 @@
1951 1951  Set DISMACANS=1
1952 1952  )))
1953 1953  
1954 -
1955 1955  ==== 3.4.2.25 Copy downlink to uplink ====
1956 1956  
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.
1957 1957  
1958 -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 +* (% style="color:#037691" %)**AT Command**(%%)**:**
1959 1959  
1960 -(% style="color:#037691" %)**AT Command**(%%)**:**
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.
1961 1961  
1962 -(% 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 +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.
1963 1963  
1964 -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.
1965 1965  
1966 -
1967 1967  [[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"]]
1968 1968  
1969 1969  For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
1970 1970  
1971 -[[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
1972 1972  
1973 -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:
1974 1974  
1907 +01 00 02 58
1975 1975  
1976 -(% style="color:#037691" %)**Downlink Payload**(%%)**:**
1909 +Uplink:
1977 1977  
1978 -There is no downlink option available for this feature.
1911 +01 01 00 02 58
1912 +)))
1979 1979  
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"]]
1980 1980  
1981 -==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
1916 +For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
1982 1982  
1983 1983  
1919 +
1920 +==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
1921 +
1984 1984  This command is used to query key information about the device, including its firmware version, frequency band, sub band, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device.
1985 1985  
1986 1986  * (((
... ... @@ -1999,13 +1999,10 @@
1999 1999  
2000 2000  == 3.5 Integrating with ThingsEye.io ==
2001 2001  
2002 -
2003 2003  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.
2004 2004  
2005 -
2006 2006  === 3.5.1 Configuring The Things Stack ===
2007 2007  
2008 -
2009 2009  We use The Things Stack Sandbox in this example:
2010 2010  
2011 2011  * In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
... ... @@ -2017,12 +2017,10 @@
2017 2017  The username and  password (API key) you created here are required in the next section.
2018 2018  {{/info}}
2019 2019  
2020 -[[image:tts-mqtt-integration.png]]
1955 +[[image:tts-mqtt-integration.png||height="625" width="1000"]]
2021 2021  
2022 -
2023 2023  === 3.5.2 Configuring ThingsEye.io ===
2024 2024  
2025 -
2026 2026  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.
2027 2027  
2028 2028  * Login to your [[ThingsEye.io >>https://thingseye.io]]account.
... ... @@ -2029,7 +2029,7 @@
2029 2029  * Under the **Integrations center**, click **Integrations**.
2030 2030  * Click the **Add integration** button (the button with the **+** symbol).
2031 2031  
2032 -[[image:thingseye-io-step-1.png]]
1965 +[[image:thingseye-io-step-1.png||height="625" width="1000"]]
2033 2033  
2034 2034  
2035 2035  On the **Add integration** window, configure the following:
... ... @@ -2044,7 +2044,7 @@
2044 2044  ** Allow create devices or assets
2045 2045  * Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
2046 2046  
2047 -[[image:thingseye-io-step-2.png]]
1980 +[[image:thingseye-io-step-2.png||height="625" width="1000"]]
2048 2048  
2049 2049  
2050 2050  **Uplink data converter:**
... ... @@ -2055,7 +2055,7 @@
2055 2055  * 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]].
2056 2056  * Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
2057 2057  
2058 -[[image:thingseye-io-step-3.png]]
1991 +[[image:thingseye-io-step-3.png||height="625" width="1000"]]
2059 2059  
2060 2060  
2061 2061  **Downlink data converter (this is an optional step):**
... ... @@ -2066,7 +2066,7 @@
2066 2066  * 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]].
2067 2067  * Click the **Next** button. You will be navigated to the **Connection** tab.
2068 2068  
2069 -[[image:thingseye-io-step-4.png]]
2002 +[[image:thingseye-io-step-4.png||height="625" width="1000"]]
2070 2070  
2071 2071  
2072 2072  **Connection:**
... ... @@ -2081,21 +2081,20 @@
2081 2081  
2082 2082  * Click the **Add** button.
2083 2083  
2084 -[[image:thingseye-io-step-5.png]]
2017 +[[image:thingseye-io-step-5.png||height="625" width="1000"]]
2085 2085  
2086 2086  
2087 2087  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.
2088 2088  
2089 2089  
2090 -[[image:thingseye.io_integrationsCenter_integrations.png]]
2023 +[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
2091 2091  
2092 2092  
2093 2093  ==== 3.5.2.1 Viewing integration details ====
2094 2094  
2095 -
2096 2096  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.
2097 2097  
2098 -[[image:integration-details.png]]
2030 +[[image:integration-details.png||height="686" width="1000"]]
2099 2099  
2100 2100  
2101 2101  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.
... ... @@ -2104,32 +2104,28 @@
2104 2104  See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
2105 2105  {{/info}}
2106 2106  
2039 +==== **3.5.2.2 Viewing events** ====
2107 2107  
2108 -==== 3.5.2.2 Viewing events ====
2109 -
2110 -
2111 2111  The **Events **tab displays all the uplink messages from the LT-22222-L.
2112 2112  
2113 2113  * Select **Debug **from the **Event type** dropdown.
2114 2114  * Select the** time frame** from the **time window**.
2115 2115  
2116 -[[image:thingseye-events.png]]
2046 +[[image:thingseye-events.png||height="686" width="1000"]]
2117 2117  
2118 2118  
2119 2119  * To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
2120 2120  
2121 -[[image:thingseye-json.png]]
2051 +[[image:thingseye-json.png||width="1000"]]
2122 2122  
2123 2123  
2124 -==== 3.5.2.3 Deleting an integration ====
2054 +==== **3.5.2.3 Deleting an integration** ====
2125 2125  
2126 -
2127 2127  If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
2128 2128  
2129 2129  
2130 2130  ==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
2131 2131  
2132 -
2133 2133  This will be added soon.
2134 2134  
2135 2135  
... ... @@ -2138,7 +2138,7 @@
2138 2138  === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
2139 2139  
2140 2140  
2141 -Supports** NPN-type **sensors.
2069 +Supports NPN-type sensors.
2142 2142  
2143 2143  [[image:1653356991268-289.png]]
2144 2144  
... ... @@ -2260,15 +2260,15 @@
2260 2260  )))
2261 2261  
2262 2262  
2263 -(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor
2191 +(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
2264 2264  
2265 -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.
2266 2266  
2267 -To detect a Dry Contact, you can supply a power source to one of the pins of the Dry Contact. A reference circuit diagram is 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.
2268 2268  
2269 2269  [[image:image-20230616235145-1.png]]
2270 2270  
2271 -(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector
2199 +(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
2272 2272  
2273 2273  [[image:image-20240219115718-1.png]]
2274 2274  
... ... @@ -2344,9 +2344,8 @@
2344 2344  [[image:image-20220524100215-10.png||height="382" width="723"]]
2345 2345  
2346 2346  
2347 -== 3.7 LED Indicators ==
2275 +== 3.7 LEDs Indicators ==
2348 2348  
2349 -
2350 2350  The table below lists the behavior of LED indicators for each port function.
2351 2351  
2352 2352  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
... ... @@ -2377,25 +2377,20 @@
2377 2377  |**RO1**|For LT-22222-L: ON when RO1 is closed, OFF when RO1 is open
2378 2378  |**RO2**|For LT-22222-L: ON when RO2 is closed, OFF when RO2 is open
2379 2379  
2380 -
2381 2381  = 4. Using AT Commands =
2382 2382  
2383 -
2384 2384  The LT-22222-L supports programming using AT Commands.
2385 2385  
2386 -
2387 2387  == 4.1 Connecting the LT-22222-L to a PC ==
2388 2388  
2389 -
2390 2390  (((
2391 -You can use a USB-to-TTL adapter/converter along 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.
2392 2392  
2393 -[[image:usb-ttl-audio-jack-connection.jpg]]
2394 -
2395 -
2316 +[[image:usb-ttl-programming.png]]
2396 2396  )))
2397 2397  
2398 2398  
2320 +
2399 2399  (((
2400 2400  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:
2401 2401  )))
... ... @@ -2406,10 +2406,7 @@
2406 2406  (((
2407 2407  You can find more details in the [[AT Command Manual>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
2408 2408  
2409 -
2410 2410  == 4.2 LT-22222-L related AT commands ==
2411 -
2412 -
2413 2413  )))
2414 2414  
2415 2415  (((
... ... @@ -2428,39 +2428,39 @@
2428 2428  * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
2429 2429  * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
2430 2430  * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
2431 -* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2432 -* **##AT+DR##**:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
2433 -* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2434 -* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)
2435 -* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency
2436 -* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2437 -* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2438 -* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2439 -* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2440 -* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2441 -* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2442 -* ##**AT+NWKID**##: Get or set the Network ID
2443 -* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)
2444 -* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)
2445 -* ##**AT+CLASS**##: Get or set the Device Class
2446 -* ##**AT+JOIN**##: Join network
2447 -* ##**AT+NJS**##: Get OTAA Join Status
2448 -* ##**AT+SENDB**##: Send hexadecimal data along with the application port
2449 -* ##**AT+SEND**##: Send text data along with the application port
2450 -* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)
2451 -* ##**AT+RECV**##: Print last received data in raw format
2452 -* ##**AT+VER**##: Get current image version and Frequency Band
2453 -* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)
2454 -* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)
2455 -* ##**AT+SNR**##: Get the SNR of the last received packet
2456 -* ##**AT+RSSI**##: Get the RSSI of the last received packet
2457 -* ##**AT+TDC**##: Get or set the application data transmission interval in ms
2458 -* ##**AT+PORT**##: Get or set the application port
2459 -* ##**AT+DISAT**##: Disable AT commands
2460 -* ##**AT+PWORD**##: Set password, max 9 digits
2461 -* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2462 -* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN470
2463 -* ##**AT+CFG**##: Print all settings
2350 +* 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
2464 2464  )))
2465 2465  
2466 2466  
... ... @@ -2606,19 +2606,16 @@
2606 2606  
2607 2607  == 5.1 Counting how many objects pass through the flow line ==
2608 2608  
2609 -
2610 2610  See [[How to set up to setup counting for objects passing through the flow line>>How to set up to count objects pass in flow line]]?
2611 2611  
2612 2612  
2613 2613  = 6. FAQ =
2614 2614  
2615 -
2616 2616  This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
2617 2617  
2618 2618  
2619 2619  == 6.1 How to update the firmware? ==
2620 2620  
2621 -
2622 2622  Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to:
2623 2623  
2624 2624  * Support new features
... ... @@ -2628,7 +2628,7 @@
2628 2628  You will need the following things before proceeding:
2629 2629  
2630 2630  * 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
2631 -* USB to TTL adapter/converter
2547 +* USB to TTL adapter
2632 2632  * 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)
2633 2633  * 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.
2634 2634  
... ... @@ -2638,7 +2638,7 @@
2638 2638  
2639 2639  Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2640 2640  
2641 -[[image:usb-ttl-audio-jack-connection.jpg]]
2557 +[[image:usb-ttl-programming.png]]
2642 2642  
2643 2643  
2644 2644  
... ... @@ -2671,8 +2671,6 @@
2671 2671  (((
2672 2672  (((
2673 2673  == 6.2 How to change the LoRaWAN frequency band/region? ==
2674 -
2675 -
2676 2676  )))
2677 2677  )))
2678 2678  
... ... @@ -2684,8 +2684,6 @@
2684 2684  
2685 2685  
2686 2686  == 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
2687 -
2688 -
2689 2689  )))
2690 2690  
2691 2691  (((
... ... @@ -2759,13 +2759,11 @@
2759 2759  
2760 2760  == 6.4 How to change the uplink interval? ==
2761 2761  
2762 -
2763 2763  Please see this link: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/]]
2764 2764  
2765 2765  
2766 2766  == 6.5 Can I see the counting event in the serial output? ==
2767 2767  
2768 -
2769 2769  (((
2770 2770  You can run the AT command **AT+DEBUG** to view the counting event in the serial output. If the firmware is too old and doesn’t support AT+DEBUG, update to the latest firmware first.
2771 2771  
... ... @@ -2772,7 +2772,6 @@
2772 2772  
2773 2773  == 6.6 Can I use point-to-point communication with LT-22222-L? ==
2774 2774  
2775 -
2776 2776  Yes, you can. Please refer to the [[Point-to-Point Communication of LT-22222-L>>https://wiki.dragino.com/xwiki/bin/view/Main/%20Point%20to%20Point%20Communication%20of%20LT-22222-L/]] page. The firmware that supports point-to-point communication can be found [[here>>https://github.com/dragino/LT-22222-L/releases]].
2777 2777  
2778 2778  
... ... @@ -2781,16 +2781,13 @@
2781 2781  (((
2782 2782  == 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
2783 2783  
2784 -
2785 2785  * If the device is not properly shut down and is directly powered off.
2786 2786  * It will default to a power-off state.
2787 2787  * In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
2788 2788  * After a restart, the status before the power failure will be read from flash.
2789 2789  
2790 -
2791 2791  == 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
2792 2792  
2793 -
2794 2794  The LT-22222-L's built-in relay is Normally Open (NO). You can use an external relay to achieve a Normally Closed (NC) configuration. The circuit diagram is shown below:
2795 2795  
2796 2796  
... ... @@ -2799,19 +2799,16 @@
2799 2799  
2800 2800  == 6.9 Can the LT-22222-L save the RO state? ==
2801 2801  
2802 -
2803 2803  To enable this feature, the firmware version must be 1.6.0 or higher.
2804 2804  
2805 2805  
2806 2806  == 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
2807 2807  
2808 -
2809 2809  It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
2810 2810  
2811 2811  
2812 2812  = 7. Troubleshooting =
2813 2813  
2814 -
2815 2815  This section provides some known troubleshooting tips.
2816 2816  
2817 2817  
... ... @@ -2820,8 +2820,6 @@
2820 2820  (((
2821 2821  (((
2822 2822  == 7.1 Downlink isn't working. How can I solve this? ==
2823 -
2824 -
2825 2825  )))
2826 2826  )))
2827 2827  
... ... @@ -2833,8 +2833,6 @@
2833 2833  
2834 2834  
2835 2835  == 7.2 Having trouble uploading an image? ==
2836 -
2837 -
2838 2838  )))
2839 2839  
2840 2840  (((
... ... @@ -2845,8 +2845,6 @@
2845 2845  
2846 2846  
2847 2847  == 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
2848 -
2849 -
2850 2850  )))
2851 2851  
2852 2852  (((
... ... @@ -2856,7 +2856,6 @@
2856 2856  
2857 2857  == 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? ==
2858 2858  
2859 -
2860 2860  The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
2861 2861  Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2862 2862  
... ... @@ -2863,7 +2863,6 @@
2863 2863  
2864 2864  = 8. Ordering information =
2865 2865  
2866 -
2867 2867  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
2868 2868  
2869 2869  (% style="color:#4f81bd" %)**XXX:**
... ... @@ -2878,11 +2878,8 @@
2878 2878  * (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865
2879 2879  * (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779
2880 2880  
2881 -
2882 -
2883 2883  = 9. Package information =
2884 2884  
2885 -
2886 2886  **Package includes**:
2887 2887  
2888 2888  * 1 x LT-22222-L I/O Controller
... ... @@ -2897,11 +2897,8 @@
2897 2897  * Package Size / pcs : 14.5 x 8 x 5 cm
2898 2898  * Weight / pcs : 170 g
2899 2899  
2900 -
2901 -
2902 2902  = 10. Support =
2903 2903  
2904 -
2905 2905  * (((
2906 2906  Support is available Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different time zones, we cannot offer live support. However, your questions will be answered as soon as possible within the aforementioned schedule.
2907 2907  )))
... ... @@ -2913,7 +2913,6 @@
2913 2913  
2914 2914  = 11. Reference​​​​​ =
2915 2915  
2916 -
2917 2917  * LT-22222-L: [[http:~~/~~/www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html>>url:http://www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html]]
2918 2918  * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]]
2919 2919  * [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]
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