Last modified by Saxer Lin on 2025/04/15 17:24
<
From version < 164.1 >
edited by Dilisi S
on 2024/11/06 05:10
To version < 178.1 >
edited by Dilisi S
on 2024/11/09 02:59
>
Change comment: Nov 8 edits - part 1

Summary

Details

Page properties
Content
... ... @@ -33,8 +33,6 @@
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  
... ... @@ -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,11 @@
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 +(% class="wikigeneratedid" %)
209 +==== ====
211 211  
211 +==== 3.2.2.1 Using the LoRaWAN Device Repository ====
212 +
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 -*
221 +
222 +* 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,11 @@
226 226  
227 227  [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
228 228  
229 -==== Entering device information manually: ====
231 +(% class="wikigeneratedid" %)
232 +==== ====
230 230  
234 +==== 3.2.2.2 Entering device information manually ====
235 +
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.
248 +* Page continued...
249 +** Enter **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
250 +** Enter **DevEUI** in the **DevEUI** field.
251 +** Enter **AppKey** in the **AppKey** field.
252 +** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
253 +** Under **After registration**, select the **View registered end device** option.
254 +** 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 ====
259 +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"]]
262 +[[image:lt-22222-device-overview.png||height="625" width="1000"]]
257 257  
258 258  
259 -== 3.3 Uplink Payload formats ==
265 +==== 3.2.2.3 Joining ====
260 260  
267 +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.
269 +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  
272 +[[image:lt-22222-join-network.png||height="625" width="1000"]]
273 +
274 +
275 +By default, you will receive an uplink data message every 10 minutes.
276 +
277 +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.
278 +
279 +[[image:lt-22222-ul-payload-decoded.png]]
280 +
281 +
282 +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.
283 +
284 +[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
285 +
286 +
287 +== 3.3 Work Modes and their Uplink Payload formats ==
288 +
289 +
290 +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.
291 +
292 +* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO
293 +
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,16 @@
273 273  
274 274  * (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5
275 275  
276 -=== 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
277 277  
305 +The uplink messages are sent over LoRaWAN FPort 2. By default, an uplink message is sent every 10 minutes.
278 278  
307 +=== 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
308 +
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" %)
310 +This is the default mode.
281 281  
312 +The uplink payload is 11 bytes long. (% style="display:none" wfd-invisible="true" %)
313 +
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*|(((
324 +)))|**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.
330 +(% 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.
337 +* RO is for the relay. ROx=1: CLOSED, ROx=0 always OPEN.
338 +* DI is for digital input. DIx=1: HIGH or FLOATING, DIx=0: LOW.
339 +* 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.
360 +* **[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.
366 +* **[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.
377 +**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.
391 +(% 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.
397 +* 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.
401 +* 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**
... ... @@ -602,9 +602,9 @@
602 602  
603 603  **Example:**
604 604  
605 -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)
637 +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)
606 606  
607 -AT+AVLIM=5000,0,0,0   (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore)
639 +AT+AVLIM=5000,0,0,0   (triggers an uplink if AVI1 voltage lower than 5V. Use 0 for parameters that are not in use)
608 608  
609 609  
610 610  (% style="color:#4f81bd" %)**Trigger based on current**:
... ... @@ -614,7 +614,7 @@
614 614  
615 615  **Example:**
616 616  
617 -AT+ACLIM=10000,15000,0,0   (If ACI1 voltage lower than 10mA or higher than 15mA, trigger an uplink)
649 +AT+ACLIM=10000,15000,0,0   (triggers an uplink if ACI1 voltage is lower than 10mA or higher than 15mA)
618 618  
619 619  
620 620  (% style="color:#4f81bd" %)**Trigger based on DI status**:
... ... @@ -629,39 +629,38 @@
629 629  AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
630 630  
631 631  
632 -(% style="color:#037691" %)**Downlink Command to set Trigger Condition:**
664 +(% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
633 633  
634 634  Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
635 635  
636 636  Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
637 637  
638 - AA: Code for this downlink Command:
670 + AA: Type Code for this downlink Command:
639 639  
640 - xx: 0: Limit for AV1 and AV2;  1: limit for AC1 and AC2 ; 2 DI1, DI2 trigger enable/disable
672 + xx: **0**: Limit for AV1 and AV2; **1**: limit for AC1 and AC2; **2**: DI1and DI2 trigger enable/disable.
641 641  
642 - yy1 yy1: AC1 or AV1 low limit or DI1/DI2 trigger status.
674 + yy1 yy1: AC1 or AV1 LOW limit or DI1/DI2 trigger status.
643 643  
644 - yy2 yy2: AC1 or AV1 high limit.
676 + yy2 yy2: AC1 or AV1 HIGH limit.
645 645  
646 - yy3 yy3: AC2 or AV2 low limit.
678 + yy3 yy3: AC2 or AV2 LOW limit.
647 647  
648 - Yy4 yy4: AC2 or AV2 high limit.
680 + Yy4 yy4: AC2 or AV2 HIGH limit.
649 649  
650 650  
651 -**Example1**: AA 00 13 88 00 00 00 00 00 00
683 +**Example 1**: AA 00 13 88 00 00 00 00 00 00
652 652  
653 -Same as AT+AVLIM=5000,0,0,0   (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore)
685 +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)
654 654  
655 655  
656 -**Example2**: AA 02 01 00
688 +**Example 2**: AA 02 01 00
657 657  
658 -Same as AT+ DTRI =1,0  (Enable DI1 trigger / disable DI2 trigger)
690 +Same as AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
659 659  
660 660  
661 -
662 662  (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:**
663 663  
664 -MOD6 Payload: total 11 bytes payload
695 +MOD6 Payload: total of 11 bytes
665 665  
666 666  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
667 667  |(% 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**
... ... @@ -675,10 +675,10 @@
675 675  MOD(6)
676 676  )))
677 677  
678 -(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1byte as below
709 +(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
679 679  
680 680  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
681 -|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
712 +|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
682 682  |(((
683 683  AV1_LOW
684 684  )))|(((
... ... @@ -697,17 +697,17 @@
697 697  AC2_HIGH
698 698  )))
699 699  
700 -* Each bits shows if the corresponding trigger has been configured.
731 +* Each bit shows if the corresponding trigger has been configured.
701 701  
702 702  **Example:**
703 703  
704 -10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW
735 +10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW
705 705  
706 706  
707 -(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1byte as below
738 +(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
708 708  
709 709  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
710 -|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
741 +|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
711 711  |(((
712 712  AV1_LOW
713 713  )))|(((
... ... @@ -726,11 +726,11 @@
726 726  AC2_HIGH
727 727  )))
728 728  
729 -* Each bits shows which status has been trigger on this uplink.
760 +* Each bit shows which status has been triggered on this uplink.
730 730  
731 731  **Example:**
732 732  
733 -10000000: Means this packet is trigger by AC1_LOW. Means voltage too low.
764 +10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.
734 734  
735 735  
736 736  (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
... ... @@ -739,7 +739,7 @@
739 739  |**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
740 740  |N/A|N/A|N/A|N/A|DI2_STATUS|DI2_FLAG|DI1_STATUS|DI1_FLAG
741 741  
742 -* Each bits shows which status has been trigger on this uplink.
773 +* Each bits shows which status has been triggered on this uplink.
743 743  
744 744  **Example:**
745 745  
... ... @@ -766,11 +766,11 @@
766 766  )))
767 767  
768 768  
769 -== 3.4 ​Configure LT via AT or Downlink ==
800 +== 3.4 ​Configure LT via AT Commands or Downlinks ==
770 770  
771 771  
772 772  (((
773 -User can configure LT I/O Controller via AT Commands or LoRaWAN Downlink Commands
804 +User can configure LT I/O Controller via AT Commands or LoRaWAN Downlinks.
774 774  )))
775 775  
776 776  (((
... ... @@ -785,9 +785,8 @@
785 785  
786 786  === 3.4.1 Common Commands ===
787 787  
788 -
789 789  (((
790 -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]]
820 +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]].
791 791  )))
792 792  
793 793  
... ... @@ -795,34 +795,37 @@
795 795  
796 796  ==== 3.4.2.1 Set Transmit Interval ====
797 797  
828 +Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
798 798  
799 -Set device uplink interval.
830 +* (% style="color:#037691" %)**AT command:**
800 800  
801 -* (% style="color:#037691" %)**AT Command:**
832 +(% style="color:blue" %)**AT+TDC=N**
802 802  
803 -(% style="color:blue" %)**AT+TDC=N **
834 +where N is the time in milliseconds.
804 804  
836 +**Example: **AT+TDC=30000. This will set the uplink interval to 30 seconds
805 805  
806 -**Example: **AT+TDC=30000. Means set interval to 30 seconds
807 807  
839 +* (% style="color:#037691" %)**Downlink payload (prefix 0x01):**
808 808  
809 -* (% style="color:#037691" %)**Downlink Payload (prefix 0x01):**
810 -
811 811  (% style="color:blue" %)**0x01 aa bb cc  **(%%)** ~/~/ Same as AT+TDC=0x(aa bb cc)**
812 812  
813 813  
814 814  
815 -==== 3.4.2.2 Set Work Mode (AT+MOD) ====
845 +==== 3.4.2.2 Set the Work Mode (AT+MOD) ====
816 816  
817 817  
818 -Set work mode.
848 +Sets the work mode.
819 819  
820 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+MOD=N  **
850 +* (% style="color:#037691" %)**AT command:**(%%) (% style="color:blue" %)**AT+MOD=N  **
821 821  
822 -**Example**: AT+MOD=2. Set work mode to Double DI counting mode
852 +Where N is the work mode.
823 823  
824 -* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A):**
854 +**Example**: AT+MOD=2. This will set the work mode to Double DI counting mode.
825 825  
856 +
857 +* (% style="color:#037691" %)**Downlink payload (prefix 0x0A):**
858 +
826 826  (% style="color:blue" %)**0x0A aa  **(%%)** ** ~/~/ Same as AT+MOD=aa
827 827  
828 828  
... ... @@ -830,10 +830,12 @@
830 830  ==== 3.4.2.3 Poll an uplink ====
831 831  
832 832  
833 -* (% style="color:#037691" %)**AT Command:**(%%) There is no AT Command to poll uplink
866 +Asks the device to send an uplink.
834 834  
835 -* (% style="color:#037691" %)**Downlink Payload (prefix 0x08):**
868 +* (% style="color:#037691" %)**AT command:**(%%) There is no AT Command to poll uplink
836 836  
870 +* (% style="color:#037691" %)**Downlink payload (prefix 0x08):**
871 +
837 837  (% style="color:blue" %)**0x08 FF  **(%%)** **~/~/ Poll an uplink
838 838  
839 839  **Example**: 0x08FF, ask device to send an Uplink
... ... @@ -840,16 +840,16 @@
840 840  
841 841  
842 842  
843 -==== 3.4.2.4 Enable Trigger Mode ====
878 +==== 3.4.2.4 Enable/Disable Trigger Mode ====
844 844  
845 845  
846 -Use of trigger mode, please check [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
881 +Enable or disable the trigger mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
847 847  
848 848  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0**
849 849  
850 -(% style="color:red" %)**1:** (%%)Enable Trigger Mode
885 +(% style="color:red" %)**1:** (%%)Enable the trigger mode
851 851  
852 -(% style="color:red" %)**0: **(%%)Disable Trigger Mode
887 +(% style="color:red" %)**0: **(%%)Disable the trigger mode
853 853  
854 854  
855 855  * (% style="color:#037691" %)**Downlink Payload (prefix 0x0A 06):**
... ... @@ -861,7 +861,7 @@
861 861  ==== 3.4.2.5 Poll trigger settings ====
862 862  
863 863  
864 -Poll trigger settings
899 +Polls the trigger settings
865 865  
866 866  * (% style="color:#037691" %)**AT Command:**
867 867  
... ... @@ -869,7 +869,7 @@
869 869  
870 870  * (% style="color:#037691" %)**Downlink Payload (prefix 0x AB 06):**
871 871  
872 -(% style="color:blue" %)**0xAB 06  ** (%%) ~/~/ Poll trigger settings, device will uplink trigger settings once receive this command
907 +(% style="color:blue" %)**0xAB 06  ** (%%) ~/~/ Poll the trigger settings. Device will uplink trigger settings once receive this command
873 873  
874 874  
875 875  
... ... @@ -876,11 +876,11 @@
876 876  ==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ====
877 877  
878 878  
879 -Enable Disable DI1/DI2/DI2 as trigger,
914 +Enable or Disable DI1/DI2/DI2 as trigger,
880 880  
881 881  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
882 882  
883 -**Example:** AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
918 +**Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
884 884  
885 885  
886 886  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 02):**
... ... @@ -912,15 +912,15 @@
912 912  ==== 3.4.2.8 Trigger2 – Set DI2 as trigger ====
913 913  
914 914  
915 -Set DI2 trigger.
950 +Sets DI2 trigger.
916 916  
917 917  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b**
918 918  
919 -(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
954 +(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
920 920  
921 921  (% style="color:red" %)**b :** (%%)delay timing.
922 922  
923 -**Example:** AT+TRIG2=0,100(set DI1 port to trigger on low level, valid signal is 100ms )
958 +**Example:** AT+TRIG2=0,100 (set DI1 port to trigger on low level, valid signal is 100ms )
924 924  
925 925  
926 926  * (% style="color:#037691" %)**Downlink Payload (prefix 0x09 02 ):**
... ... @@ -958,7 +958,7 @@
958 958  ==== 3.4.2.11 Trigger – Set minimum interval ====
959 959  
960 960  
961 -Set AV and AC trigger minimum interval, system won't response to the second trigger within this set time after the first trigger.
996 +Sets AV and AC trigger minimum interval. Device won't response to the second trigger within this set time after the first trigger.
962 962  
963 963  * (% 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.
964 964  
... ... @@ -1351,69 +1351,122 @@
1351 1351  
1352 1352  == 3.5 Integrating with ThingsEye.io ==
1353 1353  
1354 -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.
1389 +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.
1355 1355  
1356 -=== 3.5.1 Configuring The Things Stack Sandbox ===
1391 +=== 3.5.1 Configuring MQTT Connection Information with The Things Stack Sandbox ===
1357 1357  
1358 -* Go to your Application and select MQTT under Integrations.
1359 -* In the Connection credentials section, under Username, The Thins Stack displays an auto-generated username. You can use it or provide a new one.
1360 -* For the Password, click the Generate new API key button to generate a password. You can see it by clicking on the eye button.
1393 +We use The Things Stack Sandbox for demonstating the configuration but  other
1361 1361  
1395 +* In **The Things Stack Sandbox**, select your application under **Applications**.
1396 +* Select **MQTT** under **Integrations**.
1397 +* In the **Connection information **section, for **Username**, The Things Stack displays an auto-generated username. You can use it or provide a new one.
1398 +* 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.
1399 +
1400 +NOTE. The username and  password (API key) you created here are required in the next section.
1401 +
1362 1362  [[image:tts-mqtt-integration.png||height="625" width="1000"]]
1363 1363  
1364 1364  === 3.5.2 Configuring ThingsEye.io ===
1365 1365  
1366 -* Login to your thingsEye.io account.
1367 -* Under the Integrations center, click Integrations.
1368 -* Click the Add integration button (the button with the + symbol).
1406 +This section guides you on how to create an integration in ThingsEye to connect with The Things Stack MQTT server.
1369 1369  
1408 +* Login to your [[ThingsEye.io >>https://thingseye.io]]account.
1409 +* Under the **Integrations center**, click **Integrations**.
1410 +* Click the **Add integration** button (the button with the **+** symbol).
1411 +
1370 1370  [[image:thingseye-io-step-1.png||height="625" width="1000"]]
1371 1371  
1372 1372  
1373 -On the Add integration page configure the following:
1415 +On the **Add integration** window, configure the following:
1374 1374  
1375 -Basic settings:
1417 +**Basic settings:**
1376 1376  
1377 -* Select The Things Stack Community from the Integration type list.
1378 -* Enter a suitable name for your integration in the Name box or keep the default name.
1379 -* Click the Next button.
1419 +* Select **The Things Stack Community** from the **Integration type** list.
1420 +* Enter a suitable name for your integration in the **Name **text** **box or keep the default name.
1421 +* Ensure the following options are turned on.
1422 +** Enable integration
1423 +** Debug mode
1424 +** Allow create devices or assets
1425 +* Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
1380 1380  
1381 1381  [[image:thingseye-io-step-2.png||height="625" width="1000"]]
1382 1382  
1383 -Uplink Data converter:
1384 1384  
1385 -* Click the Create New button if it is not selected by default.
1386 -* Click the JavaScript button.
1387 -* Paste the uplink decoder function into the text area (first, delete the default code). The demo decoder function can be found here.
1388 -* Click the Next button.
1430 +**Uplink data converter:**
1389 1389  
1432 +* Click the **Create new** button if it is not selected by default.
1433 +* Enter a suitable name for the uplink data converter in the **Name **text** **box or keep the default name.
1434 +* Click the **JavaScript** button.
1435 +* 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]].
1436 +* Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
1437 +
1390 1390  [[image:thingseye-io-step-3.png||height="625" width="1000"]]
1391 1391  
1392 -Downlink Data converter (this is an optional step):
1393 1393  
1394 -* Click the Create new button if it is not selected by default.
1395 -* Click the JavaScript button.
1396 -* Paste the downlink decoder function into the text area (first, delete the default code). The demo decoder function can be found here.
1397 -* Click the Next button.
1441 +**Downlink data converter (this is an optional step):**
1398 1398  
1443 +* Click the **Create new** button if it is not selected by default.
1444 +* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name
1445 +* Click the **JavaScript** button.
1446 +* Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found here.
1447 +* Click the **Next** button. You will be navigated to the **Connection** tab.
1448 +
1399 1399  [[image:thingseye-io-step-4.png||height="625" width="1000"]]
1400 1400  
1401 -Connection:
1402 1402  
1403 -* Choose Region from the Host type.
1404 -* Enter the cluster of your The Things Stack in the Region textbox.
1405 -* 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.
1406 -* Click Check connection to test the connection. If the connection is successful, you can see the message saying Connected.
1407 -* Click the Add button.
1452 +**Connection:**
1408 1408  
1454 +* Choose **Region** from the **Host type**.
1455 +* 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/...).
1456 +* 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).
1457 +* Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
1458 +
1459 +[[image:message-1.png]]
1460 +
1461 +
1462 +* Click the **Add** button.
1463 +
1409 1409  [[image:thingseye-io-step-5.png||height="625" width="1000"]]
1410 1410  
1411 1411  
1412 -Your integration is added to the integrations list and it will display on the Integrations page.
1467 +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.
1413 1413  
1414 -[[image:thingseye-io-step-6.png||height="625" width="1000"]]
1415 1415  
1470 +[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
1416 1416  
1472 +
1473 +**Viewing integration details**:
1474 +
1475 +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.
1476 +
1477 +[[image:integration-details.png||height="686" width="1000"]]
1478 +
1479 +
1480 +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.
1481 +
1482 +Note: See also ThingsEye documentation.
1483 +
1484 +
1485 +**Viewing events:**
1486 +
1487 +This tab  displays all the uplink messages from the LT-22222-L.
1488 +
1489 +* Click on the **Events **tab.
1490 +* Select **Debug **from the **Event type** dropdown.
1491 +* Select the** time frame** from the **time window**.
1492 +
1493 +[insert image]
1494 +
1495 +- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
1496 +
1497 +[insert image]
1498 +
1499 +
1500 +**Deleting the integration**:
1501 +
1502 +If you want to delete this integration, click the **Delete integratio**n button.
1503 +
1504 +
1417 1417  == 3.6 Interface Details ==
1418 1418  
1419 1419  === 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) ===
... ... @@ -1669,7 +1669,7 @@
1669 1669  
1670 1670  
1671 1671  (((
1672 -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:
1760 +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:
1673 1673  )))
1674 1674  
1675 1675  [[image:1653358355238-883.png]]
... ... @@ -2014,7 +2014,7 @@
2014 2014  
2015 2015  = 6. FAQ =
2016 2016  
2017 -== 6.1 How to upgrade the image? ==
2105 +== 6.1 How to upgrade the firmware image? ==
2018 2018  
2019 2019  
2020 2020  The LT-22222-L I/O Controller is shipped with a 3.5mm cable, which is used to upload an image to LT in order to:
... ... @@ -2023,20 +2023,25 @@
2023 2023  * Fix bugs.
2024 2024  * Change LoRaWAN bands.
2025 2025  
2026 -Below is the hardware connection setup for uploading an image to the LT:
2114 +Below is the hardware connection setup for uploading an firmware image to the LT-22222-L:
2027 2027  
2116 +(% class="box infomessage" %)
2117 +(((
2118 +The latest firmware version available for the LT-22222-L is v1.6.1 at the time of this writing.
2119 +)))
2120 +
2028 2028  [[image:1653359603330-121.png]]
2029 2029  
2030 2030  
2031 2031  (((
2032 -(% style="color:#0000ff" %)**Step 1**(%%)**:** Download the F[[lash 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]].
2125 +(% style="color:#0000ff" %)**Step 1**(%%)**:** Download the F[[lash 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)
2033 2033  (% style="color:#0000ff" %)**Step 2**(%%)**:** Download the [[LT Image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]].
2034 2034  (% style="color:#0000ff" %)**Step 3**(%%)**:** Open the Flash Loader and choose the correct COM port to update.
2035 -
2036 2036  
2037 2037  (((
2038 2038  (% style="color:blue" %)**For LT-22222-L**(%%):
2039 -Hold down the PRO button, then momentarily press the RST reset button. The (% style="color:red" %)**DO1 LED**(%%) will change from OFF to ON. When the (% style="color:red" %)**DO1 LED**(%%) is ON, it indicates that the device is in download mode.
2131 +
2132 +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.
2040 2040  )))
2041 2041  
2042 2042  
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