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)
Details
- Page properties
-
- Content
-
... ... @@ -19,8 +19,6 @@ 19 19 == 1.1 What is LT Series I/O Controller == 20 20 21 21 ((( 22 - 23 - 24 24 The Dragino (% style="color:blue" %)**LT series I/O Modules**(%%) are Long Range LoRaWAN I/O Controller. It contains different I/O Interfaces such as:** (% style="color:blue" %)analog current Input, analog voltage input(%%)**(% style="color:blue" %), **relay output**, **digital input**(%%) and (% style="color:blue" %)**digital output**(%%) etc. The LT I/O Modules are designed to simplify the installation of I/O monitoring. 25 25 ))) 26 26 ... ... @@ -50,7 +50,6 @@ 50 50 51 51 ))) 52 52 53 - 54 54 == 1.2 Specifications == 55 55 56 56 ((( ... ... @@ -79,8 +79,6 @@ 79 79 ))) 80 80 81 81 ((( 82 - 83 - 84 84 **Interface for Model: LT22222-L:** 85 85 ))) 86 86 ... ... @@ -104,8 +104,6 @@ 104 104 ))) 105 105 106 106 ((( 107 - 108 - 109 109 **LoRa Spec:** 110 110 ))) 111 111 ... ... @@ -166,8 +166,6 @@ 166 166 * ((( 167 167 Packet engine up to 256 bytes with CRC. 168 168 169 - 170 - 171 171 172 172 ))) 173 173 ... ... @@ -181,9 +181,6 @@ 181 181 * Firmware upgradable via program port 182 182 * Counting 183 183 184 - 185 - 186 - 187 187 == 1.4 Applications == 188 188 189 189 * Smart Buildings & Home Automation ... ... @@ -193,9 +193,6 @@ 193 193 * Smart Cities 194 194 * Smart Factory 195 195 196 - 197 - 198 - 199 199 == 1.5 Hardware Variants == 200 200 201 201 (% border="1" style="background-color:#f7faff; width:500px" %) ... ... @@ -209,8 +209,6 @@ 209 209 * 1 x Counting Port 210 210 ))) 211 211 212 - 213 - 214 214 = 2. Power ON Device = 215 215 216 216 The LT controller can be powered by 7 ~~ 24V DC power source. Connect VIN to Power Input V+ and GND to power input V- to power the LT controller. ... ... @@ -233,9 +233,12 @@ 233 233 234 234 ((( 235 235 In case user can’t set the OTAA keys in the network server and has to use the existing keys from server. User can [[use AT Command>>||anchor="H4.UseATCommand"]] to set the keys in the devices. 219 + 220 + 236 236 ))) 237 237 238 238 224 + 239 239 == 3.2 Example to join LoRaWAN network == 240 240 241 241 ((( ... ... @@ -244,13 +244,12 @@ 244 244 245 245 [[image:image-20220523172350-1.png||height="266" width="864"]] 246 246 247 - 248 248 ((( 249 249 The LG308 is already set to connect to [[TTN network >>url:https://www.thethingsnetwork.org/]]. So what we need to do now is only configure register this device to TTN: 250 250 ))) 251 251 252 252 ((( 253 - (% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LT IO controller.238 +**Step 1**: Create a device in TTN with the OTAA keys from LT IO controller. 254 254 ))) 255 255 256 256 ((( ... ... @@ -259,7 +259,6 @@ 259 259 260 260 [[image:1653297924498-393.png]] 261 261 262 - 263 263 Input these keys in the LoRaWAN Server portal. Below is TTN screen shot: 264 264 265 265 Add APP EUI in the application. ... ... @@ -273,7 +273,7 @@ 273 273 274 274 275 275 ((( 276 - (% style="color:blue" %)**Step 2**(%%): Power on LT and it will auto join to the TTN network. After join success, it will start to upload message to TTN and user can see in the panel.260 +**Step 2**: Power on LT and it will auto join to the TTN network. After join success, it will start to upload message to TTN and user can see in the panel. 277 277 ))) 278 278 279 279 [[image:1653298044601-602.png||height="405" width="709"]] ... ... @@ -292,8 +292,6 @@ 292 292 * **ADDMOD6**: Trigger Mode, Optional, used together with MOD1 ~~ MOD5 293 293 294 294 295 - 296 - 297 297 === 3.3.1 AT+MOD~=1, 2ACI+2AVI === 298 298 299 299 The uplink payload includes totally 9 bytes. Uplink packets use FPORT=2 and every 10 minutes send one uplink by default. ... ... @@ -332,6 +332,8 @@ 332 332 * [1] RO1 relay channel is close and the RO1 LED is ON. 333 333 * [0] RO2 relay channel is open and RO2 LED is OFF; 334 334 317 + 318 + 335 335 **LT22222-L:** 336 336 337 337 * [1] DI2 channel is high input and DI2 LED is ON; ... ... @@ -347,6 +347,8 @@ 347 347 ** DO1 is high in case there is load between DO1 and V+. 348 348 ** DO1 LED is off in both case 349 349 334 + 335 + 350 350 === 3.3.2 AT+MOD~=2, (Double DI Counting) === 351 351 352 352 ... ... @@ -487,10 +487,11 @@ 487 487 488 488 ((( 489 489 Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]. 476 + 477 + 490 490 ))) 491 491 492 492 493 - 494 494 === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting === 495 495 496 496 ... ... @@ -638,11 +638,14 @@ 638 638 * **AT+MOD=1 ** **~-~->** The normal working mode 639 639 * **AT+ADDMOD6=1** **~-~->** Enable trigger 640 640 628 + 641 641 LT will keep monitoring AV1/AV2/AC1/AC2 every 5 seconds; LT will send uplink packets in two cases: 642 642 643 643 1. Periodically uplink (Base on TDC time). Payload is same as the normal MOD (MOD 1 for above command). This uplink uses LoRaWAN (% style="color:#4f81bd" %)**unconfirmed**(%%) data type 644 644 1. Trigger uplink when meet the trigger condition. LT will sent two packets in this case, the first uplink use payload specify in this mod (mod=6), the second packets use the normal mod payload(MOD=1 for above settings). Both Uplinks use LoRaWAN (% style="color:#4f81bd" %)**CONFIRMED data type.** 645 645 634 + 635 + 646 646 **AT Command to set Trigger Condition**: 647 647 648 648 (% style="color:#4f81bd" %)**Trigger base on voltage**: ... ... @@ -722,6 +722,8 @@ 722 722 723 723 * Each bits shows if the corresponding trigger has been configured. 724 724 715 + 716 + 725 725 **Example:** 726 726 727 727 10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW ... ... @@ -733,6 +733,8 @@ 733 733 734 734 * Each bits shows which status has been trigger on this uplink. 735 735 728 + 729 + 736 736 **Example:** 737 737 738 738 10000000: Means this packet is trigger by AC1_LOW. Means voltage too low. ... ... @@ -744,6 +744,8 @@ 744 744 745 745 * Each bits shows which status has been trigger on this uplink. 746 746 741 + 742 + 747 747 **Example:** 748 748 749 749 00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1. ... ... @@ -772,6 +772,7 @@ 772 772 ))) 773 773 774 774 771 + 775 775 == 3.4 Configure LT via AT or Downlink == 776 776 777 777 User can configure LT I/O Controller via AT Commands or LoRaWAN Downlink Commands ... ... @@ -784,6 +784,8 @@ 784 784 785 785 * (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L. User can see these commands below: 786 786 784 + 785 + 787 787 === 3.4.1 Common Commands === 788 788 789 789 They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.5.4, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]] ... ... @@ -2015,16 +2015,8 @@ 2015 2015 ))) 2016 2016 2017 2017 ((( 2018 - ==5.6 Why does the relay output become the default and open relay after the lt22222 is powered off? ==2017 + 2019 2019 2020 -If the device is not shut down, but directly powered off. 2021 - 2022 -It will default that this is a power-off state. 2023 - 2024 -In modes 2 to 5, DO RO status and pulse count are saved in flash. 2025 - 2026 -After restart, the status before power failure will be read from flash. 2027 - 2028 2028 = 6. Trouble Shooting = 2029 2029 ))) 2030 2030