Last modified by Mengting Qiu on 2025/06/04 18:42

From version 210.1
edited by Dilisi S
on 2024/11/24 00:36
Change comment: fix toc
To version 237.1
edited by Dilisi S
on 2024/12/23 05:13
Change comment: Dec 22 - fix typos

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-33222-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)
... ... @@ -129,10 +129,11 @@
129 129  * 1 x Counting Port
130 130  )))
131 131  
132 -== 2. Assembling the device ==
139 += 2. Assembling the device =
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  
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  
154 +The  LT-22222-L has two screw terminal blocks. The upper screw terminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals.
155 +
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  
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  
204 +The LT-22222-L comes with device registration information such as DevEUI, AppEUI, and AppKey which allows you to register it with a LoRaWAN network. This 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 +
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,9 @@
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 ====
244 +==== 3.2.1.1 Using the LoRaWAN Device Repository ====
229 229  
246 +
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"]]
257 +[[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"]]
267 +[[image:lt-22222-l-dev-repo-reg-p2.png]]
251 251  
252 252  
253 -==== 3.2.2.3 Adding device manually ====
270 +==== 3.2.1.2 Adding device manually ====
254 254  
272 +
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"]]
282 +[[image:lt-22222-l-manually-p1.png]]
265 265  
266 266  
267 267  * Register end device page continued...
... ... @@ -272,49 +272,57 @@
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"]]
293 +[[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"]]
299 +[[image:lt-22222-device-overview.png]]
282 282  
283 283  
284 -==== 3.2.2.4 Joining ====
302 +=== 3.2.2 Joining ===
285 285  
286 -On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
287 287  
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 +
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"]]
310 +[[image:lt-22222-l-joining.png]]
292 292  
293 293  
294 -==== 3.2.2.5 Uplinks ====
313 +=== 3.2.3 Uplinks ===
295 295  
296 296  
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.
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.
298 298  
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.
318 +Click on one of the **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the **decode_payload {}** JSON object.
300 300  
301 301  [[image:lt-22222-ul-payload-decoded.png]]
302 302  
303 303  
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.
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.
305 305  
306 306  {{info}}
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"]]
329 +[[image:lt-22222-ul-payload-fmt.png]]
311 311  
312 312  
313 -==== 3.2.2.6 Downlinks ====
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]]:
314 314  
315 -When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
334 +(% class="wikigeneratedid" %)
335 +[[image:lt-22222-l-js-custom-payload-formatter.png]]
316 316  
317 317  
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 +
318 318  == 3.3 Working Modes and Uplink Payload formats ==
319 319  
320 320  
... ... @@ -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  
363 +
337 337  === 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
338 338  
366 +
339 339  (((
340 340  This is the default mode.
341 341  
... ... @@ -408,6 +408,7 @@
408 408  
409 409  MOD = 1
410 410  
439 +
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  
518 +
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  
572 +
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)**
632 +(% 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)**
634 +(% 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)**
636 +(% 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  
642 +
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.**
... ... @@ -694,7 +694,7 @@
694 694  
695 695  AT+AVLIM=3000,6000,0,2000 (triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V)
696 696  
697 -AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage lower than 5V. Use 0 for parameters that are not in use)
729 +AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage is lower than 5V. Use 0 for parameters that are not in use)
698 698  
699 699  
700 700  (% style="color:#4f81bd" %)**Trigger based on current**:
... ... @@ -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**
756 +**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
758 +**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
727 727  
728 728   AA: Type Code for this downlink Command:
729 729  
... ... @@ -750,9 +750,9 @@
750 750  
751 751  (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:**
752 752  
753 -MOD6 Payload: total of 11 bytes
785 +MOD6 Payload: a total of 11 bytes
754 754  
755 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
787 +(% 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
... ... @@ -764,9 +764,9 @@
764 764  MOD(6)
765 765  )))
766 766  
767 -(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
799 +(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Total 1 byte as below.
768 768  
769 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
801 +(% 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
825 +10100000: This means the system is configured to use the triggers AV1_LOW and AV2_LOW.
794 794  
795 795  
796 -(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
828 +(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is triggered. Total 1 byte as below.
797 797  
798 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
830 +(% 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.
854 +10000000: The uplink is triggered by AV1_LOW, indicating that the voltage is too low.
823 823  
824 824  
825 -(% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
857 +(% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is triggered. Total 1 byte 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
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
830 830  
831 -* Each bits shows which status has been triggered on this uplink.
863 +* 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.
867 +00000111: This means both DI1 and DI2 triggers are enabled, and this packet is triggered by DI1.
836 836  
837 -00000101: Means both DI1 and DI2 trigger are enabled.
869 +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.
872 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled.
841 841  
842 -Downlink command to poll MOD6 status:
874 +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.
878 +When the 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  
892 +
860 860  (((
861 861  You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks.
862 862  )))
... ... @@ -863,7 +863,7 @@
863 863  
864 864  (((
865 865  (((
866 -There are two tytes of commands:
899 +There are two types of commands:
867 867  )))
868 868  )))
869 869  
... ... @@ -873,17 +873,22 @@
873 873  
874 874  === 3.4.1 Common commands ===
875 875  
909 +
876 876  (((
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.
911 +These are available for each sensor 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 +
878 878  )))
879 879  
880 880  === 3.4.2 Sensor-related commands ===
881 881  
918 +
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 -==== 3.4.2.1 Set Transmit Interval ====
922 +==== 3.4.2.1 Set Transmit/Uplink Interval ====
886 886  
924 +
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,12 +890,19 @@
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
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
895 895  |**Example**|(((
896 896  AT+TDC=30000
897 897  
898 -Sets the uplink interval to 30,000 milliseconds (30 seconds)
943 +Sets the uplink interval to **30 seconds** (30000 milliseconds)
899 899  )))
900 900  
901 901  (% style="color:#037691" %)**Downlink payload**
... ... @@ -907,27 +907,29 @@
907 907  |**Parameters**|(((
908 908  **prefix** : 0x01
909 909  
910 -**time** : uplink interval is in milliseconds, represented by 3  bytes in hexadecimal.
955 +**time** : uplink interval in **seconds**, represented by **3  bytes** in **hexadecimal**.
911 911  )))
912 912  |**Example**|(((
913 -01 **00 75 30**
958 +01 **00 00 1E**
914 914  
915 -Sets the uplink interval to 30,000 milliseconds (30 seconds)
960 +Sets the uplink interval to **30 seconds**
916 916  
917 -Conversion: 30000 (dec) = 00 75 30 (hex)
962 +Conversion: 30 (dec) = 00 00 1E (hex)
918 918  
919 -See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]]
964 +See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30]]
965 +
966 +[[image:Screenshot 2024-11-23 at 18.27.11.png]]
920 920  )))
921 921  
922 922  ==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
923 923  
971 +
924 924  Sets the working mode.
925 925  
926 926  (% style="color:#037691" %)**AT command**
927 927  
928 928  (% border="2" style="width:500px" %)
929 -|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE=<working_mode>
930 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)
977 +|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MOD=<working_mode>
931 931  |(% style="width:97px" %)**Parameters**|(% style="width:413px" %)(((
932 932  **working_mode** :
933 933  
... ... @@ -943,6 +943,18 @@
943 943  
944 944  6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5
945 945  )))
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 +)))
946 946  |(% style="width:97px" %)**Example**|(% style="width:413px" %)(((
947 947  AT+MOD=2
948 948  
... ... @@ -965,13 +965,14 @@
965 965  Sets the device to working mode 2 (Double DI Counting + DO + RO)
966 966  )))
967 967  
968 -==== 3.4.2.3 Poll an uplink ====
1027 +==== 3.4.2.3 Request an uplink from the device ====
969 969  
970 -Requests an uplink from LT-22222-L.
971 971  
1030 +Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.
1031 +
972 972  (% style="color:#037691" %)**AT command**
973 973  
974 -There is no AT Command to request an uplink from LT-22222-L
1034 +There is no AT Command available for this feature.
975 975  
976 976  (% style="color:#037691" %)**Downlink payload**
977 977  
... ... @@ -979,7 +979,7 @@
979 979  |(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF
980 980  |(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08
981 981  |(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
982 -08 FF
1042 +08 **FF**
983 983  
984 984  Requests an uplink from LT-22222-L.
985 985  )))
... ... @@ -986,6 +986,7 @@
986 986  
987 987  ==== 3.4.2.4 Enable/Disable Trigger Mode ====
988 988  
1049 +
989 989  Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
990 990  
991 991  (% style="color:#037691" %)**AT Command**
... ... @@ -1013,7 +1013,7 @@
1013 1013  |(% style="width:97px" %)**Parameters**|(% style="width:401px" %)(((
1014 1014  **prefix** : 0x0A 06 (two bytes in hexadecimal)
1015 1015  
1016 -**working mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
1077 +**enable/disable trigger_mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
1017 1017  )))
1018 1018  |(% style="width:97px" %)**Example**|(% style="width:401px" %)(((
1019 1019  0A 06 **01**
... ... @@ -1021,13 +1021,14 @@
1021 1021  Enable trigger mode for the current working mode
1022 1022  )))
1023 1023  
1024 -==== 3.4.2.5 Poll trigger settings ====
1085 +==== 3.4.2.5 Request trigger settings ====
1025 1025  
1026 -Polls the trigger settings.
1027 1027  
1088 +Requests the trigger settings.
1089 +
1028 1028  (% style="color:#037691" %)**AT Command:**
1029 1029  
1030 -There is no AT Command for this feature.
1092 +There is no AT Command available for this feature.
1031 1031  
1032 1032  (% style="color:#037691" %)**Downlink Payload**
1033 1033  
... ... @@ -1037,11 +1037,12 @@
1037 1037  |(% style="width:95px" %)**Example**|(% style="width:403px" %)(((
1038 1038  AB 06
1039 1039  
1040 -Uplinks the trigger settings.
1102 +Uplink the trigger settings.
1041 1041  )))
1042 1042  
1043 1043  ==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ====
1044 1044  
1107 +
1045 1045  Enable or disable DI1/DI2/DI3 as a trigger.
1046 1046  
1047 1047  (% style="color:#037691" %)**AT Command**
... ... @@ -1096,9 +1096,9 @@
1096 1096  
1097 1097  ==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ====
1098 1098  
1162 +
1099 1099  Sets DI1 or DI3 (for LT-33222-L) as a trigger.
1100 1100  
1101 -
1102 1102  (% style="color:#037691" %)**AT Command**
1103 1103  
1104 1104  (% border="2" style="width:500px" %)
... ... @@ -1135,9 +1135,9 @@
1135 1135  
1136 1136  ==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
1137 1137  
1201 +
1138 1138  Sets DI2 as a trigger.
1139 1139  
1140 -
1141 1141  (% style="color:#037691" %)**AT Command**
1142 1142  
1143 1143  (% border="2" style="width:500px" %)
... ... @@ -1167,10 +1167,9 @@
1167 1167  )))
1168 1168  |(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64**
1169 1169  
1170 -
1171 -
1172 1172  ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
1173 1173  
1235 +
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  
1285 +
1223 1223  Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1224 1224  
1225 1225  (% style="color:#037691" %)**AT Command**
... ... @@ -1265,8 +1265,9 @@
1265 1265  )))
1266 1266  |(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1267 1267  
1268 -==== 3.4.2.11 Trigger – Set minimum interval ====
1331 +==== 3.4.2.11 Trigger – Set the minimum interval ====
1269 1269  
1333 +
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  
1369 +
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
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
1340 1340  )))
1341 1341  
1342 1342  (((
... ... @@ -1350,153 +1350,164 @@
1350 1350  )))
1351 1351  )))
1352 1352  
1353 -
1354 -
1355 1355  ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
1356 1356  
1357 1357  
1358 -* (% style="color:#037691" %)**AT Command**
1421 +(% style="color:#037691" %)**AT command**
1359 1359  
1360 -There is no AT Command to control Digital Output
1423 +There is no AT command to control the digital output.
1361 1361  
1362 1362  
1363 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
1426 +(% style="color:#037691" %)**Downlink payload**
1364 1364  
1365 -(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Set DO1/DO2/DO3 output with time control
1366 1366  
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.
1367 1367  
1368 -This is to control the digital output time of DO pin. Include four bytes:
1434 +**01:** DO pins revert to their original state after the timeout.
1435 +**00:** DO pins switch to an inverted state after the timeout.
1369 1369  
1370 -(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
1371 1371  
1372 -(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode
1438 +**DO1_control_method_and_port_status **- 1 byte in hex
1373 1373  
1374 -01: DO pins will change back to original state after timeout.
1440 +0x01 : DO1 set to low
1375 1375  
1376 -00: DO pins will change to an inverter state after timeout 
1442 +0x00 : DO1 set to high
1377 1377  
1444 +0x11 : DO1 NO action
1378 1378  
1379 -(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
1380 1380  
1381 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1382 -|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
1383 -|0x01|DO1 set to low
1384 -|0x00|DO1 set to high
1385 -|0x11|DO1 NO Action
1447 +**DO2_control_method_and_port_status** - 1 byte in hex
1386 1386  
1387 -(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:
1449 +0x01 : DO2 set to low
1388 1388  
1389 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1390 -|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
1391 -|0x01|DO2 set to low
1392 -|0x00|DO2 set to high
1393 -|0x11|DO2 NO Action
1451 +0x00 : DO2 set to high
1394 1394  
1395 -(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:
1453 +0x11 : DO2 NO action
1396 1396  
1397 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1398 -|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
1399 -|0x01|DO3 set to low
1400 -|0x00|DO3 set to high
1401 -|0x11|DO3 NO Action
1402 1402  
1403 -(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)
1456 +**DO3_control_method_and_port_status **- 1 byte in hex
1404 1404  
1458 +0x01 : DO3 set to low
1405 1405  
1406 -(% style="color:red" %)**Note: **
1460 +0x00 : DO3 set to high
1407 1407  
1408 - Since firmware v1.6.0, the latch time support 4 bytes and 2 bytes
1462 +0x11 : DO3 NO action
1409 1409  
1410 - Before firmware v1.6.0, the latch time only supported 2 bytes.
1411 1411  
1412 -(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1465 +**latching_time** : 4 bytes in hex
1413 1413  
1467 +(% style="color:red" %)**Note: **
1414 1414  
1415 -**Example payload:**
1469 + Since firmware v1.6.0, the latch time supports 4 bytes or 2 bytes
1416 1416  
1417 -**~1. A9 01 01 01 01 07 D0**
1471 + Before firmware v1.6.0, the latch time only supported 2 bytes.
1418 1418  
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 +
1419 1419  DO1 pin, DO2 pin, and DO3 pin will be set to low, last for 2 seconds, and then revert to their original state.
1420 1420  
1421 -**2. A9 01 00 01 11 07 D0**
1422 1422  
1482 +**A9 01 00 01 11 07 D0**
1483 +
1423 1423  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.
1424 1424  
1425 -**3. A9 00 00 00 00 07 D0**
1426 1426  
1487 +**A9 00 00 00 00 07 D0**
1488 +
1427 1427  DO1 pin, DO2 pin, and DO3 pin will be set to high, last for 2 seconds, and then all change to low.
1428 1428  
1429 -**4. A9 00 11 01 00 07 D0**
1430 1430  
1431 -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.
1492 +**A9 00 11 01 00 07 D0**
1432 1432  
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 the DO1 pin takes no action, the DO2 pin is set to high, and the DO3 pin is set to low.
1495 +)))
1433 1433  
1434 1434  ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
1435 1435  
1436 1436  
1437 -* (% style="color:#037691" %)**AT Command:**
1500 +(% style="color:#037691" %)**AT Command:**
1438 1438  
1439 -There is no AT Command to control Relay Output
1502 +There is no AT Command to control the Relay Output.
1440 1440  
1441 1441  
1442 -* (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
1505 +(% style="color:#037691" %)**Downlink Payload**
1443 1443  
1444 -(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Set RO1/RO2 output
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
1445 1445  
1512 +00: Close
1446 1446  
1447 -(((
1448 -If payload is 0x030100, it means setting RO1 to close and RO2 to open.
1449 -)))
1514 +01: Open
1450 1450  
1451 -(((
1452 -00: Close ,  01: Open , 11: No action
1516 +11: No action
1453 1453  
1454 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %)
1455 -|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**RO1**|(% style="background-color:#4f81bd; color:white" %)**RO2**
1456 -|03  00  11|Open|No Action
1457 -|03  01  11|Close|No Action
1458 -|03  11  00|No Action|Open
1459 -|03  11  01|No Action|Close
1460 -|03  00  00|Open|Open
1461 -|03  01  01|Close|Close
1462 -|03  01  00|Close|Open
1463 -|03  00  01|Open|Close
1464 -)))
1465 1465  
1466 -(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
1519 +**RO2_status** : 1 byte in hex
1467 1467  
1521 +00: Close
1468 1468  
1523 +01: Open
1524 +
1525 +11: No action
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 +
1540 +(% style="color:red" %)**The device will transmit an uplink packet if the downlink payload is executed successfully.**
1541 +)))
1542 +
1469 1469  ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
1470 1470  
1545 +
1471 1471  Controls the relay output time.
1472 1472  
1473 -* (% style="color:#037691" %)**AT Command:**
1474 1474  
1475 -There is no AT Command to control Relay Output
1549 +(% style="color:#037691" %)**AT Command:**
1476 1476  
1551 +There is no AT Command to control the Relay Output
1477 1477  
1478 -* (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1479 1479  
1480 -(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Set RO1/RO2 relay with time control
1554 +(% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1481 1481  
1556 +(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
1482 1482  
1483 -This is to control the relay output time. It includes four bytes:
1484 1484  
1485 -(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
1559 +This controls the relay output time and includes 4 bytes:
1486 1486  
1487 -(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
1561 +(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)
1488 1488  
1489 -01: Relays will change back to their original state after timeout.
1563 +(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode
1490 1490  
1491 -00: Relays will change to the inverter state after timeout.
1565 +01: Relays will change back to their original state after a timeout.
1492 1492  
1567 +00: Relays will change to the inverter state after a timeout.
1493 1493  
1494 -(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
1495 1495  
1570 +(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status:
1571 +
1496 1496  [[image:image-20221008095908-1.png||height="364" width="564"]]
1497 1497  
1498 1498  
1499 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms
1575 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes (cc)**(%%): Latching time. Unit: ms
1500 1500  
1501 1501  
1502 1502  (% style="color:red" %)**Note:**
... ... @@ -1506,7 +1506,7 @@
1506 1506   Before firmware v1.6.0, the latch time only supported 2 bytes.
1507 1507  
1508 1508  
1509 -(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1585 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1510 1510  
1511 1511  
1512 1512  **Example payload:**
... ... @@ -1517,7 +1517,7 @@
1517 1517  
1518 1518  **2. 05 01 10 07 D0**
1519 1519  
1520 -Relay1 will change to NC, Relay2 will change to NO, lasting 2 seconds, then both will revert to their original state.
1596 +Relay1 will change to NC, Relay2 will change to NO, lasting 2 seconds, and then both will revert to their original state.
1521 1521  
1522 1522  **3. 05 00 01 07 D0**
1523 1523  
... ... @@ -1534,17 +1534,10 @@
1534 1534  
1535 1535  When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
1536 1536  
1537 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX   ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
1538 -
1539 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):**
1540 -
1541 -(% style="color:blue" %)**0xA5 aa bb cc   ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc
1542 -
1543 -
1544 1544  (% style="color:#037691" %)**AT Command**
1545 1545  
1546 1546  (% border="2" style="width:500px" %)
1547 -|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage><logic>
1616 +|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage>,<logic>
1548 1548  |(% style="width:137px" %)**Response**|(% style="width:361px" %)
1549 1549  |(% style="width:137px" %)**Parameters**|(% style="width:361px" %)(((
1550 1550  **voltage** : voltage threshold in mV
... ... @@ -1551,11 +1551,11 @@
1551 1551  
1552 1552  **logic**:
1553 1553  
1554 -0 : lower than
1623 +**0** : lower than
1555 1555  
1556 -1: higher than
1625 +**1**: higher than
1557 1557  
1558 -if you leave logic parameter blank, it is considered 0
1627 +if you leave the logic parameter blank, it is considered 0
1559 1559  )))
1560 1560  |(% style="width:137px" %)**Examples**|(% style="width:361px" %)(((
1561 1561  AT+VOLMAX=20000
... ... @@ -1582,11 +1582,11 @@
1582 1582  
1583 1583  **logic**: (1 byte in hexadecimal)
1584 1584  
1585 -0 : lower than
1654 +**0** : lower than
1586 1586  
1587 -1: higher than
1656 +**1**: higher than
1588 1588  
1589 -if you leave logic parameter blank, it is considered 1 (higher than)
1658 +if you leave the logic parameter blank, it is considered 1 (higher than)
1590 1590  )))
1591 1591  |(% style="width:140px" %)**Example**|(% style="width:358px" %)(((
1592 1592  A5 **4E 20**
... ... @@ -1606,22 +1606,10 @@
1606 1606  
1607 1607  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.
1608 1608  
1609 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) **
1610 -
1611 -(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count
1612 -
1613 -(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set
1614 -
1615 -
1616 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):**
1617 -
1618 -(% style="color:blue" %)**0x A8 aa bb cc dd ee     ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee)
1619 -
1620 -
1621 1621  (% style="color:#037691" %)**AT Command**
1622 1622  
1623 1623  (% border="2" style="width:500px" %)
1624 -|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter><number>
1681 +|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter>,<number>
1625 1625  |(% style="width:134px" %)**Response**|(% style="width:364px" %)
1626 1626  |(% style="width:134px" %)**Parameters**|(% style="width:364px" %)(((
1627 1627  **counting_parameter** :
... ... @@ -1667,12 +1667,6 @@
1667 1667  
1668 1668  This command clears the counting in counting mode.
1669 1669  
1670 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT         **(%%) ~/~/ clear all counting
1671 -
1672 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):**
1673 -
1674 -(% style="color:blue" %)**0x A6 01    ** (%%)~/~/ clear all counting
1675 -
1676 1676  (% style="color:#037691" %)**AT Command**
1677 1677  
1678 1678  (% border="2" style="width:500px" %)
... ... @@ -1690,24 +1690,11 @@
1690 1690  )))
1691 1691  |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
1692 1692  
1693 -==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1744 +==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ====
1694 1694  
1746 +
1695 1695  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.
1696 1696  
1697 -* (% style="color:#037691" %)**AT Command:**
1698 -
1699 -(% 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)
1700 -
1701 -
1702 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):**
1703 -
1704 -(% style="color:blue" %)**0x A7 aa bb cc     ** (%%)~/~/ same as AT+COUTIME =aa bb cc,
1705 -
1706 -(((
1707 -Range: aa bb cc:0 to 16777215,  (unit: seconds)
1708 -)))
1709 -
1710 -
1711 1711  (% style="color:#037691" %)**AT Command**
1712 1712  
1713 1713  (% border="2" style="width:500px" %)
... ... @@ -1735,22 +1735,13 @@
1735 1735  Sets the device to save its counting results to the memory every 60 seconds.
1736 1736  )))
1737 1737  
1738 -==== 3.4.2.20 Reset save RO DO state ====
1776 +==== 3.4.2.20 Reset saved RO and DO states ====
1739 1739  
1778 +
1740 1740  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.
1741 1741  
1742 -* (% style="color:#037691" %)**AT Command:**
1781 +(% style="color:#037691" %)**AT Command**
1743 1743  
1744 -(% style="color:blue" %)**AT+RODORESET=1    **(%%)~/~/ RODO will close when the device joining the network. (default)
1745 -
1746 -(% 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.
1747 -
1748 -
1749 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):**
1750 -
1751 -(% style="color:blue" %)**0x AD aa      ** (%%)~/~/ same as AT+RODORET =aa
1752 -
1753 -
1754 1754  (% border="2" style="width:500px" %)
1755 1755  |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state>
1756 1756  |(% style="width:127px" %)**Response**|(% style="width:371px" %)
... ... @@ -1771,6 +1771,8 @@
1771 1771  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.
1772 1772  )))
1773 1773  
1803 +(% style="color:#037691" %)**Downlink Payload**
1804 +
1774 1774  (% border="2" style="width:500px" %)
1775 1775  |(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state>
1776 1776  |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
... ... @@ -1794,24 +1794,20 @@
1794 1794  
1795 1795  ==== 3.4.2.21 Encrypted payload ====
1796 1796  
1828 +
1797 1797  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.
1798 1798  
1799 -* (% style="color:#037691" %)**AT Command:**
1831 +(% style="color:#037691" %)**AT Command:**
1800 1800  
1801 -(% style="color:blue" %)**AT+DECRYPT=1  ** (%%)~/~/ The payload is uploaded without encryption
1802 -
1803 -(% style="color:blue" %)**AT+DECRYPT=0    **(%%)~/~/  Encrypt when uploading payload (default)
1804 -
1805 -
1806 1806  (% border="2" style="width:500px" %)
1807 1807  |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state>
1808 1808  |(% style="width:127px" %)**Response**|(% style="width:371px" %)
1809 1809  |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1810 -state :
1837 +**state** :
1811 1811  
1812 -1 : The payload is uploaded without encryption
1839 +**1** : The payload is uploaded without encryption
1813 1813  
1814 -0 : The payload is encrypted when uploaded (default)
1841 +**0** : The payload is encrypted when uploaded (default)
1815 1815  )))
1816 1816  |(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1817 1817  AT+DECRYPT=1
... ... @@ -1828,15 +1828,11 @@
1828 1828  
1829 1829  ==== 3.4.2.22 Get sensor value ====
1830 1830  
1858 +
1831 1831  This command allows you to retrieve and optionally uplink sensor readings through the serial port.
1832 1832  
1833 -* (% style="color:#037691" %)**AT Command:**
1861 +(% style="color:#037691" %)**AT Command**
1834 1834  
1835 -(% style="color:blue" %)**AT+GETSENSORVALUE=0    **(%%)~/~/ The serial port retrieves the reading of the current sensor.
1836 -
1837 -(% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it.
1838 -
1839 -
1840 1840  (% border="2" style="width:500px" %)
1841 1841  |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state>
1842 1842  |(% style="width:127px" %)**Response**|(% style="width:371px" %)
... ... @@ -1862,15 +1862,11 @@
1862 1862  
1863 1863  ==== 3.4.2.23 Resetting the downlink packet count ====
1864 1864  
1888 +
1865 1865  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.
1866 1866  
1867 -* (% style="color:#037691" %)**AT Command:**
1891 +(% style="color:#037691" %)**AT Command**
1868 1868  
1869 -(% 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)
1870 -
1871 -(% 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.
1872 -
1873 -
1874 1874  (% border="2" style="width:500px" %)
1875 1875  |(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state>
1876 1876  |(% style="width:130px" %)**Response**|(% style="width:368px" %)(((
... ... @@ -1900,19 +1900,8 @@
1900 1900  ==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ====
1901 1901  
1902 1902  
1903 -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.
1922 +This command controls the behavior of the node when the combined size of the MAC commands (MACANS) from the server and the payload exceed 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.
1904 1904  
1905 -* (% style="color:#037691" %)**AT Command:**
1906 -
1907 -(% 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)
1908 -
1909 -(% 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.
1910 -
1911 -
1912 -* (% style="color:#037691" %)**Downlink Payload **(%%)**:**
1913 -
1914 -(% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set  the DISMACANS=1
1915 -
1916 1916  (% style="color:#037691" %)**AT Command**
1917 1917  
1918 1918  (% border="2" style="width:500px" %)
... ... @@ -1956,49 +1956,39 @@
1956 1956  
1957 1957  ==== 3.4.2.25 Copy downlink to uplink ====
1958 1958  
1959 -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.
1960 1960  
1961 -* (% style="color:#037691" %)**AT Command**(%%)**:**
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.
1962 1962  
1963 -(% 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.
1970 +(% style="color:#037691" %)**AT Command**(%%)**:**
1964 1964  
1965 -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.
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.
1966 1966  
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.
1967 1967  
1976 +
1968 1968  [[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"]]
1969 1969  
1970 1970  For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
1971 1971  
1972 -(% border="2" style="width:500px" %)
1973 -|(% style="width:122px" %)**Command**|(% style="width:376px" %)(((
1974 -AT+RPL=5
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"]]
1975 1975  
1976 -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.
1977 -)))
1978 -|(% style="width:122px" %)**Example**|(% style="width:376px" %)(((
1979 -Downlink:
1983 +For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
1980 1980  
1981 -01 00 02 58
1982 1982  
1983 -Uplink:
1986 +(% style="color:#037691" %)**Downlink Payload**(%%)**:**
1984 1984  
1985 -01 01 00 02 58
1986 -)))
1988 +There is no downlink option available for this feature.
1987 1987  
1988 -[[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"]]
1989 1989  
1990 -For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
1991 +==== 3.4.2.26 Query firmware version, frequency band, subband, and TDC time ====
1991 1991  
1992 1992  
1994 +This command is used to query key information about the device, including its firmware version, frequency band, subband, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device.
1993 1993  
1994 -==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
1995 -
1996 -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.
1997 -
1998 1998  * (((
1999 1999  (% style="color:#037691" %)**Downlink Payload**(%%)**:**
2000 2000  
2001 -(% style="color:blue" %)**26 01  ** (%%) ~/~/  The downlink payload 26 01 is used to query the device's firmware version, frequency band, sub band, and TDC time.
1999 +(% style="color:blue" %)**26 01  ** (%%) ~/~/  The downlink payload 26 01 is used to query the device's firmware version, frequency band, subband, and TDC time.
2002 2002  
2003 2003  
2004 2004  
... ... @@ -2011,10 +2011,13 @@
2011 2011  
2012 2012  == 3.5 Integrating with ThingsEye.io ==
2013 2013  
2012 +
2014 2014  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.
2015 2015  
2015 +
2016 2016  === 3.5.1 Configuring The Things Stack ===
2017 2017  
2018 +
2018 2018  We use The Things Stack Sandbox in this example:
2019 2019  
2020 2020  * In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
... ... @@ -2026,10 +2026,12 @@
2026 2026  The username and  password (API key) you created here are required in the next section.
2027 2027  {{/info}}
2028 2028  
2029 -[[image:tts-mqtt-integration.png||height="625" width="1000"]]
2030 +[[image:tts-mqtt-integration.png]]
2030 2030  
2032 +
2031 2031  === 3.5.2 Configuring ThingsEye.io ===
2032 2032  
2035 +
2033 2033  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.
2034 2034  
2035 2035  * Login to your [[ThingsEye.io >>https://thingseye.io]]account.
... ... @@ -2036,7 +2036,7 @@
2036 2036  * Under the **Integrations center**, click **Integrations**.
2037 2037  * Click the **Add integration** button (the button with the **+** symbol).
2038 2038  
2039 -[[image:thingseye-io-step-1.png||height="625" width="1000"]]
2042 +[[image:thingseye-io-step-1.png]]
2040 2040  
2041 2041  
2042 2042  On the **Add integration** window, configure the following:
... ... @@ -2048,10 +2048,10 @@
2048 2048  * Ensure the following options are turned on.
2049 2049  ** Enable integration
2050 2050  ** Debug mode
2051 -** Allow create devices or assets
2054 +** Allow creating devices or assets
2052 2052  * Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
2053 2053  
2054 -[[image:thingseye-io-step-2.png||height="625" width="1000"]]
2057 +[[image:thingseye-io-step-2.png]]
2055 2055  
2056 2056  
2057 2057  **Uplink data converter:**
... ... @@ -2062,7 +2062,7 @@
2062 2062  * 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]].
2063 2063  * Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
2064 2064  
2065 -[[image:thingseye-io-step-3.png||height="625" width="1000"]]
2068 +[[image:thingseye-io-step-3.png]]
2066 2066  
2067 2067  
2068 2068  **Downlink data converter (this is an optional step):**
... ... @@ -2073,7 +2073,7 @@
2073 2073  * 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]].
2074 2074  * Click the **Next** button. You will be navigated to the **Connection** tab.
2075 2075  
2076 -[[image:thingseye-io-step-4.png||height="625" width="1000"]]
2079 +[[image:thingseye-io-step-4.png]]
2077 2077  
2078 2078  
2079 2079  **Connection:**
... ... @@ -2088,20 +2088,21 @@
2088 2088  
2089 2089  * Click the **Add** button.
2090 2090  
2091 -[[image:thingseye-io-step-5.png||height="625" width="1000"]]
2094 +[[image:thingseye-io-step-5.png]]
2092 2092  
2093 2093  
2094 2094  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.
2095 2095  
2096 2096  
2097 -[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
2100 +[[image:thingseye.io_integrationsCenter_integrations.png]]
2098 2098  
2099 2099  
2100 2100  ==== 3.5.2.1 Viewing integration details ====
2101 2101  
2105 +
2102 2102  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.
2103 2103  
2104 -[[image:integration-details.png||height="686" width="1000"]]
2108 +[[image:integration-details.png]]
2105 2105  
2106 2106  
2107 2107  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.
... ... @@ -2110,37 +2110,45 @@
2110 2110  See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
2111 2111  {{/info}}
2112 2112  
2113 -==== **3.5.2.2 Viewing events** ====
2114 2114  
2118 +==== 3.5.2.2 Viewing events ====
2119 +
2120 +
2115 2115  The **Events **tab displays all the uplink messages from the LT-22222-L.
2116 2116  
2117 2117  * Select **Debug **from the **Event type** dropdown.
2118 2118  * Select the** time frame** from the **time window**.
2119 2119  
2120 -[[image:thingseye-events.png||height="686" width="1000"]]
2126 +[[image:thingseye-events.png]]
2121 2121  
2122 2122  
2123 -* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
2129 +* To view the **JSON payload** of a message, click on the **three dots (...)** in the **Message** column of the desired message.
2124 2124  
2125 -[[image:thingseye-json.png||width="1000"]]
2131 +[[image:thingseye-json.png]]
2126 2126  
2127 2127  
2128 -==== **3.5.2.3 Deleting an integration** ====
2134 +==== 3.5.2.3 Deleting an integration ====
2129 2129  
2136 +
2130 2130  If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
2131 2131  
2132 2132  
2133 -==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
2140 +==== 3.5.2.4 Viewing sensor data on a dashboard ====
2134 2134  
2135 -This will be added soon.
2136 2136  
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.
2137 2137  
2145 +
2146 +
2147 +[[image:lt-22222-l-dashboard.png]]
2148 +
2149 +
2138 2138  == 3.6 Interface Details ==
2139 2139  
2140 2140  === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
2141 2141  
2142 2142  
2143 -Supports NPN-type sensors.
2155 +Supports** NPN-type **sensors.
2144 2144  
2145 2145  [[image:1653356991268-289.png]]
2146 2146  
... ... @@ -2262,15 +2262,15 @@
2262 2262  )))
2263 2263  
2264 2264  
2265 -(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
2277 +(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor
2266 2266  
2267 -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.
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.
2268 2268  
2269 -To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram.
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.
2270 2270  
2271 2271  [[image:image-20230616235145-1.png]]
2272 2272  
2273 -(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
2285 +(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector
2274 2274  
2275 2275  [[image:image-20240219115718-1.png]]
2276 2276  
... ... @@ -2346,20 +2346,21 @@
2346 2346  [[image:image-20220524100215-10.png||height="382" width="723"]]
2347 2347  
2348 2348  
2349 -== 3.7 LEDs Indicators ==
2361 +== 3.7 LED Indicators ==
2350 2350  
2351 -The table below lists the behavior of LED indicators for each port function.
2352 2352  
2364 +The table below lists the behaviour of LED indicators for each port function.
2365 +
2353 2353  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
2354 2354  |(% style="background-color:#4f81bd; color:white; width:50px" %)**LEDs**|(% style="background-color:#4f81bd; color:white; width:460px" %)**Feature**
2355 2355  |**PWR**|Always on when there is power
2356 2356  |**TX**|(((
2357 2357  (((
2358 -Device boot: TX blinks 5 times.
2371 +Device booting: TX blinks 5 times.
2359 2359  )))
2360 2360  
2361 2361  (((
2362 -Successful network join: TX remains ON for 5 seconds.
2375 +Successful network joins: TX remains ON for 5 seconds.
2363 2363  )))
2364 2364  
2365 2365  (((
... ... @@ -2380,18 +2380,22 @@
2380 2380  
2381 2381  = 4. Using AT Commands =
2382 2382  
2396 +
2383 2383  The LT-22222-L supports programming using AT Commands.
2384 2384  
2399 +
2385 2385  == 4.1 Connecting the LT-22222-L to a PC ==
2386 2386  
2402 +
2387 2387  (((
2388 -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.
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.
2389 2389  
2390 -[[image:usb-ttl-programming.png]]
2406 +[[image:usb-ttl-audio-jack-connection.jpg]]
2407 +
2408 +
2391 2391  )))
2392 2392  
2393 2393  
2394 -
2395 2395  (((
2396 2396  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:
2397 2397  )))
... ... @@ -2402,7 +2402,10 @@
2402 2402  (((
2403 2403  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/]]
2404 2404  
2422 +
2405 2405  == 4.2 LT-22222-L related AT commands ==
2424 +
2425 +
2406 2406  )))
2407 2407  
2408 2408  (((
... ... @@ -2421,39 +2421,39 @@
2421 2421  * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
2422 2422  * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
2423 2423  * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
2424 -* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2425 -* AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
2426 -* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2427 -* AT+PNM: Get or set the public network mode. (0: off, 1: on)
2428 -* AT+RX2FQ: Get or set the Rx2 window frequency
2429 -* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2430 -* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2431 -* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2432 -* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2433 -* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2434 -* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2435 -* AT+NWKID: Get or set the Network ID
2436 -* AT+FCU: Get or set the Frame Counter Uplink (FCntUp)
2437 -* AT+FCD: Get or set the Frame Counter Downlink (FCntDown)
2438 -* AT+CLASS: Get or set the Device Class
2439 -* AT+JOIN: Join network
2440 -* AT+NJS: Get OTAA Join Status
2441 -* AT+SENDB: Send hexadecimal data along with the application port
2442 -* AT+SEND: Send text data along with the application port
2443 -* AT+RECVB: Print last received data in binary format (with hexadecimal values)
2444 -* AT+RECV: Print last received data in raw format
2445 -* AT+VER: Get current image version and Frequency Band
2446 -* AT+CFM: Get or Set the confirmation mode (0-1)
2447 -* AT+CFS: Get confirmation status of the last AT+SEND (0-1)
2448 -* AT+SNR: Get the SNR of the last received packet
2449 -* AT+RSSI: Get the RSSI of the last received packet
2450 -* AT+TDC: Get or set the application data transmission interval in ms
2451 -* AT+PORT: Get or set the application port
2452 -* AT+DISAT: Disable AT commands
2453 -* AT+PWORD: Set password, max 9 digits
2454 -* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2455 -* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470
2456 -* AT+CFG: Print all settings
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 the last received data in binary format (with hexadecimal values)
2464 +* ##**AT+RECV**##: Print the last received data in raw format
2465 +* ##**AT+VER**##: Get the 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
2457 2457  )))
2458 2458  
2459 2459  
... ... @@ -2470,7 +2470,7 @@
2470 2470  )))
2471 2471  
2472 2472  (((
2473 -(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**##
2493 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT command access**##
2474 2474  )))
2475 2475  
2476 2476  (((
... ... @@ -2478,7 +2478,7 @@
2478 2478  )))
2479 2479  
2480 2480  (((
2481 -(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**##
2501 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT command access**##
2482 2482  )))
2483 2483  
2484 2484  (((
... ... @@ -2509,7 +2509,7 @@
2509 2509  
2510 2510  
2511 2511  (((
2512 -(% style="background-color:#dcdcdc" %)**123456**(%%)  ~/~/ Enter password to enable AT commands access
2532 +(% style="background-color:#dcdcdc" %)**123456**(%%)  ~/~/ Enter the password to enable AT commands access
2513 2513  )))
2514 2514  )))
2515 2515  
... ... @@ -2518,7 +2518,7 @@
2518 2518  )))
2519 2519  
2520 2520  (((
2521 -(% style="background-color:#dcdcdc" %)** 123456**(%%)  ~/~/ Enter password to enable AT commands access
2541 +(% style="background-color:#dcdcdc" %)** 123456**(%%)  ~/~/ Enter the password to enable AT command access
2522 2522  )))
2523 2523  
2524 2524  (((
... ... @@ -2599,16 +2599,19 @@
2599 2599  
2600 2600  == 5.1 Counting how many objects pass through the flow line ==
2601 2601  
2602 -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]]?
2603 2603  
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]].
2604 2604  
2625 +
2605 2605  = 6. FAQ =
2606 2606  
2628 +
2607 2607  This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
2608 2608  
2609 2609  
2610 2610  == 6.1 How to update the firmware? ==
2611 2611  
2634 +
2612 2612  Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to:
2613 2613  
2614 2614  * Support new features
... ... @@ -2618,7 +2618,7 @@
2618 2618  You will need the following things before proceeding:
2619 2619  
2620 2620  * 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
2621 -* USB to TTL adapter
2644 +* USB to TTL adapter/converter
2622 2622  * 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)
2623 2623  * 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.
2624 2624  
... ... @@ -2628,7 +2628,7 @@
2628 2628  
2629 2629  Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2630 2630  
2631 -[[image:usb-ttl-programming.png]]
2654 +[[image:usb-ttl-audio-jack-connection.jpg]]
2632 2632  
2633 2633  
2634 2634  
... ... @@ -2661,17 +2661,21 @@
2661 2661  (((
2662 2662  (((
2663 2663  == 6.2 How to change the LoRaWAN frequency band/region? ==
2687 +
2688 +
2664 2664  )))
2665 2665  )))
2666 2666  
2667 2667  (((
2668 -You can follow the introductions on [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloading, select the required image file.
2693 +You can follow the introductions on [[how to upgrade the image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloading, select the required image file.
2669 2669  )))
2670 2670  
2671 2671  (((
2672 2672  
2673 2673  
2674 -== 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
2699 +== 6.3 How to set up LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
2700 +
2701 +
2675 2675  )))
2676 2676  
2677 2677  (((
... ... @@ -2745,11 +2745,13 @@
2745 2745  
2746 2746  == 6.4 How to change the uplink interval? ==
2747 2747  
2775 +
2748 2748  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/]]
2749 2749  
2750 2750  
2751 2751  == 6.5 Can I see the counting event in the serial output? ==
2752 2752  
2781 +
2753 2753  (((
2754 2754  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.
2755 2755  
... ... @@ -2756,6 +2756,7 @@
2756 2756  
2757 2757  == 6.6 Can I use point-to-point communication with LT-22222-L? ==
2758 2758  
2788 +
2759 2759  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]].
2760 2760  
2761 2761  
... ... @@ -2764,13 +2764,15 @@
2764 2764  (((
2765 2765  == 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
2766 2766  
2797 +
2767 2767  * If the device is not properly shut down and is directly powered off.
2768 2768  * It will default to a power-off state.
2769 2769  * In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
2770 -* After a restart, the status before the power failure will be read from flash.
2801 +* After a restart, the status before the power failure will be read from Flash.
2771 2771  
2772 -== 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
2803 +== 6.8 Can I set up LT-22222-L as an NC (Normally Closed) relay? ==
2773 2773  
2805 +
2774 2774  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:
2775 2775  
2776 2776  
... ... @@ -2779,16 +2779,19 @@
2779 2779  
2780 2780  == 6.9 Can the LT-22222-L save the RO state? ==
2781 2781  
2814 +
2782 2782  To enable this feature, the firmware version must be 1.6.0 or higher.
2783 2783  
2784 2784  
2785 2785  == 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
2786 2786  
2820 +
2787 2787  It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
2788 2788  
2789 2789  
2790 2790  = 7. Troubleshooting =
2791 2791  
2826 +
2792 2792  This section provides some known troubleshooting tips.
2793 2793  
2794 2794  
... ... @@ -2797,6 +2797,8 @@
2797 2797  (((
2798 2798  (((
2799 2799  == 7.1 Downlink isn't working. How can I solve this? ==
2835 +
2836 +
2800 2800  )))
2801 2801  )))
2802 2802  
... ... @@ -2808,6 +2808,8 @@
2808 2808  
2809 2809  
2810 2810  == 7.2 Having trouble uploading an image? ==
2848 +
2849 +
2811 2811  )))
2812 2812  
2813 2813  (((
... ... @@ -2818,6 +2818,8 @@
2818 2818  
2819 2819  
2820 2820  == 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
2860 +
2861 +
2821 2821  )))
2822 2822  
2823 2823  (((
... ... @@ -2827,6 +2827,7 @@
2827 2827  
2828 2828  == 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? ==
2829 2829  
2871 +
2830 2830  The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
2831 2831  Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2832 2832  
... ... @@ -2833,6 +2833,7 @@
2833 2833  
2834 2834  = 8. Ordering information =
2835 2835  
2878 +
2836 2836  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
2837 2837  
2838 2838  (% style="color:#4f81bd" %)**XXX:**
... ... @@ -2849,6 +2849,7 @@
2849 2849  
2850 2850  = 9. Package information =
2851 2851  
2895 +
2852 2852  **Package includes**:
2853 2853  
2854 2854  * 1 x LT-22222-L I/O Controller
... ... @@ -2865,6 +2865,7 @@
2865 2865  
2866 2866  = 10. Support =
2867 2867  
2912 +
2868 2868  * (((
2869 2869  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.
2870 2870  )))
... ... @@ -2876,6 +2876,7 @@
2876 2876  
2877 2877  = 11. Reference​​​​​ =
2878 2878  
2924 +
2879 2879  * 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]]
2880 2880  * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]]
2881 2881  * [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]
Screenshot 2024-11-23 at 18.27.11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +143.4 KB
Content
Screenshot 2024-12-08 193946.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +32.4 KB
Content
lt-22222-l-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