Changes for page LT-22222-L -- LoRa I/O Controller User Manual
Last modified by Saxer Lin on 2025/04/15 17:24
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 4 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -33,8 +33,6 @@ 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 - 38 38 ((( 39 39 You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways: 40 40 ... ... @@ -59,7 +59,7 @@ 59 59 * SX1276/78 Wireless Chip 60 60 * Power Consumption: 61 61 ** Idle: 4mA@12v 62 -** 20dB Transmit: 34mA@12 v60 +** 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:** ... ... @@ -68,7 +68,7 @@ 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.01 v)69 +* 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:** ... ... @@ -128,21 +128,14 @@ 128 128 * 1 x Counting Port 129 129 ))) 130 130 131 -= 2. Assembling the Device=129 += 2. Assembling = 132 132 133 - ==2.1 Whatisincluded in the package?==131 +Attach the LoRa antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper screw terminal block. Secure the antenna by tightening it clockwise. 134 134 135 -The package includes the following items: 136 - 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 141 - 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 144 == 2.2 Terminals == 145 145 135 +The LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 terminals and the lower screw terminal block has 10 terminals. 136 + 146 146 Upper screw terminal block (from left to right): 147 147 148 148 (% style="width:634px" %) ... ... @@ -169,28 +169,32 @@ 169 169 |(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2 170 170 |(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1 171 171 172 -== 2.3 Powering the LT-22222-L==163 +== 2.3 Powering the device == 173 173 174 -The LT-22222-L I/O Controller can be powered by a 7–24V DC power source. Connect thepower 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.165 +The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s positive wire to the VIN and the negative wire to the GND screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered. 175 175 167 +Powering on the device 176 176 177 - [[image:1653297104069-180.png]]169 +Once powered, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** The Things Stack. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LED** will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status. 178 178 171 +{{warning}} 172 +We recommend that you power on the LT-22222-L after configuring its registration information with a LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail. 173 +{{/warning}} 179 179 180 -= 3. Operation Mode = 181 181 182 - ==3.1How does it work? ==176 +[[image:1653297104069-180.png]] 183 183 178 + 179 += 3. Registering with a LoRaWAN Network Server = 180 + 184 184 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. 185 185 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 workingmode and start toJOINthe 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.183 +After powering on, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** the LoRaWAN network. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LED** will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status. 187 187 188 188 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. 189 189 190 - ==3.2 Registering with a LoRaWAN networkserver ==187 +The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network. 191 191 192 -The diagram below shows how the LT-22222-L connects to a typical LoRaWAN network. 193 - 194 194 [[image:image-20220523172350-1.png||height="266" width="864"]] 195 195 196 196 === 3.2.1 Prerequisites === ... ... @@ -203,63 +203,101 @@ 203 203 204 204 === 3.2.2 The Things Stack Sandbox (TTSS) === 205 205 201 +The Things Stack Sandbox was formally called The Things Stack Community Edition. 202 + 206 206 * Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account. 207 -* Create an application if you do not have one yet. 208 -* Register LT-22222-L with that application. Two registration options are available: 204 +* Create an application with The Things Stack if you do not have one yet. 205 +* Go to your application page and click on the **End devices** in the left menu. 206 +* On the End devices page, click on **+ Register end device**. Two registration options are available: 209 209 210 -==== Using the LoRaWAN Device Repository: ==== 211 211 212 -* Go to your application and click on the **Register end device** button. 209 +==== 3.2.2.1 Using the LoRaWAN Device Repository ==== 210 + 213 213 * On the **Register end device** page: 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. 212 +** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**. 213 +** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists. 214 +*** **End device brand**: Dragino Technology Co., Limited 215 +*** **Model**: LT22222-L I/O Controller 216 +*** **Hardware ver**: Unknown 217 +*** **Firmware ver**: 1.6.0 218 +*** **Profile (Region)**: Select the region that matches your device. 219 +** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 217 217 218 218 [[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]] 219 219 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. 223 + 224 +* Register end device page continued... 225 +** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network'. 226 +** In the **DevEUI** field, enter the **DevEUI**. 227 +** In the **AppKey** field, enter the **AppKey.** 228 +** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. 225 225 ** Under **After registration**, select the **View registered end device** option. 226 226 227 227 [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]] 228 228 229 -==== Enteringdeviceinformation manually:====233 +==== ==== 230 230 235 +==== 3.2.2.2 Adding device manually ==== 236 + 231 231 * On the **Register end device** page: 232 -** Select the **Enter end device specifies manually** optionas theinput method.233 -** Select the **Frequency plan** 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)** optionunder the **Activation mode**238 -** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities**. 238 +** Select the option **Enter end device specifies manually** under **Input method**. 239 +** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 240 +** Select the **LoRaWAN version** as **LoRaWAN Specification 1.0.3** 241 +** Select the **Regional Parameters version** as** RP001 Regional Parameters 1.0.3 revision A** 242 +** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the hidden section. 243 +** Select the option **Over the air activation (OTAA)** under the **Activation mode.** 244 +** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list. 239 239 240 240 [[image:lt-22222-l-manually-p1.png||height="625" width="1000"]] 241 241 242 242 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. 249 +* Register end device page continued... 250 +** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network' 251 +** In the **DevEUI** field, enter the **DevEUI**. 252 +** In the **AppKey** field, enter the **AppKey**. 253 +** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. 254 +** Under **After registration**, select the **View registered end device** option. 255 +** Click the **Register end device** button. 248 248 249 249 [[image:lt-22222-l-manually-p2.png||height="625" width="1000"]] 250 250 251 251 252 - ==== Joining====260 +You will be navigated to the **Device overview** page. 253 253 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. 255 255 256 -[[image: 1653298044601-602.png||height="405" width="709"]]263 +[[image:lt-22222-device-overview.png||height="625" width="1000"]] 257 257 258 258 266 +==== 3.2.2.3 Joining ==== 267 + 268 +On the Device overview page, click on **Live data** tab. The Live data panel for your device will display. 269 + 270 +Now power on your LT-22222-L. It will begin joining The Things Stack. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server. Once successfully joined, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**). 271 + 272 + 273 +[[image:lt-22222-join-network.png||height="625" width="1000"]] 274 + 275 + 276 +By default, you will receive an uplink data message from the device every 10 minutes. 277 + 278 +Click on one of a **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the decode_payload {} JSON object. 279 + 280 +[[image:lt-22222-ul-payload-decoded.png]] 281 + 282 + 283 +If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **End devices** > **LT-22222-L** > **Payload formatters** > **Uplink**. Then select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes. 284 + 285 +{{info}} 286 +The Things Stack provides two levels of payload formatters: application level and device level. The device-level payload formatters **override **the application-level payload formatters. 287 +{{/info}} 288 + 289 +[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]] 290 + 291 + 259 259 == 3.3 Work Modes and their Uplink Payload formats == 260 260 261 261 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 work ingmode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands.295 +The LT-22222-L has 5 **work modes**. It also has an interrupt/trigger mode for different types of applications that can be used together with any work mode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands. 263 263 264 264 * (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO 265 265 ... ... @@ -273,11 +273,15 @@ 273 273 274 274 * (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5 275 275 309 +The uplink messages are sent over LoRaWAN FPort 2. By default, an uplink message is sent every 10 minutes. 310 + 276 276 === 3.3.1 AT+MOD~=1, 2ACI+2AVI === 277 277 278 278 ((( 279 -Th e uplink payload is11 bytes long. Uplink messagesare sentoverLoRaWAN FPort 2. Bydefault,one uplink is sent every 10minutes. (% style="display:none" wfd-invisible="true" %)314 +This is the default mode. 280 280 316 +The uplink payload is 11 bytes long. (% style="display:none" wfd-invisible="true" %) 317 + 281 281 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 282 282 |(% 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** 283 283 |Value|((( ... ... @@ -324,13 +324,13 @@ 324 324 325 325 * [1] The RO1 relay channel is CLOSED, and the RO1 LED is ON. 326 326 * [0] The RO2 relay channel is OPEN, and the RO2 LED is OFF. 327 -* [1] DI3 - not used for LT-22222-L. 364 +* **[1] DI3 - not used for LT-22222-L.** 328 328 * [0] DI2 channel input is LOW, and the DI2 LED is OFF. 329 329 * [1] DI1 channel input state: 330 330 ** DI1 is FLOATING when no sensor is connected between DI1+ and DI1-. 331 331 ** DI1 is HIGH when a sensor is connected between DI1- and DI1+ and the sensor is ACTIVE. 332 332 ** DI1 LED is ON in both cases. 333 -* [0] DO3 - not used for LT-22222-L. 370 +* **[0] DO3 - not used for LT-22222-L.** 334 334 * [1] DO2 channel output is LOW, and the DO2 LED is ON. 335 335 * [0] DO1 channel output state: 336 336 ** DO1 is FLOATING when there is no load between DO1 and V+. ... ... @@ -355,7 +355,7 @@ 355 355 ))) 356 356 357 357 ((( 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. 395 +(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, FIRST, Reserve, Reserve, DO3, DO2 and DO1, and its size is 1 byte long as shown below. 359 359 360 360 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 361 361 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** ... ... @@ -1353,15 +1353,21 @@ 1353 1353 1354 1354 == 3.5 Integrating with ThingsEye.io == 1355 1355 1356 - If you are using one ofThe Things Stack plans,youcanintegrateThingsEye.iowith your application. Once integrated, ThingsEye.ioworks as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.1393 +The Things Stack application supports integration with ThingsEye.io. Once integrated, ThingsEye.io acts as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic. 1357 1357 1358 -=== 3.5.1 Configuring MQTT Connection Information withThe Things StackSandbox===1395 +=== 3.5.1 Configuring The Things Stack === 1359 1359 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. 1397 +We use The Things Stack Sandbox in this example: 1364 1364 1399 +* In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added. 1400 +* Select **MQTT** under **Integrations** in the left menu. 1401 +* In the **Connection information **section, under **Connection credentials**, The Things Stack displays an auto-generated **username**. You can use it or provide a new one. 1402 +* Click the **Generate new API key** button to generate a password. You can view it by clicking on the **visibility toggle/eye** icon. The API key works as the password. 1403 + 1404 +{{info}} 1405 +The username and password (API key) you created here are required in the next section. 1406 +{{/info}} 1407 + 1365 1365 [[image:tts-mqtt-integration.png||height="625" width="1000"]] 1366 1366 1367 1367 === 3.5.2 Configuring ThingsEye.io === ... ... @@ -1375,7 +1375,7 @@ 1375 1375 1376 1376 On the **Add integration** window, configure the following: 1377 1377 1378 - ~1.**Basic settings:**1421 +**Basic settings:** 1379 1379 1380 1380 * Select **The Things Stack Community** from the **Integration type** list. 1381 1381 * Enter a suitable name for your integration in the **Name **text** **box or keep the default name. ... ... @@ -1388,74 +1388,82 @@ 1388 1388 [[image:thingseye-io-step-2.png||height="625" width="1000"]] 1389 1389 1390 1390 1391 - 2.**Uplink data converter:**1434 +**Uplink data converter:** 1392 1392 1393 1393 * Click the **Create new** button if it is not selected by default. 1394 1394 * Enter a suitable name for the uplink data converter in the **Name **text** **box or keep the default name. 1395 1395 * Click the **JavaScript** button. 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]]. 1439 +* Paste the uplink decoder function into the text area (first, delete the default code). The demo uplink decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Uplink_Converter.js]]. 1397 1397 * Click the **Next** button. You will be navigated to the **Downlink data converter **tab. 1398 1398 1399 1399 [[image:thingseye-io-step-3.png||height="625" width="1000"]] 1400 1400 1401 -3.** Downlink data converter (this is an optional step):** 1402 1402 1445 +**Downlink data converter (this is an optional step):** 1446 + 1403 1403 * Click the **Create new** button if it is not selected by default. 1404 1404 * Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name 1405 1405 * Click the **JavaScript** button. 1406 -* Paste the downlink decoder function into the text area (first, delete the default code). The demo decoder function can be found here. 1450 +* Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Downlink_Converter.js]]. 1407 1407 * Click the **Next** button. You will be navigated to the **Connection** tab. 1408 1408 1409 1409 [[image:thingseye-io-step-4.png||height="625" width="1000"]] 1410 1410 1411 -4. **Connection:** 1412 1412 1456 +**Connection:** 1457 + 1413 1413 * Choose **Region** from the **Host type**. 1414 1414 * 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/...). 1415 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**. 1461 +* Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**. 1462 + 1463 +[[image:message-1.png]] 1464 + 1465 + 1417 1417 * Click the **Add** button. 1418 1418 1419 1419 [[image:thingseye-io-step-5.png||height="625" width="1000"]] 1420 1420 1421 1421 1422 -Your integration is added to the**itwill display on the **Integrations** page. Check whether the status is showingas'Active'.if not,checkyour configuration settingsagain.1471 +Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings. 1423 1423 1424 -[[image:thingseye-io-step-6.png||height="625" width="1000"]] 1425 1425 1474 +[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]] 1426 1426 1427 -Viewing integration details: 1428 1428 1429 - Click on theyourintegrationfrom the list. The Integration detailswindow will appear with the Details tab selected. The Details tab shows all the settings you have provided for this integration.1477 +**Viewing integration details**: 1430 1430 1431 - [add image here]1479 +Click on your integration from the list. The **Integration details** window will appear with the **Details **tab selected. The **Details **tab shows all the settings you have provided for this integration. 1432 1432 1433 - If you want toeditthesettings you have provided, click ontheToggle editmode button.1481 +[[image:integration-details.png||height="686" width="1000"]] 1434 1434 1435 -[add image here] 1436 1436 1437 -Once you have done click on the Apply changes button. 1484 +If you want to edit the settings you have provided, click on the **Toggle edit mode** button. Once you have done click on the **Apply changes **button. 1438 1438 1439 -Note: See also ThingsEye documentation. 1486 +{{info}} 1487 +See also ThingsEye documentation. 1488 +{{/info}} 1440 1440 1441 - Click ontheEventstab.1490 +**Viewing events:** 1442 1442 1443 - -SelectDebugfromtheEventtypedropdown.1492 +The **Events **tab displays all the uplink messages from the LT-22222-L. 1444 1444 1445 -- Select the time frame from the time window. 1494 +* Select **Debug **from the **Event type** dropdown. 1495 +* Select the** time frame** from the **time window**. 1446 1446 1447 -[inse rtimage]1497 +[[image:thingseye-events.png||height="686" width="1000"]] 1448 1448 1449 -- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message. 1450 1450 1451 - [insert image]1500 +* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message. 1452 1452 1502 +[[image:thingseye-json.png||width="1000"]] 1453 1453 1454 -Deleting the integration: 1455 1455 1456 - If you want to delete this integration,clicktheDeleteintegrationbutton.1505 +**Deleting the integration**: 1457 1457 1507 +If you want to delete this integration, click the **Delete integratio**n button. 1458 1458 1509 + 1459 1459 == 3.6 Interface Details == 1460 1460 1461 1461 === 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) === ... ... @@ -1698,13 +1698,14 @@ 1698 1698 |**RO1**|For LT-22222-L: ON when RO1 is closed, OFF when RO1 is open 1699 1699 |**RO2**|For LT-22222-L: ON when RO2 is closed, OFF when RO2 is open 1700 1700 1701 -= 4. Using AT Command = 1752 += 4. Using AT Commands = 1702 1702 1703 - == 4.1 Connecting the LT-22222-Ltoa computer==1754 +The LT-22222-L supports programming using AT Commands. 1704 1704 1756 +== 4.1 Connecting the LT-22222-L to a PC == 1705 1705 1706 1706 ((( 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 acomputer, as shown below.1759 +You can use a USB-to-TTL adapter along with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below. 1708 1708 ))) 1709 1709 1710 1710 [[image:1653358238933-385.png]] ... ... @@ -1711,7 +1711,7 @@ 1711 1711 1712 1712 1713 1713 ((( 1714 -On the PC, theuserneedsto 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 accessserial console of LT-22222-L.The AT commandsaredisabled by default, and a password (default:(% style="color:green" %)**123456**)(%%) must be entered to activethem, as shown below:1766 +On the PC, you need to set the (% style="color:#4f81bd" %)**serial tool **(%%)(such as [[PuTTY>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]] or [[SecureCRT>>https://www.vandyke.com/cgi-bin/releases.php?product=securecrt]]) to a baud rate of (% style="color:green" %)**9600**(%%) to access the serial console of LT-22222-L. Access to AT commands is disabled by default, and a password (default: (% style="color:green" %)**123456**)(%%) must be entered to enable AT command access, as shown below: 1715 1715 ))) 1716 1716 1717 1717 [[image:1653358355238-883.png]] ... ... @@ -1719,195 +1719,62 @@ 1719 1719 1720 1720 ((( 1721 1721 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 -))) 1723 1723 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> 1775 +== 4.2 LT-22222-L related AT commands == 1728 1728 ))) 1729 1729 1730 1730 ((( 1731 -AT+<CMD> : Run <CMD> 1732 -))) 1779 +The following is the list of all the AT commands related to the LT-22222-L, except for those used for switching between work modes. 1733 1733 1734 -((( 1735 -AT+<CMD>=<value> : Set the value 1781 +* AT+<CMD>? : Help on <CMD> 1782 +* AT+<CMD> : Run <CMD> 1783 +* AT+<CMD>=<value> : Set the value 1784 +* AT+<CMD>=? : Get the value 1785 +* ATZ: Trigger a reset of the MCU 1786 +* ##**AT+FDR**##: Reset Parameters to factory default, reserve keys 1787 +* **##AT+DEUI##**: Get or set the Device EUI (DevEUI) 1788 +* **##AT+DADDR##**: Get or set the Device Address (DevAddr) 1789 +* **##AT+APPKEY##**: Get or set the Application Key (AppKey) 1790 +* AT+NWKSKEY: Get or set the Network Session Key (NwkSKey) 1791 +* AT+APPSKEY: Get or set the Application Session Key (AppSKey) 1792 +* AT+APPEUI: Get or set the Application EUI (AppEUI) 1793 +* AT+ADR: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON) 1794 +* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification) 1795 +* AT+DR: Get or set the Data Rate. (0-7 corresponding to DR_X) 1796 +* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing 1797 +* AT+PNM: Get or set the public network mode. (0: off, 1: on) 1798 +* AT+RX2FQ: Get or set the Rx2 window frequency 1799 +* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X) 1800 +* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms 1801 +* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms 1802 +* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms 1803 +* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms 1804 +* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA) 1805 +* AT+NWKID: Get or set the Network ID 1806 +* AT+FCU: Get or set the Frame Counter Uplink (FCntUp) 1807 +* AT+FCD: Get or set the Frame Counter Downlink (FCntDown) 1808 +* AT+CLASS: Get or set the Device Class 1809 +* AT+JOIN: Join network 1810 +* AT+NJS: Get OTAA Join Status 1811 +* AT+SENDB: Send hexadecimal data along with the application port 1812 +* AT+SEND: Send text data along with the application port 1813 +* AT+RECVB: Print last received data in binary format (with hexadecimal values) 1814 +* AT+RECV: Print last received data in raw format 1815 +* AT+VER: Get current image version and Frequency Band 1816 +* AT+CFM: Get or Set the confirmation mode (0-1) 1817 +* AT+CFS: Get confirmation status of the last AT+SEND (0-1) 1818 +* AT+SNR: Get the SNR of the last received packet 1819 +* AT+RSSI: Get the RSSI of the last received packet 1820 +* AT+TDC: Get or set the application data transmission interval in ms 1821 +* AT+PORT: Get or set the application port 1822 +* AT+DISAT: Disable AT commands 1823 +* AT+PWORD: Set password, max 9 digits 1824 +* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode 1825 +* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470 1826 +* AT+CFG: Print all settings 1736 1736 ))) 1737 1737 1738 -((( 1739 -AT+<CMD>=? : Get the value 1740 -))) 1741 1741 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 - 1911 1911 == 4.2 Common AT Command Sequence == 1912 1912 1913 1913 === 4.2.1 Multi-channel ABP mode (Use with SX1301/LG308) === ... ... @@ -1916,41 +1916,41 @@ 1916 1916 1917 1917 1918 1918 ((( 1919 -(% style="color:blue" %)**If device has not joined network yet:** 1838 +(% style="color:blue" %)**If the device has not joined the network yet:** 1920 1920 ))) 1921 1921 ))) 1922 1922 1923 1923 ((( 1924 -(% style="background-color:#dcdcdc" %)**123456** 1843 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**## 1925 1925 ))) 1926 1926 1927 1927 ((( 1928 -(% style="background-color:#dcdcdc" %)**AT+FDR** 1847 +(% style="background-color:#dcdcdc" %)##**AT+FDR ~/~/reset parameters to factory default, reserve keys**## 1929 1929 ))) 1930 1930 1931 1931 ((( 1932 -(% style="background-color:#dcdcdc" %)**123456** 1851 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**## 1933 1933 ))) 1934 1934 1935 1935 ((( 1936 -(% style="background-color:#dcdcdc" %)**AT+NJM=0** 1855 +(% style="background-color:#dcdcdc" %)##**AT+NJM=0 ~/~/set to ABP mode**## 1937 1937 ))) 1938 1938 1939 1939 ((( 1940 -(% style="background-color:#dcdcdc" %)**ATZ** 1859 +(% style="background-color:#dcdcdc" %)##**ATZ ~/~/reset MCU**## 1941 1941 ))) 1942 1942 1943 1943 1944 1944 ((( 1945 -(% style="color:blue" %)**If device already joined network:** 1864 +(% style="color:blue" %)**If the device has already joined the network:** 1946 1946 ))) 1947 1947 1948 1948 ((( 1949 -(% style="background-color:#dcdcdc" %)**AT+NJM=0** 1868 +(% style="background-color:#dcdcdc" %)##**AT+NJM=0**## 1950 1950 ))) 1951 1951 1952 1952 ((( 1953 -(% style="background-color:#dcdcdc" %)**ATZ** 1872 +(% style="background-color:#dcdcdc" %)##**ATZ**## 1954 1954 ))) 1955 1955 1956 1956 ... ... @@ -2056,29 +2056,42 @@ 2056 2056 2057 2057 = 6. FAQ = 2058 2058 2059 - ==6.1 Howtoupgrade theimage?==1978 +This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly. 2060 2060 1980 +== 6.1 How to update the firmware? == 2061 2061 2062 - The LT-22222-L I/O Controller isshippedwith a 3.5mm cable,which isused to uploadn imagetoLT in orderto:1982 +Dragino frequently releases firmware updates for the LT-22222-L. 2063 2063 2064 -* Support new features. 2065 -* Fix bugs. 2066 -* Change LoRaWAN bands. 1984 +Updating your LT-22222-L with the latest firmware version helps to: 2067 2067 2068 -Below is the hardware connection setup for uploading an image to the LT: 1986 +* Support new features 1987 +* Fix bugs 1988 +* Change LoRaWAN frequency bands 2069 2069 1990 +You will need the following things before proceeding: 1991 + 1992 +* 3.5mm programming cable (included with the LT-22222-L as an additional accessory) 1993 +* USB to TTL adapter 1994 +* Download and install the [[STM32 Flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]]. (replaced by STM32CubeProgrammer) 1995 +* Download the latest firmware image from [[LT-22222-L firmware image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]]. Check the file name of the firmware to find the correct region. 1996 + 1997 +{{info}} 1998 +As of this writing, the latest firmware version available for the LT-22222-L is v1.6.1. 1999 +{{/info}} 2000 + 2001 +Below is the hardware setup for uploading a firmware image to the LT-22222-L: 2002 + 2003 + 2070 2070 [[image:1653359603330-121.png]] 2071 2071 2072 2072 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 - 2007 +Start the STM32 Flash Loader and choose the correct COM port to update. 2078 2078 2079 2079 ((( 2010 +((( 2080 2080 (% style="color:blue" %)**For LT-22222-L**(%%): 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. 2012 + 2013 +Hold down the **PRO** button, then briefly press the **RST** button. The **DO1** LED will change from OFF to ON. When the **DO1** LED is ON, it indicates that the device is in firmware download mode. 2082 2082 ))) 2083 2083 2084 2084 ... ... @@ -2100,7 +2100,7 @@ 2100 2100 2101 2101 ((( 2102 2102 ((( 2103 -== 6.2 How to change the LoRa FrequencyBands/Region? ==2035 +== 6.2 How to change the LoRaWAN frequency band/region? == 2104 2104 2105 2105 2106 2106 ))) ... ... @@ -2113,7 +2113,7 @@ 2113 2113 ((( 2114 2114 2115 2115 2116 -== 6.3 How to set 2048 +== 6.3 How to setup LT to work with a Single Channel Gateway, such as LG01/LG02? == 2117 2117 2118 2118 2119 2119 ))) ... ... @@ -2190,61 +2190,55 @@ 2190 2190 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/]] 2191 2191 2192 2192 2193 -== 6.5 Can I see the counting event in Serial? ==2125 +== 6.5 Can I see the counting event in the serial output? == 2194 2194 2195 2195 2196 2196 ((( 2197 - Usercan run AT+DEBUGcommandseethe counting event in serial. If firmware too old and doesn't support.User canupdate to latest firmware first.2129 +You can run the AT command AT+DEBUG to view the counting event in the serial output. If the firmware is too old and doesn’t support AT+DEBUG, update to the latest firmware first. 2198 2198 2199 2199 2200 2200 == 6.6 Can I use point-to-point communication with LT-22222-L? == 2201 2201 2202 2202 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 - 2205 - 2135 +Yes, you can. Please refer to the [[Point-to-Point Communication of LT-22222-L>>https://wiki.dragino.com/xwiki/bin/view/Main/%20Point%20to%20Point%20Communication%20of%20LT-22222-L/]] page. The firmware that supports point-to-point communication can be found [[here>>https://github.com/dragino/LT-22222-L/releases]]. 2206 2206 ))) 2207 2207 2208 2208 ((( 2209 -== 6.7 Why does the relay output become thedefault andopen relay after thelt22222 is powered off? ==2139 +== 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? == 2210 2210 2211 2211 2212 -If the device is not shut down, but directly powered off. 2142 +* If the device is not properly shut down and is directly powered off. 2143 +* It will default to a power-off state. 2144 +* In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory. 2145 +* After a restart, the status before the power failure will be read from flash. 2213 2213 2214 - Itwilldefaultthatthisis apower-offstate.2147 +== 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? == 2215 2215 2216 -In modes 2 to 5, DO RO status and pulse count are saved in flash. 2217 2217 2218 - After restart,thestatusbeforepowerfailure willbe readfromflash.2150 +The LT-22222-L's built-in relay is Normally Open (NO). You can use an external relay to achieve a Normally Closed (NC) configuration. The circuit diagram is shown below: 2219 2219 2220 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 - 2227 2227 [[image:image-20221006170630-1.png||height="610" width="945"]] 2228 2228 2229 2229 2230 -== 6.9 Can LT22222-L save RO state? == 2156 +== 6.9 Can the LT-22222-L save the RO state? == 2231 2231 2232 2232 2233 - Firmware versionneedsobenolessthan1.6.0.2159 +The firmware version must be at least 1.6.0. 2234 2234 2235 2235 2236 -== 6.10 Why does the LT22222 always report 15.585V when measuring AVI? == 2162 +== 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? == 2237 2237 2238 2238 2239 -It is likely that the GND is not connected during the measurement, or the wire connected to the GND is loose. 2165 +It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose. 2240 2240 2241 2241 2242 -= 7. Trouble Shooting =2168 += 7. Troubleshooting = 2243 2243 ))) 2244 2244 2245 2245 ((( 2246 2246 ((( 2247 -== 7.1 Downlink doesn't work,howtosolveit? ==2173 +== 7.1 Downlink isn't working. How can I solve this? == 2248 2248 2249 2249 2250 2250 ))) ... ... @@ -2251,42 +2251,42 @@ 2251 2251 ))) 2252 2252 2253 2253 ((( 2254 -Please see this link forhow todebug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]]2180 +Please refer to this link for debugging instructions: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]] 2255 2255 ))) 2256 2256 2257 2257 ((( 2258 2258 2259 2259 2260 -== 7.2 Hav etroubletoupload image.==2186 +== 7.2 Having trouble uploading an image? == 2261 2261 2262 2262 2263 2263 ))) 2264 2264 2265 2265 ((( 2266 - See this link for trouble2192 +Please refer to this link for troubleshooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]] 2267 2267 ))) 2268 2268 2269 2269 ((( 2270 2270 2271 2271 2272 -== 7.3 Why Ican't join TTN in US915 /AU915 bands? ==2198 +== 7.3 Why can't I join TTN in the US915 /AU915 bands? == 2273 2273 2274 2274 2275 2275 ))) 2276 2276 2277 2277 ((( 2278 -It might be a bout the channelsmapping. [[Pleasesee this link for detail>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]2204 +It might be related to the channel mapping. [[Please refer to this link for details.>>https://github.com/dragino/LT-22222-L/releases]] 2279 2279 ))) 2280 2280 2281 2281 2282 -== 7.4 Why can LT22222 perform Uplink normally, but cannot receive Downlink? == 2208 +== 7.4 Why can the LT-22222-L perform Uplink normally, but cannot receive Downlink? == 2283 2283 2284 2284 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 bringtheir countsback together: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]2211 +The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue. 2212 +Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]] 2287 2287 2288 2288 2289 -= 8. Order Info =2215 += 8. Ordering information = 2290 2290 2291 2291 2292 2292 (% style="color:#4f81bd" %)**LT-22222-L-XXX:** ... ... @@ -2293,43 +2293,42 @@ 2293 2293 2294 2294 (% style="color:#4f81bd" %)**XXX:** 2295 2295 2296 -* (% style="color:red" %)**EU433**(%%): 2297 -* (% style="color:red" %)**EU868**(%%): 2298 -* (% style="color:red" %)**KR920**(%%): 2299 -* (% style="color:red" %)**CN470**(%%): 2300 -* (% style="color:red" %)**AS923**(%%): 2301 -* (% style="color:red" %)**AU915**(%%): 2302 -* (% style="color:red" %)**US915**(%%): 2303 -* (% style="color:red" %)**IN865**(%%): 2304 -* (% style="color:red" %)**CN779**(%%): 2222 +* (% style="color:red" %)**EU433**(%%): LT with frequency bands EU433 2223 +* (% style="color:red" %)**EU868**(%%): LT with frequency bands EU868 2224 +* (% style="color:red" %)**KR920**(%%): LT with frequency bands KR920 2225 +* (% style="color:red" %)**CN470**(%%): LT with frequency bands CN470 2226 +* (% style="color:red" %)**AS923**(%%): LT with frequency bands AS923 2227 +* (% style="color:red" %)**AU915**(%%): LT with frequency bands AU915 2228 +* (% style="color:red" %)**US915**(%%): LT with frequency bands US915 2229 +* (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865 2230 +* (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779 2305 2305 2306 -= 9. Packing Info =2232 += 9. Packing information = 2307 2307 2308 2308 2309 -**Package Includes**:2235 +**Package includes**: 2310 2310 2311 -* LT-22222-L I/O Controller x 12312 -* StickAntennaforLoRaRFpartx12313 -* Bracket forcontrollerx12314 -* Program cablex 12237 +* 1 x LT-22222-L I/O Controller 2238 +* 1 x LoRa antenna matched to the frequency of the LT-22222-L 2239 +* 1 x bracket for DIN rail mounting 2240 +* 1 x 3.5mm programming cable 2315 2315 2316 2316 **Dimension and weight**: 2317 2317 2318 2318 * Device Size: 13.5 x 7 x 3 cm 2319 -* Device Weight: 105g 2245 +* Device Weight: 105 g 2320 2320 * Package Size / pcs : 14.5 x 8 x 5 cm 2321 -* Weight / pcs : 170g 2247 +* Weight / pcs : 170 g 2322 2322 2323 2323 = 10. Support = 2324 2324 2325 2325 2326 2326 * ((( 2327 -Support is providedMonday 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 thebefore-mentioned schedule.2253 +Support is available Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different time zones, we cannot offer live support. However, your questions will be answered as soon as possible within the aforementioned schedule. 2328 2328 ))) 2329 2329 * ((( 2330 -Provide as much information as possible regarding your enquiry (product models, accuratelydescribeyourproblemandsteps to replicate it etc) and send a mail to [[Support@dragino.cc>>mailto:Support@dragino.cc]]2256 +Please provide as much information as possible regarding your inquiry (e.g., product models, a detailed description of the problem, steps to replicate it, etc.) and send an email to [[support@dragino.cc>>mailto:support@dragino.cc]] 2331 2331 2332 - 2333 2333 2334 2334 ))) 2335 2335
- integration-details.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +463.9 KB - Content
- thingseye-events.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +530.6 KB - Content
- thingseye-json.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +554.8 KB - Content
- thingseye.io_integrationsCenter_integrations-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +469.3 KB - Content