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
-
... ... @@ -76,8 +76,6 @@ 76 76 ))) 77 77 78 78 ((( 79 - 80 - 81 81 **Interface for Model: LT22222-L:** 82 82 ))) 83 83 ... ... @@ -101,8 +101,6 @@ 101 101 ))) 102 102 103 103 ((( 104 - 105 - 106 106 **LoRa Spec:** 107 107 ))) 108 108 ... ... @@ -166,8 +166,6 @@ 166 166 167 167 ))) 168 168 169 - 170 - 171 171 == 1.3 Features == 172 172 173 173 * LoRaWAN Class A & Class C protocol ... ... @@ -178,8 +178,6 @@ 178 178 * Firmware upgradable via program port 179 179 * Counting 180 180 181 - 182 - 183 183 == 1.4 Applications == 184 184 185 185 * Smart Buildings & Home Automation ... ... @@ -189,8 +189,6 @@ 189 189 * Smart Cities 190 190 * Smart Factory 191 191 192 - 193 - 194 194 == 1.5 Hardware Variants == 195 195 196 196 (% border="1" style="background-color:#f7faff; width:500px" %) ... ... @@ -204,7 +204,6 @@ 204 204 * 1 x Counting Port 205 205 ))) 206 206 207 - 208 208 = 2. Power ON Device = 209 209 210 210 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. ... ... @@ -227,9 +227,12 @@ 227 227 228 228 ((( 229 229 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 + 230 230 ))) 231 231 232 232 224 + 233 233 == 3.2 Example to join LoRaWAN network == 234 234 235 235 ((( ... ... @@ -238,13 +238,12 @@ 238 238 239 239 [[image:image-20220523172350-1.png||height="266" width="864"]] 240 240 241 - 242 242 ((( 243 243 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: 244 244 ))) 245 245 246 246 ((( 247 - (% 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. 248 248 ))) 249 249 250 250 ((( ... ... @@ -253,7 +253,6 @@ 253 253 254 254 [[image:1653297924498-393.png]] 255 255 256 - 257 257 Input these keys in the LoRaWAN Server portal. Below is TTN screen shot: 258 258 259 259 Add APP EUI in the application. ... ... @@ -267,7 +267,7 @@ 267 267 268 268 269 269 ((( 270 - (% 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. 271 271 ))) 272 272 273 273 [[image:1653298044601-602.png||height="405" width="709"]] ... ... @@ -285,7 +285,6 @@ 285 285 * **MOD5**: Single DI Counting + 2 x AVI + 1 x ACI + DO + RO 286 286 * **ADDMOD6**: Trigger Mode, Optional, used together with MOD1 ~~ MOD5 287 287 288 - 289 289 === 3.3.1 AT+MOD~=1, 2ACI+2AVI === 290 290 291 291 The uplink payload includes totally 9 bytes. Uplink packets use FPORT=2 and every 10 minutes send one uplink by default. ... ... @@ -293,8 +293,6 @@ 293 293 [[image:image-20220523174024-3.png]] 294 294 295 295 ((( 296 - 297 - 298 298 (% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below 299 299 ))) 300 300 ... ... @@ -308,7 +308,6 @@ 308 308 309 309 For example if payload is: [[image:image-20220523175847-2.png]] 310 310 311 - 312 312 **The value for the interface is: ** 313 313 314 314 AVI1 channel voltage is 0x04AB/1000=1195（DEC）/1000=1.195V ... ... @@ -340,6 +340,7 @@ 340 340 ** DO1 LED is off in both case 341 341 342 342 329 + 343 343 === 3.3.2 AT+MOD~=2, (Double DI Counting) === 344 344 345 345 ... ... @@ -632,11 +632,13 @@ 632 632 * **AT+MOD=1 ** **~-~->** The normal working mode 633 633 * **AT+ADDMOD6=1** **~-~->** Enable trigger 634 634 622 + 635 635 LT will keep monitoring AV1/AV2/AC1/AC2 every 5 seconds; LT will send uplink packets in two cases: 636 636 637 637 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 638 638 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.** 639 639 628 + 640 640 **AT Command to set Trigger Condition**: 641 641 642 642 (% style="color:#4f81bd" %)**Trigger base on voltage**: ... ... @@ -650,7 +650,6 @@ 650 650 AT+AVLIM=5000,0,0,0 (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore) 651 651 652 652 653 - 654 654 (% style="color:#4f81bd" %)**Trigger base on current**: 655 655 656 656 Format: AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH> ... ... @@ -660,7 +660,6 @@ 660 660 AT+ACLIM=10000,15000,0,0 (If ACI1 voltage lower than 10mA or higher than 15mA, trigger an uplink) 661 661 662 662 663 - 664 664 (% style="color:#4f81bd" %)**Trigger base on DI status**: 665 665 666 666 DI status trigger Flag. ... ... @@ -667,13 +667,12 @@ 667 667 668 668 Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG > 669 669 670 - 671 671 **Example:** 672 672 673 673 AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 674 674 675 675 676 -**Downlink Command to set Trigger Condition :**662 +**Downlink Command to set Trigger Condition** 677 677 678 678 Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 679 679 ... ... @@ -702,7 +702,6 @@ 702 702 Same as AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 703 703 704 704 705 - 706 706 (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:** 707 707 708 708 MOD6 Payload : total 11 bytes payload ... ... @@ -716,6 +716,7 @@ 716 716 717 717 * Each bits shows if the corresponding trigger has been configured. 718 718 704 + 719 719 **Example:** 720 720 721 721 10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW ... ... @@ -727,6 +727,7 @@ 727 727 728 728 * Each bits shows which status has been trigger on this uplink. 729 729 716 + 730 730 **Example:** 731 731 732 732 10000000: Means this packet is trigger by AC1_LOW. Means voltage too low. ... ... @@ -738,6 +738,7 @@ 738 738 739 739 * Each bits shows which status has been trigger on this uplink. 740 740 728 + 741 741 **Example:** 742 742 743 743 00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1. ... ... @@ -779,6 +779,8 @@ 779 779 780 780 * (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L. User can see these commands below: 781 781 770 + 771 + 782 782 === 3.4.1 Common Commands === 783 783 784 784 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]]