Skip to Content
Last modified by Mengting Qiu on 2025/06/04 18:42
From version 236.1
edited by Dilisi S
on 2024/12/18 06:03
Change comment: Dec 17 - some minor edits
To version 216.1
edited by Dilisi S
on 2024/11/24 22:05
Change comment: Uploaded new attachment "usb-ttl-audio-jack-connection.jpg", version {1}

Summary

Details

Page properties
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
... ... @@ -100,7 +100,6 @@
100 100  
101 101  == 1.3 Features ==
102 102  
103 -
104 104  * LoRaWAN Class A & Class C modes
105 105  * Optional Customized LoRa Protocol
106 106  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
... ... @@ -111,7 +111,6 @@
111 111  
112 112  == 1.4 Applications ==
113 113  
114 -
115 115  * Smart buildings & home automation
116 116  * Logistics and supply chain management
117 117  * Smart metering
... ... @@ -121,13 +121,11 @@
121 121  
122 122  == 1.5 Hardware Variants ==
123 123  
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" %)(((
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" %)(((
131 131  * 2 x Digital Input (Bi-direction)
132 132  * 2 x Digital Output
133 133  * 2 x Relay Output (5A@250VAC / 30VDC)
... ... @@ -140,7 +140,6 @@
140 140  
141 141  == 2.1 Connecting the antenna ==
142 142  
143 -
144 144  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.
145 145  
146 146  {{warning}}
... ... @@ -147,45 +147,42 @@
147 147  **Warning! Do not power on the device without connecting the antenna.**
148 148  {{/warning}}
149 149  
150 -
151 151  == 2.2 Terminals ==
152 152  
153 -
154 154  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.
155 155  
156 156  **Upper screw terminal block (from left to right):**
157 157  
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
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
166 166  
167 167  **Lower screw terminal block (from left to right):**
168 168  
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
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
181 181  
182 182  == 2.3 Connecting LT-22222-L to a Power Source ==
183 183  
184 -
185 185  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.
186 186  
187 187  {{warning}}
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.**
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.**
189 189  {{/warning}}
190 190  
191 191  
... ... @@ -194,27 +194,23 @@
194 194  
195 195  = 3. Registering LT-22222-L with a LoRaWAN Network Server =
196 196  
197 -
198 198  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.
199 199  
200 200  
201 -== 3.1 Prerequisites ==
189 +=== 3.2.1 Prerequisites ===
202 202  
203 -
204 204  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.
205 205  
206 206  [[image:image-20230425173427-2.png||height="246" width="530"]]
207 207  
208 208  {{info}}
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.
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.
210 210  {{/info}}
211 211  
212 212  The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
213 213  
201 +=== 3.2.2 The Things Stack ===
214 214  
215 -== 3.2 The Things Stack ==
216 -
217 -
218 218  This section guides you through how to register your LT-22222-L with The Things Stack Sandbox.
219 219  
220 220  {{info}}
... ... @@ -225,7 +225,7 @@
225 225  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.
226 226  
227 227  
228 -[[image:dragino-lorawan-nw-lt-22222-n.jpg||height="374" width="1400"]]
213 +[[image:dragino-lorawan-nw-lt-22222-n.jpg]]
229 229  
230 230  {{info}}
231 231   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.
... ... @@ -232,9 +232,8 @@
232 232  {{/info}}
233 233  
234 234  
235 -=== 3.2.1 Setting up ===
220 +==== 3.2.2.1 Setting up ====
236 236  
237 -
238 238  * Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet.
239 239  * Log in to your The Things Stack Sandbox account.
240 240  * Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs).
... ... @@ -241,9 +241,8 @@
241 241  * Go to your application's page and click on the **End devices** in the left menu.
242 242  * On the End devices page, click on **+ Register end device**. Two registration options are available:
243 243  
244 -==== 3.2.1.1 Using the LoRaWAN Device Repository ====
228 +==== 3.2.2.2 Using the LoRaWAN Device Repository ====
245 245  
246 -
247 247  * On the **Register end device** page:
248 248  ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
249 249  ** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists.
... ... @@ -254,7 +254,7 @@
254 254  *** **Profile (Region)**: Select the region that matches your device.
255 255  ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
256 256  
257 -[[image:lt-22222-l-dev-repo-reg-p1.png]]
240 +[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
258 258  
259 259  
260 260  * Register end device page continued...
... ... @@ -264,12 +264,11 @@
264 264  ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
265 265  ** Under **After registration**, select the **View registered end device** option.
266 266  
267 -[[image:lt-22222-l-dev-repo-reg-p2.png]]
250 +[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
268 268  
269 269  
270 -==== 3.2.1.2 Adding device manually ====
253 +==== 3.2.2.3 Adding device manually ====
271 271  
272 -
273 273  * On the **Register end device** page:
274 274  ** Select the option **Enter end device specifies manually** under **Input method**.
275 275  ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
... ... @@ -279,7 +279,7 @@
279 279  ** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
280 280  ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
281 281  
282 -[[image:lt-22222-l-manually-p1.png]]
264 +[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
283 283  
284 284  
285 285  * Register end device page continued...
... ... @@ -290,57 +290,49 @@
290 290  ** Under **After registration**, select the **View registered end device** option.
291 291  ** Click the **Register end device** button.
292 292  
293 -[[image:lt-22222-l-manually-p2.png]]
275 +[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
294 294  
295 295  
296 296  You will be navigated to the **Device overview** page.
297 297  
298 298  
299 -[[image:lt-22222-device-overview.png]]
281 +[[image:lt-22222-device-overview.png||height="625" width="1000"]]
300 300  
301 301  
302 -=== 3.2.2 Joining ===
284 +==== 3.2.2.4 Joining ====
303 303  
286 +On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
304 304  
305 -On the end device's page (in this case, lt-22222-l), click on **Live data** tab. The Live data panel for your device will display. Initially, it is blank.
306 -
307 307  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.
308 308  
309 309  
310 -[[image:lt-22222-l-joining.png]]
291 +[[image:lt-22222-join-network.png||height="625" width="1000"]]
311 311  
312 312  
313 -=== 3.2.3 Uplinks ===
294 +==== 3.2.2.5 Uplinks ====
314 314  
315 315  
316 -After successfully joining, the device will send its first **uplink data message** to The Things Stack application it belongs to (in this example, it is **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.
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.
317 317  
318 -Click on one of a **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the **decode_payload {}** JSON object.
299 +Click on one of a **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the decode_payload {} JSON object.
319 319  
320 320  [[image:lt-22222-ul-payload-decoded.png]]
321 321  
322 322  
323 -If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **Applications > [your application] > End devices** > [**your end device]** > **Payload formatters** > **Uplink**. Then  select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
304 +If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **Applications > your application > End devices** > **your end device** > **Payload formatters** > **Uplink**. Then  select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
324 324  
325 325  {{info}}
326 326  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.
327 327  {{/info}}
328 328  
329 -[[image:lt-22222-ul-payload-fmt.png]]
310 +[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
330 330  
331 331  
332 -We have written a payload formatter that resolves some decoding issues present in The Things Stack Device Repository payload 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]]:
313 +==== 3.2.2.6 Downlinks ====
333 333  
334 -(% class="wikigeneratedid" %)
335 -[[image:lt-22222-l-js-custom-payload-formatter.png]]
315 +When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
336 336  
337 337  
338 -=== 3.2.4 Downlinks ===
339 -
340 -
341 -When the LT-22222-L receives a downlink message from the LoRaWAN Network Server, the **RX LED** turns on for **1 second**.
342 -
343 -
344 344  == 3.3 Working Modes and Uplink Payload formats ==
345 345  
346 346  
... ... @@ -360,10 +360,8 @@
360 360  
361 361  The uplink messages are sent over LoRaWAN FPort=2. By default, an uplink message is sent every 10 minutes.
362 362  
363 -
364 364  === 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
365 365  
366 -
367 367  (((
368 368  This is the default mode.
369 369  
... ... @@ -436,7 +436,6 @@
436 436  
437 437  MOD = 1
438 438  
439 -
440 440  === 3.3.2 AT+MOD~=2, (Double DI Counting) ===
441 441  
442 442  
... ... @@ -515,7 +515,6 @@
515 515  
516 516  === 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI ===
517 517  
518 -
519 519  (% style="color:red" %)**Note: The maximum count depends on the bytes it is.
520 520  The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
521 521  It starts counting again when it reaches the maximum value.**
... ... @@ -569,7 +569,6 @@
569 569  
570 570  === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting ===
571 571  
572 -
573 573  (% style="color:red" %)**Note:The maximum count depends on the bytes it is.
574 574  The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
575 575  It starts counting again when it reaches the maximum value.**
... ... @@ -629,17 +629,16 @@
629 629  
630 630  (% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)**
631 631  
632 -(% 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)**
633 633  
634 -(% 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)**
635 635  
636 -(% 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)**
637 637  )))
638 638  
639 639  
640 640  === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI ===
641 641  
642 -
643 643  (% style="color:red" %)**Note:The maximum count depends on the bytes it is.
644 644  The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
645 645  It starts counting again when it reaches the maximum value.**
... ... @@ -753,9 +753,9 @@
753 753  
754 754  (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
755 755  
756 -**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**
757 757  
758 -**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
726 +Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
759 759  
760 760   AA: Type Code for this downlink Command:
761 761  
... ... @@ -784,7 +784,7 @@
784 784  
785 785  MOD6 Payload: total of 11 bytes
786 786  
787 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
755 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
788 788  |(% 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**
789 789  |Value|(((
790 790  TRI_A FLAG
... ... @@ -798,7 +798,7 @@
798 798  
799 799  (% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
800 800  
801 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
769 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
802 802  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
803 803  |(((
804 804  AV1_LOW
... ... @@ -822,12 +822,12 @@
822 822  
823 823  **Example:**
824 824  
825 -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
826 826  
827 827  
828 828  (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
829 829  
830 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
798 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
831 831  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
832 832  |(((
833 833  AV1_LOW
... ... @@ -851,31 +851,31 @@
851 851  
852 852  **Example:**
853 853  
854 -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.
855 855  
856 856  
857 857  (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
858 858  
859 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
860 -|(% 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**
861 -|(% 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
862 862  
863 -* Each bit shows which status has been triggered on this uplink.
831 +* Each bits shows which status has been triggered on this uplink.
864 864  
865 865  **Example:**
866 866  
867 -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.
868 868  
869 -00000101: This means both DI1 and DI2 triggers are enabled.
837 +00000101: Means both DI1 and DI2 trigger are enabled.
870 870  
871 871  
872 -(% 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.
873 873  
874 -Downlink command to poll/request MOD6 status:
842 +Downlink command to poll MOD6 status:
875 875  
876 876  **AB 06**
877 877  
878 -When device receives this command, it will send the MOD6 payload.
846 +When device got this command, it will send the MOD6 payload.
879 879  
880 880  
881 881  === 3.3.7 Payload Decoder ===
... ... @@ -889,7 +889,6 @@
889 889  
890 890  == 3.4 ​Configure LT-22222-L via AT Commands or Downlinks ==
891 891  
892 -
893 893  (((
894 894  You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks.
895 895  )))
... ... @@ -906,22 +906,17 @@
906 906  
907 907  === 3.4.1 Common commands ===
908 908  
909 -
910 910  (((
911 911  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.
912 -
913 -
914 914  )))
915 915  
916 916  === 3.4.2 Sensor-related commands ===
917 917  
918 -
919 919  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.
920 920  
921 921  
922 922  ==== 3.4.2.1 Set Transmit/Uplink Interval ====
923 923  
924 -
925 925  Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
926 926  
927 927  (% style="color:#037691" %)**AT command**
... ... @@ -928,15 +928,8 @@
928 928  
929 929  (% border="2" style="width:500px" %)
930 930  |**Command**|AT+TDC=<time>
931 -|**Parameters**|**time **: uplink interval in milliseconds
932 -|**Get**|AT+TDC=?
933 -|**Response**|(((
934 -current uplink interval
935 -
936 -OK
937 -)))
938 -|**Set**|AT+TDC=<time>
939 -|**Response**|OK
893 +|**Response**|
894 +|**Parameters**|**time** : uplink interval is in **milliseconds**
940 940  |**Example**|(((
941 941  AT+TDC=30000
942 942  
... ... @@ -952,7 +952,7 @@
952 952  |**Parameters**|(((
953 953  **prefix** : 0x01
954 954  
955 -**time** : uplink interval in **seconds**, represented by **3  bytes** in **hexadecimal**.
910 +**time** : uplink interval is in **seconds**, represented by **3  bytes** in **hexadecimal**.
956 956  )))
957 957  |**Example**|(((
958 958  01 **00 00 1E**
... ... @@ -968,13 +968,13 @@
968 968  
969 969  ==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
970 970  
971 -
972 972  Sets the working mode.
973 973  
974 974  (% style="color:#037691" %)**AT command**
975 975  
976 976  (% border="2" style="width:500px" %)
977 -|(% 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" %)
978 978  |(% style="width:97px" %)**Parameters**|(% style="width:413px" %)(((
979 979  **working_mode** :
980 980  
... ... @@ -990,18 +990,6 @@
990 990  
991 991  6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5
992 992  )))
993 -|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=?
994 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
995 -Current working mode
996 -
997 -OK
998 -)))
999 -|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode>
1000 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
1001 -Attention:Take effect after ATZ
1002 -
1003 -OK
1004 -)))
1005 1005  |(% style="width:97px" %)**Example**|(% style="width:413px" %)(((
1006 1006  AT+MOD=2
1007 1007  
... ... @@ -1024,9 +1024,8 @@
1024 1024  Sets the device to working mode 2 (Double DI Counting + DO + RO)
1025 1025  )))
1026 1026  
1027 -==== 3.4.2.3 Request an uplink from the device ====
970 +==== 3.4.2.3 Poll an uplink ====
1028 1028  
1029 -
1030 1030  Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.
1031 1031  
1032 1032  (% style="color:#037691" %)**AT command**
... ... @@ -1046,7 +1046,6 @@
1046 1046  
1047 1047  ==== 3.4.2.4 Enable/Disable Trigger Mode ====
1048 1048  
1049 -
1050 1050  Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
1051 1051  
1052 1052  (% style="color:#037691" %)**AT Command**
... ... @@ -1082,11 +1082,10 @@
1082 1082  Enable trigger mode for the current working mode
1083 1083  )))
1084 1084  
1085 -==== 3.4.2.5 Request trigger settings ====
1026 +==== 3.4.2.5 Poll trigger settings ====
1086 1086  
1028 +Polls the trigger settings.
1087 1087  
1088 -Requests the trigger settings.
1089 -
1090 1090  (% style="color:#037691" %)**AT Command:**
1091 1091  
1092 1092  There is no AT Command available for this feature.
... ... @@ -1104,7 +1104,6 @@
1104 1104  
1105 1105  ==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ====
1106 1106  
1107 -
1108 1108  Enable or disable DI1/DI2/DI3 as a trigger.
1109 1109  
1110 1110  (% style="color:#037691" %)**AT Command**
... ... @@ -1159,9 +1159,9 @@
1159 1159  
1160 1160  ==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ====
1161 1161  
1162 -
1163 1163  Sets DI1 or DI3 (for LT-33222-L) as a trigger.
1164 1164  
1103 +
1165 1165  (% style="color:#037691" %)**AT Command**
1166 1166  
1167 1167  (% border="2" style="width:500px" %)
... ... @@ -1198,9 +1198,9 @@
1198 1198  
1199 1199  ==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
1200 1200  
1201 -
1202 1202  Sets DI2 as a trigger.
1203 1203  
1142 +
1204 1204  (% style="color:#037691" %)**AT Command**
1205 1205  
1206 1206  (% border="2" style="width:500px" %)
... ... @@ -1232,7 +1232,6 @@
1232 1232  
1233 1233  ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
1234 1234  
1235 -
1236 1236  Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1237 1237  
1238 1238  (% style="color:#037691" %)**AT Command**
... ... @@ -1282,7 +1282,6 @@
1282 1282  
1283 1283  ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
1284 1284  
1285 -
1286 1286  Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1287 1287  
1288 1288  (% style="color:#037691" %)**AT Command**
... ... @@ -1330,7 +1330,6 @@
1330 1330  
1331 1331  ==== 3.4.2.11 Trigger – Set minimum interval ====
1332 1332  
1333 -
1334 1334  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.
1335 1335  
1336 1336  (% style="color:#037691" %)**AT Command**
... ... @@ -1366,7 +1366,6 @@
1366 1366  
1367 1367  ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
1368 1368  
1369 -
1370 1370  Controls the digital outputs DO1, DO2, and DO3
1371 1371  
1372 1372  (% style="color:#037691" %)**AT Command**
... ... @@ -1397,11 +1397,11 @@
1397 1397  (((
1398 1398  01: Low,  00: High,  11: No action
1399 1399  
1400 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:383px" %)
1401 -|(% 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**
1402 -|(% style="width:126px" %)02  01  00  11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action
1403 -|(% style="width:126px" %)02  00  11  01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low
1404 -|(% 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
1405 1405  )))
1406 1406  
1407 1407  (((
... ... @@ -1418,161 +1418,148 @@
1418 1418  ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
1419 1419  
1420 1420  
1421 -(% style="color:#037691" %)**AT command**
1356 +* (% 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 -(% style="color:#037691" %)**Downlink payload**
1361 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
1427 1427  
1363 +(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Set DO1/DO2/DO3 output with time control
1428 1428  
1429 -(% border="2" style="width:500px" %)
1430 -|(% style="width:116px" %)**Prefix**|(% style="width:382px" %)0xA9
1431 -|(% style="width:116px" %)**Parameters**|(% style="width:382px" %)(((
1432 -**inverter_mode**: 1 byte in hex.
1433 1433  
1434 -**01:** DO pins revert to their original state after the timeout.
1435 -**00:** DO pins switch to an inverted state after the timeout.
1366 +This is to control the digital output time of DO pin. Include four bytes:
1436 1436  
1368 +(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
1437 1437  
1438 -**DO1_control_method_and_port_status **- 1 byte in hex
1370 +(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode
1439 1439  
1440 -0x01 : DO1 set to low
1372 +01: DO pins will change back to original state after timeout.
1441 1441  
1442 -0x00 : DO1 set to high
1374 +00: DO pins will change to an inverter state after timeout 
1443 1443  
1444 -0x11 : DO1 NO action
1445 1445  
1377 +(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
1446 1446  
1447 -**DO2_control_method_and_port_status** - 1 byte in hex
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 1448  
1449 -0x01 : DO2 set to low
1385 +(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:
1450 1450  
1451 -0x00 : DO2 set to high
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 1452  
1453 -0x11 : DO2 NO action
1393 +(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:
1454 1454  
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
1455 1455  
1456 -**DO3_control_method_and_port_status **- 1 byte in hex
1401 +(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)
1457 1457  
1458 -0x01 : DO3 set to low
1459 1459  
1460 -0x00 : DO3 set to high
1404 +(% style="color:red" %)**Note: **
1461 1461  
1462 -0x11 : DO3 NO action
1406 + Since firmware v1.6.0, the latch time support 4 bytes and 2 bytes
1463 1463  
1408 + Before firmware v1.6.0, the latch time only supported 2 bytes.
1464 1464  
1465 -**latching_time** : 4 bytes in hex
1410 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1466 1466  
1467 -(% style="color:red" %)**Note: **
1468 1468  
1469 - Since firmware v1.6.0, the latch time support 4 bytes or 2 bytes
1413 +**Example payload:**
1470 1470  
1471 - Before firmware v1.6.0, the latch time only supported 2 bytes.
1415 +**~1. A9 01 01 01 01 07 D0**
1472 1472  
1473 -(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1474 -)))
1475 -|(% 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>
1476 -|(% style="width:116px" %)**Example**|(% style="width:382px" %)(((
1477 -**A9 01 01 01 01 07 D0**
1478 -
1479 1479  DO1 pin, DO2 pin, and DO3 pin will be set to low, last for 2 seconds, and then revert to their original state.
1480 1480  
1419 +**2. A9 01 00 01 11 07 D0**
1481 1481  
1482 -**A9 01 00 01 11 07 D0**
1483 -
1484 1484  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.
1485 1485  
1423 +**3. A9 00 00 00 00 07 D0**
1486 1486  
1487 -**A9 00 00 00 00 07 D0**
1488 -
1489 1489  DO1 pin, DO2 pin, and DO3 pin will be set to high, last for 2 seconds, and then all change to low.
1490 1490  
1427 +**4. A9 00 11 01 00 07 D0**
1491 1491  
1492 -**A9 00 11 01 00 07 D0**
1493 -
1494 1494  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.
1495 -)))
1496 1496  
1431 +
1497 1497  ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
1498 1498  
1499 1499  
1500 -(% style="color:#037691" %)**AT Command:**
1435 +* (% style="color:#037691" %)**AT Command:**
1501 1501  
1502 -There is no AT Command to control the Relay Output.
1437 +There is no AT Command to control Relay Output
1503 1503  
1504 1504  
1505 -(% style="color:#037691" %)**Downlink Payload**
1440 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
1506 1506  
1507 -(% border="2" style="width:500px" %)
1508 -|(% style="width:113px" %)**Prefix**|(% style="width:384px" %)0x03
1509 -|(% style="width:113px" %)**Parameters**|(% style="width:384px" %)(((
1510 -**RO1_status** : 1 byte in hex
1442 +(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Set RO1/RO2 output
1511 1511  
1512 -00: Close
1513 1513  
1514 -01: Open
1445 +(((
1446 +If payload is 0x030100, it means setting RO1 to close and RO2 to open.
1447 +)))
1515 1515  
1516 -11: No action
1449 +(((
1450 +00: Close ,  01: Open , 11: No action
1517 1517  
1518 -
1519 -**RO2_status** : 1 byte in hex
1520 -
1521 -00: Close
1522 -
1523 -01: Open
1524 -
1525 -11: No action
1452 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %)
1453 +|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**RO1**|(% style="background-color:#4f81bd; color:white" %)**RO2**
1454 +|03  00  11|Open|No Action
1455 +|03  01  11|Close|No Action
1456 +|03  11  00|No Action|Open
1457 +|03  11  01|No Action|Close
1458 +|03  00  00|Open|Open
1459 +|03  01  01|Close|Close
1460 +|03  01  00|Close|Open
1461 +|03  00  01|Open|Close
1526 1526  )))
1527 -|(% style="width:113px" %)**Payload format**|(% style="width:384px" %)<prefix><RO1_status><RO2_status>
1528 -|(% style="width:113px" %)**Example**|(% style="width:384px" %)(((
1529 -(% border="2" %)
1530 -|=Payload|=RO1|=RO2
1531 -|03  00  11|Open|No action
1532 -|03  01  11|Close|No action
1533 -|03 11  00|No action|Open
1534 -|03 11 10|No action|Close
1535 -|03 00 00|Open|Open
1536 -|03 01 01|Close|Close
1537 -|03 01 00|Close|Open
1538 -|03 00 01|Open|Close
1539 1539  
1540 -(% style="color:red" %)**The device will transmit an uplink packet if the downlink payload is executed successfully.**
1541 -)))
1464 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
1542 1542  
1466 +
1543 1543  ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
1544 1544  
1545 -
1546 1546  Controls the relay output time.
1547 1547  
1471 +* (% style="color:#037691" %)**AT Command:**
1548 1548  
1549 -(% style="color:#037691" %)**AT Command:**
1473 +There is no AT Command to control Relay Output
1550 1550  
1551 -There is no AT Command to control the Relay Output
1552 1552  
1476 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1553 1553  
1554 -(% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1478 +(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Set RO1/RO2 relay with time control
1555 1555  
1556 -(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
1557 1557  
1481 +This is to control the relay output time. It includes four bytes:
1558 1558  
1559 -This controls the relay output time and includes 4 bytes:
1483 +(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
1560 1560  
1561 -(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)
1485 +(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
1562 1562  
1563 -(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode
1564 -
1565 1565  01: Relays will change back to their original state after timeout.
1566 1566  
1567 1567  00: Relays will change to the inverter state after timeout.
1568 1568  
1569 1569  
1570 -(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status:
1492 +(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
1571 1571  
1572 1572  [[image:image-20221008095908-1.png||height="364" width="564"]]
1573 1573  
1574 1574  
1575 -(% 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
1576 1576  
1577 1577  
1578 1578  (% style="color:red" %)**Note:**
... ... @@ -1582,7 +1582,7 @@
1582 1582   Before firmware v1.6.0, the latch time only supported 2 bytes.
1583 1583  
1584 1584  
1585 -(% 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.**
1586 1586  
1587 1587  
1588 1588  **Example payload:**
... ... @@ -1741,9 +1741,8 @@
1741 1741  )))
1742 1742  |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
1743 1743  
1744 -==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ====
1666 +==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1745 1745  
1746 -
1747 1747  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.
1748 1748  
1749 1749  (% style="color:#037691" %)**AT Command**
... ... @@ -1773,9 +1773,8 @@
1773 1773  Sets the device to save its counting results to the memory every 60 seconds.
1774 1774  )))
1775 1775  
1776 -==== 3.4.2.20 Reset saved RO and DO states ====
1697 +==== 3.4.2.20 Reset save RO DO state ====
1777 1777  
1778 -
1779 1779  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.
1780 1780  
1781 1781  (% style="color:#037691" %)**AT Command**
... ... @@ -1800,6 +1800,7 @@
1800 1800  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.
1801 1801  )))
1802 1802  
1723 +
1803 1803  (% style="color:#037691" %)**Downlink Payload**
1804 1804  
1805 1805  (% border="2" style="width:500px" %)
... ... @@ -1825,7 +1825,6 @@
1825 1825  
1826 1826  ==== 3.4.2.21 Encrypted payload ====
1827 1827  
1828 -
1829 1829  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.
1830 1830  
1831 1831  (% style="color:#037691" %)**AT Command:**
... ... @@ -1855,7 +1855,6 @@
1855 1855  
1856 1856  ==== 3.4.2.22 Get sensor value ====
1857 1857  
1858 -
1859 1859  This command allows you to retrieve and optionally uplink sensor readings through the serial port.
1860 1860  
1861 1861  (% style="color:#037691" %)**AT Command**
... ... @@ -1885,7 +1885,6 @@
1885 1885  
1886 1886  ==== 3.4.2.23 Resetting the downlink packet count ====
1887 1887  
1888 -
1889 1889  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.
1890 1890  
1891 1891  (% style="color:#037691" %)**AT Command**
... ... @@ -1964,33 +1964,43 @@
1964 1964  
1965 1965  ==== 3.4.2.25 Copy downlink to uplink ====
1966 1966  
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.
1967 1967  
1968 -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**(%%)**:**
1969 1969  
1970 -(% 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.
1971 1971  
1972 -(% 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.
1973 1973  
1974 -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.
1975 1975  
1976 -
1977 1977  [[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"]]
1978 1978  
1979 1979  For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
1980 1980  
1981 -[[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
1982 1982  
1983 -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:
1984 1984  
1907 +01 00 02 58
1985 1985  
1986 -(% style="color:#037691" %)**Downlink Payload**(%%)**:**
1909 +Uplink:
1987 1987  
1988 -There is no downlink option available for this feature.
1911 +01 01 00 02 58
1912 +)))
1989 1989  
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"]]
1990 1990  
1991 -==== 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.
1992 1992  
1993 1993  
1919 +
1920 +==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
1921 +
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,13 +2009,10 @@
2009 2009  
2010 2010  == 3.5 Integrating with ThingsEye.io ==
2011 2011  
2012 -
2013 2013  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.
2014 2014  
2015 -
2016 2016  === 3.5.1 Configuring The Things Stack ===
2017 2017  
2018 -
2019 2019  We use The Things Stack Sandbox in this example:
2020 2020  
2021 2021  * In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
... ... @@ -2027,12 +2027,10 @@
2027 2027  The username and  password (API key) you created here are required in the next section.
2028 2028  {{/info}}
2029 2029  
2030 -[[image:tts-mqtt-integration.png]]
1955 +[[image:tts-mqtt-integration.png||height="625" width="1000"]]
2031 2031  
2032 -
2033 2033  === 3.5.2 Configuring ThingsEye.io ===
2034 2034  
2035 -
2036 2036  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.
2037 2037  
2038 2038  * Login to your [[ThingsEye.io >>https://thingseye.io]]account.
... ... @@ -2039,7 +2039,7 @@
2039 2039  * Under the **Integrations center**, click **Integrations**.
2040 2040  * Click the **Add integration** button (the button with the **+** symbol).
2041 2041  
2042 -[[image:thingseye-io-step-1.png]]
1965 +[[image:thingseye-io-step-1.png||height="625" width="1000"]]
2043 2043  
2044 2044  
2045 2045  On the **Add integration** window, configure the following:
... ... @@ -2054,7 +2054,7 @@
2054 2054  ** Allow create devices or assets
2055 2055  * Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
2056 2056  
2057 -[[image:thingseye-io-step-2.png]]
1980 +[[image:thingseye-io-step-2.png||height="625" width="1000"]]
2058 2058  
2059 2059  
2060 2060  **Uplink data converter:**
... ... @@ -2065,7 +2065,7 @@
2065 2065  * 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]].
2066 2066  * Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
2067 2067  
2068 -[[image:thingseye-io-step-3.png]]
1991 +[[image:thingseye-io-step-3.png||height="625" width="1000"]]
2069 2069  
2070 2070  
2071 2071  **Downlink data converter (this is an optional step):**
... ... @@ -2076,7 +2076,7 @@
2076 2076  * 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]].
2077 2077  * Click the **Next** button. You will be navigated to the **Connection** tab.
2078 2078  
2079 -[[image:thingseye-io-step-4.png]]
2002 +[[image:thingseye-io-step-4.png||height="625" width="1000"]]
2080 2080  
2081 2081  
2082 2082  **Connection:**
... ... @@ -2091,21 +2091,20 @@
2091 2091  
2092 2092  * Click the **Add** button.
2093 2093  
2094 -[[image:thingseye-io-step-5.png]]
2017 +[[image:thingseye-io-step-5.png||height="625" width="1000"]]
2095 2095  
2096 2096  
2097 2097  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.
2098 2098  
2099 2099  
2100 -[[image:thingseye.io_integrationsCenter_integrations.png]]
2023 +[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
2101 2101  
2102 2102  
2103 2103  ==== 3.5.2.1 Viewing integration details ====
2104 2104  
2105 -
2106 2106  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.
2107 2107  
2108 -[[image:integration-details.png]]
2030 +[[image:integration-details.png||height="686" width="1000"]]
2109 2109  
2110 2110  
2111 2111  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.
... ... @@ -2114,45 +2114,37 @@
2114 2114  See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
2115 2115  {{/info}}
2116 2116  
2039 +==== **3.5.2.2 Viewing events** ====
2117 2117  
2118 -==== 3.5.2.2 Viewing events ====
2119 -
2120 -
2121 2121  The **Events **tab displays all the uplink messages from the LT-22222-L.
2122 2122  
2123 2123  * Select **Debug **from the **Event type** dropdown.
2124 2124  * Select the** time frame** from the **time window**.
2125 2125  
2126 -[[image:thingseye-events.png]]
2046 +[[image:thingseye-events.png||height="686" width="1000"]]
2127 2127  
2128 2128  
2129 -* To view the **JSON payload** of a message, click on the **three dots (...)** in the **Message** column of the desired message.
2049 +* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
2130 2130  
2131 -[[image:thingseye-json.png]]
2051 +[[image:thingseye-json.png||width="1000"]]
2132 2132  
2133 2133  
2134 -==== 3.5.2.3 Deleting an integration ====
2054 +==== **3.5.2.3 Deleting an integration** ====
2135 2135  
2136 -
2137 2137  If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
2138 2138  
2139 2139  
2140 -==== 3.5.2.4 Viewing sensor data on a dashboard ====
2059 +==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
2141 2141  
2061 +This will be added soon.
2142 2142  
2143 -You can create a dashboard with ThingsEye to visualize the sensor data coming from the LHT65N-VIB. The following image shows a dashboard created for the LT-22222-L. See **Creating a dashboard** in ThingsEye documentation for more information.
2144 2144  
2145 -
2146 -
2147 -[[image:lt-22222-l-dashboard.png]]
2148 -
2149 -
2150 2150  == 3.6 Interface Details ==
2151 2151  
2152 2152  === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
2153 2153  
2154 2154  
2155 -Supports** NPN-type **sensors.
2069 +Supports NPN-type sensors.
2156 2156  
2157 2157  [[image:1653356991268-289.png]]
2158 2158  
... ... @@ -2274,15 +2274,15 @@
2274 2274  )))
2275 2275  
2276 2276  
2277 -(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor
2191 +(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
2278 2278  
2279 -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.
2280 2280  
2281 -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.
2282 2282  
2283 2283  [[image:image-20230616235145-1.png]]
2284 2284  
2285 -(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector
2199 +(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
2286 2286  
2287 2287  [[image:image-20240219115718-1.png]]
2288 2288  
... ... @@ -2358,9 +2358,8 @@
2358 2358  [[image:image-20220524100215-10.png||height="382" width="723"]]
2359 2359  
2360 2360  
2361 -== 3.7 LED Indicators ==
2275 +== 3.7 LEDs Indicators ==
2362 2362  
2363 -
2364 2364  The table below lists the behavior of LED indicators for each port function.
2365 2365  
2366 2366  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
... ... @@ -2393,22 +2393,18 @@
2393 2393  
2394 2394  = 4. Using AT Commands =
2395 2395  
2396 -
2397 2397  The LT-22222-L supports programming using AT Commands.
2398 2398  
2399 -
2400 2400  == 4.1 Connecting the LT-22222-L to a PC ==
2401 2401  
2402 -
2403 2403  (((
2404 -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.
2405 2405  
2406 -[[image:usb-ttl-audio-jack-connection.jpg]]
2407 -
2408 -
2316 +[[image:usb-ttl-programming.png]]
2409 2409  )))
2410 2410  
2411 2411  
2320 +
2412 2412  (((
2413 2413  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:
2414 2414  )))
... ... @@ -2419,10 +2419,7 @@
2419 2419  (((
2420 2420  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/]]
2421 2421  
2422 -
2423 2423  == 4.2 LT-22222-L related AT commands ==
2424 -
2425 -
2426 2426  )))
2427 2427  
2428 2428  (((
... ... @@ -2441,39 +2441,39 @@
2441 2441  * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
2442 2442  * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
2443 2443  * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
2444 -* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2445 -* **##AT+DR##**:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
2446 -* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2447 -* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)
2448 -* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency
2449 -* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2450 -* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2451 -* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2452 -* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2453 -* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2454 -* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2455 -* ##**AT+NWKID**##: Get or set the Network ID
2456 -* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)
2457 -* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)
2458 -* ##**AT+CLASS**##: Get or set the Device Class
2459 -* ##**AT+JOIN**##: Join network
2460 -* ##**AT+NJS**##: Get OTAA Join Status
2461 -* ##**AT+SENDB**##: Send hexadecimal data along with the application port
2462 -* ##**AT+SEND**##: Send text data along with the application port
2463 -* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)
2464 -* ##**AT+RECV**##: Print last received data in raw format
2465 -* ##**AT+VER**##: Get current image version and Frequency Band
2466 -* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)
2467 -* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)
2468 -* ##**AT+SNR**##: Get the SNR of the last received packet
2469 -* ##**AT+RSSI**##: Get the RSSI of the last received packet
2470 -* ##**AT+TDC**##: Get or set the application data transmission interval in ms
2471 -* ##**AT+PORT**##: Get or set the application port
2472 -* ##**AT+DISAT**##: Disable AT commands
2473 -* ##**AT+PWORD**##: Set password, max 9 digits
2474 -* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2475 -* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN470
2476 -* ##**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
2477 2477  )))
2478 2478  
2479 2479  
... ... @@ -2619,19 +2619,16 @@
2619 2619  
2620 2620  == 5.1 Counting how many objects pass through the flow line ==
2621 2621  
2622 -
2623 2623  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]]?
2624 2624  
2625 2625  
2626 2626  = 6. FAQ =
2627 2627  
2628 -
2629 2629  This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
2630 2630  
2631 2631  
2632 2632  == 6.1 How to update the firmware? ==
2633 2633  
2634 -
2635 2635  Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to:
2636 2636  
2637 2637  * Support new features
... ... @@ -2641,7 +2641,7 @@
2641 2641  You will need the following things before proceeding:
2642 2642  
2643 2643  * 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
2644 -* USB to TTL adapter/converter
2547 +* USB to TTL adapter
2645 2645  * 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)
2646 2646  * 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.
2647 2647  
... ... @@ -2651,7 +2651,7 @@
2651 2651  
2652 2652  Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2653 2653  
2654 -[[image:usb-ttl-audio-jack-connection.jpg]]
2557 +[[image:usb-ttl-programming.png]]
2655 2655  
2656 2656  
2657 2657  
... ... @@ -2684,8 +2684,6 @@
2684 2684  (((
2685 2685  (((
2686 2686  == 6.2 How to change the LoRaWAN frequency band/region? ==
2687 -
2688 -
2689 2689  )))
2690 2690  )))
2691 2691  
... ... @@ -2697,8 +2697,6 @@
2697 2697  
2698 2698  
2699 2699  == 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
2700 -
2701 -
2702 2702  )))
2703 2703  
2704 2704  (((
... ... @@ -2772,13 +2772,11 @@
2772 2772  
2773 2773  == 6.4 How to change the uplink interval? ==
2774 2774  
2775 -
2776 2776  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/]]
2777 2777  
2778 2778  
2779 2779  == 6.5 Can I see the counting event in the serial output? ==
2780 2780  
2781 -
2782 2782  (((
2783 2783  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.
2784 2784  
... ... @@ -2785,7 +2785,6 @@
2785 2785  
2786 2786  == 6.6 Can I use point-to-point communication with LT-22222-L? ==
2787 2787  
2788 -
2789 2789  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]].
2790 2790  
2791 2791  
... ... @@ -2794,7 +2794,6 @@
2794 2794  (((
2795 2795  == 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
2796 2796  
2797 -
2798 2798  * If the device is not properly shut down and is directly powered off.
2799 2799  * It will default to a power-off state.
2800 2800  * In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
... ... @@ -2802,7 +2802,6 @@
2802 2802  
2803 2803  == 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
2804 2804  
2805 -
2806 2806  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:
2807 2807  
2808 2808  
... ... @@ -2811,19 +2811,16 @@
2811 2811  
2812 2812  == 6.9 Can the LT-22222-L save the RO state? ==
2813 2813  
2814 -
2815 2815  To enable this feature, the firmware version must be 1.6.0 or higher.
2816 2816  
2817 2817  
2818 2818  == 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
2819 2819  
2820 -
2821 2821  It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
2822 2822  
2823 2823  
2824 2824  = 7. Troubleshooting =
2825 2825  
2826 -
2827 2827  This section provides some known troubleshooting tips.
2828 2828  
2829 2829  
... ... @@ -2832,8 +2832,6 @@
2832 2832  (((
2833 2833  (((
2834 2834  == 7.1 Downlink isn't working. How can I solve this? ==
2835 -
2836 -
2837 2837  )))
2838 2838  )))
2839 2839  
... ... @@ -2845,8 +2845,6 @@
2845 2845  
2846 2846  
2847 2847  == 7.2 Having trouble uploading an image? ==
2848 -
2849 -
2850 2850  )))
2851 2851  
2852 2852  (((
... ... @@ -2857,8 +2857,6 @@
2857 2857  
2858 2858  
2859 2859  == 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
2860 -
2861 -
2862 2862  )))
2863 2863  
2864 2864  (((
... ... @@ -2868,7 +2868,6 @@
2868 2868  
2869 2869  == 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? ==
2870 2870  
2871 -
2872 2872  The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
2873 2873  Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2874 2874  
... ... @@ -2875,7 +2875,6 @@
2875 2875  
2876 2876  = 8. Ordering information =
2877 2877  
2878 -
2879 2879  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
2880 2880  
2881 2881  (% style="color:#4f81bd" %)**XXX:**
... ... @@ -2892,7 +2892,6 @@
2892 2892  
2893 2893  = 9. Package information =
2894 2894  
2895 -
2896 2896  **Package includes**:
2897 2897  
2898 2898  * 1 x LT-22222-L I/O Controller
... ... @@ -2909,7 +2909,6 @@
2909 2909  
2910 2910  = 10. Support =
2911 2911  
2912 -
2913 2913  * (((
2914 2914  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.
2915 2915  )))
... ... @@ -2921,7 +2921,6 @@
2921 2921  
2922 2922  = 11. Reference​​​​​ =
2923 2923  
2924 -
2925 2925  * 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]]
2926 2926  * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]]
2927 2927  * [[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-dashboard.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -352.8 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