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 (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 3 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -LT-22222-L -- LoRa I /O Controller User Manual1 +LT-22222-L -- LoRa IO Controller User Manual - Content
-
... ... @@ -40,9 +40,7 @@ 40 40 * If there is no public LoRaWAN coverage in your area, you can set up a LoRaWAN gateway, or multiple gateways, and connect them to a LoRaWAN network server to create adequate coverage. Then, register the LT-22222-L I/O controller with this network. 41 41 * Setup your own private LoRaWAN network. 42 42 43 -{{info}} 44 - You can use a LoRaWAN gateway, such as the [[Dragino LG308>>https://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], to expand or create LoRaWAN coverage in your area. 45 -{{/info}} 43 +> You can use a LoRaWAN gateway, such as the Dragino LG308, to expand or create LoRaWAN coverage in your area. 46 46 ))) 47 47 48 48 ((( ... ... @@ -58,13 +58,13 @@ 58 58 * STM32L072xxxx MCU 59 59 * SX1276/78 Wireless Chip 60 60 * Power Consumption: 61 -** Idle: 4mA@12 V59 +** Idle: 4mA@12v 62 62 ** 20dB Transmit: 34mA@12V 63 63 * Operating Temperature: -40 ~~ 85 Degrees, No Dew 64 64 65 65 (% style="color:#037691" %)**Interface for Model: LT22222-L:** 66 66 67 -* 2 x Digital dual direction Input (Detect High/Low signal, Max: 50 V, or 220Vwith optional external resistor)65 +* 2 x Digital dual direction Input (Detect High/Low signal, Max: 50v, or 220v with optional external resistor) 68 68 * 2 x Digital Output (NPN output. Max pull-up voltage 36V,450mA) 69 69 * 2 x Relay Output (5A@250VAC / 30VDC) 70 70 * 2 x 0~~20mA Analog Input (res:0.01mA) ... ... @@ -74,8 +74,8 @@ 74 74 (% style="color:#037691" %)**LoRa Spec:** 75 75 76 76 * Frequency Range: 77 -** Band 1 (HF): 862 ~~ 1020 M Hz78 -** Band 2 (LF): 410 ~~ 528 M Hz75 +** Band 1 (HF): 862 ~~ 1020 Mhz 76 +** Band 2 (LF): 410 ~~ 528 Mhz 79 79 * 168 dB maximum link budget. 80 80 * +20 dBm - 100 mW constant RF output vs. 81 81 * +14 dBm high-efficiency PA. ... ... @@ -94,7 +94,7 @@ 94 94 95 95 == 1.3 Features == 96 96 97 -* LoRaWAN Class A & Class C modes95 +* LoRaWAN Class A & Class C protocol 98 98 * Optional Customized LoRa Protocol 99 99 * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869 100 100 * AT Commands to change parameters ... ... @@ -104,28 +104,45 @@ 104 104 105 105 == 1.4 Applications == 106 106 107 -* Smart buildings &homeautomation108 -* Logistics and supplychainmanagement109 -* Smart metering110 -* Smart agriculture111 -* Smart cities112 -* Smart factory105 +* Smart Buildings & Home Automation 106 +* Logistics and Supply Chain Management 107 +* Smart Metering 108 +* Smart Agriculture 109 +* Smart Cities 110 +* Smart Factory 113 113 112 +== 1.5 Hardware Variants == 114 114 115 -= 2. Assembling the device = 116 116 117 -== 2.1 Connecting the antenna == 115 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %) 116 +|(% style="background-color:#4f81bd; color:white; width:103px" %)**Model**|(% style="background-color:#4f81bd; color:white; width:131px" %)**Photo**|(% style="background-color:#4f81bd; color:white; width:266px" %)**Description** 117 +|(% style="width:103px" %)**LT22222-L**|(% style="width:131px" %)((( 118 +(% style="text-align:center" %) 119 +[[image:image-20230424115112-1.png||height="106" width="58"]] 120 +)))|(% style="width:334px" %)((( 121 +* 2 x Digital Input (Bi-direction) 122 +* 2 x Digital Output 123 +* 2 x Relay Output (5A@250VAC / 30VDC) 124 +* 2 x 0~~20mA Analog Input (res:0.01mA) 125 +* 2 x 0~~30V Analog Input (res:0.01v) 126 +* 1 x Counting Port 127 +))) 118 118 119 - Connectthe LoRa antenna to the antenna connector, **ANT**,** **located on the top rightside of the device, next to the upperscrew terminalblock. Securetheantenna by tightening itclockwise.129 += 2. Assembling the Device = 120 120 121 -{{warning}} 122 -Warning! Do not power on the device without connecting the antenna. 123 -{{/warning}} 131 +== 2.1 What is included in the package? == 124 124 125 - == 2.2Terminals==133 +The package includes the following items: 126 126 127 -The LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 terminals and the lower screw terminal block has 10 terminals. 135 +* 1 x LT-22222-L I/O Controller 136 +* 1 x LoRaWAN antenna matched to the frequency of the LT-22222-L 137 +* 1 x bracket for DIN rail mounting 138 +* 1 x programming cable 128 128 140 +Attach the LoRaWAN antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper terminal block. Secure the antenna by tightening it clockwise. 141 + 142 +== 2.2 Terminals == 143 + 129 129 Upper screw terminal block (from left to right): 130 130 131 131 (% style="width:634px" %) ... ... @@ -152,28 +152,26 @@ 152 152 |(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2 153 153 |(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1 154 154 155 -== 2.3 Powering the device==170 +== 2.3 Powering the LT-22222-L == 156 156 157 -The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect yourpower supply’s positive wire to the VIN and the negative wire to the GND screw terminals. The power indicator**(PWR) LED**will turn on when the device is properly powered.172 +The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect the power supply’s positive wire to the VIN and the negative wire to the GND screw terminals. The power indicator (PWR) LED will turn on when the device is properly powered. 158 158 159 -Once powered, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** The Things Stack. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LED** will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status. 160 160 161 -{{warning}} 162 -We recommend that you power on the LT-22222-L after configuring its registration information with a LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail. 163 -{{/warning}} 164 - 165 - 166 166 [[image:1653297104069-180.png]] 167 167 168 168 169 -= 3. Registeringwith a LoRaWAN NetworkServer=178 += 3. Operation Mode = 170 170 180 +== 3.1 How does it work? == 181 + 171 171 By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode. It supports OTAA (Over-the-Air Activation), the most secure method for activating a device with a LoRaWAN network server. The LT-22222-L comes with device registration information that allows you to register it with a LoRaWAN network, enabling the device to perform OTAA activation with the network server upon initial power-up and after any subsequent reboots. 172 172 173 -After powering on, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** the LoRaWAN network. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LE D** will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status.184 +After powering on, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** the LoRaWAN network. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LE**D will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status. 174 174 175 175 In case you can't set the root key and other identifiers in the network server and must use them from the server, you can use [[AT Commands>>||anchor="H4.UseATCommand"]] to configure them on the device. 176 176 188 +== 3.2 Registering with a LoRaWAN network server == 189 + 177 177 The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network. 178 178 179 179 [[image:image-20220523172350-1.png||height="266" width="864"]] ... ... @@ -188,33 +188,28 @@ 188 188 189 189 === 3.2.2 The Things Stack Sandbox (TTSS) === 190 190 191 -The Things Stack Sandbox was formally called The Things Stack Community Edition. 192 - 193 193 * Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account. 194 -* Create an application with The Things Stack if you do not have one yet. 195 -* Go to your application page and click on the **End devices** in the left menu. 196 -* On the End devices page, click on **+ Register end device**. Two registration options are available: 205 +* Create an application if you do not have one yet. 206 +* Register LT-22222-L with that application. Two registration options are available: 197 197 208 +==== ==== 209 + 198 198 ==== 3.2.2.1 Using the LoRaWAN Device Repository ==== 199 199 212 +* Go to your application and click on the **Register end device** button. 200 200 * On the **Register end device** page: 201 -** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**. 202 -** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists. 203 -*** **End device brand**: Dragino Technology Co., Limited 204 -*** **Model**: LT22222-L I/O Controller 205 -*** **Hardware ver**: Unknown 206 -*** **Firmware ver**: 1.6.0 207 -*** **Profile (Region)**: Select the region that matches your device. 208 -** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 214 +** Select the option **Select the end device in the LoRaWAN Device Repository**. 215 +** Choose the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)**. 216 +** Select the **Frequency plan** that matches your device. 209 209 210 210 [[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]] 211 211 212 212 213 -* Register end device page continued...214 -** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network'.215 -** In the **DevEUI**field,enterthe **DevEUI**.216 -** In the **AppKey**field, enterthe **AppKey.**217 -** In the **End device ID** field, enter a unique name for your LT-22222-Nwithin this application.221 +* Page continued... 222 +** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. 223 +** Enter the **DevEUI** in the **DevEUI** field. 224 +** Enter the **AppKey** in the **AppKey** field. 225 +** In the **End device ID** field, enter a unique name within this application for your LT-22222-N. 218 218 ** Under **After registration**, select the **View registered end device** option. 219 219 220 220 [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]] ... ... @@ -221,25 +221,25 @@ 221 221 222 222 ==== ==== 223 223 224 -==== 3.2.2.2 Adding device manually ====232 +==== 3.2.2.2 Entering device information manually ==== 225 225 226 226 * On the **Register end device** page: 227 -** Select the option**Enter end device specifies manually**under**Input method**.228 -** Select the **Frequency plan** from the **Frequency plan** dropdown list.229 -** Select the **LoRaWAN version** as **LoRaWAN Specification 1.0.3**230 -** Select the **Regional Parameters version** as** RP001 Regional Parameters 1.0.3 revision A**231 -** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the hiddensection.232 -** Select the option**Over the air activation (OTAA)** under the **Activation mode.**233 -** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.235 +** Select the **Enter end device specifies manually** option as the input method. 236 +** Select the **Frequency plan** that matches your device. 237 +** Select the **LoRaWAN version**. 238 +** Select the **Regional Parameters version**. 239 +** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the section. 240 +** Select **Over the air activation (OTAA)** option under the **Activation mode** 241 +** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities**. 234 234 235 235 [[image:lt-22222-l-manually-p1.png||height="625" width="1000"]] 236 236 237 237 238 -* Register end device page continued...239 -** Enter the**AppEUI** in the **JoinEUI** field and click the **Confirm** button.If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network'240 -** Inhefield,enter the **DevEUI**.241 -** Inhefield, enterthe **AppKey**.242 -** In the **End device ID** field, enter a unique name for your LT-22222-Nwithin this application.246 +* Page continued... 247 +** Enter **AppEUI** in the **JoinEUI** field and click the **Confirm** button. 248 +** Enter **DevEUI** in the **DevEUI** field. 249 +** Enter **AppKey** in the **AppKey** field. 250 +** In the **End device ID** field, enter a unique name within this application for your LT-22222-N. 243 243 ** Under **After registration**, select the **View registered end device** option. 244 244 ** Click the **Register end device** button. 245 245 ... ... @@ -254,15 +254,15 @@ 254 254 255 255 ==== 3.2.2.3 Joining ==== 256 256 257 - On the Device overview page, click on **Live data** tab. The Live data panel for yourdevicewill display.265 +Click on **Live data** in the left navigation. The Live data panel for your application will display. 258 258 259 - Nowpower on your LT-22222-L. It will begin joining The Things Stack. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server. Once successfully joined, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**).267 +Power on your LT-22222-L. It will begin joining The Things Stack LoRaWAN network server. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server. Once successfully joined, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**). 260 260 261 261 262 262 [[image:lt-22222-join-network.png||height="625" width="1000"]] 263 263 264 264 265 -By default, you will receive an uplink data message from thedeviceevery 10 minutes.273 +By default, you will receive an uplink data message every 10 minutes. 266 266 267 267 Click on one of a **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the decode_payload {} JSON object. 268 268 ... ... @@ -271,14 +271,10 @@ 271 271 272 272 If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **End devices** > **LT-22222-L** > **Payload formatters** > **Uplink**. Then select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes. 273 273 274 -{{info}} 275 -The Things Stack provides two levels of payload formatters: application level and device level. The device-level payload formatters **override **the application-level payload formatters. 276 -{{/info}} 277 - 278 278 [[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]] 279 279 280 280 281 -== 3.3 Work Modes and Uplink Payload formats == 285 +== 3.3 Work Modes and their Uplink Payload formats == 282 282 283 283 284 284 The LT-22222-L has 5 **work modes**. It also has an interrupt/trigger mode for different types of applications that can be used together with any work mode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands. ... ... @@ -302,12 +302,8 @@ 302 302 ((( 303 303 This is the default mode. 304 304 305 -The uplink payload is 11 bytes long. 309 +The uplink payload is 11 bytes long. (% style="display:none" wfd-invisible="true" %) 306 306 307 -(% style="color:red" %)**Note:The maximum count depends on the bytes it is. 308 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 309 -It starts counting again when it reaches the maximum value.**(% style="display:none" wfd-invisible="true" %) 310 - 311 311 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 312 312 |(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1** 313 313 |Value|((( ... ... @@ -377,10 +377,6 @@ 377 377 ((( 378 378 The uplink payload is 11 bytes long. 379 379 380 -(% style="color:red" %)**Note:The maximum count depends on the bytes it is. 381 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 382 -It starts counting again when it reaches the maximum value.** 383 - 384 384 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 385 385 |(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**4**|(% style="background-color:#4f81bd; color:white" %)**4**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1** 386 386 |Value|COUNT1|COUNT2 |DIDORO*|((( ... ... @@ -445,9 +445,6 @@ 445 445 446 446 === 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI === 447 447 448 -(% style="color:red" %)**Note: The maximum count depends on the bytes it is. 449 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 450 -It starts counting again when it reaches the maximum value.** 451 451 452 452 **LT22222-L**: In this mode, the DI1 is used as a counting pin. 453 453 ... ... @@ -498,11 +498,7 @@ 498 498 499 499 === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting === 500 500 501 -(% style="color:red" %)**Note:The maximum count depends on the bytes it is. 502 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 503 -It starts counting again when it reaches the maximum value.** 504 504 505 - 506 506 ((( 507 507 **LT22222-L**: In this mode, the DI1 is used as a counting pin. 508 508 ))) ... ... @@ -555,23 +555,19 @@ 555 555 ((( 556 556 **In addition to that, below are the commands for AVI1 Counting:** 557 557 558 -(% style="color:blue" %)**AT+SETCNT=3,60 547 +(% style="color:blue" %)**AT+SETCNT=3,60**(%%)** (Sets AVI Count to 60)** 559 559 560 -(% style="color:blue" %)**AT+VOLMAX=20000 549 +(% style="color:blue" %)**AT+VOLMAX=20000**(%%)** (If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 561 561 562 -(% style="color:blue" %)**AT+VOLMAX=20000,0 551 +(% style="color:blue" %)**AT+VOLMAX=20000,0**(%%)** (If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)** 563 563 564 -(% style="color:blue" %)**AT+VOLMAX=20000,1 553 +(% style="color:blue" %)**AT+VOLMAX=20000,1**(%%)** (If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 565 565 ))) 566 566 567 567 568 568 === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI === 569 569 570 -(% style="color:red" %)**Note:The maximum count depends on the bytes it is. 571 -The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 572 -It starts counting again when it reaches the maximum value.** 573 573 574 - 575 575 **LT22222-L**: In this mode, the DI1 is used as a counting pin. 576 576 577 577 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) ... ... @@ -629,17 +629,15 @@ 629 629 630 630 For example, if you configured the following commands: 631 631 632 -* **AT+MOD=1 ** **~-~->** The defaultwork mode617 +* **AT+MOD=1 ** **~-~->** The normal working mode 633 633 * **AT+ADDMOD6=1** **~-~->** Enable trigger mode 634 634 635 635 The LT-22222-L will continuously monitor AV1, AV2, AC1, and AC2 every 5 seconds. LT will send uplink packets in two cases: 636 636 637 637 1. Periodically uplink (Based on TDC time). The payload is the same as in normal mode (MOD=1 for the commands above). These are (% style="color:#4f81bd" %)**unconfirmed**(%%) uplinks. 638 -1. ((( 639 -Trigger uplink when the trigger condition is met. LT will send two packets in this case. The first uplink uses the payload specified in trigger mode (MOD=6). The second packet uses the normal mode payload (MOD=1 as set above). Both are (% style="color:#4f81bd" %)**confirmed uplinks.** 640 -))) 623 +1. Trigger uplink when the trigger condition is met. LT will send two packets in this case. The first uplink uses the payload specified in trigger mode (MOD=6). The second packet uses the normal mode payload (MOD=1 as set above). Both are (% style="color:#4f81bd" %)**CONFIRMED uplinks.** 641 641 642 -(% style="color:#037691" %)**AT Command sto set Trigger Condition**:625 +(% style="color:#037691" %)**AT Command to set Trigger Condition**: 643 643 644 644 (% style="color:#4f81bd" %)**Trigger based on voltage**: 645 645 ... ... @@ -811,68 +811,50 @@ 811 811 ))) 812 812 813 813 814 -== 3.4 Configure LT -22222-Lvia AT Commands or Downlinks ==797 +== 3.4 Configure LT via AT Commands or Downlinks == 815 815 799 + 816 816 ((( 817 - Youcan configure LT-22222-LI/O Controller via AT Commands or LoRaWAN Downlinks.801 +User can configure LT I/O Controller via AT Commands or LoRaWAN Downlinks. 818 818 ))) 819 819 820 820 ((( 821 821 ((( 822 -There are two tytes ofcommands:806 +There are two kinds of Commands: 823 823 ))) 824 824 ))) 825 825 826 -* (% style="color:blue" %)**Common commands**(%%):810 +* (% style="color:blue" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.5.4, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]] 827 827 828 -* (% style="color:blue" %)**Sensor -relatedcommands**(%%):812 +* (% style="color:blue" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L. User can see these commands below: 829 829 830 -=== 3.4.1 Common commands ===814 +=== 3.4.1 Common Commands === 831 831 832 832 ((( 833 -These a re available foreachsensorsandinclude actionssuch as changing the:[[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]s.817 +These commands should be available for all Dragino sensors, such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]. 834 834 ))) 835 835 836 -=== 3.4.2 Sensor-related commands === 837 837 838 - Thesecommandsarespecially designed fortheLT-22222-L. Commands can be sentto theeviceusing options such as an AT commandor a LoRaWAN downlink payload.821 +=== 3.4.2 Sensor related commands === 839 839 840 840 ==== 3.4.2.1 Set Transmit Interval ==== 841 841 842 842 Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes. 843 843 844 -(% style="color:#037691" %)**AT command** 827 +* (% style="color:#037691" %)**AT command:** 845 845 846 -(% style="width:500px" %) 847 -|**Command**|AT+TDC<time> 848 -|**Response**| 849 -|**Parameters**|<time> uplink interval is in milliseconds 850 -|**Example**|((( 851 -AT+TDC=30000 829 +(% style="color:blue" %)**AT+TDC=N** 852 852 853 -Sets the uplink interval to 30,000 milliseconds (30 seconds) 854 -))) 831 +where N is the time in milliseconds. 855 855 856 - (% style="color:#037691"%)**Downlinkpayload**833 +**Example: **AT+TDC=30000. This will set the uplink interval to 30 seconds 857 857 858 -(% style="width:500px" %) 859 -|**Payload**|((( 860 -<prefix><time> 861 -))) 862 -|**Parameters**|((( 863 -<prefix> 0x01 864 864 865 -<time> uplink interval is in milliseconds, represented by 3 bytes in hexadecimal. 866 -))) 867 -|**Example**|((( 868 -01 **00 75 30** 836 +* (% style="color:#037691" %)**Downlink payload (prefix 0x01):** 869 869 870 - Setsthe uplink intervalto 30,000milliseconds(30seconds)838 +(% style="color:blue" %)**0x01 aa bb cc **(%%)** ~/~/ Same as AT+TDC=0x(aa bb cc)** 871 871 872 -Conversion: 30000 (dec) = 00 75 30 (hex) 873 873 874 -See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]] 875 -))) 876 876 877 877 ==== 3.4.2.2 Set the Work Mode (AT+MOD) ==== 878 878 ... ... @@ -894,8 +894,8 @@ 894 894 895 895 ==== 3.4.2.3 Poll an uplink ==== 896 896 897 -Requests the device to send an uplink. 898 898 863 +Asks the device to send an uplink. 899 899 900 900 * (% style="color:#037691" %)**AT command:**(%%) There is no AT Command to poll uplink 901 901 ... ... @@ -909,6 +909,7 @@ 909 909 910 910 ==== 3.4.2.4 Enable/Disable Trigger Mode ==== 911 911 877 + 912 912 Enable or disable the trigger mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]). 913 913 914 914 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0** ... ... @@ -926,8 +926,9 @@ 926 926 927 927 ==== 3.4.2.5 Poll trigger settings ==== 928 928 929 -Polls the trigger settings. 930 930 896 +Polls the trigger settings 897 + 931 931 * (% style="color:#037691" %)**AT Command:** 932 932 933 933 There is no AT Command for this feature. ... ... @@ -938,10 +938,11 @@ 938 938 939 939 940 940 941 -==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as atrigger ====908 +==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ==== 942 942 943 -Enable or disable DI1/DI2/DI2 as a trigger. 944 944 911 +Enable or Disable DI1/DI2/DI2 as trigger, 912 + 945 945 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >** 946 946 947 947 **Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) ... ... @@ -953,10 +953,11 @@ 953 953 954 954 955 955 956 -==== 3.4.2.7 Trigger1 – Set DI or DI3 as atrigger ====924 +==== 3.4.2.7 Trigger1 – Set DI1 or DI3 as trigger ==== 957 957 958 -Sets DI1 or DI3 (for LT-33222-L) as a trigger. 959 959 927 +Set DI1 or DI3(for LT-33222-L) trigger. 928 + 960 960 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG1=a,b** 961 961 962 962 (% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1). ... ... @@ -971,10 +971,12 @@ 971 971 (% style="color:blue" %)**0x09 01 aa bb cc ** (%%) ~/~/ same as AT+TRIG1=aa,0x(bb cc) 972 972 973 973 974 -==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ==== 975 975 976 -Set sDI2 asatrigger.944 +==== 3.4.2.8 Trigger2 – Set DI2 as trigger ==== 977 977 946 + 947 +Sets DI2 trigger. 948 + 978 978 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b** 979 979 980 980 (% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1). ... ... @@ -989,10 +989,12 @@ 989 989 (% style="color:blue" %)**0x09 02 aa bb cc ** (%%)~/~/ same as AT+TRIG2=aa,0x(bb cc) 990 990 991 991 992 -==== 3.4.2.9 Trigger – Set AC (current) as a trigger ==== 993 993 994 - Setsthecurrent triggerbasedon the ACport.See[[triggermode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]964 +==== 3.4.2.9 Trigger – Set AC (current) as trigger ==== 995 995 966 + 967 +Set current trigger , base on AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 968 + 996 996 * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ACLIM** 997 997 998 998 * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 01 )** ... ... @@ -1003,8 +1003,9 @@ 1003 1003 1004 1004 ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ==== 1005 1005 1006 -Sets the current trigger based on the AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1007 1007 980 +Set current trigger , base on AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 981 + 1008 1008 * (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+AVLIM **(%%)** See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]** 1009 1009 1010 1010 * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 00 )** ... ... @@ -1012,8 +1012,10 @@ 1012 1012 (% style="color:blue" %)**0x AA 00 aa bb cc dd ee ff gg hh ** (%%) ~/~/ same as AT+AVLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1013 1013 1014 1014 989 + 1015 1015 ==== 3.4.2.11 Trigger – Set minimum interval ==== 1016 1016 992 + 1017 1017 Sets AV and AC trigger minimum interval. Device won't response to the second trigger within this set time after the first trigger. 1018 1018 1019 1019 * (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+ATDC=5 ** ~/~/ (%%)Device won't response the second trigger within 5 minute after the first trigger. ... ... @@ -1030,7 +1030,6 @@ 1030 1030 1031 1031 ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ==== 1032 1032 1033 -Controls the digital outputs DO1, DO2, and DO3 1034 1034 1035 1035 * (% style="color:#037691" %)**AT Command** 1036 1036 ... ... @@ -1408,25 +1408,25 @@ 1408 1408 1409 1409 == 3.5 Integrating with ThingsEye.io == 1410 1410 1411 -The Things Stack application upportsintegrationwith ThingsEye.io. Once integrated, ThingsEye.ioacts as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.1386 +The Things Stack applications can be integrated with ThingsEye.io. Once integrated, ThingsEye.io works as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic. 1412 1412 1413 -=== 3.5.1 Configuring The Things Stack === 1388 +=== 3.5.1 Configuring MQTT Connection Information with The Things Stack Sandbox === 1414 1414 1415 -We use The Things Stack Sandbox in thi sexample:1390 +We use The Things Stack Sandbox for demonstating the configuration but other 1416 1416 1417 -* In **The Things Stack Sandbox**, go tothefor the LT-22222-L you added.1418 -* Select **MQTT** under **Integrations** in the left menu.1419 -* In the **Connection information **section, under **Connection credentials**, The Things Stack displays an auto-generated**username**. You can use it or provide a new one.1420 -* Click the **Generate new API key** button to generate a password. You canviewit by clicking on the **visibility toggle/eye**icon. The API key works as the password.1392 +* In **The Things Stack Sandbox**, select your application under **Applications**. 1393 +* Select **MQTT** under **Integrations**. 1394 +* In the **Connection information **section, for **Username**, The Things Stack displays an auto-generated username. You can use it or provide a new one. 1395 +* For the **Password**, click the **Generate new API key** button to generate a password. You can see it by clicking on the **eye** button. The API key works as the password. 1421 1421 1422 -{{info}} 1423 -The username and password (API key) you created here are required in the next section. 1424 -{{/info}} 1397 +NOTE. The username and password (API key) you created here are required in the next section. 1425 1425 1426 1426 [[image:tts-mqtt-integration.png||height="625" width="1000"]] 1427 1427 1428 1428 === 3.5.2 Configuring ThingsEye.io === 1429 1429 1403 +This section guides you on how to create an integration in ThingsEye to connect with The Things Stack MQTT server. 1404 + 1430 1430 * Login to your [[ThingsEye.io >>https://thingseye.io]]account. 1431 1431 * Under the **Integrations center**, click **Integrations**. 1432 1432 * Click the **Add integration** button (the button with the **+** symbol). ... ... @@ -1463,9 +1463,9 @@ 1463 1463 **Downlink data converter (this is an optional step):** 1464 1464 1465 1465 * Click the **Create new** button if it is not selected by default. 1466 -* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name .1441 +* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name 1467 1467 * Click the **JavaScript** button. 1468 -* Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Downlink_Converter.js]].1443 +* Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found here. 1469 1469 * Click the **Next** button. You will be navigated to the **Connection** tab. 1470 1470 1471 1471 [[image:thingseye-io-step-4.png||height="625" width="1000"]] ... ... @@ -1475,7 +1475,7 @@ 1475 1475 1476 1476 * Choose **Region** from the **Host type**. 1477 1477 * Enter the **cluster** of your **The Things Stack** in the **Region** textbox. You can find the cluster in the url (e.g., https:~/~/**eu1**.cloud.thethings.network/...). 1478 -* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The **username**and**password**can be found on the MQTT integration page of your The Things Stack account (see Configuring The Things Stack).1453 +* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The username and password can be found on the MQTT integration page of your The Things Stack account (see Configuring MQTT Connection information with The Things Stack Sandbox). 1479 1479 * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**. 1480 1480 1481 1481 [[image:message-1.png]] ... ... @@ -1494,7 +1494,7 @@ 1494 1494 1495 1495 **Viewing integration details**: 1496 1496 1497 -Click on your integration from the list. The **Integration details**window will appear with the**Details**tab selected. The**Details**tab shows all the settings you have provided for this integration.1472 +Click on your integration from the list. The Integration details window will appear with the Details tab selected. The Details tab shows all the settings you have provided for this integration. 1498 1498 1499 1499 [[image:integration-details.png||height="686" width="1000"]] 1500 1500 ... ... @@ -1501,25 +1501,24 @@ 1501 1501 1502 1502 If you want to edit the settings you have provided, click on the **Toggle edit mode** button. Once you have done click on the **Apply changes **button. 1503 1503 1504 -{{info}} 1505 -See also ThingsEye documentation. 1506 -{{/info}} 1479 +Note: See also ThingsEye documentation. 1507 1507 1481 + 1508 1508 **Viewing events:** 1509 1509 1510 -Th e **Events**tab displays all the uplink messages from the LT-22222-L.1484 +This tab displays all the uplink messages from the LT-22222-L. 1511 1511 1486 +* Click on the **Events **tab. 1512 1512 * Select **Debug **from the **Event type** dropdown. 1513 1513 * Select the** time frame** from the **time window**. 1514 1514 1515 -[ [image:thingseye-events.png||height="686"width="1000"]]1490 +[insert image] 1516 1516 1492 +- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message. 1517 1517 1518 - * To view the JSON payload of a message, click on the three dots(...)in the Message column of the desired message.1494 +[insert image] 1519 1519 1520 -[[image:thingseye-json.png||width="1000"]] 1521 1521 1522 - 1523 1523 **Deleting the integration**: 1524 1524 1525 1525 If you want to delete this integration, click the **Delete integratio**n button. ... ... @@ -1738,11 +1738,10 @@ 1738 1738 1739 1739 == 3.7 LEDs Indicators == 1740 1740 1741 -The table below lists the behavior of LED indicators for each port function. 1742 1742 1743 1743 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) 1744 1744 |(% style="background-color:#4f81bd; color:white; width:50px" %)**LEDs**|(% style="background-color:#4f81bd; color:white; width:460px" %)**Feature** 1745 -|**PWR**|Always on whenthere is power1718 +|**PWR**|Always on if there is power 1746 1746 |**TX**|((( 1747 1747 ((( 1748 1748 Device boot: TX blinks 5 times. ... ... @@ -1749,7 +1749,7 @@ 1749 1749 ))) 1750 1750 1751 1751 ((( 1752 -Successful network join: TXremainsON for 5 seconds.1725 +Successful join network: TX ON for 5 seconds. 1753 1753 ))) 1754 1754 1755 1755 ((( ... ... @@ -1756,7 +1756,7 @@ 1756 1756 Transmit a LoRa packet: TX blinks once 1757 1757 ))) 1758 1758 ))) 1759 -|**RX**|RX blinks once when a packet is received.1732 +|**RX**|RX blinks once when receiving a packet. 1760 1760 |**DO1**|For LT-22222-L: ON when DO1 is low, OFF when DO1 is high 1761 1761 |**DO2**|For LT-22222-L: ON when DO2 is low, OFF when DO2 is high 1762 1762 |**DI1**|((( ... ... @@ -1988,14 +1988,14 @@ 1988 1988 1989 1989 == 5.1 Counting how many objects pass through the flow Line == 1990 1990 1991 -See [[How to set up to setup counting for objects passing through the flow line>>How to set up to count objects pass in flow line]]? 1992 1992 1965 +Reference Link: [[How to set up to setup counting for objects passing through the flow line>>How to set up to count objects pass in flow line]]? 1993 1993 1967 + 1994 1994 = 6. FAQ = 1995 1995 1996 1996 This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly. 1997 1997 1998 - 1999 1999 == 6.1 How to update the firmware? == 2000 2000 2001 2001 Dragino frequently releases firmware updates for the LT-22222-L. ... ... @@ -2052,6 +2052,8 @@ 2052 2052 ((( 2053 2053 ((( 2054 2054 == 6.2 How to change the LoRaWAN frequency band/region? == 2028 + 2029 + 2055 2055 ))) 2056 2056 ))) 2057 2057 ... ... @@ -2063,6 +2063,8 @@ 2063 2063 2064 2064 2065 2065 == 6.3 How to setup LT to work with a Single Channel Gateway, such as LG01/LG02? == 2041 + 2042 + 2066 2066 ))) 2067 2067 2068 2068 ((( ... ... @@ -2133,11 +2133,13 @@ 2133 2133 2134 2134 == 6.4 How to change the uplink interval? == 2135 2135 2113 + 2136 2136 Please see this link: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/]] 2137 2137 2138 2138 2139 2139 == 6.5 Can I see the counting event in the serial output? == 2140 2140 2119 + 2141 2141 ((( 2142 2142 You can run the AT command AT+DEBUG to view the counting event in the serial output. If the firmware is too old and doesn’t support AT+DEBUG, update to the latest firmware first. 2143 2143 ... ... @@ -2144,14 +2144,14 @@ 2144 2144 2145 2145 == 6.6 Can I use point-to-point communication with LT-22222-L? == 2146 2146 2147 -Yes, you can. Please refer to the [[Point-to-Point Communication of LT-22222-L>>https://wiki.dragino.com/xwiki/bin/view/Main/%20Point%20to%20Point%20Communication%20of%20LT-22222-L/]] page. The firmware that supports point-to-point communication can be found [[here>>https://github.com/dragino/LT-22222-L/releases]]. 2148 2148 2149 - 2127 +Yes, you can. Please refer to the [[Point-to-Point Communication of LT-22222-L>>https://wiki.dragino.com/xwiki/bin/view/Main/%20Point%20to%20Point%20Communication%20of%20LT-22222-L/]] page. The firmware that supports point-to-point communication can be found [[here>>https://github.com/dragino/LT-22222-L/releases]]. 2150 2150 ))) 2151 2151 2152 2152 ((( 2153 2153 == 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? == 2154 2154 2133 + 2155 2155 * If the device is not properly shut down and is directly powered off. 2156 2156 * It will default to a power-off state. 2157 2157 * In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory. ... ... @@ -2159,6 +2159,7 @@ 2159 2159 2160 2160 == 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? == 2161 2161 2141 + 2162 2162 The LT-22222-L's built-in relay is Normally Open (NO). You can use an external relay to achieve a Normally Closed (NC) configuration. The circuit diagram is shown below: 2163 2163 2164 2164 ... ... @@ -2167,24 +2167,24 @@ 2167 2167 2168 2168 == 6.9 Can the LT-22222-L save the RO state? == 2169 2169 2150 + 2170 2170 The firmware version must be at least 1.6.0. 2171 2171 2172 2172 2173 2173 == 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? == 2174 2174 2156 + 2175 2175 It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose. 2176 2176 2177 2177 2178 2178 = 7. Troubleshooting = 2179 - 2180 -This section provides some known troubleshooting tips. 2181 - 2182 - 2183 2183 ))) 2184 2184 2185 2185 ((( 2186 2186 ((( 2187 2187 == 7.1 Downlink isn't working. How can I solve this? == 2166 + 2167 + 2188 2188 ))) 2189 2189 ))) 2190 2190 ... ... @@ -2196,6 +2196,8 @@ 2196 2196 2197 2197 2198 2198 == 7.2 Having trouble uploading an image? == 2179 + 2180 + 2199 2199 ))) 2200 2200 2201 2201 ((( ... ... @@ -2206,6 +2206,8 @@ 2206 2206 2207 2207 2208 2208 == 7.3 Why can't I join TTN in the US915 /AU915 bands? == 2191 + 2192 + 2209 2209 ))) 2210 2210 2211 2211 ((( ... ... @@ -2215,6 +2215,7 @@ 2215 2215 2216 2216 == 7.4 Why can the LT-22222-L perform Uplink normally, but cannot receive Downlink? == 2217 2217 2202 + 2218 2218 The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue. 2219 2219 Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]] 2220 2220 ... ... @@ -2221,6 +2221,7 @@ 2221 2221 2222 2222 = 8. Ordering information = 2223 2223 2209 + 2224 2224 (% style="color:#4f81bd" %)**LT-22222-L-XXX:** 2225 2225 2226 2226 (% style="color:#4f81bd" %)**XXX:** ... ... @@ -2237,12 +2237,13 @@ 2237 2237 2238 2238 = 9. Packing information = 2239 2239 2226 + 2240 2240 **Package includes**: 2241 2241 2242 -* 1 xLT-22222-L I/O Controller2243 -* 1x LoRa antennamatched to thefrequencyoftheLT-22222-L2244 -* 1 x bracket forDIN rail mounting2245 -* 1 x3.5mmprogramming cable2229 +* LT-22222-L I/O Controller x 1 2230 +* Stick Antenna for LoRa RF part x 1 2231 +* Bracket for controller x1 2232 +* 3.5mm Programming cable x 1 2246 2246 2247 2247 **Dimension and weight**: 2248 2248 ... ... @@ -2253,6 +2253,7 @@ 2253 2253 2254 2254 = 10. Support = 2255 2255 2243 + 2256 2256 * ((( 2257 2257 Support is available Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different time zones, we cannot offer live support. However, your questions will be answered as soon as possible within the aforementioned schedule. 2258 2258 ))) ... ... @@ -2264,6 +2264,7 @@ 2264 2264 2265 2265 = 11. Reference = 2266 2266 2255 + 2267 2267 * LT-22222-L: [[http:~~/~~/www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html>>url:http://www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html]] 2268 2268 * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]] 2269 2269 * [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]
- lt-22222-l-abp.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -321.4 KB - Content
- thingseye-json.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -554.8 KB - Content
- usb-ttl-programming.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -462.9 KB - Content