Skip to Content
Last modified by Mengting Qiu on 2025/06/04 18:42
From version 214.1
edited by Dilisi S
on 2024/11/24 01:55
Change comment: add example dl screenshot
To version 233.1
edited by Dilisi S
on 2024/12/17 04:56
Change comment: Uploaded new attachment "lt-22222-l-dashboard.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -21,6 +21,7 @@
21 21  
22 22  == 1.1 What is the LT-22222-L I/O Controller? ==
23 23  
24 +
24 24  (((
25 25  (((
26 26  {{info}}
... ... @@ -54,8 +54,10 @@
54 54  (% class="wikigeneratedid" %)
55 55  [[image:lorawan-nw.jpg||height="354" width="900"]]
56 56  
58 +
57 57  == 1.2 Specifications ==
58 58  
61 +
59 59  (% style="color:#037691" %)**Hardware System:**
60 60  
61 61  * STM32L072xxxx MCU
... ... @@ -97,6 +97,7 @@
97 97  
98 98  == 1.3 Features ==
99 99  
103 +
100 100  * LoRaWAN Class A & Class C modes
101 101  * Optional Customized LoRa Protocol
102 102  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
... ... @@ -107,6 +107,7 @@
107 107  
108 108  == 1.4 Applications ==
109 109  
114 +
110 110  * Smart buildings & home automation
111 111  * Logistics and supply chain management
112 112  * Smart metering
... ... @@ -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" %)(((
124 +
125 +(% border="1" cellspacing="3" style="width:510px" %)
126 +|(% style="background-color:#4f81bd; color:white; width:94px" %)**Model**|(% style="background-color:#4f81bd; color:white; width:172px" %)**Photo**|(% style="background-color:#4f81bd; color:white; width:244px" %)**Description**
127 +|(% style="width:94px" %)**LT-22222-L**|(% style="width:172px" %)(((
128 +(% style="text-align:center" %)
129 +[[image:lt33222-l.jpg||height="110" width="95"]]
130 +)))|(% 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)
... ... @@ -133,6 +133,7 @@
133 133  
134 134  == 2.1 Connecting the antenna ==
135 135  
143 +
136 136  Connect the LoRa antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper screw terminal block. Secure the antenna by tightening it clockwise.
137 137  
138 138  {{warning}}
... ... @@ -139,42 +139,45 @@
139 139  **Warning! Do not power on the device without connecting the antenna.**
140 140  {{/warning}}
141 141  
150 +
142 142  == 2.2 Terminals ==
143 143  
153 +
144 144  The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals.
145 145  
146 146  **Upper screw terminal block (from left to right):**
147 147  
148 -(% style="width:634px" %)
149 -|=(% style="width: 295px;" %)Screw Terminal|=(% style="width: 338px;" %)Function
150 -|(% style="width:295px" %)GND|(% style="width:338px" %)Ground
151 -|(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage
152 -|(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2
153 -|(% style="width:295px" %)AVI1|(% style="width:338px" %)Analog Voltage Input Terminal 1
154 -|(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2
155 -|(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1
158 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:381px" %)
159 +|=(% style="width: 139px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 242px;background-color:#4f81bd;color:white" %)Function
160 +|(% style="width:139px" %)GND|(% style="width:242px" %)Ground
161 +|(% style="width:139px" %)VIN|(% style="width:242px" %)Input Voltage
162 +|(% style="width:139px" %)AVI2|(% style="width:242px" %)Analog Voltage Input Terminal 2
163 +|(% style="width:139px" %)AVI1|(% style="width:242px" %)Analog Voltage Input Terminal 1
164 +|(% style="width:139px" %)ACI2|(% style="width:242px" %)Analog Current Input Terminal 2
165 +|(% style="width:139px" %)ACI1|(% style="width:242px" %)Analog Current Input Terminal 1
156 156  
157 157  **Lower screw terminal block (from left to right):**
158 158  
159 -(% style="width:633px" %)
160 -|=(% style="width: 296px;" %)Screw Terminal|=(% style="width: 334px;" %)Function
161 -|(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1
162 -|(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1
163 -|(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2
164 -|(% style="width:296px" %)RO2-1|(% style="width:334px" %)Relay Output 2
165 -|(% style="width:296px" %)DI2+|(% style="width:334px" %)Digital Input 2
166 -|(% style="width:296px" %)DI2-|(% style="width:334px" %)Digital Input 2
167 -|(% style="width:296px" %)DI1+|(% style="width:334px" %)Digital Input 1
168 -|(% style="width:296px" %)DI1-|(% style="width:334px" %)Digital Input 1
169 -|(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
170 -|(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
169 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:253px" %)
170 +|=(% style="width: 125px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 128px;background-color:#4f81bd;color:white" %)Function
171 +|(% style="width:125px" %)RO1-2|(% style="width:128px" %)Relay Output 1
172 +|(% style="width:125px" %)RO1-1|(% style="width:128px" %)Relay Output 1
173 +|(% style="width:125px" %)RO2-2|(% style="width:128px" %)Relay Output 2
174 +|(% style="width:125px" %)RO2-1|(% style="width:128px" %)Relay Output 2
175 +|(% style="width:125px" %)DI2+|(% style="width:128px" %)Digital Input 2
176 +|(% style="width:125px" %)DI2-|(% style="width:128px" %)Digital Input 2
177 +|(% style="width:125px" %)DI1+|(% style="width:128px" %)Digital Input 1
178 +|(% style="width:125px" %)DI1-|(% style="width:128px" %)Digital Input 1
179 +|(% style="width:125px" %)DO2|(% style="width:128px" %)Digital Output 2
180 +|(% style="width:125px" %)DO1|(% style="width:128px" %)Digital Output 1
171 171  
172 172  == 2.3 Connecting LT-22222-L to a Power Source ==
173 173  
184 +
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.**
188 +**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  
... ... @@ -183,23 +183,27 @@
183 183  
184 184  = 3. Registering LT-22222-L with a LoRaWAN Network Server =
185 185  
197 +
186 186  The LT-22222-L supports both OTAA (Over-the-Air Activation) and ABP (Activation By Personalization) methods to activate with a LoRaWAN Network Server. However, OTAA is the most secure method for activating a device with a LoRaWAN Network Server. OTAA regenerates session keys upon initial registration and regenerates new session keys after any subsequent reboots. By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode.
187 187  
188 188  
189 -=== 3.2.1 Prerequisites ===
201 +== 3.1 Prerequisites ==
190 190  
203 +
191 191  The LT-22222-L comes with device registration information such as DevEUI, AppEUI, and AppKey that allows you to register it with a LoRaWAN network. These registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference.
192 192  
193 193  [[image:image-20230425173427-2.png||height="246" width="530"]]
194 194  
195 195  {{info}}
196 -In case you can't set the root key and other identifiers in the network server and must use them from the server, you can use [[AT Commands>>||anchor="H4.UseATCommand"]] to configure them on the device.
209 +If you are unable to set the provided root key and other identifiers in the network server, you must generate new keys and identifiers with the network server and configure the device with them using AT commands.
197 197  {{/info}}
198 198  
199 199  The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
200 200  
201 -=== 3.2.2 The Things Stack ===
202 202  
215 +== 3.2 The Things Stack ==
216 +
217 +
203 203  This section guides you through how to register your LT-22222-L with The Things Stack Sandbox.
204 204  
205 205  {{info}}
... ... @@ -210,7 +210,7 @@
210 210  The network diagram below illustrates the connection between the LT-22222-L and The Things Stack, as well as how the data can be integrated with the ThingsEye IoT platform.
211 211  
212 212  
213 -[[image:dragino-lorawan-nw-lt-22222-n.jpg]]
228 +[[image:dragino-lorawan-nw-lt-22222-n.jpg||height="374" width="1400"]]
214 214  
215 215  {{info}}
216 216   You can use a LoRaWAN gateway, such as the [[Dragino LPS8N>>https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]], to expand or create LoRaWAN coverage in your area.
... ... @@ -217,8 +217,9 @@
217 217  {{/info}}
218 218  
219 219  
220 -==== 3.2.2.1 Setting up ====
235 +=== 3.2.1 Setting up ===
221 221  
237 +
222 222  * Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet.
223 223  * Log in to your The Things Stack Sandbox account.
224 224  * Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs).
... ... @@ -225,8 +225,10 @@
225 225  * Go to your application's page and click on the **End devices** in the left menu.
226 226  * On the End devices page, click on **+ Register end device**. Two registration options are available:
227 227  
228 -==== 3.2.2.2 Using the LoRaWAN Device Repository ====
229 229  
245 +==== 3.2.1.1 Using the LoRaWAN Device Repository ====
246 +
247 +
230 230  * On the **Register end device** page:
231 231  ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
232 232  ** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists.
... ... @@ -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"]]
258 +[[image:lt-22222-l-dev-repo-reg-p1.png]]
241 241  
242 242  
243 243  * Register end device page continued...
... ... @@ -247,11 +247,12 @@
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"]]
268 +[[image:lt-22222-l-dev-repo-reg-p2.png]]
251 251  
252 252  
253 -==== 3.2.2.3 Adding device manually ====
271 +==== 3.2.1.2 Adding device manually ====
254 254  
273 +
255 255  * On the **Register end device** page:
256 256  ** Select the option **Enter end device specifies manually** under **Input method**.
257 257  ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
... ... @@ -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"]]
283 +[[image:lt-22222-l-manually-p1.png]]
265 265  
266 266  
267 267  * Register end device page continued...
... ... @@ -272,26 +272,27 @@
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"]]
294 +[[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"]]
300 +[[image:lt-22222-device-overview.png]]
282 282  
283 283  
284 -==== 3.2.2.4 Joining ====
303 +=== 3.2.2 Joining ===
285 285  
305 +
286 286  On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
287 287  
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"]]
311 +[[image:lt-22222-l-joining.png]]
292 292  
293 293  
294 -==== 3.2.2.5 Uplinks ====
314 +=== 3.2.3 Uplinks ===
295 295  
296 296  
297 297  After successfully joining, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**). When the LT-22222-L sends an uplink message to the server, the **TX LED** turns on for **1 second**. By default, you will receive an uplink data message from the device every 10 minutes.
... ... @@ -307,11 +307,18 @@
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"]]
330 +[[image:lt-22222-ul-payload-fmt.png]]
311 311  
312 312  
313 -==== 3.2.2.6 Downlinks ====
333 +We also have a payload formatter that resolves some decoding issues present in the Device Repository formatter. You can add it under the Custom JavaScript formatter. It can be found [[here>>https://github.com/dragino/dragino-end-node-decoder/blob/main/LT22222-L/v1.6_decoder_ttn%20.txt]]:
314 314  
335 +(% class="wikigeneratedid" %)
336 +[[image:lt-22222-l-js-custom-payload-formatter.png]]
337 +
338 +
339 +=== 3.2.4 Downlinks ===
340 +
341 +
315 315  When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
316 316  
317 317  
... ... @@ -334,8 +334,10 @@
334 334  
335 335  The uplink messages are sent over LoRaWAN FPort=2. By default, an uplink message is sent every 10 minutes.
336 336  
364 +
337 337  === 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
338 338  
367 +
339 339  (((
340 340  This is the default mode.
341 341  
... ... @@ -408,6 +408,7 @@
408 408  
409 409  MOD = 1
410 410  
440 +
411 411  === 3.3.2 AT+MOD~=2, (Double DI Counting) ===
412 412  
413 413  
... ... @@ -486,6 +486,7 @@
486 486  
487 487  === 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI ===
488 488  
519 +
489 489  (% style="color:red" %)**Note: The maximum count depends on the bytes it is.
490 490  The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
491 491  It starts counting again when it reaches the maximum value.**
... ... @@ -539,6 +539,7 @@
539 539  
540 540  === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting ===
541 541  
573 +
542 542  (% style="color:red" %)**Note:The maximum count depends on the bytes it is.
543 543  The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
544 544  It starts counting again when it reaches the maximum value.**
... ... @@ -598,16 +598,17 @@
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)**
633 +(% 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)**
635 +(% 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)**
637 +(% 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  
609 609  === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI ===
610 610  
643 +
611 611  (% style="color:red" %)**Note:The maximum count depends on the bytes it is.
612 612  The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
613 613  It starts counting again when it reaches the maximum value.**
... ... @@ -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**
757 +**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
759 +**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" %)
788 +(% 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" %)
802 +(% 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
826 +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" %)
831 +(% 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.
855 +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
860 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
861 +|(% 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**
862 +|(% 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.
864 +* 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.
868 +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.
870 +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.
873 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled.
841 841  
842 -Downlink command to poll MOD6 status:
875 +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.
879 +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  
893 +
860 860  (((
861 861  You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks.
862 862  )))
... ... @@ -873,17 +873,22 @@
873 873  
874 874  === 3.4.1 Common commands ===
875 875  
910 +
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.
913 +
914 +
878 878  )))
879 879  
880 880  === 3.4.2 Sensor-related commands ===
881 881  
919 +
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  
925 +
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**
932 +|**Parameters**|**time **: uplink interval in milliseconds
933 +|**Get**|AT+TDC=?
934 +|**Response**|(((
935 +current uplink interval
936 +
937 +OK
938 +)))
939 +|**Set**|AT+TDC=<time>
940 +|**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**.
956 +**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  
972 +
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" %)
978 +|(% 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  )))
994 +|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=?
995 +|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
996 +Current working mode
997 +
998 +OK
999 +)))
1000 +|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode>
1001 +|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
1002 +Attention:Take effect after ATZ
1003 +
1004 +OK
1005 +)))
948 948  |(% style="width:97px" %)**Example**|(% style="width:413px" %)(((
949 949  AT+MOD=2
950 950  
... ... @@ -967,13 +967,14 @@
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 ====
1028 +==== 3.4.2.3 Request an uplink from the device ====
971 971  
972 -Requests an uplink from LT-22222-L.
973 973  
1031 +Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.
1032 +
974 974  (% style="color:#037691" %)**AT command**
975 975  
976 -There is no AT Command to request an uplink from LT-22222-L
1035 +There is no AT Command available for this feature.
977 977  
978 978  (% style="color:#037691" %)**Downlink payload**
979 979  
... ... @@ -981,7 +981,7 @@
981 981  |(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF
982 982  |(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08
983 983  |(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
984 -08 FF
1043 +08 **FF**
985 985  
986 986  Requests an uplink from LT-22222-L.
987 987  )))
... ... @@ -988,6 +988,7 @@
988 988  
989 989  ==== 3.4.2.4 Enable/Disable Trigger Mode ====
990 990  
1050 +
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**
... ... @@ -1015,7 +1015,7 @@
1015 1015  |(% style="width:97px" %)**Parameters**|(% style="width:401px" %)(((
1016 1016  **prefix** : 0x0A 06 (two bytes in hexadecimal)
1017 1017  
1018 -**working mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
1078 +**enable/disable trigger_mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
1019 1019  )))
1020 1020  |(% style="width:97px" %)**Example**|(% style="width:401px" %)(((
1021 1021  0A 06 **01**
... ... @@ -1023,13 +1023,14 @@
1023 1023  Enable trigger mode for the current working mode
1024 1024  )))
1025 1025  
1026 -==== 3.4.2.5 Poll trigger settings ====
1086 +==== 3.4.2.5 Request trigger settings ====
1027 1027  
1028 -Polls the trigger settings.
1029 1029  
1089 +Requests the trigger settings.
1090 +
1030 1030  (% style="color:#037691" %)**AT Command:**
1031 1031  
1032 -There is no AT Command for this feature.
1093 +There is no AT Command available for this feature.
1033 1033  
1034 1034  (% style="color:#037691" %)**Downlink Payload**
1035 1035  
... ... @@ -1044,6 +1044,7 @@
1044 1044  
1045 1045  ==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ====
1046 1046  
1108 +
1047 1047  Enable or disable DI1/DI2/DI3 as a trigger.
1048 1048  
1049 1049  (% style="color:#037691" %)**AT Command**
... ... @@ -1098,9 +1098,9 @@
1098 1098  
1099 1099  ==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ====
1100 1100  
1163 +
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" %)
... ... @@ -1137,9 +1137,9 @@
1137 1137  
1138 1138  ==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
1139 1139  
1202 +
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" %)
... ... @@ -1171,6 +1171,7 @@
1171 1171  
1172 1172  ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
1173 1173  
1236 +
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**
... ... @@ -1220,6 +1220,7 @@
1220 1220  
1221 1221  ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
1222 1222  
1286 +
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**
... ... @@ -1267,6 +1267,7 @@
1267 1267  
1268 1268  ==== 3.4.2.11 Trigger – Set minimum interval ====
1269 1269  
1334 +
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**
... ... @@ -1302,6 +1302,7 @@
1302 1302  
1303 1303  ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
1304 1304  
1370 +
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
1401 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:383px" %)
1402 +|(% 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**
1403 +|(% style="width:126px" %)02  01  00  11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action
1404 +|(% style="width:126px" %)02  00  11  01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low
1405 +|(% 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  (((
... ... @@ -1353,80 +1353,81 @@
1353 1353  ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
1354 1354  
1355 1355  
1356 -* (% style="color:#037691" %)**AT Command**
1422 +(% style="color:#037691" %)**AT command**
1357 1357  
1358 -There is no AT Command to control Digital Output
1424 +There is no AT command to control the digital output.
1359 1359  
1360 1360  
1361 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
1427 +(% style="color:#037691" %)**Downlink payload**
1362 1362  
1363 -(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Set DO1/DO2/DO3 output with time control
1364 1364  
1430 +(% border="2" style="width:500px" %)
1431 +|(% style="width:116px" %)**Prefix**|(% style="width:382px" %)0xA9
1432 +|(% style="width:116px" %)**Parameters**|(% style="width:382px" %)(((
1433 +**inverter_mode**: 1 byte in hex.
1365 1365  
1366 -This is to control the digital output time of DO pin. Include four bytes:
1435 +**01:** DO pins revert to their original state after the timeout.
1436 +**00:** DO pins switch to an inverted state after the timeout.
1367 1367  
1368 -(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
1369 1369  
1370 -(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode
1439 +**DO1_control_method_and_port_status **- 1 byte in hex
1371 1371  
1372 -01: DO pins will change back to original state after timeout.
1441 +0x01 : DO1 set to low
1373 1373  
1374 -00: DO pins will change to an inverter state after timeout 
1443 +0x00 : DO1 set to high
1375 1375  
1445 +0x11 : DO1 NO action
1376 1376  
1377 -(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
1378 1378  
1379 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1380 -|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
1381 -|0x01|DO1 set to low
1382 -|0x00|DO1 set to high
1383 -|0x11|DO1 NO Action
1448 +**DO2_control_method_and_port_status** - 1 byte in hex
1384 1384  
1385 -(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:
1450 +0x01 : DO2 set to low
1386 1386  
1387 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1388 -|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
1389 -|0x01|DO2 set to low
1390 -|0x00|DO2 set to high
1391 -|0x11|DO2 NO Action
1452 +0x00 : DO2 set to high
1392 1392  
1393 -(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:
1454 +0x11 : DO2 NO action
1394 1394  
1395 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1396 -|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
1397 -|0x01|DO3 set to low
1398 -|0x00|DO3 set to high
1399 -|0x11|DO3 NO Action
1400 1400  
1401 -(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)
1457 +**DO3_control_method_and_port_status **- 1 byte in hex
1402 1402  
1459 +0x01 : DO3 set to low
1403 1403  
1404 -(% style="color:red" %)**Note: **
1461 +0x00 : DO3 set to high
1405 1405  
1406 - Since firmware v1.6.0, the latch time support 4 bytes and 2 bytes
1463 +0x11 : DO3 NO action
1407 1407  
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.**
1466 +**latching_time** : 4 bytes in hex
1411 1411  
1468 +(% style="color:red" %)**Note: **
1412 1412  
1413 -**Example payload:**
1470 + Since firmware v1.6.0, the latch time support 4 bytes or 2 bytes
1414 1414  
1415 -**~1. A9 01 01 01 01 07 D0**
1472 + Before firmware v1.6.0, the latch time only supported 2 bytes.
1416 1416  
1474 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1475 +)))
1476 +|(% style="width:116px" %)**Payload format**|(% style="width:382px" %)<prefix><inverter_mode><DO1_control_method_and_port_status><DO2_control_method_and_port_status><DO2_control_method_and_port_status><latching_time>
1477 +|(% style="width:116px" %)**Example**|(% style="width:382px" %)(((
1478 +**A9 01 01 01 01 07 D0**
1479 +
1417 1417  DO1 pin, DO2 pin, and DO3 pin will be set to low, last for 2 seconds, and then revert to their original state.
1418 1418  
1419 -**2. A9 01 00 01 11 07 D0**
1420 1420  
1483 +**A9 01 00 01 11 07 D0**
1484 +
1421 1421  DO1 pin is set to high, DO2 pin is set to low, and DO3 pin takes no action. This lasts for 2 seconds and then reverts to the original state.
1422 1422  
1423 -**3. A9 00 00 00 00 07 D0**
1424 1424  
1488 +**A9 00 00 00 00 07 D0**
1489 +
1425 1425  DO1 pin, DO2 pin, and DO3 pin will be set to high, last for 2 seconds, and then all change to low.
1426 1426  
1427 -**4. A9 00 11 01 00 07 D0**
1428 1428  
1493 +**A9 00 11 01 00 07 D0**
1494 +
1429 1429  DO1 pin takes no action, DO2 pin is set to low, and DO3 pin is set to high. This lasts for 2 seconds, after which DO1 pin takes no action, DO2 pin is set to high, and DO3 pin is set to low.
1496 +)))
1430 1430  
1431 1431  
1432 1432  ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
... ... @@ -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
1504 +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
1509 +(% 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.
1513 +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.**
1531 +(% 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  
1536 +
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
1541 +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
1546 +(% 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:
1549 +This controls the relay output time and includes 4 bytes:
1482 1482  
1483 -(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
1551 +(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)
1484 1484  
1485 -(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
1553 +(% 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:
1560 +(% 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
1565 +(% 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.**
1575 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1508 1508  
1509 1509  
1510 1510  **Example payload:**
... ... @@ -1532,17 +1532,10 @@
1532 1532  
1533 1533  When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
1534 1534  
1535 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX   ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
1536 -
1537 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):**
1538 -
1539 -(% style="color:blue" %)**0xA5 aa bb cc   ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc
1540 -
1541 -
1542 1542  (% style="color:#037691" %)**AT Command**
1543 1543  
1544 1544  (% border="2" style="width:500px" %)
1545 -|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage><logic>
1606 +|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage>,<logic>
1546 1546  |(% style="width:137px" %)**Response**|(% style="width:361px" %)
1547 1547  |(% style="width:137px" %)**Parameters**|(% style="width:361px" %)(((
1548 1548  **voltage** : voltage threshold in mV
... ... @@ -1549,9 +1549,9 @@
1549 1549  
1550 1550  **logic**:
1551 1551  
1552 -0 : lower than
1613 +**0** : lower than
1553 1553  
1554 -1: higher than
1615 +**1**: higher than
1555 1555  
1556 1556  if you leave logic parameter blank, it is considered 0
1557 1557  )))
... ... @@ -1580,9 +1580,9 @@
1580 1580  
1581 1581  **logic**: (1 byte in hexadecimal)
1582 1582  
1583 -0 : lower than
1644 +**0** : lower than
1584 1584  
1585 -1: higher than
1646 +**1**: higher than
1586 1586  
1587 1587  if you leave logic parameter blank, it is considered 1 (higher than)
1588 1588  )))
... ... @@ -1604,22 +1604,10 @@
1604 1604  
1605 1605  This command allows users to pre-configure specific count numbers for various counting parameters such as Count1, Count2, or AVI1 Count. Use the AT command to set the desired count number for each configuration.
1606 1606  
1607 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) **
1608 -
1609 -(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count
1610 -
1611 -(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set
1612 -
1613 -
1614 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):**
1615 -
1616 -(% style="color:blue" %)**0x A8 aa bb cc dd ee     ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee)
1617 -
1618 -
1619 1619  (% style="color:#037691" %)**AT Command**
1620 1620  
1621 1621  (% border="2" style="width:500px" %)
1622 -|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter><number>
1671 +|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter>,<number>
1623 1623  |(% style="width:134px" %)**Response**|(% style="width:364px" %)
1624 1624  |(% style="width:134px" %)**Parameters**|(% style="width:364px" %)(((
1625 1625  **counting_parameter** :
... ... @@ -1665,12 +1665,6 @@
1665 1665  
1666 1666  This command clears the counting in counting mode.
1667 1667  
1668 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT         **(%%) ~/~/ clear all counting
1669 -
1670 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):**
1671 -
1672 -(% style="color:blue" %)**0x A6 01    ** (%%)~/~/ clear all counting
1673 -
1674 1674  (% style="color:#037691" %)**AT Command**
1675 1675  
1676 1676  (% border="2" style="width:500px" %)
... ... @@ -1688,24 +1688,11 @@
1688 1688  )))
1689 1689  |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
1690 1690  
1691 -==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1734 +==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ====
1692 1692  
1736 +
1693 1693  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.
1694 1694  
1695 -* (% style="color:#037691" %)**AT Command:**
1696 -
1697 -(% style="color:blue" %)**AT+COUTIME=60  **(%%)~/~/ Sets the save time to 60 seconds. The device will save the counting result in internal flash every 60 seconds. (Min value: 30 seconds)
1698 -
1699 -
1700 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):**
1701 -
1702 -(% style="color:blue" %)**0x A7 aa bb cc     ** (%%)~/~/ same as AT+COUTIME =aa bb cc,
1703 -
1704 -(((
1705 -Range: aa bb cc:0 to 16777215,  (unit: seconds)
1706 -)))
1707 -
1708 -
1709 1709  (% style="color:#037691" %)**AT Command**
1710 1710  
1711 1711  (% border="2" style="width:500px" %)
... ... @@ -1733,22 +1733,13 @@
1733 1733  Sets the device to save its counting results to the memory every 60 seconds.
1734 1734  )))
1735 1735  
1736 -==== 3.4.2.20 Reset save RO DO state ====
1766 +==== 3.4.2.20 Reset saved RO and DO states ====
1737 1737  
1768 +
1738 1738  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.
1739 1739  
1740 -* (% style="color:#037691" %)**AT Command:**
1771 +(% style="color:#037691" %)**AT Command**
1741 1741  
1742 -(% style="color:blue" %)**AT+RODORESET=1    **(%%)~/~/ RODO will close when the device joining the network. (default)
1743 -
1744 -(% style="color:blue" %)**AT+RODORESET=0    **(%%)~/~/ After the device is reset, the previously saved RODO state (only MOD2 to MOD5) is read, and its state will not change when the device reconnects to the network.
1745 -
1746 -
1747 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):**
1748 -
1749 -(% style="color:blue" %)**0x AD aa      ** (%%)~/~/ same as AT+RODORET =aa
1750 -
1751 -
1752 1752  (% border="2" style="width:500px" %)
1753 1753  |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state>
1754 1754  |(% style="width:127px" %)**Response**|(% style="width:371px" %)
... ... @@ -1769,6 +1769,8 @@
1769 1769  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.
1770 1770  )))
1771 1771  
1793 +(% style="color:#037691" %)**Downlink Payload**
1794 +
1772 1772  (% border="2" style="width:500px" %)
1773 1773  |(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state>
1774 1774  |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
... ... @@ -1792,24 +1792,20 @@
1792 1792  
1793 1793  ==== 3.4.2.21 Encrypted payload ====
1794 1794  
1818 +
1795 1795  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.
1796 1796  
1797 -* (% style="color:#037691" %)**AT Command:**
1821 +(% style="color:#037691" %)**AT Command:**
1798 1798  
1799 -(% style="color:blue" %)**AT+DECRYPT=1  ** (%%)~/~/ The payload is uploaded without encryption
1800 -
1801 -(% style="color:blue" %)**AT+DECRYPT=0    **(%%)~/~/  Encrypt when uploading payload (default)
1802 -
1803 -
1804 1804  (% border="2" style="width:500px" %)
1805 1805  |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state>
1806 1806  |(% style="width:127px" %)**Response**|(% style="width:371px" %)
1807 1807  |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1808 -state :
1827 +**state** :
1809 1809  
1810 -1 : The payload is uploaded without encryption
1829 +**1** : The payload is uploaded without encryption
1811 1811  
1812 -0 : The payload is encrypted when uploaded (default)
1831 +**0** : The payload is encrypted when uploaded (default)
1813 1813  )))
1814 1814  |(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1815 1815  AT+DECRYPT=1
... ... @@ -1826,15 +1826,11 @@
1826 1826  
1827 1827  ==== 3.4.2.22 Get sensor value ====
1828 1828  
1848 +
1829 1829  This command allows you to retrieve and optionally uplink sensor readings through the serial port.
1830 1830  
1831 -* (% style="color:#037691" %)**AT Command:**
1851 +(% style="color:#037691" %)**AT Command**
1832 1832  
1833 -(% style="color:blue" %)**AT+GETSENSORVALUE=0    **(%%)~/~/ The serial port retrieves the reading of the current sensor.
1834 -
1835 -(% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it.
1836 -
1837 -
1838 1838  (% border="2" style="width:500px" %)
1839 1839  |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state>
1840 1840  |(% style="width:127px" %)**Response**|(% style="width:371px" %)
... ... @@ -1860,15 +1860,11 @@
1860 1860  
1861 1861  ==== 3.4.2.23 Resetting the downlink packet count ====
1862 1862  
1878 +
1863 1863  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.
1864 1864  
1865 -* (% style="color:#037691" %)**AT Command:**
1881 +(% style="color:#037691" %)**AT Command**
1866 1866  
1867 -(% style="color:blue" %)**AT+DISFCNTCHECK=0   **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node will no longer receive downlink packets (default)
1868 -
1869 -(% style="color:blue" %)**AT+DISFCNTCHECK=1   **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node resets the downlink packet count and keeps it consistent with the server downlink packet count.
1870 -
1871 -
1872 1872  (% border="2" style="width:500px" %)
1873 1873  |(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state>
1874 1874  |(% style="width:130px" %)**Response**|(% style="width:368px" %)(((
... ... @@ -1900,17 +1900,6 @@
1900 1900  
1901 1901  This command controls the behavior of the node when the combined size of the MAC commands (MACANS) from the server and the payload exceeds the allowed byte limit for the current data rate (DR). The command provides two modes: one enables splitting the data into batches to ensure compliance with the byte limit, while the other prioritizes the payload and ignores the MACANS in cases of overflow.
1902 1902  
1903 -* (% style="color:#037691" %)**AT Command:**
1904 -
1905 -(% style="color:blue" %)**AT+DISMACANS=0**   (%%) ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of 11 bytes (DR0 of US915, DR2 of AS923, DR2 of AU195), the node will send a packet with a payload of 00 and a port of 4. (default)
1906 -
1907 -(% style="color:blue" %)**AT+DISMACANS=1**  (%%) ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of the DR, the node will ignore the MACANS and not reply, and only upload the payload part.
1908 -
1909 -
1910 -* (% style="color:#037691" %)**Downlink Payload **(%%)**:**
1911 -
1912 -(% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set  the DISMACANS=1
1913 -
1914 1914  (% style="color:#037691" %)**AT Command**
1915 1915  
1916 1916  (% border="2" style="width:500px" %)
... ... @@ -1954,43 +1954,33 @@
1954 1954  
1955 1955  ==== 3.4.2.25 Copy downlink to uplink ====
1956 1956  
1957 -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.
1958 1958  
1959 -* (% style="color:#037691" %)**AT Command**(%%)**:**
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.
1960 1960  
1961 -(% 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.
1960 +(% style="color:#037691" %)**AT Command**(%%)**:**
1962 1962  
1963 -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.
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.
1964 1964  
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 +
1966 1966  [[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"]]
1967 1967  
1968 1968  For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
1969 1969  
1970 -(% border="2" style="width:500px" %)
1971 -|(% style="width:122px" %)**Command**|(% style="width:376px" %)(((
1972 -AT+RPL=5
1973 -
1974 -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.
1975 -)))
1976 -|(% style="width:122px" %)**Example**|(% style="width:376px" %)(((
1977 -Downlink:
1978 -
1979 -01 00 02 58
1980 -
1981 -Uplink:
1982 -
1983 -01 01 00 02 58
1984 -)))
1985 -
1986 1986  [[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"]]
1987 1987  
1988 1988  For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
1989 1989  
1990 1990  
1976 +(% style="color:#037691" %)**Downlink Payload**(%%)**:**
1991 1991  
1978 +There is no downlink option available for this feature.
1979 +
1980 +
1992 1992  ==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
1993 1993  
1983 +
1994 1994  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.
1995 1995  
1996 1996  * (((
... ... @@ -2009,10 +2009,13 @@
2009 2009  
2010 2010  == 3.5 Integrating with ThingsEye.io ==
2011 2011  
2002 +
2012 2012  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.
2013 2013  
2005 +
2014 2014  === 3.5.1 Configuring The Things Stack ===
2015 2015  
2008 +
2016 2016  We use The Things Stack Sandbox in this example:
2017 2017  
2018 2018  * In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
... ... @@ -2024,10 +2024,12 @@
2024 2024  The username and  password (API key) you created here are required in the next section.
2025 2025  {{/info}}
2026 2026  
2027 -[[image:tts-mqtt-integration.png||height="625" width="1000"]]
2020 +[[image:tts-mqtt-integration.png]]
2028 2028  
2022 +
2029 2029  === 3.5.2 Configuring ThingsEye.io ===
2030 2030  
2025 +
2031 2031  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.
2032 2032  
2033 2033  * Login to your [[ThingsEye.io >>https://thingseye.io]]account.
... ... @@ -2034,7 +2034,7 @@
2034 2034  * Under the **Integrations center**, click **Integrations**.
2035 2035  * Click the **Add integration** button (the button with the **+** symbol).
2036 2036  
2037 -[[image:thingseye-io-step-1.png||height="625" width="1000"]]
2032 +[[image:thingseye-io-step-1.png]]
2038 2038  
2039 2039  
2040 2040  On the **Add integration** window, configure the following:
... ... @@ -2049,7 +2049,7 @@
2049 2049  ** Allow create devices or assets
2050 2050  * Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
2051 2051  
2052 -[[image:thingseye-io-step-2.png||height="625" width="1000"]]
2047 +[[image:thingseye-io-step-2.png]]
2053 2053  
2054 2054  
2055 2055  **Uplink data converter:**
... ... @@ -2060,7 +2060,7 @@
2060 2060  * 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]].
2061 2061  * Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
2062 2062  
2063 -[[image:thingseye-io-step-3.png||height="625" width="1000"]]
2058 +[[image:thingseye-io-step-3.png]]
2064 2064  
2065 2065  
2066 2066  **Downlink data converter (this is an optional step):**
... ... @@ -2071,7 +2071,7 @@
2071 2071  * 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]].
2072 2072  * Click the **Next** button. You will be navigated to the **Connection** tab.
2073 2073  
2074 -[[image:thingseye-io-step-4.png||height="625" width="1000"]]
2069 +[[image:thingseye-io-step-4.png]]
2075 2075  
2076 2076  
2077 2077  **Connection:**
... ... @@ -2086,20 +2086,21 @@
2086 2086  
2087 2087  * Click the **Add** button.
2088 2088  
2089 -[[image:thingseye-io-step-5.png||height="625" width="1000"]]
2084 +[[image:thingseye-io-step-5.png]]
2090 2090  
2091 2091  
2092 2092  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.
2093 2093  
2094 2094  
2095 -[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
2090 +[[image:thingseye.io_integrationsCenter_integrations.png]]
2096 2096  
2097 2097  
2098 2098  ==== 3.5.2.1 Viewing integration details ====
2099 2099  
2095 +
2100 2100  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.
2101 2101  
2102 -[[image:integration-details.png||height="686" width="1000"]]
2098 +[[image:integration-details.png]]
2103 2103  
2104 2104  
2105 2105  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.
... ... @@ -2108,28 +2108,32 @@
2108 2108  See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
2109 2109  {{/info}}
2110 2110  
2111 -==== **3.5.2.2 Viewing events** ====
2112 2112  
2108 +==== 3.5.2.2 Viewing events ====
2109 +
2110 +
2113 2113  The **Events **tab displays all the uplink messages from the LT-22222-L.
2114 2114  
2115 2115  * Select **Debug **from the **Event type** dropdown.
2116 2116  * Select the** time frame** from the **time window**.
2117 2117  
2118 -[[image:thingseye-events.png||height="686" width="1000"]]
2116 +[[image:thingseye-events.png]]
2119 2119  
2120 2120  
2121 2121  * To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
2122 2122  
2123 -[[image:thingseye-json.png||width="1000"]]
2121 +[[image:thingseye-json.png]]
2124 2124  
2125 2125  
2126 -==== **3.5.2.3 Deleting an integration** ====
2124 +==== 3.5.2.3 Deleting an integration ====
2127 2127  
2126 +
2128 2128  If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
2129 2129  
2130 2130  
2131 2131  ==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
2132 2132  
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.
2141 +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" %)**Example4**(%%): Connecting to Dry Contact sensor
2263 +(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor
2264 2264  
2265 -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.
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.
2266 2266  
2267 -To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram.
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.
2268 2268  
2269 2269  [[image:image-20230616235145-1.png]]
2270 2270  
2271 -(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
2271 +(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector
2272 2272  
2273 2273  [[image:image-20240219115718-1.png]]
2274 2274  
... ... @@ -2344,8 +2344,9 @@
2344 2344  [[image:image-20220524100215-10.png||height="382" width="723"]]
2345 2345  
2346 2346  
2347 -== 3.7 LEDs Indicators ==
2347 +== 3.7 LED Indicators ==
2348 2348  
2349 +
2349 2349  The table below lists the behavior of LED indicators for each port function.
2350 2350  
2351 2351  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
... ... @@ -2378,18 +2378,22 @@
2378 2378  
2379 2379  = 4. Using AT Commands =
2380 2380  
2382 +
2381 2381  The LT-22222-L supports programming using AT Commands.
2382 2382  
2385 +
2383 2383  == 4.1 Connecting the LT-22222-L to a PC ==
2384 2384  
2388 +
2385 2385  (((
2386 -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.
2390 +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.
2387 2387  
2388 -[[image:usb-ttl-programming.png]]
2392 +[[image:usb-ttl-audio-jack-connection.jpg]]
2393 +
2394 +
2389 2389  )))
2390 2390  
2391 2391  
2392 -
2393 2393  (((
2394 2394  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:
2395 2395  )))
... ... @@ -2400,7 +2400,10 @@
2400 2400  (((
2401 2401  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/]]
2402 2402  
2408 +
2403 2403  == 4.2 LT-22222-L related AT commands ==
2410 +
2411 +
2404 2404  )))
2405 2405  
2406 2406  (((
... ... @@ -2419,39 +2419,39 @@
2419 2419  * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
2420 2420  * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
2421 2421  * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
2422 -* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2423 -* AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
2424 -* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2425 -* AT+PNM: Get or set the public network mode. (0: off, 1: on)
2426 -* AT+RX2FQ: Get or set the Rx2 window frequency
2427 -* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2428 -* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2429 -* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2430 -* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2431 -* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2432 -* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2433 -* AT+NWKID: Get or set the Network ID
2434 -* AT+FCU: Get or set the Frame Counter Uplink (FCntUp)
2435 -* AT+FCD: Get or set the Frame Counter Downlink (FCntDown)
2436 -* AT+CLASS: Get or set the Device Class
2437 -* AT+JOIN: Join network
2438 -* AT+NJS: Get OTAA Join Status
2439 -* AT+SENDB: Send hexadecimal data along with the application port
2440 -* AT+SEND: Send text data along with the application port
2441 -* AT+RECVB: Print last received data in binary format (with hexadecimal values)
2442 -* AT+RECV: Print last received data in raw format
2443 -* AT+VER: Get current image version and Frequency Band
2444 -* AT+CFM: Get or Set the confirmation mode (0-1)
2445 -* AT+CFS: Get confirmation status of the last AT+SEND (0-1)
2446 -* AT+SNR: Get the SNR of the last received packet
2447 -* AT+RSSI: Get the RSSI of the last received packet
2448 -* AT+TDC: Get or set the application data transmission interval in ms
2449 -* AT+PORT: Get or set the application port
2450 -* AT+DISAT: Disable AT commands
2451 -* AT+PWORD: Set password, max 9 digits
2452 -* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2453 -* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470
2454 -* AT+CFG: Print all settings
2430 +* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2431 +* **##AT+DR##**:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
2432 +* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2433 +* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)
2434 +* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency
2435 +* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2436 +* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2437 +* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2438 +* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2439 +* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2440 +* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2441 +* ##**AT+NWKID**##: Get or set the Network ID
2442 +* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)
2443 +* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)
2444 +* ##**AT+CLASS**##: Get or set the Device Class
2445 +* ##**AT+JOIN**##: Join network
2446 +* ##**AT+NJS**##: Get OTAA Join Status
2447 +* ##**AT+SENDB**##: Send hexadecimal data along with the application port
2448 +* ##**AT+SEND**##: Send text data along with the application port
2449 +* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)
2450 +* ##**AT+RECV**##: Print last received data in raw format
2451 +* ##**AT+VER**##: Get current image version and Frequency Band
2452 +* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)
2453 +* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)
2454 +* ##**AT+SNR**##: Get the SNR of the last received packet
2455 +* ##**AT+RSSI**##: Get the RSSI of the last received packet
2456 +* ##**AT+TDC**##: Get or set the application data transmission interval in ms
2457 +* ##**AT+PORT**##: Get or set the application port
2458 +* ##**AT+DISAT**##: Disable AT commands
2459 +* ##**AT+PWORD**##: Set password, max 9 digits
2460 +* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2461 +* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN470
2462 +* ##**AT+CFG**##: Print all settings
2455 2455  )))
2456 2456  
2457 2457  
... ... @@ -2597,16 +2597,19 @@
2597 2597  
2598 2598  == 5.1 Counting how many objects pass through the flow line ==
2599 2599  
2608 +
2600 2600  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]]?
2601 2601  
2602 2602  
2603 2603  = 6. FAQ =
2604 2604  
2614 +
2605 2605  This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
2606 2606  
2607 2607  
2608 2608  == 6.1 How to update the firmware? ==
2609 2609  
2620 +
2610 2610  Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to:
2611 2611  
2612 2612  * Support new features
... ... @@ -2616,7 +2616,7 @@
2616 2616  You will need the following things before proceeding:
2617 2617  
2618 2618  * 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
2619 -* USB to TTL adapter
2630 +* USB to TTL adapter/converter
2620 2620  * 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)
2621 2621  * 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.
2622 2622  
... ... @@ -2626,7 +2626,7 @@
2626 2626  
2627 2627  Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2628 2628  
2629 -[[image:usb-ttl-programming.png]]
2640 +[[image:usb-ttl-audio-jack-connection.jpg]]
2630 2630  
2631 2631  
2632 2632  
... ... @@ -2659,6 +2659,8 @@
2659 2659  (((
2660 2660  (((
2661 2661  == 6.2 How to change the LoRaWAN frequency band/region? ==
2673 +
2674 +
2662 2662  )))
2663 2663  )))
2664 2664  
... ... @@ -2670,6 +2670,8 @@
2670 2670  
2671 2671  
2672 2672  == 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
2686 +
2687 +
2673 2673  )))
2674 2674  
2675 2675  (((
... ... @@ -2743,11 +2743,13 @@
2743 2743  
2744 2744  == 6.4 How to change the uplink interval? ==
2745 2745  
2761 +
2746 2746  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/]]
2747 2747  
2748 2748  
2749 2749  == 6.5 Can I see the counting event in the serial output? ==
2750 2750  
2767 +
2751 2751  (((
2752 2752  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.
2753 2753  
... ... @@ -2754,6 +2754,7 @@
2754 2754  
2755 2755  == 6.6 Can I use point-to-point communication with LT-22222-L? ==
2756 2756  
2774 +
2757 2757  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]].
2758 2758  
2759 2759  
... ... @@ -2762,6 +2762,7 @@
2762 2762  (((
2763 2763  == 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
2764 2764  
2783 +
2765 2765  * If the device is not properly shut down and is directly powered off.
2766 2766  * It will default to a power-off state.
2767 2767  * In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
... ... @@ -2769,6 +2769,7 @@
2769 2769  
2770 2770  == 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
2771 2771  
2791 +
2772 2772  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:
2773 2773  
2774 2774  
... ... @@ -2777,16 +2777,19 @@
2777 2777  
2778 2778  == 6.9 Can the LT-22222-L save the RO state? ==
2779 2779  
2800 +
2780 2780  To enable this feature, the firmware version must be 1.6.0 or higher.
2781 2781  
2782 2782  
2783 2783  == 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
2784 2784  
2806 +
2785 2785  It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
2786 2786  
2787 2787  
2788 2788  = 7. Troubleshooting =
2789 2789  
2812 +
2790 2790  This section provides some known troubleshooting tips.
2791 2791  
2792 2792  
... ... @@ -2795,6 +2795,8 @@
2795 2795  (((
2796 2796  (((
2797 2797  == 7.1 Downlink isn't working. How can I solve this? ==
2821 +
2822 +
2798 2798  )))
2799 2799  )))
2800 2800  
... ... @@ -2806,6 +2806,8 @@
2806 2806  
2807 2807  
2808 2808  == 7.2 Having trouble uploading an image? ==
2834 +
2835 +
2809 2809  )))
2810 2810  
2811 2811  (((
... ... @@ -2816,6 +2816,8 @@
2816 2816  
2817 2817  
2818 2818  == 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
2846 +
2847 +
2819 2819  )))
2820 2820  
2821 2821  (((
... ... @@ -2825,6 +2825,7 @@
2825 2825  
2826 2826  == 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? ==
2827 2827  
2857 +
2828 2828  The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
2829 2829  Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2830 2830  
... ... @@ -2831,6 +2831,7 @@
2831 2831  
2832 2832  = 8. Ordering information =
2833 2833  
2864 +
2834 2834  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
2835 2835  
2836 2836  (% style="color:#4f81bd" %)**XXX:**
... ... @@ -2847,6 +2847,7 @@
2847 2847  
2848 2848  = 9. Package information =
2849 2849  
2881 +
2850 2850  **Package includes**:
2851 2851  
2852 2852  * 1 x LT-22222-L I/O Controller
... ... @@ -2863,6 +2863,7 @@
2863 2863  
2864 2864  = 10. Support =
2865 2865  
2898 +
2866 2866  * (((
2867 2867  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.
2868 2868  )))
... ... @@ -2874,6 +2874,7 @@
2874 2874  
2875 2875  = 11. Reference​​​​​ =
2876 2876  
2910 +
2877 2877  * 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]]
2878 2878  * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]]
2879 2879  * [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]
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-dashboard.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +352.8 KB
Content
lt-22222-l-joining.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +301.9 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
usb-ttl-audio-jack-connection.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +394.4 KB
Content