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 ... ... @@ -162,10 +162,10 @@ 162 162 ))) 163 163 * ((( 164 164 Packet engine up to 256 bytes with CRC. 161 + 162 + 165 165 ))) 166 166 167 - 168 - 169 169 == 1.3 Features == 170 170 171 171 * LoRaWAN Class A & Class C protocol ... ... @@ -176,8 +176,6 @@ 176 176 * Firmware upgradable via program port 177 177 * Counting 178 178 179 - 180 - 181 181 == 1.4 Applications == 182 182 183 183 * Smart Buildings & Home Automation ... ... @@ -187,8 +187,6 @@ 187 187 * Smart Cities 188 188 * Smart Factory 189 189 190 - 191 - 192 192 == 1.5 Hardware Variants == 193 193 194 194 (% border="1" style="background-color:#f7faff; width:500px" %) ... ... @@ -202,7 +202,6 @@ 202 202 * 1 x Counting Port 203 203 ))) 204 204 205 - 206 206 = 2. Power ON Device = 207 207 208 208 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. ... ... @@ -225,9 +225,12 @@ 225 225 226 226 ((( 227 227 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 + 228 228 ))) 229 229 230 230 224 + 231 231 == 3.2 Example to join LoRaWAN network == 232 232 233 233 ((( ... ... @@ -236,13 +236,12 @@ 236 236 237 237 [[image:image-20220523172350-1.png||height="266" width="864"]] 238 238 239 - 240 240 ((( 241 241 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: 242 242 ))) 243 243 244 244 ((( 245 - (% 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. 246 246 ))) 247 247 248 248 ((( ... ... @@ -251,7 +251,6 @@ 251 251 252 252 [[image:1653297924498-393.png]] 253 253 254 - 255 255 Input these keys in the LoRaWAN Server portal. Below is TTN screen shot: 256 256 257 257 Add APP EUI in the application. ... ... @@ -265,7 +265,7 @@ 265 265 266 266 267 267 ((( 268 - (% 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. 269 269 ))) 270 270 271 271 [[image:1653298044601-602.png||height="405" width="709"]] ... ... @@ -283,7 +283,6 @@ 283 283 * **MOD5**: Single DI Counting + 2 x AVI + 1 x ACI + DO + RO 284 284 * **ADDMOD6**: Trigger Mode, Optional, used together with MOD1 ~~ MOD5 285 285 286 - 287 287 === 3.3.1 AT+MOD~=1, 2ACI+2AVI === 288 288 289 289 The uplink payload includes totally 9 bytes. Uplink packets use FPORT=2 and every 10 minutes send one uplink by default. ... ... @@ -291,8 +291,6 @@ 291 291 [[image:image-20220523174024-3.png]] 292 292 293 293 ((( 294 - 295 - 296 296 (% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below 297 297 ))) 298 298 ... ... @@ -306,7 +306,6 @@ 306 306 307 307 For example if payload is: [[image:image-20220523175847-2.png]] 308 308 309 - 310 310 **The value for the interface is: ** 311 311 312 312 AVI1 channel voltage is 0x04AB/1000=1195（DEC）/1000=1.195V ... ... @@ -338,6 +338,7 @@ 338 338 ** DO1 LED is off in both case 339 339 340 340 329 + 341 341 === 3.3.2 AT+MOD~=2, (Double DI Counting) === 342 342 343 343 ... ... @@ -630,11 +630,13 @@ 630 630 * **AT+MOD=1 ** **~-~->** The normal working mode 631 631 * **AT+ADDMOD6=1** **~-~->** Enable trigger 632 632 622 + 633 633 LT will keep monitoring AV1/AV2/AC1/AC2 every 5 seconds; LT will send uplink packets in two cases: 634 634 635 635 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 636 636 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.** 637 637 628 + 638 638 **AT Command to set Trigger Condition**: 639 639 640 640 (% style="color:#4f81bd" %)**Trigger base on voltage**: ... ... @@ -648,7 +648,6 @@ 648 648 AT+AVLIM=5000,0,0,0 (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore) 649 649 650 650 651 - 652 652 (% style="color:#4f81bd" %)**Trigger base on current**: 653 653 654 654 Format: AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH> ... ... @@ -658,7 +658,6 @@ 658 658 AT+ACLIM=10000,15000,0,0 (If ACI1 voltage lower than 10mA or higher than 15mA, trigger an uplink) 659 659 660 660 661 - 662 662 (% style="color:#4f81bd" %)**Trigger base on DI status**: 663 663 664 664 DI status trigger Flag. ... ... @@ -665,13 +665,12 @@ 665 665 666 666 Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG > 667 667 668 - 669 669 **Example:** 670 670 671 671 AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 672 672 673 673 674 -**Downlink Command to set Trigger Condition :**662 +**Downlink Command to set Trigger Condition** 675 675 676 676 Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 677 677 ... ... @@ -700,7 +700,6 @@ 700 700 Same as AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 701 701 702 702 703 - 704 704 (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:** 705 705 706 706 MOD6 Payload : total 11 bytes payload ... ... @@ -714,6 +714,7 @@ 714 714 715 715 * Each bits shows if the corresponding trigger has been configured. 716 716 704 + 717 717 **Example:** 718 718 719 719 10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW ... ... @@ -725,6 +725,7 @@ 725 725 726 726 * Each bits shows which status has been trigger on this uplink. 727 727 716 + 728 728 **Example:** 729 729 730 730 10000000: Means this packet is trigger by AC1_LOW. Means voltage too low. ... ... @@ -736,6 +736,7 @@ 736 736 737 737 * Each bits shows which status has been trigger on this uplink. 738 738 728 + 739 739 **Example:** 740 740 741 741 00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1. ... ... @@ -777,6 +777,8 @@ 777 777 778 778 * (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L. User can see these commands below: 779 779 770 + 771 + 780 780 === 3.4.1 Common Commands === 781 781 782 782 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]]