Last modified by Saxer Lin on 2025/04/15 17:24
<
From version < 163.1 >
edited by Dilisi S
on 2024/11/06 04:29
To version < 179.1 >
edited by Dilisi S
on 2024/11/09 05:29
>
Change comment: Nov 8 edit FAQ and Troubleshooting sections

Summary

Details

Page properties
Content
... ... @@ -33,14 +33,12 @@
33 33  With the LT-22222-L I/O Controller, users can transmit data over ultra-long distances with low power consumption using LoRa, a spread-spectrum modulation technique derived from chirp spread spectrum (CSS) technology that operates on license-free ISM bands.
34 34  )))
35 35  
36 -> The LT Series I/O Controllers are designed for easy, low-cost installation on LoRaWAN networks.
37 -
38 38  (((
39 39  You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways:
40 40  
41 41  * If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Network), you can select a network and register the LT-22222-L I/O controller with it.
42 42  * If there is no public LoRaWAN coverage in your area, you can set up a LoRaWAN gateway, or multiple gateways, and connect them to a LoRaWAN network server to create adequate coverage. Then, register the LT-22222-L I/O controller with this network.
43 -* Set up your own private LoRaWAN network.
41 +* Setup your own private LoRaWAN network.
44 44  
45 45  > You can use a LoRaWAN gateway, such as the Dragino LG308, to expand or create LoRaWAN coverage in your area.
46 46  )))
... ... @@ -59,7 +59,7 @@
59 59  * SX1276/78 Wireless Chip 
60 60  * Power Consumption:
61 61  ** Idle: 4mA@12v
62 -** 20dB Transmit: 34mA@12v
60 +** 20dB Transmit: 34mA@12V
63 63  * Operating Temperature: -40 ~~ 85 Degrees, No Dew
64 64  
65 65  (% style="color:#037691" %)**Interface for Model: LT22222-L:**
... ... @@ -68,7 +68,7 @@
68 68  * 2 x Digital Output (NPN output. Max pull-up voltage 36V,450mA)
69 69  * 2 x Relay Output (5A@250VAC / 30VDC)
70 70  * 2 x 0~~20mA Analog Input (res:0.01mA)
71 -* 2 x 0~~30V Analog Input (res:0.01v)
69 +* 2 x 0~~30V Analog Input (res:0.01V)
72 72  * Power Input 7~~ 24V DC. 
73 73  
74 74  (% style="color:#037691" %)**LoRa Spec:**
... ... @@ -136,10 +136,10 @@
136 136  
137 137  * 1 x LT-22222-L I/O Controller
138 138  * 1 x LoRaWAN antenna matched to the frequency of the LT-22222-L
139 -* 1 x bracket for wall mounting
137 +* 1 x bracket for DIN rail mounting
140 140  * 1 x programming cable
141 141  
142 -Attach the LoRaWAN antenna to the antenna connector, ANT,** **located on the top right side of the device, next to the upper terminal block. Secure the antenna by tightening it clockwise.
140 +Attach the LoRaWAN antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper terminal block. Secure the antenna by tightening it clockwise.
143 143  
144 144  == 2.2 Terminals ==
145 145  
... ... @@ -169,9 +169,9 @@
169 169  |(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
170 170  |(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
171 171  
172 -== 2.3 Powering the LT-22222-L  ==
170 +== 2.3 Powering the LT-22222-L ==
173 173  
174 -The LT-22222-L I/O Controller can be powered by a 7–24V DC power source. Connect the 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.
172 +The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect the 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  
177 177  [[image:1653297104069-180.png]]
... ... @@ -183,13 +183,13 @@
183 183  
184 184  By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode. It supports OTAA (Over-the-Air Activation), the most secure method for activating a device with a LoRaWAN network server. The LT-22222-L comes with device registration information that allows you to register it with a LoRaWAN network, enabling the device to perform OTAA activation with the network server upon initial power-up and after any subsequent reboots.
185 185  
186 -For LT-22222-L, the LED will show the Join status: After powering on, the TX LED will fast-blink 5 times which means the LT-22222-L will enter the working mode and start to JOIN the LoRaWAN network. The TX LED will be on for 5 seconds after joining the network. When there is a message from the server, the RX LED will be on for 1 second. 
184 +After powering on, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** the LoRaWAN network. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LE**D will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status.
187 187  
188 188  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.
189 189  
190 190  == 3.2 Registering with a LoRaWAN network server ==
191 191  
192 -The diagram below shows how the LT-22222-L connects to a typical LoRaWAN network.
190 +The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
193 193  
194 194  [[image:image-20220523172350-1.png||height="266" width="864"]]
195 195  
... ... @@ -207,8 +207,10 @@
207 207  * Create an application if you do not have one yet.
208 208  * Register LT-22222-L with that application. Two registration options are available:
209 209  
210 -==== Using the LoRaWAN Device Repository: ====
208 +==== ====
211 211  
210 +==== 3.2.2.1 Using the LoRaWAN Device Repository ====
211 +
212 212  * Go to your application and click on the **Register end device** button.
213 213  * On the **Register end device** page:
214 214  ** Select the option **Select the end device in the LoRaWAN Device Repository**.
... ... @@ -217,7 +217,8 @@
217 217  
218 218  [[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
219 219  
220 -*
220 +
221 +* Page continued...
221 221  ** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
222 222  ** Enter the **DevEUI** in the **DevEUI** field.
223 223  ** Enter the **AppKey** in the **AppKey** field.
... ... @@ -226,8 +226,10 @@
226 226  
227 227  [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
228 228  
229 -==== Entering device information manually: ====
230 +==== ====
230 230  
232 +==== 3.2.2.2 Entering device information manually ====
233 +
231 231  * On the **Register end device** page:
232 232  ** Select the **Enter end device specifies manually** option as the input method.
233 233  ** Select the **Frequency plan** that matches your device.
... ... @@ -240,29 +240,52 @@
240 240  [[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
241 241  
242 242  
243 -* Enter **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
244 -* Enter **DevEUI** in the **DevEUI** field.
245 -* Enter **AppKey** in the **AppKey** field.
246 -* In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
247 -* Under **After registration**, select the **View registered end device** option.
246 +* Page continued...
247 +** Enter **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
248 +** Enter **DevEUI** in the **DevEUI** field.
249 +** Enter **AppKey** in the **AppKey** field.
250 +** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
251 +** Under **After registration**, select the **View registered end device** option.
252 +** Click the **Register end device** button.
248 248  
249 249  [[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
250 250  
251 251  
252 -==== Joining ====
257 +You will be navigated to the **Device overview** page.
253 253  
254 -Click on **Live Data** in the left navigation. Then, power on the device, and it will join The Things Stack Sandbox. You can see the join request, join accept, followed by uplink messages form the device showing in the Live Data panel.
255 255  
256 -[[image:1653298044601-602.png||height="405" width="709"]]
260 +[[image:lt-22222-device-overview.png||height="625" width="1000"]]
257 257  
258 258  
259 -== 3.3 Uplink Payload formats ==
263 +==== 3.2.2.3 Joining ====
260 260  
265 +Click on **Live data** in the left navigation. The Live data panel for your application will display.
261 261  
262 -The LT-22222-L has 5 working modes. It also has an interrupt/trigger mode for different types of applications that can be used together with any working mode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands.
267 +Power on your LT-22222-L. It will begin joining The Things Stack LoRaWAN network server. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server. Once successfully joined, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**).
263 263  
264 -* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2 x ACI + 2AVI + DI + DO + RO
265 265  
270 +[[image:lt-22222-join-network.png||height="625" width="1000"]]
271 +
272 +
273 +By default, you will receive an uplink data message every 10 minutes.
274 +
275 +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.
276 +
277 +[[image:lt-22222-ul-payload-decoded.png]]
278 +
279 +
280 +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 **End devices** > **LT-22222-L** > **Payload formatters** > **Uplink**. Then  select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
281 +
282 +[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
283 +
284 +
285 +== 3.3 Work Modes and their Uplink Payload formats ==
286 +
287 +
288 +The LT-22222-L has 5 **work modes**. It also has an interrupt/trigger mode for different types of applications that can be used together with any work mode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands.
289 +
290 +* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO
291 +
266 266  * (% style="color:blue" %)**MOD2**(%%): Double DI Counting + DO + RO
267 267  
268 268  * (% style="color:blue" %)**MOD3**(%%): Single DI Counting + 2 x ACI + DO + RO
... ... @@ -273,12 +273,15 @@
273 273  
274 274  * (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5
275 275  
302 +The uplink messages are sent over LoRaWAN FPort 2. By default, an uplink message is sent every 10 minutes.
303 +
276 276  === 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
277 277  
278 -
279 279  (((
280 -The uplink payload is 11 bytes long. Uplink packets are sent over LoRaWAN FPort=2. By default, one uplink is sent every 10 minutes. (% style="display:none" wfd-invisible="true" %)
307 +This is the default mode.
281 281  
309 +The uplink payload is 11 bytes long. (% style="display:none" wfd-invisible="true" %)
310 +
282 282  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
283 283  |(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**
284 284  |Value|(((
... ... @@ -289,13 +289,13 @@
289 289  ACI1 Current
290 290  )))|(((
291 291  ACI2 Current
292 -)))|DIDORO*|(((
321 +)))|**DIDORO***|(((
293 293  Reserve
294 294  )))|MOD
295 295  )))
296 296  
297 297  (((
298 -(% style="color:#4f81bd" %)*** DIDORO**(%%) is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below.
327 +(% style="color:#4f81bd" %)*** DIDORO**(%%) is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, and its size is1 byte long as shown below.
299 299  
300 300  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
301 301  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
... ... @@ -302,9 +302,9 @@
302 302  |RO1|RO2|--DI3--|DI2|DI1|--DO3--|DO2|DO1
303 303  )))
304 304  
305 -* RO is for the relay. ROx=1: closed, ROx=0 always open.
306 -* DI is for digital input. DIx=1: high or floating, DIx=0: low.
307 -* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.
334 +* RO is for the relay. ROx=1: CLOSED, ROx=0 always OPEN.
335 +* DI is for digital input. DIx=1: HIGH or FLOATING, DIx=0: LOW.
336 +* DO is for reverse digital output. DOx=1: LOW, DOx=0: HIGH or FLOATING.
308 308  
309 309  (% style="color:red" %)**Note: DI3 and DO3 bits are not valid for LT-22222-L**
310 310  
... ... @@ -325,13 +325,13 @@
325 325  
326 326  * [1] The RO1 relay channel is CLOSED, and the RO1 LED is ON.
327 327  * [0] The RO2 relay channel is OPEN, and the RO2 LED is OFF.
328 -* [1] DI3 - not used for LT-22222-L.
357 +* **[1] DI3 - not used for LT-22222-L.**
329 329  * [0] DI2 channel input is LOW, and the DI2 LED is OFF.
330 330  * [1] DI1 channel input state:
331 331  ** DI1 is FLOATING when no sensor is connected between DI1+ and DI1-.
332 332  ** DI1 is HIGH when a sensor is connected between DI1- and DI1+ and the sensor is ACTIVE.
333 333  ** DI1 LED is ON in both cases.
334 -* [0] DO3 - not used for LT-22222-L.
363 +* **[0] DO3 - not used for LT-22222-L.**
335 335  * [1] DO2 channel output is LOW, and the DO2 LED is ON.
336 336  * [0] DO1 channel output state:
337 337  ** DO1 is FLOATING when there is no load between DO1 and V+.
... ... @@ -342,7 +342,7 @@
342 342  
343 343  
344 344  (((
345 -**For LT-22222-L**: In this mode, the **DI1 and DI2** are used as counting pins.
374 +**For LT-22222-L**: In this mode, **DI1 and DI2** are used as counting pins.
346 346  )))
347 347  
348 348  (((
... ... @@ -356,17 +356,17 @@
356 356  )))
357 357  
358 358  (((
359 -(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, DO3, DO2 and DO1, for a total of 1 byte, as shown below.
388 +(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, FIRST, Reserve, Reserve, DO3, DO2 and DO1, and its size is 1 byte long as shown below.
360 360  
361 361  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
362 362  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
363 363  |RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1
364 364  
365 -* RO is for the relay. ROx=1: closed, ROx=0 always open.
394 +* RO is for the relay. ROx=1: CLOSED, ROx=0 always OPEN.
366 366  )))
367 367  
368 368  * FIRST: Indicates that this is the first packet after joining the network.
369 -* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.
398 +* DO is for reverse digital output. DOx=1: LOW, DOx=0: HIGH or FLOATING.
370 370  
371 371  (((
372 372  (% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L**
... ... @@ -593,7 +593,6 @@
593 593  1. Periodically uplink (Based on TDC time). The payload is the same as in normal mode (MOD=1 for the commands above). These are (% style="color:#4f81bd" %)**unconfirmed**(%%) uplinks.
594 594  1. Trigger uplink when the trigger condition is met. LT will send two packets in this case. The first uplink uses the payload specified in trigger mode (MOD=6). The second packet uses the normal mode payload (MOD=1 as set above). Both are (% style="color:#4f81bd" %)**CONFIRMED uplinks.**
595 595  
596 -
597 597  (% style="color:#037691" %)**AT Command to set Trigger Condition**:
598 598  
599 599  (% style="color:#4f81bd" %)**Trigger based on voltage**:
... ... @@ -603,9 +603,9 @@
603 603  
604 604  **Example:**
605 605  
606 -AT+AVLIM=3000,6000,0,2000   (If AVI1 voltage lower than 3v or higher than 6v. or AV2 voltage is higher than 2v, LT will trigger Uplink)
634 +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)
607 607  
608 -AT+AVLIM=5000,0,0,0   (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore)
636 +AT+AVLIM=5000,0,0,0   (triggers an uplink if AVI1 voltage lower than 5V. Use 0 for parameters that are not in use)
609 609  
610 610  
611 611  (% style="color:#4f81bd" %)**Trigger based on current**:
... ... @@ -615,12 +615,12 @@
615 615  
616 616  **Example:**
617 617  
618 -AT+ACLIM=10000,15000,0,0   (If ACI1 voltage lower than 10mA or higher than 15mA, trigger an uplink)
646 +AT+ACLIM=10000,15000,0,0   (triggers an uplink if ACI1 voltage is lower than 10mA or higher than 15mA)
619 619  
620 620  
621 -(% style="color:#4f81bd" %)**Trigger base on DI status**:
649 +(% style="color:#4f81bd" %)**Trigger based on DI status**:
622 622  
623 -DI status trigger Flag.
651 +DI status triggers Flag.
624 624  
625 625  Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >
626 626  
... ... @@ -630,39 +630,38 @@
630 630  AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
631 631  
632 632  
633 -(% style="color:#037691" %)**Downlink Command to set Trigger Condition:**
661 +(% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
634 634  
635 635  Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
636 636  
637 637  Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
638 638  
639 - AA: Code for this downlink Command:
667 + AA: Type Code for this downlink Command:
640 640  
641 - xx: 0: Limit for AV1 and AV2;  1: limit for AC1 and AC2 ; 2 DI1, DI2 trigger enable/disable
669 + xx: **0**: Limit for AV1 and AV2; **1**: limit for AC1 and AC2; **2**: DI1and DI2 trigger enable/disable.
642 642  
643 - yy1 yy1: AC1 or AV1 low limit or DI1/DI2 trigger status.
671 + yy1 yy1: AC1 or AV1 LOW limit or DI1/DI2 trigger status.
644 644  
645 - yy2 yy2: AC1 or AV1 high limit.
673 + yy2 yy2: AC1 or AV1 HIGH limit.
646 646  
647 - yy3 yy3: AC2 or AV2 low limit.
675 + yy3 yy3: AC2 or AV2 LOW limit.
648 648  
649 - Yy4 yy4: AC2 or AV2 high limit.
677 + Yy4 yy4: AC2 or AV2 HIGH limit.
650 650  
651 651  
652 -**Example1**: AA 00 13 88 00 00 00 00 00 00
680 +**Example 1**: AA 00 13 88 00 00 00 00 00 00
653 653  
654 -Same as AT+AVLIM=5000,0,0,0   (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore)
682 +Same as AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage is lower than 5V. Use 0s for parameters that are not in use)
655 655  
656 656  
657 -**Example2**: AA 02 01 00
685 +**Example 2**: AA 02 01 00
658 658  
659 -Same as AT+ DTRI =1,0  (Enable DI1 trigger / disable DI2 trigger)
687 +Same as AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
660 660  
661 661  
662 -
663 663  (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:**
664 664  
665 -MOD6 Payload : total 11 bytes payload
692 +MOD6 Payload: total of 11 bytes
666 666  
667 667  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
668 668  |(% 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**
... ... @@ -676,10 +676,10 @@
676 676  MOD(6)
677 677  )))
678 678  
679 -(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if trigger is set for this part. Totally 1byte as below
706 +(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
680 680  
681 681  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
682 -|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
709 +|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
683 683  |(((
684 684  AV1_LOW
685 685  )))|(((
... ... @@ -698,17 +698,17 @@
698 698  AC2_HIGH
699 699  )))
700 700  
701 -* Each bits shows if the corresponding trigger has been configured.
728 +* Each bit shows if the corresponding trigger has been configured.
702 702  
703 703  **Example:**
704 704  
705 -10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW
732 +10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW
706 706  
707 707  
708 -(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1byte as below
735 +(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
709 709  
710 710  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
711 -|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
738 +|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
712 712  |(((
713 713  AV1_LOW
714 714  )))|(((
... ... @@ -727,11 +727,11 @@
727 727  AC2_HIGH
728 728  )))
729 729  
730 -* Each bits shows which status has been trigger on this uplink.
757 +* Each bit shows which status has been triggered on this uplink.
731 731  
732 732  **Example:**
733 733  
734 -10000000: Means this packet is trigger by AC1_LOW. Means voltage too low.
761 +10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.
735 735  
736 736  
737 737  (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
... ... @@ -740,7 +740,7 @@
740 740  |**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
741 741  |N/A|N/A|N/A|N/A|DI2_STATUS|DI2_FLAG|DI1_STATUS|DI1_FLAG
742 742  
743 -* Each bits shows which status has been trigger on this uplink.
770 +* Each bits shows which status has been triggered on this uplink.
744 744  
745 745  **Example:**
746 746  
... ... @@ -767,11 +767,11 @@
767 767  )))
768 768  
769 769  
770 -== 3.4 ​Configure LT via AT or Downlink ==
797 +== 3.4 ​Configure LT via AT Commands or Downlinks ==
771 771  
772 772  
773 773  (((
774 -User can configure LT I/O Controller via AT Commands or LoRaWAN Downlink Commands
801 +User can configure LT I/O Controller via AT Commands or LoRaWAN Downlinks.
775 775  )))
776 776  
777 777  (((
... ... @@ -786,9 +786,8 @@
786 786  
787 787  === 3.4.1 Common Commands ===
788 788  
789 -
790 790  (((
791 -They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.5.4, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
817 +These commands should be available for all Dragino sensors, 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]].
792 792  )))
793 793  
794 794  
... ... @@ -796,34 +796,37 @@
796 796  
797 797  ==== 3.4.2.1 Set Transmit Interval ====
798 798  
825 +Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
799 799  
800 -Set device uplink interval.
827 +* (% style="color:#037691" %)**AT command:**
801 801  
802 -* (% style="color:#037691" %)**AT Command:**
829 +(% style="color:blue" %)**AT+TDC=N**
803 803  
804 -(% style="color:blue" %)**AT+TDC=N **
831 +where N is the time in milliseconds.
805 805  
833 +**Example: **AT+TDC=30000. This will set the uplink interval to 30 seconds
806 806  
807 -**Example: **AT+TDC=30000. Means set interval to 30 seconds
808 808  
836 +* (% style="color:#037691" %)**Downlink payload (prefix 0x01):**
809 809  
810 -* (% style="color:#037691" %)**Downlink Payload (prefix 0x01):**
811 -
812 812  (% style="color:blue" %)**0x01 aa bb cc  **(%%)** ~/~/ Same as AT+TDC=0x(aa bb cc)**
813 813  
814 814  
815 815  
816 -==== 3.4.2.2 Set Work Mode (AT+MOD) ====
842 +==== 3.4.2.2 Set the Work Mode (AT+MOD) ====
817 817  
818 818  
819 -Set work mode.
845 +Sets the work mode.
820 820  
821 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+MOD=N  **
847 +* (% style="color:#037691" %)**AT command:**(%%) (% style="color:blue" %)**AT+MOD=N  **
822 822  
823 -**Example**: AT+MOD=2. Set work mode to Double DI counting mode
849 +Where N is the work mode.
824 824  
825 -* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A):**
851 +**Example**: AT+MOD=2. This will set the work mode to Double DI counting mode.
826 826  
853 +
854 +* (% style="color:#037691" %)**Downlink payload (prefix 0x0A):**
855 +
827 827  (% style="color:blue" %)**0x0A aa  **(%%)** ** ~/~/ Same as AT+MOD=aa
828 828  
829 829  
... ... @@ -831,10 +831,12 @@
831 831  ==== 3.4.2.3 Poll an uplink ====
832 832  
833 833  
834 -* (% style="color:#037691" %)**AT Command:**(%%) There is no AT Command to poll uplink
863 +Asks the device to send an uplink.
835 835  
836 -* (% style="color:#037691" %)**Downlink Payload (prefix 0x08):**
865 +* (% style="color:#037691" %)**AT command:**(%%) There is no AT Command to poll uplink
837 837  
867 +* (% style="color:#037691" %)**Downlink payload (prefix 0x08):**
868 +
838 838  (% style="color:blue" %)**0x08 FF  **(%%)** **~/~/ Poll an uplink
839 839  
840 840  **Example**: 0x08FF, ask device to send an Uplink
... ... @@ -841,16 +841,16 @@
841 841  
842 842  
843 843  
844 -==== 3.4.2.4 Enable Trigger Mode ====
875 +==== 3.4.2.4 Enable/Disable Trigger Mode ====
845 845  
846 846  
847 -Use of trigger mode, please check [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
878 +Enable or disable the trigger mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
848 848  
849 849  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0**
850 850  
851 -(% style="color:red" %)**1:** (%%)Enable Trigger Mode
882 +(% style="color:red" %)**1:** (%%)Enable the trigger mode
852 852  
853 -(% style="color:red" %)**0: **(%%)Disable Trigger Mode
884 +(% style="color:red" %)**0: **(%%)Disable the trigger mode
854 854  
855 855  
856 856  * (% style="color:#037691" %)**Downlink Payload (prefix 0x0A 06):**
... ... @@ -862,7 +862,7 @@
862 862  ==== 3.4.2.5 Poll trigger settings ====
863 863  
864 864  
865 -Poll trigger settings
896 +Polls the trigger settings
866 866  
867 867  * (% style="color:#037691" %)**AT Command:**
868 868  
... ... @@ -870,7 +870,7 @@
870 870  
871 871  * (% style="color:#037691" %)**Downlink Payload (prefix 0x AB 06):**
872 872  
873 -(% style="color:blue" %)**0xAB 06  ** (%%) ~/~/ Poll trigger settings, device will uplink trigger settings once receive this command
904 +(% style="color:blue" %)**0xAB 06  ** (%%) ~/~/ Poll the trigger settings. Device will uplink trigger settings once receive this command
874 874  
875 875  
876 876  
... ... @@ -877,11 +877,11 @@
877 877  ==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ====
878 878  
879 879  
880 -Enable Disable DI1/DI2/DI2 as trigger,
911 +Enable or Disable DI1/DI2/DI2 as trigger,
881 881  
882 882  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
883 883  
884 -**Example:** AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
915 +**Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
885 885  
886 886  
887 887  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 02):**
... ... @@ -913,15 +913,15 @@
913 913  ==== 3.4.2.8 Trigger2 – Set DI2 as trigger ====
914 914  
915 915  
916 -Set DI2 trigger.
947 +Sets DI2 trigger.
917 917  
918 918  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b**
919 919  
920 -(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
951 +(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
921 921  
922 922  (% style="color:red" %)**b :** (%%)delay timing.
923 923  
924 -**Example:** AT+TRIG2=0,100(set DI1 port to trigger on low level, valid signal is 100ms )
955 +**Example:** AT+TRIG2=0,100 (set DI1 port to trigger on low level, valid signal is 100ms )
925 925  
926 926  
927 927  * (% style="color:#037691" %)**Downlink Payload (prefix 0x09 02 ):**
... ... @@ -959,7 +959,7 @@
959 959  ==== 3.4.2.11 Trigger – Set minimum interval ====
960 960  
961 961  
962 -Set AV and AC trigger minimum interval, system won't response to the second trigger within this set time after the first trigger.
993 +Sets AV and AC trigger minimum interval. Device won't response to the second trigger within this set time after the first trigger.
963 963  
964 964  * (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+ATDC=5        ** ~/~/ (%%)Device won't response the second trigger within 5 minute after the first trigger.
965 965  
... ... @@ -1107,7 +1107,7 @@
1107 1107  )))
1108 1108  
1109 1109  (((
1110 -00: Close ,  01: Open , 11: No action
1141 +00: Closed ,  01: Open , 11: No action
1111 1111  
1112 1112  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %)
1113 1113  |(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**RO1**|(% style="background-color:#4f81bd; color:white" %)**RO2**
... ... @@ -1229,7 +1229,7 @@
1229 1229  
1230 1230  
1231 1231  
1232 -==== 3.4.2.19 Counting ~-~- Change counting mode save time ====
1263 +==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1233 1233  
1234 1234  
1235 1235  * (% style="color:#037691" %)**AT Command:**
... ... @@ -1352,69 +1352,122 @@
1352 1352  
1353 1353  == 3.5 Integrating with ThingsEye.io ==
1354 1354  
1355 -If you are using one of The Things Stack plans, you can integrate ThingsEye.io with your application. Once integrated, ThingsEye.io works as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
1386 +The Things Stack applications can be integrated with ThingsEye.io. Once integrated, ThingsEye.io works as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
1356 1356  
1357 -=== 3.5.1 Configuring The Things Stack Sandbox ===
1388 +=== 3.5.1 Configuring MQTT Connection Information with The Things Stack Sandbox ===
1358 1358  
1359 -* Go to your Application and select MQTT under Integrations.
1360 -* In the Connection credentials section, under Username, The Thins Stack displays an auto-generated username. You can use it or provide a new one.
1361 -* For the Password, click the Generate new API key button to generate a password. You can see it by clicking on the eye button.
1390 +We use The Things Stack Sandbox for demonstating the configuration but  other
1362 1362  
1392 +* In **The Things Stack Sandbox**, select your application under **Applications**.
1393 +* Select **MQTT** under **Integrations**.
1394 +* In the **Connection information **section, for **Username**, The Things Stack displays an auto-generated username. You can use it or provide a new one.
1395 +* For the **Password**, click the **Generate new API key** button to generate a password. You can see it by clicking on the **eye** button. The API key works as the password.
1396 +
1397 +NOTE. The username and  password (API key) you created here are required in the next section.
1398 +
1363 1363  [[image:tts-mqtt-integration.png||height="625" width="1000"]]
1364 1364  
1365 1365  === 3.5.2 Configuring ThingsEye.io ===
1366 1366  
1367 -* Login to your thingsEye.io account.
1368 -* Under the Integrations center, click Integrations.
1369 -* Click the Add integration button (the button with the + symbol).
1403 +This section guides you on how to create an integration in ThingsEye to connect with The Things Stack MQTT server.
1370 1370  
1405 +* Login to your [[ThingsEye.io >>https://thingseye.io]]account.
1406 +* Under the **Integrations center**, click **Integrations**.
1407 +* Click the **Add integration** button (the button with the **+** symbol).
1408 +
1371 1371  [[image:thingseye-io-step-1.png||height="625" width="1000"]]
1372 1372  
1373 1373  
1374 -On the Add integration page configure the following:
1412 +On the **Add integration** window, configure the following:
1375 1375  
1376 -Basic settings:
1414 +**Basic settings:**
1377 1377  
1378 -* Select The Things Stack Community from the Integration type list.
1379 -* Enter a suitable name for your integration in the Name box or keep the default name.
1380 -* Click the Next button.
1416 +* Select **The Things Stack Community** from the **Integration type** list.
1417 +* Enter a suitable name for your integration in the **Name **text** **box or keep the default name.
1418 +* Ensure the following options are turned on.
1419 +** Enable integration
1420 +** Debug mode
1421 +** Allow create devices or assets
1422 +* Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
1381 1381  
1382 1382  [[image:thingseye-io-step-2.png||height="625" width="1000"]]
1383 1383  
1384 -Uplink Data converter:
1385 1385  
1386 -* Click the Create New button if it is not selected by default.
1387 -* Click the JavaScript button.
1388 -* Paste the uplink decoder function into the text area (first, delete the default code). The demo decoder function can be found here.
1389 -* Click the Next button.
1427 +**Uplink data converter:**
1390 1390  
1429 +* Click the **Create new** button if it is not selected by default.
1430 +* Enter a suitable name for the uplink data converter in the **Name **text** **box or keep the default name.
1431 +* Click the **JavaScript** button.
1432 +* 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]].
1433 +* Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
1434 +
1391 1391  [[image:thingseye-io-step-3.png||height="625" width="1000"]]
1392 1392  
1393 -Downlink Data converter (this is an optional step):
1394 1394  
1395 -* Click the Create new button if it is not selected by default.
1396 -* Click the JavaScript button.
1397 -* Paste the downlink decoder function into the text area (first, delete the default code). The demo decoder function can be found here.
1398 -* Click the Next button.
1438 +**Downlink data converter (this is an optional step):**
1399 1399  
1440 +* Click the **Create new** button if it is not selected by default.
1441 +* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name
1442 +* Click the **JavaScript** button.
1443 +* Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found here.
1444 +* Click the **Next** button. You will be navigated to the **Connection** tab.
1445 +
1400 1400  [[image:thingseye-io-step-4.png||height="625" width="1000"]]
1401 1401  
1402 -Connection:
1403 1403  
1404 -* Choose Region from the Host type.
1405 -* Enter the cluster of your The Things Stack in the Region textbox.
1406 -* Enter the Username and Password in the Credentials section. Use the same username and password you created with the MQTT page of The Things Stack.
1407 -* Click Check connection to test the connection. If the connection is successful, you can see the message saying Connected.
1408 -* Click the Add button.
1449 +**Connection:**
1409 1409  
1451 +* Choose **Region** from the **Host type**.
1452 +* Enter the **cluster** of your **The Things Stack** in the **Region** textbox. You can find the cluster in the url (e.g., https:~/~/**eu1**.cloud.thethings.network/...).
1453 +* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The username and password can be found on the MQTT integration page of your The Things Stack account (see Configuring MQTT Connection information with The Things Stack Sandbox).
1454 +* Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
1455 +
1456 +[[image:message-1.png]]
1457 +
1458 +
1459 +* Click the **Add** button.
1460 +
1410 1410  [[image:thingseye-io-step-5.png||height="625" width="1000"]]
1411 1411  
1412 1412  
1413 -Your integration is added to the integrations list and it will display on the Integrations page.
1464 +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.
1414 1414  
1415 -[[image:thingseye-io-step-6.png||height="625" width="1000"]]
1416 1416  
1467 +[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
1417 1417  
1469 +
1470 +**Viewing integration details**:
1471 +
1472 +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.
1473 +
1474 +[[image:integration-details.png||height="686" width="1000"]]
1475 +
1476 +
1477 +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.
1478 +
1479 +Note: See also ThingsEye documentation.
1480 +
1481 +
1482 +**Viewing events:**
1483 +
1484 +This tab  displays all the uplink messages from the LT-22222-L.
1485 +
1486 +* Click on the **Events **tab.
1487 +* Select **Debug **from the **Event type** dropdown.
1488 +* Select the** time frame** from the **time window**.
1489 +
1490 +[insert image]
1491 +
1492 +- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
1493 +
1494 +[insert image]
1495 +
1496 +
1497 +**Deleting the integration**:
1498 +
1499 +If you want to delete this integration, click the **Delete integratio**n button.
1500 +
1501 +
1418 1418  == 3.6 Interface Details ==
1419 1419  
1420 1420  === 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) ===
... ... @@ -1670,7 +1670,7 @@
1670 1670  
1671 1671  
1672 1672  (((
1673 -On the PC, the user needs to set the (% style="color:#4f81bd" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) to a baud rate of (% style="color:green" %)**9600**(%%) to access to access serial console of LT-22222-L. The AT commands are disabled by default, and a password (default:(% style="color:green" %)**123456**)(%%) must be entered to active them, as shown below:
1757 +On the PC, the user needs 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. The AT commands are disabled by default, and a password (default:(% style="color:green" %)**123456**)(%%) must be entered to active them, as shown below:
1674 1674  )))
1675 1675  
1676 1676  [[image:1653358355238-883.png]]
... ... @@ -2007,37 +2007,49 @@
2007 2007  
2008 2008  = 5. Case Study =
2009 2009  
2010 -== 5.1 Counting how many objects pass in Flow Line ==
2094 +== 5.1 Counting how many objects pass through the flow Line ==
2011 2011  
2012 2012  
2013 -Reference Link: [[How to set up to count objects pass in flow line>>How to set up to count objects pass in flow line]]?
2097 +Reference Link: [[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]]?
2014 2014  
2015 2015  
2016 2016  = 6. FAQ =
2017 2017  
2018 -== 6.1 How to upgrade the image? ==
2102 +== 6.1 How to update the firmware? ==
2019 2019  
2020 2020  
2021 -The LT LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to LT to:
2105 +Dragino frequently releases firmware updates for the LT-22222-L.
2022 2022  
2107 +Updating your LT-22222-L with the latest firmware version helps to:
2108 +
2023 2023  * Support new features
2024 -* For bug fix
2025 -* Change LoRaWAN bands.
2110 +* Fix bugs
2111 +* Change LoRaWAN frequency bands
2026 2026  
2027 -Below is the hardware connection for how to upload an image to the LT:
2113 +You will need the following things before proceeding:
2028 2028  
2115 +* 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
2116 +* USB to TTL adapter
2117 +* 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)
2118 +* 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.
2119 +
2120 +{{info}}
2121 +As of this writing, the latest firmware version available for the LT-22222-L is v1.6.1.
2122 +{{/info}}
2123 +
2124 +Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2125 +
2126 +
2029 2029  [[image:1653359603330-121.png]]
2030 2030  
2031 2031  
2032 -(((
2033 -(% style="color:blue" %)**Step1**(%%)**:** Download [[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]].
2034 -(% style="color:blue" %)**Step2**(%%)**:** Download the [[LT Image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]].
2035 -(% style="color:blue" %)**Step3**(%%)**:** Open flashloader; choose the correct COM port to update.
2036 -
2130 +Start the STM32 Flash Loader and choose the correct COM port to update.
2037 2037  
2038 2038  (((
2133 +(((
2039 2039  (% style="color:blue" %)**For LT-22222-L**(%%):
2040 -Hold down the PRO button and then momentarily press the RST reset button and the (% style="color:red" %)**DO1 led**(%%) will change from OFF to ON. When (% style="color:red" %)**DO1 LED**(%%) is on, it means the device is in download mode.
2135 +
2136 +Hold down the **PRO** button, then briefly press the **RST** button. The **DO1** LED will change from OFF to ON. When the **DO1** LED is ON, it indicates that the device is in firmware download mode.
2041 2041  )))
2042 2042  
2043 2043  
... ... @@ -2052,7 +2052,7 @@
2052 2052  [[image:image-20220524104033-15.png]]
2053 2053  
2054 2054  
2055 -(% style="color:red" %)**Notice**(%%): In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
2151 +(% style="color:red" %)**Note**(%%): If you have lost the programming cable, you can make one from a 3.5mm cable. The pin mapping is as follows:
2056 2056  
2057 2057  [[image:1653360054704-518.png||height="186" width="745"]]
2058 2058  
... ... @@ -2059,7 +2059,7 @@
2059 2059  
2060 2060  (((
2061 2061  (((
2062 -== 6.2 How to change the LoRa Frequency Bands/Region? ==
2158 +== 6.2 How to change the LoRaWAN frequency band/region? ==
2063 2063  
2064 2064  
2065 2065  )))
... ... @@ -2066,13 +2066,13 @@
2066 2066  )))
2067 2067  
2068 2068  (((
2069 -User can follow the introduction for [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
2165 +You can follow the introductions on [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloading, select the required image file.
2070 2070  )))
2071 2071  
2072 2072  (((
2073 2073  
2074 2074  
2075 -== 6.3 How to set up LT to work with Single Channel Gateway such as LG01/LG02? ==
2171 +== 6.3 How to setup LT to work with a Single Channel Gateway, such as LG01/LG02? ==
2076 2076  
2077 2077  
2078 2078  )))
... ... @@ -2079,13 +2079,13 @@
2079 2079  
2080 2080  (((
2081 2081  (((
2082 -In this case, users need to set LT-33222-L to work in ABP mode & transmit in only one frequency.
2178 +In this case, you need to set the LT-33222-L to work in ABP mode and transmit on only one frequency.
2083 2083  )))
2084 2084  )))
2085 2085  
2086 2086  (((
2087 2087  (((
2088 -Assume we have a LG02 working in the frequency 868400000 now , below is the step.
2184 +Assume you have an LG02 working on the frequency 868400000. Below are the steps.
2089 2089  
2090 2090  
2091 2091  )))
... ... @@ -2092,7 +2092,7 @@
2092 2092  )))
2093 2093  
2094 2094  (((
2095 -(% style="color:blue" %)**Step1**(%%):  Log in TTN, Create an ABP device in the application and input the network session key (NETSKEY), app session key (APPSKEY) from the device.
2191 +(% style="color:#0000ff" %)**Step 1**(%%):  Log in to The Things Stack SANDBOX, create an ABP device in the application, and input the Network Session key (NwkSKey), App session key (AppSKey) of the device.
2096 2096  
2097 2097  
2098 2098  )))
... ... @@ -2149,61 +2149,56 @@
2149 2149  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/]]
2150 2150  
2151 2151  
2152 -== 6.5 Can I see counting event in Serial? ==
2248 +== 6.5 Can I see the counting event in the serial output? ==
2153 2153  
2154 2154  
2155 2155  (((
2156 -User can run AT+DEBUG command to see the counting event in serial. If firmware too old and doesn't support AT+DEBUG. User can update to latest firmware first.
2252 +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.
2157 2157  
2158 2158  
2159 -== 6.6 Can i use point to point communication for LT-22222-L? ==
2255 +== 6.6 Can I use point-to-point communication with LT-22222-L? ==
2160 2160  
2161 2161  
2162 -Yes, please refer [[Point to Point Communication>>doc:Main. Point to Point Communication of LT-22222-L.WebHome]]  ，this is [[firmware>>https://github.com/dragino/LT-22222-L/releases]].
2163 -
2164 -
2258 +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]].
2165 2165  )))
2166 2166  
2167 2167  (((
2168 -== 6.7 Why does the relay output become the default and open relay after the lt22222 is powered off? ==
2262 +== 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
2169 2169  
2170 2170  
2171 -If the device is not shut down, but directly powered off.
2265 +* If the device is not properly shut down and is directly powered off.
2266 +* It will default to a power-off state.
2267 +* In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
2268 +* After a restart, the status before the power failure will be read from flash.
2172 2172  
2173 -It will default that this is a power-off state.
2174 2174  
2175 -In modes 2 to 5, DO RO status and pulse count are saved in flash.
2271 +== 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
2176 2176  
2177 -After restart, the status before power failure will be read from flash.
2178 2178  
2274 +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:
2179 2179  
2180 -== 6.8 Can i set up LT-22222-L as a NC(Normal Close) Relay? ==
2181 2181  
2182 -
2183 -LT-22222-L built-in relay is NO (Normal Open). User can use an external relay to achieve Normal Close purpose. Diagram as below:
2184 -
2185 -
2186 2186  [[image:image-20221006170630-1.png||height="610" width="945"]]
2187 2187  
2188 2188  
2189 -== 6.9 Can LT22222-L save RO state? ==
2280 +== 6.9 Can the LT-22222-L save the RO state? ==
2190 2190  
2191 2191  
2192 -Firmware version needs to be no less than 1.6.0.
2283 +The firmware version must be at least 1.6.0.
2193 2193  
2194 2194  
2195 -== 6.10 Why does the LT22222 always report 15.585V when measuring AVI? ==
2286 +== 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
2196 2196  
2197 2197  
2198 -It is likely that the GND is not connected during the measurement, or the wire connected to the GND is loose.
2289 +It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
2199 2199  
2200 2200  
2201 -= 7. Trouble Shooting =
2292 += 7. Troubleshooting =
2202 2202  )))
2203 2203  
2204 2204  (((
2205 2205  (((
2206 -== 7.1 Downlink doesn't work, how to solve it? ==
2297 +== 7.1 Downlink isn't working. How can I solve this? ==
2207 2207  
2208 2208  
2209 2209  )))
... ... @@ -2210,42 +2210,42 @@
2210 2210  )))
2211 2211  
2212 2212  (((
2213 -Please see this link for how to debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]]
2304 +Please refer to this link for debugging instructions: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]]
2214 2214  )))
2215 2215  
2216 2216  (((
2217 2217  
2218 2218  
2219 -== 7.2 Have trouble to upload image. ==
2310 +== 7.2 Having trouble uploading an image? ==
2220 2220  
2221 2221  
2222 2222  )))
2223 2223  
2224 2224  (((
2225 -See this link for trouble shooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
2316 +Please refer to this link for troubleshooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
2226 2226  )))
2227 2227  
2228 2228  (((
2229 2229  
2230 2230  
2231 -== 7.3 Why I can't join TTN in US915 /AU915 bands? ==
2322 +== 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
2232 2232  
2233 2233  
2234 2234  )))
2235 2235  
2236 2236  (((
2237 -It might be about the channels mapping. [[Please see this link for detail>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
2328 +It might be related to the channel mapping. [[Please refer to this link for details.>>https://github.com/dragino/LT-22222-L/releases||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
2238 2238  )))
2239 2239  
2240 2240  
2241 -== 7.4 Why can LT22222 perform Uplink normally, but cannot receive Downlink? ==
2332 +== 7.4 Why can the LT-22222-L perform Uplink normally, but cannot receive Downlink? ==
2242 2242  
2243 2243  
2244 -The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue state.
2245 -Use this command to bring their counts back together: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2335 +The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
2336 +Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2246 2246  
2247 2247  
2248 -= 8. Order Info =
2339 += 8. Ordering information =
2249 2249  
2250 2250  
2251 2251  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
... ... @@ -2252,43 +2252,44 @@
2252 2252  
2253 2253  (% style="color:#4f81bd" %)**XXX:**
2254 2254  
2255 -* (% style="color:red" %)**EU433**(%%):  LT with frequency bands EU433
2256 -* (% style="color:red" %)**EU868**(%%):  LT with frequency bands EU868
2257 -* (% style="color:red" %)**KR920**(%%):  LT with frequency bands KR920
2258 -* (% style="color:red" %)**CN470**(%%):  LT with frequency bands CN470
2259 -* (% style="color:red" %)**AS923**(%%):  LT with frequency bands AS923
2260 -* (% style="color:red" %)**AU915**(%%):  LT with frequency bands AU915
2261 -* (% style="color:red" %)**US915**(%%):  LT with frequency bands US915
2262 -* (% style="color:red" %)**IN865**(%%):  LT with frequency bands IN865
2263 -* (% style="color:red" %)**CN779**(%%):  LT with frequency bands CN779
2346 +* (% style="color:red" %)**EU433**(%%): LT with frequency bands EU433
2347 +* (% style="color:red" %)**EU868**(%%): LT with frequency bands EU868
2348 +* (% style="color:red" %)**KR920**(%%): LT with frequency bands KR920
2349 +* (% style="color:red" %)**CN470**(%%): LT with frequency bands CN470
2350 +* (% style="color:red" %)**AS923**(%%): LT with frequency bands AS923
2351 +* (% style="color:red" %)**AU915**(%%): LT with frequency bands AU915
2352 +* (% style="color:red" %)**US915**(%%): LT with frequency bands US915
2353 +* (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865
2354 +* (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779
2264 2264  
2265 -= 9. Packing Info =
2266 2266  
2357 += 9. Packing information =
2267 2267  
2268 -**Package Includes**:
2269 2269  
2360 +**Package includes**:
2361 +
2270 2270  * LT-22222-L I/O Controller x 1
2271 2271  * Stick Antenna for LoRa RF part x 1
2272 2272  * Bracket for controller x1
2273 -* Program cable x 1
2365 +* 3.5mm Programming cable x 1
2274 2274  
2275 2275  **Dimension and weight**:
2276 2276  
2277 2277  * Device Size: 13.5 x 7 x 3 cm
2278 -* Device Weight: 105g
2370 +* Device Weight: 105 g
2279 2279  * Package Size / pcs : 14.5 x 8 x 5 cm
2280 -* Weight / pcs : 170g
2372 +* Weight / pcs : 170 g
2281 2281  
2374 +
2282 2282  = 10. Support =
2283 2283  
2284 2284  
2285 2285  * (((
2286 -Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
2379 +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.
2287 2287  )))
2288 2288  * (((
2289 -Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[Support@dragino.cc>>mailto:Support@dragino.cc]]
2382 +Please provide as much information as possible regarding your inquiry (e.g., product models, a detailed description of the problem, steps to replicate it, etc.) and send an email to [[support@dragino.cc>>mailto:support@dragino.cc]]
2290 2290  
2291 -
2292 2292  
2293 2293  )))
2294 2294  
integration-details.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +463.9 KB
Content
lt-22222-device-overview.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +497.2 KB
Content
lt-22222-join-network.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +340.6 KB
Content
lt-22222-ul-payload-decoded.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +48.7 KB
Content
lt-22222-ul-payload-fmt.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +438.6 KB
Content
message-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +20.1 KB
Content
thingseye.io_integrationsCenter_integrations-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +469.3 KB
Content
thingseye.io_integrationsCenter_integrations.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +302.3 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0