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,6 +76,8 @@ 76 76 ))) 77 77 78 78 ((( 79 + 80 + 79 79 **Interface for Model: LT22222-L:** 80 80 ))) 81 81 ... ... @@ -99,6 +99,8 @@ 99 99 ))) 100 100 101 101 ((( 104 + 105 + 102 102 **LoRa Spec:** 103 103 ))) 104 104 ... ... @@ -162,6 +162,8 @@ 162 162 163 163 ))) 164 164 169 + 170 + 165 165 == 1.3 Features == 166 166 167 167 * LoRaWAN Class A & Class C protocol ... ... @@ -172,6 +172,8 @@ 172 172 * Firmware upgradable via program port 173 173 * Counting 174 174 181 + 182 + 175 175 == 1.4 Applications == 176 176 177 177 * Smart Buildings & Home Automation ... ... @@ -181,6 +181,8 @@ 181 181 * Smart Cities 182 182 * Smart Factory 183 183 192 + 193 + 184 184 == 1.5 Hardware Variants == 185 185 186 186 (% border="1" style="background-color:#f7faff; width:500px" %) ... ... @@ -194,6 +194,7 @@ 194 194 * 1 x Counting Port 195 195 ))) 196 196 207 + 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 241 + 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 -**Step 1**: Create a device in TTN with the OTAA keys from LT IO controller. 247 +(% 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 256 + 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 -**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. 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. 261 261 ))) 262 262 263 263 [[image:1653298044601-602.png||height="405" width="709"]] ... ... @@ -275,6 +275,7 @@ 275 275 * **MOD5**: Single DI Counting + 2 x AVI + 1 x ACI + DO + RO 276 276 * **ADDMOD6**: Trigger Mode, Optional, used together with MOD1 ~~ MOD5 277 277 288 + 278 278 === 3.3.1 AT+MOD~=1, 2ACI+2AVI === 279 279 280 280 The uplink payload includes totally 9 bytes. Uplink packets use FPORT=2 and every 10 minutes send one uplink by default. ... ... @@ -282,6 +282,8 @@ 282 282 [[image:image-20220523174024-3.png]] 283 283 284 284 ((( 296 + 297 + 285 285 (% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below 286 286 ))) 287 287 ... ... @@ -295,6 +295,7 @@ 295 295 296 296 For example if payload is: [[image:image-20220523175847-2.png]] 297 297 311 + 298 298 **The value for the interface is: ** 299 299 300 300 AVI1 channel voltage is 0x04AB/1000=1195（DEC）/1000=1.195V ... ... @@ -325,8 +325,10 @@ 325 325 ** DO1 is high in case there is load between DO1 and V+. 326 326 ** DO1 LED is off in both case 327 327 342 + 328 328 === 3.3.2 AT+MOD~=2, (Double DI Counting) === 329 329 345 + 330 330 **For LT-22222-L**: this mode the **DI1 and DI2** are used as counting pins. 331 331 332 332 ((( ... ... @@ -335,6 +335,7 @@ 335 335 336 336 [[image:image-20220523180452-3.png]] 337 337 354 + 338 338 ((( 339 339 (% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DO3, DO2 and DO1. Totally 1bytes as below 340 340 ))) ... ... @@ -350,6 +350,8 @@ 350 350 ))) 351 351 352 352 ((( 370 + 371 + 353 353 **To use counting mode, please run:** 354 354 ))) 355 355 ... ... @@ -368,6 +368,8 @@ 368 368 ))) 369 369 370 370 ((( 390 + 391 + 371 371 (% style="color:#4f81bd" %)**AT Commands for counting:** 372 372 ))) 373 373 ... ... @@ -464,9 +464,9 @@ 464 464 ))) 465 465 466 466 467 - 468 468 === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting === 469 469 490 + 470 470 **LT22222-L**: This mode the DI1 is used as a counting pin. 471 471 472 472 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. ... ... @@ -473,6 +473,7 @@ 473 473 474 474 [[image:image-20220523181903-8.png]] 475 475 497 + 476 476 ((( 477 477 (% style="color:#4f81bd" %)**DIDORO **(%%)is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below 478 478 ))) ... ... @@ -488,6 +488,8 @@ 488 488 ))) 489 489 490 490 ((( 513 + 514 + 491 491 **To use this mode, please run:** 492 492 ))) 493 493 ... ... @@ -514,6 +514,8 @@ 514 514 ))) 515 515 516 516 ((( 541 + 542 + 517 517 **Plus below command for AVI1 Counting:** 518 518 ))) 519 519 ... ... @@ -549,11 +549,14 @@ 549 549 550 550 === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI === 551 551 578 + 552 552 **LT22222-L**: This mode the DI1 is used as a counting pin. 553 553 554 554 [[image:image-20220523182334-9.png]] 555 555 556 556 ((( 584 + 585 + 557 557 (% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below 558 558 ))) 559 559 ... ... @@ -568,6 +568,8 @@ 568 568 ))) 569 569 570 570 ((( 600 + 601 + 571 571 **To use this mode, please run:** 572 572 ))) 573 573 ... ... @@ -587,8 +587,6 @@ 587 587 588 588 ((( 589 589 Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]. 590 - 591 - 592 592 ))) 593 593 594 594 ... ... @@ -595,6 +595,7 @@ 595 595 596 596 === 3.3.6 AT+ADDMOD~=6. (Trigger Mode, Optional) === 597 597 627 + 598 598 (% style="color:#4f81bd" %)**This mode is an optional mode for trigger purpose. It can run together with other mode.** 599 599 600 600 For example, if user has configured below commands: ... ... @@ -602,13 +602,11 @@ 602 602 * **AT+MOD=1 ** **~-~->** The normal working mode 603 603 * **AT+ADDMOD6=1** **~-~->** Enable trigger 604 604 605 - 606 606 LT will keep monitoring AV1/AV2/AC1/AC2 every 5 seconds; LT will send uplink packets in two cases: 607 607 608 608 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 609 609 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.** 610 610 611 - 612 612 **AT Command to set Trigger Condition**: 613 613 614 614 (% style="color:#4f81bd" %)**Trigger base on voltage**: ... ... @@ -622,6 +622,7 @@ 622 622 AT+AVLIM=5000,0,0,0 (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore) 623 623 624 624 653 + 625 625 (% style="color:#4f81bd" %)**Trigger base on current**: 626 626 627 627 Format: AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH> ... ... @@ -631,6 +631,7 @@ 631 631 AT+ACLIM=10000,15000,0,0 (If ACI1 voltage lower than 10mA or higher than 15mA, trigger an uplink) 632 632 633 633 663 + 634 634 (% style="color:#4f81bd" %)**Trigger base on DI status**: 635 635 636 636 DI status trigger Flag. ... ... @@ -637,12 +637,13 @@ 637 637 638 638 Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG > 639 639 670 + 640 640 **Example:** 641 641 642 642 AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 643 643 644 644 645 -**Downlink Command to set Trigger Condition** 676 +**Downlink Command to set Trigger Condition:** 646 646 647 647 Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 648 648 ... ... @@ -671,6 +671,7 @@ 671 671 Same as AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 672 672 673 673 705 + 674 674 (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:** 675 675 676 676 MOD6 Payload : total 11 bytes payload ... ... @@ -684,7 +684,6 @@ 684 684 685 685 * Each bits shows if the corresponding trigger has been configured. 686 686 687 - 688 688 **Example:** 689 689 690 690 10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW ... ... @@ -696,7 +696,6 @@ 696 696 697 697 * Each bits shows which status has been trigger on this uplink. 698 698 699 - 700 700 **Example:** 701 701 702 702 10000000: Means this packet is trigger by AC1_LOW. Means voltage too low. ... ... @@ -708,7 +708,6 @@ 708 708 709 709 * Each bits shows which status has been trigger on this uplink. 710 710 711 - 712 712 **Example:** 713 713 714 714 00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1. ... ... @@ -729,6 +729,8 @@ 729 729 === 3.3.7 Payload Decoder === 730 730 731 731 ((( 761 + 762 + 732 732 **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/]] 733 733 734 734 ... ... @@ -748,8 +748,6 @@ 748 748 749 749 * (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L. User can see these commands below: 750 750 751 - 752 - 753 753 === 3.4.1 Common Commands === 754 754 755 755 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]]