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

Summary

Details

Page properties
Content
... ... @@ -162,6 +162,8 @@
162 162  
163 163  )))
164 164  
165 +
166 +
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  
177 +
178 +
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  
188 +
189 +
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  
203 +
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  
237 +
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.
243 +(% 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  
252 +
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.
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.
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  
284 +
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  (((
292 +
293 +
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  
307 +
298 298  **The value for the interface is:  **
299 299  
300 300  AVI1 channel voltage is 0x04AB/1000=1195(DEC)/1000=1.195V
... ... @@ -325,6 +325,7 @@
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  
338 +
328 328  === 3.3.2 AT+MOD~=2, (Double DI Counting) ===
329 329  
330 330  
... ... @@ -617,13 +617,11 @@
617 617  * **AT+MOD=1 ** **~-~->** The normal working mode
618 618  * **AT+ADDMOD6=1**   **~-~->** Enable trigger
619 619  
620 -
621 621  LT will keep monitoring AV1/AV2/AC1/AC2 every 5 seconds; LT will send uplink packets in two cases:
622 622  
623 623  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
624 624  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.**
625 625  
626 -
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  
649 +
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  
659 +
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  
666 +
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**
672 +**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  
701 +
689 689  (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:**
690 690  
691 691  MOD6 Payload : total 11 bytes payload
... ... @@ -699,7 +699,6 @@
699 699  
700 700  * Each bits shows if the corresponding trigger has been configured.
701 701  
702 -
703 703  **Example:**
704 704  
705 705  10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW
... ... @@ -711,7 +711,6 @@
711 711  
712 712  * Each bits shows which status has been trigger on this uplink.
713 713  
714 -
715 715  **Example:**
716 716  
717 717  10000000: Means this packet is trigger by AC1_LOW. Means voltage too low.
... ... @@ -723,7 +723,6 @@
723 723  
724 724  * Each bits shows which status has been trigger on this uplink.
725 725  
726 -
727 727  **Example:**
728 728  
729 729  00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
... ... @@ -765,8 +765,6 @@
765 765  
766 766  * (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L.  User can see these commands below:
767 767  
768 -
769 -
770 770  === 3.4.1 Common Commands ===
771 771  
772 772  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