<
From version < 82.1 >
edited by Bei Jinggeng
on 2022/06/15 08:49
To version < 77.98 >
edited by Xiaoling
on 2022/06/10 09:32
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.Xiaoling
Content
... ... @@ -48,7 +48,6 @@
48 48  
49 49  )))
50 50  
51 -
52 52  == 1.2  Specifications ==
53 53  
54 54  (((
... ... @@ -77,8 +77,6 @@
77 77  )))
78 78  
79 79  (((
80 -
81 -
82 82  **Interface for Model: LT22222-L:**
83 83  )))
84 84  
... ... @@ -102,8 +102,6 @@
102 102  )))
103 103  
104 104  (((
105 -
106 -
107 107  **LoRa Spec:**
108 108  )))
109 109  
... ... @@ -163,9 +163,10 @@
163 163  )))
164 164  * (((
165 165  Packet engine up to 256 bytes with CRC.
161 +
162 +
166 166  )))
167 167  
168 -
169 169  == 1.3 Features ==
170 170  
171 171  * LoRaWAN Class A & Class C protocol
... ... @@ -176,7 +176,6 @@
176 176  * Firmware upgradable via program port
177 177  * Counting
178 178  
179 -
180 180  == 1.4  Applications ==
181 181  
182 182  * Smart Buildings & Home Automation
... ... @@ -186,7 +186,6 @@
186 186  * Smart Cities
187 187  * Smart Factory
188 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,6 +281,7 @@
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  
278 +
284 284  === 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
285 285  
286 286  The uplink payload includes totally 9 bytes. Uplink packets use FPORT=2 and every 10 minutes send one uplink by default.
... ... @@ -319,6 +319,8 @@
319 319  * [1] RO1 relay channel is close and the RO1 LED is ON.
320 320  * [0] RO2 relay channel is open and RO2 LED is OFF;
321 321  
317 +
318 +
322 322  **LT22222-L:**
323 323  
324 324  * [1] DI2 channel is high input and DI2 LED is ON;
... ... @@ -334,6 +334,8 @@
334 334  ** DO1 is high in case there is load between DO1 and V+.
335 335  ** DO1 LED is off in both case
336 336  
334 +
335 +
337 337  === 3.3.2 AT+MOD~=2, (Double DI Counting) ===
338 338  
339 339  
... ... @@ -474,10 +474,11 @@
474 474  
475 475  (((
476 476  Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]].
476 +
477 +
477 477  )))
478 478  
479 479  
480 -
481 481  === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting ===
482 482  
483 483  
... ... @@ -625,11 +625,14 @@
625 625  * **AT+MOD=1 ** **~-~->** The normal working mode
626 626  * **AT+ADDMOD6=1**   **~-~->** Enable trigger
627 627  
628 +
628 628  LT will keep monitoring AV1/AV2/AC1/AC2 every 5 seconds; LT will send uplink packets in two cases:
629 629  
630 630  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
631 631  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.**
632 632  
634 +
635 +
633 633  **AT Command to set Trigger Condition**:
634 634  
635 635  (% style="color:#4f81bd" %)**Trigger base on voltage**:
... ... @@ -709,6 +709,8 @@
709 709  
710 710  * Each bits shows if the corresponding trigger has been configured.
711 711  
715 +
716 +
712 712  **Example:**
713 713  
714 714  10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW
... ... @@ -720,6 +720,8 @@
720 720  
721 721  * Each bits shows which status has been trigger on this uplink.
722 722  
728 +
729 +
723 723  **Example:**
724 724  
725 725  10000000: Means this packet is trigger by AC1_LOW. Means voltage too low.
... ... @@ -731,6 +731,8 @@
731 731  
732 732  * Each bits shows which status has been trigger on this uplink.
733 733  
741 +
742 +
734 734  **Example:**
735 735  
736 736  00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
... ... @@ -759,6 +759,7 @@
759 759  )))
760 760  
761 761  
771 +
762 762  == 3.4 ​Configure LT via AT or Downlink ==
763 763  
764 764  User can configure LT I/O Controller via AT Commands or LoRaWAN Downlink Commands
... ... @@ -771,6 +771,8 @@
771 771  
772 772  * (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L.  User can see these commands below:
773 773  
784 +
785 +
774 774  === 3.4.1 Common Commands ===
775 775  
776 776  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]]
... ... @@ -2002,16 +2002,8 @@
2002 2002  )))
2003 2003  
2004 2004  (((
2005 -== 5.6 Why does the relay output become the default and open relay after the lt22222 is powered off? ==
2017 +
2006 2006  
2007 -If the device is not shut down, but directly powered off.
2008 -
2009 -It will default that this is a power-off state.
2010 -
2011 -In modes 2 to 5, DO RO status and pulse count are saved in flash.
2012 -
2013 -After restart, the status before power failure will be read from flash.
2014 -
2015 2015  = 6. Trouble Shooting =
2016 2016  )))
2017 2017  
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0