Last modified by Saxer Lin on 2025/04/15 17:24
<
From version < 191.1 >
edited by Dilisi S
on 2024/11/14 03:08
To version < 175.1 >
edited by Dilisi S
on 2024/11/08 06:36
>
Change comment: Uploaded new attachment "thingseye.io_integrationsCenter_integrations-2.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
... ... @@ -33,6 +33,8 @@
33 33  With the LT-22222-L I/O Controller, users can transmit data over ultra-long distances with low power consumption using LoRa, a spread-spectrum modulation technique derived from chirp spread spectrum (CSS) technology that operates on license-free ISM bands.
34 34  )))
35 35  
36 +> The LT Series I/O Controllers are designed for easy, low-cost installation on LoRaWAN networks.
37 +
36 36  (((
37 37  You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways:
38 38  
... ... @@ -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}}
45 +> 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,24 +58,24 @@
58 58  * STM32L072xxxx MCU
59 59  * SX1276/78 Wireless Chip 
60 60  * Power Consumption:
61 -** Idle: 4mA@12V
62 -** 20dB Transmit: 34mA@12V
61 +** Idle: 4mA@12v
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)
67 +* 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)
71 -* 2 x 0~~30V Analog Input (res:0.01V)
71 +* 2 x 0~~30V Analog Input (res:0.01v)
72 72  * Power Input 7~~ 24V DC. 
73 73  
74 74  (% style="color:#037691" %)**LoRa Spec:**
75 75  
76 76  * Frequency Range:
77 -** Band 1 (HF): 862 ~~ 1020 MHz
78 -** Band 2 (LF): 410 ~~ 528 MHz
77 +** Band 1 (HF): 862 ~~ 1020 Mhz
78 +** 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
97 +* 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,28 +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
107 +* Smart Buildings & Home Automation
108 +* Logistics and Supply Chain Management
109 +* Smart Metering
110 +* Smart Agriculture
111 +* Smart Cities
112 +* Smart Factory
113 113  
114 +== 1.5 Hardware Variants ==
114 114  
115 -= 2. Assembling the device =
116 116  
117 -== 2.1 Connecting the antenna ==
117 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %)
118 +|(% 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**
119 +|(% style="width:103px" %)**LT22222-L**|(% style="width:131px" %)(((
120 +(% style="text-align:center" %)
121 +[[image:image-20230424115112-1.png||height="106" width="58"]]
122 +)))|(% style="width:334px" %)(((
123 +* 2 x Digital Input (Bi-direction)
124 +* 2 x Digital Output
125 +* 2 x Relay Output (5A@250VAC / 30VDC)
126 +* 2 x 0~~20mA Analog Input (res:0.01mA)
127 +* 2 x 0~~30V Analog Input (res:0.01v)
128 +* 1 x Counting Port
129 +)))
118 118  
119 -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.
131 += 2. Assembling the Device =
120 120  
121 -{{warning}}
122 -Warning! Do not power on the device without connecting the antenna.
123 -{{/warning}}
133 +== 2.1 What is included in the package? ==
124 124  
125 -== 2.2 Terminals ==
135 +The package includes the following items:
126 126  
127 -The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 terminals and the lower screw terminal block has 10 terminals.
137 +* 1 x LT-22222-L I/O Controller
138 +* 1 x LoRaWAN antenna matched to the frequency of the LT-22222-L
139 +* 1 x bracket for wall mounting
140 +* 1 x programming cable
128 128  
142 +Attach the LoRaWAN antenna to the antenna connector, ANT,** **located on the top right side of the device, next to the upper terminal block. Secure the antenna by tightening it clockwise.
143 +
144 +== 2.2 Terminals ==
145 +
129 129  Upper screw terminal block (from left to right):
130 130  
131 131  (% style="width:634px" %)
... ... @@ -152,30 +152,28 @@
152 152  |(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
153 153  |(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
154 154  
155 -== 2.3 Powering the device ==
172 +== 2.3 Powering the LT-22222-L ==
156 156  
157 -The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s positive wire to the VIN and the negative wire to the GND screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered.
174 +The LT-22222-L I/O Controller can be powered by a 7–24V DC power source. Connect the power supply’s positive wire to the VIN and the negative wire to the GND screw terminals. The power indicator (PWR) LED will turn on when the device is properly powered.
158 158  
159 -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.
160 160  
161 -{{warning}}
162 -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.
163 -{{/warning}}
164 -
165 -
166 166  [[image:1653297104069-180.png]]
167 167  
168 168  
169 -= 3. Registering with a LoRaWAN Network Server =
180 += 3. Operation Mode =
170 170  
182 +== 3.1 How does it work? ==
183 +
171 171  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.
172 172  
173 -After powering on, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** the LoRaWAN network. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LED** will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status.
186 +For LT-22222-L, the LED will show the Join status: After powering on, the TX LED will fast-blink 5 times which means the LT-22222-L will enter the working mode and start to JOIN the LoRaWAN network. The TX LED will be on for 5 seconds after joining the network. When there is a message from the server, the RX LED will be on for 1 second. 
174 174  
175 175  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.
176 176  
177 -The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
190 +== 3.2 Registering with a LoRaWAN network server ==
178 178  
192 +The diagram below shows how the LT-22222-L connects to a typical LoRaWAN network.
193 +
179 179  [[image:image-20220523172350-1.png||height="266" width="864"]]
180 180  
181 181  === 3.2.1 Prerequisites ===
... ... @@ -188,101 +188,64 @@
188 188  
189 189  === 3.2.2 The Things Stack Sandbox (TTSS) ===
190 190  
191 -The Things Stack Sandbox was formally called The Things Stack Community Edition.
192 -
193 193  * Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account.
194 -* Create an application with The Things Stack if you do not have one yet.
195 -* Go to your application page and click on the **End devices** in the left menu.
196 -* On the End devices page, click on **+ Register end device**. Two registration options are available:
207 +* Create an application if you do not have one yet.
208 +* Register LT-22222-L with that application. Two registration options are available:
197 197  
198 -==== 3.2.2.1 Using the LoRaWAN Device Repository ====
210 +==== Using the LoRaWAN Device Repository: ====
199 199  
212 +* Go to your application and click on the **Register end device** button.
200 200  * On the **Register end device** page:
201 -** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
202 -** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists.
203 -*** **End device brand**: Dragino Technology Co., Limited
204 -*** **Model**: LT22222-L I/O Controller
205 -*** **Hardware ver**: Unknown
206 -*** **Firmware ver**: 1.6.0
207 -*** **Profile (Region)**: Select the region that matches your device.
208 -** 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.
209 209  
210 210  [[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
211 211  
212 -
213 -* Register end device page continued...
214 -** 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'.
215 -** In the **DevEUI** field, enter the **DevEUI**.
216 -** In the **AppKey** field, enter the **AppKey.**
217 -** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
220 +*
221 +** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
222 +** Enter the **DevEUI** in the **DevEUI** field.
223 +** Enter the **AppKey** in the **AppKey** field.
224 +** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
218 218  ** Under **After registration**, select the **View registered end device** option.
219 219  
220 220  [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
221 221  
222 -==== ====
229 +==== Entering device information manually: ====
223 223  
224 -==== 3.2.2.2 Adding device manually ====
225 -
226 226  * On the **Register end device** page:
227 -** Select the option **Enter end device specifies manually** under **Input method**.
228 -** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
229 -** Select the **LoRaWAN version** as **LoRaWAN Specification 1.0.3**
230 -** Select the **Regional Parameters version** as** RP001 Regional Parameters 1.0.3 revision A**
231 -** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the hidden section.
232 -** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
233 -** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
232 +** Select the **Enter end device specifies manually** option as the input method.
233 +** Select the **Frequency plan** that matches your device.
234 +** Select the **LoRaWAN version**.
235 +** Select the **Regional Parameters version**.
236 +** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the section.
237 +** Select **Over the air activation (OTAA)** option under the **Activation mode**
238 +** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities**.
234 234  
235 235  [[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
236 236  
237 237  
238 -* Register end device page continued...
239 -** 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'
240 -** In the **DevEUI** field, enter the **DevEUI**.
241 -** In the **AppKey** field, enter the **AppKey**.
242 -** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
243 -** Under **After registration**, select the **View registered end device** option.
244 -** Click the **Register end device** button.
243 +* Enter **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
244 +* Enter **DevEUI** in the **DevEUI** field.
245 +* Enter **AppKey** in the **AppKey** field.
246 +* In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
247 +* Under **After registration**, select the **View registered end device** option.
245 245  
246 246  [[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
247 247  
248 248  
249 -You will be navigated to the **Device overview** page.
252 +==== Joining ====
250 250  
254 +Click on **Live Data** in the left navigation. Then, power on the device, and it will join The Things Stack Sandbox. You can see the join request, join accept, followed by uplink messages form the device showing in the Live Data panel.
251 251  
252 -[[image:lt-22222-device-overview.png||height="625" width="1000"]]
256 +[[image:1653298044601-602.png||height="405" width="709"]]
253 253  
254 254  
255 -==== 3.2.2.3 Joining ====
259 +== 3.3 Work Modes and their Uplink Payload formats ==
256 256  
257 -On the Device overview page, click on **Live data** tab. The Live data panel for your device will display.
258 258  
259 -Now power on your LT-22222-L. It will begin joining The Things Stack. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server. Once successfully joined, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**).
262 +The LT-22222-L has 5 **work modes**. It also has an interrupt/trigger mode for different types of applications that can be used together with any working mode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands.
260 260  
261 -
262 -[[image:lt-22222-join-network.png||height="625" width="1000"]]
263 -
264 -
265 -By default, you will receive an uplink data message from the device every 10 minutes.
266 -
267 -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.
268 -
269 -[[image:lt-22222-ul-payload-decoded.png]]
270 -
271 -
272 -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.
273 -
274 -{{info}}
275 -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.
276 -{{/info}}
277 -
278 -[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
279 -
280 -
281 -== 3.3 Work Modes and Uplink Payload formats ==
282 -
283 -
284 -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.
285 -
286 286  * (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO
287 287  
288 288  * (% style="color:blue" %)**MOD2**(%%): Double DI Counting + DO + RO
... ... @@ -295,19 +295,11 @@
295 295  
296 296  * (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5
297 297  
298 -The uplink messages are sent over LoRaWAN FPort 2. By default, an uplink message is sent every 10 minutes.
299 -
300 300  === 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
301 301  
302 302  (((
303 -This is the default mode.
279 +The uplink payload is 11 bytes long. Uplink messages are sent over LoRaWAN FPort 2. By default, one uplink is sent every 10 minutes. (% style="display:none" wfd-invisible="true" %)
304 304  
305 -The uplink payload is 11 bytes long.
306 -
307 -(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
308 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
309 -It starts counting again when it reaches the maximum value.**(% style="display:none" wfd-invisible="true" %)
310 -
311 311  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
312 312  |(% 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**
313 313  |Value|(((
... ... @@ -354,13 +354,13 @@
354 354  
355 355  * [1] The RO1 relay channel is CLOSED, and the RO1 LED is ON.
356 356  * [0] The RO2 relay channel is OPEN, and the RO2 LED is OFF.
357 -* **[1] DI3 - not used for LT-22222-L.**
327 +* [1] DI3 - not used for LT-22222-L.
358 358  * [0] DI2 channel input is LOW, and the DI2 LED is OFF.
359 359  * [1] DI1 channel input state:
360 360  ** DI1 is FLOATING when no sensor is connected between DI1+ and DI1-.
361 361  ** DI1 is HIGH when a sensor is connected between DI1- and DI1+ and the sensor is ACTIVE.
362 362  ** DI1 LED is ON in both cases.
363 -* **[0] DO3 - not used for LT-22222-L.**
333 +* [0] DO3 - not used for LT-22222-L.
364 364  * [1] DO2 channel output is LOW, and the DO2 LED is ON.
365 365  * [0] DO1 channel output state:
366 366  ** DO1 is FLOATING when there is no load between DO1 and V+.
... ... @@ -377,10 +377,6 @@
377 377  (((
378 378  The uplink payload is 11 bytes long.
379 379  
380 -(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
381 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
382 -It starts counting again when it reaches the maximum value.**
383 -
384 384  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
385 385  |(% 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**
386 386  |Value|COUNT1|COUNT2 |DIDORO*|(((
... ... @@ -389,7 +389,7 @@
389 389  )))
390 390  
391 391  (((
392 -(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, FIRST, Reserve, Reserve, DO3, DO2 and DO1, and its size is 1 byte long as shown below.
358 +(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, DO3, DO2 and DO1, and its size is 1 byte long as shown below.
393 393  
394 394  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
395 395  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
... ... @@ -445,9 +445,6 @@
445 445  
446 446  === 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI ===
447 447  
448 -(% style="color:red" %)**Note: The maximum count depends on the bytes it is.
449 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
450 -It starts counting again when it reaches the maximum value.**
451 451  
452 452  **LT22222-L**: In this mode, the DI1 is used as a counting pin.
453 453  
... ... @@ -498,11 +498,7 @@
498 498  
499 499  === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting ===
500 500  
501 -(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
502 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
503 -It starts counting again when it reaches the maximum value.**
504 504  
505 -
506 506  (((
507 507  **LT22222-L**: In this mode, the DI1 is used as a counting pin.
508 508  )))
... ... @@ -555,23 +555,19 @@
555 555  (((
556 556  **In addition to that, below are the commands for AVI1 Counting:**
557 557  
558 -(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI Count to 60)**
517 +(% style="color:blue" %)**AT+SETCNT=3,60**(%%)**  (Sets AVI Count to 60)**
559 559  
560 -(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
519 +(% style="color:blue" %)**AT+VOLMAX=20000**(%%)**  (If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
561 561  
562 -(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
521 +(% style="color:blue" %)**AT+VOLMAX=20000,0**(%%)**  (If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
563 563  
564 -(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
523 +(% style="color:blue" %)**AT+VOLMAX=20000,1**(%%)**  (If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
565 565  )))
566 566  
567 567  
568 568  === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI ===
569 569  
570 -(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
571 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
572 -It starts counting again when it reaches the maximum value.**
573 573  
574 -
575 575  **LT22222-L**: In this mode, the DI1 is used as a counting pin.
576 576  
577 577  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
... ... @@ -629,17 +629,15 @@
629 629  
630 630  For example, if you configured the following commands:
631 631  
632 -* **AT+MOD=1 ** **~-~->**  The default work mode
587 +* **AT+MOD=1 ** **~-~->**  The normal working mode
633 633  * **AT+ADDMOD6=1**   **~-~->**  Enable trigger mode
634 634  
635 635  The LT-22222-L will continuously monitor AV1, AV2, AC1, and AC2 every 5 seconds. LT will send uplink packets in two cases:
636 636  
637 637  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.
638 -1. (((
639 -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 -)))
593 +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.**
641 641  
642 -(% style="color:#037691" %)**AT Commands to set Trigger Condition**:
595 +(% style="color:#037691" %)**AT Command to set Trigger Condition**:
643 643  
644 644  (% style="color:#4f81bd" %)**Trigger based on voltage**:
645 645  
... ... @@ -811,68 +811,50 @@
811 811  )))
812 812  
813 813  
814 -== 3.4 ​Configure LT-22222-L via AT Commands or Downlinks ==
767 +== 3.4 ​Configure LT via AT Commands or Downlinks ==
815 815  
769 +
816 816  (((
817 -You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks.
771 +User can configure LT I/O Controller via AT Commands or LoRaWAN Downlinks.
818 818  )))
819 819  
820 820  (((
821 821  (((
822 -There are two tytes of commands:
776 +There are two kinds of Commands:
823 823  )))
824 824  )))
825 825  
826 -* (% style="color:blue" %)**Common commands**(%%):
780 +* (% 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]]
827 827  
828 -* (% style="color:blue" %)**Sensor-related commands**(%%):
782 +* (% style="color:blue" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L.  User can see these commands below:
829 829  
830 -=== 3.4.1 Common commands ===
784 +=== 3.4.1 Common Commands ===
831 831  
832 832  (((
833 -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.
787 +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]].
834 834  )))
835 835  
836 -=== 3.4.2 Sensor-related commands ===
837 837  
838 -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.
791 +=== 3.4.2 Sensor related commands ===
839 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**
797 +* (% 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
799 +(% style="color:blue" %)**AT+TDC=N**
852 852  
853 -Sets the uplink interval to 30,000 milliseconds (30 seconds)
854 -)))
801 +where N is the time in milliseconds.
855 855  
856 -(% style="color:#037691" %)**Downlink payload**
803 +**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**
806 +* (% style="color:#037691" %)**Downlink payload (prefix 0x01):**
869 869  
870 -Sets the uplink interval to 30,000 milliseconds (30 seconds)
808 +(% 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  
877 877  ==== 3.4.2.2 Set the Work Mode (AT+MOD) ====
878 878  
... ... @@ -894,8 +894,8 @@
894 894  
895 895  ==== 3.4.2.3 Poll an uplink ====
896 896  
897 -Requests the device to send an uplink.
898 898  
833 +Asks the device to send an uplink.
899 899  
900 900  * (% style="color:#037691" %)**AT command:**(%%) There is no AT Command to poll uplink
901 901  
... ... @@ -909,6 +909,7 @@
909 909  
910 910  ==== 3.4.2.4 Enable/Disable Trigger Mode ====
911 911  
847 +
912 912  Enable or disable the trigger mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
913 913  
914 914  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0**
... ... @@ -926,8 +926,9 @@
926 926  
927 927  ==== 3.4.2.5 Poll trigger settings ====
928 928  
929 -Polls the trigger settings.
930 930  
866 +Polls the trigger settings
867 +
931 931  * (% style="color:#037691" %)**AT Command:**
932 932  
933 933  There is no AT Command for this feature.
... ... @@ -938,10 +938,11 @@
938 938  
939 939  
940 940  
941 -==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as a trigger ====
878 +==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ====
942 942  
943 -Enable or disable DI1/DI2/DI2 as a trigger.
944 944  
881 +Enable or Disable DI1/DI2/DI2 as trigger,
882 +
945 945  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
946 946  
947 947  **Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
... ... @@ -953,10 +953,11 @@
953 953  
954 954  
955 955  
956 -==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ====
894 +==== 3.4.2.7 Trigger1 – Set DI1 or DI3 as trigger ====
957 957  
958 -Sets DI1 or DI3 (for LT-33222-L) as a trigger.
959 959  
897 +Set DI1 or DI3(for LT-33222-L) trigger.
898 +
960 960  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG1=a,b**
961 961  
962 962  (% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
... ... @@ -971,10 +971,12 @@
971 971  (% style="color:blue" %)**0x09 01 aa bb cc    ** (%%) ~/~/ same as AT+TRIG1=aa,0x(bb cc)
972 972  
973 973  
974 -==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
975 975  
976 -Sets DI2 as a trigger.
914 +==== 3.4.2.8 Trigger2 – Set DI2 as trigger ====
977 977  
916 +
917 +Sets DI2 trigger.
918 +
978 978  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b**
979 979  
980 980  (% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
... ... @@ -989,10 +989,12 @@
989 989  (% style="color:blue" %)**0x09 02 aa bb cc   ** (%%)~/~/ same as AT+TRIG2=aa,0x(bb cc)
990 990  
991 991  
992 -==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
993 993  
994 -Sets the current trigger based on the AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
934 +==== 3.4.2.9 Trigger – Set AC (current) as trigger ====
995 995  
936 +
937 +Set current trigger , base on AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
938 +
996 996  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ACLIM**
997 997  
998 998  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 01 )**
... ... @@ -1003,8 +1003,9 @@
1003 1003  
1004 1004  ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
1005 1005  
1006 -Sets the current trigger based on the AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
1007 1007  
950 +Set current trigger , base on AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
951 +
1008 1008  * (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+AVLIM    **(%%)** See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]**
1009 1009  
1010 1010  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 00 )**
... ... @@ -1012,8 +1012,10 @@
1012 1012  (% 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"]]
1013 1013  
1014 1014  
959 +
1015 1015  ==== 3.4.2.11 Trigger – Set minimum interval ====
1016 1016  
962 +
1017 1017  Sets AV and AC trigger minimum interval. Device won't response to the second trigger within this set time after the first trigger.
1018 1018  
1019 1019  * (% 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.
... ... @@ -1030,7 +1030,6 @@
1030 1030  
1031 1031  ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
1032 1032  
1033 -Controls the digital outputs DO1, DO2, and DO3
1034 1034  
1035 1035  * (% style="color:#037691" %)**AT Command**
1036 1036  
... ... @@ -1408,21 +1408,15 @@
1408 1408  
1409 1409  == 3.5 Integrating with ThingsEye.io ==
1410 1410  
1411 -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.
1356 +If you are using one of The Things Stack plans, you can integrate ThingsEye.io with your application. Once integrated, ThingsEye.io works as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
1412 1412  
1413 -=== 3.5.1 Configuring The Things Stack ===
1358 +=== 3.5.1 Configuring MQTT Connection Information with The Things Stack Sandbox ===
1414 1414  
1415 -We use The Things Stack Sandbox in this example:
1360 +* In **The Things Stack Sandbox**, select your application under **Applications**.
1361 +* Select **MQTT** under **Integrations**.
1362 +* In the **Connection information **section, for **Username**, The Things Stack displays an auto-generated username. You can use it or provide a new one.
1363 +* For the **Password**, click the **Generate new API key** button to generate a password. You can see it by clicking on the **eye** button.
1416 1416  
1417 -* In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
1418 -* Select **MQTT** under **Integrations** in the left menu.
1419 -* 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.
1420 -* 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.
1421 -
1422 -{{info}}
1423 -The username and  password (API key) you created here are required in the next section.
1424 -{{/info}}
1425 -
1426 1426  [[image:tts-mqtt-integration.png||height="625" width="1000"]]
1427 1427  
1428 1428  === 3.5.2 Configuring ThingsEye.io ===
... ... @@ -1436,7 +1436,7 @@
1436 1436  
1437 1437  On the **Add integration** window, configure the following:
1438 1438  
1439 -**Basic settings:**
1378 +~1. **Basic settings:**
1440 1440  
1441 1441  * Select **The Things Stack Community** from the **Integration type** list.
1442 1442  * Enter a suitable name for your integration in the **Name **text** **box or keep the default name.
... ... @@ -1449,82 +1449,74 @@
1449 1449  [[image:thingseye-io-step-2.png||height="625" width="1000"]]
1450 1450  
1451 1451  
1452 -**Uplink data converter:**
1391 +2. **Uplink data converter:**
1453 1453  
1454 1454  * Click the **Create new** button if it is not selected by default.
1455 1455  * Enter a suitable name for the uplink data converter in the **Name **text** **box or keep the default name.
1456 1456  * Click the **JavaScript** button.
1457 -* Paste the uplink decoder function into the text area (first, delete the default code). The demo uplink decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Uplink_Converter.js]].
1396 +* Paste the uplink decoder function into the text area (first, delete the default code). The demo decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Uplink_Converter.js]].
1458 1458  * Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
1459 1459  
1460 1460  [[image:thingseye-io-step-3.png||height="625" width="1000"]]
1461 1461  
1401 +3.** Downlink data converter (this is an optional step):**
1462 1462  
1463 -**Downlink data converter (this is an optional step):**
1464 -
1465 1465  * Click the **Create new** button if it is not selected by default.
1466 -* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name.
1404 +* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name
1467 1467  * Click the **JavaScript** button.
1468 -* 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]].
1406 +* Paste the downlink decoder function into the text area (first, delete the default code). The demo decoder function can be found here.
1469 1469  * Click the **Next** button. You will be navigated to the **Connection** tab.
1470 1470  
1471 1471  [[image:thingseye-io-step-4.png||height="625" width="1000"]]
1472 1472  
1411 +4. **Connection:**
1473 1473  
1474 -**Connection:**
1475 -
1476 1476  * Choose **Region** from the **Host type**.
1477 1477  * 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/...).
1478 -* 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).
1479 -* Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
1480 -
1481 -[[image:message-1.png]]
1482 -
1483 -
1415 +* 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).
1416 +* Click the **Check connection** button to test the connection. If the connection is successful, you can see the message saying **Connected**.
1484 1484  * Click the **Add** button.
1485 1485  
1486 1486  [[image:thingseye-io-step-5.png||height="625" width="1000"]]
1487 1487  
1488 1488  
1489 -Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings.
1422 +Your integration is added to the** Integrations** list and it will display on the **Integrations** page. Check whether the status is showing as 'Active'. if not, check your configuration settings again.
1490 1490  
1424 +[[image:thingseye-io-step-6.png||height="625" width="1000"]]
1491 1491  
1492 -[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
1493 1493  
1427 +Viewing integration details:
1494 1494  
1495 -**Viewing integration details**:
1429 +Click on the 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.
1496 1496  
1497 -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.
1431 +[add image here]
1498 1498  
1499 -[[image:integration-details.png||height="686" width="1000"]]
1433 +If you want to edit the settings you have provided, click on the Toggle edit mode button.
1500 1500  
1435 +[add image here]
1501 1501  
1502 -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.
1437 +Once you have done click on the Apply changes button.
1503 1503  
1504 -{{info}}
1505 -See also ThingsEye documentation.
1506 -{{/info}}
1439 +Note: See also ThingsEye documentation.
1507 1507  
1508 -**Viewing events:**
1441 +Click on the Events tab.
1509 1509  
1510 -The **Events **tab displays all the uplink messages from the LT-22222-L.
1443 +- Select Debug from the Event type dropdown.
1511 1511  
1512 -* Select **Debug **from the **Event type** dropdown.
1513 -* Select the** time frame** from the **time window**.
1445 +- Select the time frame from the time window.
1514 1514  
1515 -[[image:thingseye-events.png||height="686" width="1000"]]
1447 +[insert image]
1516 1516  
1449 +- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
1517 1517  
1518 -* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
1451 +[insert image]
1519 1519  
1520 -[[image:thingseye-json.png||width="1000"]]
1521 1521  
1454 +Deleting the integration:
1522 1522  
1523 -**Deleting the integration**:
1456 +If you want to delete this integration, click the Delete integration button.
1524 1524  
1525 -If you want to delete this integration, click the **Delete integratio**n button.
1526 1526  
1527 -
1528 1528  == 3.6 Interface Details ==
1529 1529  
1530 1530  === 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) ===
... ... @@ -1738,11 +1738,10 @@
1738 1738  
1739 1739  == 3.7 LEDs Indicators ==
1740 1740  
1741 -The table below lists the behavior of LED indicators for each port function.
1742 1742  
1743 1743  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1744 1744  |(% style="background-color:#4f81bd; color:white; width:50px" %)**LEDs**|(% style="background-color:#4f81bd; color:white; width:460px" %)**Feature**
1745 -|**PWR**|Always on when there is power
1675 +|**PWR**|Always on if there is power
1746 1746  |**TX**|(((
1747 1747  (((
1748 1748  Device boot: TX blinks 5 times.
... ... @@ -1749,7 +1749,7 @@
1749 1749  )))
1750 1750  
1751 1751  (((
1752 -Successful network join: TX remains ON for 5 seconds.
1682 +Successful join network: TX ON for 5 seconds.
1753 1753  )))
1754 1754  
1755 1755  (((
... ... @@ -1756,7 +1756,7 @@
1756 1756  Transmit a LoRa packet: TX blinks once
1757 1757  )))
1758 1758  )))
1759 -|**RX**|RX blinks once when a packet is received.
1689 +|**RX**|RX blinks once when receiving a packet.
1760 1760  |**DO1**|For LT-22222-L: ON when DO1 is low, OFF when DO1 is high
1761 1761  |**DO2**|For LT-22222-L: ON when DO2 is low, OFF when DO2 is high
1762 1762  |**DI1**|(((
... ... @@ -1768,14 +1768,13 @@
1768 1768  |**RO1**|For LT-22222-L: ON when RO1 is closed, OFF when RO1 is open
1769 1769  |**RO2**|For LT-22222-L: ON when RO2 is closed, OFF when RO2 is open
1770 1770  
1771 -= 4. Using AT Commands =
1701 += 4. Using AT Command =
1772 1772  
1773 -The LT-22222-L supports programming using AT Commands.
1703 +== 4.1 Connecting the LT-22222-L to a computer ==
1774 1774  
1775 -== 4.1 Connecting the LT-22222-L to a PC ==
1776 1776  
1777 1777  (((
1778 -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.
1707 +The LT-22222-L supports programming using AT Commands. You can use a USB-to-TTL adapter along with a 3.5mm Program Cable to connect the LT-22222-L to a computer, as shown below.
1779 1779  )))
1780 1780  
1781 1781  [[image:1653358238933-385.png]]
... ... @@ -1782,7 +1782,7 @@
1782 1782  
1783 1783  
1784 1784  (((
1785 -On the PC, you need to set the (% style="color:#4f81bd" %)**serial tool **(%%)(such as [[PuTTY>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]] or [[SecureCRT>>https://www.vandyke.com/cgi-bin/releases.php?product=securecrt]]) to a baud rate of (% style="color:green" %)**9600**(%%) to access the serial console of LT-22222-L. Access to AT commands is disabled by default, and a password (default: (% style="color:green" %)**123456**)(%%) must be entered to enable AT command access, as shown below:
1714 +On the PC, the user needs to set the (% style="color:#4f81bd" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) to a baud rate of (% style="color:green" %)**9600**(%%) to access to access serial console of LT-22222-L. The AT commands are disabled by default, and a password (default:(% style="color:green" %)**123456**)(%%) must be entered to active them, as shown below:
1786 1786  )))
1787 1787  
1788 1788  [[image:1653358355238-883.png]]
... ... @@ -1790,62 +1790,195 @@
1790 1790  
1791 1791  (((
1792 1792  You can find more details in the [[AT Command Manual>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
1722 +)))
1793 1793  
1794 -== 4.2 LT-22222-L related AT commands ==
1724 +(((
1725 +The following table lists all the AT commands related to the LT-22222-L, except for those used for switching between modes.
1726 +
1727 +AT+<CMD>?        : Help on <CMD>
1795 1795  )))
1796 1796  
1797 1797  (((
1798 -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.
1731 +AT+<CMD>         : Run <CMD>
1732 +)))
1799 1799  
1800 -* AT+<CMD>? : Help on <CMD>
1801 -* AT+<CMD> : Run <CMD>
1802 -* AT+<CMD>=<value> : Set the value
1803 -* AT+<CMD>=? : Get the value
1804 -* ATZ: Trigger a reset of the MCU
1805 -* ##**AT+FDR**##: Reset Parameters to factory default, reserve keys 
1806 -* **##AT+DEUI##**: Get or set the Device EUI (DevEUI)
1807 -* **##AT+DADDR##**: Get or set the Device Address (DevAddr)
1808 -* **##AT+APPKEY##**: Get or set the Application Key (AppKey)
1809 -* AT+NWKSKEY: Get or set the Network Session Key (NwkSKey)
1810 -* AT+APPSKEY: Get or set the Application Session Key (AppSKey)
1811 -* AT+APPEUI: Get or set the Application EUI (AppEUI)
1812 -* AT+ADR: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
1813 -* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
1814 -* AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
1815 -* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
1816 -* AT+PNM: Get or set the public network mode. (0: off, 1: on)
1817 -* AT+RX2FQ: Get or set the Rx2 window frequency
1818 -* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
1819 -* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
1820 -* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
1821 -* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
1822 -* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
1823 -* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
1824 -* AT+NWKID: Get or set the Network ID
1825 -* AT+FCU: Get or set the Frame Counter Uplink (FCntUp)
1826 -* AT+FCD: Get or set the Frame Counter Downlink (FCntDown)
1827 -* AT+CLASS: Get or set the Device Class
1828 -* AT+JOIN: Join network
1829 -* AT+NJS: Get OTAA Join Status
1830 -* AT+SENDB: Send hexadecimal data along with the application port
1831 -* AT+SEND: Send text data along with the application port
1832 -* AT+RECVB: Print last received data in binary format (with hexadecimal values)
1833 -* AT+RECV: Print last received data in raw format
1834 -* AT+VER: Get current image version and Frequency Band
1835 -* AT+CFM: Get or Set the confirmation mode (0-1)
1836 -* AT+CFS: Get confirmation status of the last AT+SEND (0-1)
1837 -* AT+SNR: Get the SNR of the last received packet
1838 -* AT+RSSI: Get the RSSI of the last received packet
1839 -* AT+TDC: Get or set the application data transmission interval in ms
1840 -* AT+PORT: Get or set the application port
1841 -* AT+DISAT: Disable AT commands
1842 -* AT+PWORD: Set password, max 9 digits
1843 -* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode
1844 -* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470
1845 -* AT+CFG: Print all settings
1734 +(((
1735 +AT+<CMD>=<value> : Set the value
1846 1846  )))
1847 1847  
1738 +(((
1739 +AT+<CMD>=?       :  Get the value
1740 +)))
1848 1848  
1742 +(((
1743 +ATZ: Trig a reset of the MCU
1744 +)))
1745 +
1746 +(((
1747 +AT+FDR: Reset Parameters to Factory Default, Keys Reserve 
1748 +)))
1749 +
1750 +(((
1751 +AT+DEUI: Get or Set the Device EUI
1752 +)))
1753 +
1754 +(((
1755 +AT+DADDR: Get or Set the Device Address
1756 +)))
1757 +
1758 +(((
1759 +AT+APPKEY: Get or Set the Application Key
1760 +)))
1761 +
1762 +(((
1763 +AT+NWKSKEY: Get or Set the Network Session Key
1764 +)))
1765 +
1766 +(((
1767 +AT+APPSKEY:  Get or Set the Application Session Key
1768 +)))
1769 +
1770 +(((
1771 +AT+APPEUI:  Get or Set the Application EUI
1772 +)))
1773 +
1774 +(((
1775 +AT+ADR: Get or Set the Adaptive Data Rate setting. (0: off, 1: on)
1776 +)))
1777 +
1778 +(((
1779 +AT+TXP: Get or Set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Spec)
1780 +)))
1781 +
1782 +(((
1783 +AT+DR:  Get or Set the Data Rate. (0-7 corresponding to DR_X)  
1784 +)))
1785 +
1786 +(((
1787 +AT+DCS: Get or Set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
1788 +)))
1789 +
1790 +(((
1791 +AT+PNM: Get or Set the public network mode. (0: off, 1: on)
1792 +)))
1793 +
1794 +(((
1795 +AT+RX2FQ: Get or Set the Rx2 window frequency
1796 +)))
1797 +
1798 +(((
1799 +AT+RX2DR: Get or Set the Rx2 window data rate (0-7 corresponding to DR_X)
1800 +)))
1801 +
1802 +(((
1803 +AT+RX1DL: Get or Set the delay between the end of the Tx and the Rx Window 1 in ms
1804 +)))
1805 +
1806 +(((
1807 +AT+RX2DL: Get or Set the delay between the end of the Tx and the Rx Window 2 in ms
1808 +)))
1809 +
1810 +(((
1811 +AT+JN1DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
1812 +)))
1813 +
1814 +(((
1815 +AT+JN2DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
1816 +)))
1817 +
1818 +(((
1819 +AT+NJM:  Get or Set the Network Join Mode. (0: ABP, 1: OTAA)
1820 +)))
1821 +
1822 +(((
1823 +AT+NWKID: Get or Set the Network ID
1824 +)))
1825 +
1826 +(((
1827 +AT+FCU: Get or Set the Frame Counter Uplink
1828 +)))
1829 +
1830 +(((
1831 +AT+FCD: Get or Set the Frame Counter Downlink
1832 +)))
1833 +
1834 +(((
1835 +AT+CLASS: Get or Set the Device Class
1836 +)))
1837 +
1838 +(((
1839 +AT+JOIN: Join network
1840 +)))
1841 +
1842 +(((
1843 +AT+NJS: Get OTAA Join Status
1844 +)))
1845 +
1846 +(((
1847 +AT+SENDB: Send hexadecimal data along with the application port
1848 +)))
1849 +
1850 +(((
1851 +AT+SEND: Send text data along with the application port
1852 +)))
1853 +
1854 +(((
1855 +AT+RECVB: Print last received data in binary format (with hexadecimal values)
1856 +)))
1857 +
1858 +(((
1859 +AT+RECV: Print last received data in raw format
1860 +)))
1861 +
1862 +(((
1863 +AT+VER:  Get current image version and Frequency Band
1864 +)))
1865 +
1866 +(((
1867 +AT+CFM: Get or Set the confirmation mode (0-1)
1868 +)))
1869 +
1870 +(((
1871 +AT+CFS:  Get confirmation status of the last AT+SEND (0-1)
1872 +)))
1873 +
1874 +(((
1875 +AT+SNR: Get the SNR of the last received packet
1876 +)))
1877 +
1878 +(((
1879 +AT+RSSI: Get the RSSI of the last received packet
1880 +)))
1881 +
1882 +(((
1883 +AT+TDC: Get or set the application data transmission interval in ms
1884 +)))
1885 +
1886 +(((
1887 +AT+PORT: Get or set the application port
1888 +)))
1889 +
1890 +(((
1891 +AT+DISAT: Disable AT commands
1892 +)))
1893 +
1894 +(((
1895 +AT+PWORD: Set password, max 9 digits
1896 +)))
1897 +
1898 +(((
1899 +AT+CHS: Get or Set Frequency (Unit: Hz) for Single Channel Mode
1900 +)))
1901 +
1902 +(((
1903 +AT+CHE: Get or Set eight channels mode, Only for US915, AU915, CN470
1904 +)))
1905 +
1906 +(((
1907 +AT+CFG: Print all settings
1908 +)))
1909 +
1910 +
1849 1849  == 4.2 Common AT Command Sequence ==
1850 1850  
1851 1851  === 4.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
... ... @@ -1854,41 +1854,41 @@
1854 1854  
1855 1855  
1856 1856  (((
1857 -(% style="color:blue" %)**If the device has not joined the network yet:**
1919 +(% style="color:blue" %)**If device has not joined network yet:**
1858 1858  )))
1859 1859  )))
1860 1860  
1861 1861  (((
1862 -(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**##
1924 +(% style="background-color:#dcdcdc" %)**123456**
1863 1863  )))
1864 1864  
1865 1865  (((
1866 -(% style="background-color:#dcdcdc" %)##**AT+FDR ~/~/reset parameters to factory default, reserve keys**##
1928 +(% style="background-color:#dcdcdc" %)**AT+FDR**
1867 1867  )))
1868 1868  
1869 1869  (((
1870 -(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**##
1932 +(% style="background-color:#dcdcdc" %)**123456**
1871 1871  )))
1872 1872  
1873 1873  (((
1874 -(% style="background-color:#dcdcdc" %)##**AT+NJM=0 ~/~/set to ABP mode**##
1936 +(% style="background-color:#dcdcdc" %)**AT+NJM=0**
1875 1875  )))
1876 1876  
1877 1877  (((
1878 -(% style="background-color:#dcdcdc" %)##**ATZ ~/~/reset MCU**##
1940 +(% style="background-color:#dcdcdc" %)**ATZ**
1879 1879  )))
1880 1880  
1881 1881  
1882 1882  (((
1883 -(% style="color:blue" %)**If the device has already joined the network:**
1945 +(% style="color:blue" %)**If device already joined network:**
1884 1884  )))
1885 1885  
1886 1886  (((
1887 -(% style="background-color:#dcdcdc" %)##**AT+NJM=0**##
1949 +(% style="background-color:#dcdcdc" %)**AT+NJM=0**
1888 1888  )))
1889 1889  
1890 1890  (((
1891 -(% style="background-color:#dcdcdc" %)##**ATZ**##
1953 +(% style="background-color:#dcdcdc" %)**ATZ**
1892 1892  )))
1893 1893  
1894 1894  
... ... @@ -1988,48 +1988,35 @@
1988 1988  
1989 1989  == 5.1 Counting how many objects pass through the flow Line ==
1990 1990  
1991 -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]]?
1992 1992  
2054 +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]]?
1993 1993  
2056 +
1994 1994  = 6. FAQ =
1995 1995  
1996 -This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
2059 +== 6.1 How to upgrade the image? ==
1997 1997  
1998 1998  
1999 -== 6.1 How to update the firmware? ==
2062 +The LT-22222-L I/O Controller is shipped with a 3.5mm cable, which is used to upload an image to LT in order to:
2000 2000  
2001 -Dragino frequently releases firmware updates for the LT-22222-L.
2064 +* Support new features.
2065 +* Fix bugs.
2066 +* Change LoRaWAN bands.
2002 2002  
2003 -Updating your LT-22222-L with the latest firmware version helps to:
2068 +Below is the hardware connection setup for uploading an image to the LT:
2004 2004  
2005 -* Support new features
2006 -* Fix bugs
2007 -* Change LoRaWAN frequency bands
2008 -
2009 -You will need the following things before proceeding:
2010 -
2011 -* 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
2012 -* USB to TTL adapter
2013 -* Download and install the [[STM32 Flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]]. (replaced by STM32CubeProgrammer)
2014 -* Download the latest firmware image from [[LT-22222-L firmware image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]]. Check the file name of the firmware to find the correct region.
2015 -
2016 -{{info}}
2017 -As of this writing, the latest firmware version available for the LT-22222-L is v1.6.1.
2018 -{{/info}}
2019 -
2020 -Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2021 -
2022 -
2023 2023  [[image:1653359603330-121.png]]
2024 2024  
2025 2025  
2026 -Start the STM32 Flash Loader and choose the correct COM port to update.
2073 +(((
2074 +(% style="color:#0000ff" %)**Step 1**(%%)**:** Download the F[[lash Loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]].
2075 +(% style="color:#0000ff" %)**Step 2**(%%)**:** Download the [[LT Image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]].
2076 +(% style="color:#0000ff" %)**Step 3**(%%)**:** Open the Flash Loader and choose the correct COM port to update.
2077 +
2027 2027  
2028 2028  (((
2029 -(((
2030 2030  (% style="color:blue" %)**For LT-22222-L**(%%):
2031 -
2032 -Hold down the **PRO** button, then briefly press the **RST** button. The **DO1** LED will change from OFF to ON. When the **DO1** LED is ON, it indicates that the device is in firmware download mode.
2081 +Hold down the PRO button, then momentarily press the RST reset button. The (% style="color:red" %)**DO1 LED**(%%) will change from OFF to ON. When the (% style="color:red" %)**DO1 LED**(%%) is ON, it indicates that the device is in download mode.
2033 2033  )))
2034 2034  
2035 2035  
... ... @@ -2051,7 +2051,9 @@
2051 2051  
2052 2052  (((
2053 2053  (((
2054 -== 6.2 How to change the LoRaWAN frequency band/region? ==
2103 +== 6.2 How to change the LoRa Frequency Bands/Region? ==
2104 +
2105 +
2055 2055  )))
2056 2056  )))
2057 2057  
... ... @@ -2062,7 +2062,9 @@
2062 2062  (((
2063 2063  
2064 2064  
2065 -== 6.3 How to setup LT to work with a Single Channel Gateway, such as LG01/LG02? ==
2116 +== 6.3 How to set up LT to work with a Single Channel Gateway, such as LG01/LG02? ==
2117 +
2118 +
2066 2066  )))
2067 2067  
2068 2068  (((
... ... @@ -2133,137 +2133,156 @@
2133 2133  
2134 2134  == 6.4 How to change the uplink interval? ==
2135 2135  
2189 +
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 -== 6.5 Can I see the counting event in the serial output? ==
2193 +== 6.5 Can I see the counting event in Serial? ==
2140 2140  
2195 +
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.
2197 +User can run AT+DEBUG command to see the counting event in serial. If firmware too old and doesn't support AT+DEBUG. User can update to latest firmware first.
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  
2203 +Yes, please refer [[Point to Point Communication>>doc:Main. Point to Point Communication of LT-22222-L.WebHome]]. this is [[firmware>>https://github.com/dragino/LT-22222-L/releases]].
2204 +
2149 2149  
2150 2150  )))
2151 2151  
2152 2152  (((
2153 -== 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
2209 +== 6.7 Why does the relay output become the default and open relay after the lt22222 is powered off? ==
2154 2154  
2155 -* If the device is not properly shut down and is directly powered off.
2156 -* It will default to a power-off state.
2157 -* In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
2158 -* After a restart, the status before the power failure will be read from flash.
2159 2159  
2160 -== 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
2212 +If the device is not shut down, but directly powered off.
2161 2161  
2162 -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:
2214 +It will default that this is a power-off state.
2163 2163  
2216 +In modes 2 to 5, DO RO status and pulse count are saved in flash.
2164 2164  
2218 +After restart, the status before power failure will be read from flash.
2219 +
2220 +
2221 +== 6.8 Can i set up LT-22222-L as a NC(Normal Close) Relay? ==
2222 +
2223 +
2224 +LT-22222-L built-in relay is NO (Normal Open). User can use an external relay to achieve Normal Close purpose. Diagram as below:
2225 +
2226 +
2165 2165  [[image:image-20221006170630-1.png||height="610" width="945"]]
2166 2166  
2167 2167  
2168 -== 6.9 Can the LT-22222-L save the RO state? ==
2230 +== 6.9 Can LT22222-L save RO state? ==
2169 2169  
2170 -The firmware version must be at least 1.6.0.
2171 2171  
2233 +Firmware version needs to be no less than 1.6.0.
2172 2172  
2173 -== 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
2174 2174  
2175 -It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
2236 +== 6.10 Why does the LT22222 always report 15.585V when measuring AVI? ==
2176 2176  
2177 2177  
2178 -= 7. Troubleshooting =
2239 +It is likely that the GND is not connected during the measurement, or the wire connected to the GND is loose.
2179 2179  
2180 -This section provides some known troubleshooting tips.
2181 2181  
2182 -
2242 += 7. Trouble Shooting =
2183 2183  )))
2184 2184  
2185 2185  (((
2186 2186  (((
2187 -== 7.1 Downlink isn't working. How can I solve this? ==
2247 +== 7.1 Downlink doesn't work, how to solve it? ==
2248 +
2249 +
2188 2188  )))
2189 2189  )))
2190 2190  
2191 2191  (((
2192 -Please refer to this link for debugging instructions: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]]
2254 +Please see this link for how to debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]]
2193 2193  )))
2194 2194  
2195 2195  (((
2196 2196  
2197 2197  
2198 -== 7.2 Having trouble uploading an image? ==
2260 +== 7.2 Have trouble to upload image. ==
2261 +
2262 +
2199 2199  )))
2200 2200  
2201 2201  (((
2202 -Please refer to this link for troubleshooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
2266 +See this link for trouble shooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
2203 2203  )))
2204 2204  
2205 2205  (((
2206 2206  
2207 2207  
2208 -== 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
2272 +== 7.3 Why I can't join TTN in US915 /AU915 bands? ==
2273 +
2274 +
2209 2209  )))
2210 2210  
2211 2211  (((
2212 -It might be related to the channel mapping. [[Please refer to this link for details.>>https://github.com/dragino/LT-22222-L/releases]]
2278 +It might be about the channels mapping. [[Please see this link for detail>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
2213 2213  )))
2214 2214  
2215 2215  
2216 -== 7.4 Why can the LT-22222-L perform Uplink normally, but cannot receive Downlink? ==
2282 +== 7.4 Why can LT22222 perform Uplink normally, but cannot receive Downlink? ==
2217 2217  
2218 -The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
2219 -Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2220 2220  
2285 +The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue state.
2286 +Use this command to bring their counts back together: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2221 2221  
2222 -= 8. Ordering information =
2223 2223  
2289 += 8. Order Info =
2290 +
2291 +
2224 2224  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
2225 2225  
2226 2226  (% style="color:#4f81bd" %)**XXX:**
2227 2227  
2228 -* (% style="color:red" %)**EU433**(%%): LT with frequency bands EU433
2229 -* (% style="color:red" %)**EU868**(%%): LT with frequency bands EU868
2230 -* (% style="color:red" %)**KR920**(%%): LT with frequency bands KR920
2231 -* (% style="color:red" %)**CN470**(%%): LT with frequency bands CN470
2232 -* (% style="color:red" %)**AS923**(%%): LT with frequency bands AS923
2233 -* (% style="color:red" %)**AU915**(%%): LT with frequency bands AU915
2234 -* (% style="color:red" %)**US915**(%%): LT with frequency bands US915
2235 -* (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865
2236 -* (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779
2296 +* (% style="color:red" %)**EU433**(%%):  LT with frequency bands EU433
2297 +* (% style="color:red" %)**EU868**(%%):  LT with frequency bands EU868
2298 +* (% style="color:red" %)**KR920**(%%):  LT with frequency bands KR920
2299 +* (% style="color:red" %)**CN470**(%%):  LT with frequency bands CN470
2300 +* (% style="color:red" %)**AS923**(%%):  LT with frequency bands AS923
2301 +* (% style="color:red" %)**AU915**(%%):  LT with frequency bands AU915
2302 +* (% style="color:red" %)**US915**(%%):  LT with frequency bands US915
2303 +* (% style="color:red" %)**IN865**(%%):  LT with frequency bands IN865
2304 +* (% style="color:red" %)**CN779**(%%):  LT with frequency bands CN779
2237 2237  
2238 -= 9. Packing information =
2306 += 9. Packing Info =
2239 2239  
2240 -**Package includes**:
2241 2241  
2242 -* 1 x LT-22222-L I/O Controller
2243 -* 1 x LoRa antenna matched to the frequency of the LT-22222-L
2244 -* 1 x bracket for DIN rail mounting
2245 -* 1 x 3.5mm programming cable
2309 +**Package Includes**:
2246 2246  
2311 +* LT-22222-L I/O Controller x 1
2312 +* Stick Antenna for LoRa RF part x 1
2313 +* Bracket for controller x1
2314 +* Program cable x 1
2315 +
2247 2247  **Dimension and weight**:
2248 2248  
2249 2249  * Device Size: 13.5 x 7 x 3 cm
2250 -* Device Weight: 105 g
2319 +* Device Weight: 105g
2251 2251  * Package Size / pcs : 14.5 x 8 x 5 cm
2252 -* Weight / pcs : 170 g
2321 +* Weight / pcs : 170g
2253 2253  
2254 2254  = 10. Support =
2255 2255  
2325 +
2256 2256  * (((
2257 -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.
2327 +Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
2258 2258  )))
2259 2259  * (((
2260 -Please provide as much information as possible regarding your inquiry (e.g., product models, a detailed description of the problem, steps to replicate it, etc.) and send an email to [[support@dragino.cc>>mailto:support@dragino.cc]]
2330 +Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[Support@dragino.cc>>mailto:Support@dragino.cc]]
2261 2261  
2332 +
2262 2262  
2263 2263  )))
2264 2264  
2265 2265  = 11. Reference​​​​​ =
2266 2266  
2338 +
2267 2267  * 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]]
2268 2268  * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]]
2269 2269  * [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]
integration-details.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -463.9 KB
Content
lt-22222-l-abp.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -321.4 KB
Content
thingseye-events.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -530.6 KB
Content
thingseye-json.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -554.8 KB
Content
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