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 (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 5 removed)
Details
- Page properties
-
- Content
-
... ... @@ -21,7 +21,6 @@ 21 21 22 22 == 1.1 What is the LT-22222-L I/O Controller? == 23 23 24 - 25 25 ((( 26 26 ((( 27 27 {{info}} ... ... @@ -55,10 +55,8 @@ 55 55 (% class="wikigeneratedid" %) 56 56 [[image:lorawan-nw.jpg||height="354" width="900"]] 57 57 58 - 59 59 == 1.2 Specifications == 60 60 61 - 62 62 (% style="color:#037691" %)**Hardware System:** 63 63 64 64 * STM32L072xxxx MCU ... ... @@ -100,7 +100,6 @@ 100 100 101 101 == 1.3 Features == 102 102 103 - 104 104 * LoRaWAN Class A & Class C modes 105 105 * Optional Customized LoRa Protocol 106 106 * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869 ... ... @@ -111,7 +111,6 @@ 111 111 112 112 == 1.4 Applications == 113 113 114 - 115 115 * Smart buildings & home automation 116 116 * Logistics and supply chain management 117 117 * Smart metering ... ... @@ -121,13 +121,11 @@ 121 121 122 122 == 1.5 Hardware Variants == 123 123 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" %)((( 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" %)((( 131 131 * 2 x Digital Input (Bi-direction) 132 132 * 2 x Digital Output 133 133 * 2 x Relay Output (5A@250VAC / 30VDC) ... ... @@ -140,7 +140,6 @@ 140 140 141 141 == 2.1 Connecting the antenna == 142 142 143 - 144 144 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. 145 145 146 146 {{warning}} ... ... @@ -147,45 +147,42 @@ 147 147 **Warning! Do not power on the device without connecting the antenna.** 148 148 {{/warning}} 149 149 150 - 151 151 == 2.2 Terminals == 152 152 153 - 154 154 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. 155 155 156 156 **Upper screw terminal block (from left to right):** 157 157 158 -(% 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" %)Function160 -|(% style="width: 139px" %)GND|(% style="width:242px" %)Ground161 -|(% style="width: 139px" %)VIN|(% style="width:242px" %)Input Voltage162 -|(% style="width: 139px" %)AVI2|(% style="width:242px" %)Analog Voltage Input Terminal 2163 -|(% style="width: 139px" %)AVI1|(% style="width:242px" %)Analog Voltage Input Terminal 1164 -|(% style="width: 139px" %)ACI2|(% style="width:242px" %)Analog Current Input Terminal 2165 -|(% style="width: 139px" %)ACI1|(% style="width:242px" %)Analog Current Input Terminal 1148 +(% style="width:634px" %) 149 +|=(% style="width: 295px;" %)Screw Terminal|=(% style="width: 338px;" %)Function 150 +|(% style="width:295px" %)GND|(% style="width:338px" %)Ground 151 +|(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage 152 +|(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2 153 +|(% style="width:295px" %)AVI1|(% style="width:338px" %)Analog Voltage Input Terminal 1 154 +|(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2 155 +|(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1 166 166 167 167 **Lower screw terminal block (from left to right):** 168 168 169 -(% 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" %)Function171 -|(% style="width: 125px" %)RO1-2|(% style="width:128px" %)Relay Output 1172 -|(% style="width: 125px" %)RO1-1|(% style="width:128px" %)Relay Output 1173 -|(% style="width: 125px" %)RO2-2|(% style="width:128px" %)Relay Output 2174 -|(% style="width: 125px" %)RO2-1|(% style="width:128px" %)Relay Output 2175 -|(% style="width: 125px" %)DI2+|(% style="width:128px" %)Digital Input 2176 -|(% style="width: 125px" %)DI2-|(% style="width:128px" %)Digital Input 2177 -|(% style="width: 125px" %)DI1+|(% style="width:128px" %)Digital Input 1178 -|(% style="width: 125px" %)DI1-|(% style="width:128px" %)Digital Input 1179 -|(% style="width: 125px" %)DO2|(% style="width:128px" %)Digital Output 2180 -|(% style="width: 125px" %)DO1|(% style="width:128px" %)Digital Output 1159 +(% style="width:633px" %) 160 +|=(% style="width: 296px;" %)Screw Terminal|=(% style="width: 334px;" %)Function 161 +|(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1 162 +|(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1 163 +|(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2 164 +|(% style="width:296px" %)RO2-1|(% style="width:334px" %)Relay Output 2 165 +|(% style="width:296px" %)DI2+|(% style="width:334px" %)Digital Input 2 166 +|(% style="width:296px" %)DI2-|(% style="width:334px" %)Digital Input 2 167 +|(% style="width:296px" %)DI1+|(% style="width:334px" %)Digital Input 1 168 +|(% style="width:296px" %)DI1-|(% style="width:334px" %)Digital Input 1 169 +|(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2 170 +|(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1 181 181 182 182 == 2.3 Connecting LT-22222-L to a Power Source == 183 183 184 - 185 185 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. 186 186 187 187 {{warning}} 188 -**We recommend that you power on the LT-22222-L after adding its registration information to theLoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.**177 +**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.** 189 189 {{/warning}} 190 190 191 191 ... ... @@ -194,27 +194,23 @@ 194 194 195 195 = 3. Registering LT-22222-L with a LoRaWAN Network Server = 196 196 197 - 198 198 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. 199 199 200 200 201 -== 3.1 Prerequisites == 189 +=== 3.2.1 Prerequisites === 202 202 203 - 204 204 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. 205 205 206 206 [[image:image-20230425173427-2.png||height="246" width="530"]] 207 207 208 208 {{info}} 209 -I fyou are unabletoset theprovided root key and other identifiers in the network server,youmustgeneratenew keysandidentifierswith the networkserverand configure thedevicewiththemusing ATcommands.196 +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. 210 210 {{/info}} 211 211 212 212 The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers. 213 213 201 +=== 3.2.2 The Things Stack === 214 214 215 -== 3.2 The Things Stack == 216 - 217 - 218 218 This section guides you through how to register your LT-22222-L with The Things Stack Sandbox. 219 219 220 220 {{info}} ... ... @@ -225,7 +225,7 @@ 225 225 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. 226 226 227 227 228 -[[image:dragino-lorawan-nw-lt-22222-n.jpg ||height="374" width="1400"]]213 +[[image:dragino-lorawan-nw-lt-22222-n.jpg]] 229 229 230 230 {{info}} 231 231 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. ... ... @@ -232,9 +232,8 @@ 232 232 {{/info}} 233 233 234 234 235 -=== 3.2.1 Setting up === 220 +==== 3.2.2.1 Setting up ==== 236 236 237 - 238 238 * Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet. 239 239 * Log in to your The Things Stack Sandbox account. 240 240 * Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs). ... ... @@ -241,10 +241,8 @@ 241 241 * Go to your application's page and click on the **End devices** in the left menu. 242 242 * On the End devices page, click on **+ Register end device**. Two registration options are available: 243 243 228 +==== 3.2.2.2 Using the LoRaWAN Device Repository ==== 244 244 245 -==== 3.2.1.1 Using the LoRaWAN Device Repository ==== 246 - 247 - 248 248 * On the **Register end device** page: 249 249 ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**. 250 250 ** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists. ... ... @@ -255,7 +255,7 @@ 255 255 *** **Profile (Region)**: Select the region that matches your device. 256 256 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 257 257 258 -[[image:lt-22222-l-dev-repo-reg-p1.png]] 240 +[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]] 259 259 260 260 261 261 * Register end device page continued... ... ... @@ -265,12 +265,11 @@ 265 265 ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. 266 266 ** Under **After registration**, select the **View registered end device** option. 267 267 268 -[[image:lt-22222-l-dev-repo-reg-p2.png]] 250 +[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]] 269 269 270 270 271 -==== 3.2. 1.2 Adding device manually ====253 +==== 3.2.2.3 Adding device manually ==== 272 272 273 - 274 274 * On the **Register end device** page: 275 275 ** Select the option **Enter end device specifies manually** under **Input method**. 276 276 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. ... ... @@ -280,7 +280,7 @@ 280 280 ** Select the option **Over the air activation (OTAA)** under the **Activation mode.** 281 281 ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list. 282 282 283 -[[image:lt-22222-l-manually-p1.png]] 264 +[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]] 284 284 285 285 286 286 * Register end device page continued... ... ... @@ -291,27 +291,26 @@ 291 291 ** Under **After registration**, select the **View registered end device** option. 292 292 ** Click the **Register end device** button. 293 293 294 -[[image:lt-22222-l-manually-p2.png]] 275 +[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]] 295 295 296 296 297 297 You will be navigated to the **Device overview** page. 298 298 299 299 300 -[[image:lt-22222-device-overview.png]] 281 +[[image:lt-22222-device-overview.png||height="625" width="1000"]] 301 301 302 302 303 -=== 3.2.2 Joining === 284 +==== 3.2.2.4 Joining ==== 304 304 305 - 306 306 On the Device's page, click on **Live data** tab. The Live data panel for your device will display. 307 307 308 308 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. 309 309 310 310 311 -[[image:lt-22222- l-joining.png]]291 +[[image:lt-22222-join-network.png||height="625" width="1000"]] 312 312 313 313 314 -=== 3.2. 3Uplinks ===294 +==== 3.2.2.5 Uplinks ==== 315 315 316 316 317 317 After successfully joining, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**). When the LT-22222-L sends an uplink message to the server, the **TX LED** turns on for **1 second**. By default, you will receive an uplink data message from the device every 10 minutes. ... ... @@ -327,18 +327,11 @@ 327 327 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. 328 328 {{/info}} 329 329 330 -[[image:lt-22222-ul-payload-fmt.png]] 310 +[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]] 331 331 332 332 333 - Wealso 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]]:313 +==== 3.2.2.6 Downlinks ==== 334 334 335 -(% class="wikigeneratedid" %) 336 -[[image:lt-22222-l-js-custom-payload-formatter.png]] 337 - 338 - 339 -=== 3.2.4 Downlinks === 340 - 341 - 342 342 When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**. 343 343 344 344 ... ... @@ -361,10 +361,8 @@ 361 361 362 362 The uplink messages are sent over LoRaWAN FPort=2. By default, an uplink message is sent every 10 minutes. 363 363 364 - 365 365 === 3.3.1 AT+MOD~=1, 2ACI+2AVI === 366 366 367 - 368 368 ((( 369 369 This is the default mode. 370 370 ... ... @@ -437,7 +437,6 @@ 437 437 438 438 MOD = 1 439 439 440 - 441 441 === 3.3.2 AT+MOD~=2, (Double DI Counting) === 442 442 443 443 ... ... @@ -516,7 +516,6 @@ 516 516 517 517 === 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI === 518 518 519 - 520 520 (% style="color:red" %)**Note: The maximum count depends on the bytes it is. 521 521 The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 522 522 It starts counting again when it reaches the maximum value.** ... ... @@ -570,7 +570,6 @@ 570 570 571 571 === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting === 572 572 573 - 574 574 (% style="color:red" %)**Note:The maximum count depends on the bytes it is. 575 575 The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 576 576 It starts counting again when it reaches the maximum value.** ... ... @@ -630,17 +630,16 @@ 630 630 631 631 (% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)** 632 632 633 -(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If theAVI1 voltageishigher than VOLMAX (20000mV =20V),thecounter increasesby1)**601 +(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 634 634 635 -(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If theAVI1 voltageislower than VOLMAX (20000mV =20V), counter increasesby1)**603 +(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)** 636 636 637 -(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If theAVI1 voltageishigher than VOLMAX (20000mV =20V), counter increasesby1)**605 +(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 638 638 ))) 639 639 640 640 641 641 === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI === 642 642 643 - 644 644 (% style="color:red" %)**Note:The maximum count depends on the bytes it is. 645 645 The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec). 646 646 It starts counting again when it reaches the maximum value.** ... ... @@ -754,9 +754,9 @@ 754 754 755 755 (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:** 756 756 757 - **Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**724 +Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 758 758 759 - **Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4726 +Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4 760 760 761 761 AA: Type Code for this downlink Command: 762 762 ... ... @@ -785,7 +785,7 @@ 785 785 786 786 MOD6 Payload: total of 11 bytes 787 787 788 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)755 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 789 789 |(% 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** 790 790 |Value|((( 791 791 TRI_A FLAG ... ... @@ -799,7 +799,7 @@ 799 799 800 800 (% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below 801 801 802 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)769 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 803 803 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 804 804 |((( 805 805 AV1_LOW ... ... @@ -823,12 +823,12 @@ 823 823 824 824 **Example:** 825 825 826 -10100000: This means the systemis configuredto use the triggersAV1_LOW and AV2_LOW.793 +10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW 827 827 828 828 829 829 (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below 830 830 831 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)798 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %) 832 832 |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0** 833 833 |((( 834 834 AV1_LOW ... ... @@ -852,31 +852,31 @@ 852 852 853 853 **Example:** 854 854 855 -10000000: The uplink is triggered by AV1_LOW,indicatingthatthe voltage is too low.822 +10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low. 856 856 857 857 858 858 (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below 859 859 860 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:515px" %)861 -|(% 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**862 -|(% style="width:4 9px" %)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_FLAG827 +(% 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_FLAG 863 863 864 -* Each bit shows which status has been triggered on this uplink. 831 +* Each bits shows which status has been triggered on this uplink. 865 865 866 866 **Example:** 867 867 868 -00000111: This means both DI1 and DI2 triggersare enabled,and this packet is trigger by DI1.835 +00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1. 869 869 870 -00000101: This means both DI1 and DI2 triggersare enabled.837 +00000101: Means both DI1 and DI2 trigger are enabled. 871 871 872 872 873 -(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable d. 0x00: MOD6 is disabled.840 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable. 874 874 875 -Downlink command to poll /requestMOD6 status:842 +Downlink command to poll MOD6 status: 876 876 877 877 **AB 06** 878 878 879 -When device receivesthis command, it will send the MOD6 payload.846 +When device got this command, it will send the MOD6 payload. 880 880 881 881 882 882 === 3.3.7 Payload Decoder === ... ... @@ -890,7 +890,6 @@ 890 890 891 891 == 3.4 Configure LT-22222-L via AT Commands or Downlinks == 892 892 893 - 894 894 ((( 895 895 You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks. 896 896 ))) ... ... @@ -907,22 +907,17 @@ 907 907 908 908 === 3.4.1 Common commands === 909 909 910 - 911 911 ((( 912 912 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. 913 - 914 - 915 915 ))) 916 916 917 917 === 3.4.2 Sensor-related commands === 918 918 919 - 920 920 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. 921 921 922 922 923 923 ==== 3.4.2.1 Set Transmit/Uplink Interval ==== 924 924 925 - 926 926 Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes. 927 927 928 928 (% style="color:#037691" %)**AT command** ... ... @@ -929,15 +929,8 @@ 929 929 930 930 (% border="2" style="width:500px" %) 931 931 |**Command**|AT+TDC=<time> 932 -|**Parameters**|**time **: uplink interval in milliseconds 933 -|**Get**|AT+TDC=? 934 -|**Response**|((( 935 -current uplink interval 936 - 937 -OK 938 -))) 939 -|**Set**|AT+TDC=<time> 940 -|**Response**|OK 893 +|**Response**| 894 +|**Parameters**|**time** : uplink interval is in **milliseconds** 941 941 |**Example**|((( 942 942 AT+TDC=30000 943 943 ... ... @@ -953,7 +953,7 @@ 953 953 |**Parameters**|((( 954 954 **prefix** : 0x01 955 955 956 -**time** : uplink interval in **seconds**, represented by **3 bytes** in **hexadecimal**. 910 +**time** : uplink interval is in **seconds**, represented by **3 bytes** in **hexadecimal**. 957 957 ))) 958 958 |**Example**|((( 959 959 01 **00 00 1E** ... ... @@ -969,13 +969,13 @@ 969 969 970 970 ==== 3.4.2.2 Set the Working Mode (AT+MOD) ==== 971 971 972 - 973 973 Sets the working mode. 974 974 975 975 (% style="color:#037691" %)**AT command** 976 976 977 977 (% border="2" style="width:500px" %) 978 -|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MOD=<working_mode> 931 +|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE=<working_mode> 932 +|(% style="width:97px" %)**Response**|(% style="width:413px" %) 979 979 |(% style="width:97px" %)**Parameters**|(% style="width:413px" %)((( 980 980 **working_mode** : 981 981 ... ... @@ -991,18 +991,6 @@ 991 991 992 992 6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5 993 993 ))) 994 -|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=? 995 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)((( 996 -Current working mode 997 - 998 -OK 999 -))) 1000 -|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode> 1001 -|(% style="width:97px" %)**Response**|(% style="width:413px" %)((( 1002 -Attention:Take effect after ATZ 1003 - 1004 -OK 1005 -))) 1006 1006 |(% style="width:97px" %)**Example**|(% style="width:413px" %)((( 1007 1007 AT+MOD=2 1008 1008 ... ... @@ -1025,9 +1025,8 @@ 1025 1025 Sets the device to working mode 2 (Double DI Counting + DO + RO) 1026 1026 ))) 1027 1027 1028 -==== 3.4.2.3 Requestan uplinkfrom the device====970 +==== 3.4.2.3 Poll an uplink ==== 1029 1029 1030 - 1031 1031 Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode. 1032 1032 1033 1033 (% style="color:#037691" %)**AT command** ... ... @@ -1047,7 +1047,6 @@ 1047 1047 1048 1048 ==== 3.4.2.4 Enable/Disable Trigger Mode ==== 1049 1049 1050 - 1051 1051 Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]). 1052 1052 1053 1053 (% style="color:#037691" %)**AT Command** ... ... @@ -1083,11 +1083,10 @@ 1083 1083 Enable trigger mode for the current working mode 1084 1084 ))) 1085 1085 1086 -==== 3.4.2.5 Requesttrigger settings ====1026 +==== 3.4.2.5 Poll trigger settings ==== 1087 1087 1028 +Polls the trigger settings. 1088 1088 1089 -Requests the trigger settings. 1090 - 1091 1091 (% style="color:#037691" %)**AT Command:** 1092 1092 1093 1093 There is no AT Command available for this feature. ... ... @@ -1105,7 +1105,6 @@ 1105 1105 1106 1106 ==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ==== 1107 1107 1108 - 1109 1109 Enable or disable DI1/DI2/DI3 as a trigger. 1110 1110 1111 1111 (% style="color:#037691" %)**AT Command** ... ... @@ -1160,9 +1160,9 @@ 1160 1160 1161 1161 ==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ==== 1162 1162 1163 - 1164 1164 Sets DI1 or DI3 (for LT-33222-L) as a trigger. 1165 1165 1103 + 1166 1166 (% style="color:#037691" %)**AT Command** 1167 1167 1168 1168 (% border="2" style="width:500px" %) ... ... @@ -1199,9 +1199,9 @@ 1199 1199 1200 1200 ==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ==== 1201 1201 1202 - 1203 1203 Sets DI2 as a trigger. 1204 1204 1142 + 1205 1205 (% style="color:#037691" %)**AT Command** 1206 1206 1207 1207 (% border="2" style="width:500px" %) ... ... @@ -1233,7 +1233,6 @@ 1233 1233 1234 1234 ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ==== 1235 1235 1236 - 1237 1237 Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1238 1238 1239 1239 (% style="color:#037691" %)**AT Command** ... ... @@ -1283,7 +1283,6 @@ 1283 1283 1284 1284 ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ==== 1285 1285 1286 - 1287 1287 Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] 1288 1288 1289 1289 (% style="color:#037691" %)**AT Command** ... ... @@ -1331,7 +1331,6 @@ 1331 1331 1332 1332 ==== 3.4.2.11 Trigger – Set minimum interval ==== 1333 1333 1334 - 1335 1335 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. 1336 1336 1337 1337 (% style="color:#037691" %)**AT Command** ... ... @@ -1367,7 +1367,6 @@ 1367 1367 1368 1368 ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ==== 1369 1369 1370 - 1371 1371 Controls the digital outputs DO1, DO2, and DO3 1372 1372 1373 1373 (% style="color:#037691" %)**AT Command** ... ... @@ -1398,11 +1398,11 @@ 1398 1398 ((( 1399 1399 01: Low, 00: High, 11: No action 1400 1400 1401 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:383px" %)1402 -|(% 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**1403 -| (% style="width:126px" %)02 01 00 11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action1404 -| (% style="width:126px" %)02 00 11 01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low1405 -| (% style="width:126px" %)02 11 01 00|(% style="width:85px" %)No Action|(% style="width:86px" %)Low|(% style="width:86px" %)High1335 +(% 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 1406 1406 ))) 1407 1407 1408 1408 ((( ... ... @@ -1419,81 +1419,80 @@ 1419 1419 ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ==== 1420 1420 1421 1421 1422 -(% style="color:#037691" %)**AT command**1356 +* (% style="color:#037691" %)**AT Command** 1423 1423 1424 -There is no AT command to controlthe digitaloutput.1358 +There is no AT Command to control Digital Output 1425 1425 1426 1426 1427 -(% style="color:#037691" %)**Downlink payload**1361 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)** 1428 1428 1363 +(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Set DO1/DO2/DO3 output with time control 1429 1429 1430 -(% border="2" style="width:500px" %) 1431 -|(% style="width:116px" %)**Prefix**|(% style="width:382px" %)0xA9 1432 -|(% style="width:116px" %)**Parameters**|(% style="width:382px" %)((( 1433 -**inverter_mode**: 1 byte in hex. 1434 1434 1435 -**01:** DO pins revert to their original state after the timeout. 1436 -**00:** DO pins switch to an inverted state after the timeout. 1366 +This is to control the digital output time of DO pin. Include four bytes: 1437 1437 1368 +(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9) 1438 1438 1439 - **DO1_control_method_and_port_status**-1 byteinhex1370 +(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode 1440 1440 1441 -0 x011setto low1372 +01: DO pins will change back to original state after timeout. 1442 1442 1443 -0 x00:1settohigh1374 +00: DO pins will change to an inverter state after timeout 1444 1444 1445 -0x11 : DO1 NO action 1446 1446 1377 +(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status: 1447 1447 1448 -**DO2_control_method_and_port_status** - 1 byte in hex 1379 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1380 +|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** 1381 +|0x01|DO1 set to low 1382 +|0x00|DO1 set to high 1383 +|0x11|DO1 NO Action 1449 1449 1450 - 0x01:DO2 set tolow1385 +(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status: 1451 1451 1452 -0x00 : DO2 set to high 1387 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1388 +|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** 1389 +|0x01|DO2 set to low 1390 +|0x00|DO2 set to high 1391 +|0x11|DO2 NO Action 1453 1453 1454 - 0x11:DO2NOaction1393 +(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status: 1455 1455 1395 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1396 +|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** 1397 +|0x01|DO3 set to low 1398 +|0x00|DO3 set to high 1399 +|0x11|DO3 NO Action 1456 1456 1457 - **DO3_control_method_and_port_status-1 byteinhex1401 +(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms) 1458 1458 1459 -0x01 : DO3 set to low 1460 1460 1461 - 0x00: DO3settohigh1404 +(% style="color:red" %)**Note: ** 1462 1462 1463 - 0x11:DO3NOaction1406 + Since firmware v1.6.0, the latch time support 4 bytes and 2 bytes 1464 1464 1408 + Before firmware v1.6.0, the latch time only supported 2 bytes. 1465 1465 1466 -**la tching_time**: 4 bytesinhex1410 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.** 1467 1467 1468 -(% style="color:red" %)**Note: ** 1469 1469 1470 - Since firmware v1.6.0, the latch timesupport 4 bytesor 2 bytes1413 +**Example payload:** 1471 1471 1472 - Before firmware v1.6.0,thelatchtimeonlysupported2bytes.1415 +**~1. A9 01 01 01 01 07 D0** 1473 1473 1474 -(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.** 1475 -))) 1476 -|(% style="width:116px" %)**Payload format**|(% style="width:382px" %)<prefix><inverter_mode><DO1_control_method_and_port_status><DO2_control_method_and_port_status><DO2_control_method_and_port_status><latching_time> 1477 -|(% style="width:116px" %)**Example**|(% style="width:382px" %)((( 1478 -**A9 01 01 01 01 07 D0** 1479 - 1480 1480 DO1 pin, DO2 pin, and DO3 pin will be set to low, last for 2 seconds, and then revert to their original state. 1481 1481 1419 +**2. A9 01 00 01 11 07 D0** 1482 1482 1483 -**A9 01 00 01 11 07 D0** 1484 - 1485 1485 DO1 pin is set to high, DO2 pin is set to low, and DO3 pin takes no action. This lasts for 2 seconds and then reverts to the original state. 1486 1486 1423 +**3. A9 00 00 00 00 07 D0** 1487 1487 1488 -**A9 00 00 00 00 07 D0** 1489 - 1490 1490 DO1 pin, DO2 pin, and DO3 pin will be set to high, last for 2 seconds, and then all change to low. 1491 1491 1427 +**4. A9 00 11 01 00 07 D0** 1492 1492 1493 -**A9 00 11 01 00 07 D0** 1494 - 1495 1495 DO1 pin takes no action, DO2 pin is set to low, and DO3 pin is set to high. This lasts for 2 seconds, after which DO1 pin takes no action, DO2 pin is set to high, and DO3 pin is set to low. 1496 -))) 1497 1497 1498 1498 1499 1499 ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ==== ... ... @@ -1501,16 +1501,16 @@ 1501 1501 1502 1502 * (% style="color:#037691" %)**AT Command:** 1503 1503 1504 -There is no AT Command to control theRelay Output1437 +There is no AT Command to control Relay Output 1505 1505 1506 1506 1507 1507 * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):** 1508 1508 1509 -(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set sRO1/RO2 output1442 +(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set RO1/RO2 output 1510 1510 1511 1511 1512 1512 ((( 1513 -If thepayload is 0x030100, it means setting RO1 to close and RO2 to open.1446 +If payload is 0x030100, it means setting RO1 to close and RO2 to open. 1514 1514 ))) 1515 1515 1516 1516 ((( ... ... @@ -1528,29 +1528,28 @@ 1528 1528 |03 00 01|Open|Close 1529 1529 ))) 1530 1530 1531 -(% style="color:red" %)** Thedevice will uplinka packet ifthedownlink code executes successfully.**1464 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1532 1532 1533 1533 1534 1534 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== 1535 1535 1536 - 1537 1537 Controls the relay output time. 1538 1538 1539 1539 * (% style="color:#037691" %)**AT Command:** 1540 1540 1541 -There is no AT Command to control theRelay Output1473 +There is no AT Command to control Relay Output 1542 1542 1543 1543 1544 1544 * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):** 1545 1545 1546 -(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set sRO1/RO2 relayswith time control1478 +(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set RO1/RO2 relay with time control 1547 1547 1548 1548 1549 -This control sthe relay output timeandincludes4bytes:1481 +This is to control the relay output time. It includes four bytes: 1550 1550 1551 -(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)1483 +(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05) 1552 1552 1553 -(% style="color:#4f81bd" %)**Second byte1485 +(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode 1554 1554 1555 1555 01: Relays will change back to their original state after timeout. 1556 1556 ... ... @@ -1557,12 +1557,12 @@ 1557 1557 00: Relays will change to the inverter state after timeout. 1558 1558 1559 1559 1560 -(% style="color:#4f81bd" %)**Third byte1492 +(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status: 1561 1561 1562 1562 [[image:image-20221008095908-1.png||height="364" width="564"]] 1563 1563 1564 1564 1565 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes1497 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms 1566 1566 1567 1567 1568 1568 (% style="color:red" %)**Note:** ... ... @@ -1572,7 +1572,7 @@ 1572 1572 Before firmware v1.6.0, the latch time only supported 2 bytes. 1573 1573 1574 1574 1575 -(% style="color:red" %)** Thedevice will uplinka packet if the downlink code executes successfully.**1507 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.** 1576 1576 1577 1577 1578 1578 **Example payload:** ... ... @@ -1731,9 +1731,8 @@ 1731 1731 ))) 1732 1732 |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01** 1733 1733 1734 -==== 3.4.2.19 Counting ~-~- Set SavingIntervalfor 'CountingResult'====1666 +==== 3.4.2.19 Counting ~-~- Change counting mode to save time ==== 1735 1735 1736 - 1737 1737 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. 1738 1738 1739 1739 (% style="color:#037691" %)**AT Command** ... ... @@ -1763,9 +1763,8 @@ 1763 1763 Sets the device to save its counting results to the memory every 60 seconds. 1764 1764 ))) 1765 1765 1766 -==== 3.4.2.20 Reset save dROandDO states====1697 +==== 3.4.2.20 Reset save RO DO state ==== 1767 1767 1768 - 1769 1769 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. 1770 1770 1771 1771 (% style="color:#037691" %)**AT Command** ... ... @@ -1790,6 +1790,7 @@ 1790 1790 After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network. 1791 1791 ))) 1792 1792 1723 + 1793 1793 (% style="color:#037691" %)**Downlink Payload** 1794 1794 1795 1795 (% border="2" style="width:500px" %) ... ... @@ -1815,7 +1815,6 @@ 1815 1815 1816 1816 ==== 3.4.2.21 Encrypted payload ==== 1817 1817 1818 - 1819 1819 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. 1820 1820 1821 1821 (% style="color:#037691" %)**AT Command:** ... ... @@ -1845,7 +1845,6 @@ 1845 1845 1846 1846 ==== 3.4.2.22 Get sensor value ==== 1847 1847 1848 - 1849 1849 This command allows you to retrieve and optionally uplink sensor readings through the serial port. 1850 1850 1851 1851 (% style="color:#037691" %)**AT Command** ... ... @@ -1875,7 +1875,6 @@ 1875 1875 1876 1876 ==== 3.4.2.23 Resetting the downlink packet count ==== 1877 1877 1878 - 1879 1879 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. 1880 1880 1881 1881 (% style="color:#037691" %)**AT Command** ... ... @@ -1954,33 +1954,43 @@ 1954 1954 1955 1955 ==== 3.4.2.25 Copy downlink to uplink ==== 1956 1956 1885 +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. 1957 1957 1958 - Thiscommandenableshe device to immediatelyuplink thepayload of a received downlink packet back tothe server.Thecommandallows for quick data replication from downlink to uplink, with a fixed port number of 100.1887 +* (% style="color:#037691" %)**AT Command**(%%)**:** 1959 1959 1960 -(% style="color: #037691" %)**ATCommand**(%%)**:**1889 +(% style="color:blue" %)**AT+RPL=5** (%%) ~/~/ After receiving the package from the server, it will immediately upload the content of the package to the server, the port number is 100. 1961 1961 1962 - (% style="color:blue" %)**AT+RPL=5**(%%)~/~/Afterreceivingadownlink payloadfromtherver,thedevice will immediately uplinkthe payloadback to the serverusingportnumber100.1891 +Example:**aa xx xx xx xx** ~/~/ aa indicates whether the configuration has changed, 00 is yes, 01 is no; xx xx xx xx are the bytes sent. 1963 1963 1964 -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. 1965 1965 1966 - 1967 1967 [[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"]] 1968 1968 1969 1969 For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77. 1970 1970 1971 -[[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"]] 1898 +(% border="2" style="width:500px" %) 1899 +|(% style="width:122px" %)**Command**|(% style="width:376px" %)((( 1900 +AT+RPL=5 1972 1972 1973 -For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. 1902 +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. 1903 +))) 1904 +|(% style="width:122px" %)**Example**|(% style="width:376px" %)((( 1905 +Downlink: 1974 1974 1907 +01 00 02 58 1975 1975 1976 - (% style="color:#037691" %)**DownlinkPayload**(%%)**:**1909 +Uplink: 1977 1977 1978 -There is no downlink option available for this feature. 1911 +01 01 00 02 58 1912 +))) 1979 1979 1914 +[[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"]] 1980 1980 1981 - ====3.4.2.26Queryfirmwareversion,frequency band,subband,andTDCtime====1916 +For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. 1982 1982 1983 1983 1919 + 1920 +==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ==== 1921 + 1984 1984 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. 1985 1985 1986 1986 * ((( ... ... @@ -1999,13 +1999,10 @@ 1999 1999 2000 2000 == 3.5 Integrating with ThingsEye.io == 2001 2001 2002 - 2003 2003 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. 2004 2004 2005 - 2006 2006 === 3.5.1 Configuring The Things Stack === 2007 2007 2008 - 2009 2009 We use The Things Stack Sandbox in this example: 2010 2010 2011 2011 * In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added. ... ... @@ -2017,12 +2017,10 @@ 2017 2017 The username and password (API key) you created here are required in the next section. 2018 2018 {{/info}} 2019 2019 2020 -[[image:tts-mqtt-integration.png]] 1955 +[[image:tts-mqtt-integration.png||height="625" width="1000"]] 2021 2021 2022 - 2023 2023 === 3.5.2 Configuring ThingsEye.io === 2024 2024 2025 - 2026 2026 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. 2027 2027 2028 2028 * Login to your [[ThingsEye.io >>https://thingseye.io]]account. ... ... @@ -2029,7 +2029,7 @@ 2029 2029 * Under the **Integrations center**, click **Integrations**. 2030 2030 * Click the **Add integration** button (the button with the **+** symbol). 2031 2031 2032 -[[image:thingseye-io-step-1.png]] 1965 +[[image:thingseye-io-step-1.png||height="625" width="1000"]] 2033 2033 2034 2034 2035 2035 On the **Add integration** window, configure the following: ... ... @@ -2044,7 +2044,7 @@ 2044 2044 ** Allow create devices or assets 2045 2045 * Click the **Next** button. you will be navigated to the **Uplink data converter** tab. 2046 2046 2047 -[[image:thingseye-io-step-2.png]] 1980 +[[image:thingseye-io-step-2.png||height="625" width="1000"]] 2048 2048 2049 2049 2050 2050 **Uplink data converter:** ... ... @@ -2055,7 +2055,7 @@ 2055 2055 * 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]]. 2056 2056 * Click the **Next** button. You will be navigated to the **Downlink data converter **tab. 2057 2057 2058 -[[image:thingseye-io-step-3.png]] 1991 +[[image:thingseye-io-step-3.png||height="625" width="1000"]] 2059 2059 2060 2060 2061 2061 **Downlink data converter (this is an optional step):** ... ... @@ -2066,7 +2066,7 @@ 2066 2066 * 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]]. 2067 2067 * Click the **Next** button. You will be navigated to the **Connection** tab. 2068 2068 2069 -[[image:thingseye-io-step-4.png]] 2002 +[[image:thingseye-io-step-4.png||height="625" width="1000"]] 2070 2070 2071 2071 2072 2072 **Connection:** ... ... @@ -2081,21 +2081,20 @@ 2081 2081 2082 2082 * Click the **Add** button. 2083 2083 2084 -[[image:thingseye-io-step-5.png]] 2017 +[[image:thingseye-io-step-5.png||height="625" width="1000"]] 2085 2085 2086 2086 2087 2087 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. 2088 2088 2089 2089 2090 -[[image:thingseye.io_integrationsCenter_integrations.png]] 2023 +[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]] 2091 2091 2092 2092 2093 2093 ==== 3.5.2.1 Viewing integration details ==== 2094 2094 2095 - 2096 2096 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. 2097 2097 2098 -[[image:integration-details.png]] 2030 +[[image:integration-details.png||height="686" width="1000"]] 2099 2099 2100 2100 2101 2101 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. ... ... @@ -2104,32 +2104,28 @@ 2104 2104 See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]]. 2105 2105 {{/info}} 2106 2106 2039 +==== **3.5.2.2 Viewing events** ==== 2107 2107 2108 -==== 3.5.2.2 Viewing events ==== 2109 - 2110 - 2111 2111 The **Events **tab displays all the uplink messages from the LT-22222-L. 2112 2112 2113 2113 * Select **Debug **from the **Event type** dropdown. 2114 2114 * Select the** time frame** from the **time window**. 2115 2115 2116 -[[image:thingseye-events.png]] 2046 +[[image:thingseye-events.png||height="686" width="1000"]] 2117 2117 2118 2118 2119 2119 * To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message. 2120 2120 2121 -[[image:thingseye-json.png]] 2051 +[[image:thingseye-json.png||width="1000"]] 2122 2122 2123 2123 2124 -==== 3.5.2.3 Deleting an integration ==== 2054 +==== **3.5.2.3 Deleting an integration** ==== 2125 2125 2126 - 2127 2127 If you want to delete an integration, click the **Delete integratio**n button on the Integrations page. 2128 2128 2129 2129 2130 2130 ==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ==== 2131 2131 2132 - 2133 2133 This will be added soon. 2134 2134 2135 2135 ... ... @@ -2138,7 +2138,7 @@ 2138 2138 === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) === 2139 2139 2140 2140 2141 -Supports **NPN-type**sensors.2069 +Supports NPN-type sensors. 2142 2142 2143 2143 [[image:1653356991268-289.png]] 2144 2144 ... ... @@ -2260,15 +2260,15 @@ 2260 2260 ))) 2261 2261 2262 2262 2263 -(% style="color:blue" %)**Example aDry Contact sensor2191 +(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor 2264 2264 2265 -From the DI port circuit above, activating the photocoupler requires a voltage difference between the DI+ and DI- ports. However, the Dry Contact sensor is a passive component and cannot provide this voltage difference on its own.2193 +From the DI port circuit above, you can see that activating the photocoupler requires a voltage difference between the DI+ and DI- ports. However, the Dry Contact sensor is a passive component and cannot provide this voltage difference. 2266 2266 2267 -To detect a Dry Contact, you can supply a power source to one of thepinsof the Dry Contact.Areference circuit diagramis shown below.2195 +To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram. 2268 2268 2269 2269 [[image:image-20230616235145-1.png]] 2270 2270 2271 -(% style="color:blue" %)**Example 2199 +(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector 2272 2272 2273 2273 [[image:image-20240219115718-1.png]] 2274 2274 ... ... @@ -2344,9 +2344,8 @@ 2344 2344 [[image:image-20220524100215-10.png||height="382" width="723"]] 2345 2345 2346 2346 2347 -== 3.7 LED Indicators == 2275 +== 3.7 LEDs Indicators == 2348 2348 2349 - 2350 2350 The table below lists the behavior of LED indicators for each port function. 2351 2351 2352 2352 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) ... ... @@ -2379,22 +2379,18 @@ 2379 2379 2380 2380 = 4. Using AT Commands = 2381 2381 2382 - 2383 2383 The LT-22222-L supports programming using AT Commands. 2384 2384 2385 - 2386 2386 == 4.1 Connecting the LT-22222-L to a PC == 2387 2387 2388 - 2389 2389 ((( 2390 -You can use a USB-to-TTL adapter /converteralong with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below.2314 +You can use a USB-to-TTL adapter along with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below. 2391 2391 2392 -[[image:usb-ttl-audio-jack-connection.jpg]] 2393 - 2394 - 2316 +[[image:usb-ttl-programming.png]] 2395 2395 ))) 2396 2396 2397 2397 2320 + 2398 2398 ((( 2399 2399 On the PC, you need to set the (% style="color:#4f81bd" %)**serial tool **(%%)(such as [[PuTTY>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]] or [[SecureCRT>>https://www.vandyke.com/cgi-bin/releases.php?product=securecrt]]) to a baud rate of (% style="color:green" %)**9600**(%%) to access the serial console of LT-22222-L. Access to AT commands is disabled by default, and a password (default: (% style="color:green" %)**123456**)(%%) must be entered to enable AT command access, as shown below: 2400 2400 ))) ... ... @@ -2405,10 +2405,7 @@ 2405 2405 ((( 2406 2406 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/]] 2407 2407 2408 - 2409 2409 == 4.2 LT-22222-L related AT commands == 2410 - 2411 - 2412 2412 ))) 2413 2413 2414 2414 ((( ... ... @@ -2427,39 +2427,39 @@ 2427 2427 * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey) 2428 2428 * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI) 2429 2429 * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON) 2430 -* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)2431 -* **##AT+DR##**: Get or set the Data Rate. (0-7 corresponding to DR_X)2432 -* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing2433 -* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)2434 -* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency2435 -* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)2436 -* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms2437 -* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms2438 -* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms2439 -* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms2440 -* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)2441 -* ##**AT+NWKID**##: Get or set the Network ID2442 -* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)2443 -* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)2444 -* ##**AT+CLASS**##: Get or set the Device Class2445 -* ##**AT+JOIN**##: Join network2446 -* ##**AT+NJS**##: Get OTAA Join Status2447 -* ##**AT+SENDB**##: Send hexadecimal data along with the application port2448 -* ##**AT+SEND**##: Send text data along with the application port2449 -* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)2450 -* ##**AT+RECV**##: Print last received data in raw format2451 -* ##**AT+VER**##: Get current image version and Frequency Band2452 -* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)2453 -* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)2454 -* ##**AT+SNR**##: Get the SNR of the last received packet2455 -* ##**AT+RSSI**##: Get the RSSI of the last received packet2456 -* ##**AT+TDC**##: Get or set the application data transmission interval in ms2457 -* ##**AT+PORT**##: Get or set the application port2458 -* ##**AT+DISAT**##: Disable AT commands2459 -* ##**AT+PWORD**##: Set password, max 9 digits2460 -* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode2461 -* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN4702462 -* ##**AT+CFG**##: Print all settings2350 +* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification) 2351 +* AT+DR: Get or set the Data Rate. (0-7 corresponding to DR_X) 2352 +* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing 2353 +* AT+PNM: Get or set the public network mode. (0: off, 1: on) 2354 +* AT+RX2FQ: Get or set the Rx2 window frequency 2355 +* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X) 2356 +* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms 2357 +* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms 2358 +* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms 2359 +* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms 2360 +* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA) 2361 +* AT+NWKID: Get or set the Network ID 2362 +* AT+FCU: Get or set the Frame Counter Uplink (FCntUp) 2363 +* AT+FCD: Get or set the Frame Counter Downlink (FCntDown) 2364 +* AT+CLASS: Get or set the Device Class 2365 +* AT+JOIN: Join network 2366 +* AT+NJS: Get OTAA Join Status 2367 +* AT+SENDB: Send hexadecimal data along with the application port 2368 +* AT+SEND: Send text data along with the application port 2369 +* AT+RECVB: Print last received data in binary format (with hexadecimal values) 2370 +* AT+RECV: Print last received data in raw format 2371 +* AT+VER: Get current image version and Frequency Band 2372 +* AT+CFM: Get or Set the confirmation mode (0-1) 2373 +* AT+CFS: Get confirmation status of the last AT+SEND (0-1) 2374 +* AT+SNR: Get the SNR of the last received packet 2375 +* AT+RSSI: Get the RSSI of the last received packet 2376 +* AT+TDC: Get or set the application data transmission interval in ms 2377 +* AT+PORT: Get or set the application port 2378 +* AT+DISAT: Disable AT commands 2379 +* AT+PWORD: Set password, max 9 digits 2380 +* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode 2381 +* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470 2382 +* AT+CFG: Print all settings 2463 2463 ))) 2464 2464 2465 2465 ... ... @@ -2605,19 +2605,16 @@ 2605 2605 2606 2606 == 5.1 Counting how many objects pass through the flow line == 2607 2607 2608 - 2609 2609 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]]? 2610 2610 2611 2611 2612 2612 = 6. FAQ = 2613 2613 2614 - 2615 2615 This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly. 2616 2616 2617 2617 2618 2618 == 6.1 How to update the firmware? == 2619 2619 2620 - 2621 2621 Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to: 2622 2622 2623 2623 * Support new features ... ... @@ -2627,7 +2627,7 @@ 2627 2627 You will need the following things before proceeding: 2628 2628 2629 2629 * 3.5mm programming cable (included with the LT-22222-L as an additional accessory) 2630 -* USB to TTL adapter /converter2547 +* USB to TTL adapter 2631 2631 * Download and install the [[STM32 Flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]]. (replaced by STM32CubeProgrammer) 2632 2632 * Download the latest firmware image from [[LT-22222-L firmware image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]]. Check the file name of the firmware to find the correct region. 2633 2633 ... ... @@ -2637,7 +2637,7 @@ 2637 2637 2638 2638 Below is the hardware setup for uploading a firmware image to the LT-22222-L: 2639 2639 2640 -[[image:usb-ttl- audio-jack-connection.jpg]]2557 +[[image:usb-ttl-programming.png]] 2641 2641 2642 2642 2643 2643 ... ... @@ -2670,8 +2670,6 @@ 2670 2670 ((( 2671 2671 ((( 2672 2672 == 6.2 How to change the LoRaWAN frequency band/region? == 2673 - 2674 - 2675 2675 ))) 2676 2676 ))) 2677 2677 ... ... @@ -2683,8 +2683,6 @@ 2683 2683 2684 2684 2685 2685 == 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? == 2686 - 2687 - 2688 2688 ))) 2689 2689 2690 2690 ((( ... ... @@ -2758,13 +2758,11 @@ 2758 2758 2759 2759 == 6.4 How to change the uplink interval? == 2760 2760 2761 - 2762 2762 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/]] 2763 2763 2764 2764 2765 2765 == 6.5 Can I see the counting event in the serial output? == 2766 2766 2767 - 2768 2768 ((( 2769 2769 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. 2770 2770 ... ... @@ -2771,7 +2771,6 @@ 2771 2771 2772 2772 == 6.6 Can I use point-to-point communication with LT-22222-L? == 2773 2773 2774 - 2775 2775 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]]. 2776 2776 2777 2777 ... ... @@ -2780,7 +2780,6 @@ 2780 2780 ((( 2781 2781 == 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? == 2782 2782 2783 - 2784 2784 * If the device is not properly shut down and is directly powered off. 2785 2785 * It will default to a power-off state. 2786 2786 * In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory. ... ... @@ -2788,7 +2788,6 @@ 2788 2788 2789 2789 == 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? == 2790 2790 2791 - 2792 2792 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: 2793 2793 2794 2794 ... ... @@ -2797,19 +2797,16 @@ 2797 2797 2798 2798 == 6.9 Can the LT-22222-L save the RO state? == 2799 2799 2800 - 2801 2801 To enable this feature, the firmware version must be 1.6.0 or higher. 2802 2802 2803 2803 2804 2804 == 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? == 2805 2805 2806 - 2807 2807 It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose. 2808 2808 2809 2809 2810 2810 = 7. Troubleshooting = 2811 2811 2812 - 2813 2813 This section provides some known troubleshooting tips. 2814 2814 2815 2815 ... ... @@ -2818,8 +2818,6 @@ 2818 2818 ((( 2819 2819 ((( 2820 2820 == 7.1 Downlink isn't working. How can I solve this? == 2821 - 2822 - 2823 2823 ))) 2824 2824 ))) 2825 2825 ... ... @@ -2831,8 +2831,6 @@ 2831 2831 2832 2832 2833 2833 == 7.2 Having trouble uploading an image? == 2834 - 2835 - 2836 2836 ))) 2837 2837 2838 2838 ((( ... ... @@ -2843,8 +2843,6 @@ 2843 2843 2844 2844 2845 2845 == 7.3 Why can't I join TTN in the US915 /AU915 bands? == 2846 - 2847 - 2848 2848 ))) 2849 2849 2850 2850 ((( ... ... @@ -2854,7 +2854,6 @@ 2854 2854 2855 2855 == 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? == 2856 2856 2857 - 2858 2858 The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue. 2859 2859 Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]] 2860 2860 ... ... @@ -2861,7 +2861,6 @@ 2861 2861 2862 2862 = 8. Ordering information = 2863 2863 2864 - 2865 2865 (% style="color:#4f81bd" %)**LT-22222-L-XXX:** 2866 2866 2867 2867 (% style="color:#4f81bd" %)**XXX:** ... ... @@ -2878,7 +2878,6 @@ 2878 2878 2879 2879 = 9. Package information = 2880 2880 2881 - 2882 2882 **Package includes**: 2883 2883 2884 2884 * 1 x LT-22222-L I/O Controller ... ... @@ -2895,7 +2895,6 @@ 2895 2895 2896 2896 = 10. Support = 2897 2897 2898 - 2899 2899 * ((( 2900 2900 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. 2901 2901 ))) ... ... @@ -2907,7 +2907,6 @@ 2907 2907 2908 2908 = 11. Reference = 2909 2909 2910 - 2911 2911 * 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]] 2912 2912 * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]] 2913 2913 * [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]
- Screenshot 2024-12-08 193946.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -32.4 KB - Content
- lt-22222-l-joining.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -301.9 KB - Content
- lt-22222-l-js-custom-payload-formatter.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -453.9 KB - Content
- lt33222-l.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.3 KB - Content
- usb-ttl-audio-jack-connection.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -394.4 KB - Content