Last modified by Saxer Lin on 2025/04/15 17:24
<
From version < 77.97 >
edited by Xiaoling
on 2022/06/10 09:32
To version < 82.5 >
edited by Xiaoling
on 2022/06/20 11:17
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -19,6 +19,8 @@
19 19  == 1.1 What is LT Series I/O Controller ==
20 20  
21 21  (((
22 +
23 +
22 22  The Dragino (% style="color:blue" %)**LT series I/O Modules**(%%) are Long Range LoRaWAN I/O Controller. It contains different I/O Interfaces such as:** (% style="color:blue" %)analog current Input, analog voltage input(%%)**(% style="color:blue" %), **relay output**, **digital input**(%%) and (% style="color:blue" %)**digital output**(%%) etc. The LT I/O Modules are designed to simplify the installation of I/O monitoring.
23 23  )))
24 24  
... ... @@ -48,6 +48,7 @@
48 48  
49 49  )))
50 50  
53 +
51 51  == 1.2  Specifications ==
52 52  
53 53  (((
... ... @@ -76,6 +76,8 @@
76 76  )))
77 77  
78 78  (((
82 +
83 +
79 79  **Interface for Model: LT22222-L:**
80 80  )))
81 81  
... ... @@ -99,6 +99,8 @@
99 99  )))
100 100  
101 101  (((
107 +
108 +
102 102  **LoRa Spec:**
103 103  )))
104 104  
... ... @@ -159,6 +159,8 @@
159 159  * (((
160 160  Packet engine up to 256 bytes with CRC.
161 161  
169 +
170 +
162 162  
163 163  )))
164 164  
... ... @@ -172,6 +172,9 @@
172 172  * Firmware upgradable via program port
173 173  * Counting
174 174  
184 +
185 +
186 +
175 175  == 1.4  Applications ==
176 176  
177 177  * Smart Buildings & Home Automation
... ... @@ -181,6 +181,9 @@
181 181  * Smart Cities
182 182  * Smart Factory
183 183  
196 +
197 +
198 +
184 184  == 1.5 Hardware Variants ==
185 185  
186 186  (% border="1" style="background-color:#f7faff; width:500px" %)
... ... @@ -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  
245 +
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.
251 +(% 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  
260 +
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.
274 +(% 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,7 +275,6 @@
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  
278 -
279 279  === 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
280 280  
281 281  The uplink payload includes totally 9 bytes. Uplink packets use FPORT=2 and every 10 minutes send one uplink by default.
... ... @@ -314,8 +314,6 @@
314 314  * [1] RO1 relay channel is close and the RO1 LED is ON.
315 315  * [0] RO2 relay channel is open and RO2 LED is OFF;
316 316  
317 -
318 -
319 319  **LT22222-L:**
320 320  
321 321  * [1] DI2 channel is high input and DI2 LED is ON;
... ... @@ -331,7 +331,6 @@
331 331  ** DO1 is high in case there is load between DO1 and V+.
332 332  ** DO1 LED is off in both case
333 333  
334 -
335 335  === 3.3.2 AT+MOD~=2, (Double DI Counting) ===
336 336  
337 337  
... ... @@ -472,11 +472,10 @@
472 472  
473 473  (((
474 474  Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]].
475 -
476 -
477 477  )))
478 478  
479 479  
488 +
480 480  === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting ===
481 481  
482 482  
... ... @@ -624,14 +624,11 @@
624 624  * **AT+MOD=1 ** **~-~->** The normal working mode
625 625  * **AT+ADDMOD6=1**   **~-~->** Enable trigger
626 626  
627 -
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  
633 -
634 -
635 635  **AT Command to set Trigger Condition**:
636 636  
637 637  (% style="color:#4f81bd" %)**Trigger base on voltage**:
... ... @@ -711,8 +711,6 @@
711 711  
712 712  * Each bits shows if the corresponding trigger has been configured.
713 713  
714 -
715 -
716 716  **Example:**
717 717  
718 718  10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW
... ... @@ -724,8 +724,6 @@
724 724  
725 725  * Each bits shows which status has been trigger on this uplink.
726 726  
727 -
728 -
729 729  **Example:**
730 730  
731 731  10000000: Means this packet is trigger by AC1_LOW. Means voltage too low.
... ... @@ -737,8 +737,6 @@
737 737  
738 738  * Each bits shows which status has been trigger on this uplink.
739 739  
740 -
741 -
742 742  **Example:**
743 743  
744 744  00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
... ... @@ -767,7 +767,6 @@
767 767  )))
768 768  
769 769  
770 -
771 771  == 3.4 ​Configure LT via AT or Downlink ==
772 772  
773 773  User can configure LT I/O Controller via AT Commands or LoRaWAN Downlink Commands
... ... @@ -780,8 +780,6 @@
780 780  
781 781  * (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L.  User can see these commands below:
782 782  
783 -
784 -
785 785  === 3.4.1 Common Commands ===
786 786  
787 787  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]]
... ... @@ -2013,8 +2013,16 @@
2013 2013  )))
2014 2014  
2015 2015  (((
2016 -
2013 +== 5.6 Why does the relay output become the default and open relay after the lt22222 is powered off? ==
2017 2017  
2015 +If the device is not shut down, but directly powered off.
2016 +
2017 +It will default that this is a power-off state.
2018 +
2019 +In modes 2 to 5, DO RO status and pulse count are saved in flash.
2020 +
2021 +After restart, the status before power failure will be read from flash.
2022 +
2018 2018  = 6. Trouble Shooting =
2019 2019  )))
2020 2020  

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0