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, 2 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,49 +203,61 @@ 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. 248 -* Click the **Register end device** button. 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. 249 249 250 250 [[image:lt-22222-l-manually-p2.png||height="625" width="1000"]] 251 251 ... ... @@ -252,23 +252,33 @@ 252 252 253 253 You will be navigated to the **Device overview** page. 254 254 262 + 255 255 [[image:lt-22222-device-overview.png||height="625" width="1000"]] 256 256 257 257 258 -==== Joining ==== 266 +==== 3.2.2.3 Joining ==== 259 259 260 - Click on**Live data** in theleft navigation. Then,poweron LT-22222-L. It will join TheThingsStackLoRaWANnetworkserver.You can seethe**joinrequest**, **joinaccept**,followedby **uplinkdatamessages**formthedeviceshowingin the **Livedata**panel.268 +On the Device overview page, click on **Live data** tab. The Live data panel for your device will display. 261 261 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 + 262 262 [[image:lt-22222-join-network.png||height="625" width="1000"]] 263 263 264 264 265 - Clickon a messagewiththemessgetype, **Forwarduplink data message**.Youcan seetheodeduplink payloadasshownbelow.276 +By default, you will receive an uplink data message from the device every 10 minutes. 266 266 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 + 267 267 [[image:lt-22222-ul-payload-decoded.png]] 268 268 269 269 270 270 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. 271 271 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 + 272 272 [[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]] 273 273 274 274 ... ... @@ -275,7 +275,7 @@ 275 275 == 3.3 Work Modes and their Uplink Payload formats == 276 276 277 277 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 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. 279 279 280 280 * (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO 281 281 ... ... @@ -289,11 +289,15 @@ 289 289 290 290 * (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5 291 291 309 +The uplink messages are sent over LoRaWAN FPort 2. By default, an uplink message is sent every 10 minutes. 310 + 292 292 === 3.3.1 AT+MOD~=1, 2ACI+2AVI === 293 293 294 294 ((( 295 -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. 296 296 316 +The uplink payload is 11 bytes long. (% style="display:none" wfd-invisible="true" %) 317 + 297 297 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 298 298 |(% 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** 299 299 |Value|((( ... ... @@ -340,13 +340,13 @@ 340 340 341 341 * [1] The RO1 relay channel is CLOSED, and the RO1 LED is ON. 342 342 * [0] The RO2 relay channel is OPEN, and the RO2 LED is OFF. 343 -* [1] DI3 - not used for LT-22222-L. 364 +* **[1] DI3 - not used for LT-22222-L.** 344 344 * [0] DI2 channel input is LOW, and the DI2 LED is OFF. 345 345 * [1] DI1 channel input state: 346 346 ** DI1 is FLOATING when no sensor is connected between DI1+ and DI1-. 347 347 ** DI1 is HIGH when a sensor is connected between DI1- and DI1+ and the sensor is ACTIVE. 348 348 ** DI1 LED is ON in both cases. 349 -* [0] DO3 - not used for LT-22222-L. 370 +* **[0] DO3 - not used for LT-22222-L.** 350 350 * [1] DO2 channel output is LOW, and the DO2 LED is ON. 351 351 * [0] DO1 channel output state: 352 352 ** DO1 is FLOATING when there is no load between DO1 and V+. ... ... @@ -371,7 +371,7 @@ 371 371 ))) 372 372 373 373 ((( 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. 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. 375 375 376 376 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 377 377 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** ... ... @@ -1369,25 +1369,25 @@ 1369 1369 1370 1370 == 3.5 Integrating with ThingsEye.io == 1371 1371 1372 -The Things Stack applications can beintegratedwith ThingsEye.io. 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. 1373 1373 1374 -=== 3.5.1 Configuring MQTT Connection Information withThe Things StackSandbox===1395 +=== 3.5.1 Configuring The Things Stack === 1375 1375 1376 -We use The Things Stack Sandbox for demonstatingthe configurationbut other1397 +We use The Things Stack Sandbox in this example: 1377 1377 1378 -* In **The Things Stack Sandbox**, select yourapplicationunder**Applications**.1379 -* Select **MQTT** under **Integrations**. 1380 -* In the **Connection information **section, for **Username**, The Things Stack displays an auto-generated username. You can use it or provide a new one.1381 -* For the **Password**, click the **Generate new API key** button to generate a password. You canseeit by clicking on the **eye**button. The API key works as the password.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. 1382 1382 1383 -NOTE. The username and password (API key) you created here are required in the next section. 1404 +{{info}} 1405 +The username and password (API key) you created here are required in the next section. 1406 +{{/info}} 1384 1384 1385 1385 [[image:tts-mqtt-integration.png||height="625" width="1000"]] 1386 1386 1387 1387 === 3.5.2 Configuring ThingsEye.io === 1388 1388 1389 -This section guides you on how to create an integration in ThingsEye to connect with The Things Stack MQTT server. 1390 - 1391 1391 * Login to your [[ThingsEye.io >>https://thingseye.io]]account. 1392 1392 * Under the **Integrations center**, click **Integrations**. 1393 1393 * Click the **Add integration** button (the button with the **+** symbol). ... ... @@ -1426,7 +1426,7 @@ 1426 1426 * Click the **Create new** button if it is not selected by default. 1427 1427 * Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name 1428 1428 * Click the **JavaScript** button. 1429 -* Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink 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]]. 1430 1430 * Click the **Next** button. You will be navigated to the **Connection** tab. 1431 1431 1432 1432 [[image:thingseye-io-step-4.png||height="625" width="1000"]] ... ... @@ -1455,7 +1455,7 @@ 1455 1455 1456 1456 **Viewing integration details**: 1457 1457 1458 -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. 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. 1459 1459 1460 1460 [[image:integration-details.png||height="686" width="1000"]] 1461 1461 ... ... @@ -1462,24 +1462,25 @@ 1462 1462 1463 1463 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. 1464 1464 1465 -Note: See also ThingsEye documentation. 1486 +{{info}} 1487 +See also ThingsEye documentation. 1488 +{{/info}} 1466 1466 1467 - 1468 1468 **Viewing events:** 1469 1469 1470 -Th is tab1492 +The **Events **tab displays all the uplink messages from the LT-22222-L. 1471 1471 1472 -* Click on the **Events **tab. 1473 1473 * Select **Debug **from the **Event type** dropdown. 1474 -* Select the** 1495 +* Select the** time frame** from the **time window**. 1475 1475 1476 -[inse rtimage]1497 +[[image:thingseye-events.png||height="686" width="1000"]] 1477 1477 1478 -- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message. 1479 1479 1480 - [insert image]1500 +* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message. 1481 1481 1502 +[[image:thingseye-json.png||width="1000"]] 1482 1482 1504 + 1483 1483 **Deleting the integration**: 1484 1484 1485 1485 If you want to delete this integration, click the **Delete integratio**n button. ... ... @@ -1727,13 +1727,14 @@ 1727 1727 |**RO1**|For LT-22222-L: ON when RO1 is closed, OFF when RO1 is open 1728 1728 |**RO2**|For LT-22222-L: ON when RO2 is closed, OFF when RO2 is open 1729 1729 1730 -= 4. Using AT Command = 1752 += 4. Using AT Commands = 1731 1731 1732 - == 4.1 Connecting the LT-22222-Ltoa computer==1754 +The LT-22222-L supports programming using AT Commands. 1733 1733 1756 +== 4.1 Connecting the LT-22222-L to a PC == 1734 1734 1735 1735 ((( 1736 - 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. 1737 1737 ))) 1738 1738 1739 1739 [[image:1653358238933-385.png]] ... ... @@ -1740,7 +1740,7 @@ 1740 1740 1741 1741 1742 1742 ((( 1743 -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: 1744 1744 ))) 1745 1745 1746 1746 [[image:1653358355238-883.png]] ... ... @@ -1748,195 +1748,62 @@ 1748 1748 1749 1749 ((( 1750 1750 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/]] 1751 -))) 1752 1752 1753 -((( 1754 -The following table lists all the AT commands related to the LT-22222-L, except for those used for switching between modes. 1755 - 1756 -AT+<CMD>? : Help on <CMD> 1775 +== 4.2 LT-22222-L related AT commands == 1757 1757 ))) 1758 1758 1759 1759 ((( 1760 -AT+<CMD> : Run <CMD> 1761 -))) 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. 1762 1762 1763 -((( 1764 -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 1765 1765 ))) 1766 1766 1767 -((( 1768 -AT+<CMD>=? : Get the value 1769 -))) 1770 1770 1771 -((( 1772 -ATZ: Trig a reset of the MCU 1773 -))) 1774 - 1775 -((( 1776 -AT+FDR: Reset Parameters to Factory Default, Keys Reserve 1777 -))) 1778 - 1779 -((( 1780 -AT+DEUI: Get or Set the Device EUI 1781 -))) 1782 - 1783 -((( 1784 -AT+DADDR: Get or Set the Device Address 1785 -))) 1786 - 1787 -((( 1788 -AT+APPKEY: Get or Set the Application Key 1789 -))) 1790 - 1791 -((( 1792 -AT+NWKSKEY: Get or Set the Network Session Key 1793 -))) 1794 - 1795 -((( 1796 -AT+APPSKEY: Get or Set the Application Session Key 1797 -))) 1798 - 1799 -((( 1800 -AT+APPEUI: Get or Set the Application EUI 1801 -))) 1802 - 1803 -((( 1804 -AT+ADR: Get or Set the Adaptive Data Rate setting. (0: off, 1: on) 1805 -))) 1806 - 1807 -((( 1808 -AT+TXP: Get or Set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Spec) 1809 -))) 1810 - 1811 -((( 1812 -AT+DR: Get or Set the Data Rate. (0-7 corresponding to DR_X) 1813 -))) 1814 - 1815 -((( 1816 -AT+DCS: Get or Set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing 1817 -))) 1818 - 1819 -((( 1820 -AT+PNM: Get or Set the public network mode. (0: off, 1: on) 1821 -))) 1822 - 1823 -((( 1824 -AT+RX2FQ: Get or Set the Rx2 window frequency 1825 -))) 1826 - 1827 -((( 1828 -AT+RX2DR: Get or Set the Rx2 window data rate (0-7 corresponding to DR_X) 1829 -))) 1830 - 1831 -((( 1832 -AT+RX1DL: Get or Set the delay between the end of the Tx and the Rx Window 1 in ms 1833 -))) 1834 - 1835 -((( 1836 -AT+RX2DL: Get or Set the delay between the end of the Tx and the Rx Window 2 in ms 1837 -))) 1838 - 1839 -((( 1840 -AT+JN1DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms 1841 -))) 1842 - 1843 -((( 1844 -AT+JN2DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms 1845 -))) 1846 - 1847 -((( 1848 -AT+NJM: Get or Set the Network Join Mode. (0: ABP, 1: OTAA) 1849 -))) 1850 - 1851 -((( 1852 -AT+NWKID: Get or Set the Network ID 1853 -))) 1854 - 1855 -((( 1856 -AT+FCU: Get or Set the Frame Counter Uplink 1857 -))) 1858 - 1859 -((( 1860 -AT+FCD: Get or Set the Frame Counter Downlink 1861 -))) 1862 - 1863 -((( 1864 -AT+CLASS: Get or Set the Device Class 1865 -))) 1866 - 1867 -((( 1868 -AT+JOIN: Join network 1869 -))) 1870 - 1871 -((( 1872 -AT+NJS: Get OTAA Join Status 1873 -))) 1874 - 1875 -((( 1876 -AT+SENDB: Send hexadecimal data along with the application port 1877 -))) 1878 - 1879 -((( 1880 -AT+SEND: Send text data along with the application port 1881 -))) 1882 - 1883 -((( 1884 -AT+RECVB: Print last received data in binary format (with hexadecimal values) 1885 -))) 1886 - 1887 -((( 1888 -AT+RECV: Print last received data in raw format 1889 -))) 1890 - 1891 -((( 1892 -AT+VER: Get current image version and Frequency Band 1893 -))) 1894 - 1895 -((( 1896 -AT+CFM: Get or Set the confirmation mode (0-1) 1897 -))) 1898 - 1899 -((( 1900 -AT+CFS: Get confirmation status of the last AT+SEND (0-1) 1901 -))) 1902 - 1903 -((( 1904 -AT+SNR: Get the SNR of the last received packet 1905 -))) 1906 - 1907 -((( 1908 -AT+RSSI: Get the RSSI of the last received packet 1909 -))) 1910 - 1911 -((( 1912 -AT+TDC: Get or set the application data transmission interval in ms 1913 -))) 1914 - 1915 -((( 1916 -AT+PORT: Get or set the application port 1917 -))) 1918 - 1919 -((( 1920 -AT+DISAT: Disable AT commands 1921 -))) 1922 - 1923 -((( 1924 -AT+PWORD: Set password, max 9 digits 1925 -))) 1926 - 1927 -((( 1928 -AT+CHS: Get or Set Frequency (Unit: Hz) for Single Channel Mode 1929 -))) 1930 - 1931 -((( 1932 -AT+CHE: Get or Set eight channels mode, Only for US915, AU915, CN470 1933 -))) 1934 - 1935 -((( 1936 -AT+CFG: Print all settings 1937 -))) 1938 - 1939 - 1940 1940 == 4.2 Common AT Command Sequence == 1941 1941 1942 1942 === 4.2.1 Multi-channel ABP mode (Use with SX1301/LG308) === ... ... @@ -1945,41 +1945,41 @@ 1945 1945 1946 1946 1947 1947 ((( 1948 -(% style="color:blue" %)**If device has not joined network yet:** 1838 +(% style="color:blue" %)**If the device has not joined the network yet:** 1949 1949 ))) 1950 1950 ))) 1951 1951 1952 1952 ((( 1953 -(% style="background-color:#dcdcdc" %)**123456** 1843 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**## 1954 1954 ))) 1955 1955 1956 1956 ((( 1957 -(% style="background-color:#dcdcdc" %)**AT+FDR** 1847 +(% style="background-color:#dcdcdc" %)##**AT+FDR ~/~/reset parameters to factory default, reserve keys**## 1958 1958 ))) 1959 1959 1960 1960 ((( 1961 -(% style="background-color:#dcdcdc" %)**123456** 1851 +(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**## 1962 1962 ))) 1963 1963 1964 1964 ((( 1965 -(% style="background-color:#dcdcdc" %)**AT+NJM=0** 1855 +(% style="background-color:#dcdcdc" %)##**AT+NJM=0 ~/~/set to ABP mode**## 1966 1966 ))) 1967 1967 1968 1968 ((( 1969 -(% style="background-color:#dcdcdc" %)**ATZ** 1859 +(% style="background-color:#dcdcdc" %)##**ATZ ~/~/reset MCU**## 1970 1970 ))) 1971 1971 1972 1972 1973 1973 ((( 1974 -(% style="color:blue" %)**If device already joined network:** 1864 +(% style="color:blue" %)**If the device has already joined the network:** 1975 1975 ))) 1976 1976 1977 1977 ((( 1978 -(% style="background-color:#dcdcdc" %)**AT+NJM=0** 1868 +(% style="background-color:#dcdcdc" %)##**AT+NJM=0**## 1979 1979 ))) 1980 1980 1981 1981 ((( 1982 -(% style="background-color:#dcdcdc" %)**ATZ** 1872 +(% style="background-color:#dcdcdc" %)##**ATZ**## 1983 1983 ))) 1984 1984 1985 1985 ... ... @@ -2085,29 +2085,42 @@ 2085 2085 2086 2086 = 6. FAQ = 2087 2087 2088 - ==6.1 Howtoupgrade theimage?==1978 +This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly. 2089 2089 1980 +== 6.1 How to update the firmware? == 2090 2090 2091 - 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. 2092 2092 2093 -* Support new features. 2094 -* Fix bugs. 2095 -* Change LoRaWAN bands. 1984 +Updating your LT-22222-L with the latest firmware version helps to: 2096 2096 2097 -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 2098 2098 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 + 2099 2099 [[image:1653359603330-121.png]] 2100 2100 2101 2101 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 - 2007 +Start the STM32 Flash Loader and choose the correct COM port to update. 2107 2107 2108 2108 ((( 2010 +((( 2109 2109 (% style="color:blue" %)**For LT-22222-L**(%%): 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. 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. 2111 2111 ))) 2112 2112 2113 2113 ... ... @@ -2129,7 +2129,7 @@ 2129 2129 2130 2130 ((( 2131 2131 ((( 2132 -== 6.2 How to change the LoRa FrequencyBands/Region? ==2035 +== 6.2 How to change the LoRaWAN frequency band/region? == 2133 2133 2134 2134 2135 2135 ))) ... ... @@ -2142,7 +2142,7 @@ 2142 2142 ((( 2143 2143 2144 2144 2145 -== 6.3 How to set 2048 +== 6.3 How to setup LT to work with a Single Channel Gateway, such as LG01/LG02? == 2146 2146 2147 2147 2148 2148 ))) ... ... @@ -2219,61 +2219,55 @@ 2219 2219 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/]] 2220 2220 2221 2221 2222 -== 6.5 Can I see the counting event in Serial? ==2125 +== 6.5 Can I see the counting event in the serial output? == 2223 2223 2224 2224 2225 2225 ((( 2226 - 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. 2227 2227 2228 2228 2229 2229 == 6.6 Can I use point-to-point communication with LT-22222-L? == 2230 2230 2231 2231 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 - 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]]. 2235 2235 ))) 2236 2236 2237 2237 ((( 2238 -== 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? == 2239 2239 2240 2240 2241 -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. 2242 2242 2243 - Itwilldefaultthatthisis apower-offstate.2147 +== 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? == 2244 2244 2245 -In modes 2 to 5, DO RO status and pulse count are saved in flash. 2246 2246 2247 - 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: 2248 2248 2249 2249 2250 -== 6.8 Can i set up LT-22222-L as a NC(Normal Close) Relay? == 2251 - 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 - 2256 2256 [[image:image-20221006170630-1.png||height="610" width="945"]] 2257 2257 2258 2258 2259 -== 6.9 Can LT22222-L save RO state? == 2156 +== 6.9 Can the LT-22222-L save the RO state? == 2260 2260 2261 2261 2262 - Firmware versionneedsobenolessthan1.6.0.2159 +The firmware version must be at least 1.6.0. 2263 2263 2264 2264 2265 -== 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? == 2266 2266 2267 2267 2268 -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. 2269 2269 2270 2270 2271 -= 7. Trouble Shooting =2168 += 7. Troubleshooting = 2272 2272 ))) 2273 2273 2274 2274 ((( 2275 2275 ((( 2276 -== 7.1 Downlink doesn't work,howtosolveit? ==2173 +== 7.1 Downlink isn't working. How can I solve this? == 2277 2277 2278 2278 2279 2279 ))) ... ... @@ -2280,42 +2280,42 @@ 2280 2280 ))) 2281 2281 2282 2282 ((( 2283 -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"]] 2284 2284 ))) 2285 2285 2286 2286 ((( 2287 2287 2288 2288 2289 -== 7.2 Hav etroubletoupload image.==2186 +== 7.2 Having trouble uploading an image? == 2290 2290 2291 2291 2292 2292 ))) 2293 2293 2294 2294 ((( 2295 - 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]] 2296 2296 ))) 2297 2297 2298 2298 ((( 2299 2299 2300 2300 2301 -== 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? == 2302 2302 2303 2303 2304 2304 ))) 2305 2305 2306 2306 ((( 2307 -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]] 2308 2308 ))) 2309 2309 2310 2310 2311 -== 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? == 2312 2312 2313 2313 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 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"]] 2316 2316 2317 2317 2318 -= 8. Order Info =2215 += 8. Ordering information = 2319 2319 2320 2320 2321 2321 (% style="color:#4f81bd" %)**LT-22222-L-XXX:** ... ... @@ -2322,43 +2322,42 @@ 2322 2322 2323 2323 (% style="color:#4f81bd" %)**XXX:** 2324 2324 2325 -* (% style="color:red" %)**EU433**(%%): 2326 -* (% style="color:red" %)**EU868**(%%): 2327 -* (% style="color:red" %)**KR920**(%%): 2328 -* (% style="color:red" %)**CN470**(%%): 2329 -* (% style="color:red" %)**AS923**(%%): 2330 -* (% style="color:red" %)**AU915**(%%): 2331 -* (% style="color:red" %)**US915**(%%): 2332 -* (% style="color:red" %)**IN865**(%%): 2333 -* (% 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 2334 2334 2335 -= 9. Packing Info =2232 += 9. Packing information = 2336 2336 2337 2337 2338 -**Package Includes**:2235 +**Package includes**: 2339 2339 2340 -* LT-22222-L I/O Controller x 12341 -* StickAntennaforLoRaRFpartx12342 -* Bracket forcontrollerx12343 -* 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 2344 2344 2345 2345 **Dimension and weight**: 2346 2346 2347 2347 * Device Size: 13.5 x 7 x 3 cm 2348 -* Device Weight: 105g 2245 +* Device Weight: 105 g 2349 2349 * Package Size / pcs : 14.5 x 8 x 5 cm 2350 -* Weight / pcs : 170g 2247 +* Weight / pcs : 170 g 2351 2351 2352 2352 = 10. Support = 2353 2353 2354 2354 2355 2355 * ((( 2356 -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. 2357 2357 ))) 2358 2358 * ((( 2359 -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]] 2360 2360 2361 - 2362 2362 2363 2363 ))) 2364 2364
- 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