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,9 +162,10 @@ 162 162 ))) 163 163 * ((( 164 164 Packet engine up to 256 bytes with CRC. 161 + 162 + 165 165 ))) 166 166 167 - 168 168 == 1.3 Features == 169 169 170 170 * LoRaWAN Class A & Class C protocol ... ... @@ -175,7 +175,6 @@ 175 175 * Firmware upgradable via program port 176 176 * Counting 177 177 178 - 179 179 == 1.4 Applications == 180 180 181 181 * Smart Buildings & Home Automation ... ... @@ -185,7 +185,6 @@ 185 185 * Smart Cities 186 186 * Smart Factory 187 187 188 - 189 189 == 1.5 Hardware Variants == 190 190 191 191 (% border="1" style="background-color:#f7faff; width:500px" %) ... ... @@ -199,7 +199,6 @@ 199 199 * 1 x Counting Port 200 200 ))) 201 201 202 - 203 203 = 2. Power ON Device = 204 204 205 205 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. ... ... @@ -222,9 +222,12 @@ 222 222 223 223 ((( 224 224 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 + 225 225 ))) 226 226 227 227 224 + 228 228 == 3.2 Example to join LoRaWAN network == 229 229 230 230 ((( ... ... @@ -233,13 +233,12 @@ 233 233 234 234 [[image:image-20220523172350-1.png||height="266" width="864"]] 235 235 236 - 237 237 ((( 238 238 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: 239 239 ))) 240 240 241 241 ((( 242 - (% 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. 243 243 ))) 244 244 245 245 ((( ... ... @@ -248,7 +248,6 @@ 248 248 249 249 [[image:1653297924498-393.png]] 250 250 251 - 252 252 Input these keys in the LoRaWAN Server portal. Below is TTN screen shot: 253 253 254 254 Add APP EUI in the application. ... ... @@ -262,7 +262,7 @@ 262 262 263 263 264 264 ((( 265 - (% 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. 266 266 ))) 267 267 268 268 [[image:1653298044601-602.png||height="405" width="709"]] ... ... @@ -280,9 +280,6 @@ 280 280 * **MOD5**: Single DI Counting + 2 x AVI + 1 x ACI + DO + RO 281 281 * **ADDMOD6**: Trigger Mode, Optional, used together with MOD1 ~~ MOD5 282 282 283 - 284 - 285 - 286 286 === 3.3.1 AT+MOD~=1, 2ACI+2AVI === 287 287 288 288 The uplink payload includes totally 9 bytes. Uplink packets use FPORT=2 and every 10 minutes send one uplink by default. ... ... @@ -290,8 +290,6 @@ 290 290 [[image:image-20220523174024-3.png]] 291 291 292 292 ((( 293 - 294 - 295 295 (% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below 296 296 ))) 297 297 ... ... @@ -305,7 +305,6 @@ 305 305 306 306 For example if payload is: [[image:image-20220523175847-2.png]] 307 307 308 - 309 309 **The value for the interface is: ** 310 310 311 311 AVI1 channel voltage is 0x04AB/1000=1195（DEC）/1000=1.195V ... ... @@ -336,12 +336,8 @@ 336 336 ** DO1 is high in case there is load between DO1 and V+. 337 337 ** DO1 LED is off in both case 338 338 339 - 340 - 341 - 342 342 === 3.3.2 AT+MOD~=2, (Double DI Counting) === 343 343 344 - 345 345 **For LT-22222-L**: this mode the **DI1 and DI2** are used as counting pins. 346 346 347 347 ((( ... ... @@ -350,7 +350,6 @@ 350 350 351 351 [[image:image-20220523180452-3.png]] 352 352 353 - 354 354 ((( 355 355 (% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DO3, DO2 and DO1. Totally 1bytes as below 356 356 ))) ... ... @@ -366,8 +366,6 @@ 366 366 ))) 367 367 368 368 ((( 369 - 370 - 371 371 **To use counting mode, please run:** 372 372 ))) 373 373 ... ... @@ -386,8 +386,6 @@ 386 386 ))) 387 387 388 388 ((( 389 - 390 - 391 391 (% style="color:#4f81bd" %)**AT Commands for counting:** 392 392 ))) 393 393 ... ... @@ -487,7 +487,6 @@ 487 487 488 488 === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting === 489 489 490 - 491 491 **LT22222-L**: This mode the DI1 is used as a counting pin. 492 492 493 493 The AVI1 is also used for counting. AVI1 is used to monitor the voltage. It will check the voltage **every 60s**, if voltage is higher or lower than VOLMAX mV, the AVI1 Counting increase 1, so AVI1 counting can be used to measure a machine working hour. ... ... @@ -494,7 +494,6 @@ 494 494 495 495 [[image:image-20220523181903-8.png]] 496 496 497 - 498 498 ((( 499 499 (% style="color:#4f81bd" %)**DIDORO **(%%)is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below 500 500 ))) ... ... @@ -510,8 +510,6 @@ 510 510 ))) 511 511 512 512 ((( 513 - 514 - 515 515 **To use this mode, please run:** 516 516 ))) 517 517 ... ... @@ -538,8 +538,6 @@ 538 538 ))) 539 539 540 540 ((( 541 - 542 - 543 543 **Plus below command for AVI1 Counting:** 544 544 ))) 545 545 ... ... @@ -575,14 +575,11 @@ 575 575 576 576 === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI === 577 577 578 - 579 579 **LT22222-L**: This mode the DI1 is used as a counting pin. 580 580 581 581 [[image:image-20220523182334-9.png]] 582 582 583 583 ((( 584 - 585 - 586 586 (% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below 587 587 ))) 588 588 ... ... @@ -597,8 +597,6 @@ 597 597 ))) 598 598 599 599 ((( 600 - 601 - 602 602 **To use this mode, please run:** 603 603 ))) 604 604 ... ... @@ -624,7 +624,6 @@ 624 624 625 625 === 3.3.6 AT+ADDMOD~=6. (Trigger Mode, Optional) === 626 626 627 - 628 628 (% style="color:#4f81bd" %)**This mode is an optional mode for trigger purpose. It can run together with other mode.** 629 629 630 630 For example, if user has configured below commands: ... ... @@ -632,11 +632,13 @@ 632 632 * **AT+MOD=1 ** **~-~->** The normal working mode 633 633 * **AT+ADDMOD6=1** **~-~->** Enable trigger 634 634 603 + 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 609 + 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 :**643 +**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 685 + 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 697 + 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 709 + 741 741 **Example:** 742 742 743 743 00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1. ... ... @@ -758,8 +758,6 @@ 758 758 === 3.3.7 Payload Decoder === 759 759 760 760 ((( 761 - 762 - 763 763 **Decoder for TTN/loraserver/ChirpStack**: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/Payload_decoder/>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/Payload_decoder/]] 764 764 765 765 ... ... @@ -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 749 + 750 + 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]]