Changes for page LT-22222-L -- LoRa I/O Controller User Manual
Last modified by Saxer Lin on 2025/04/15 17:24
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -19,6 +19,8 @@ 19 19 == 1.1 What is LT Series I/O Controller == 20 20 21 21 ((( 22 + 23 + 22 22 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. 23 23 ))) 24 24 ... ... @@ -48,6 +48,7 @@ 48 48 49 49 ))) 50 50 53 + 51 51 == 1.2 Specifications == 52 52 53 53 ((( ... ... @@ -76,6 +76,8 @@ 76 76 ))) 77 77 78 78 ((( 82 + 83 + 79 79 **Interface for Model: LT22222-L:** 80 80 ))) 81 81 ... ... @@ -99,6 +99,8 @@ 99 99 ))) 100 100 101 101 ((( 107 + 108 + 102 102 **LoRa Spec:** 103 103 ))) 104 104 ... ... @@ -159,6 +159,8 @@ 159 159 * ((( 160 160 Packet engine up to 256 bytes with CRC. 161 161 169 + 170 + 162 162 163 163 ))) 164 164 ... ... @@ -172,6 +172,9 @@ 172 172 * Firmware upgradable via program port 173 173 * Counting 174 174 184 + 185 + 186 + 175 175 == 1.4 Applications == 176 176 177 177 * Smart Buildings & Home Automation ... ... @@ -181,6 +181,9 @@ 181 181 * Smart Cities 182 182 * Smart Factory 183 183 196 + 197 + 198 + 184 184 == 1.5 Hardware Variants == 185 185 186 186 (% border="1" style="background-color:#f7faff; width:500px" %) ... ... @@ -194,6 +194,8 @@ 194 194 * 1 x Counting Port 195 195 ))) 196 196 212 + 213 + 197 197 = 2. Power ON Device = 198 198 199 199 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. ... ... @@ -216,12 +216,9 @@ 216 216 217 217 ((( 218 218 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 - 221 221 ))) 222 222 223 223 224 - 225 225 == 3.2 Example to join LoRaWAN network == 226 226 227 227 ((( ... ... @@ -230,12 +230,13 @@ 230 230 231 231 [[image:image-20220523172350-1.png||height="266" width="864"]] 232 232 247 + 233 233 ((( 234 234 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: 235 235 ))) 236 236 237 237 ((( 238 - **(% style="color:blue" %)Step 1**(%%): Create a device in TTN with the OTAA keys from LT IO controller.253 +(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LT IO controller. 239 239 ))) 240 240 241 241 ((( ... ... @@ -244,6 +244,7 @@ 244 244 245 245 [[image:1653297924498-393.png]] 246 246 262 + 247 247 Input these keys in the LoRaWAN Server portal. Below is TTN screen shot: 248 248 249 249 Add APP EUI in the application. ... ... @@ -257,7 +257,7 @@ 257 257 258 258 259 259 ((( 260 - **(% 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.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. 261 261 ))) 262 262 263 263 [[image:1653298044601-602.png||height="405" width="709"]] ... ... @@ -277,6 +277,7 @@ 277 277 278 278 279 279 296 + 280 280 === 3.3.1 AT+MOD~=1, 2ACI+2AVI === 281 281 282 282 The uplink payload includes totally 9 bytes. Uplink packets use FPORT=2 and every 10 minutes send one uplink by default. ... ... @@ -315,8 +315,6 @@ 315 315 * [1] RO1 relay channel is close and the RO1 LED is ON. 316 316 * [0] RO2 relay channel is open and RO2 LED is OFF; 317 317 318 - 319 - 320 320 **LT22222-L:** 321 321 322 322 * [1] DI2 channel is high input and DI2 LED is ON; ... ... @@ -332,8 +332,6 @@ 332 332 ** DO1 is high in case there is load between DO1 and V+. 333 333 ** DO1 LED is off in both case 334 334 335 - 336 - 337 337 === 3.3.2 AT+MOD~=2, (Double DI Counting) === 338 338 339 339 ... ... @@ -474,11 +474,10 @@ 474 474 475 475 ((( 476 476 Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]. 477 - 478 - 479 479 ))) 480 480 481 481 493 + 482 482 === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting === 483 483 484 484 ... ... @@ -626,14 +626,11 @@ 626 626 * **AT+MOD=1 ** **~-~->** The normal working mode 627 627 * **AT+ADDMOD6=1** **~-~->** Enable trigger 628 628 629 - 630 630 LT will keep monitoring AV1/AV2/AC1/AC2 every 5 seconds; LT will send uplink packets in two cases: 631 631 632 632 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 633 633 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.** 634 634 635 - 636 - 637 637 **AT Command to set Trigger Condition**: 638 638 639 639 (% style="color:#4f81bd" %)**Trigger base on voltage**: ... ... @@ -713,8 +713,6 @@ 713 713 714 714 * Each bits shows if the corresponding trigger has been configured. 715 715 716 - 717 - 718 718 **Example:** 719 719 720 720 10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW ... ... @@ -726,8 +726,6 @@ 726 726 727 727 * Each bits shows which status has been trigger on this uplink. 728 728 729 - 730 - 731 731 **Example:** 732 732 733 733 10000000: Means this packet is trigger by AC1_LOW. Means voltage too low. ... ... @@ -739,8 +739,6 @@ 739 739 740 740 * Each bits shows which status has been trigger on this uplink. 741 741 742 - 743 - 744 744 **Example:** 745 745 746 746 00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1. ... ... @@ -769,7 +769,6 @@ 769 769 ))) 770 770 771 771 772 - 773 773 == 3.4 Configure LT via AT or Downlink == 774 774 775 775 User can configure LT I/O Controller via AT Commands or LoRaWAN Downlink Commands ... ... @@ -782,8 +782,6 @@ 782 782 783 783 * (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L. User can see these commands below: 784 784 785 - 786 - 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,8 +2015,16 @@ 2015 2015 ))) 2016 2016 2017 2017 ((( 2018 - 2018 +== 5.6 Why does the relay output become the default and open relay after the lt22222 is powered off? == 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 + 2020 2020 = 6. Trouble Shooting = 2021 2021 ))) 2022 2022