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
-
... ... @@ -194,6 +194,8 @@ 194 194 * 1 x Counting Port 195 195 ))) 196 196 197 + 198 + 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 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,8 @@ 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 + 280 + 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 ((( 288 + 289 + 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 303 + 298 298 **The value for the interface is: ** 299 299 300 300 AVI1 channel voltage is 0x04AB/1000=1195（DEC）/1000=1.195V ... ... @@ -327,6 +327,7 @@ 327 327 ** DO1 LED is off in both case 328 328 329 329 336 + 330 330 === 3.3.2 AT+MOD~=2, (Double DI Counting) === 331 331 332 332 ... ... @@ -624,6 +624,7 @@ 624 624 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 625 625 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.** 626 626 634 + 627 627 **AT Command to set Trigger Condition**: 628 628 629 629 (% style="color:#4f81bd" %)**Trigger base on voltage**: ... ... @@ -637,6 +637,7 @@ 637 637 AT+AVLIM=5000,0,0,0 (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore) 638 638 639 639 648 + 640 640 (% style="color:#4f81bd" %)**Trigger base on current**: 641 641 642 642 Format: AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH> ... ... @@ -646,6 +646,7 @@ 646 646 AT+ACLIM=10000,15000,0,0 (If ACI1 voltage lower than 10mA or higher than 15mA, trigger an uplink) 647 647 648 648 658 + 649 649 (% style="color:#4f81bd" %)**Trigger base on DI status**: 650 650 651 651 DI status trigger Flag. ... ... @@ -652,12 +652,13 @@ 652 652 653 653 Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG > 654 654 665 + 655 655 **Example:** 656 656 657 657 AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 658 658 659 659 660 -**Downlink Command to set Trigger Condition** 671 +**Downlink Command to set Trigger Condition:** 661 661 662 662 Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 663 663 ... ... @@ -686,6 +686,7 @@ 686 686 Same as AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger) 687 687 688 688 700 + 689 689 (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:** 690 690 691 691 MOD6 Payload : total 11 bytes payload ... ... @@ -699,6 +699,7 @@ 699 699 700 700 * Each bits shows if the corresponding trigger has been configured. 701 701 714 + 702 702 **Example:** 703 703 704 704 10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW ... ... @@ -710,6 +710,7 @@ 710 710 711 711 * Each bits shows which status has been trigger on this uplink. 712 712 726 + 713 713 **Example:** 714 714 715 715 10000000: Means this packet is trigger by AC1_LOW. Means voltage too low. ... ... @@ -721,6 +721,7 @@ 721 721 722 722 * Each bits shows which status has been trigger on this uplink. 723 723 738 + 724 724 **Example:** 725 725 726 726 00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.