<
From version < 193.1 >
edited by Dilisi S
on 2024/11/14 05:28
To version < 183.1 >
edited by Dilisi S
on 2024/11/10 05:26
>
Change comment: Uploaded new attachment "thingseye-json.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 -= 2Assembling 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,14 +270,10 @@
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 Work Modes and Uplink Payload formats ==
285 +== 3.3 Work Modes and their Uplink Payload formats ==
281 281  
282 282  
283 283  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.
... ... @@ -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 it is.
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|(((
... ... @@ -376,10 +376,6 @@
376 376  (((
377 377  The uplink payload is 11 bytes long.
378 378  
379 -(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
380 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
381 -It starts counting again when it reaches the maximum value.**
382 -
383 383  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
384 384  |(% 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**
385 385  |Value|COUNT1|COUNT2 |DIDORO*|(((
... ... @@ -444,9 +444,6 @@
444 444  
445 445  === 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI ===
446 446  
447 -(% style="color:red" %)**Note: The maximum count depends on the bytes it is.
448 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
449 -It starts counting again when it reaches the maximum value.**
450 450  
451 451  **LT22222-L**: In this mode, the DI1 is used as a counting pin.
452 452  
... ... @@ -497,11 +497,7 @@
497 497  
498 498  === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting ===
499 499  
500 -(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
501 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
502 -It starts counting again when it reaches the maximum value.**
503 503  
504 -
505 505  (((
506 506  **LT22222-L**: In this mode, the DI1 is used as a counting pin.
507 507  )))
... ... @@ -554,23 +554,19 @@
554 554  (((
555 555  **In addition to that, below are the commands for AVI1 Counting:**
556 556  
557 -(% 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)**
558 558  
559 -(% 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)**
560 560  
561 -(% 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)**
562 562  
563 -(% 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)**
564 564  )))
565 565  
566 566  
567 567  === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI ===
568 568  
569 -(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
570 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
571 -It starts counting again when it reaches the maximum value.**
572 572  
573 -
574 574  **LT22222-L**: In this mode, the DI1 is used as a counting pin.
575 575  
576 576  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
... ... @@ -628,17 +628,15 @@
628 628  
629 629  For example, if you configured the following commands:
630 630  
631 -* **AT+MOD=1 ** **~-~->**  The default work mode
617 +* **AT+MOD=1 ** **~-~->**  The normal working mode
632 632  * **AT+ADDMOD6=1**   **~-~->**  Enable trigger mode
633 633  
634 634  The LT-22222-L will continuously monitor AV1, AV2, AC1, and AC2 every 5 seconds. LT will send uplink packets in two cases:
635 635  
636 636  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.
637 -1. (((
638 -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.**
639 -)))
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.**
640 640  
641 -(% style="color:#037691" %)**AT Commands to set Trigger Condition**:
625 +(% style="color:#037691" %)**AT Command to set Trigger Condition**:
642 642  
643 643  (% style="color:#4f81bd" %)**Trigger based on voltage**:
644 644  
... ... @@ -810,68 +810,50 @@
810 810  )))
811 811  
812 812  
813 -== 3.4 ​Configure LT-22222-L via AT Commands or Downlinks ==
797 +== 3.4 ​Configure LT via AT Commands or Downlinks ==
814 814  
799 +
815 815  (((
816 -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.
817 817  )))
818 818  
819 819  (((
820 820  (((
821 -There are two tytes of commands:
806 +There are two kinds of Commands:
822 822  )))
823 823  )))
824 824  
825 -* (% 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]]
826 826  
827 -* (% 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:
828 828  
829 -=== 3.4.1 Common commands ===
814 +=== 3.4.1 Common Commands ===
830 830  
831 831  (((
832 -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]].
833 833  )))
834 834  
835 -=== 3.4.2 Sensor-related commands ===
836 836  
837 -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 ===
838 838  
839 839  ==== 3.4.2.1 Set Transmit Interval ====
840 840  
841 841  Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
842 842  
843 -(% style="color:#037691" %)**AT command**
827 +* (% style="color:#037691" %)**AT command:**
844 844  
845 -(% style="width:500px" %)
846 -|**Command**|AT+TDC<time>
847 -|**Response**|
848 -|**Parameters**|<time> uplink interval is in milliseconds
849 -|**Example**|(((
850 -AT+TDC=30000
829 +(% style="color:blue" %)**AT+TDC=N**
851 851  
852 -Sets the uplink interval to 30,000 milliseconds (30 seconds)
853 -)))
831 +where N is the time in milliseconds.
854 854  
855 -(% style="color:#037691" %)**Downlink payload**
833 +**Example: **AT+TDC=30000. This will set the uplink interval to 30 seconds
856 856  
857 -(% style="width:500px" %)
858 -|**Payload**|(((
859 -<prefix><time>
860 -)))
861 -|**Parameters**|(((
862 -<prefix> 0x01
863 863  
864 -<time> uplink interval is in milliseconds, represented by 3  bytes in hexadecimal.
865 -)))
866 -|**Example**|(((
867 -01 **00 75 30**
836 +* (% style="color:#037691" %)**Downlink payload (prefix 0x01):**
868 868  
869 -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)**
870 870  
871 -Conversion: 30000 (dec) = 00 75 30 (hex)
872 872  
873 -See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]]
874 -)))
875 875  
876 876  ==== 3.4.2.2 Set the Work Mode (AT+MOD) ====
877 877  
... ... @@ -893,8 +893,8 @@
893 893  
894 894  ==== 3.4.2.3 Poll an uplink ====
895 895  
896 -Requests the device to send an uplink.
897 897  
863 +Asks the device to send an uplink.
898 898  
899 899  * (% style="color:#037691" %)**AT command:**(%%) There is no AT Command to poll uplink
900 900  
... ... @@ -908,6 +908,7 @@
908 908  
909 909  ==== 3.4.2.4 Enable/Disable Trigger Mode ====
910 910  
877 +
911 911  Enable or disable the trigger mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
912 912  
913 913  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0**
... ... @@ -925,8 +925,9 @@
925 925  
926 926  ==== 3.4.2.5 Poll trigger settings ====
927 927  
928 -Polls the trigger settings.
929 929  
896 +Polls the trigger settings
897 +
930 930  * (% style="color:#037691" %)**AT Command:**
931 931  
932 932  There is no AT Command for this feature.
... ... @@ -937,10 +937,11 @@
937 937  
938 938  
939 939  
940 -==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as a trigger ====
908 +==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ====
941 941  
942 -Enable or disable DI1/DI2/DI2 as a trigger.
943 943  
911 +Enable or Disable DI1/DI2/DI2 as trigger,
912 +
944 944  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
945 945  
946 946  **Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
... ... @@ -952,10 +952,11 @@
952 952  
953 953  
954 954  
955 -==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ====
924 +==== 3.4.2.7 Trigger1 – Set DI1 or DI3 as trigger ====
956 956  
957 -Sets DI1 or DI3 (for LT-33222-L) as a trigger.
958 958  
927 +Set DI1 or DI3(for LT-33222-L) trigger.
928 +
959 959  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG1=a,b**
960 960  
961 961  (% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
... ... @@ -970,10 +970,12 @@
970 970  (% style="color:blue" %)**0x09 01 aa bb cc    ** (%%) ~/~/ same as AT+TRIG1=aa,0x(bb cc)
971 971  
972 972  
973 -==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
974 974  
975 -Sets DI2 as a trigger.
944 +==== 3.4.2.8 Trigger2 – Set DI2 as trigger ====
976 976  
946 +
947 +Sets DI2 trigger.
948 +
977 977  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b**
978 978  
979 979  (% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
... ... @@ -988,10 +988,12 @@
988 988  (% style="color:blue" %)**0x09 02 aa bb cc   ** (%%)~/~/ same as AT+TRIG2=aa,0x(bb cc)
989 989  
990 990  
991 -==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
992 992  
993 -Sets the current trigger based on the AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
964 +==== 3.4.2.9 Trigger Set AC (current) as trigger ====
994 994  
966 +
967 +Set current trigger , base on AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
968 +
995 995  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ACLIM**
996 996  
997 997  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 01 )**
... ... @@ -1002,8 +1002,9 @@
1002 1002  
1003 1003  ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
1004 1004  
1005 -Sets the current trigger based on the AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1006 1006  
980 +Set current trigger , base on AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
981 +
1007 1007  * (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+AVLIM    **(%%)** See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]**
1008 1008  
1009 1009  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 00 )**
... ... @@ -1011,8 +1011,10 @@
1011 1011  (% 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"]]
1012 1012  
1013 1013  
989 +
1014 1014  ==== 3.4.2.11 Trigger – Set minimum interval ====
1015 1015  
992 +
1016 1016  Sets AV and AC trigger minimum interval. Device won't response to the second trigger within this set time after the first trigger.
1017 1017  
1018 1018  * (% 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.
... ... @@ -1029,7 +1029,6 @@
1029 1029  
1030 1030  ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
1031 1031  
1032 -Controls the digital outputs DO1, DO2, and DO3
1033 1033  
1034 1034  * (% style="color:#037691" %)**AT Command**
1035 1035  
... ... @@ -1407,25 +1407,25 @@
1407 1407  
1408 1408  == 3.5 Integrating with ThingsEye.io ==
1409 1409  
1410 -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.
1411 1411  
1412 -=== 3.5.1 Configuring The Things Stack ===
1388 +=== 3.5.1 Configuring MQTT Connection Information with The Things Stack Sandbox ===
1413 1413  
1414 -We use The Things Stack Sandbox in this example:
1390 +We use The Things Stack Sandbox for demonstating the configuration but  other
1415 1415  
1416 -* In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
1417 -* Select **MQTT** under **Integrations** in the left menu.
1418 -* 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.
1419 -* 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.
1420 1420  
1421 -{{info}}
1422 -The username and  password (API key) you created here are required in the next section.
1423 -{{/info}}
1397 +NOTE. The username and  password (API key) you created here are required in the next section.
1424 1424  
1425 1425  [[image:tts-mqtt-integration.png||height="625" width="1000"]]
1426 1426  
1427 1427  === 3.5.2 Configuring ThingsEye.io ===
1428 1428  
1403 +This section guides you on how to create an integration in ThingsEye to connect with The Things Stack MQTT server.
1404 +
1429 1429  * Login to your [[ThingsEye.io >>https://thingseye.io]]account.
1430 1430  * Under the **Integrations center**, click **Integrations**.
1431 1431  * Click the **Add integration** button (the button with the **+** symbol).
... ... @@ -1462,9 +1462,9 @@
1462 1462  **Downlink data converter (this is an optional step):**
1463 1463  
1464 1464  * Click the **Create new** button if it is not selected by default.
1465 -* 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
1466 1466  * Click the **JavaScript** button.
1467 -* 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.
1468 1468  * Click the **Next** button. You will be navigated to the **Connection** tab.
1469 1469  
1470 1470  [[image:thingseye-io-step-4.png||height="625" width="1000"]]
... ... @@ -1474,7 +1474,7 @@
1474 1474  
1475 1475  * Choose **Region** from the **Host type**.
1476 1476  * 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/...).
1477 -* 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).
1478 1478  * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
1479 1479  
1480 1480  [[image:message-1.png]]
... ... @@ -1493,7 +1493,7 @@
1493 1493  
1494 1494  **Viewing integration details**:
1495 1495  
1496 -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.
1497 1497  
1498 1498  [[image:integration-details.png||height="686" width="1000"]]
1499 1499  
... ... @@ -1500,25 +1500,24 @@
1500 1500  
1501 1501  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.
1502 1502  
1503 -{{info}}
1504 -See also ThingsEye documentation.
1505 -{{/info}}
1479 +Note: See also ThingsEye documentation.
1506 1506  
1481 +
1507 1507  **Viewing events:**
1508 1508  
1509 -The **Events **tab displays all the uplink messages from the LT-22222-L.
1484 +This tab  displays all the uplink messages from the LT-22222-L.
1510 1510  
1486 +* Click on the **Events **tab.
1511 1511  * Select **Debug **from the **Event type** dropdown.
1512 1512  * Select the** time frame** from the **time window**.
1513 1513  
1514 -[[image:thingseye-events.png||height="686" width="1000"]]
1490 +[insert image]
1515 1515  
1492 +- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
1516 1516  
1517 -* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
1494 +[insert image]
1518 1518  
1519 -[[image:thingseye-json.png||width="1000"]]
1520 1520  
1521 -
1522 1522  **Deleting the integration**:
1523 1523  
1524 1524  If you want to delete this integration, click the **Delete integratio**n button.
... ... @@ -1737,11 +1737,10 @@
1737 1737  
1738 1738  == 3.7 LEDs Indicators ==
1739 1739  
1740 -The table below lists the behavior of LED indicators for each port function.
1741 1741  
1742 1742  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1743 1743  |(% style="background-color:#4f81bd; color:white; width:50px" %)**LEDs**|(% style="background-color:#4f81bd; color:white; width:460px" %)**Feature**
1744 -|**PWR**|Always on when there is power
1718 +|**PWR**|Always on if there is power
1745 1745  |**TX**|(((
1746 1746  (((
1747 1747  Device boot: TX blinks 5 times.
... ... @@ -1748,7 +1748,7 @@
1748 1748  )))
1749 1749  
1750 1750  (((
1751 -Successful network join: TX remains ON for 5 seconds.
1725 +Successful join network: TX ON for 5 seconds.
1752 1752  )))
1753 1753  
1754 1754  (((
... ... @@ -1755,7 +1755,7 @@
1755 1755  Transmit a LoRa packet: TX blinks once
1756 1756  )))
1757 1757  )))
1758 -|**RX**|RX blinks once when a packet is received.
1732 +|**RX**|RX blinks once when receiving a packet.
1759 1759  |**DO1**|For LT-22222-L: ON when DO1 is low, OFF when DO1 is high
1760 1760  |**DO2**|For LT-22222-L: ON when DO2 is low, OFF when DO2 is high
1761 1761  |**DI1**|(((
... ... @@ -1794,7 +1794,7 @@
1794 1794  )))
1795 1795  
1796 1796  (((
1797 -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.
1798 1798  
1799 1799  * AT+<CMD>? : Help on <CMD>
1800 1800  * AT+<CMD> : Run <CMD>
... ... @@ -1853,28 +1853,28 @@
1853 1853  
1854 1854  
1855 1855  (((
1856 -(% 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:**
1857 1857  )))
1858 1858  )))
1859 1859  
1860 1860  (((
1861 -(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**##
1835 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**##
1862 1862  )))
1863 1863  
1864 1864  (((
1865 -(% 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**##
1866 1866  )))
1867 1867  
1868 1868  (((
1869 -(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**##
1843 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**##
1870 1870  )))
1871 1871  
1872 1872  (((
1873 -(% style="background-color:#dcdcdc" %)##**AT+NJM=0 ~/~/Set to ABP mode**##
1847 +(% style="background-color:#dcdcdc" %)##**AT+NJM=0 ~/~/set to ABP mode**##
1874 1874  )))
1875 1875  
1876 1876  (((
1877 -(% style="background-color:#dcdcdc" %)##**ATZ ~/~/Reset MCU**##
1851 +(% style="background-color:#dcdcdc" %)##**ATZ ~/~/reset MCU**##
1878 1878  )))
1879 1879  
1880 1880  
... ... @@ -1897,20 +1897,20 @@
1897 1897  
1898 1898  
1899 1899  (((
1900 -(% style="background-color:#dcdcdc" %)**123456**(%%)  ~/~/ Enter password to enable AT commands access
1874 +(% style="background-color:#dcdcdc" %)**123456**(%%)  ~/~/ Enter Password to have AT access.
1901 1901  )))
1902 1902  )))
1903 1903  
1904 1904  (((
1905 -(% 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
1906 1906  )))
1907 1907  
1908 1908  (((
1909 -(% style="background-color:#dcdcdc" %)** 123456**(%%)  ~/~/ Enter password to enable AT commands access
1883 +(% style="background-color:#dcdcdc" %)** 123456**(%%)  ~/~/ Enter Password to have AT access.
1910 1910  )))
1911 1911  
1912 1912  (((
1913 -(% 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
1914 1914  )))
1915 1915  
1916 1916  (((
... ... @@ -1930,19 +1930,19 @@
1930 1930  )))
1931 1931  
1932 1932  (((
1933 -(% 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
1934 1934  )))
1935 1935  
1936 1936  (((
1937 -(% 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)
1938 1938  )))
1939 1939  
1940 1940  (((
1941 -(% 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
1942 1942  )))
1943 1943  
1944 1944  (((
1945 -(% 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.
1946 1946  )))
1947 1947  
1948 1948  (((
... ... @@ -1956,14 +1956,14 @@
1956 1956  )))
1957 1957  
1958 1958  (((
1959 -**~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.**
1960 1960  
1961 -**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.**
1962 1962  
1963 -**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?
1964 1964  dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.**
1965 1965  
1966 -**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.**
1967 1967  )))
1968 1968  
1969 1969  (((
... ... @@ -1987,18 +1987,20 @@
1987 1987  
1988 1988  == 5.1 Counting how many objects pass through the flow Line ==
1989 1989  
1990 -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]]?
1991 1991  
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]]?
1992 1992  
1967 +
1993 1993  = 6. FAQ =
1994 1994  
1995 1995  This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
1996 1996  
1997 -
1998 1998  == 6.1 How to update the firmware? ==
1999 1999  
2000 -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.
2001 2001  
1976 +Updating your LT-22222-L with the latest firmware version helps to:
1977 +
2002 2002  * Support new features
2003 2003  * Fix bugs
2004 2004  * Change LoRaWAN frequency bands
... ... @@ -2016,8 +2016,8 @@
2016 2016  
2017 2017  Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2018 2018  
2019 -[[image:usb-ttl-programming.png]]
2020 2020  
1996 +[[image:1653359603330-121.png]]
2021 2021  
2022 2022  
2023 2023  Start the STM32 Flash Loader and choose the correct COM port to update.
... ... @@ -2041,7 +2041,7 @@
2041 2041  [[image:image-20220524104033-15.png]]
2042 2042  
2043 2043  
2044 -(% 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:
2045 2045  
2046 2046  [[image:1653360054704-518.png||height="186" width="745"]]
2047 2047  
... ... @@ -2049,6 +2049,8 @@
2049 2049  (((
2050 2050  (((
2051 2051  == 6.2 How to change the LoRaWAN frequency band/region? ==
2028 +
2029 +
2052 2052  )))
2053 2053  )))
2054 2054  
... ... @@ -2059,18 +2059,20 @@
2059 2059  (((
2060 2060  
2061 2061  
2062 -== 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 +
2063 2063  )))
2064 2064  
2065 2065  (((
2066 2066  (((
2067 -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.
2068 2068  )))
2069 2069  )))
2070 2070  
2071 2071  (((
2072 2072  (((
2073 -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.
2074 2074  
2075 2075  
2076 2076  )))
... ... @@ -2077,55 +2077,52 @@
2077 2077  )))
2078 2078  
2079 2079  (((
2080 -(% 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.
2081 2081  
2082 -[[image:lt-22222-l-abp.png||height="686" width="1000"]]
2062 +
2083 2083  )))
2084 2084  
2085 2085  (((
2066 +[[image:1653360231087-571.png||height="401" width="727"]]
2067 +
2086 2086  
2087 2087  )))
2088 2088  
2089 -{{warning}}
2090 -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.
2091 -{{/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 +)))
2092 2092  
2093 2093  
2076 +
2094 2094  (((
2095 -(% 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:
2096 2096  
2097 2097  
2098 2098  )))
2099 2099  
2100 2100  (((
2101 -(% style="background-color:#dcdcdc" %)**123456** (%%) : Enter the password to enable AT access.
2084 +(% style="background-color:#dcdcdc" %)**123456** (%%) :  Enter Password to have AT access.
2102 2102  
2103 -(% 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
2104 2104  
2105 -(% style="background-color:#dcdcdc" %)**AT+NJM=0** (%%) : Set to ABP mode.
2088 +(% style="background-color:#dcdcdc" %)**AT+NJM=0** (%%) :  Set to ABP mode
2106 2106  
2107 -(% 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
2108 2108  
2109 -(% 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)
2110 2110  
2111 -(% 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
2112 2112  
2113 -(% 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
2114 2114  
2115 -(% 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
2116 2116  
2117 -(% 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)
2118 -
2119 -(% 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)
2120 -
2121 -(% 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)
2122 -
2123 -(% style="background-color:#dcdcdc" %)**ATZ**        (%%) : Reset MCU.
2100 +(% style="background-color:#dcdcdc" %)**ATZ**        (%%) :  Reset MCU
2124 2124  )))
2125 2125  
2126 2126  
2127 2127  (((
2128 -(% 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:
2129 2129  )))
2130 2130  
2131 2131  [[image:1653360498588-932.png||height="485" width="726"]]
... ... @@ -2133,33 +2133,35 @@
2133 2133  
2134 2134  == 6.4 How to change the uplink interval? ==
2135 2135  
2113 +
2136 2136  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/]]
2137 2137  
2138 2138  
2139 2139  == 6.5 Can I see the counting event in the serial output? ==
2140 2140  
2119 +
2141 2141  (((
2142 -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.
2143 2143  
2144 2144  
2145 2145  == 6.6 Can I use point-to-point communication with LT-22222-L? ==
2146 2146  
2147 -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]].
2148 2148  
2149 -
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]].
2150 2150  )))
2151 2151  
2152 2152  (((
2153 2153  == 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
2154 2154  
2133 +
2155 2155  * If the device is not properly shut down and is directly powered off.
2156 2156  * It will default to a power-off state.
2157 2157  * In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
2158 2158  * After a restart, the status before the power failure will be read from flash.
2159 2159  
2160 -
2161 2161  == 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
2162 2162  
2141 +
2163 2163  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:
2164 2164  
2165 2165  
... ... @@ -2168,24 +2168,24 @@
2168 2168  
2169 2169  == 6.9 Can the LT-22222-L save the RO state? ==
2170 2170  
2171 -To enable this feature, the firmware version must be 1.6.0 or higher.
2172 2172  
2151 +The firmware version must be at least 1.6.0.
2173 2173  
2153 +
2174 2174  == 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
2175 2175  
2156 +
2176 2176  It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
2177 2177  
2178 2178  
2179 2179  = 7. Troubleshooting =
2180 -
2181 -This section provides some known troubleshooting tips.
2182 -
2183 -
2184 2184  )))
2185 2185  
2186 2186  (((
2187 2187  (((
2188 2188  == 7.1 Downlink isn't working. How can I solve this? ==
2166 +
2167 +
2189 2189  )))
2190 2190  )))
2191 2191  
... ... @@ -2197,6 +2197,8 @@
2197 2197  
2198 2198  
2199 2199  == 7.2 Having trouble uploading an image? ==
2179 +
2180 +
2200 2200  )))
2201 2201  
2202 2202  (((
... ... @@ -2207,6 +2207,8 @@
2207 2207  
2208 2208  
2209 2209  == 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
2191 +
2192 +
2210 2210  )))
2211 2211  
2212 2212  (((
... ... @@ -2214,8 +2214,9 @@
2214 2214  )))
2215 2215  
2216 2216  
2217 -== 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? ==
2218 2218  
2202 +
2219 2219  The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
2220 2220  Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2221 2221  
... ... @@ -2222,6 +2222,7 @@
2222 2222  
2223 2223  = 8. Ordering information =
2224 2224  
2209 +
2225 2225  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
2226 2226  
2227 2227  (% style="color:#4f81bd" %)**XXX:**
... ... @@ -2236,15 +2236,15 @@
2236 2236  * (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865
2237 2237  * (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779
2238 2238  
2224 += 9. Packing information =
2239 2239  
2240 -= 9. Package information =
2241 2241  
2242 2242  **Package includes**:
2243 2243  
2244 -* 1 x LT-22222-L I/O Controller
2245 -* 1 x LoRa antenna matched to the frequency of the LT-22222-L
2246 -* 1 x bracket for DIN rail mounting
2247 -* 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
2248 2248  
2249 2249  **Dimension and weight**:
2250 2250  
... ... @@ -2253,9 +2253,9 @@
2253 2253  * Package Size / pcs : 14.5 x 8 x 5 cm
2254 2254  * Weight / pcs : 170 g
2255 2255  
2256 -
2257 2257  = 10. Support =
2258 2258  
2243 +
2259 2259  * (((
2260 2260  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.
2261 2261  )))
... ... @@ -2267,6 +2267,7 @@
2267 2267  
2268 2268  = 11. Reference​​​​​ =
2269 2269  
2255 +
2270 2270  * 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]]
2271 2271  * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]]
2272 2272  * [[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
usb-ttl-programming.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -462.9 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0