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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -LT-22222-L -- LoRa I/O Controller User Manual
1 +LT-22222-L -- LoRa IO Controller User Manual
Content
... ... @@ -40,9 +40,7 @@
40 40  * If there is no public LoRaWAN coverage in your area, you can set up a LoRaWAN gateway, or multiple gateways, and connect them to a LoRaWAN network server to create adequate coverage. Then, register the LT-22222-L I/O controller with this network.
41 41  * Setup your own private LoRaWAN network.
42 42  
43 -{{info}}
44 - You can use a LoRaWAN gateway, such as the [[Dragino LG308>>https://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], to expand or create LoRaWAN coverage in your area.
45 -{{/info}}
43 +> You can use a LoRaWAN gateway, such as the Dragino LG308, to expand or create LoRaWAN coverage in your area.
46 46  )))
47 47  
48 48  (((
... ... @@ -58,13 +58,13 @@
58 58  * STM32L072xxxx MCU
59 59  * SX1276/78 Wireless Chip 
60 60  * Power Consumption:
61 -** Idle: 4mA@12V
59 +** Idle: 4mA@12v
62 62  ** 20dB Transmit: 34mA@12V
63 63  * Operating Temperature: -40 ~~ 85 Degrees, No Dew
64 64  
65 65  (% style="color:#037691" %)**Interface for Model: LT22222-L:**
66 66  
67 -* 2 x Digital dual direction Input (Detect High/Low signal, Max: 50V, or 220V with optional external resistor)
65 +* 2 x Digital dual direction Input (Detect High/Low signal, Max: 50v, or 220v with optional external resistor)
68 68  * 2 x Digital Output (NPN output. Max pull-up voltage 36V,450mA)
69 69  * 2 x Relay Output (5A@250VAC / 30VDC)
70 70  * 2 x 0~~20mA Analog Input (res:0.01mA)
... ... @@ -74,8 +74,8 @@
74 74  (% style="color:#037691" %)**LoRa Spec:**
75 75  
76 76  * Frequency Range:
77 -** Band 1 (HF): 862 ~~ 1020 MHz
78 -** Band 2 (LF): 410 ~~ 528 MHz
75 +** Band 1 (HF): 862 ~~ 1020 Mhz
76 +** Band 2 (LF): 410 ~~ 528 Mhz
79 79  * 168 dB maximum link budget.
80 80  * +20 dBm - 100 mW constant RF output vs.
81 81  * +14 dBm high-efficiency PA.
... ... @@ -94,7 +94,7 @@
94 94  
95 95  == 1.3 Features ==
96 96  
97 -* LoRaWAN Class A & Class C modes
95 +* LoRaWAN Class A & Class C protocol
98 98  * Optional Customized LoRa Protocol
99 99  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
100 100  * AT Commands to change parameters
... ... @@ -104,27 +104,45 @@
104 104  
105 105  == 1.4 Applications ==
106 106  
107 -* Smart buildings & home automation
108 -* Logistics and supply chain management
109 -* Smart metering
110 -* Smart agriculture
111 -* Smart cities
112 -* Smart factory
105 +* Smart Buildings & Home Automation
106 +* Logistics and Supply Chain Management
107 +* Smart Metering
108 +* Smart Agriculture
109 +* Smart Cities
110 +* Smart Factory
113 113  
114 -= 2. Assembling the device =
112 +== 1.5 Hardware Variants ==
115 115  
116 -== 2.1 Connecting the antenna ==
117 117  
118 -Connect the LoRa antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper screw terminal block. Secure the antenna by tightening it clockwise.
115 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %)
116 +|(% style="background-color:#4f81bd; color:white; width:103px" %)**Model**|(% style="background-color:#4f81bd; color:white; width:131px" %)**Photo**|(% style="background-color:#4f81bd; color:white; width:266px" %)**Description**
117 +|(% style="width:103px" %)**LT22222-L**|(% style="width:131px" %)(((
118 +(% style="text-align:center" %)
119 +[[image:image-20230424115112-1.png||height="106" width="58"]]
120 +)))|(% style="width:334px" %)(((
121 +* 2 x Digital Input (Bi-direction)
122 +* 2 x Digital Output
123 +* 2 x Relay Output (5A@250VAC / 30VDC)
124 +* 2 x 0~~20mA Analog Input (res:0.01mA)
125 +* 2 x 0~~30V Analog Input (res:0.01v)
126 +* 1 x Counting Port
127 +)))
119 119  
120 -{{warning}}
121 -Warning! Do not power on the device without connecting the antenna.
122 -{{/warning}}
129 += 2. Assembling the Device =
123 123  
124 -== 2.2 Terminals ==
131 +== 2.1 What is included in the package? ==
125 125  
126 -The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 terminals and the lower screw terminal block has 10 terminals.
133 +The package includes the following items:
127 127  
135 +* 1 x LT-22222-L I/O Controller
136 +* 1 x LoRaWAN antenna matched to the frequency of the LT-22222-L
137 +* 1 x bracket for DIN rail mounting
138 +* 1 x programming cable
139 +
140 +Attach the LoRaWAN antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper terminal block. Secure the antenna by tightening it clockwise.
141 +
142 +== 2.2 Terminals ==
143 +
128 128  Upper screw terminal block (from left to right):
129 129  
130 130  (% style="width:634px" %)
... ... @@ -151,28 +151,26 @@
151 151  |(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
152 152  |(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
153 153  
154 -== 2.3 Powering the device ==
170 +== 2.3 Powering the LT-22222-L ==
155 155  
156 -The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s positive wire to the VIN and the negative wire to the GND screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered.
172 +The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect the power supply’s positive wire to the VIN and the negative wire to the GND screw terminals. The power indicator (PWR) LED will turn on when the device is properly powered.
157 157  
158 -Once powered, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** The Things Stack. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LED** will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status.
159 159  
160 -{{warning}}
161 -We recommend that you power on the LT-22222-L after configuring its registration information with a LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.
162 -{{/warning}}
163 -
164 -
165 165  [[image:1653297104069-180.png]]
166 166  
167 167  
168 -= 3. Registering with a LoRaWAN Network Server =
178 += 3. Operation Mode =
169 169  
180 +== 3.1 How does it work? ==
181 +
170 170  By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode. It supports OTAA (Over-the-Air Activation), the most secure method for activating a device with a LoRaWAN network server. The LT-22222-L comes with device registration information that allows you to register it with a LoRaWAN network, enabling the device to perform OTAA activation with the network server upon initial power-up and after any subsequent reboots.
171 171  
172 -After powering on, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** the LoRaWAN network. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LED** will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status.
184 +After powering on, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** the LoRaWAN network. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LE**D will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status.
173 173  
174 174  In case you can't set the root key and other identifiers in the network server and must use them from the server, you can use [[AT Commands>>||anchor="H4.UseATCommand"]] to configure them on the device.
175 175  
188 +== 3.2 Registering with a LoRaWAN network server ==
189 +
176 176  The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
177 177  
178 178  [[image:image-20220523172350-1.png||height="266" width="864"]]
... ... @@ -187,33 +187,28 @@
187 187  
188 188  === 3.2.2 The Things Stack Sandbox (TTSS) ===
189 189  
190 -The Things Stack Sandbox was formally called The Things Stack Community Edition.
191 -
192 192  * Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account.
193 -* Create an application with The Things Stack if you do not have one yet.
194 -* Go to your application page and click on the **End devices** in the left menu.
195 -* On the End devices page, click on **+ Register end device**. Two registration options are available:
205 +* Create an application if you do not have one yet.
206 +* Register LT-22222-L with that application. Two registration options are available:
196 196  
208 +==== ====
209 +
197 197  ==== 3.2.2.1 Using the LoRaWAN Device Repository ====
198 198  
212 +* Go to your application and click on the **Register end device** button.
199 199  * On the **Register end device** page:
200 -** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
201 -** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists.
202 -*** **End device brand**: Dragino Technology Co., Limited
203 -*** **Model**: LT22222-L I/O Controller
204 -*** **Hardware ver**: Unknown
205 -*** **Firmware ver**: 1.6.0
206 -*** **Profile (Region)**: Select the region that matches your device.
207 -** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
214 +** Select the option **Select the end device in the LoRaWAN Device Repository**.
215 +** Choose the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)**.
216 +** Select the **Frequency plan** that matches your device.
208 208  
209 209  [[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
210 210  
211 211  
212 -* Register end device page continued...
213 -** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network'.
214 -** In the **DevEUI** field, enter the **DevEUI**.
215 -** In the **AppKey** field, enter the **AppKey.**
216 -** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
221 +* Page continued...
222 +** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
223 +** Enter the **DevEUI** in the **DevEUI** field.
224 +** Enter the **AppKey** in the **AppKey** field.
225 +** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
217 217  ** Under **After registration**, select the **View registered end device** option.
218 218  
219 219  [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
... ... @@ -220,25 +220,25 @@
220 220  
221 221  ==== ====
222 222  
223 -==== 3.2.2.2 Adding device manually ====
232 +==== 3.2.2.2 Entering device information manually ====
224 224  
225 225  * On the **Register end device** page:
226 -** Select the option **Enter end device specifies manually** under **Input method**.
227 -** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
228 -** Select the **LoRaWAN version** as **LoRaWAN Specification 1.0.3**
229 -** Select the **Regional Parameters version** as** RP001 Regional Parameters 1.0.3 revision A**
230 -** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the hidden section.
231 -** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
232 -** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
235 +** Select the **Enter end device specifies manually** option as the input method.
236 +** Select the **Frequency plan** that matches your device.
237 +** Select the **LoRaWAN version**.
238 +** Select the **Regional Parameters version**.
239 +** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the section.
240 +** Select **Over the air activation (OTAA)** option under the **Activation mode**
241 +** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities**.
233 233  
234 234  [[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
235 235  
236 236  
237 -* Register end device page continued...
238 -** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network'
239 -** In the **DevEUI** field, enter the **DevEUI**.
240 -** In the **AppKey** field, enter the **AppKey**.
241 -** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
246 +* Page continued...
247 +** Enter **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
248 +** Enter **DevEUI** in the **DevEUI** field.
249 +** Enter **AppKey** in the **AppKey** field.
250 +** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
242 242  ** Under **After registration**, select the **View registered end device** option.
243 243  ** Click the **Register end device** button.
244 244  
... ... @@ -253,15 +253,15 @@
253 253  
254 254  ==== 3.2.2.3 Joining ====
255 255  
256 -On the Device overview page, click on **Live data** tab. The Live data panel for your device will display.
265 +Click on **Live data** in the left navigation. The Live data panel for your application will display.
257 257  
258 -Now power on your LT-22222-L. It will begin joining The Things Stack. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server. Once successfully joined, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**).
267 +Power on your LT-22222-L. It will begin joining The Things Stack LoRaWAN network server. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server. Once successfully joined, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**).
259 259  
260 260  
261 261  [[image:lt-22222-join-network.png||height="625" width="1000"]]
262 262  
263 263  
264 -By default, you will receive an uplink data message from the device every 10 minutes.
273 +By default, you will receive an uplink data message every 10 minutes.
265 265  
266 266  Click on one of a **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the decode_payload {} JSON object.
267 267  
... ... @@ -270,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,181 +810,107 @@
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 -
840 840  ==== 3.4.2.1 Set Transmit Interval ====
841 841  
842 842  Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
843 843  
844 -(% style="color:#037691" %)**AT command**
827 +* (% style="color:#037691" %)**AT command:**
845 845  
846 -(% style="width:500px" %)
847 -|**Command**|AT+TDC<time>
848 -|**Response**|
849 -|**Parameters**|time : uplink interval is in milliseconds
850 -|**Example**|(((
851 -AT+TDC=30000
829 +(% style="color:blue" %)**AT+TDC=N**
852 852  
853 -Sets the uplink interval to 30,000 milliseconds (30 seconds)
854 -)))
831 +where N is the time in milliseconds.
855 855  
856 -(% style="color:#037691" %)**Downlink payload**
833 +**Example: **AT+TDC=30000. This will set the uplink interval to 30 seconds
857 857  
858 -(% style="width:500px" %)
859 -|**Payload**|(((
860 -<prefix><time>
861 -)))
862 -|**Parameters**|(((
863 -prefix : 0x01
864 864  
865 -time : uplink interval is in milliseconds, represented by 3  bytes in hexadecimal.
866 -)))
867 -|**Example**|(((
868 -01 **00 75 30**
836 +* (% style="color:#037691" %)**Downlink payload (prefix 0x01):**
869 869  
870 -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)**
871 871  
872 -Conversion: 30000 (dec) = 00 75 30 (hex)
873 873  
874 -See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]]
875 -)))
876 876  
842 +==== 3.4.2.2 Set the Work Mode (AT+MOD) ====
877 877  
878 -==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
879 879  
880 -Sets the working mode.
845 +Sets the work mode.
881 881  
882 -(% style="color:#037691" %)**AT command**
847 +* (% style="color:#037691" %)**AT command:**(%%) (% style="color:blue" %)**AT+MOD=N  **
883 883  
884 -(% style="width:500px" %)
885 -|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE<working_mode>
886 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)
887 -|(% style="width:97px" %)**Parameters**|(% style="width:413px" %)(((
888 -working_mode :
849 +Where N is the work mode.
889 889  
890 -1 = (Default mode/factory set):  2ACI + 2AVI + DI + DO + RO
851 +**Example**: AT+MOD=2. This will set the work mode to Double DI counting mode.
891 891  
892 -2 = Double DI Counting + DO + RO
893 893  
894 -3 = Single DI Counting + 2 x ACI + DO + RO
854 +* (% style="color:#037691" %)**Downlink payload (prefix 0x0A):**
895 895  
896 -4 = Single DI Counting + 1 x Voltage Counting + DO + RO
856 +(% style="color:blue" %)**0x0A aa  **(%%)** ** ~/~/ Same as AT+MOD=aa
897 897  
898 -5 = Single DI Counting + 2 x AVI + 1 x ACI + DO + RO
899 899  
900 -6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5
901 -)))
902 -|(% style="width:97px" %)**Example**|(% style="width:413px" %)(((
903 -AT+MOD=2
904 904  
905 -Sets the device to working mode 2 (Double DI Counting + DO + RO)
906 -)))
907 -
908 -
909 -(% class="wikigeneratedid" %)
910 -(% style="color:#037691" %)**Downlink payload**
911 -
912 -(% style="width:500px" %)
913 -|(% style="width:98px" %)**Payload**|(% style="width:400px" %)<prefix><working_mode>
914 -|(% style="width:98px" %)**Parameters**|(% style="width:400px" %)(((
915 -prefix : 0x0A
916 -
917 -working_mode : Working mode, represented by 1 byte in hexadecimal.
918 -)))
919 -|(% style="width:98px" %)**Example**|(% style="width:400px" %)(((
920 -0A **02**
921 -
922 -Sets the device to working mode 2 (Double DI Counting + DO + RO)
923 -)))
924 -
925 -
926 926  ==== 3.4.2.3 Poll an uplink ====
927 927  
928 -Requests an uplink from LT-22222-L.
929 929  
930 -(% style="color:#037691" %)**AT command**
863 +Asks the device to send an uplink.
931 931  
932 -There is no AT Command to request an uplink from LT-22222-L
865 +* (% style="color:#037691" %)**AT command:**(%%) There is no AT Command to poll uplink
933 933  
934 -(% style="color:#037691" %)**Downlink payload**
867 +* (% style="color:#037691" %)**Downlink payload (prefix 0x08):**
935 935  
936 -(% style="width:500px" %)
937 -|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF
938 -|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)prefix : 0x08
939 -|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
940 -08 FF
869 +(% style="color:blue" %)**0x08 FF  **(%%)** **~/~/ Poll an uplink
941 941  
942 -Requests an uplink from LT-22222-L.
943 -)))
871 +**Example**: 0x08FF, ask device to send an Uplink
944 944  
945 945  
874 +
946 946  ==== 3.4.2.4 Enable/Disable Trigger Mode ====
947 947  
948 -Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
949 949  
950 -(% style="color:#037691" %)**AT Command**
878 +Enable or disable the trigger mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
951 951  
952 -(% style="width:500px" %)
953 -|(% style="width:95px" %)**Command**|(% style="width:403px" %)AT+ADDMOD6=<enable/disable trigger_mode>
954 -|(% style="width:95px" %)**Response**|(% style="width:403px" %)
955 -|(% style="width:95px" %)**Parameters**|(% style="width:403px" %)(((
956 -enable/disable trigger_mode :
880 +* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0**
957 957  
958 -1 = enable trigger mode
882 +(% style="color:red" %)**1:** (%%)Enable the trigger mode
959 959  
960 -0 = disable trigger mode
961 -)))
962 -|(% style="width:95px" %)**Example**|(% style="width:403px" %)(((
963 -AT+ADDMOD6=1
884 +(% style="color:red" %)**0: **(%%)Disable the trigger mode
964 964  
965 -Enable trigger mode for the current working mode
966 -)))
967 967  
968 -(% style="color:#037691" %)**Downlink payload**
887 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A 06):**
969 969  
970 -(% style="width:500px" %)
971 -|(% style="width:97px" %)**Payload**|(% style="width:401px" %)<prefix><enable/disable trigger_mode>
972 -|(% style="width:97px" %)**Parameters**|(% style="width:401px" %)(((
973 -prefix : 0x0A 06
889 +(% style="color:blue" %)**0x0A 06 aa    **(%%) ~/~/ Same as AT+ADDMOD6=aa
974 974  
975 -working mode : enable (1) or disable (0), represented by 1 byte in hexadecimal.
976 -)))
977 -|(% style="width:97px" %)**Example**|(% style="width:401px" %)(((
978 -0A 06 **01**
979 979  
980 -Enable trigger mode for the current working mode
981 -)))
982 982  
983 -
984 984  ==== 3.4.2.5 Poll trigger settings ====
985 985  
986 -Polls the trigger settings.
987 987  
896 +Polls the trigger settings
897 +
988 988  * (% style="color:#037691" %)**AT Command:**
989 989  
990 990  There is no AT Command for this feature.
... ... @@ -994,15 +994,11 @@
994 994  (% style="color:blue" %)**0xAB 06  ** (%%) ~/~/ Poll the trigger settings. Device will uplink trigger settings once receive this command
995 995  
996 996  
997 -(% style="width:500px" %)
998 -|(% style="width:95px" %)**Payload**|(% style="width:403px" %)<prefix>
999 -|(% style="width:95px" %)**Parameters**|(% style="width:403px" %)prefix : AB 06
1000 -|(% style="width:95px" %)**Example**|(% style="width:403px" %)AB 06
1001 1001  
908 +==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ====
1002 1002  
1003 -==== 3.4.2.6 Enable / Disable DI1/DI2 as a trigger ====
1004 1004  
1005 -Enable or disable DI1/DI2 as a trigger.
911 +Enable or Disable DI1/DI2/DI2 as trigger,
1006 1006  
1007 1007  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
1008 1008  
... ... @@ -1014,29 +1014,12 @@
1014 1014  (% style="color:blue" %)**0xAA 02 aa bb   ** (%%) ~/~/ Same as AT+DTRI=aa,bb
1015 1015  
1016 1016  
1017 -(% style="width:500px" %)
1018 -|(% style="width:98px" %)Command|(% style="width:400px" %)AT+DTRI=<DI1_trigger><DI2_trigger>
1019 -|(% style="width:98px" %)Response|(% style="width:400px" %)
1020 -|(% style="width:98px" %)Parameters|(% style="width:400px" %)(((
1021 -DI1_trigger:
1022 1022  
1023 -1 = enable DI_1 trigger
924 +==== 3.4.2.7 Trigger1 – Set DI1 or DI3 as trigger ====
1024 1024  
1025 -0 = disable DI_1 trigger
1026 1026  
1027 -DI2 _trigger
927 +Set DI1 or DI3(for LT-33222-L) trigger.
1028 1028  
1029 -1 = enable D2_1 trigger
1030 -
1031 -0 = disable D2_1 trigger
1032 -)))
1033 -|(% style="width:98px" %)Example|(% style="width:400px" %)
1034 -
1035 -
1036 -==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ====
1037 -
1038 -Sets DI1 or DI3 (for LT-33222-L) as a trigger.
1039 -
1040 1040  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG1=a,b**
1041 1041  
1042 1042  (% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
... ... @@ -1051,10 +1051,12 @@
1051 1051  (% style="color:blue" %)**0x09 01 aa bb cc    ** (%%) ~/~/ same as AT+TRIG1=aa,0x(bb cc)
1052 1052  
1053 1053  
1054 -==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
1055 1055  
1056 -Sets DI2 as a trigger.
944 +==== 3.4.2.8 Trigger2 – Set DI2 as trigger ====
1057 1057  
946 +
947 +Sets DI2 trigger.
948 +
1058 1058  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b**
1059 1059  
1060 1060  (% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
... ... @@ -1069,10 +1069,12 @@
1069 1069  (% style="color:blue" %)**0x09 02 aa bb cc   ** (%%)~/~/ same as AT+TRIG2=aa,0x(bb cc)
1070 1070  
1071 1071  
1072 -==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
1073 1073  
1074 -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 ====
1075 1075  
966 +
967 +Set current trigger , base on AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
968 +
1076 1076  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ACLIM**
1077 1077  
1078 1078  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 01 )**
... ... @@ -1083,8 +1083,9 @@
1083 1083  
1084 1084  ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
1085 1085  
1086 -Sets the current trigger based on the AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1087 1087  
980 +Set current trigger , base on AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
981 +
1088 1088  * (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+AVLIM    **(%%)** See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]**
1089 1089  
1090 1090  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 00 )**
... ... @@ -1092,8 +1092,10 @@
1092 1092  (% 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"]]
1093 1093  
1094 1094  
989 +
1095 1095  ==== 3.4.2.11 Trigger – Set minimum interval ====
1096 1096  
992 +
1097 1097  Sets AV and AC trigger minimum interval. Device won't response to the second trigger within this set time after the first trigger.
1098 1098  
1099 1099  * (% 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.
... ... @@ -1110,7 +1110,6 @@
1110 1110  
1111 1111  ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
1112 1112  
1113 -Controls the digital outputs DO1, DO2, and DO3
1114 1114  
1115 1115  * (% style="color:#037691" %)**AT Command**
1116 1116  
... ... @@ -1488,25 +1488,25 @@
1488 1488  
1489 1489  == 3.5 Integrating with ThingsEye.io ==
1490 1490  
1491 -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.
1492 1492  
1493 -=== 3.5.1 Configuring The Things Stack ===
1388 +=== 3.5.1 Configuring MQTT Connection Information with The Things Stack Sandbox ===
1494 1494  
1495 -We use The Things Stack Sandbox in this example:
1390 +We use The Things Stack Sandbox for demonstating the configuration but  other
1496 1496  
1497 -* In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
1498 -* Select **MQTT** under **Integrations** in the left menu.
1499 -* 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.
1500 -* 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.
1501 1501  
1502 -{{info}}
1503 -The username and  password (API key) you created here are required in the next section.
1504 -{{/info}}
1397 +NOTE. The username and  password (API key) you created here are required in the next section.
1505 1505  
1506 1506  [[image:tts-mqtt-integration.png||height="625" width="1000"]]
1507 1507  
1508 1508  === 3.5.2 Configuring ThingsEye.io ===
1509 1509  
1403 +This section guides you on how to create an integration in ThingsEye to connect with The Things Stack MQTT server.
1404 +
1510 1510  * Login to your [[ThingsEye.io >>https://thingseye.io]]account.
1511 1511  * Under the **Integrations center**, click **Integrations**.
1512 1512  * Click the **Add integration** button (the button with the **+** symbol).
... ... @@ -1543,9 +1543,9 @@
1543 1543  **Downlink data converter (this is an optional step):**
1544 1544  
1545 1545  * Click the **Create new** button if it is not selected by default.
1546 -* 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
1547 1547  * Click the **JavaScript** button.
1548 -* 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.
1549 1549  * Click the **Next** button. You will be navigated to the **Connection** tab.
1550 1550  
1551 1551  [[image:thingseye-io-step-4.png||height="625" width="1000"]]
... ... @@ -1555,7 +1555,7 @@
1555 1555  
1556 1556  * Choose **Region** from the **Host type**.
1557 1557  * 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/...).
1558 -* 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).
1559 1559  * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
1560 1560  
1561 1561  [[image:message-1.png]]
... ... @@ -1572,9 +1572,9 @@
1572 1572  [[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
1573 1573  
1574 1574  
1575 -==== 3.5.2.1 Viewing integration details ====
1470 +**Viewing integration details**:
1576 1576  
1577 -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.
1578 1578  
1579 1579  [[image:integration-details.png||height="686" width="1000"]]
1580 1580  
... ... @@ -1581,30 +1581,29 @@
1581 1581  
1582 1582  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.
1583 1583  
1584 -{{info}}
1585 -See also ThingsEye documentation.
1586 -{{/info}}
1479 +Note: See also ThingsEye documentation.
1587 1587  
1588 -==== **3.5.2.2 Viewing events** ====
1589 1589  
1590 -The **Events **tab displays all the uplink messages from the LT-22222-L.
1482 +**Viewing events:**
1591 1591  
1484 +This tab  displays all the uplink messages from the LT-22222-L.
1485 +
1486 +* Click on the **Events **tab.
1592 1592  * Select **Debug **from the **Event type** dropdown.
1593 1593  * Select the** time frame** from the **time window**.
1594 1594  
1595 -[[image:thingseye-events.png||height="686" width="1000"]]
1490 +[insert image]
1596 1596  
1492 +- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
1597 1597  
1598 -* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
1494 +[insert image]
1599 1599  
1600 -[[image:thingseye-json.png||width="1000"]]
1601 1601  
1497 +**Deleting the integration**:
1602 1602  
1603 -==== **3.5.2.3 Deleting an integration** ====
1499 +If you want to delete this integration, click the **Delete integratio**n button.
1604 1604  
1605 -If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
1606 1606  
1607 -
1608 1608  == 3.6 Interface Details ==
1609 1609  
1610 1610  === 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) ===
... ... @@ -1615,7 +1615,7 @@
1615 1615  [[image:1653356991268-289.png]]
1616 1616  
1617 1617  
1618 -=== 3.6.2 Digital Input Ports: DI1/DI2 ===
1512 +=== 3.6.2 Digital Input Ports: DI1/DI2 ( For LT-22222-L) ===
1619 1619  
1620 1620  
1621 1621  (((
... ... @@ -1745,7 +1745,7 @@
1745 1745  [[image:image-20240219115718-1.png]]
1746 1746  
1747 1747  
1748 -=== 3.6.3 Digital Output Ports: DO1/DO2 ===
1642 +=== 3.6.3 Digital Output Ports: DO1/DO2 /DO3 ===
1749 1749  
1750 1750  
1751 1751  (% style="color:blue" %)**NPN output**(%%): GND or Float. The maximum voltage that can be applied to the output pin is 36V.
... ... @@ -1818,11 +1818,10 @@
1818 1818  
1819 1819  == 3.7 LEDs Indicators ==
1820 1820  
1821 -The table below lists the behavior of LED indicators for each port function.
1822 1822  
1823 1823  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1824 1824  |(% style="background-color:#4f81bd; color:white; width:50px" %)**LEDs**|(% style="background-color:#4f81bd; color:white; width:460px" %)**Feature**
1825 -|**PWR**|Always on when there is power
1718 +|**PWR**|Always on if there is power
1826 1826  |**TX**|(((
1827 1827  (((
1828 1828  Device boot: TX blinks 5 times.
... ... @@ -1829,7 +1829,7 @@
1829 1829  )))
1830 1830  
1831 1831  (((
1832 -Successful network join: TX remains ON for 5 seconds.
1725 +Successful join network: TX ON for 5 seconds.
1833 1833  )))
1834 1834  
1835 1835  (((
... ... @@ -1836,7 +1836,7 @@
1836 1836  Transmit a LoRa packet: TX blinks once
1837 1837  )))
1838 1838  )))
1839 -|**RX**|RX blinks once when a packet is received.
1732 +|**RX**|RX blinks once when receiving a packet.
1840 1840  |**DO1**|For LT-22222-L: ON when DO1 is low, OFF when DO1 is high
1841 1841  |**DO2**|For LT-22222-L: ON when DO2 is low, OFF when DO2 is high
1842 1842  |**DI1**|(((
... ... @@ -1856,10 +1856,9 @@
1856 1856  
1857 1857  (((
1858 1858  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.
1859 -
1860 -[[image:usb-ttl-programming.png]]
1861 1861  )))
1862 1862  
1754 +[[image:1653358238933-385.png]]
1863 1863  
1864 1864  
1865 1865  (((
... ... @@ -1876,21 +1876,21 @@
1876 1876  )))
1877 1877  
1878 1878  (((
1879 -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.
1880 1880  
1881 -* **##AT##+<CMD>?** : Help on <CMD>
1882 -* **##AT##+<CMD>** : Run <CMD>
1883 -* **##AT##+<CMD>=<value>** : Set the value
1884 -* **##AT##+<CMD>=?** : Get the value
1885 -* ##**ATZ**##: Trigger a reset of the MCU
1773 +* AT+<CMD>? : Help on <CMD>
1774 +* AT+<CMD> : Run <CMD>
1775 +* AT+<CMD>=<value> : Set the value
1776 +* AT+<CMD>=? : Get the value
1777 +* ATZ: Trigger a reset of the MCU
1886 1886  * ##**AT+FDR**##: Reset Parameters to factory default, reserve keys 
1887 1887  * **##AT+DEUI##**: Get or set the Device EUI (DevEUI)
1888 1888  * **##AT+DADDR##**: Get or set the Device Address (DevAddr)
1889 1889  * **##AT+APPKEY##**: Get or set the Application Key (AppKey)
1890 -* ##**AT+NWKSKEY**##: Get or set the Network Session Key (NwkSKey)
1891 -* **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
1892 -* **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
1893 -* **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
1782 +* AT+NWKSKEY: Get or set the Network Session Key (NwkSKey)
1783 +* AT+APPSKEY: Get or set the Application Session Key (AppSKey)
1784 +* AT+APPEUI: Get or set the Application EUI (AppEUI)
1785 +* AT+ADR: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
1894 1894  * AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
1895 1895  * AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
1896 1896  * AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
... ... @@ -1935,28 +1935,28 @@
1935 1935  
1936 1936  
1937 1937  (((
1938 -(% 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:**
1939 1939  )))
1940 1940  )))
1941 1941  
1942 1942  (((
1943 -(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**##
1835 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**##
1944 1944  )))
1945 1945  
1946 1946  (((
1947 -(% 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**##
1948 1948  )))
1949 1949  
1950 1950  (((
1951 -(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**##
1843 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**##
1952 1952  )))
1953 1953  
1954 1954  (((
1955 -(% style="background-color:#dcdcdc" %)##**AT+NJM=0 ~/~/Set to ABP mode**##
1847 +(% style="background-color:#dcdcdc" %)##**AT+NJM=0 ~/~/set to ABP mode**##
1956 1956  )))
1957 1957  
1958 1958  (((
1959 -(% style="background-color:#dcdcdc" %)##**ATZ ~/~/Reset MCU**##
1851 +(% style="background-color:#dcdcdc" %)##**ATZ ~/~/reset MCU**##
1960 1960  )))
1961 1961  
1962 1962  
... ... @@ -1979,20 +1979,20 @@
1979 1979  
1980 1980  
1981 1981  (((
1982 -(% style="background-color:#dcdcdc" %)**123456**(%%)  ~/~/ Enter password to enable AT commands access
1874 +(% style="background-color:#dcdcdc" %)**123456**(%%)  ~/~/ Enter Password to have AT access.
1983 1983  )))
1984 1984  )))
1985 1985  
1986 1986  (((
1987 -(% 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
1988 1988  )))
1989 1989  
1990 1990  (((
1991 -(% style="background-color:#dcdcdc" %)** 123456**(%%)  ~/~/ Enter password to enable AT commands access
1883 +(% style="background-color:#dcdcdc" %)** 123456**(%%)  ~/~/ Enter Password to have AT access.
1992 1992  )))
1993 1993  
1994 1994  (((
1995 -(% 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
1996 1996  )))
1997 1997  
1998 1998  (((
... ... @@ -2012,19 +2012,19 @@
2012 2012  )))
2013 2013  
2014 2014  (((
2015 -(% 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
2016 2016  )))
2017 2017  
2018 2018  (((
2019 -(% 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)
2020 2020  )))
2021 2021  
2022 2022  (((
2023 -(% 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
2024 2024  )))
2025 2025  
2026 2026  (((
2027 -(% 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.
2028 2028  )))
2029 2029  
2030 2030  (((
... ... @@ -2038,14 +2038,14 @@
2038 2038  )))
2039 2039  
2040 2040  (((
2041 -**~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.**
2042 2042  
2043 -**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.**
2044 2044  
2045 -**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?
2046 2046  dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.**
2047 2047  
2048 -**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.**
2049 2049  )))
2050 2050  
2051 2051  (((
... ... @@ -2057,7 +2057,7 @@
2057 2057  
2058 2058  
2059 2059  (((
2060 -(% style="color:blue" %)**If the sensor has JOINED:**
1952 +(% style="color:blue" %)**If sensor JOINED:**
2061 2061  
2062 2062  (% style="background-color:#dcdcdc" %)**AT+CLASS=A**
2063 2063  
... ... @@ -2067,20 +2067,22 @@
2067 2067  
2068 2068  = 5. Case Study =
2069 2069  
2070 -== 5.1 Counting how many objects pass through the flow line ==
1962 +== 5.1 Counting how many objects pass through the flow Line ==
2071 2071  
2072 -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]]?
2073 2073  
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]]?
2074 2074  
1967 +
2075 2075  = 6. FAQ =
2076 2076  
2077 2077  This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
2078 2078  
2079 -
2080 2080  == 6.1 How to update the firmware? ==
2081 2081  
2082 -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.
2083 2083  
1976 +Updating your LT-22222-L with the latest firmware version helps to:
1977 +
2084 2084  * Support new features
2085 2085  * Fix bugs
2086 2086  * Change LoRaWAN frequency bands
... ... @@ -2098,8 +2098,8 @@
2098 2098  
2099 2099  Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2100 2100  
2101 -[[image:usb-ttl-programming.png]]
2102 2102  
1996 +[[image:1653359603330-121.png]]
2103 2103  
2104 2104  
2105 2105  Start the STM32 Flash Loader and choose the correct COM port to update.
... ... @@ -2123,7 +2123,7 @@
2123 2123  [[image:image-20220524104033-15.png]]
2124 2124  
2125 2125  
2126 -(% 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:
2127 2127  
2128 2128  [[image:1653360054704-518.png||height="186" width="745"]]
2129 2129  
... ... @@ -2131,6 +2131,8 @@
2131 2131  (((
2132 2132  (((
2133 2133  == 6.2 How to change the LoRaWAN frequency band/region? ==
2028 +
2029 +
2134 2134  )))
2135 2135  )))
2136 2136  
... ... @@ -2141,18 +2141,20 @@
2141 2141  (((
2142 2142  
2143 2143  
2144 -== 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 +
2145 2145  )))
2146 2146  
2147 2147  (((
2148 2148  (((
2149 -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.
2150 2150  )))
2151 2151  )))
2152 2152  
2153 2153  (((
2154 2154  (((
2155 -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.
2156 2156  
2157 2157  
2158 2158  )))
... ... @@ -2159,55 +2159,52 @@
2159 2159  )))
2160 2160  
2161 2161  (((
2162 -(% 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.
2163 2163  
2164 -[[image:lt-22222-l-abp.png||height="686" width="1000"]]
2062 +
2165 2165  )))
2166 2166  
2167 2167  (((
2066 +[[image:1653360231087-571.png||height="401" width="727"]]
2067 +
2168 2168  
2169 2169  )))
2170 2170  
2171 -{{warning}}
2172 -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.
2173 -{{/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 +)))
2174 2174  
2175 2175  
2076 +
2176 2176  (((
2177 -(% 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:
2178 2178  
2179 2179  
2180 2180  )))
2181 2181  
2182 2182  (((
2183 -(% style="background-color:#dcdcdc" %)**123456** (%%) : Enter the password to enable AT access.
2084 +(% style="background-color:#dcdcdc" %)**123456** (%%) :  Enter Password to have AT access.
2184 2184  
2185 -(% 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
2186 2186  
2187 -(% style="background-color:#dcdcdc" %)**AT+NJM=0** (%%) : Set to ABP mode.
2088 +(% style="background-color:#dcdcdc" %)**AT+NJM=0** (%%) :  Set to ABP mode
2188 2188  
2189 -(% 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
2190 2190  
2191 -(% 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)
2192 2192  
2193 -(% 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
2194 2194  
2195 -(% 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
2196 2196  
2197 -(% 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
2198 2198  
2199 -(% 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)
2200 -
2201 -(% 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)
2202 -
2203 -(% 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)
2204 -
2205 -(% style="background-color:#dcdcdc" %)**ATZ**        (%%) : Reset MCU.
2100 +(% style="background-color:#dcdcdc" %)**ATZ**        (%%) :  Reset MCU
2206 2206  )))
2207 2207  
2208 2208  
2209 2209  (((
2210 -(% 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:
2211 2211  )))
2212 2212  
2213 2213  [[image:1653360498588-932.png||height="485" width="726"]]
... ... @@ -2215,25 +2215,27 @@
2215 2215  
2216 2216  == 6.4 How to change the uplink interval? ==
2217 2217  
2113 +
2218 2218  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/]]
2219 2219  
2220 2220  
2221 2221  == 6.5 Can I see the counting event in the serial output? ==
2222 2222  
2119 +
2223 2223  (((
2224 -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.
2225 2225  
2226 2226  
2227 2227  == 6.6 Can I use point-to-point communication with LT-22222-L? ==
2228 2228  
2229 -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]].
2230 2230  
2231 -
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]].
2232 2232  )))
2233 2233  
2234 2234  (((
2235 2235  == 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
2236 2236  
2133 +
2237 2237  * If the device is not properly shut down and is directly powered off.
2238 2238  * It will default to a power-off state.
2239 2239  * In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
... ... @@ -2241,6 +2241,7 @@
2241 2241  
2242 2242  == 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
2243 2243  
2141 +
2244 2244  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:
2245 2245  
2246 2246  
... ... @@ -2249,24 +2249,24 @@
2249 2249  
2250 2250  == 6.9 Can the LT-22222-L save the RO state? ==
2251 2251  
2252 -To enable this feature, the firmware version must be 1.6.0 or higher.
2253 2253  
2151 +The firmware version must be at least 1.6.0.
2254 2254  
2153 +
2255 2255  == 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
2256 2256  
2156 +
2257 2257  It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
2258 2258  
2259 2259  
2260 2260  = 7. Troubleshooting =
2261 -
2262 -This section provides some known troubleshooting tips.
2263 -
2264 -
2265 2265  )))
2266 2266  
2267 2267  (((
2268 2268  (((
2269 2269  == 7.1 Downlink isn't working. How can I solve this? ==
2166 +
2167 +
2270 2270  )))
2271 2271  )))
2272 2272  
... ... @@ -2278,6 +2278,8 @@
2278 2278  
2279 2279  
2280 2280  == 7.2 Having trouble uploading an image? ==
2179 +
2180 +
2281 2281  )))
2282 2282  
2283 2283  (((
... ... @@ -2288,6 +2288,8 @@
2288 2288  
2289 2289  
2290 2290  == 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
2191 +
2192 +
2291 2291  )))
2292 2292  
2293 2293  (((
... ... @@ -2295,8 +2295,9 @@
2295 2295  )))
2296 2296  
2297 2297  
2298 -== 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? ==
2299 2299  
2202 +
2300 2300  The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
2301 2301  Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2302 2302  
... ... @@ -2303,6 +2303,7 @@
2303 2303  
2304 2304  = 8. Ordering information =
2305 2305  
2209 +
2306 2306  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
2307 2307  
2308 2308  (% style="color:#4f81bd" %)**XXX:**
... ... @@ -2317,14 +2317,15 @@
2317 2317  * (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865
2318 2318  * (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779
2319 2319  
2320 -= 9. Package information =
2224 += 9. Packing information =
2321 2321  
2226 +
2322 2322  **Package includes**:
2323 2323  
2324 -* 1 x LT-22222-L I/O Controller
2325 -* 1 x LoRa antenna matched to the frequency of the LT-22222-L
2326 -* 1 x bracket for DIN rail mounting
2327 -* 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
2328 2328  
2329 2329  **Dimension and weight**:
2330 2330  
... ... @@ -2335,6 +2335,7 @@
2335 2335  
2336 2336  = 10. Support =
2337 2337  
2243 +
2338 2338  * (((
2339 2339  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.
2340 2340  )))
... ... @@ -2346,6 +2346,7 @@
2346 2346  
2347 2347  = 11. Reference​​​​​ =
2348 2348  
2255 +
2349 2349  * 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]]
2350 2350  * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]]
2351 2351  * [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]
lt-22222-l-abp.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -321.4 KB
Content
thingseye-json.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -554.8 KB
Content
usb-ttl-programming.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -462.9 KB
Content

Applications

Navigation

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