<
From version < 179.1 >
edited by Dilisi S
on 2024/11/09 05:29
To version < 177.1 >
edited by Dilisi S
on 2024/11/08 06:48
>
Change comment: NOV 7 edits - part 2

Summary

Details

Page properties
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  
... ... @@ -57,7 +57,7 @@
57 57  * SX1276/78 Wireless Chip 
58 58  * Power Consumption:
59 59  ** Idle: 4mA@12v
60 -** 20dB Transmit: 34mA@12V
62 +** 20dB Transmit: 34mA@12v
61 61  * Operating Temperature: -40 ~~ 85 Degrees, No Dew
62 62  
63 63  (% style="color:#037691" %)**Interface for Model: LT22222-L:**
... ... @@ -66,7 +66,7 @@
66 66  * 2 x Digital Output (NPN output. Max pull-up voltage 36V,450mA)
67 67  * 2 x Relay Output (5A@250VAC / 30VDC)
68 68  * 2 x 0~~20mA Analog Input (res:0.01mA)
69 -* 2 x 0~~30V Analog Input (res:0.01V)
71 +* 2 x 0~~30V Analog Input (res:0.01v)
70 70  * Power Input 7~~ 24V DC. 
71 71  
72 72  (% style="color:#037691" %)**LoRa Spec:**
... ... @@ -134,10 +134,10 @@
134 134  
135 135  * 1 x LT-22222-L I/O Controller
136 136  * 1 x LoRaWAN antenna matched to the frequency of the LT-22222-L
137 -* 1 x bracket for DIN rail mounting
139 +* 1 x bracket for wall mounting
138 138  * 1 x programming cable
139 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.
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.
141 141  
142 142  == 2.2 Terminals ==
143 143  
... ... @@ -169,7 +169,7 @@
169 169  
170 170  == 2.3 Powering the LT-22222-L ==
171 171  
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.
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.
173 173  
174 174  
175 175  [[image:1653297104069-180.png]]
... ... @@ -181,13 +181,13 @@
181 181  
182 182  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.
183 183  
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.
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. 
185 185  
186 186  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.
187 187  
188 188  == 3.2 Registering with a LoRaWAN network server ==
189 189  
190 -The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
192 +The diagram below shows how the LT-22222-L connects to a typical LoRaWAN network.
191 191  
192 192  [[image:image-20220523172350-1.png||height="266" width="864"]]
193 193  
... ... @@ -205,10 +205,8 @@
205 205  * Create an application if you do not have one yet.
206 206  * Register LT-22222-L with that application. Two registration options are available:
207 207  
208 -==== ====
210 +==== Using the LoRaWAN Device Repository: ====
209 209  
210 -==== 3.2.2.1 Using the LoRaWAN Device Repository ====
211 -
212 212  * Go to your application and click on the **Register end device** button.
213 213  * On the **Register end device** page:
214 214  ** Select the option **Select the end device in the LoRaWAN Device Repository**.
... ... @@ -217,8 +217,7 @@
217 217  
218 218  [[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
219 219  
220 -
221 -* Page continued...
220 +*
222 222  ** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
223 223  ** Enter the **DevEUI** in the **DevEUI** field.
224 224  ** Enter the **AppKey** in the **AppKey** field.
... ... @@ -227,10 +227,8 @@
227 227  
228 228  [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
229 229  
230 -==== ====
229 +==== Entering device information manually: ====
231 231  
232 -==== 3.2.2.2 Entering device information manually ====
233 -
234 234  * On the **Register end device** page:
235 235  ** Select the **Enter end device specifies manually** option as the input method.
236 236  ** Select the **Frequency plan** that matches your device.
... ... @@ -243,13 +243,12 @@
243 243  [[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
244 244  
245 245  
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.
251 -** Under **After registration**, select the **View registered end device** option.
252 -** 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.
248 +* Click the **Register end device** button.
253 253  
254 254  [[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
255 255  
... ... @@ -256,24 +256,18 @@
256 256  
257 257  You will be navigated to the **Device overview** page.
258 258  
259 -
260 260  [[image:lt-22222-device-overview.png||height="625" width="1000"]]
261 261  
262 262  
263 -==== 3.2.2.3 Joining ====
258 +==== Joining ====
264 264  
265 -Click on **Live data** in the left navigation. The Live data panel for your application will display.
260 +Click on **Live data** in the left navigation. Then, power on LT-22222-L. It will join The Things Stack LoRaWAN network server. You can see the **join request**, **join accept**, followed by **uplink data messages** form the device showing in the **Live data** panel.
266 266  
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**).
268 -
269 -
270 270  [[image:lt-22222-join-network.png||height="625" width="1000"]]
271 271  
272 272  
273 -By default, you will receive an uplink data message every 10 minutes.
265 +Click on a message with the messge type, **Forward uplink data message**. You can see the  decoded uplink payload as shown below.
274 274  
275 -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.
276 -
277 277  [[image:lt-22222-ul-payload-decoded.png]]
278 278  
279 279  
... ... @@ -285,7 +285,7 @@
285 285  == 3.3 Work Modes and their Uplink Payload formats ==
286 286  
287 287  
288 -The LT-22222-L has 5 **work modes**. It also has an interrupt/trigger mode for different types of applications that can be used together with any work mode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands.
278 +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.
289 289  
290 290  * (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO
291 291  
... ... @@ -299,15 +299,11 @@
299 299  
300 300  * (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5
301 301  
302 -The uplink messages are sent over LoRaWAN FPort 2. By default, an uplink message is sent every 10 minutes.
303 -
304 304  === 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
305 305  
306 306  (((
307 -This is the default mode.
295 +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" %)
308 308  
309 -The uplink payload is 11 bytes long. (% 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.**
343 +* [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.**
349 +* [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+.
... ... @@ -385,7 +385,7 @@
385 385  )))
386 386  
387 387  (((
388 -(% 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.
374 +(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, DO3, DO2 and DO1, and its size is 1 byte long as shown below.
389 389  
390 390  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
391 391  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
... ... @@ -1485,7 +1485,7 @@
1485 1485  
1486 1486  * Click on the **Events **tab.
1487 1487  * Select **Debug **from the **Event type** dropdown.
1488 -* Select the** time frame** from the **time window**.
1474 +* Select the** time frame** from the **time window**.
1489 1489  
1490 1490  [insert image]
1491 1491  
... ... @@ -1754,7 +1754,7 @@
1754 1754  
1755 1755  
1756 1756  (((
1757 -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]] 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. The AT commands are disabled by default, and a password (default:(% style="color:green" %)**123456**)(%%) must be entered to active them, as shown below:
1743 +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:
1758 1758  )))
1759 1759  
1760 1760  [[image:1653358355238-883.png]]
... ... @@ -2099,41 +2099,29 @@
2099 2099  
2100 2100  = 6. FAQ =
2101 2101  
2102 -== 6.1 How to update the firmware? ==
2088 +== 6.1 How to upgrade the image? ==
2103 2103  
2104 2104  
2105 -Dragino frequently releases firmware updates for the LT-22222-L.
2091 +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:
2106 2106  
2107 -Updating your LT-22222-L with the latest firmware version helps to:
2093 +* Support new features.
2094 +* Fix bugs.
2095 +* Change LoRaWAN bands.
2108 2108  
2109 -* Support new features
2110 -* Fix bugs
2111 -* Change LoRaWAN frequency bands
2097 +Below is the hardware connection setup for uploading an image to the LT:
2112 2112  
2113 -You will need the following things before proceeding:
2114 -
2115 -* 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
2116 -* USB to TTL adapter
2117 -* 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)
2118 -* 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.
2119 -
2120 -{{info}}
2121 -As of this writing, the latest firmware version available for the LT-22222-L is v1.6.1.
2122 -{{/info}}
2123 -
2124 -Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2125 -
2126 -
2127 2127  [[image:1653359603330-121.png]]
2128 2128  
2129 2129  
2130 -Start the STM32 Flash Loader and choose the correct COM port to update.
2102 +(((
2103 +(% 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]].
2104 +(% 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]].
2105 +(% style="color:#0000ff" %)**Step 3**(%%)**:** Open the Flash Loader and choose the correct COM port to update.
2106 +
2131 2131  
2132 2132  (((
2133 -(((
2134 2134  (% style="color:blue" %)**For LT-22222-L**(%%):
2135 -
2136 -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.
2110 +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.
2137 2137  )))
2138 2138  
2139 2139  
... ... @@ -2155,7 +2155,7 @@
2155 2155  
2156 2156  (((
2157 2157  (((
2158 -== 6.2 How to change the LoRaWAN frequency band/region? ==
2132 +== 6.2 How to change the LoRa Frequency Bands/Region? ==
2159 2159  
2160 2160  
2161 2161  )))
... ... @@ -2168,7 +2168,7 @@
2168 2168  (((
2169 2169  
2170 2170  
2171 -== 6.3 How to setup LT to work with a Single Channel Gateway, such as LG01/LG02? ==
2145 +== 6.3 How to set up LT to work with a Single Channel Gateway, such as LG01/LG02? ==
2172 2172  
2173 2173  
2174 2174  )))
... ... @@ -2245,56 +2245,61 @@
2245 2245  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/]]
2246 2246  
2247 2247  
2248 -== 6.5 Can I see the counting event in the serial output? ==
2222 +== 6.5 Can I see the counting event in Serial? ==
2249 2249  
2250 2250  
2251 2251  (((
2252 -You can run the AT command AT+DEBUG to view the counting event in the serial output. If the firmware is too old and doesnt support AT+DEBUG, update to the latest firmware first.
2226 +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.
2253 2253  
2254 2254  
2255 2255  == 6.6 Can I use point-to-point communication with LT-22222-L? ==
2256 2256  
2257 2257  
2258 -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 +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]].
2233 +
2234 +
2259 2259  )))
2260 2260  
2261 2261  (((
2262 -== 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
2238 +== 6.7 Why does the relay output become the default and open relay after the lt22222 is powered off? ==
2263 2263  
2264 2264  
2265 -* If the device is not properly shut down and is directly powered off.
2266 -* It will default to a power-off state.
2267 -* In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
2268 -* After a restart, the status before the power failure will be read from flash.
2241 +If the device is not shut down, but directly powered off.
2269 2269  
2243 +It will default that this is a power-off state.
2270 2270  
2271 -== 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
2245 +In modes 2 to 5, DO RO status and pulse count are saved in flash.
2272 2272  
2247 +After restart, the status before power failure will be read from flash.
2273 2273  
2274 -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:
2275 2275  
2250 +== 6.8 Can i set up LT-22222-L as a NC(Normal Close) Relay? ==
2276 2276  
2252 +
2253 +LT-22222-L built-in relay is NO (Normal Open). User can use an external relay to achieve Normal Close purpose. Diagram as below:
2254 +
2255 +
2277 2277  [[image:image-20221006170630-1.png||height="610" width="945"]]
2278 2278  
2279 2279  
2280 -== 6.9 Can the LT-22222-L save the RO state? ==
2259 +== 6.9 Can LT22222-L save RO state? ==
2281 2281  
2282 2282  
2283 -The firmware version must be at least 1.6.0.
2262 +Firmware version needs to be no less than 1.6.0.
2284 2284  
2285 2285  
2286 -== 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
2265 +== 6.10 Why does the LT22222 always report 15.585V when measuring AVI? ==
2287 2287  
2288 2288  
2289 -It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
2268 +It is likely that the GND is not connected during the measurement, or the wire connected to the GND is loose.
2290 2290  
2291 2291  
2292 -= 7. Troubleshooting =
2271 += 7. Trouble Shooting =
2293 2293  )))
2294 2294  
2295 2295  (((
2296 2296  (((
2297 -== 7.1 Downlink isn't working. How can I solve this? ==
2276 +== 7.1 Downlink doesn't work, how to solve it? ==
2298 2298  
2299 2299  
2300 2300  )))
... ... @@ -2301,42 +2301,42 @@
2301 2301  )))
2302 2302  
2303 2303  (((
2304 -Please refer to this link for debugging instructions: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]]
2283 +Please see this link for how to debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]]
2305 2305  )))
2306 2306  
2307 2307  (((
2308 2308  
2309 2309  
2310 -== 7.2 Having trouble uploading an image? ==
2289 +== 7.2 Have trouble to upload image. ==
2311 2311  
2312 2312  
2313 2313  )))
2314 2314  
2315 2315  (((
2316 -Please refer to this link for troubleshooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
2295 +See this link for trouble shooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
2317 2317  )))
2318 2318  
2319 2319  (((
2320 2320  
2321 2321  
2322 -== 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
2301 +== 7.3 Why I can't join TTN in US915 /AU915 bands? ==
2323 2323  
2324 2324  
2325 2325  )))
2326 2326  
2327 2327  (((
2328 -It might be related to the channel mapping. [[Please refer to this link for details.>>https://github.com/dragino/LT-22222-L/releases||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
2307 +It might be about the channels mapping. [[Please see this link for detail>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
2329 2329  )))
2330 2330  
2331 2331  
2332 -== 7.4 Why can the LT-22222-L perform Uplink normally, but cannot receive Downlink? ==
2311 +== 7.4 Why can LT22222 perform Uplink normally, but cannot receive Downlink? ==
2333 2333  
2334 2334  
2335 -The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
2336 -Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2314 +The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue state.
2315 +Use this command to bring their counts back together: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
2337 2337  
2338 2338  
2339 -= 8. Ordering information =
2318 += 8. Order Info =
2340 2340  
2341 2341  
2342 2342  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
... ... @@ -2343,44 +2343,43 @@
2343 2343  
2344 2344  (% style="color:#4f81bd" %)**XXX:**
2345 2345  
2346 -* (% style="color:red" %)**EU433**(%%): LT with frequency bands EU433
2347 -* (% style="color:red" %)**EU868**(%%): LT with frequency bands EU868
2348 -* (% style="color:red" %)**KR920**(%%): LT with frequency bands KR920
2349 -* (% style="color:red" %)**CN470**(%%): LT with frequency bands CN470
2350 -* (% style="color:red" %)**AS923**(%%): LT with frequency bands AS923
2351 -* (% style="color:red" %)**AU915**(%%): LT with frequency bands AU915
2352 -* (% style="color:red" %)**US915**(%%): LT with frequency bands US915
2353 -* (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865
2354 -* (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779
2325 +* (% style="color:red" %)**EU433**(%%):  LT with frequency bands EU433
2326 +* (% style="color:red" %)**EU868**(%%):  LT with frequency bands EU868
2327 +* (% style="color:red" %)**KR920**(%%):  LT with frequency bands KR920
2328 +* (% style="color:red" %)**CN470**(%%):  LT with frequency bands CN470
2329 +* (% style="color:red" %)**AS923**(%%):  LT with frequency bands AS923
2330 +* (% style="color:red" %)**AU915**(%%):  LT with frequency bands AU915
2331 +* (% style="color:red" %)**US915**(%%):  LT with frequency bands US915
2332 +* (% style="color:red" %)**IN865**(%%):  LT with frequency bands IN865
2333 +* (% style="color:red" %)**CN779**(%%):  LT with frequency bands CN779
2355 2355  
2335 += 9. Packing Info =
2356 2356  
2357 -= 9. Packing information =
2358 2358  
2338 +**Package Includes**:
2359 2359  
2360 -**Package includes**:
2361 -
2362 2362  * LT-22222-L I/O Controller x 1
2363 2363  * Stick Antenna for LoRa RF part x 1
2364 2364  * Bracket for controller x1
2365 -* 3.5mm Programming cable x 1
2343 +* Program cable x 1
2366 2366  
2367 2367  **Dimension and weight**:
2368 2368  
2369 2369  * Device Size: 13.5 x 7 x 3 cm
2370 -* Device Weight: 105 g
2348 +* Device Weight: 105g
2371 2371  * Package Size / pcs : 14.5 x 8 x 5 cm
2372 -* Weight / pcs : 170 g
2350 +* Weight / pcs : 170g
2373 2373  
2374 -
2375 2375  = 10. Support =
2376 2376  
2377 2377  
2378 2378  * (((
2379 -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.
2356 +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.
2380 2380  )))
2381 2381  * (((
2382 -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]]
2359 +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]]
2383 2383  
2361 +
2384 2384  
2385 2385  )))
2386 2386  
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0