<
From version < 77.111 >
edited by Xiaoling
on 2022/06/10 09:37
To version < 77.86 >
edited by Xiaoling
on 2022/06/10 09:27
>
Change comment: There is no comment for this version

Summary

Details

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