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 ... ... @@ -158,8 +158,6 @@ 158 158 ))) 159 159 * ((( 160 160 Packet engine up to 256 bytes with CRC. 161 - 162 - 163 163 ))) 164 164 165 165 == 1.3 Features == ... ... @@ -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 232 + 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. 238 +(% 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 247 + 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. 261 +(% 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 279 + 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 ((( 287 + 288 + 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 302 + 298 298 **The value for the interface is: ** 299 299 300 300 AVI1 channel voltage is 0x04AB/1000=1195(DEC)/1000=1.195V ... ... @@ -310,6 +310,8 @@ 310 310 * [1] RO1 relay channel is close and the RO1 LED is ON. 311 311 * [0] RO2 relay channel is open and RO2 LED is OFF; 312 312 318 + 319 + 313 313 **LT22222-L:** 314 314 315 315 * [1] DI2 channel is high input and DI2 LED is ON; ... ... @@ -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 335 + 328 328 === 3.3.2 AT+MOD~=2, (Double DI Counting) === 329 329 338 + 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 347 + 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 ((( 363 + 364 + 353 353 **To use counting mode, please run:** 354 354 ))) 355 355 ... ... @@ -368,6 +368,8 @@ 368 368 ))) 369 369 370 370 ((( 383 + 384 + 371 371 (% style="color:#4f81bd" %)**AT Commands for counting:** 372 372 ))) 373 373 ... ... @@ -604,6 +604,7 @@ 604 604 605 605 === 3.3.6 AT+ADDMOD~=6. (Trigger Mode, Optional) === 606 606 621 + 607 607 (% style="color:#4f81bd" %)**This mode is an optional mode for trigger purpose. It can run together with other mode.** 608 608 609 609 For example, if user has configured below commands: ... ... @@ -611,13 +611,11 @@ 611 611 * **AT+MOD=1 ** **~-~->** The normal working mode 612 612 * **AT+ADDMOD6=1** **~-~->** Enable trigger 613 613 614 - 615 615 LT will keep monitoring AV1/AV2/AC1/AC2 every 5 seconds; LT will send uplink packets in two cases: 616 616 617 617 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 618 618 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.** 619 619 620 - 621 621 **AT Command to set Trigger Condition**: 622 622 623 623 (% style="color:#4f81bd" %)**Trigger base on voltage**: ... ... @@ -631,6 +631,7 @@ 631 631 AT+AVLIM=5000,0,0,0 (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore) 632 632 633 633 647 + 634 634 (% style="color:#4f81bd" %)**Trigger base on current**: 635 635 636 636 Format: AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH> ... ... @@ -640,6 +640,7 @@ 640 640 AT+ACLIM=10000,15000,0,0 (If ACI1 voltage lower than 10mA or higher than 15mA, trigger an uplink) 641 641 642 642 657 + 643 643 (% style="color:#4f81bd" %)**Trigger base on DI status**: 644 644 645 645 DI status trigger Flag. ... ... @@ -646,12 +646,13 @@ 646 646 647 647 Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG > 648 648 664 + 649 649 **Example:** 650 650 651 651 AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 652 652 653 653 654 -**Downlink Command to set Trigger Condition** 670 +**Downlink Command to set Trigger Condition:** 655 655 656 656 Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 657 657 ... ... @@ -680,6 +680,7 @@ 680 680 Same as AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 681 681 682 682 699 + 683 683 (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:** 684 684 685 685 MOD6 Payload : total 11 bytes payload ... ... @@ -693,7 +693,6 @@ 693 693 694 694 * Each bits shows if the corresponding trigger has been configured. 695 695 696 - 697 697 **Example:** 698 698 699 699 10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW ... ... @@ -705,7 +705,6 @@ 705 705 706 706 * Each bits shows which status has been trigger on this uplink. 707 707 708 - 709 709 **Example:** 710 710 711 711 10000000: Means this packet is trigger by AC1_LOW. Means voltage too low. ... ... @@ -717,7 +717,6 @@ 717 717 718 718 * Each bits shows which status has been trigger on this uplink. 719 719 720 - 721 721 **Example:** 722 722 723 723 00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1. ... ... @@ -738,6 +738,8 @@ 738 738 === 3.3.7 Payload Decoder === 739 739 740 740 ((( 755 + 756 + 741 741 **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/]] 742 742 743 743 ... ... @@ -757,8 +757,6 @@ 757 757 758 758 * (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L. User can see these commands below: 759 759 760 - 761 - 762 762 === 3.4.1 Common Commands === 763 763 764 764 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]]