Last modified by Saxer Lin on 2025/04/15 17:24
<
From version < 196.1 >
edited by Dilisi S
on 2024/11/17 06:09
To version < 181.1 >
edited by Dilisi S
on 2024/11/10 05:03
>
Change comment: Uploaded new attachment "thingseye-events.png", version {1}

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -LT-22222-L -- LoRa I/O Controller User Manual
1 +LT-22222-L -- LoRa IO Controller User Manual
Content
... ... @@ -40,9 +40,7 @@
40 40  * 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.
41 41  * Setup your own private LoRaWAN network.
42 42  
43 -{{info}}
44 - You can use a LoRaWAN gateway, such as the [[Dragino LG308>>https://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], to expand or create LoRaWAN coverage in your area.
45 -{{/info}}
43 +> You can use a LoRaWAN gateway, such as the Dragino LG308, to expand or create LoRaWAN coverage in your area.
46 46  )))
47 47  
48 48  (((
... ... @@ -58,13 +58,13 @@
58 58  * STM32L072xxxx MCU
59 59  * SX1276/78 Wireless Chip 
60 60  * Power Consumption:
61 -** Idle: 4mA@12V
59 +** Idle: 4mA@12v
62 62  ** 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:**
66 66  
67 -* 2 x Digital dual direction Input (Detect High/Low signal, Max: 50V, or 220V with optional external resistor)
65 +* 2 x Digital dual direction Input (Detect High/Low signal, Max: 50v, or 220v with optional external resistor)
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)
... ... @@ -74,8 +74,8 @@
74 74  (% style="color:#037691" %)**LoRa Spec:**
75 75  
76 76  * Frequency Range:
77 -** Band 1 (HF): 862 ~~ 1020 MHz
78 -** Band 2 (LF): 410 ~~ 528 MHz
75 +** Band 1 (HF): 862 ~~ 1020 Mhz
76 +** Band 2 (LF): 410 ~~ 528 Mhz
79 79  * 168 dB maximum link budget.
80 80  * +20 dBm - 100 mW constant RF output vs.
81 81  * +14 dBm high-efficiency PA.
... ... @@ -94,7 +94,7 @@
94 94  
95 95  == 1.3 Features ==
96 96  
97 -* LoRaWAN Class A & Class C modes
95 +* LoRaWAN Class A & Class C protocol
98 98  * Optional Customized LoRa Protocol
99 99  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
100 100  * AT Commands to change parameters
... ... @@ -104,27 +104,45 @@
104 104  
105 105  == 1.4 Applications ==
106 106  
107 -* Smart buildings & home automation
108 -* Logistics and supply chain management
109 -* Smart metering
110 -* Smart agriculture
111 -* Smart cities
112 -* Smart factory
105 +* Smart Buildings & Home Automation
106 +* Logistics and Supply Chain Management
107 +* Smart Metering
108 +* Smart Agriculture
109 +* Smart Cities
110 +* Smart Factory
113 113  
114 -= 2. Assembling the device =
112 +== 1.5 Hardware Variants ==
115 115  
116 -== 2.1 Connecting the antenna ==
117 117  
118 -Connect the LoRa antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper screw terminal block. Secure the antenna by tightening it clockwise.
115 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %)
116 +|(% style="background-color:#4f81bd; color:white; width:103px" %)**Model**|(% style="background-color:#4f81bd; color:white; width:131px" %)**Photo**|(% style="background-color:#4f81bd; color:white; width:266px" %)**Description**
117 +|(% style="width:103px" %)**LT22222-L**|(% style="width:131px" %)(((
118 +(% style="text-align:center" %)
119 +[[image:image-20230424115112-1.png||height="106" width="58"]]
120 +)))|(% style="width:334px" %)(((
121 +* 2 x Digital Input (Bi-direction)
122 +* 2 x Digital Output
123 +* 2 x Relay Output (5A@250VAC / 30VDC)
124 +* 2 x 0~~20mA Analog Input (res:0.01mA)
125 +* 2 x 0~~30V Analog Input (res:0.01v)
126 +* 1 x Counting Port
127 +)))
119 119  
120 -{{warning}}
121 -Warning! Do not power on the device without connecting the antenna.
122 -{{/warning}}
129 += 2. Assembling the Device =
123 123  
124 -== 2.2 Terminals ==
131 +== 2.1 What is included in the package? ==
125 125  
126 -The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 terminals and the lower screw terminal block has 10 terminals.
133 +The package includes the following items:
127 127  
135 +* 1 x LT-22222-L I/O Controller
136 +* 1 x LoRaWAN antenna matched to the frequency of the LT-22222-L
137 +* 1 x bracket for DIN rail mounting
138 +* 1 x programming cable
139 +
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.
141 +
142 +== 2.2 Terminals ==
143 +
128 128  Upper screw terminal block (from left to right):
129 129  
130 130  (% style="width:634px" %)
... ... @@ -151,28 +151,26 @@
151 151  |(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
152 152  |(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
153 153  
154 -== 2.3 Powering the device ==
170 +== 2.3 Powering the LT-22222-L ==
155 155  
156 -The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s positive wire to the VIN and the negative wire to the GND screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered.
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.
157 157  
158 -Once powered, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** The Things Stack. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LED** 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.
159 159  
160 -{{warning}}
161 -We recommend that you power on the LT-22222-L after configuring its registration information with a LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.
162 -{{/warning}}
163 -
164 -
165 165  [[image:1653297104069-180.png]]
166 166  
167 167  
168 -= 3. Registering with a LoRaWAN Network Server =
178 += 3. Operation Mode =
169 169  
180 +== 3.1 How does it work? ==
181 +
170 170  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.
171 171  
172 -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 LED** 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.
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.
173 173  
174 174  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.
175 175  
188 +== 3.2 Registering with a LoRaWAN network server ==
189 +
176 176  The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
177 177  
178 178  [[image:image-20220523172350-1.png||height="266" width="864"]]
... ... @@ -187,33 +187,28 @@
187 187  
188 188  === 3.2.2 The Things Stack Sandbox (TTSS) ===
189 189  
190 -The Things Stack Sandbox was formally called The Things Stack Community Edition.
191 -
192 192  * Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account.
193 -* Create an application with The Things Stack if you do not have one yet.
194 -* Go to your application page and click on the **End devices** in the left menu.
195 -* On the End devices page, click on **+ Register end device**. Two registration options are available:
205 +* Create an application if you do not have one yet.
206 +* Register LT-22222-L with that application. Two registration options are available:
196 196  
208 +==== ====
209 +
197 197  ==== 3.2.2.1 Using the LoRaWAN Device Repository ====
198 198  
212 +* Go to your application and click on the **Register end device** button.
199 199  * On the **Register end device** page:
200 -** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
201 -** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists.
202 -*** **End device brand**: Dragino Technology Co., Limited
203 -*** **Model**: LT22222-L I/O Controller
204 -*** **Hardware ver**: Unknown
205 -*** **Firmware ver**: 1.6.0
206 -*** **Profile (Region)**: Select the region that matches your device.
207 -** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
214 +** Select the option **Select the end device in the LoRaWAN Device Repository**.
215 +** Choose the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)**.
216 +** Select the **Frequency plan** that matches your device.
208 208  
209 209  [[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
210 210  
211 211  
212 -* Register end device page continued...
213 -** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network'.
214 -** In the **DevEUI** field, enter the **DevEUI**.
215 -** In the **AppKey** field, enter the **AppKey.**
216 -** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
221 +* Page continued...
222 +** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
223 +** Enter the **DevEUI** in the **DevEUI** field.
224 +** Enter the **AppKey** in the **AppKey** field.
225 +** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
217 217  ** Under **After registration**, select the **View registered end device** option.
218 218  
219 219  [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
... ... @@ -220,25 +220,25 @@
220 220  
221 221  ==== ====
222 222  
223 -==== 3.2.2.2 Adding device manually ====
232 +==== 3.2.2.2 Entering device information manually ====
224 224  
225 225  * On the **Register end device** page:
226 -** Select the option **Enter end device specifies manually** under **Input method**.
227 -** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
228 -** Select the **LoRaWAN version** as **LoRaWAN Specification 1.0.3**
229 -** Select the **Regional Parameters version** as** RP001 Regional Parameters 1.0.3 revision A**
230 -** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the hidden section.
231 -** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
232 -** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
235 +** Select the **Enter end device specifies manually** option as the input method.
236 +** Select the **Frequency plan** that matches your device.
237 +** Select the **LoRaWAN version**.
238 +** Select the **Regional Parameters version**.
239 +** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the section.
240 +** Select **Over the air activation (OTAA)** option under the **Activation mode**
241 +** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities**.
233 233  
234 234  [[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
235 235  
236 236  
237 -* Register end device page continued...
238 -** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network'
239 -** In the **DevEUI** field, enter the **DevEUI**.
240 -** In the **AppKey** field, enter the **AppKey**.
241 -** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
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.
242 242  ** Under **After registration**, select the **View registered end device** option.
243 243  ** Click the **Register end device** button.
244 244  
... ... @@ -253,15 +253,15 @@
253 253  
254 254  ==== 3.2.2.3 Joining ====
255 255  
256 -On the Device overview page, click on **Live data** tab. The Live data panel for your device will display.
265 +Click on **Live data** in the left navigation. The Live data panel for your application will display.
257 257  
258 -Now power on your LT-22222-L. It will begin joining The Things Stack. 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**).
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**).
259 259  
260 260  
261 261  [[image:lt-22222-join-network.png||height="625" width="1000"]]
262 262  
263 263  
264 -By default, you will receive an uplink data message from the device every 10 minutes.
273 +By default, you will receive an uplink data message every 10 minutes.
265 265  
266 266  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.
267 267  
... ... @@ -270,17 +270,13 @@
270 270  
271 271  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.
272 272  
273 -{{info}}
274 -The Things Stack provides two levels of payload formatters: application level and device level. The device-level payload formatters **override **the application-level payload formatters.
275 -{{/info}}
276 -
277 277  [[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
278 278  
279 279  
280 -== 3.3 Working Modes and Uplink Payload formats ==
285 +== 3.3 Work Modes and their Uplink Payload formats ==
281 281  
282 282  
283 -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.
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.
284 284  
285 285  * (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO
286 286  
... ... @@ -294,7 +294,7 @@
294 294  
295 295  * (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5
296 296  
297 -The uplink messages are sent over LoRaWAN FPort=2. By default, an uplink message is sent every 10 minutes.
302 +The uplink messages are sent over LoRaWAN FPort 2. By default, an uplink message is sent every 10 minutes.
298 298  
299 299  === 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
300 300  
... ... @@ -301,12 +301,8 @@
301 301  (((
302 302  This is the default mode.
303 303  
304 -The uplink payload is 11 bytes long.
309 +The uplink payload is 11 bytes long. (% style="display:none" wfd-invisible="true" %)
305 305  
306 -(% style="color:red" %)**Note:The maximum count depends on the bytes number of bytes.
307 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
308 -It starts counting again when it reaches the maximum value.**(% style="display:none" wfd-invisible="true" %)
309 -
310 310  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
311 311  |(% 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**
312 312  |Value|(((
... ... @@ -363,13 +363,9 @@
363 363  * [1] DO2 channel output is LOW, and the DO2 LED is ON.
364 364  * [0] DO1 channel output state:
365 365  ** DO1 is FLOATING when there is no load between DO1 and V+.
366 -** DO1 is HIGH and there is a load between DO1 and V+.
367 +** DO1 is HIGH when there is a load between DO1 and V+.
367 367  ** DO1 LED is OFF in both cases.
368 368  
369 -Reserve = 0
370 -
371 -MOD = 1
372 -
373 373  === 3.3.2 AT+MOD~=2, (Double DI Counting) ===
374 374  
375 375  
... ... @@ -380,10 +380,6 @@
380 380  (((
381 381  The uplink payload is 11 bytes long.
382 382  
383 -(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
384 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
385 -It starts counting again when it reaches the maximum value.**
386 -
387 387  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
388 388  |(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**4**|(% style="background-color:#4f81bd; color:white" %)**4**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**
389 389  |Value|COUNT1|COUNT2 |DIDORO*|(((
... ... @@ -448,9 +448,6 @@
448 448  
449 449  === 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI ===
450 450  
451 -(% style="color:red" %)**Note: The maximum count depends on the bytes it is.
452 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
453 -It starts counting again when it reaches the maximum value.**
454 454  
455 455  **LT22222-L**: In this mode, the DI1 is used as a counting pin.
456 456  
... ... @@ -501,11 +501,7 @@
501 501  
502 502  === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting ===
503 503  
504 -(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
505 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
506 -It starts counting again when it reaches the maximum value.**
507 507  
508 -
509 509  (((
510 510  **LT22222-L**: In this mode, the DI1 is used as a counting pin.
511 511  )))
... ... @@ -558,23 +558,19 @@
558 558  (((
559 559  **In addition to that, below are the commands for AVI1 Counting:**
560 560  
561 -(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI Count to 60)**
547 +(% style="color:blue" %)**AT+SETCNT=3,60**(%%)**  (Sets AVI Count to 60)**
562 562  
563 -(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
549 +(% style="color:blue" %)**AT+VOLMAX=20000**(%%)**  (If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
564 564  
565 -(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
551 +(% style="color:blue" %)**AT+VOLMAX=20000,0**(%%)**  (If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
566 566  
567 -(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
553 +(% style="color:blue" %)**AT+VOLMAX=20000,1**(%%)**  (If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
568 568  )))
569 569  
570 570  
571 571  === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI ===
572 572  
573 -(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
574 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
575 -It starts counting again when it reaches the maximum value.**
576 576  
577 -
578 578  **LT22222-L**: In this mode, the DI1 is used as a counting pin.
579 579  
580 580  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
... ... @@ -625,28 +625,23 @@
625 625  )))
626 626  
627 627  
628 -=== 3.3.6 AT+ADDMOD~=6 (Trigger Mode, Optional) ===
610 +=== 3.3.6 AT+ADDMOD~=6. (Trigger Mode, Optional) ===
629 629  
630 630  
631 -(% style="color:#4f81bd" %)**This mode is optional and intended for trigger purposes. It can operate __alongside__ with other modes.**
613 +(% style="color:#4f81bd" %)**This mode is optional and intended for trigger purposes. It can operate together with other modes.**
632 632  
633 -For example, if you configure the following commands:
615 +For example, if you configured the following commands:
634 634  
635 -* **AT+MOD=1 ** **~-~->**  Sets the default working mode
636 -* **AT+ADDMOD6=1**   **~-~->**  Enables trigger mode
617 +* **AT+MOD=1 ** **~-~->**  The normal working mode
618 +* **AT+ADDMOD6=1**   **~-~->**  Enable trigger mode
637 637  
638 -The LT-22222-L will continuously monitor AV1, AV2, AC1, and AC2 every 5 seconds. It will send uplink packets in two cases:
620 +The LT-22222-L will continuously monitor AV1, AV2, AC1, and AC2 every 5 seconds. LT will send uplink packets in two cases:
639 639  
640 -1. Periodic uplink: Based on TDC time. The payload is the same as in normal mode (MOD=1 as set above). These are (% style="color:#4f81bd" %)**unconfirmed**(%%) uplinks.
641 -1. (((
642 -Trigger uplink: sent when a trigger condition is met. In this case, LT will send two packets
622 +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.
623 +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.**
643 643  
644 -* The first uplink uses the payload specified in trigger mode (MOD=6).
645 -* The second packet uses the normal mode payload (MOD=1 as set above). Both are (% style="color:#4f81bd" %)**confirmed uplinks.**
646 -)))
625 +(% style="color:#037691" %)**AT Command to set Trigger Condition**:
647 647  
648 -(% style="color:#037691" %)**AT Commands to set Trigger Conditions**:
649 -
650 650  (% style="color:#4f81bd" %)**Trigger based on voltage**:
651 651  
652 652  Format: AT+AVLIM=<AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH>
... ... @@ -654,9 +654,9 @@
654 654  
655 655  **Example:**
656 656  
657 -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)
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)
658 658  
659 -AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage lower than 5V. Use 0 for parameters that are not in use)
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)
660 660  
661 661  
662 662  (% style="color:#4f81bd" %)**Trigger based on current**:
... ... @@ -666,7 +666,7 @@
666 666  
667 667  **Example:**
668 668  
669 -AT+ACLIM=10000,15000,0,0 (triggers an uplink if AC1 current is lower than 10mA or higher than 15mA)
646 +AT+ACLIM=10000,15000,0,0   (triggers an uplink if ACI1 voltage is lower than 10mA or higher than 15mA)
670 670  
671 671  
672 672  (% style="color:#4f81bd" %)**Trigger based on DI status**:
... ... @@ -817,249 +817,138 @@
817 817  )))
818 818  
819 819  
820 -== 3.4 ​Configure LT-22222-L via AT Commands or Downlinks ==
797 +== 3.4 ​Configure LT via AT Commands or Downlinks ==
821 821  
799 +
822 822  (((
823 -You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks.
801 +User can configure LT I/O Controller via AT Commands or LoRaWAN Downlinks.
824 824  )))
825 825  
826 826  (((
827 827  (((
828 -There are two tytes of commands:
806 +There are two kinds of Commands:
829 829  )))
830 830  )))
831 831  
832 -* (% style="color:blue" %)**Common commands**(%%):
810 +* (% style="color:blue" %)**Common Commands**(%%): They should be available for each sensor, 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]]
833 833  
834 -* (% style="color:blue" %)**Sensor-related commands**(%%):
812 +* (% style="color:blue" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L.  User can see these commands below:
835 835  
836 -=== 3.4.1 Common commands ===
814 +=== 3.4.1 Common Commands ===
837 837  
838 838  (((
839 -These are available for each sensors and include actions such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]s.
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]].
840 840  )))
841 841  
842 -=== 3.4.2 Sensor-related commands ===
843 843  
844 -These commands are specially designed for the LT-22222-L. Commands can be sent to the device using options such as an AT command or a LoRaWAN downlink payload.
821 +=== 3.4.2 Sensor related commands ===
845 845  
846 -
847 847  ==== 3.4.2.1 Set Transmit Interval ====
848 848  
849 849  Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
850 850  
851 -(% style="color:#037691" %)**AT command**
827 +* (% style="color:#037691" %)**AT command:**
852 852  
853 -(% style="width:500px" %)
854 -|**Command**|AT+TDC<time>
855 -|**Response**|
856 -|**Parameters**|time : uplink interval is in milliseconds
857 -|**Example**|(((
858 -AT+TDC=30000
829 +(% style="color:blue" %)**AT+TDC=N**
859 859  
860 -Sets the uplink interval to 30,000 milliseconds (30 seconds)
861 -)))
831 +where N is the time in milliseconds.
862 862  
863 -(% style="color:#037691" %)**Downlink payload**
833 +**Example: **AT+TDC=30000. This will set the uplink interval to 30 seconds
864 864  
865 -(% style="width:500px" %)
866 -|**Payload**|(((
867 -<prefix><time>
868 -)))
869 -|**Parameters**|(((
870 -prefix : 0x01
871 871  
872 -time : uplink interval is in milliseconds, represented by 3  bytes in hexadecimal.
873 -)))
874 -|**Example**|(((
875 -01 **00 75 30**
836 +* (% style="color:#037691" %)**Downlink payload (prefix 0x01):**
876 876  
877 -Sets the uplink interval to 30,000 milliseconds (30 seconds)
838 +(% style="color:blue" %)**0x01 aa bb cc  **(%%)** ~/~/ Same as AT+TDC=0x(aa bb cc)**
878 878  
879 -Conversion: 30000 (dec) = 00 75 30 (hex)
880 880  
881 -See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]]
882 -)))
883 883  
884 -==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
842 +==== 3.4.2.2 Set the Work Mode (AT+MOD) ====
885 885  
886 -Sets the working mode.
887 887  
888 -(% style="color:#037691" %)**AT command**
845 +Sets the work mode.
889 889  
890 -(% style="width:500px" %)
891 -|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE<working_mode>
892 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)
893 -|(% style="width:97px" %)**Parameters**|(% style="width:413px" %)(((
894 -working_mode :
847 +* (% style="color:#037691" %)**AT command:**(%%) (% style="color:blue" %)**AT+MOD=N  **
895 895  
896 -1 = (Default mode/factory set):  2ACI + 2AVI + DI + DO + RO
849 +Where N is the work mode.
897 897  
898 -2 = Double DI Counting + DO + RO
851 +**Example**: AT+MOD=2. This will set the work mode to Double DI counting mode.
899 899  
900 -3 = Single DI Counting + 2 x ACI + DO + RO
901 901  
902 -4 = Single DI Counting + 1 x Voltage Counting + DO + RO
854 +* (% style="color:#037691" %)**Downlink payload (prefix 0x0A):**
903 903  
904 -5 = Single DI Counting + 2 x AVI + 1 x ACI + DO + RO
856 +(% style="color:blue" %)**0x0A aa  **(%%)** ** ~/~/ Same as AT+MOD=aa
905 905  
906 -6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5
907 -)))
908 -|(% style="width:97px" %)**Example**|(% style="width:413px" %)(((
909 -AT+MOD=2
910 910  
911 -Sets the device to working mode 2 (Double DI Counting + DO + RO)
912 -)))
913 913  
914 -(% class="wikigeneratedid" %)
915 -(% style="color:#037691" %)**Downlink payload**
860 +==== 3.4.2.3 Poll an uplink ====
916 916  
917 -(% style="width:500px" %)
918 -|(% style="width:98px" %)**Payload**|(% style="width:400px" %)<prefix><working_mode>
919 -|(% style="width:98px" %)**Parameters**|(% style="width:400px" %)(((
920 -prefix : 0x0A
921 921  
922 -working_mode : Working mode, represented by 1 byte in hexadecimal.
923 -)))
924 -|(% style="width:98px" %)**Example**|(% style="width:400px" %)(((
925 -0A **02**
863 +Asks the device to send an uplink.
926 926  
927 -Sets the device to working mode 2 (Double DI Counting + DO + RO)
928 -)))
865 +* (% style="color:#037691" %)**AT command:**(%%) There is no AT Command to poll uplink
929 929  
930 -==== 3.4.2.3 Poll an uplink ====
867 +* (% style="color:#037691" %)**Downlink payload (prefix 0x08):**
931 931  
932 -Requests an uplink from LT-22222-L.
869 +(% style="color:blue" %)**0x08 FF  **(%%)** **~/~/ Poll an uplink
933 933  
934 -(% style="color:#037691" %)**AT command**
871 +**Example**: 0x08FF, ask device to send an Uplink
935 935  
936 -There is no AT Command to request an uplink from LT-22222-L
937 937  
938 -(% style="color:#037691" %)**Downlink payload**
939 939  
940 -(% style="width:500px" %)
941 -|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF
942 -|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)prefix : 0x08
943 -|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
944 -08 FF
945 -
946 -Requests an uplink from LT-22222-L.
947 -)))
948 -
949 949  ==== 3.4.2.4 Enable/Disable Trigger Mode ====
950 950  
951 -Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
952 952  
953 -(% style="color:#037691" %)**AT Command**
878 +Enable or disable the trigger mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
954 954  
955 -(% style="width:500px" %)
956 -|(% style="width:95px" %)**Command**|(% style="width:403px" %)AT+ADDMOD6=<enable/disable trigger_mode>
957 -|(% style="width:95px" %)**Response**|(% style="width:403px" %)
958 -|(% style="width:95px" %)**Parameters**|(% style="width:403px" %)(((
959 -enable/disable trigger_mode :
880 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0**
960 960  
961 -1 = enable trigger mode
882 +(% style="color:red" %)**1:** (%%)Enable the trigger mode
962 962  
963 -0 = disable trigger mode
964 -)))
965 -|(% style="width:95px" %)**Example**|(% style="width:403px" %)(((
966 -AT+ADDMOD6=1
884 +(% style="color:red" %)**0: **(%%)Disable the trigger mode
967 967  
968 -Enable trigger mode for the current working mode
969 -)))
970 970  
971 -(% style="color:#037691" %)**Downlink payload**
887 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A 06):**
972 972  
973 -(% style="width:500px" %)
974 -|(% style="width:97px" %)**Payload**|(% style="width:401px" %)<prefix><enable/disable trigger_mode>
975 -|(% style="width:97px" %)**Parameters**|(% style="width:401px" %)(((
976 -prefix : 0x0A 06
889 +(% style="color:blue" %)**0x0A 06 aa    **(%%) ~/~/ Same as AT+ADDMOD6=aa
977 977  
978 -working mode : enable (1) or disable (0), represented by 1 byte in hexadecimal.
979 -)))
980 -|(% style="width:97px" %)**Example**|(% style="width:401px" %)(((
981 -0A 06 **01**
982 982  
983 -Enable trigger mode for the current working mode
984 -)))
985 985  
986 986  ==== 3.4.2.5 Poll trigger settings ====
987 987  
988 -Polls the trigger settings.
989 989  
990 -(% style="color:#037691" %)**AT Command:**
896 +Polls the trigger settings
991 991  
898 +* (% style="color:#037691" %)**AT Command:**
899 +
992 992  There is no AT Command for this feature.
993 993  
994 -(% style="color:#037691" %)**Downlink Payload**
902 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x AB 06):**
995 995  
996 -(% style="width:500px" %)
997 -|(% style="width:95px" %)**Payload**|(% style="width:403px" %)<prefix>
998 -|(% style="width:95px" %)**Parameters**|(% style="width:403px" %)prefix : AB 06
999 -|(% style="width:95px" %)**Example**|(% style="width:403px" %)(((
1000 -AB 06
904 +(% style="color:blue" %)**0xAB 06  ** (%%) ~/~/ Poll the trigger settings. Device will uplink trigger settings once receive this command
1001 1001  
1002 -Uplinks the trigger settings.
1003 -)))
1004 1004  
1005 -==== 3.4.2.6 Enable/Disable DI1/DI2 as a trigger ====
1006 1006  
1007 -Enable or disable DI1/DI2 as a trigger.
908 +==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ====
1008 1008  
1009 -(% style="color:#037691" %)**AT Command**
1010 1010  
1011 -(% style="width:500px" %)
1012 -|(% style="width:98px" %)Command|(% style="width:400px" %)AT+DTRI=<DI1_trigger><DI2_trigger>
1013 -|(% style="width:98px" %)Response|(% style="width:400px" %)
1014 -|(% style="width:98px" %)Parameters|(% style="width:400px" %)(((
1015 -DI1_trigger:
911 +Enable or Disable DI1/DI2/DI2 as trigger,
1016 1016  
1017 -1 = enable DI1 trigger
913 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
1018 1018  
1019 -0 = disable DI1 trigger
915 +**Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
1020 1020  
1021 -DI2 _trigger
1022 1022  
1023 -1 = enable DI2 trigger
918 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 02):**
1024 1024  
1025 -0 = disable DI2 trigger
1026 -)))
1027 -|(% style="width:98px" %)Example|(% style="width:400px" %)(((
1028 -AT+DTRI=1,0
920 +(% style="color:blue" %)**0xAA 02 aa bb   ** (%%) ~/~/ Same as AT+DTRI=aa,bb
1029 1029  
1030 -Enable DI1 trigger, disable DI2 trigger
1031 -)))
1032 1032  
1033 -(% class="wikigeneratedid" %)
1034 -(% style="color:#037691" %)**Downlink Payload**
1035 1035  
1036 -(% style="width:500px" %)
1037 -|(% style="width:101px" %)Payload|(% style="width:397px" %)<prefix><DI1_trigger><DI2_trigger>
1038 -|(% style="width:101px" %)Parameters|(% style="width:397px" %)(((
1039 -prefix : AA 02
924 +==== 3.4.2.7 Trigger1 – Set DI1 or DI3 as trigger ====
1040 1040  
1041 -DI1_trigger:
1042 1042  
1043 -1 = enable DI1 trigger, represented by 1 byte in hexadecimal.
927 +Set DI1 or DI3(for LT-33222-L) trigger.
1044 1044  
1045 -0 = disable DI1 trigger, represented by 1 byte in hexadecimal.
1046 -
1047 -DI2 _trigger
1048 -
1049 -1 = enable DI2 trigger, represented by 1 byte in hexadecimal.
1050 -
1051 -0 = disable DI2 trigger, represented by 1 byte in hexadecimal.
1052 -)))
1053 -|(% style="width:101px" %)Example|(% style="width:397px" %)(((
1054 -AA 02 **01 00**
1055 -
1056 -Enable DI1 trigger, disable DI2 trigger
1057 -)))
1058 -
1059 -==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ====
1060 -
1061 -Sets DI1 or DI3 (for LT-33222-L) as a trigger.
1062 -
1063 1063  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG1=a,b**
1064 1064  
1065 1065  (% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
... ... @@ -1074,16 +1074,11 @@
1074 1074  (% style="color:blue" %)**0x09 01 aa bb cc    ** (%%) ~/~/ same as AT+TRIG1=aa,0x(bb cc)
1075 1075  
1076 1076  
1077 -(% style="width:500px" %)
1078 -|(% style="width:101px" %)Command|(% style="width:397px" %)
1079 -|(% style="width:101px" %)Response|(% style="width:397px" %)
1080 -|(% style="width:101px" %)Parameters|(% style="width:397px" %)
1081 -|(% style="width:101px" %)Example|(% style="width:397px" %)
1082 1082  
944 +==== 3.4.2.8 Trigger2 – Set DI2 as trigger ====
1083 1083  
1084 -==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
1085 1085  
1086 -Sets DI2 as a trigger.
947 +Sets DI2 trigger.
1087 1087  
1088 1088  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b**
1089 1089  
... ... @@ -1091,7 +1091,7 @@
1091 1091  
1092 1092  (% style="color:red" %)**b :** (%%)delay timing.
1093 1093  
1094 -**Example:** AT+TRIG2=0,100 (Set the DI1 port to trigger on a falling edge; the valid signal duration is 100 ms)
955 +**Example:** AT+TRIG2=0,100 (set DI1 port to trigger on low level, valid signal is 100ms )
1095 1095  
1096 1096  
1097 1097  * (% style="color:#037691" %)**Downlink Payload (prefix 0x09 02 ):**
... ... @@ -1099,39 +1099,12 @@
1099 1099  (% style="color:blue" %)**0x09 02 aa bb cc   ** (%%)~/~/ same as AT+TRIG2=aa,0x(bb cc)
1100 1100  
1101 1101  
1102 -(% style="color:#037691" %)**AT Command**
1103 1103  
1104 -(% style="width:500px" %)
1105 -|(% style="width:94px" %)Command|(% style="width:404px" %)AT+TRIG=<interrupt_mode><minimum_signal_duration>
1106 -|(% style="width:94px" %)Response|(% style="width:404px" %)
1107 -|(% style="width:94px" %)Parameters|(% style="width:404px" %)(((
1108 -interrupt_mode :  0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
964 +==== 3.4.2.9 Trigger – Set AC (current) as trigger ====
1109 1109  
1110 -minimum_signal_duration : the **minimum signal duration** required for the DI1 port to recognize a valid trigger.
1111 -)))
1112 -|(% style="width:94px" %)Example|(% style="width:404px" %)(((
1113 -AT+TRIG2=0,100
1114 1114  
1115 -Set the DI1 port to trigger on a falling edge; the valid signal duration is 100 ms.
1116 -)))
967 +Set current trigger , base on AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1117 1117  
1118 -(% style="color:#037691" %)**Downlink Payload**
1119 -
1120 -(% style="width:500px" %)
1121 -|(% style="width:96px" %)Payload|(% style="width:402px" %)<prefix><interrupt_mode><minimum_signal_duration>
1122 -|(% style="width:96px" %)Parameters|(% style="width:402px" %)(((
1123 -prefix : 09 02
1124 -
1125 -interrupt_mode : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal.
1126 -
1127 -<minimum_signal_duration>, represented two bytes in hexadecimal
1128 -)))
1129 -|(% style="width:96px" %)Example|(% style="width:402px" %)09 02 **00 00 64**
1130 -
1131 -==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
1132 -
1133 -Sets the current trigger based on the AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1134 -
1135 1135  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ACLIM**
1136 1136  
1137 1137  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 01 )**
... ... @@ -1139,24 +1139,12 @@
1139 1139  (% style="color:blue" %)**0x AA 01 aa bb cc dd ee ff gg hh        ** (%%) ~/~/ same as AT+ACLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1140 1140  
1141 1141  
1142 -(% style="width:500px" %)
1143 -|(% style="width:104px" %)Command|(% style="width:394px" %)AT+ACLIM
1144 -|(% style="width:104px" %)Response|(% style="width:394px" %)
1145 -|(% style="width:104px" %)Parameters|(% style="width:394px" %)-
1146 -|(% style="width:104px" %)Example|(% style="width:394px" %)AT+ACLIM
1147 1147  
1148 -
1149 -
1150 -(% style="width:500px" %)
1151 -|(% style="width:104px" %)Payload|(% style="width:394px" %)<prefix>
1152 -|(% style="width:104px" %)Parameters|(% style="width:394px" %)prefix : AA 01
1153 -|(% style="width:104px" %)Example|(% style="width:394px" %)AA 01 aa bb cc dd ee ff gg hh
1154 -
1155 -
1156 1156  ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
1157 1157  
1158 -Sets the current trigger based on the AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1159 1159  
980 +Set current trigger , base on AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
981 +
1160 1160  * (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+AVLIM    **(%%)** See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]**
1161 1161  
1162 1162  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 00 )**
... ... @@ -1164,8 +1164,10 @@
1164 1164  (% style="color:blue" %)**0x AA 00 aa bb cc dd ee ff gg hh    ** (%%) ~/~/ same as AT+AVLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1165 1165  
1166 1166  
989 +
1167 1167  ==== 3.4.2.11 Trigger – Set minimum interval ====
1168 1168  
992 +
1169 1169  Sets AV and AC trigger minimum interval. Device won't response to the second trigger within this set time after the first trigger.
1170 1170  
1171 1171  * (% 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.
... ... @@ -1182,7 +1182,6 @@
1182 1182  
1183 1183  ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
1184 1184  
1185 -Controls the digital outputs DO1, DO2, and DO3
1186 1186  
1187 1187  * (% style="color:#037691" %)**AT Command**
1188 1188  
... ... @@ -1560,25 +1560,25 @@
1560 1560  
1561 1561  == 3.5 Integrating with ThingsEye.io ==
1562 1562  
1563 -The Things Stack application supports integration with ThingsEye.io. Once integrated, ThingsEye.io acts as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
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.
1564 1564  
1565 -=== 3.5.1 Configuring The Things Stack ===
1388 +=== 3.5.1 Configuring MQTT Connection Information with The Things Stack Sandbox ===
1566 1566  
1567 -We use The Things Stack Sandbox in this example:
1390 +We use The Things Stack Sandbox for demonstating the configuration but  other
1568 1568  
1569 -* In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
1570 -* Select **MQTT** under **Integrations** in the left menu.
1571 -* In the **Connection information **section, under **Connection credentials**, The Things Stack displays an auto-generated **username**. You can use it or provide a new one.
1572 -* Click the **Generate new API key** button to generate a password. You can view it by clicking on the **visibility toggle/eye** icon. The API key works as the password.
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.
1573 1573  
1574 -{{info}}
1575 -The username and  password (API key) you created here are required in the next section.
1576 -{{/info}}
1397 +NOTE. The username and  password (API key) you created here are required in the next section.
1577 1577  
1578 1578  [[image:tts-mqtt-integration.png||height="625" width="1000"]]
1579 1579  
1580 1580  === 3.5.2 Configuring ThingsEye.io ===
1581 1581  
1403 +This section guides you on how to create an integration in ThingsEye to connect with The Things Stack MQTT server.
1404 +
1582 1582  * Login to your [[ThingsEye.io >>https://thingseye.io]]account.
1583 1583  * Under the **Integrations center**, click **Integrations**.
1584 1584  * Click the **Add integration** button (the button with the **+** symbol).
... ... @@ -1615,9 +1615,9 @@
1615 1615  **Downlink data converter (this is an optional step):**
1616 1616  
1617 1617  * Click the **Create new** button if it is not selected by default.
1618 -* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name.
1441 +* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name
1619 1619  * Click the **JavaScript** button.
1620 -* Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Downlink_Converter.js]].
1443 +* Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found here.
1621 1621  * Click the **Next** button. You will be navigated to the **Connection** tab.
1622 1622  
1623 1623  [[image:thingseye-io-step-4.png||height="625" width="1000"]]
... ... @@ -1627,7 +1627,7 @@
1627 1627  
1628 1628  * Choose **Region** from the **Host type**.
1629 1629  * 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/...).
1630 -* 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 The Things Stack).
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).
1631 1631  * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
1632 1632  
1633 1633  [[image:message-1.png]]
... ... @@ -1644,9 +1644,9 @@
1644 1644  [[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
1645 1645  
1646 1646  
1647 -==== 3.5.2.1 Viewing integration details ====
1470 +**Viewing integration details**:
1648 1648  
1649 -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.
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.
1650 1650  
1651 1651  [[image:integration-details.png||height="686" width="1000"]]
1652 1652  
... ... @@ -1653,30 +1653,29 @@
1653 1653  
1654 1654  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.
1655 1655  
1656 -{{info}}
1657 -See also ThingsEye documentation.
1658 -{{/info}}
1479 +Note: See also ThingsEye documentation.
1659 1659  
1660 -==== **3.5.2.2 Viewing events** ====
1661 1661  
1662 -The **Events **tab displays all the uplink messages from the LT-22222-L.
1482 +**Viewing events:**
1663 1663  
1484 +This tab  displays all the uplink messages from the LT-22222-L.
1485 +
1486 +* Click on the **Events **tab.
1664 1664  * Select **Debug **from the **Event type** dropdown.
1665 1665  * Select the** time frame** from the **time window**.
1666 1666  
1667 -[[image:thingseye-events.png||height="686" width="1000"]]
1490 +[insert image]
1668 1668  
1492 +- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
1669 1669  
1670 -* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
1494 +[insert image]
1671 1671  
1672 -[[image:thingseye-json.png||width="1000"]]
1673 1673  
1497 +**Deleting the integration**:
1674 1674  
1675 -==== **3.5.2.3 Deleting an integration** ====
1499 +If you want to delete this integration, click the **Delete integratio**n button.
1676 1676  
1677 -If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
1678 1678  
1679 -
1680 1680  == 3.6 Interface Details ==
1681 1681  
1682 1682  === 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) ===
... ... @@ -1687,7 +1687,7 @@
1687 1687  [[image:1653356991268-289.png]]
1688 1688  
1689 1689  
1690 -=== 3.6.2 Digital Input Ports: DI1/DI2 ===
1512 +=== 3.6.2 Digital Input Ports: DI1/DI2 ( For LT-22222-L) ===
1691 1691  
1692 1692  
1693 1693  (((
... ... @@ -1817,7 +1817,7 @@
1817 1817  [[image:image-20240219115718-1.png]]
1818 1818  
1819 1819  
1820 -=== 3.6.3 Digital Output Ports: DO1/DO2 ===
1642 +=== 3.6.3 Digital Output Ports: DO1/DO2 /DO3 ===
1821 1821  
1822 1822  
1823 1823  (% style="color:blue" %)**NPN output**(%%): GND or Float. The maximum voltage that can be applied to the output pin is 36V.
... ... @@ -1890,11 +1890,10 @@
1890 1890  
1891 1891  == 3.7 LEDs Indicators ==
1892 1892  
1893 -The table below lists the behavior of LED indicators for each port function.
1894 1894  
1895 1895  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1896 1896  |(% style="background-color:#4f81bd; color:white; width:50px" %)**LEDs**|(% style="background-color:#4f81bd; color:white; width:460px" %)**Feature**
1897 -|**PWR**|Always on when there is power
1718 +|**PWR**|Always on if there is power
1898 1898  |**TX**|(((
1899 1899  (((
1900 1900  Device boot: TX blinks 5 times.
... ... @@ -1901,7 +1901,7 @@
1901 1901  )))
1902 1902  
1903 1903  (((
1904 -Successful network join: TX remains ON for 5 seconds.
1725 +Successful join network: TX ON for 5 seconds.
1905 1905  )))
1906 1906  
1907 1907  (((
... ... @@ -1908,7 +1908,7 @@
1908 1908  Transmit a LoRa packet: TX blinks once
1909 1909  )))
1910 1910  )))
1911 -|**RX**|RX blinks once when a packet is received.
1732 +|**RX**|RX blinks once when receiving a packet.
1912 1912  |**DO1**|For LT-22222-L: ON when DO1 is low, OFF when DO1 is high
1913 1913  |**DO2**|For LT-22222-L: ON when DO2 is low, OFF when DO2 is high
1914 1914  |**DI1**|(((
... ... @@ -1928,10 +1928,9 @@
1928 1928  
1929 1929  (((
1930 1930  You can use a USB-to-TTL adapter along with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below.
1931 -
1932 -[[image:usb-ttl-programming.png]]
1933 1933  )))
1934 1934  
1754 +[[image:1653358238933-385.png]]
1935 1935  
1936 1936  
1937 1937  (((
... ... @@ -1948,21 +1948,21 @@
1948 1948  )))
1949 1949  
1950 1950  (((
1951 -The following is the list of all the AT commands related to the LT-22222-L, except for those used for switching between working modes.
1771 +The following is the list of all the AT commands related to the LT-22222-L, except for those used for switching between work modes.
1952 1952  
1953 -* **##AT##+<CMD>?** : Help on <CMD>
1954 -* **##AT##+<CMD>** : Run <CMD>
1955 -* **##AT##+<CMD>=<value>** : Set the value
1956 -* **##AT##+<CMD>=?** : Get the value
1957 -* ##**ATZ**##: Trigger a reset of the MCU
1773 +* AT+<CMD>? : Help on <CMD>
1774 +* AT+<CMD> : Run <CMD>
1775 +* AT+<CMD>=<value> : Set the value
1776 +* AT+<CMD>=? : Get the value
1777 +* ATZ: Trigger a reset of the MCU
1958 1958  * ##**AT+FDR**##: Reset Parameters to factory default, reserve keys 
1959 1959  * **##AT+DEUI##**: Get or set the Device EUI (DevEUI)
1960 1960  * **##AT+DADDR##**: Get or set the Device Address (DevAddr)
1961 1961  * **##AT+APPKEY##**: Get or set the Application Key (AppKey)
1962 -* ##**AT+NWKSKEY**##: Get or set the Network Session Key (NwkSKey)
1963 -* **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
1964 -* **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
1965 -* **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
1782 +* AT+NWKSKEY: Get or set the Network Session Key (NwkSKey)
1783 +* AT+APPSKEY: Get or set the Application Session Key (AppSKey)
1784 +* AT+APPEUI: Get or set the Application EUI (AppEUI)
1785 +* AT+ADR: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
1966 1966  * AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
1967 1967  * AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
1968 1968  * AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
... ... @@ -2007,28 +2007,28 @@
2007 2007  
2008 2008  
2009 2009  (((
2010 -(% style="color:blue" %)**If the device has not yet joined the network:**
1830 +(% style="color:blue" %)**If the device has not joined the network yet:**
2011 2011  )))
2012 2012  )))
2013 2013  
2014 2014  (((
2015 -(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**##
1835 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**##
2016 2016  )))
2017 2017  
2018 2018  (((
2019 -(% style="background-color:#dcdcdc" %)##**AT+FDR ~/~/Reset parameters to factory default, Reserve keys**##
1839 +(% style="background-color:#dcdcdc" %)##**AT+FDR ~/~/reset parameters to factory default, reserve keys**##
2020 2020  )))
2021 2021  
2022 2022  (((
2023 -(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**##
1843 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**##
2024 2024  )))
2025 2025  
2026 2026  (((
2027 -(% style="background-color:#dcdcdc" %)##**AT+NJM=0 ~/~/Set to ABP mode**##
1847 +(% style="background-color:#dcdcdc" %)##**AT+NJM=0 ~/~/set to ABP mode**##
2028 2028  )))
2029 2029  
2030 2030  (((
2031 -(% style="background-color:#dcdcdc" %)##**ATZ ~/~/Reset MCU**##
1851 +(% style="background-color:#dcdcdc" %)##**ATZ ~/~/reset MCU**##
2032 2032  )))
2033 2033  
2034 2034  
... ... @@ -2051,20 +2051,20 @@
2051 2051  
2052 2052  
2053 2053  (((
2054 -(% style="background-color:#dcdcdc" %)**123456**(%%)  ~/~/ Enter password to enable AT commands access
1874 +(% style="background-color:#dcdcdc" %)**123456**(%%)  ~/~/ Enter Password to have AT access.
2055 2055  )))
2056 2056  )))
2057 2057  
2058 2058  (((
2059 -(% style="background-color:#dcdcdc" %)** AT+FDR**(%%)  ~/~/ Reset parameters to Factory Default, Reserve keys
1879 +(% style="background-color:#dcdcdc" %)** AT+FDR**(%%)  ~/~/ Reset Parameters to Factory Default, Keys Reserve
2060 2060  )))
2061 2061  
2062 2062  (((
2063 -(% style="background-color:#dcdcdc" %)** 123456**(%%)  ~/~/ Enter password to enable AT commands access
1883 +(% style="background-color:#dcdcdc" %)** 123456**(%%)  ~/~/ Enter Password to have AT access.
2064 2064  )))
2065 2065  
2066 2066  (((
2067 -(% style="background-color:#dcdcdc" %)** AT+CLASS=C**(%%)  ~/~/ Set to CLASS C mode
1887 +(% style="background-color:#dcdcdc" %)** AT+CLASS=C**(%%)  ~/~/ Set to work in CLASS C
2068 2068  )))
2069 2069  
2070 2070  (((
... ... @@ -2084,19 +2084,19 @@
2084 2084  )))
2085 2085  
2086 2086  (((
2087 -(% style="background-color:#dcdcdc" %)** AT+CHS=868400000**(%%)  ~/~/ Set transmit frequency to 868.4 MHz
1907 +(% style="background-color:#dcdcdc" %)** AT+CHS=868400000**(%%)  ~/~/ Set transmit frequency to 868.4Mhz
2088 2088  )))
2089 2089  
2090 2090  (((
2091 -(% style="background-color:#dcdcdc" %)** AT+RX2FQ=868400000**(%%)  ~/~/ Set RX2 frequency to 868.4 MHz (according to the result from the server)
1911 +(% style="background-color:#dcdcdc" %)** AT+RX2FQ=868400000**(%%)  ~/~/ Set RX2Frequency to 868.4Mhz (according to the result from server)
2092 2092  )))
2093 2093  
2094 2094  (((
2095 -(% style="background-color:#dcdcdc" %)** AT+RX2DR=5**(%%)** ** ~/~/ Set RX2 DR to match the downlink DR from the server. See below.
1915 +(% style="background-color:#dcdcdc" %)** AT+RX2DR=5**(%%)** ** ~/~/ Set RX2DR to match the downlink DR from server. see below
2096 2096  )))
2097 2097  
2098 2098  (((
2099 -(% style="background-color:#dcdcdc" %)** AT+DADDR=26 01 1A F1** (%%) ~/~/ Set Device Address. The Device Address can be found in the application on the LoRaWAN NS.
1919 +(% style="background-color:#dcdcdc" %)** AT+DADDR=26 01 1A F1** (%%) ~/~/ Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
2100 2100  )))
2101 2101  
2102 2102  (((
... ... @@ -2110,14 +2110,14 @@
2110 2110  )))
2111 2111  
2112 2112  (((
2113 -**~1. Ensure that the device is set to ABP mode in the LoRaWAN Network Server.**
1933 +**~1. Make sure the device is set to ABP mode in the IoT Server.**
2114 2114  
2115 -**2. Verify that the LG01/02 gateway RX frequency matches the AT+CHS setting exactly.**
1935 +**2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.**
2116 2116  
2117 -**3. Make sure the SF/bandwidth settings in the LG01/LG02 match the settings of AT+DR. Refer to [[this link>>url:http://www.dragino.com/downloads/index.php?
1937 +**3. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?
2118 2118  dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.**
2119 2119  
2120 -**4. The commands AT+RX2FQ and AT+RX2DR enable downlink functionality. To set the correct parameters, you can check the actual downlink parameters to be used as shown below. Here, RX2FQ should be set to 868400000 and RX2DR should be set to 5.**
1940 +**4. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5.**
2121 2121  )))
2122 2122  
2123 2123  (((
... ... @@ -2129,7 +2129,7 @@
2129 2129  
2130 2130  
2131 2131  (((
2132 -(% style="color:blue" %)**If the sensor has JOINED:**
1952 +(% style="color:blue" %)**If sensor JOINED:**
2133 2133  
2134 2134  (% style="background-color:#dcdcdc" %)**AT+CLASS=A**
2135 2135  
... ... @@ -2139,20 +2139,22 @@
2139 2139  
2140 2140  = 5. Case Study =
2141 2141  
2142 -== 5.1 Counting how many objects pass through the flow line ==
1962 +== 5.1 Counting how many objects pass through the flow Line ==
2143 2143  
2144 -See [[How to set up to setup counting for objects passing through the flow line>>How to set up to count objects pass in flow line]]?
2145 2145  
1965 +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]]?
2146 2146  
1967 +
2147 2147  = 6. FAQ =
2148 2148  
2149 2149  This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
2150 2150  
2151 -
2152 2152  == 6.1 How to update the firmware? ==
2153 2153  
2154 -Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to:
1974 +Dragino frequently releases firmware updates for the LT-22222-L.
2155 2155  
1976 +Updating your LT-22222-L with the latest firmware version helps to:
1977 +
2156 2156  * Support new features
2157 2157  * Fix bugs
2158 2158  * Change LoRaWAN frequency bands
... ... @@ -2170,8 +2170,8 @@
2170 2170  
2171 2171  Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2172 2172  
2173 -[[image:usb-ttl-programming.png]]
2174 2174  
1996 +[[image:1653359603330-121.png]]
2175 2175  
2176 2176  
2177 2177  Start the STM32 Flash Loader and choose the correct COM port to update.
... ... @@ -2195,7 +2195,7 @@
2195 2195  [[image:image-20220524104033-15.png]]
2196 2196  
2197 2197  
2198 -(% style="color:red" %)**Note**(%%): If you have lost the programming cable, you can make one from a 3.5 mm cable. The pin mapping is as follows:
2020 +(% 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:
2199 2199  
2200 2200  [[image:1653360054704-518.png||height="186" width="745"]]
2201 2201  
... ... @@ -2203,6 +2203,8 @@
2203 2203  (((
2204 2204  (((
2205 2205  == 6.2 How to change the LoRaWAN frequency band/region? ==
2028 +
2029 +
2206 2206  )))
2207 2207  )))
2208 2208  
... ... @@ -2213,18 +2213,20 @@
2213 2213  (((
2214 2214  
2215 2215  
2216 -== 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
2040 +== 6.3 How to setup LT to work with a Single Channel Gateway, such as LG01/LG02? ==
2041 +
2042 +
2217 2217  )))
2218 2218  
2219 2219  (((
2220 2220  (((
2221 -In this case, you need to set the LT-22222-L to work in ABP mode and transmit on only one frequency.
2047 +In this case, you need to set the LT-33222-L to work in ABP mode and transmit on only one frequency.
2222 2222  )))
2223 2223  )))
2224 2224  
2225 2225  (((
2226 2226  (((
2227 -We assume you have an LG01/LG02 working on the frequency 868400000. Below are the steps.
2053 +Assume you have an LG02 working on the frequency 868400000. Below are the steps.
2228 2228  
2229 2229  
2230 2230  )))
... ... @@ -2231,55 +2231,52 @@
2231 2231  )))
2232 2232  
2233 2233  (((
2234 -(% style="color:#0000ff" %)**Step 1**(%%): Log in to The Things Stack Sandbox account and create an ABP device in the application. To do this, use the manual registration option as explained in section 3.2.2.2, //Adding a Device Manually//. Select //Activation by Personalization (ABP)// under Activation Mode. Enter the DevEUI exactly as shown on the registration information sticker, then generate the Device Address, Application Session Key (AppSKey), and Network Session Key (NwkSKey).
2060 +(% 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.
2235 2235  
2236 -[[image:lt-22222-l-abp.png||height="686" width="1000"]]
2062 +
2237 2237  )))
2238 2238  
2239 2239  (((
2066 +[[image:1653360231087-571.png||height="401" width="727"]]
2067 +
2240 2240  
2241 2241  )))
2242 2242  
2243 -{{warning}}
2244 -Ensure that the Device Address (DevAddr) and the two keys match between the LT-22222-L and The Things Stack. You can modify them either in The Things Stack or on the LT-22222-L to make them align. In The Things Stack, you can configure the NwkSKey and AppSKey on the settings page, but note that the Device Address is generated by The Things Stack.
2245 -{{/warning}}
2071 +(((
2072 +(% style="color:red" %)**Note: user just need to make sure above three keys match, User can change either in TTN or Device to make then match. In TTN, NETSKEY and APPSKEY can be configured by user in setting page, but Device Addr is generated by TTN.**
2073 +)))
2246 2246  
2247 2247  
2076 +
2248 2248  (((
2249 -(% style="color:blue" %)**Step 2**(%%)**:  **(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)Run AT commands to configure the LT-22222-L to operate in single-frequency and ABP mode. The AT commands are as follows:
2078 +(% style="color:blue" %)**Step2**(%%)**:  **Run AT Command to make LT work in Single frequency & ABP mode. Below is the AT commands:
2250 2250  
2251 2251  
2252 2252  )))
2253 2253  
2254 2254  (((
2255 -(% style="background-color:#dcdcdc" %)**123456** (%%) : Enter the password to enable AT access.
2084 +(% style="background-color:#dcdcdc" %)**123456** (%%) :  Enter Password to have AT access.
2256 2256  
2257 -(% style="background-color:#dcdcdc" %)**AT+FDR**(%%) : Reset parameters to factory default, keeping keys reserved.
2086 +(% style="background-color:#dcdcdc" %)**AT+FDR**(%%)  :  Reset Parameters to Factory Default, Keys Reserve
2258 2258  
2259 -(% style="background-color:#dcdcdc" %)**AT+NJM=0** (%%) : Set to ABP mode.
2088 +(% style="background-color:#dcdcdc" %)**AT+NJM=0** (%%) :  Set to ABP mode
2260 2260  
2261 -(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%) : Disable the Adaptive Data Rate (ADR).
2090 +(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%) :  Set the Adaptive Data Rate Off
2262 2262  
2263 -(% style="background-color:#dcdcdc" %)**AT+DR=5** (%%) : Set Data Rate (Use AT+DR=3 for the 915 MHz band).
2092 +(% style="background-color:#dcdcdc" %)**AT+DR=5** (%%) :  Set Data Rate (Set AT+DR=3 for 915 band)
2264 2264  
2265 -(% style="background-color:#dcdcdc" %)**AT+TDC=60000 **(%%) : Set transmit interval to 60 seconds.
2094 +(% style="background-color:#dcdcdc" %)**AT+TDC=60000 **(%%) :  Set transmit interval to 60 seconds
2266 2266  
2267 -(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) : Set transmit frequency to 868.4 MHz.
2096 +(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) : Set transmit frequency to 868.4Mhz
2268 2268  
2269 -(% style="background-color:#dcdcdc" %)**AT+DADDR=xxxx**(%%) : Set the Device Address (DevAddr)
2098 +(% style="background-color:#dcdcdc" %)**AT+DADDR=26 01 1A F1**(%%)  :  Set Device Address to 26 01 1A F1
2270 2270  
2271 -(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:700; text-decoration:none; white-space:pre-wrap" %)**AT+APPKEY=xxxx**(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %): Get or set the Application Key (AppKey)
2272 -
2273 -(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)**AT+NWKSKEY=xxxx**: Get or set the Network Session Key (NwkSKey)
2274 -
2275 -(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)**AT+APPSKEY=xxxx**: Get or set the Application Session Key (AppSKey)
2276 -
2277 -(% style="background-color:#dcdcdc" %)**ATZ**        (%%) : Reset MCU.
2100 +(% style="background-color:#dcdcdc" %)**ATZ**        (%%) :  Reset MCU
2278 2278  )))
2279 2279  
2280 2280  
2281 2281  (((
2282 -(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)The following figure shows the screenshot of the command set above, issued using a serial tool:
2105 +As shown in below:
2283 2283  )))
2284 2284  
2285 2285  [[image:1653360498588-932.png||height="485" width="726"]]
... ... @@ -2287,25 +2287,27 @@
2287 2287  
2288 2288  == 6.4 How to change the uplink interval? ==
2289 2289  
2113 +
2290 2290  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/]]
2291 2291  
2292 2292  
2293 2293  == 6.5 Can I see the counting event in the serial output? ==
2294 2294  
2119 +
2295 2295  (((
2296 -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.
2121 +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.
2297 2297  
2298 2298  
2299 2299  == 6.6 Can I use point-to-point communication with LT-22222-L? ==
2300 2300  
2301 -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]].
2302 2302  
2303 -
2127 +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]].
2304 2304  )))
2305 2305  
2306 2306  (((
2307 2307  == 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
2308 2308  
2133 +
2309 2309  * If the device is not properly shut down and is directly powered off.
2310 2310  * It will default to a power-off state.
2311 2311  * In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
... ... @@ -2313,6 +2313,7 @@
2313 2313  
2314 2314  == 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
2315 2315  
2141 +
2316 2316  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:
2317 2317  
2318 2318  
... ... @@ -2321,24 +2321,24 @@
2321 2321  
2322 2322  == 6.9 Can the LT-22222-L save the RO state? ==
2323 2323  
2324 -To enable this feature, the firmware version must be 1.6.0 or higher.
2325 2325  
2151 +The firmware version must be at least 1.6.0.
2326 2326  
2153 +
2327 2327  == 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
2328 2328  
2156 +
2329 2329  It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
2330 2330  
2331 2331  
2332 2332  = 7. Troubleshooting =
2333 -
2334 -This section provides some known troubleshooting tips.
2335 -
2336 -
2337 2337  )))
2338 2338  
2339 2339  (((
2340 2340  (((
2341 2341  == 7.1 Downlink isn't working. How can I solve this? ==
2166 +
2167 +
2342 2342  )))
2343 2343  )))
2344 2344  
... ... @@ -2350,6 +2350,8 @@
2350 2350  
2351 2351  
2352 2352  == 7.2 Having trouble uploading an image? ==
2179 +
2180 +
2353 2353  )))
2354 2354  
2355 2355  (((
... ... @@ -2360,6 +2360,8 @@
2360 2360  
2361 2361  
2362 2362  == 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
2191 +
2192 +
2363 2363  )))
2364 2364  
2365 2365  (((
... ... @@ -2367,8 +2367,9 @@
2367 2367  )))
2368 2368  
2369 2369  
2370 -== 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? ==
2200 +== 7.4 Why can the LT-22222-L perform Uplink normally, but cannot receive Downlink? ==
2371 2371  
2202 +
2372 2372  The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
2373 2373  Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2374 2374  
... ... @@ -2375,6 +2375,7 @@
2375 2375  
2376 2376  = 8. Ordering information =
2377 2377  
2209 +
2378 2378  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
2379 2379  
2380 2380  (% style="color:#4f81bd" %)**XXX:**
... ... @@ -2389,14 +2389,15 @@
2389 2389  * (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865
2390 2390  * (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779
2391 2391  
2392 -= 9. Package information =
2224 += 9. Packing information =
2393 2393  
2226 +
2394 2394  **Package includes**:
2395 2395  
2396 -* 1 x LT-22222-L I/O Controller
2397 -* 1 x LoRa antenna matched to the frequency of the LT-22222-L
2398 -* 1 x bracket for DIN rail mounting
2399 -* 1 x 3.5 mm programming cable
2229 +* LT-22222-L I/O Controller x 1
2230 +* Stick Antenna for LoRa RF part x 1
2231 +* Bracket for controller x1
2232 +* 3.5mm Programming cable x 1
2400 2400  
2401 2401  **Dimension and weight**:
2402 2402  
... ... @@ -2407,6 +2407,7 @@
2407 2407  
2408 2408  = 10. Support =
2409 2409  
2243 +
2410 2410  * (((
2411 2411  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.
2412 2412  )))
... ... @@ -2418,6 +2418,7 @@
2418 2418  
2419 2419  = 11. Reference​​​​​ =
2420 2420  
2255 +
2421 2421  * LT-22222-L: [[http:~~/~~/www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html>>url:http://www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html]]
2422 2422  * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]]
2423 2423  * [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]
lt-22222-l-abp.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -321.4 KB
Content
thingseye-json.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -554.8 KB
Content
usb-ttl-programming.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -462.9 KB
Content

Applications

Navigation

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