Skip to Content
Last modified by Mengting Qiu on 2025/06/04 18:42
From version 185.1
edited by Dilisi S
on 2024/11/10 05:32
Change comment: Nov 9 edits (saturday)
To version 163.1
edited by Dilisi S
on 2024/11/06 04:29
Change comment: minor edits set 1

Summary

Details

Page properties
Content
... ... @@ -33,12 +33,14 @@
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 +
36 36  (((
37 37  You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways:
38 38  
39 39  * If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Network), you can select a network and register the LT-22222-L I/O controller with it.
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 -* Setup your own private LoRaWAN network.
43 +* Set up your own private LoRaWAN network.
42 42  
43 43  > You can use a LoRaWAN gateway, such as the Dragino LG308, to expand or create LoRaWAN coverage in your area.
44 44  )))
... ... @@ -57,7 +57,7 @@
57 57  * SX1276/78 Wireless Chip 
58 58  * Power Consumption:
59 59  ** Idle: 4mA@12v
60 -** 20dB Transmit: 34mA@12V
62 +** 20dB Transmit: 34mA@12v
61 61  * Operating Temperature: -40 ~~ 85 Degrees, No Dew
62 62  
63 63  (% style="color:#037691" %)**Interface for Model: LT22222-L:**
... ... @@ -66,7 +66,7 @@
66 66  * 2 x Digital Output (NPN output. Max pull-up voltage 36V,450mA)
67 67  * 2 x Relay Output (5A@250VAC / 30VDC)
68 68  * 2 x 0~~20mA Analog Input (res:0.01mA)
69 -* 2 x 0~~30V Analog Input (res:0.01V)
71 +* 2 x 0~~30V Analog Input (res:0.01v)
70 70  * Power Input 7~~ 24V DC. 
71 71  
72 72  (% style="color:#037691" %)**LoRa Spec:**
... ... @@ -126,14 +126,21 @@
126 126  * 1 x Counting Port
127 127  )))
128 128  
129 -= 2. Assembling =
131 += 2. Assembling the Device =
130 130  
131 -Attach 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.
133 +== 2.1 What is included in the package? ==
132 132  
133 -== 2.2 Terminals ==
135 +The package includes the following items:
134 134  
135 -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.
137 +* 1 x LT-22222-L I/O Controller
138 +* 1 x LoRaWAN antenna matched to the frequency of the LT-22222-L
139 +* 1 x bracket for wall mounting
140 +* 1 x programming cable
136 136  
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.
143 +
144 +== 2.2 Terminals ==
145 +
137 137  Upper screw terminal block (from left to right):
138 138  
139 139  (% style="width:634px" %)
... ... @@ -160,32 +160,28 @@
160 160  |(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
161 161  |(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
162 162  
163 -== 2.3 Powering the device ==
172 +== 2.3 Powering the LT-22222-L  ==
164 164  
165 -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.
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.
166 166  
167 -Powering on the device
168 168  
169 -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.
170 -
171 -{{warning}}
172 -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.
173 -{{/warning}}
174 -
175 -
176 176  [[image:1653297104069-180.png]]
177 177  
178 178  
179 -= 3. Registering with a LoRaWAN Network Server =
180 += 3. Operation Mode =
180 180  
182 +== 3.1 How does it work? ==
183 +
181 181  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.
182 182  
183 -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.
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 184  
185 185  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.
186 186  
187 -The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
190 +== 3.2 Registering with a LoRaWAN network server ==
188 188  
192 +The diagram below shows how the LT-22222-L connects to a typical LoRaWAN network.
193 +
189 189  [[image:image-20220523172350-1.png||height="266" width="864"]]
190 190  
191 191  === 3.2.1 Prerequisites ===
... ... @@ -198,104 +198,66 @@
198 198  
199 199  === 3.2.2 The Things Stack Sandbox (TTSS) ===
200 200  
201 -The Things Stack Sandbox was formally called The Things Stack Community Edition.
202 -
203 203  * Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account.
204 -* Create an application with The Things Stack if you do not have one yet.
205 -* Go to your application page and click on the **End devices** in the left menu.
206 -* On the End devices page, click on **+ Register end device**. Two registration options are available:
207 +* Create an application if you do not have one yet.
208 +* Register LT-22222-L with that application. Two registration options are available:
207 207  
210 +==== Using the LoRaWAN Device Repository: ====
208 208  
209 -==== 3.2.2.1 Using the LoRaWAN Device Repository ====
210 -
212 +* Go to your application and click on the **Register end device** button.
211 211  * On the **Register end device** page:
212 -** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
213 -** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists.
214 -*** **End device brand**: Dragino Technology Co., Limited
215 -*** **Model**: LT22222-L I/O Controller
216 -*** **Hardware ver**: Unknown
217 -*** **Firmware ver**: 1.6.0
218 -*** **Profile (Region)**: Select the region that matches your device.
219 -** 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.
220 220  
221 221  [[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
222 222  
223 -
224 -* Register end device page continued...
225 -** 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'.
226 -** In the **DevEUI** field, enter the **DevEUI**.
227 -** In the **AppKey** field, enter the **AppKey.**
228 -** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
220 +*
221 +** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
222 +** Enter the **DevEUI** in the **DevEUI** field.
223 +** Enter the **AppKey** in the **AppKey** field.
224 +** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
229 229  ** Under **After registration**, select the **View registered end device** option.
230 230  
231 231  [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
232 232  
233 -==== ====
229 +==== Entering device information manually: ====
234 234  
235 -==== 3.2.2.2 Adding device manually ====
236 -
237 237  * On the **Register end device** page:
238 -** Select the option **Enter end device specifies manually** under **Input method**.
239 -** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
240 -** Select the **LoRaWAN version** as **LoRaWAN Specification 1.0.3**
241 -** Select the **Regional Parameters version** as** RP001 Regional Parameters 1.0.3 revision A**
242 -** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the hidden section.
243 -** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
244 -** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
232 +** Select the **Enter end device specifies manually** option as the input method.
233 +** Select the **Frequency plan** that matches your device.
234 +** Select the **LoRaWAN version**.
235 +** Select the **Regional Parameters version**.
236 +** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the section.
237 +** Select **Over the air activation (OTAA)** option under the **Activation mode**
238 +** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities**.
245 245  
246 246  [[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
247 247  
248 248  
249 -* Register end device page continued...
250 -** 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'
251 -** In the **DevEUI** field, enter the **DevEUI**.
252 -** In the **AppKey** field, enter the **AppKey**.
253 -** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
254 -** Under **After registration**, select the **View registered end device** option.
255 -** Click the **Register end device** button.
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.
256 256  
257 257  [[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
258 258  
259 259  
260 -You will be navigated to the **Device overview** page.
252 +==== Joining ====
261 261  
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.
262 262  
263 -[[image:lt-22222-device-overview.png||height="625" width="1000"]]
256 +[[image:1653298044601-602.png||height="405" width="709"]]
264 264  
265 265  
266 -==== 3.2.2.3 Joining ====
259 +== 3.3 Uplink Payload formats ==
267 267  
268 -On the Device overview page, click on **Live data** tab. The Live data panel for your device will display.
269 269  
270 -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**).
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.
271 271  
264 +* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2 x ACI + 2AVI + DI + DO + RO
272 272  
273 -[[image:lt-22222-join-network.png||height="625" width="1000"]]
274 -
275 -
276 -By default, you will receive an uplink data message from the device every 10 minutes.
277 -
278 -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.
279 -
280 -[[image:lt-22222-ul-payload-decoded.png]]
281 -
282 -
283 -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.
284 -
285 -{{info}}
286 -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.
287 -{{/info}}
288 -
289 -[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
290 -
291 -
292 -== 3.3 Work Modes and their Uplink Payload formats ==
293 -
294 -
295 -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.
296 -
297 -* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO
298 -
299 299  * (% style="color:blue" %)**MOD2**(%%): Double DI Counting + DO + RO
300 300  
301 301  * (% style="color:blue" %)**MOD3**(%%): Single DI Counting + 2 x ACI + DO + RO
... ... @@ -306,15 +306,12 @@
306 306  
307 307  * (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5
308 308  
309 -The uplink messages are sent over LoRaWAN FPort 2. By default, an uplink message is sent every 10 minutes.
310 -
311 311  === 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
312 312  
278 +
313 313  (((
314 -This is the default mode.
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" %)
315 315  
316 -The uplink payload is 11 bytes long. (% style="display:none" wfd-invisible="true" %)
317 -
318 318  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
319 319  |(% 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**
320 320  |Value|(((
... ... @@ -325,13 +325,13 @@
325 325  ACI1 Current
326 326  )))|(((
327 327  ACI2 Current
328 -)))|**DIDORO***|(((
292 +)))|DIDORO*|(((
329 329  Reserve
330 330  )))|MOD
331 331  )))
332 332  
333 333  (((
334 -(% 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.
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.
335 335  
336 336  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
337 337  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
... ... @@ -338,9 +338,9 @@
338 338  |RO1|RO2|--DI3--|DI2|DI1|--DO3--|DO2|DO1
339 339  )))
340 340  
341 -* RO is for the relay. ROx=1: CLOSED, ROx=0 always OPEN.
342 -* DI is for digital input. DIx=1: HIGH or FLOATING, DIx=0: LOW.
343 -* DO is for reverse digital output. DOx=1: LOW, DOx=0: HIGH or FLOATING.
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.
344 344  
345 345  (% style="color:red" %)**Note: DI3 and DO3 bits are not valid for LT-22222-L**
346 346  
... ... @@ -361,13 +361,13 @@
361 361  
362 362  * [1] The RO1 relay channel is CLOSED, and the RO1 LED is ON.
363 363  * [0] The RO2 relay channel is OPEN, and the RO2 LED is OFF.
364 -* **[1] DI3 - not used for LT-22222-L.**
328 +* [1] DI3 - not used for LT-22222-L.
365 365  * [0] DI2 channel input is LOW, and the DI2 LED is OFF.
366 366  * [1] DI1 channel input state:
367 367  ** DI1 is FLOATING when no sensor is connected between DI1+ and DI1-.
368 368  ** DI1 is HIGH when a sensor is connected between DI1- and DI1+ and the sensor is ACTIVE.
369 369  ** DI1 LED is ON in both cases.
370 -* **[0] DO3 - not used for LT-22222-L.**
334 +* [0] DO3 - not used for LT-22222-L.
371 371  * [1] DO2 channel output is LOW, and the DO2 LED is ON.
372 372  * [0] DO1 channel output state:
373 373  ** DO1 is FLOATING when there is no load between DO1 and V+.
... ... @@ -378,7 +378,7 @@
378 378  
379 379  
380 380  (((
381 -**For LT-22222-L**: In this mode, **DI1 and DI2** are used as counting pins.
345 +**For LT-22222-L**: In this mode, the **DI1 and DI2** are used as counting pins.
382 382  )))
383 383  
384 384  (((
... ... @@ -392,17 +392,17 @@
392 392  )))
393 393  
394 394  (((
395 -(% 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.
359 +(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, DO3, DO2 and DO1, for a total of 1 byte, as shown below.
396 396  
397 397  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
398 398  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
399 399  |RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1
400 400  
401 -* RO is for the relay. ROx=1: CLOSED, ROx=0 always OPEN.
365 +* RO is for the relay. ROx=1: closed, ROx=0 always open.
402 402  )))
403 403  
404 404  * FIRST: Indicates that this is the first packet after joining the network.
405 -* DO is for reverse digital output. DOx=1: LOW, DOx=0: HIGH or FLOATING.
369 +* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.
406 406  
407 407  (((
408 408  (% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L**
... ... @@ -629,6 +629,7 @@
629 629  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.
630 630  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.**
631 631  
596 +
632 632  (% style="color:#037691" %)**AT Command to set Trigger Condition**:
633 633  
634 634  (% style="color:#4f81bd" %)**Trigger based on voltage**:
... ... @@ -638,9 +638,9 @@
638 638  
639 639  **Example:**
640 640  
641 -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 +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)
642 642  
643 -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 +AT+AVLIM=5000,0,0,0   (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore)
644 644  
645 645  
646 646  (% style="color:#4f81bd" %)**Trigger based on current**:
... ... @@ -650,12 +650,12 @@
650 650  
651 651  **Example:**
652 652  
653 -AT+ACLIM=10000,15000,0,0   (triggers an uplink if ACI1 voltage is lower than 10mA or higher than 15mA)
618 +AT+ACLIM=10000,15000,0,0   (If ACI1 voltage lower than 10mA or higher than 15mA, trigger an uplink)
654 654  
655 655  
656 -(% style="color:#4f81bd" %)**Trigger based on DI status**:
621 +(% style="color:#4f81bd" %)**Trigger base on DI status**:
657 657  
658 -DI status triggers Flag.
623 +DI status trigger Flag.
659 659  
660 660  Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >
661 661  
... ... @@ -665,38 +665,39 @@
665 665  AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
666 666  
667 667  
668 -(% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
633 +(% style="color:#037691" %)**Downlink Command to set Trigger Condition:**
669 669  
670 670  Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
671 671  
672 672  Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
673 673  
674 - AA: Type Code for this downlink Command:
639 + AA: Code for this downlink Command:
675 675  
676 - xx: **0**: Limit for AV1 and AV2; **1**: limit for AC1 and AC2; **2**: DI1and DI2 trigger enable/disable.
641 + xx: 0: Limit for AV1 and AV2;  1: limit for AC1 and AC2 ; 2 DI1, DI2 trigger enable/disable
677 677  
678 - yy1 yy1: AC1 or AV1 LOW limit or DI1/DI2 trigger status.
643 + yy1 yy1: AC1 or AV1 low limit or DI1/DI2 trigger status.
679 679  
680 - yy2 yy2: AC1 or AV1 HIGH limit.
645 + yy2 yy2: AC1 or AV1 high limit.
681 681  
682 - yy3 yy3: AC2 or AV2 LOW limit.
647 + yy3 yy3: AC2 or AV2 low limit.
683 683  
684 - Yy4 yy4: AC2 or AV2 HIGH limit.
649 + Yy4 yy4: AC2 or AV2 high limit.
685 685  
686 686  
687 -**Example 1**: AA 00 13 88 00 00 00 00 00 00
652 +**Example1**: AA 00 13 88 00 00 00 00 00 00
688 688  
689 -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 +Same as AT+AVLIM=5000,0,0,0   (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore)
690 690  
691 691  
692 -**Example 2**: AA 02 01 00
657 +**Example2**: AA 02 01 00
693 693  
694 -Same as AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
659 +Same as AT+ DTRI =1,0  (Enable DI1 trigger / disable DI2 trigger)
695 695  
696 696  
662 +
697 697  (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:**
698 698  
699 -MOD6 Payload: total of 11 bytes
665 +MOD6 Payload : total 11 bytes payload
700 700  
701 701  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
702 702  |(% 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**
... ... @@ -710,10 +710,10 @@
710 710  MOD(6)
711 711  )))
712 712  
713 -(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
679 +(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if trigger is set for this part. Totally 1byte as below
714 714  
715 715  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
716 -|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
682 +|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
717 717  |(((
718 718  AV1_LOW
719 719  )))|(((
... ... @@ -732,17 +732,17 @@
732 732  AC2_HIGH
733 733  )))
734 734  
735 -* Each bit shows if the corresponding trigger has been configured.
701 +* Each bits shows if the corresponding trigger has been configured.
736 736  
737 737  **Example:**
738 738  
739 -10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW
705 +10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW
740 740  
741 741  
742 -(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
708 +(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1byte as below
743 743  
744 744  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
745 -|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
711 +|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
746 746  |(((
747 747  AV1_LOW
748 748  )))|(((
... ... @@ -761,11 +761,11 @@
761 761  AC2_HIGH
762 762  )))
763 763  
764 -* Each bit shows which status has been triggered on this uplink.
730 +* Each bits shows which status has been trigger on this uplink.
765 765  
766 766  **Example:**
767 767  
768 -10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.
734 +10000000: Means this packet is trigger by AC1_LOW. Means voltage too low.
769 769  
770 770  
771 771  (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
... ... @@ -774,7 +774,7 @@
774 774  |**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
775 775  |N/A|N/A|N/A|N/A|DI2_STATUS|DI2_FLAG|DI1_STATUS|DI1_FLAG
776 776  
777 -* Each bits shows which status has been triggered on this uplink.
743 +* Each bits shows which status has been trigger on this uplink.
778 778  
779 779  **Example:**
780 780  
... ... @@ -801,11 +801,11 @@
801 801  )))
802 802  
803 803  
804 -== 3.4 ​Configure LT via AT Commands or Downlinks ==
770 +== 3.4 ​Configure LT via AT or Downlink ==
805 805  
806 806  
807 807  (((
808 -User can configure LT I/O Controller via AT Commands or LoRaWAN Downlinks.
774 +User can configure LT I/O Controller via AT Commands or LoRaWAN Downlink Commands
809 809  )))
810 810  
811 811  (((
... ... @@ -820,8 +820,9 @@
820 820  
821 821  === 3.4.1 Common Commands ===
822 822  
789 +
823 823  (((
824 -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 +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]]
825 825  )))
826 826  
827 827  
... ... @@ -829,37 +829,34 @@
829 829  
830 830  ==== 3.4.2.1 Set Transmit Interval ====
831 831  
832 -Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
833 833  
834 -* (% style="color:#037691" %)**AT command:**
800 +Set device uplink interval.
835 835  
836 -(% style="color:blue" %)**AT+TDC=N**
802 +* (% style="color:#037691" %)**AT Command:**
837 837  
838 -where N is the time in milliseconds.
804 +(% style="color:blue" %)**AT+TDC=N **
839 839  
840 -**Example: **AT+TDC=30000. This will set the uplink interval to 30 seconds
841 841  
807 +**Example: **AT+TDC=30000. Means set interval to 30 seconds
842 842  
843 -* (% style="color:#037691" %)**Downlink payload (prefix 0x01):**
844 844  
810 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x01):**
811 +
845 845  (% style="color:blue" %)**0x01 aa bb cc  **(%%)** ~/~/ Same as AT+TDC=0x(aa bb cc)**
846 846  
847 847  
848 848  
849 -==== 3.4.2.2 Set the Work Mode (AT+MOD) ====
816 +==== 3.4.2.2 Set Work Mode (AT+MOD) ====
850 850  
851 851  
852 -Sets the work mode.
819 +Set work mode.
853 853  
854 -* (% style="color:#037691" %)**AT command:**(%%) (% style="color:blue" %)**AT+MOD=N  **
821 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+MOD=N  **
855 855  
856 -Where N is the work mode.
823 +**Example**: AT+MOD=2. Set work mode to Double DI counting mode
857 857  
858 -**Example**: AT+MOD=2. This will set the work mode to Double DI counting mode.
825 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A):**
859 859  
860 -
861 -* (% style="color:#037691" %)**Downlink payload (prefix 0x0A):**
862 -
863 863  (% style="color:blue" %)**0x0A aa  **(%%)** ** ~/~/ Same as AT+MOD=aa
864 864  
865 865  
... ... @@ -867,12 +867,10 @@
867 867  ==== 3.4.2.3 Poll an uplink ====
868 868  
869 869  
870 -Asks the device to send an uplink.
834 +* (% style="color:#037691" %)**AT Command:**(%%) There is no AT Command to poll uplink
871 871  
872 -* (% style="color:#037691" %)**AT command:**(%%) There is no AT Command to poll uplink
836 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x08):**
873 873  
874 -* (% style="color:#037691" %)**Downlink payload (prefix 0x08):**
875 -
876 876  (% style="color:blue" %)**0x08 FF  **(%%)** **~/~/ Poll an uplink
877 877  
878 878  **Example**: 0x08FF, ask device to send an Uplink
... ... @@ -879,16 +879,16 @@
879 879  
880 880  
881 881  
882 -==== 3.4.2.4 Enable/Disable Trigger Mode ====
844 +==== 3.4.2.4 Enable Trigger Mode ====
883 883  
884 884  
885 -Enable or disable the trigger mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
847 +Use of trigger mode, please check [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
886 886  
887 887  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0**
888 888  
889 -(% style="color:red" %)**1:** (%%)Enable the trigger mode
851 +(% style="color:red" %)**1:** (%%)Enable Trigger Mode
890 890  
891 -(% style="color:red" %)**0: **(%%)Disable the trigger mode
853 +(% style="color:red" %)**0: **(%%)Disable Trigger Mode
892 892  
893 893  
894 894  * (% style="color:#037691" %)**Downlink Payload (prefix 0x0A 06):**
... ... @@ -900,7 +900,7 @@
900 900  ==== 3.4.2.5 Poll trigger settings ====
901 901  
902 902  
903 -Polls the trigger settings
865 +Poll trigger settings
904 904  
905 905  * (% style="color:#037691" %)**AT Command:**
906 906  
... ... @@ -908,7 +908,7 @@
908 908  
909 909  * (% style="color:#037691" %)**Downlink Payload (prefix 0x AB 06):**
910 910  
911 -(% style="color:blue" %)**0xAB 06  ** (%%) ~/~/ Poll the trigger settings. Device will uplink trigger settings once receive this command
873 +(% style="color:blue" %)**0xAB 06  ** (%%) ~/~/ Poll trigger settings, device will uplink trigger settings once receive this command
912 912  
913 913  
914 914  
... ... @@ -915,11 +915,11 @@
915 915  ==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ====
916 916  
917 917  
918 -Enable or Disable DI1/DI2/DI2 as trigger,
880 +Enable Disable DI1/DI2/DI2 as trigger,
919 919  
920 920  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
921 921  
922 -**Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
884 +**Example:** AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
923 923  
924 924  
925 925  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 02):**
... ... @@ -951,15 +951,15 @@
951 951  ==== 3.4.2.8 Trigger2 – Set DI2 as trigger ====
952 952  
953 953  
954 -Sets DI2 trigger.
916 +Set DI2 trigger.
955 955  
956 956  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b**
957 957  
958 -(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
920 +(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
959 959  
960 960  (% style="color:red" %)**b :** (%%)delay timing.
961 961  
962 -**Example:** AT+TRIG2=0,100 (set DI1 port to trigger on low level, valid signal is 100ms )
924 +**Example:** AT+TRIG2=0,100(set DI1 port to trigger on low level, valid signal is 100ms )
963 963  
964 964  
965 965  * (% style="color:#037691" %)**Downlink Payload (prefix 0x09 02 ):**
... ... @@ -997,7 +997,7 @@
997 997  ==== 3.4.2.11 Trigger – Set minimum interval ====
998 998  
999 999  
1000 -Sets AV and AC trigger minimum interval. Device won't response to the second trigger within this set time after the first trigger.
962 +Set AV and AC trigger minimum interval, system won't response to the second trigger within this set time after the first trigger.
1001 1001  
1002 1002  * (% 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.
1003 1003  
... ... @@ -1145,7 +1145,7 @@
1145 1145  )))
1146 1146  
1147 1147  (((
1148 -00: Closed ,  01: Open , 11: No action
1110 +00: Close ,  01: Open , 11: No action
1149 1149  
1150 1150  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %)
1151 1151  |(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**RO1**|(% style="background-color:#4f81bd; color:white" %)**RO2**
... ... @@ -1267,7 +1267,7 @@
1267 1267  
1268 1268  
1269 1269  
1270 -==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1232 +==== 3.4.2.19 Counting ~-~- Change counting mode save time ====
1271 1271  
1272 1272  
1273 1273  * (% style="color:#037691" %)**AT Command:**
... ... @@ -1390,123 +1390,69 @@
1390 1390  
1391 1391  == 3.5 Integrating with ThingsEye.io ==
1392 1392  
1393 -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.
1355 +If you are using one of The Things Stack plans, you can integrate ThingsEye.io with your application. Once integrated, ThingsEye.io works as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
1394 1394  
1395 -=== 3.5.1 Configuring The Things Stack ===
1357 +=== 3.5.1 Configuring The Things Stack Sandbox ===
1396 1396  
1397 -We use The Things Stack Sandbox in this example:
1359 +* Go to your Application and select MQTT under Integrations.
1360 +* In the Connection credentials section, under Username, The Thins Stack displays an auto-generated username. You can use it or provide a new one.
1361 +* For the Password, click the Generate new API key button to generate a password. You can see it by clicking on the eye button.
1398 1398  
1399 -* In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
1400 -* Select **MQTT** under **Integrations** in the left menu.
1401 -* 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.
1402 -* 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.
1403 -
1404 -{{info}}
1405 -The username and  password (API key) you created here are required in the next section.
1406 -{{/info}}
1407 -
1408 1408  [[image:tts-mqtt-integration.png||height="625" width="1000"]]
1409 1409  
1410 1410  === 3.5.2 Configuring ThingsEye.io ===
1411 1411  
1412 -* Login to your [[ThingsEye.io >>https://thingseye.io]]account.
1413 -* Under the **Integrations center**, click **Integrations**.
1414 -* Click the **Add integration** button (the button with the **+** symbol).
1367 +* Login to your thingsEye.io account.
1368 +* Under the Integrations center, click Integrations.
1369 +* Click the Add integration button (the button with the + symbol).
1415 1415  
1416 1416  [[image:thingseye-io-step-1.png||height="625" width="1000"]]
1417 1417  
1418 1418  
1419 -On the **Add integration** window, configure the following:
1374 +On the Add integration page configure the following:
1420 1420  
1421 -**Basic settings:**
1376 +Basic settings:
1422 1422  
1423 -* Select **The Things Stack Community** from the **Integration type** list.
1424 -* Enter a suitable name for your integration in the **Name **text** **box or keep the default name.
1425 -* Ensure the following options are turned on.
1426 -** Enable integration
1427 -** Debug mode
1428 -** Allow create devices or assets
1429 -* Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
1378 +* Select The Things Stack Community from the Integration type list.
1379 +* Enter a suitable name for your integration in the Name box or keep the default name.
1380 +* Click the Next button.
1430 1430  
1431 1431  [[image:thingseye-io-step-2.png||height="625" width="1000"]]
1432 1432  
1384 +Uplink Data converter:
1433 1433  
1434 -**Uplink data converter:**
1386 +* Click the Create New button if it is not selected by default.
1387 +* Click the JavaScript button.
1388 +* Paste the uplink decoder function into the text area (first, delete the default code). The demo decoder function can be found here.
1389 +* Click the Next button.
1435 1435  
1436 -* Click the **Create new** button if it is not selected by default.
1437 -* Enter a suitable name for the uplink data converter in the **Name **text** **box or keep the default name.
1438 -* Click the **JavaScript** button.
1439 -* 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]].
1440 -* Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
1441 -
1442 1442  [[image:thingseye-io-step-3.png||height="625" width="1000"]]
1443 1443  
1393 +Downlink Data converter (this is an optional step):
1444 1444  
1445 -**Downlink data converter (this is an optional step):**
1395 +* Click the Create new button if it is not selected by default.
1396 +* Click the JavaScript button.
1397 +* Paste the downlink decoder function into the text area (first, delete the default code). The demo decoder function can be found here.
1398 +* Click the Next button.
1446 1446  
1447 -* Click the **Create new** button if it is not selected by default.
1448 -* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name
1449 -* Click the **JavaScript** button.
1450 -* 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]].
1451 -* Click the **Next** button. You will be navigated to the **Connection** tab.
1452 -
1453 1453  [[image:thingseye-io-step-4.png||height="625" width="1000"]]
1454 1454  
1402 +Connection:
1455 1455  
1456 -**Connection:**
1404 +* Choose Region from the Host type.
1405 +* Enter the cluster of your The Things Stack in the Region textbox.
1406 +* Enter the Username and Password in the Credentials section. Use the same username and password you created with the MQTT page of The Things Stack.
1407 +* Click Check connection to test the connection. If the connection is successful, you can see the message saying Connected.
1408 +* Click the Add button.
1457 1457  
1458 -* Choose **Region** from the **Host type**.
1459 -* 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/...).
1460 -* 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).
1461 -* Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
1462 -
1463 -[[image:message-1.png]]
1464 -
1465 -
1466 -* Click the **Add** button.
1467 -
1468 1468  [[image:thingseye-io-step-5.png||height="625" width="1000"]]
1469 1469  
1470 1470  
1471 -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 +Your integration is added to the integrations list and it will display on the Integrations page.
1472 1472  
1415 +[[image:thingseye-io-step-6.png||height="625" width="1000"]]
1473 1473  
1474 -[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
1475 1475  
1476 -
1477 -**Viewing integration details**:
1478 -
1479 -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.
1480 -
1481 -[[image:integration-details.png||height="686" width="1000"]]
1482 -
1483 -
1484 -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.
1485 -
1486 -{{info}}
1487 -See also ThingsEye documentation.
1488 -{{/info}}
1489 -
1490 -**Viewing events:**
1491 -
1492 -The **Events **tab displays all the uplink messages from the LT-22222-L.
1493 -
1494 -* Select **Debug **from the **Event type** dropdown.
1495 -* Select the** time frame** from the **time window**.
1496 -
1497 -[[image:thingseye-events.png||height="686" width="1000"]]
1498 -
1499 -
1500 -* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
1501 -
1502 -[[image:thingseye-json.png||width="1000"]]
1503 -
1504 -
1505 -**Deleting the integration**:
1506 -
1507 -If you want to delete this integration, click the **Delete integratio**n button.
1508 -
1509 -
1510 1510  == 3.6 Interface Details ==
1511 1511  
1512 1512  === 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) ===
... ... @@ -1749,14 +1749,13 @@
1749 1749  |**RO1**|For LT-22222-L: ON when RO1 is closed, OFF when RO1 is open
1750 1750  |**RO2**|For LT-22222-L: ON when RO2 is closed, OFF when RO2 is open
1751 1751  
1752 -= 4. Using AT Commands =
1660 += 4. Using AT Command =
1753 1753  
1754 -The LT-22222-L supports programming using AT Commands.
1662 +== 4.1 Connecting the LT-22222-L to a computer ==
1755 1755  
1756 -== 4.1 Connecting the LT-22222-L to a PC ==
1757 1757  
1758 1758  (((
1759 -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.
1666 +The LT-22222-L supports programming using AT Commands. You can use a USB-to-TTL adapter along with a 3.5mm Program Cable to connect the LT-22222-L to a computer, as shown below.
1760 1760  )))
1761 1761  
1762 1762  [[image:1653358238933-385.png]]
... ... @@ -1763,7 +1763,7 @@
1763 1763  
1764 1764  
1765 1765  (((
1766 -On the PC, you need to set the (% style="color:#4f81bd" %)**serial tool **(%%)(such as [[PuTTY>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]] or [[SecureCRT>>https://www.vandyke.com/cgi-bin/releases.php?product=securecrt]]) to a baud rate of (% style="color:green" %)**9600**(%%) to access the serial console of LT-22222-L. Access to AT commands is disabled by default, and a password (default: (% style="color:green" %)**123456**)(%%) must be entered to enable AT command access, as shown below:
1673 +On the PC, the user needs to set the (% style="color:#4f81bd" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) to a baud rate of (% style="color:green" %)**9600**(%%) to access to access serial console of LT-22222-L. The AT commands are disabled by default, and a password (default:(% style="color:green" %)**123456**)(%%) must be entered to active them, as shown below:
1767 1767  )))
1768 1768  
1769 1769  [[image:1653358355238-883.png]]
... ... @@ -1771,62 +1771,195 @@
1771 1771  
1772 1772  (((
1773 1773  You can find more details in the [[AT Command Manual>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
1681 +)))
1774 1774  
1775 -== 4.2 LT-22222-L related AT commands ==
1683 +(((
1684 +The following table lists all the AT commands related to the LT-22222-L, except for those used for switching between modes.
1685 +
1686 +AT+<CMD>?        : Help on <CMD>
1776 1776  )))
1777 1777  
1778 1778  (((
1779 -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.
1690 +AT+<CMD>         : Run <CMD>
1691 +)))
1780 1780  
1781 -* AT+<CMD>? : Help on <CMD>
1782 -* AT+<CMD> : Run <CMD>
1783 -* AT+<CMD>=<value> : Set the value
1784 -* AT+<CMD>=? : Get the value
1785 -* ATZ: Trigger a reset of the MCU
1786 -* ##**AT+FDR**##: Reset Parameters to factory default, reserve keys 
1787 -* **##AT+DEUI##**: Get or set the Device EUI (DevEUI)
1788 -* **##AT+DADDR##**: Get or set the Device Address (DevAddr)
1789 -* **##AT+APPKEY##**: Get or set the Application Key (AppKey)
1790 -* AT+NWKSKEY: Get or set the Network Session Key (NwkSKey)
1791 -* AT+APPSKEY: Get or set the Application Session Key (AppSKey)
1792 -* AT+APPEUI: Get or set the Application EUI (AppEUI)
1793 -* AT+ADR: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
1794 -* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
1795 -* AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
1796 -* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
1797 -* AT+PNM: Get or set the public network mode. (0: off, 1: on)
1798 -* AT+RX2FQ: Get or set the Rx2 window frequency
1799 -* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
1800 -* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
1801 -* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
1802 -* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
1803 -* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
1804 -* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
1805 -* AT+NWKID: Get or set the Network ID
1806 -* AT+FCU: Get or set the Frame Counter Uplink (FCntUp)
1807 -* AT+FCD: Get or set the Frame Counter Downlink (FCntDown)
1808 -* AT+CLASS: Get or set the Device Class
1809 -* AT+JOIN: Join network
1810 -* AT+NJS: Get OTAA Join Status
1811 -* AT+SENDB: Send hexadecimal data along with the application port
1812 -* AT+SEND: Send text data along with the application port
1813 -* AT+RECVB: Print last received data in binary format (with hexadecimal values)
1814 -* AT+RECV: Print last received data in raw format
1815 -* AT+VER: Get current image version and Frequency Band
1816 -* AT+CFM: Get or Set the confirmation mode (0-1)
1817 -* AT+CFS: Get confirmation status of the last AT+SEND (0-1)
1818 -* AT+SNR: Get the SNR of the last received packet
1819 -* AT+RSSI: Get the RSSI of the last received packet
1820 -* AT+TDC: Get or set the application data transmission interval in ms
1821 -* AT+PORT: Get or set the application port
1822 -* AT+DISAT: Disable AT commands
1823 -* AT+PWORD: Set password, max 9 digits
1824 -* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode
1825 -* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470
1826 -* AT+CFG: Print all settings
1693 +(((
1694 +AT+<CMD>=<value> : Set the value
1827 1827  )))
1828 1828  
1697 +(((
1698 +AT+<CMD>=?       :  Get the value
1699 +)))
1829 1829  
1701 +(((
1702 +ATZ: Trig a reset of the MCU
1703 +)))
1704 +
1705 +(((
1706 +AT+FDR: Reset Parameters to Factory Default, Keys Reserve 
1707 +)))
1708 +
1709 +(((
1710 +AT+DEUI: Get or Set the Device EUI
1711 +)))
1712 +
1713 +(((
1714 +AT+DADDR: Get or Set the Device Address
1715 +)))
1716 +
1717 +(((
1718 +AT+APPKEY: Get or Set the Application Key
1719 +)))
1720 +
1721 +(((
1722 +AT+NWKSKEY: Get or Set the Network Session Key
1723 +)))
1724 +
1725 +(((
1726 +AT+APPSKEY:  Get or Set the Application Session Key
1727 +)))
1728 +
1729 +(((
1730 +AT+APPEUI:  Get or Set the Application EUI
1731 +)))
1732 +
1733 +(((
1734 +AT+ADR: Get or Set the Adaptive Data Rate setting. (0: off, 1: on)
1735 +)))
1736 +
1737 +(((
1738 +AT+TXP: Get or Set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Spec)
1739 +)))
1740 +
1741 +(((
1742 +AT+DR:  Get or Set the Data Rate. (0-7 corresponding to DR_X)  
1743 +)))
1744 +
1745 +(((
1746 +AT+DCS: Get or Set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
1747 +)))
1748 +
1749 +(((
1750 +AT+PNM: Get or Set the public network mode. (0: off, 1: on)
1751 +)))
1752 +
1753 +(((
1754 +AT+RX2FQ: Get or Set the Rx2 window frequency
1755 +)))
1756 +
1757 +(((
1758 +AT+RX2DR: Get or Set the Rx2 window data rate (0-7 corresponding to DR_X)
1759 +)))
1760 +
1761 +(((
1762 +AT+RX1DL: Get or Set the delay between the end of the Tx and the Rx Window 1 in ms
1763 +)))
1764 +
1765 +(((
1766 +AT+RX2DL: Get or Set the delay between the end of the Tx and the Rx Window 2 in ms
1767 +)))
1768 +
1769 +(((
1770 +AT+JN1DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
1771 +)))
1772 +
1773 +(((
1774 +AT+JN2DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
1775 +)))
1776 +
1777 +(((
1778 +AT+NJM:  Get or Set the Network Join Mode. (0: ABP, 1: OTAA)
1779 +)))
1780 +
1781 +(((
1782 +AT+NWKID: Get or Set the Network ID
1783 +)))
1784 +
1785 +(((
1786 +AT+FCU: Get or Set the Frame Counter Uplink
1787 +)))
1788 +
1789 +(((
1790 +AT+FCD: Get or Set the Frame Counter Downlink
1791 +)))
1792 +
1793 +(((
1794 +AT+CLASS: Get or Set the Device Class
1795 +)))
1796 +
1797 +(((
1798 +AT+JOIN: Join network
1799 +)))
1800 +
1801 +(((
1802 +AT+NJS: Get OTAA Join Status
1803 +)))
1804 +
1805 +(((
1806 +AT+SENDB: Send hexadecimal data along with the application port
1807 +)))
1808 +
1809 +(((
1810 +AT+SEND: Send text data along with the application port
1811 +)))
1812 +
1813 +(((
1814 +AT+RECVB: Print last received data in binary format (with hexadecimal values)
1815 +)))
1816 +
1817 +(((
1818 +AT+RECV: Print last received data in raw format
1819 +)))
1820 +
1821 +(((
1822 +AT+VER:  Get current image version and Frequency Band
1823 +)))
1824 +
1825 +(((
1826 +AT+CFM: Get or Set the confirmation mode (0-1)
1827 +)))
1828 +
1829 +(((
1830 +AT+CFS:  Get confirmation status of the last AT+SEND (0-1)
1831 +)))
1832 +
1833 +(((
1834 +AT+SNR: Get the SNR of the last received packet
1835 +)))
1836 +
1837 +(((
1838 +AT+RSSI: Get the RSSI of the last received packet
1839 +)))
1840 +
1841 +(((
1842 +AT+TDC: Get or set the application data transmission interval in ms
1843 +)))
1844 +
1845 +(((
1846 +AT+PORT: Get or set the application port
1847 +)))
1848 +
1849 +(((
1850 +AT+DISAT: Disable AT commands
1851 +)))
1852 +
1853 +(((
1854 +AT+PWORD: Set password, max 9 digits
1855 +)))
1856 +
1857 +(((
1858 +AT+CHS: Get or Set Frequency (Unit: Hz) for Single Channel Mode
1859 +)))
1860 +
1861 +(((
1862 +AT+CHE: Get or Set eight channels mode, Only for US915, AU915, CN470
1863 +)))
1864 +
1865 +(((
1866 +AT+CFG: Print all settings
1867 +)))
1868 +
1869 +
1830 1830  == 4.2 Common AT Command Sequence ==
1831 1831  
1832 1832  === 4.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
... ... @@ -1835,41 +1835,41 @@
1835 1835  
1836 1836  
1837 1837  (((
1838 -(% style="color:blue" %)**If the device has not joined the network yet:**
1878 +(% style="color:blue" %)**If device has not joined network yet:**
1839 1839  )))
1840 1840  )))
1841 1841  
1842 1842  (((
1843 -(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**##
1883 +(% style="background-color:#dcdcdc" %)**123456**
1844 1844  )))
1845 1845  
1846 1846  (((
1847 -(% style="background-color:#dcdcdc" %)##**AT+FDR ~/~/reset parameters to factory default, reserve keys**##
1887 +(% style="background-color:#dcdcdc" %)**AT+FDR**
1848 1848  )))
1849 1849  
1850 1850  (((
1851 -(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**##
1891 +(% style="background-color:#dcdcdc" %)**123456**
1852 1852  )))
1853 1853  
1854 1854  (((
1855 -(% style="background-color:#dcdcdc" %)##**AT+NJM=0 ~/~/set to ABP mode**##
1895 +(% style="background-color:#dcdcdc" %)**AT+NJM=0**
1856 1856  )))
1857 1857  
1858 1858  (((
1859 -(% style="background-color:#dcdcdc" %)##**ATZ ~/~/reset MCU**##
1899 +(% style="background-color:#dcdcdc" %)**ATZ**
1860 1860  )))
1861 1861  
1862 1862  
1863 1863  (((
1864 -(% style="color:blue" %)**If the device has already joined the network:**
1904 +(% style="color:blue" %)**If device already joined network:**
1865 1865  )))
1866 1866  
1867 1867  (((
1868 -(% style="background-color:#dcdcdc" %)##**AT+NJM=0**##
1908 +(% style="background-color:#dcdcdc" %)**AT+NJM=0**
1869 1869  )))
1870 1870  
1871 1871  (((
1872 -(% style="background-color:#dcdcdc" %)##**ATZ**##
1912 +(% style="background-color:#dcdcdc" %)**ATZ**
1873 1873  )))
1874 1874  
1875 1875  
... ... @@ -1967,50 +1967,37 @@
1967 1967  
1968 1968  = 5. Case Study =
1969 1969  
1970 -== 5.1 Counting how many objects pass through the flow Line ==
2010 +== 5.1 Counting how many objects pass in Flow Line ==
1971 1971  
1972 1972  
1973 -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]]?
2013 +Reference Link: [[How to set up to count objects pass in flow line>>How to set up to count objects pass in flow line]]?
1974 1974  
1975 1975  
1976 1976  = 6. FAQ =
1977 1977  
1978 -This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
2018 +== 6.1 How to upgrade the image? ==
1979 1979  
1980 -== 6.1 How to update the firmware? ==
1981 1981  
1982 -Dragino frequently releases firmware updates for the LT-22222-L.
2021 +The LT LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to LT to:
1983 1983  
1984 -Updating your LT-22222-L with the latest firmware version helps to:
1985 -
1986 1986  * Support new features
1987 -* Fix bugs
1988 -* Change LoRaWAN frequency bands
2024 +* For bug fix
2025 +* Change LoRaWAN bands.
1989 1989  
1990 -You will need the following things before proceeding:
2027 +Below is the hardware connection for how to upload an image to the LT:
1991 1991  
1992 -* 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
1993 -* USB to TTL adapter
1994 -* Download and install the [[STM32 Flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]]. (replaced by STM32CubeProgrammer)
1995 -* Download the latest firmware image from [[LT-22222-L firmware image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]]. Check the file name of the firmware to find the correct region.
1996 -
1997 -{{info}}
1998 -As of this writing, the latest firmware version available for the LT-22222-L is v1.6.1.
1999 -{{/info}}
2000 -
2001 -Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2002 -
2003 -
2004 2004  [[image:1653359603330-121.png]]
2005 2005  
2006 2006  
2007 -Start the STM32 Flash Loader and choose the correct COM port to update.
2032 +(((
2033 +(% style="color:blue" %)**Step1**(%%)**:** Download [[flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]].
2034 +(% style="color:blue" %)**Step2**(%%)**:** Download the [[LT Image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]].
2035 +(% style="color:blue" %)**Step3**(%%)**:** Open flashloader; choose the correct COM port to update.
2036 +
2008 2008  
2009 2009  (((
2010 -(((
2011 2011  (% style="color:blue" %)**For LT-22222-L**(%%):
2012 -
2013 -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 +Hold down the PRO button and then momentarily press the RST reset button and the (% style="color:red" %)**DO1 led**(%%) will change from OFF to ON. When (% style="color:red" %)**DO1 LED**(%%) is on, it means the device is in download mode.
2014 2014  )))
2015 2015  
2016 2016  
... ... @@ -2025,7 +2025,7 @@
2025 2025  [[image:image-20220524104033-15.png]]
2026 2026  
2027 2027  
2028 -(% 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:
2055 +(% style="color:red" %)**Notice**(%%): In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
2029 2029  
2030 2030  [[image:1653360054704-518.png||height="186" width="745"]]
2031 2031  
... ... @@ -2032,7 +2032,7 @@
2032 2032  
2033 2033  (((
2034 2034  (((
2035 -== 6.2 How to change the LoRaWAN frequency band/region? ==
2062 +== 6.2 How to change the LoRa Frequency Bands/Region? ==
2036 2036  
2037 2037  
2038 2038  )))
... ... @@ -2039,13 +2039,13 @@
2039 2039  )))
2040 2040  
2041 2041  (((
2042 -You can follow the introductions on [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloading, select the required image file.
2069 +User can follow the introduction for [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
2043 2043  )))
2044 2044  
2045 2045  (((
2046 2046  
2047 2047  
2048 -== 6.3 How to setup LT to work with a Single Channel Gateway, such as LG01/LG02? ==
2075 +== 6.3 How to set up LT to work with Single Channel Gateway such as LG01/LG02? ==
2049 2049  
2050 2050  
2051 2051  )))
... ... @@ -2052,13 +2052,13 @@
2052 2052  
2053 2053  (((
2054 2054  (((
2055 -In this case, you need to set the LT-33222-L to work in ABP mode and transmit on only one frequency.
2082 +In this case, users need to set LT-33222-L to work in ABP mode & transmit in only one frequency.
2056 2056  )))
2057 2057  )))
2058 2058  
2059 2059  (((
2060 2060  (((
2061 -Assume you have an LG02 working on the frequency 868400000. Below are the steps.
2088 +Assume we have a LG02 working in the frequency 868400000 now , below is the step.
2062 2062  
2063 2063  
2064 2064  )))
... ... @@ -2065,7 +2065,7 @@
2065 2065  )))
2066 2066  
2067 2067  (((
2068 -(% 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.
2095 +(% style="color:blue" %)**Step1**(%%):  Log in TTN, Create an ABP device in the application and input the network session key (NETSKEY), app session key (APPSKEY) from the device.
2069 2069  
2070 2070  
2071 2071  )))
... ... @@ -2122,55 +2122,61 @@
2122 2122  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/]]
2123 2123  
2124 2124  
2125 -== 6.5 Can I see the counting event in the serial output? ==
2152 +== 6.5 Can I see counting event in Serial? ==
2126 2126  
2127 2127  
2128 2128  (((
2129 -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.
2156 +User can run AT+DEBUG command to see the counting event in serial. If firmware too old and doesn't support AT+DEBUG. User can update to latest firmware first.
2130 2130  
2131 2131  
2132 -== 6.6 Can I use point-to-point communication with LT-22222-L? ==
2159 +== 6.6 Can i use point to point communication for LT-22222-L? ==
2133 2133  
2134 2134  
2135 -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]].
2162 +Yes, please refer [[Point to Point Communication>>doc:Main. Point to Point Communication of LT-22222-L.WebHome]]  ，this is [[firmware>>https://github.com/dragino/LT-22222-L/releases]].
2163 +
2164 +
2136 2136  )))
2137 2137  
2138 2138  (((
2139 -== 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
2168 +== 6.7 Why does the relay output become the default and open relay after the lt22222 is powered off? ==
2140 2140  
2141 2141  
2142 -* If the device is not properly shut down and is directly powered off.
2143 -* It will default to a power-off state.
2144 -* In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
2145 -* After a restart, the status before the power failure will be read from flash.
2171 +If the device is not shut down, but directly powered off.
2146 2146  
2147 -== 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
2173 +It will default that this is a power-off state.
2148 2148  
2175 +In modes 2 to 5, DO RO status and pulse count are saved in flash.
2149 2149  
2150 -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:
2177 +After restart, the status before power failure will be read from flash.
2151 2151  
2152 2152  
2180 +== 6.8 Can i set up LT-22222-L as a NC(Normal Close) Relay? ==
2181 +
2182 +
2183 +LT-22222-L built-in relay is NO (Normal Open). User can use an external relay to achieve Normal Close purpose. Diagram as below:
2184 +
2185 +
2153 2153  [[image:image-20221006170630-1.png||height="610" width="945"]]
2154 2154  
2155 2155  
2156 -== 6.9 Can the LT-22222-L save the RO state? ==
2189 +== 6.9 Can LT22222-L save RO state? ==
2157 2157  
2158 2158  
2159 -The firmware version must be at least 1.6.0.
2192 +Firmware version needs to be no less than 1.6.0.
2160 2160  
2161 2161  
2162 -== 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
2195 +== 6.10 Why does the LT22222 always report 15.585V when measuring AVI? ==
2163 2163  
2164 2164  
2165 -It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
2198 +It is likely that the GND is not connected during the measurement, or the wire connected to the GND is loose.
2166 2166  
2167 2167  
2168 -= 7. Troubleshooting =
2201 += 7. Trouble Shooting =
2169 2169  )))
2170 2170  
2171 2171  (((
2172 2172  (((
2173 -== 7.1 Downlink isn't working. How can I solve this? ==
2206 +== 7.1 Downlink doesn't work, how to solve it? ==
2174 2174  
2175 2175  
2176 2176  )))
... ... @@ -2177,42 +2177,42 @@
2177 2177  )))
2178 2178  
2179 2179  (((
2180 -Please refer to this link for debugging instructions: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]]
2213 +Please see this link for how to debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]]
2181 2181  )))
2182 2182  
2183 2183  (((
2184 2184  
2185 2185  
2186 -== 7.2 Having trouble uploading an image? ==
2219 +== 7.2 Have trouble to upload image. ==
2187 2187  
2188 2188  
2189 2189  )))
2190 2190  
2191 2191  (((
2192 -Please refer to this link for troubleshooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
2225 +See this link for trouble shooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
2193 2193  )))
2194 2194  
2195 2195  (((
2196 2196  
2197 2197  
2198 -== 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
2231 +== 7.3 Why I can't join TTN in US915 /AU915 bands? ==
2199 2199  
2200 2200  
2201 2201  )))
2202 2202  
2203 2203  (((
2204 -It might be related to the channel mapping. [[Please refer to this link for details.>>https://github.com/dragino/LT-22222-L/releases]]
2237 +It might be about the channels mapping. [[Please see this link for detail>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
2205 2205  )))
2206 2206  
2207 2207  
2208 -== 7.4 Why can the LT-22222-L perform Uplink normally, but cannot receive Downlink? ==
2241 +== 7.4 Why can LT22222 perform Uplink normally, but cannot receive Downlink? ==
2209 2209  
2210 2210  
2211 -The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
2212 -Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2244 +The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue state.
2245 +Use this command to bring their counts back together: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2213 2213  
2214 2214  
2215 -= 8. Ordering information =
2248 += 8. Order Info =
2216 2216  
2217 2217  
2218 2218  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
... ... @@ -2219,42 +2219,43 @@
2219 2219  
2220 2220  (% style="color:#4f81bd" %)**XXX:**
2221 2221  
2222 -* (% style="color:red" %)**EU433**(%%): LT with frequency bands EU433
2223 -* (% style="color:red" %)**EU868**(%%): LT with frequency bands EU868
2224 -* (% style="color:red" %)**KR920**(%%): LT with frequency bands KR920
2225 -* (% style="color:red" %)**CN470**(%%): LT with frequency bands CN470
2226 -* (% style="color:red" %)**AS923**(%%): LT with frequency bands AS923
2227 -* (% style="color:red" %)**AU915**(%%): LT with frequency bands AU915
2228 -* (% style="color:red" %)**US915**(%%): LT with frequency bands US915
2229 -* (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865
2230 -* (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779
2255 +* (% style="color:red" %)**EU433**(%%):  LT with frequency bands EU433
2256 +* (% style="color:red" %)**EU868**(%%):  LT with frequency bands EU868
2257 +* (% style="color:red" %)**KR920**(%%):  LT with frequency bands KR920
2258 +* (% style="color:red" %)**CN470**(%%):  LT with frequency bands CN470
2259 +* (% style="color:red" %)**AS923**(%%):  LT with frequency bands AS923
2260 +* (% style="color:red" %)**AU915**(%%):  LT with frequency bands AU915
2261 +* (% style="color:red" %)**US915**(%%):  LT with frequency bands US915
2262 +* (% style="color:red" %)**IN865**(%%):  LT with frequency bands IN865
2263 +* (% style="color:red" %)**CN779**(%%):  LT with frequency bands CN779
2231 2231  
2232 -= 9. Packing information =
2265 += 9. Packing Info =
2233 2233  
2234 2234  
2235 -**Package includes**:
2268 +**Package Includes**:
2236 2236  
2237 -* 1 x LT-22222-L I/O Controller
2238 -* 1 x LoRa antenna matched to the frequency of the LT-22222-L
2239 -* 1 x bracket for DIN rail mounting
2240 -* 1 x 3.5mm programming cable
2270 +* LT-22222-L I/O Controller x 1
2271 +* Stick Antenna for LoRa RF part x 1
2272 +* Bracket for controller x1
2273 +* Program cable x 1
2241 2241  
2242 2242  **Dimension and weight**:
2243 2243  
2244 2244  * Device Size: 13.5 x 7 x 3 cm
2245 -* Device Weight: 105 g
2278 +* Device Weight: 105g
2246 2246  * Package Size / pcs : 14.5 x 8 x 5 cm
2247 -* Weight / pcs : 170 g
2280 +* Weight / pcs : 170g
2248 2248  
2249 2249  = 10. Support =
2250 2250  
2251 2251  
2252 2252  * (((
2253 -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.
2286 +Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
2254 2254  )))
2255 2255  * (((
2256 -Please provide as much information as possible regarding your inquiry (e.g., product models, a detailed description of the problem, steps to replicate it, etc.) and send an email to [[support@dragino.cc>>mailto:support@dragino.cc]]
2289 +Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[Support@dragino.cc>>mailto:Support@dragino.cc]]
2257 2257  
2291 +
2258 2258  
2259 2259  )))
2260 2260  
integration-details.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -463.9 KB
Content
lt-22222-device-overview.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -497.2 KB
Content
lt-22222-join-network.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -340.6 KB
Content
lt-22222-ul-payload-decoded.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -48.7 KB
Content
lt-22222-ul-payload-fmt.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -438.6 KB
Content
message-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -20.1 KB
Content
thingseye-events.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -530.6 KB
Content
thingseye-json.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -554.8 KB
Content
thingseye.io_integrationsCenter_integrations-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -469.3 KB
Content
thingseye.io_integrationsCenter_integrations.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -302.3 KB
Content