Changes for page LT-22222-L -- LoRa I/O Controller User Manual
Last modified by Mengting Qiu on 2025/06/04 18:42
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (1 modified, 3 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. pradeeka1 +XWiki.Xiaoling - Content
-
... ... @@ -21,6 +21,7 @@ 21 21 22 22 == 1.1 What is the LT-22222-L I/O Controller? == 23 23 24 + 24 24 ((( 25 25 ((( 26 26 {{info}} ... ... @@ -54,8 +54,10 @@ 54 54 (% class="wikigeneratedid" %) 55 55 [[image:lorawan-nw.jpg||height="354" width="900"]] 56 56 58 + 57 57 == 1.2 Specifications == 58 58 61 + 59 59 (% style="color:#037691" %)**Hardware System:** 60 60 61 61 * STM32L072xxxx MCU ... ... @@ -97,6 +97,7 @@ 97 97 98 98 == 1.3 Features == 99 99 103 + 100 100 * LoRaWAN Class A & Class C modes 101 101 * Optional Customized LoRa Protocol 102 102 * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869 ... ... @@ -107,6 +107,7 @@ 107 107 108 108 == 1.4 Applications == 109 109 114 + 110 110 * Smart buildings & home automation 111 111 * Logistics and supply chain management 112 112 * Smart metering ... ... @@ -116,11 +116,13 @@ 116 116 117 117 == 1.5 Hardware Variants == 118 118 119 -(% style="width:524px" %) 120 -|(% style="width:94px" %)**Model**|(% style="width:98px" %)**Photo**|(% style="width:329px" %)**Description** 121 -|(% style="width:94px" %)**LT33222-L**|(% style="width:98px" %)((( 122 - 123 -)))|(% style="width:329px" %)((( 124 + 125 +(% border="1" cellspacing="3" style="width:510px" %) 126 +|(% style="background-color:#4f81bd; color:white; width:94px" %)**Model**|(% style="background-color:#4f81bd; color:white; width:172px" %)**Photo**|(% style="background-color:#4f81bd; color:white; width:244px" %)**Description** 127 +|(% style="width:94px" %)**LT-22222-L**|(% style="width:172px" %)((( 128 +(% style="text-align:center" %) 129 +[[image:lt33222-l.jpg||height="110" width="95"]] 130 +)))|(% style="width:256px" %)((( 124 124 * 2 x Digital Input (Bi-direction) 125 125 * 2 x Digital Output 126 126 * 2 x Relay Output (5A@250VAC / 30VDC) ... ... @@ -133,6 +133,7 @@ 133 133 134 134 == 2.1 Connecting the antenna == 135 135 143 + 136 136 Connect the LoRa antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper screw terminal block. Secure the antenna by tightening it clockwise. 137 137 138 138 {{warning}} ... ... @@ -139,42 +139,46 @@ 139 139 **Warning! Do not power on the device without connecting the antenna.** 140 140 {{/warning}} 141 141 150 + 142 142 == 2.2 Terminals == 143 143 153 + 144 144 The LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals. 145 145 146 146 **Upper screw terminal block (from left to right):** 147 147 148 -(% style="width: 634px" %)149 -|=(% style="width: 295px;" %)Screw Terminal|=(% style="width:338px;" %)Function150 -|(% style="width: 295px" %)GND|(% style="width:338px" %)Ground151 -|(% style="width: 295px" %)VIN|(% style="width:338px" %)Input Voltage152 -|(% style="width: 295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2153 -|(% style="width: 295px" %)AVI1|(% style="width:338px" %)Analog Voltage Input Terminal 1154 -|(% style="width: 295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2155 -|(% style="width: 295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1158 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:381px" %) 159 +|=(% style="width: 139px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 242px;background-color:#4f81bd;color:white" %)Function 160 +|(% style="width:139px" %)GND|(% style="width:242px" %)Ground 161 +|(% style="width:139px" %)VIN|(% style="width:242px" %)Input Voltage 162 +|(% style="width:139px" %)AVI2|(% style="width:242px" %)Analog Voltage Input Terminal 2 163 +|(% style="width:139px" %)AVI1|(% style="width:242px" %)Analog Voltage Input Terminal 1 164 +|(% style="width:139px" %)ACI2|(% style="width:242px" %)Analog Current Input Terminal 2 165 +|(% style="width:139px" %)ACI1|(% style="width:242px" %)Analog Current Input Terminal 1 156 156 157 157 **Lower screw terminal block (from left to right):** 158 158 159 -(% style="width: 633px" %)160 -|=(% style="width: 2 96px;" %)Screw Terminal|=(% style="width:334px;" %)Function161 -|(% style="width:2 96px" %)RO1-2|(% style="width:334px" %)Relay Output 1162 -|(% style="width:2 96px" %)RO1-1|(% style="width:334px" %)Relay Output 1163 -|(% style="width:2 96px" %)RO2-2|(% style="width:334px" %)Relay Output 2164 -|(% style="width:2 96px" %)RO2-1|(% style="width:334px" %)Relay Output 2165 -|(% style="width:2 96px" %)DI2+|(% style="width:334px" %)Digital Input 2166 -|(% style="width:2 96px" %)DI2-|(% style="width:334px" %)Digital Input 2167 -|(% style="width:2 96px" %)DI1+|(% style="width:334px" %)Digital Input 1168 -|(% style="width:2 96px" %)DI1-|(% style="width:334px" %)Digital Input 1169 -|(% style="width:2 96px" %)DO2|(% style="width:334px" %)Digital Output 2170 -|(% style="width:2 96px" %)DO1|(% style="width:334px" %)Digital Output 1169 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:253px" %) 170 +|=(% style="width: 125px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 128px;background-color:#4f81bd;color:white" %)Function 171 +|(% style="width:125px" %)RO1-2|(% style="width:128px" %)Relay Output 1 172 +|(% style="width:125px" %)RO1-1|(% style="width:128px" %)Relay Output 1 173 +|(% style="width:125px" %)RO2-2|(% style="width:128px" %)Relay Output 2 174 +|(% style="width:125px" %)RO2-1|(% style="width:128px" %)Relay Output 2 175 +|(% style="width:125px" %)DI2+|(% style="width:128px" %)Digital Input 2 176 +|(% style="width:125px" %)DI2-|(% style="width:128px" %)Digital Input 2 177 +|(% style="width:125px" %)DI1+|(% style="width:128px" %)Digital Input 1 178 +|(% style="width:125px" %)DI1-|(% style="width:128px" %)Digital Input 1 179 +|(% style="width:125px" %)DO2|(% style="width:128px" %)Digital Output 2 180 +|(% style="width:125px" %)DO1|(% style="width:128px" %)Digital Output 1 171 171 182 + 172 172 == 2.3 Connecting LT-22222-L to a Power Source == 173 173 185 + 174 174 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 176 176 {{warning}} 177 -**We recommend that you power on the LT-22222-L after configuring its registration informationwithaLoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.**189 +**We recommend that you power on the LT-22222-L after adding its registration information to the LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.** 178 178 {{/warning}} 179 179 180 180 ... ... @@ -183,11 +183,13 @@ 183 183 184 184 = 3. Registering LT-22222-L with a LoRaWAN Network Server = 185 185 198 + 186 186 The LT-22222-L supports both OTAA (Over-the-Air Activation) and ABP (Activation By Personalization) methods to activate with a LoRaWAN Network Server. However, OTAA is the most secure method for activating a device with a LoRaWAN Network Server. OTAA regenerates session keys upon initial registration and regenerates new session keys after any subsequent reboots. By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode. 187 187 188 188 189 189 === 3.2.1 Prerequisites === 190 190 204 + 191 191 The LT-22222-L comes with device registration information such as DevEUI, AppEUI, and AppKey that allows you to register it with a LoRaWAN network. These registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference. 192 192 193 193 [[image:image-20230425173427-2.png||height="246" width="530"]] ... ... @@ -198,8 +198,10 @@ 198 198 199 199 The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers. 200 200 215 + 201 201 === 3.2.2 The Things Stack === 202 202 218 + 203 203 This section guides you through how to register your LT-22222-L with The Things Stack Sandbox. 204 204 205 205 {{info}} ... ... @@ -210,7 +210,7 @@ 210 210 The network diagram below illustrates the connection between the LT-22222-L and The Things Stack, as well as how the data can be integrated with the ThingsEye IoT platform. 211 211 212 212 213 -[[image:dragino-lorawan-nw-lt-22222-n.jpg]] 229 +[[image:dragino-lorawan-nw-lt-22222-n.jpg||height="374" width="1400"]] 214 214 215 215 {{info}} 216 216 You can use a LoRaWAN gateway, such as the [[Dragino LPS8N>>https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]], to expand or create LoRaWAN coverage in your area. ... ... @@ -219,6 +219,7 @@ 219 219 220 220 ==== 3.2.2.1 Setting up ==== 221 221 238 + 222 222 * Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet. 223 223 * Log in to your The Things Stack Sandbox account. 224 224 * Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs). ... ... @@ -225,8 +225,10 @@ 225 225 * Go to your application's page and click on the **End devices** in the left menu. 226 226 * On the End devices page, click on **+ Register end device**. Two registration options are available: 227 227 245 + 228 228 ==== 3.2.2.2 Using the LoRaWAN Device Repository ==== 229 229 248 + 230 230 * On the **Register end device** page: 231 231 ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**. 232 232 ** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists. ... ... @@ -237,7 +237,7 @@ 237 237 *** **Profile (Region)**: Select the region that matches your device. 238 238 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 239 239 240 -[[image:lt-22222-l-dev-repo-reg-p1.png ||height="625" width="1000"]]259 +[[image:lt-22222-l-dev-repo-reg-p1.png]] 241 241 242 242 243 243 * Register end device page continued... ... ... @@ -247,11 +247,12 @@ 247 247 ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. 248 248 ** Under **After registration**, select the **View registered end device** option. 249 249 250 -[[image:lt-22222-l-dev-repo-reg-p2.png ||height="625" width="1000"]]269 +[[image:lt-22222-l-dev-repo-reg-p2.png]] 251 251 252 252 253 253 ==== 3.2.2.3 Adding device manually ==== 254 254 274 + 255 255 * On the **Register end device** page: 256 256 ** Select the option **Enter end device specifies manually** under **Input method**. 257 257 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. ... ... @@ -261,7 +261,7 @@ 261 261 ** Select the option **Over the air activation (OTAA)** under the **Activation mode.** 262 262 ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list. 263 263 264 -[[image:lt-22222-l-manually-p1.png ||height="625" width="1000"]]284 +[[image:lt-22222-l-manually-p1.png]] 265 265 266 266 267 267 * Register end device page continued... ... ... @@ -272,23 +272,24 @@ 272 272 ** Under **After registration**, select the **View registered end device** option. 273 273 ** Click the **Register end device** button. 274 274 275 -[[image:lt-22222-l-manually-p2.png ||height="625" width="1000"]]295 +[[image:lt-22222-l-manually-p2.png]] 276 276 277 277 278 278 You will be navigated to the **Device overview** page. 279 279 280 280 281 -[[image:lt-22222-device-overview.png ||height="625" width="1000"]]301 +[[image:lt-22222-device-overview.png]] 282 282 283 283 284 284 ==== 3.2.2.4 Joining ==== 285 285 306 + 286 286 On the Device's page, click on **Live data** tab. The Live data panel for your device will display. 287 287 288 288 Now power on your LT-22222-L. 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 network server. The **TX LED** will be on for **5 seconds** after joining the network. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server. 289 289 290 290 291 -[[image:lt-22222-join -network.png||height="625" width="1000"]]312 +[[image:lt-22222-l-joining.png]] 292 292 293 293 294 294 ==== 3.2.2.5 Uplinks ==== ... ... @@ -307,11 +307,18 @@ 307 307 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. 308 308 {{/info}} 309 309 310 -[[image:lt-22222-ul-payload-fmt.png ||height="686" width="1000"]]331 +[[image:lt-22222-ul-payload-fmt.png]] 311 311 312 312 334 +We also have a payload formatter that resolves some decoding issues present in the Device Repository formatter. You can add it under the Custom JavaScript formatter. It can be found [[here>>https://github.com/dragino/dragino-end-node-decoder/blob/main/LT22222-L/v1.6_decoder_ttn%20.txt]]: 335 + 336 +(% class="wikigeneratedid" %) 337 +[[image:lt-22222-l-js-custom-payload-formatter.png]] 338 + 339 + 313 313 ==== 3.2.2.6 Downlinks ==== 314 314 342 + 315 315 When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**. 316 316 317 317 ... ... @@ -334,8 +334,10 @@ 334 334 335 335 The uplink messages are sent over LoRaWAN FPort=2. By default, an uplink message is sent every 10 minutes. 336 336 365 + 337 337 === 3.3.1 AT+MOD~=1, 2ACI+2AVI === 338 338 368 + 339 339 ((( 340 340 This is the default mode. 341 341 ... ... @@ -408,6 +408,7 @@ 408 408 409 409 MOD = 1 410 410 441 + 411 411 === 3.3.2 AT+MOD~=2, (Double DI Counting) === 412 412 413 413 ... ... @@ -486,6 +486,7 @@ 486 486 487 487 === 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI === 488 488 520 + 489 489 (% style="color:red" %)**Note: The maximum count depends on the bytes it is. 490 490 The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 491 491 It starts counting again when it reaches the maximum value.** ... ... @@ -539,6 +539,7 @@ 539 539 540 540 === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting === 541 541 574 + 542 542 (% style="color:red" %)**Note:The maximum count depends on the bytes it is. 543 543 The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 544 544 It starts counting again when it reaches the maximum value.** ... ... @@ -598,16 +598,17 @@ 598 598 599 599 (% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)** 600 600 601 -(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20 v), counter increase 1)**634 +(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), the counter increases by 1)** 602 602 603 -(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20 v), counter increase 1)**636 +(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If the AVI1 voltage is lower than VOLMAX (20000mV =20V), counter increases by 1)** 604 604 605 -(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20 v), counter increase 1)**638 +(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), counter increases by 1)** 606 606 ))) 607 607 608 608 609 609 === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI === 610 610 644 + 611 611 (% style="color:red" %)**Note:The maximum count depends on the bytes it is. 612 612 The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 613 613 It starts counting again when it reaches the maximum value.** ... ... @@ -721,9 +721,9 @@ 721 721 722 722 (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:** 723 723 724 -Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 758 +**Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 725 725 726 -Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4 760 +**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4 727 727 728 728 AA: Type Code for this downlink Command: 729 729 ... ... @@ -752,7 +752,7 @@ 752 752 753 753 MOD6 Payload: total of 11 bytes 754 754 755 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:515px" %)789 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) 756 756 |(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:69px" %)**1**|(% style="background-color:#4f81bd; color:white; width:69px" %)**1**|(% style="background-color:#4f81bd; color:white; width:109px" %)**1**|(% style="background-color:#4f81bd; color:white; width:49px" %)**6**|(% style="background-color:#4f81bd; color:white; width:109px" %)**1**|(% style="background-color:#4f81bd; color:white; width:50px" %)**1** 757 757 |Value|((( 758 758 TRI_A FLAG ... ... @@ -766,7 +766,7 @@ 766 766 767 767 (% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below 768 768 769 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:515px" %)803 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) 770 770 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 771 771 |((( 772 772 AV1_LOW ... ... @@ -790,12 +790,12 @@ 790 790 791 791 **Example:** 792 792 793 -10100000: Means the systemhas configure to use the trigger:AV1_LOW and AV2_LOW827 +10100000: This means the system is configured to use the triggers AV1_LOW and AV2_LOW. 794 794 795 795 796 796 (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below 797 797 798 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:515px" %)832 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) 799 799 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 800 800 |((( 801 801 AV1_LOW ... ... @@ -819,31 +819,31 @@ 819 819 820 820 **Example:** 821 821 822 -10000000: Meansthisuplink is triggered by AV1_LOW.Thatmeansthe voltage is too low.856 +10000000: The uplink is triggered by AV1_LOW, indicating that the voltage is too low. 823 823 824 824 825 825 (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below 826 826 827 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:674px" %)828 -|(% style="width: 64px" %)**bit 7**|(% style="width:68px" %)**bit 6**|(% style="width:63px" %)**bit 5**|(% style="width:66px" %)**bit 4**|(% style="width:109px" %)**bit 3**|(% style="width:93px" %)**bit 2**|(% style="width:109px" %)**bit 1**|(% style="width:99px" %)**bit 0**829 -|(% style="width: 64px" %)N/A|(% style="width:68px" %)N/A|(% style="width:63px" %)N/A|(% style="width:66px" %)N/A|(% style="width:109px" %)DI2_STATUS|(% style="width:93px" %)DI2_FLAG|(% style="width:109px" %)DI1_STATUS|(% style="width:99px" %)DI1_FLAG861 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %) 862 +|(% style="width:50px" %)**bit 7**|(% style="width:50px" %)**bit 6**|(% style="width:50px" %)**bit 5**|(% style="width:50px" %)**bit 4**|(% style="width:90px" %)**bit 3**|(% style="width:80px" %)**bit 2**|(% style="width:90px" %)**bit 1**|(% style="width:95px" %)**bit 0** 863 +|(% style="width:49px" %)N/A|(% style="width:53px" %)N/A|(% style="width:53px" %)N/A|(% style="width:55px" %)N/A|(% style="width:99px" %)DI2_STATUS|(% style="width:83px" %)DI2_FLAG|(% style="width:98px" %)DI1_STATUS|(% style="width:85px" %)DI1_FLAG 830 830 831 -* Each bit sshows which status has been triggered on this uplink.865 +* Each bit shows which status has been triggered on this uplink. 832 832 833 833 **Example:** 834 834 835 -00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.869 +00000111: This means both DI1 and DI2 triggers are enabled, and this packet is trigger by DI1. 836 836 837 -00000101: Means both DI1 and DI2 trigger are enabled.871 +00000101: This means both DI1 and DI2 triggers are enabled. 838 838 839 839 840 -(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable. 874 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled. 841 841 842 -Downlink command to poll MOD6 status: 876 +Downlink command to poll/request MOD6 status: 843 843 844 844 **AB 06** 845 845 846 -When device gotthis command, it will send the MOD6 payload.880 +When device receives this command, it will send the MOD6 payload. 847 847 848 848 849 849 === 3.3.7 Payload Decoder === ... ... @@ -857,6 +857,7 @@ 857 857 858 858 == 3.4 Configure LT-22222-L via AT Commands or Downlinks == 859 859 894 + 860 860 ((( 861 861 You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks. 862 862 ))) ... ... @@ -871,19 +871,25 @@ 871 871 872 872 * (% style="color:blue" %)**Sensor-related commands**(%%): 873 873 909 + 874 874 === 3.4.1 Common commands === 875 875 912 + 876 876 ((( 877 877 These are available for each sensors and include actions such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]s. 915 + 916 + 878 878 ))) 879 879 880 880 === 3.4.2 Sensor-related commands === 881 881 921 + 882 882 These commands are specially designed for the LT-22222-L. Commands can be sent to the device using options such as an AT command or a LoRaWAN downlink payload. 883 883 884 884 885 885 ==== 3.4.2.1 Set Transmit/Uplink Interval ==== 886 886 927 + 887 887 Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes. 888 888 889 889 (% style="color:#037691" %)**AT command** ... ... @@ -890,8 +890,15 @@ 890 890 891 891 (% border="2" style="width:500px" %) 892 892 |**Command**|AT+TDC=<time> 893 -|**Response**| 894 -|**Parameters**|**time** : uplink interval is in **milliseconds** 934 +|**Parameters**|**time **: uplink interval in milliseconds 935 +|**Get**|AT+TDC=? 936 +|**Response**|((( 937 +current uplink interval 938 + 939 +OK 940 +))) 941 +|**Set**|AT+TDC=<time> 942 +|**Response**|OK 895 895 |**Example**|((( 896 896 AT+TDC=30000 897 897 ... ... @@ -907,7 +907,7 @@ 907 907 |**Parameters**|((( 908 908 **prefix** : 0x01 909 909 910 -**time** : uplink interval i s in **seconds**, represented by **3 bytes** in **hexadecimal**.958 +**time** : uplink interval in **seconds**, represented by **3 bytes** in **hexadecimal**. 911 911 ))) 912 912 |**Example**|((( 913 913 01 **00 00 1E** ... ... @@ -923,13 +923,13 @@ 923 923 924 924 ==== 3.4.2.2 Set the Working Mode (AT+MOD) ==== 925 925 974 + 926 926 Sets the working mode. 927 927 928 928 (% style="color:#037691" %)**AT command** 929 929 930 930 (% border="2" style="width:500px" %) 931 -|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE=<working_mode> 932 -|(% style="width:97px" %)**Response**|(% style="width:413px" %) 980 +|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MOD=<working_mode> 933 933 |(% style="width:97px" %)**Parameters**|(% style="width:413px" %)((( 934 934 **working_mode** : 935 935 ... ... @@ -945,6 +945,18 @@ 945 945 946 946 6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5 947 947 ))) 996 +|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=? 997 +|(% style="width:97px" %)**Response**|(% style="width:413px" %)((( 998 +Current working mode 999 + 1000 +OK 1001 +))) 1002 +|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode> 1003 +|(% style="width:97px" %)**Response**|(% style="width:413px" %)((( 1004 +Attention:Take effect after ATZ 1005 + 1006 +OK 1007 +))) 948 948 |(% style="width:97px" %)**Example**|(% style="width:413px" %)((( 949 949 AT+MOD=2 950 950 ... ... @@ -967,8 +967,9 @@ 967 967 Sets the device to working mode 2 (Double DI Counting + DO + RO) 968 968 ))) 969 969 970 -==== 3.4.2.3 Pollan uplink ====1030 +==== 3.4.2.3 Request an uplink from the device ==== 971 971 1032 + 972 972 Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode. 973 973 974 974 (% style="color:#037691" %)**AT command** ... ... @@ -988,6 +988,7 @@ 988 988 989 989 ==== 3.4.2.4 Enable/Disable Trigger Mode ==== 990 990 1052 + 991 991 Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]). 992 992 993 993 (% style="color:#037691" %)**AT Command** ... ... @@ -1023,10 +1023,11 @@ 1023 1023 Enable trigger mode for the current working mode 1024 1024 ))) 1025 1025 1026 -==== 3.4.2.5 Polltrigger settings ====1088 +==== 3.4.2.5 Request trigger settings ==== 1027 1027 1028 -Polls the trigger settings. 1029 1029 1091 +Requests the trigger settings. 1092 + 1030 1030 (% style="color:#037691" %)**AT Command:** 1031 1031 1032 1032 There is no AT Command available for this feature. ... ... @@ -1044,6 +1044,7 @@ 1044 1044 1045 1045 ==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ==== 1046 1046 1110 + 1047 1047 Enable or disable DI1/DI2/DI3 as a trigger. 1048 1048 1049 1049 (% style="color:#037691" %)**AT Command** ... ... @@ -1098,9 +1098,9 @@ 1098 1098 1099 1099 ==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ==== 1100 1100 1165 + 1101 1101 Sets DI1 or DI3 (for LT-33222-L) as a trigger. 1102 1102 1103 - 1104 1104 (% style="color:#037691" %)**AT Command** 1105 1105 1106 1106 (% border="2" style="width:500px" %) ... ... @@ -1137,9 +1137,9 @@ 1137 1137 1138 1138 ==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ==== 1139 1139 1204 + 1140 1140 Sets DI2 as a trigger. 1141 1141 1142 - 1143 1143 (% style="color:#037691" %)**AT Command** 1144 1144 1145 1145 (% border="2" style="width:500px" %) ... ... @@ -1171,6 +1171,7 @@ 1171 1171 1172 1172 ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ==== 1173 1173 1238 + 1174 1174 Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1175 1175 1176 1176 (% style="color:#037691" %)**AT Command** ... ... @@ -1220,6 +1220,7 @@ 1220 1220 1221 1221 ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ==== 1222 1222 1288 + 1223 1223 Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1224 1224 1225 1225 (% style="color:#037691" %)**AT Command** ... ... @@ -1267,6 +1267,7 @@ 1267 1267 1268 1268 ==== 3.4.2.11 Trigger – Set minimum interval ==== 1269 1269 1336 + 1270 1270 Sets the AV and AC trigger minimum interval. The device won't respond to a second trigger within this set time after the first trigger. 1271 1271 1272 1272 (% style="color:#037691" %)**AT Command** ... ... @@ -1302,6 +1302,7 @@ 1302 1302 1303 1303 ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ==== 1304 1304 1372 + 1305 1305 Controls the digital outputs DO1, DO2, and DO3 1306 1306 1307 1307 (% style="color:#037691" %)**AT Command** ... ... @@ -1332,11 +1332,11 @@ 1332 1332 ((( 1333 1333 01: Low, 00: High, 11: No action 1334 1334 1335 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:510px" %)1336 -|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**DO1**|(% style="background-color:#4f81bd; color:white" %)**DO2**|(% style="background-color:#4f81bd; color:white" %)**DO3** 1337 -|02 01 00 11|Low|High|No Action 1338 -|02 00 11 01|High|No Action|Low 1339 -|02 11 01 00|No Action|Low|High 1403 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:383px" %) 1404 +|(% style="background-color:#4f81bd; color:white; width:126px" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white; width:85px" %)**DO1**|(% style="background-color:#4f81bd; color:white; width:86px" %)**DO2**|(% style="background-color:#4f81bd; color:white; width:86px" %)**DO3** 1405 +|(% style="width:126px" %)02 01 00 11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action 1406 +|(% style="width:126px" %)02 00 11 01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low 1407 +|(% style="width:126px" %)02 11 01 00|(% style="width:85px" %)No Action|(% style="width:86px" %)Low|(% style="width:86px" %)High 1340 1340 ))) 1341 1341 1342 1342 ((( ... ... @@ -1355,25 +1355,23 @@ 1355 1355 1356 1356 * (% style="color:#037691" %)**AT Command** 1357 1357 1358 -There is no AT Command to controlDigitalOutput1426 +There is no AT command to control the digital output. 1359 1359 1360 1360 1361 1361 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)** 1362 1362 1363 -(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Set DO1/DO2/DO3 output with time control 1431 +(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control 1364 1364 1365 - 1366 1366 This is to control the digital output time of DO pin. Include four bytes: 1367 1367 1368 -(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)1435 +(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9) 1369 1369 1370 -(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode1437 +(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode 1371 1371 1372 -01: DO pins will change back to original state after timeout. 1439 +**01:** DO pins revert to their original state after the timeout. 1440 +**00:** DO pins switch to an inverted state after the timeout. 1373 1373 1374 -00: DO pins will change to an inverter state after timeout 1375 1375 1376 - 1377 1377 (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status: 1378 1378 1379 1379 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) ... ... @@ -1382,7 +1382,7 @@ 1382 1382 |0x00|DO1 set to high 1383 1383 |0x11|DO1 NO Action 1384 1384 1385 -(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:1451 +(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status: 1386 1386 1387 1387 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1388 1388 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1390,7 +1390,7 @@ 1390 1390 |0x00|DO2 set to high 1391 1391 |0x11|DO2 NO Action 1392 1392 1393 -(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:1459 +(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status: 1394 1394 1395 1395 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1396 1396 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1398,7 +1398,7 @@ 1398 1398 |0x00|DO3 set to high 1399 1399 |0x11|DO3 NO Action 1400 1400 1401 -(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)1467 +(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms) 1402 1402 1403 1403 1404 1404 (% style="color:red" %)**Note: ** ... ... @@ -1407,7 +1407,7 @@ 1407 1407 1408 1408 Before firmware v1.6.0, the latch time only supported 2 bytes. 1409 1409 1410 -(% style="color:red" %)** Device will uploada packet if the downlink code executes successfully.**1476 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.** 1411 1411 1412 1412 1413 1413 **Example payload:** ... ... @@ -1434,16 +1434,16 @@ 1434 1434 1435 1435 * (% style="color:#037691" %)**AT Command:** 1436 1436 1437 -There is no AT Command to control Relay Output 1503 +There is no AT Command to control the Relay Output 1438 1438 1439 1439 1440 1440 * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):** 1441 1441 1442 -(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set RO1/RO2 output 1508 +(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Sets RO1/RO2 output 1443 1443 1444 1444 1445 1445 ((( 1446 -If payload is 0x030100, it means setting RO1 to close and RO2 to open. 1512 +If the payload is 0x030100, it means setting RO1 to close and RO2 to open. 1447 1447 ))) 1448 1448 1449 1449 ((( ... ... @@ -1461,28 +1461,29 @@ 1461 1461 |03 00 01|Open|Close 1462 1462 ))) 1463 1463 1464 -(% style="color:red" %)** Device will uploada packet if downlink code executes successfully.**1530 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.** 1465 1465 1466 1466 1467 1467 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== 1468 1468 1535 + 1469 1469 Controls the relay output time. 1470 1470 1471 1471 * (% style="color:#037691" %)**AT Command:** 1472 1472 1473 -There is no AT Command to control Relay Output 1540 +There is no AT Command to control the Relay Output 1474 1474 1475 1475 1476 1476 * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):** 1477 1477 1478 -(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set RO1/RO2 relay with time control 1545 +(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Sets RO1/RO2 relays with time control 1479 1479 1480 1480 1481 -This is tocontrol the relay output time.Itincludesfourbytes:1548 +This controls the relay output time and includes 4 bytes: 1482 1482 1483 -(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)1550 +(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05) 1484 1484 1485 -(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode1552 +(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode 1486 1486 1487 1487 01: Relays will change back to their original state after timeout. 1488 1488 ... ... @@ -1489,12 +1489,12 @@ 1489 1489 00: Relays will change to the inverter state after timeout. 1490 1490 1491 1491 1492 -(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:1559 +(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status: 1493 1493 1494 1494 [[image:image-20221008095908-1.png||height="364" width="564"]] 1495 1495 1496 1496 1497 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms1564 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes (cc)**(%%): Latching time. Unit: ms 1498 1498 1499 1499 1500 1500 (% style="color:red" %)**Note:** ... ... @@ -1504,7 +1504,7 @@ 1504 1504 Before firmware v1.6.0, the latch time only supported 2 bytes. 1505 1505 1506 1506 1507 -(% style="color:red" %)** Device will uploada packet if the downlink code executes successfully.**1574 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.** 1508 1508 1509 1509 1510 1510 **Example payload:** ... ... @@ -1663,8 +1663,9 @@ 1663 1663 ))) 1664 1664 |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01** 1665 1665 1666 -==== 3.4.2.19 Counting ~-~- Changecountingmodetosavetime====1733 +==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ==== 1667 1667 1735 + 1668 1668 This command allows you to configure the device to save its counting result to internal flash memory at specified intervals. By setting a save time, the device will periodically store the counting data to prevent loss in case of power failure. The save interval can be adjusted to suit your requirements, with a minimum value of 30 seconds. 1669 1669 1670 1670 (% style="color:#037691" %)**AT Command** ... ... @@ -1694,8 +1694,9 @@ 1694 1694 Sets the device to save its counting results to the memory every 60 seconds. 1695 1695 ))) 1696 1696 1697 -==== 3.4.2.20 Reset save RO DO state ==== 1765 +==== 3.4.2.20 Reset saved RO and DO states ==== 1698 1698 1767 + 1699 1699 This command allows you to reset the saved relay output (RO) and digital output (DO) states when the device joins the network. By configuring this setting, you can control whether the device should retain or reset the relay states after a reset and rejoin to the network. 1700 1700 1701 1701 (% style="color:#037691" %)**AT Command** ... ... @@ -1745,6 +1745,7 @@ 1745 1745 1746 1746 ==== 3.4.2.21 Encrypted payload ==== 1747 1747 1817 + 1748 1748 This command allows you to configure whether the device should upload data in an encrypted format or in plaintext. By default, the device encrypts the payload before uploading. You can toggle this setting to either upload encrypted data or transmit it without encryption. 1749 1749 1750 1750 (% style="color:#037691" %)**AT Command:** ... ... @@ -1774,6 +1774,7 @@ 1774 1774 1775 1775 ==== 3.4.2.22 Get sensor value ==== 1776 1776 1847 + 1777 1777 This command allows you to retrieve and optionally uplink sensor readings through the serial port. 1778 1778 1779 1779 (% style="color:#037691" %)**AT Command** ... ... @@ -1803,6 +1803,7 @@ 1803 1803 1804 1804 ==== 3.4.2.23 Resetting the downlink packet count ==== 1805 1805 1877 + 1806 1806 This command manages how the node handles mismatched downlink packet counts. It offers two modes: one disables the reception of further downlink packets if discrepancies occur, while the other resets the downlink packet count to align with the server, ensuring continued communication. 1807 1807 1808 1808 (% style="color:#037691" %)**AT Command** ... ... @@ -1881,43 +1881,33 @@ 1881 1881 1882 1882 ==== 3.4.2.25 Copy downlink to uplink ==== 1883 1883 1884 -This command enables the device to immediately uplink the content of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100. 1885 1885 1886 - *(%style="color:#037691"%)**ATCommand**(%%)**:**1957 +This command enables the device to immediately uplink the payload of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100. 1887 1887 1888 -(% style="color: blue" %)**AT+RPL=5**(%%) ~/~/ After receiving the package fromthe server, it will immediately upload the content of the package to the server, the port number is 100.1959 +(% style="color:#037691" %)**AT Command**(%%)**:** 1889 1889 1890 - Example:**aa xx xx xx xx**aaindicateswhether the configuration haschanged,00isyes,01 is no;xx xx xx xx arethebytessent.1961 +(% style="color:blue" %)**AT+RPL=5** (%%) ~/~/ After receiving a downlink payload from the server, the device will immediately uplink the payload back to the server using port number 100. 1891 1891 1963 +Example:**aa xx xx xx xx** ~/~/ **aa** indicates whether the configuration has changed: **00** means YES, and **01** means NO. **xx xx xx xx** are the bytes uplinked back. 1892 1892 1965 + 1893 1893 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173747-6.png?width=1124&height=165&rev=1.1||alt="image-20220823173747-6.png"]] 1894 1894 1895 1895 For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77. 1896 1896 1897 -(% border="2" style="width:500px" %) 1898 -|(% style="width:122px" %)**Command**|(% style="width:376px" %)((( 1899 -AT+RPL=5 1900 - 1901 -After receiving a downlink packet from the server, the node immediately uplinks the content of the packet back to the server using port number 100. 1902 -))) 1903 -|(% style="width:122px" %)**Example**|(% style="width:376px" %)((( 1904 -Downlink: 1905 - 1906 -01 00 02 58 1907 - 1908 -Uplink: 1909 - 1910 -01 01 00 02 58 1911 -))) 1912 - 1913 1913 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]] 1914 1914 1915 1915 For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. 1916 1916 1917 1917 1975 +(% style="color:#037691" %)**Downlink Payload**(%%)**:** 1918 1918 1977 +There is no downlink option available for this feature. 1978 + 1979 + 1919 1919 ==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ==== 1920 1920 1982 + 1921 1921 This command is used to query key information about the device, including its firmware version, frequency band, sub band, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device. 1922 1922 1923 1923 * ((( ... ... @@ -1936,10 +1936,13 @@ 1936 1936 1937 1937 == 3.5 Integrating with ThingsEye.io == 1938 1938 2001 + 1939 1939 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. 1940 1940 2004 + 1941 1941 === 3.5.1 Configuring The Things Stack === 1942 1942 2007 + 1943 1943 We use The Things Stack Sandbox in this example: 1944 1944 1945 1945 * In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added. ... ... @@ -1951,10 +1951,12 @@ 1951 1951 The username and password (API key) you created here are required in the next section. 1952 1952 {{/info}} 1953 1953 1954 -[[image:tts-mqtt-integration.png ||height="625" width="1000"]]2019 +[[image:tts-mqtt-integration.png]] 1955 1955 2021 + 1956 1956 === 3.5.2 Configuring ThingsEye.io === 1957 1957 2024 + 1958 1958 The ThingsEye.io IoT platform is not open for self-registration at the moment. If you are interested in testing the platform, please send your project information to admin@thingseye.io, and we will create an account for you. 1959 1959 1960 1960 * Login to your [[ThingsEye.io >>https://thingseye.io]]account. ... ... @@ -1961,7 +1961,7 @@ 1961 1961 * Under the **Integrations center**, click **Integrations**. 1962 1962 * Click the **Add integration** button (the button with the **+** symbol). 1963 1963 1964 -[[image:thingseye-io-step-1.png ||height="625" width="1000"]]2031 +[[image:thingseye-io-step-1.png]] 1965 1965 1966 1966 1967 1967 On the **Add integration** window, configure the following: ... ... @@ -1976,7 +1976,7 @@ 1976 1976 ** Allow create devices or assets 1977 1977 * Click the **Next** button. you will be navigated to the **Uplink data converter** tab. 1978 1978 1979 -[[image:thingseye-io-step-2.png ||height="625" width="1000"]]2046 +[[image:thingseye-io-step-2.png]] 1980 1980 1981 1981 1982 1982 **Uplink data converter:** ... ... @@ -1987,7 +1987,7 @@ 1987 1987 * 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]]. 1988 1988 * Click the **Next** button. You will be navigated to the **Downlink data converter **tab. 1989 1989 1990 -[[image:thingseye-io-step-3.png ||height="625" width="1000"]]2057 +[[image:thingseye-io-step-3.png]] 1991 1991 1992 1992 1993 1993 **Downlink data converter (this is an optional step):** ... ... @@ -1998,7 +1998,7 @@ 1998 1998 * 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]]. 1999 1999 * Click the **Next** button. You will be navigated to the **Connection** tab. 2000 2000 2001 -[[image:thingseye-io-step-4.png ||height="625" width="1000"]]2068 +[[image:thingseye-io-step-4.png]] 2002 2002 2003 2003 2004 2004 **Connection:** ... ... @@ -2013,20 +2013,21 @@ 2013 2013 2014 2014 * Click the **Add** button. 2015 2015 2016 -[[image:thingseye-io-step-5.png ||height="625" width="1000"]]2083 +[[image:thingseye-io-step-5.png]] 2017 2017 2018 2018 2019 2019 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 and correct any errors. 2020 2020 2021 2021 2022 -[[image:thingseye.io_integrationsCenter_integrations.png ||height="686" width="1000"]]2089 +[[image:thingseye.io_integrationsCenter_integrations.png]] 2023 2023 2024 2024 2025 2025 ==== 3.5.2.1 Viewing integration details ==== 2026 2026 2094 + 2027 2027 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. 2028 2028 2029 -[[image:integration-details.png ||height="686" width="1000"]]2097 +[[image:integration-details.png]] 2030 2030 2031 2031 2032 2032 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. ... ... @@ -2035,28 +2035,32 @@ 2035 2035 See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]]. 2036 2036 {{/info}} 2037 2037 2038 -==== **3.5.2.2 Viewing events** ==== 2039 2039 2107 +==== 3.5.2.2 Viewing events ==== 2108 + 2109 + 2040 2040 The **Events **tab displays all the uplink messages from the LT-22222-L. 2041 2041 2042 2042 * Select **Debug **from the **Event type** dropdown. 2043 2043 * Select the** time frame** from the **time window**. 2044 2044 2045 -[[image:thingseye-events.png ||height="686" width="1000"]]2115 +[[image:thingseye-events.png]] 2046 2046 2047 2047 2048 2048 * To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message. 2049 2049 2050 -[[image:thingseye-json.png ||width="1000"]]2120 +[[image:thingseye-json.png]] 2051 2051 2052 2052 2053 -==== **3.5.2.3 Deleting an integration**====2123 +==== 3.5.2.3 Deleting an integration ==== 2054 2054 2125 + 2055 2055 If you want to delete an integration, click the **Delete integratio**n button on the Integrations page. 2056 2056 2057 2057 2058 2058 ==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ==== 2059 2059 2131 + 2060 2060 This will be added soon. 2061 2061 2062 2062 ... ... @@ -2065,7 +2065,7 @@ 2065 2065 === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) === 2066 2066 2067 2067 2068 -Supports** 2140 +Supports** NPN-type **sensors. 2069 2069 2070 2070 [[image:1653356991268-289.png]] 2071 2071 ... ... @@ -2273,6 +2273,7 @@ 2273 2273 2274 2274 == 3.7 LED Indicators == 2275 2275 2348 + 2276 2276 The table below lists the behavior of LED indicators for each port function. 2277 2277 2278 2278 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) ... ... @@ -2305,10 +2305,13 @@ 2305 2305 2306 2306 = 4. Using AT Commands = 2307 2307 2381 + 2308 2308 The LT-22222-L supports programming using AT Commands. 2309 2309 2384 + 2310 2310 == 4.1 Connecting the LT-22222-L to a PC == 2311 2311 2387 + 2312 2312 ((( 2313 2313 You can use a USB-to-TTL adapter/converter along with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below. 2314 2314 ... ... @@ -2328,7 +2328,10 @@ 2328 2328 ((( 2329 2329 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/]] 2330 2330 2407 + 2331 2331 == 4.2 LT-22222-L related AT commands == 2409 + 2410 + 2332 2332 ))) 2333 2333 2334 2334 ((( ... ... @@ -2525,16 +2525,19 @@ 2525 2525 2526 2526 == 5.1 Counting how many objects pass through the flow line == 2527 2527 2607 + 2528 2528 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]]? 2529 2529 2530 2530 2531 2531 = 6. FAQ = 2532 2532 2613 + 2533 2533 This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly. 2534 2534 2535 2535 2536 2536 == 6.1 How to update the firmware? == 2537 2537 2619 + 2538 2538 Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to: 2539 2539 2540 2540 * Support new features ... ... @@ -2587,6 +2587,8 @@ 2587 2587 ((( 2588 2588 ((( 2589 2589 == 6.2 How to change the LoRaWAN frequency band/region? == 2672 + 2673 + 2590 2590 ))) 2591 2591 ))) 2592 2592 ... ... @@ -2598,6 +2598,8 @@ 2598 2598 2599 2599 2600 2600 == 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? == 2685 + 2686 + 2601 2601 ))) 2602 2602 2603 2603 ((( ... ... @@ -2671,11 +2671,13 @@ 2671 2671 2672 2672 == 6.4 How to change the uplink interval? == 2673 2673 2760 + 2674 2674 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/]] 2675 2675 2676 2676 2677 2677 == 6.5 Can I see the counting event in the serial output? == 2678 2678 2766 + 2679 2679 ((( 2680 2680 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. 2681 2681 ... ... @@ -2682,6 +2682,7 @@ 2682 2682 2683 2683 == 6.6 Can I use point-to-point communication with LT-22222-L? == 2684 2684 2773 + 2685 2685 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]]. 2686 2686 2687 2687 ... ... @@ -2690,6 +2690,7 @@ 2690 2690 ((( 2691 2691 == 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? == 2692 2692 2782 + 2693 2693 * If the device is not properly shut down and is directly powered off. 2694 2694 * It will default to a power-off state. 2695 2695 * In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory. ... ... @@ -2697,6 +2697,7 @@ 2697 2697 2698 2698 == 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? == 2699 2699 2790 + 2700 2700 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: 2701 2701 2702 2702 ... ... @@ -2705,16 +2705,19 @@ 2705 2705 2706 2706 == 6.9 Can the LT-22222-L save the RO state? == 2707 2707 2799 + 2708 2708 To enable this feature, the firmware version must be 1.6.0 or higher. 2709 2709 2710 2710 2711 2711 == 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? == 2712 2712 2805 + 2713 2713 It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose. 2714 2714 2715 2715 2716 2716 = 7. Troubleshooting = 2717 2717 2811 + 2718 2718 This section provides some known troubleshooting tips. 2719 2719 2720 2720 ... ... @@ -2723,6 +2723,8 @@ 2723 2723 ((( 2724 2724 ((( 2725 2725 == 7.1 Downlink isn't working. How can I solve this? == 2820 + 2821 + 2726 2726 ))) 2727 2727 ))) 2728 2728 ... ... @@ -2734,6 +2734,8 @@ 2734 2734 2735 2735 2736 2736 == 7.2 Having trouble uploading an image? == 2833 + 2834 + 2737 2737 ))) 2738 2738 2739 2739 ((( ... ... @@ -2744,6 +2744,8 @@ 2744 2744 2745 2745 2746 2746 == 7.3 Why can't I join TTN in the US915 /AU915 bands? == 2845 + 2846 + 2747 2747 ))) 2748 2748 2749 2749 ((( ... ... @@ -2753,6 +2753,7 @@ 2753 2753 2754 2754 == 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? == 2755 2755 2856 + 2756 2756 The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue. 2757 2757 Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]] 2758 2758 ... ... @@ -2759,6 +2759,7 @@ 2759 2759 2760 2760 = 8. Ordering information = 2761 2761 2863 + 2762 2762 (% style="color:#4f81bd" %)**LT-22222-L-XXX:** 2763 2763 2764 2764 (% style="color:#4f81bd" %)**XXX:** ... ... @@ -2775,6 +2775,7 @@ 2775 2775 2776 2776 = 9. Package information = 2777 2777 2880 + 2778 2778 **Package includes**: 2779 2779 2780 2780 * 1 x LT-22222-L I/O Controller ... ... @@ -2791,6 +2791,7 @@ 2791 2791 2792 2792 = 10. Support = 2793 2793 2897 + 2794 2794 * ((( 2795 2795 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. 2796 2796 ))) ... ... @@ -2802,6 +2802,7 @@ 2802 2802 2803 2803 = 11. Reference = 2804 2804 2909 + 2805 2805 * 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]] 2806 2806 * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]] 2807 2807 * [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]
- lt-22222-l-joining.png
-
- Size
-
... ... @@ -1,1 +1,1 @@ 1 - 274.1 KB1 +301.9 KB - Content
- Screenshot 2024-12-08 193946.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +32.4 KB - Content
- lt-22222-l-js-custom-payload-formatter.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +453.9 KB - Content
- lt33222-l.jpg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +31.3 KB - Content