Changes for page LT-22222-L -- LoRa I/O Controller User Manual

Last modified by Mengting Qiu on 2025/06/04 18:42

From 77.83 to 77.84 From 90.3 to 90.4

From version 77.84

edited by Xiaoling
on 2022/06/10 09:26

Change comment: There is no comment for this version

To version 90.3

edited by Xiaoling
on 2022/08/18 11:46

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 3 added, 0 removed)

Details

Page properties

Content

@@ -1,7 +1,6 @@
  (% style="text-align:center" %)
  [[image:image-20220523163353-1.jpeg||height="604" width="500"]]
--**LT-22222-L LoRa IO Controller User Manual **
  **Table of Contents:**
@@ -19,6 +19,8 @@
  == 1.1 What is LT Series I/O Controller ==
  (((
++
++
  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.
  )))
@@ -40,6 +40,8 @@
  (((
 ) User can set up a LoRaWAN gateway locally and configure the controller to connect to the gateway via wireless.
++
++
  )))
  (((
@@ -48,6 +48,7 @@
  )))
++
  == 1.2  Specifications ==
  (((
@@ -76,6 +76,8 @@
  )))
  (((
++
++
  **Interface for Model: LT22222-L:**
  )))
@@ -99,6 +99,8 @@
  )))
  (((
++
++
  **LoRa Spec:**
  )))
@@ -159,11 +159,14 @@
  * (((
  Packet engine up to 256 bytes with CRC.
++
++
  )))
  == 1.3 Features ==
++
  * LoRaWAN Class A & Class C protocol
  * Optional Customized LoRa Protocol
  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865
@@ -172,8 +172,12 @@
  * Firmware upgradable via program port
  * Counting
++
++
++
  == 1.4  Applications ==
++
  * Smart Buildings & Home Automation
  * Logistics and Supply Chain Management
  * Smart Metering
@@ -181,8 +181,12 @@
  * Smart Cities
  * Smart Factory
++
++
++
  == 1.5 Hardware Variants ==
++
  (% border="1" style="background-color:#f7faff; width:500px" %)
  |(% style="width:103px" %)**Model**|(% style="width:131px" %)**Photo**|(% style="width:334px" %)**Description**
  |(% style="width:103px" %)**LT22222-L**|(% style="width:131px" %)[[image:1653296302983-697.png]]|(% style="width:334px" %)(((
@@ -194,8 +194,11 @@
  * 1 x Counting Port
  )))
++
++
  = 2. Power ON Device =
++
  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.
  (((
@@ -210,14 +210,13 @@
  == 3.1 How it works? ==
++
  (((
--The LT is configured as LoRaWAN OTAA Class C mode by default. It has OTAA keys to join network. To connect a local LoRaWAN network, user just need to input the OTAA keys in the network server and power on the LT. It will auto join the network via OTAA. For LT-22222-L, the LED will show the Join status: After power on **TX LED** will fast blink 5 times, LT-22222-L will enter working mode and start to JOIN LoRaWAN network. **TX LED** will be on for 5 seconds after joined in network. When there is message from server, the **RX LED** will be on for 1 second.
++The LT is configured as LoRaWAN OTAA Class C mode by default. It has OTAA keys to join network. To connect a local LoRaWAN network, user just need to input the OTAA keys in the network server and power on the LT. It will auto join the network via OTAA. For LT-22222-L, the LED will show the Join status: After power on (% style="color:green" %)**TX LED**(%%) will fast blink 5 times, LT-22222-L will enter working mode and start to JOIN LoRaWAN network. (% style="color:green" %)**TX LED**(%%) will be on for 5 seconds after joined in network. When there is message from server, the RX LED will be on for 1 second.
  )))
  (((
--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.
--
--
++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.
  )))
@@ -224,18 +224,24 @@
  == 3.2 Example to join LoRaWAN network ==
++
  (((
  This chapter shows an example for how to join the TTN LoRaWAN Network. Below is the network structure, we use our LG308 as LoRaWAN gateway here.
++
++
  )))
  [[image:image-20220523172350-1.png||height="266" width="864"]]
++
  (((
  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:
++
++
  )))
  (((
--**Step 1**: Create a device in TTN with the OTAA keys from LT IO controller.
++(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LT IO controller.
  )))
  (((
@@ -244,6 +244,7 @@
  [[image:1653297924498-393.png]]
++
  Input these keys in the LoRaWAN Server portal. Below is TTN screen shot:
  Add APP EUI in the application.
@@ -256,8 +256,9 @@
  [[image:1653298023685-319.png]]
++
  (((
--**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.
++(% 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.
  )))
  [[image:1653298044601-602.png||height="405" width="709"]]
@@ -266,22 +266,29 @@
  == 3.3 Uplink Payload ==
++
  There are five working modes + one interrupt mode on LT for different type application:
--* **MOD1**: (default setting): 2 x ACI + 2AVI + DI + DO + RO
--* **MOD2**: Double DI Counting + DO + RO
--* **MOD3**: Single DI Counting + 2 x ACI + DO + RO
--* **MOD4**: Single DI Counting + 1 x Voltage Counting + DO + RO
--* **MOD5**: Single DI Counting + 2 x AVI + 1 x ACI + DO + RO
--* **ADDMOD6**: Trigger Mode, Optional, used together with MOD1 ~~ MOD5
++* (% style="color:blue" %)**MOD1**(%%): (default setting): 2 x ACI + 2AVI + DI + DO + RO
++* (% style="color:blue" %)**MOD2**(%%): Double DI Counting + DO + RO
++* (% style="color:blue" %)**MOD3**(%%): Single DI Counting + 2 x ACI + DO + RO
++* (% style="color:blue" %)**MOD4**(%%): Single DI Counting + 1 x Voltage Counting + DO + RO
++* (% style="color:blue" %)**MOD5**(%%): Single DI Counting + 2 x AVI + 1 x ACI + DO + RO
++* (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5
++
++
++
  === 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
++
  The uplink payload includes totally 9 bytes. Uplink packets use FPORT=2 and every 10 minutes send one uplink by default.
  [[image:image-20220523174024-3.png]]
  (((
++
++
  (% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below
  )))
@@ -295,6 +295,7 @@
  For example if payload is: [[image:image-20220523175847-2.png]]
++
  **The value for the interface is:  **
  AVI1 channel voltage is 0x04AB/1000=1195（DEC）/1000=1.195V
@@ -310,6 +310,7 @@
  * [1] RO1 relay channel is close and the RO1 LED is ON.
  * [0] RO2 relay channel is open and RO2 LED is OFF;
++
  **LT22222-L:**
  * [1] DI2 channel is high input and DI2 LED is ON;
@@ -325,8 +325,12 @@
  ** DO1 is high in case there is load between DO1 and V+.
  ** DO1 LED is off in both case
++
++
++
  === 3.3.2 AT+MOD~=2, (Double DI Counting) ===
++
  **For LT-22222-L**: this mode the **DI1 and DI2** are used as counting pins.
  (((
@@ -335,6 +335,7 @@
  [[image:image-20220523180452-3.png]]
++
  (((
  (% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DO3, DO2 and DO1. Totally 1bytes as below
  )))
@@ -359,12 +359,7 @@
  (((
  (((
  **AT+MOD=2**
--)))
--)))
--(% class="box infomessage" %)
--(((
--(((
  **ATZ**
  )))
  )))
@@ -377,59 +377,33 @@
  (((
  **For LT22222-L:**
--)))
--(% class="box infomessage" %)
--(((
--(((
--**AT+TRIG1=0,100 (set DI1 port to trigger on low level, valid signal is 100ms) **
--)))
--)))
--(% class="box infomessage" %)
--(((
--(((
--**AT+TRIG1=1,100(set DI1 port to trigger on high level, valid signal is 100ms ) **
--)))
--)))
++(% style="color:blue" %)**AT+TRIG1=0,100**(%%)**    (set DI1 port to trigger on low level, valid signal is 100ms) **
--(% class="box infomessage" %)
--(((
--(((
--**AT+TRIG2=0,100 (set DI2 port to trigger on low level, valid signal is 100ms) **
--)))
--)))
++(% style="color:blue" %)**AT+TRIG1=1,100**(%%)**    (set DI1 port to trigger on high level, valid signal is 100ms ) **
--(% class="box infomessage" %)
--(((
--(((
--**AT+TRIG2=1,100 (set DI2 port to trigger on high level, valid signal is 100ms ) **
--)))
--)))
++(% style="color:blue" %)**AT+TRIG2=0,100**(%%)**    (set DI2 port to trigger on low level, valid signal is 100ms) **
--(% class="box infomessage" %)
--(((
--(((
--**AT+SETCNT=1,60   (Set COUNT1 value to 60)**
--)))
--)))
++(% style="color:blue" %)**AT+TRIG2=1,100**(%%)**    (set DI2 port to trigger on high level, valid signal is 100ms ) **
--(% class="box infomessage" %)
--(((
--(((
--**AT+SETCNT=2,60   (Set COUNT2 value to 60)**
++(% style="color:blue" %)**AT+SETCNT=1,60**(%%)**   (Set COUNT1 value to 60)**
++
++(% style="color:blue" %)**AT+SETCNT=2,60**(%%)**   (Set COUNT2 value to 60)**
  )))
--)))
  === 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI ===
++
  **LT22222-L**: This mode the DI1 is used as a counting pin.
  [[image:image-20220523181246-5.png]]
  (((
++
++
  (% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below
  )))
@@ -443,6 +443,7 @@
  (% style="color:red" %)Note: DO3 is not valid for LT-22222-L.
  )))
++
  (((
  **To use counting mode, please run:**
  )))
@@ -451,12 +451,7 @@
  (((
  (((
  **AT+MOD=3**
--)))
--)))
--(% class="box infomessage" %)
--(((
--(((
  **ATZ**
  )))
  )))
@@ -463,11 +463,10 @@
  (((
  Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]].
--
--
  )))
++
  === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting ===
@@ -502,20 +502,13 @@
  (((
  (((
  **AT+MOD=4**
--)))
--)))
--(% class="box infomessage" %)
--(((
--(((
  **ATZ**
  )))
  )))
--(((
--
--)))
++
  (((
  Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]].
  )))
@@ -524,35 +524,16 @@
  **Plus below command for AVI1 Counting:**
--)))
--(% class="box infomessage" %)
--(((
--(((
--**AT+SETCNT=3,60   (set AVI Count to 60)**
--)))
--)))
--(% class="box infomessage" %)
--(((
--(((
--**AT+VOLMAX=20000   (If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
--)))
--)))
++(% style="color:blue" %)**AT+SETCNT=3,60**(%%)**            (set AVI Count to 60)**
--(% class="box infomessage" %)
--(((
--(((
--**AT+VOLMAX=20000,0   (If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
--)))
--)))
++(% style="color:blue" %)**AT+VOLMAX=20000**(%%)**       (If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
--(% class="box infomessage" %)
--(((
--(((
--**AT+VOLMAX=20000,1   (If AVI1 voltage higer than VOLMAX (20000mV =20v), counter increase 1)**
++(% style="color:blue" %)**AT+VOLMAX=20000,0**(%%)**    (If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
++
++(% style="color:blue" %)**AT+VOLMAX=20000,1**(%%)**    (If AVI1 voltage higer than VOLMAX (20000mV =20v), counter increase 1)**
  )))
--)))
@@ -589,12 +589,7 @@
  (((
  (((
  **AT+MOD=5**
--)))
--)))
--(% class="box infomessage" %)
--(((
--(((
  **ATZ**
  )))
  )))
@@ -612,17 +612,16 @@
  For example, if user has configured below commands:
--* **AT+MOD=1 **  **~-~->** The normal working mode
--* **AT+ADDMOD6=1**   **~-~->** Enable trigger
++* **AT+MOD=1 **            **~-~->**   The normal working mode
++* **AT+ADDMOD6=1**   **~-~->**   Enable trigger
--
  LT will keep monitoring AV1/AV2/AC1/AC2 every 5 seconds; LT will send uplink packets in two cases:
 . 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
 . 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.**
++(% style="color:#037691" %)**AT Command to set Trigger Condition**:
--**AT Command to set Trigger Condition**:
  (% style="color:#4f81bd" %)**Trigger base on voltage**:
@@ -635,6 +635,7 @@
  AT+AVLIM=5000,0,0,0   (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore)
++
  (% style="color:#4f81bd" %)**Trigger base on current**:
  Format: AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH>
@@ -644,6 +644,7 @@
  AT+ACLIM=10000,15000,0,0   (If ACI1 voltage lower than 10mA or higher than 15mA, trigger an uplink)
++
  (% style="color:#4f81bd" %)**Trigger base on DI status**:
  DI status trigger Flag.
@@ -650,12 +650,13 @@
  Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >
++
  **Example:**
  AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
--**Downlink Command to set Trigger Condition**
++(% style="color:#037691" %)**Downlink Command to set Trigger Condition:**
  Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
@@ -684,6 +684,7 @@
  Same as AT+ DTRI =1,0  (Enable DI1 trigger / disable DI2 trigger)
++
  (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:**
  MOD6 Payload : total 11 bytes payload
@@ -697,7 +697,6 @@
  * Each bits shows if the corresponding trigger has been configured.
--
  **Example:**
  10100000: Means the system has configure to use the trigger: AC1_LOW and AV2_LOW
@@ -709,7 +709,6 @@
  * Each bits shows which status has been trigger on this uplink.
--
  **Example:**
  10000000: Means this packet is trigger by AC1_LOW. Means voltage too low.
@@ -721,7 +721,6 @@
  * Each bits shows which status has been trigger on this uplink.
--
  **Example:**
  00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
@@ -750,9 +750,9 @@
  )))
--
  == 3.4 Configure LT via AT or Downlink ==
++
  User can configure LT I/O Controller via AT Commands or LoRaWAN Downlink Commands
  (((
@@ -765,8 +765,10 @@
++
  === 3.4.1 Common Commands ===
++
  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]]
@@ -773,80 +773,72 @@
  === 3.4.2 Sensor related commands ===
++
  ==== 3.4.2.1 Set Transmit Interval ====
++
  Set device uplink interval.
--* AT Command:
++* (% style="color:#037691" %)**AT Command:**
--(% class="box infomessage" %)
--(((
  **AT+TDC=N **
--)))
++
  **Example: **AT+TDC=30000. Means set interval to 30 seconds
--* Downlink Payload (prefix 0x01):
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x01):**
--(% class="box infomessage" %)
--(((
  **0x01 aa bb cc     ~/~/ Same as AT+TDC=0x(aa bb cc)**
--)))
++
  ==== 3.4.2.2 Set Work Mode (AT+MOD) ====
++
  Set work mode.
--* AT Command:
++* (% style="color:#037691" %)**AT Command:**
--(% class="box infomessage" %)
--(((
  **AT+MOD=N  **
--)))
++
  **Example**: AT+MOD=2. Set work mode to Double DI counting mode
--* Downlink Payload (prefix 0x0A):
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A):**
--(% class="box infomessage" %)
--(((
--**0x0A aa     ~/~/ Same as AT+MOD=aa**
--)))
++**0x0A aa    ** ~/~/ Same as AT+MOD=aa
++
  ==== 3.4.2.3 Poll an uplink ====
--* AT Command:
++* (% style="color:#037691" %)**AT Command:**
++
  There is no AT Command to poll uplink
--* Downlink Payload (prefix 0x08):
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x08):**
--(% class="box infomessage" %)
--(((
--**0x08 FF     ~/~/ Poll an uplink,**
--)))
++**0x08 FF     **~/~/ Poll an uplink
  **Example**: 0x08FF, ask device to send an Uplink
++
  ==== 3.4.2.4 Enable Trigger Mode ====
++
  Use of trigger mode, please check [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--* AT Command:
++* (% style="color:#037691" %)**AT Command:**
--(% class="box infomessage" %)
--(((
  **AT+ADDMOD6=1 or 0**
--)))
 : Enable Trigger Mode
@@ -853,43 +853,38 @@
 : Disable Trigger Mode
--* Downlink Payload (prefix 0x0A 06):
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A 06):**
--(% class="box infomessage" %)
--(((
--**0x0A 06 aa     ~/~/ Same as AT+ADDMOD6=aa,**
--)))
++**0x0A 06 aa    ** ~/~/ Same as AT+ADDMOD6=aa
++
  ==== 3.4.2.5 Poll trigger settings ====
++
  Poll trigger settings,
--* AT Command:
++* (% style="color:#037691" %)**AT Command:**
  There is no AT Command for this feature.
--* Downlink Payload (prefix 0x AB 06):
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x AB 06):**
--(% class="box infomessage" %)
--(((
--**0xAB 06  ~/~/ Poll trigger settings, device will uplink trigger settings once receive this command**
--)))
++**0xAB 06         **~/~/ Poll trigger settings, device will uplink trigger settings once receive this command
++
  ==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ====
++
  Enable Disable DI1/DI2/DI2 as trigger,
--* AT Command:
++* (% style="color:#037691" %)**AT Command:**
--(% class="box infomessage" %)
--(((
  **Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
--)))
  **Example:**
@@ -896,25 +896,21 @@
  AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
--* Downlink Payload (prefix 0xAA 02):
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 02):**
--(% class="box infomessage" %)
--(((
--**0xAA 02 aa bb  ~/~/ Same as AT+DTRI=aa,bb**
--)))
++**0xAA 02 aa bb        **~/~/ Same as AT+DTRI=aa,bb
++
  ==== 3.4.2.7 Trigger1 – Set DI1 or DI3 as trigger ====
++
  Set DI1 or DI3(for LT-33222-L) trigger.
--* AT Command:
++* (% style="color:#037691" %)**AT Command:**
--(% class="box infomessage" %)
--(((
  **AT+TRIG1=a,b**
--)))
  a : Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
@@ -926,26 +926,22 @@
  AT+TRIG1=1,100(set DI1 port to trigger on high level, valid signal is 100ms )
--* Downlink Payload (prefix 0x09 01 ):
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 01 ):**
++* **0x09 01 aa bb cc    **     ~/~/ same as AT+TRIG1=aa,0x(bb cc)
--(% class="box infomessage" %)
--(((
--**0x09 01 aa bb cc ~/~/ same as AT+TRIG1=aa,0x(bb cc)**
--)))
  ==== 3.4.2.8 Trigger2 – Set DI2 as trigger ====
++
  Set DI2 trigger.
--* AT Command:
++* (% style="color:#037691" %)**AT Command:**
--(% class="box infomessage" %)
--(((
  **AT+TRIG2=a,b**
--)))
++
  a : Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
  b : delay timing.
@@ -956,93 +956,82 @@
  AT+TRIG2=0,100(set DI1 port to trigger on low level, valid signal is 100ms )
--* Downlink Payload (prefix 0x09 02 ):
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 02 ):**
--(% class="box infomessage" %)
--(((
--**0x09 02 aa bb cc ~/~/ same as AT+TRIG1=aa,0x(bb cc)**
--)))
++**0x09 02 aa bb cc           **~/~/ same as AT+TRIG1=aa,0x(bb cc)
++
  ==== 3.4.2.9 Trigger – Set AC (current) as trigger ====
++
  Set current trigger , base on AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--* AT Command:
++* (% style="color:#037691" %)**AT Command**
--(% class="box infomessage" %)
--(((
--**AT+ACLIM. **
--)))
++**AT+ACLIM**
--* Downlink Payload (prefix 0xAA 01 ):
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 01 )**
--(% class="box infomessage" %)
--(((
--**0x AA 01 aa bb cc dd ee ff gg hh ~/~/ same as AT+ACLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]**
--)))
++**0x AA 01 aa bb cc dd ee ff gg hh        **   ~/~/ same as AT+ACLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
++
  ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
++
  Set current trigger , base on AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--* AT Command:
++* (% style="color:#037691" %)**AT Command**
--(% class="box infomessage" %)
--(((
--**AT+AVLIM. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]**
--)))
++**AT+AVLIM            See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]**
--* Downlink Payload (prefix 0xAA 00 ):
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 00 )**
--(% class="box infomessage" %)
--(((
--**0x AA 00 aa bb cc dd ee ff gg hh ~/~/ same as AT+AVLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]] **
--)))
++**0x AA 00 aa bb cc dd ee ff gg hh    ** ~/~/ same as AT+AVLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
++
  ==== 3.4.2.11 Trigger – Set minimum interval ====
--Set AV and AC trigger minimum interval, system won’t response to the second trigger within this set time after the first trigger.
--* AT Command:
++Set AV and AC trigger minimum interval, system won't response to the second trigger within this set time after the first trigger.
--(% class="box infomessage" %)
--(((
--**AT+ATDC=5. Device won’t response the second trigger within 5 minute after the first trigger.**
--)))
++* (% style="color:#037691" %)**AT Command**
++**AT+ATDC=5        ** Device won't response the second trigger within 5 minute after the first trigger.
--* Downlink Payload (prefix 0xAC ):
--(% class="box infomessage" %)
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xAC )**
++
++**0x AC aa bb   ** ~/~/ same as AT+ATDC=0x(aa bb)   . Unit (min)
++
  (((
--**0x AC aa bb ~/~/ same as AT+ATDC=0x(aa bb)   . Unit (min)**
++
++
++(% style="color:red" %)Note: ATDC setting must be more than 5min
  )))
++
  ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
--* AT Command:
++* (% style="color:#037691" %)**AT Command**
++
  There is no AT Command to control Digital Output
--* Downlink Payload (prefix 0x02):
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x02)**
++* **0x02 aa bb cc     **~/~/ Set DO1/DO2/DO3 output
--(% class="box infomessage" %)
  (((
--**0x02 aa bb cc     ~/~/ Set DO1/DO2/DO3 output**
--)))
--
--(((
  If payload = 0x02010001, while there is load between V+ and DOx, it means set DO1 to low, DO2 to high and DO3 to low.
  )))
@@ -1062,22 +1062,20 @@
++
  ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
--* AT Command:
++* (% style="color:#037691" %)**AT Command**
++
  There is no AT Command to control Digital Output
--* Downlink Payload (prefix 0xA9):
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
--(% class="box infomessage" %)
--(((
--(((
--**0xA9 aa bb cc     ~/~/ Set DO1/DO2/DO3 output with time control**
--)))
--)))
++**0xA9 aa bb cc     **~/~/ Set DO1/DO2/DO3 output with time control
++
  This is to control the digital output time of DO pin. Include four bytes:
  (% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
@@ -1131,20 +1131,20 @@
++
  ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
--* AT Command:
++* (% style="color:#037691" %)**AT Command:**
++
  There is no AT Command to control Relay Output
--* Downlink Payload (prefix 0x03):
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
--(% class="box infomessage" %)
--(((
--**0x03 aa bb     ~/~/ Set RO1/RO2 output**
--)))
++**0x03 aa bb     **~/~/ Set RO1/RO2 output
++
  (((
  If payload = 0x030100, it means set RO1 to close and RO2 to open.
  )))
@@ -1161,20 +1161,20 @@
++
  ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
--* AT Command:
++* (% style="color:#037691" %)**AT Command:**
++
  There is no AT Command to control Relay Output
--* Downlink Payload (prefix 0x05):
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
--(% class="box infomessage" %)
--(((
--**0x05 aa bb cc dd     ~/~/ Set RO1/RO2 relay with time control:**
--)))
++**0x05 aa bb cc dd     **~/~/ Set RO1/RO2 relay with time control
++
  This is to control the relay output time of relay. Include four bytes:
  (% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
@@ -1188,7 +1188,7 @@
  (% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
--[[image:image-20220524093831-10.png]]
++[[image:image-20220714135731-1.png||height="406" width="627"]]
  (% style="color:#4f81bd" %)**Fourth/Fifth Bytes(cc)**(%%): Latching time. Unit: ms
@@ -1198,53 +1198,48 @@
  **Example payload:**
--**~1. 05 01 11 07 D0**
++**~1. 05 01 11 07 D**
--Relay1 and Relay 2 will be set to NO , last 2 seconds, then change back to original state.
++Relay1 and Relay 2 will be set to NC , last 2 seconds, then change back to original state.
  **2. 05 01 10 07 D0**
--Relay1 will change to NO, Relay2 will change to NC, last 2 seconds, then both change back to original state.
++Relay1 will change to NC, Relay2 will change to NO, last 2 seconds, then both change back to original state.
  **3. 05 00 01 07 D0**
--Relay1 will change to NC, Relay2 will change to NO, last 2 seconds, then relay change to NO, Relay2 change to NC.
++Relay1 will change to NO, Relay2 will change to NC, last 2 seconds, then relay change to NC,Relay2 change to NO.
  **4. 05 00 00 07 D0**
--Relay 1 & relay2 will change to NC, last 2 seconds, then both change to NO.
++Relay 1 & relay2 will change to NO, last 2 seconds, then both change to NC.
++
  ==== 3.4.2.16 Counting ~-~- Voltage threshold counting ====
++
  When voltage exceed the threshold, count. Feature see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
--* AT Command:
++* (% style="color:#037691" %)**AT Command:**
--(% class="box infomessage" %)
--(((
--**AT+VOLMAX    ~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]**
--)))
++**AT+VOLMAX   ** ~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
--* Downlink Payload (prefix 0xA5):
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):**
--(% class="box infomessage" %)
--(((
--**0xA5 aa bb cc   ~/~/ Same as AT+VOLMAX=(aa bb),cc**
--)))
++**0xA5 aa bb cc   **~/~/ Same as AT+VOLMAX=(aa bb),cc
++
  ==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ====
--* AT Command:
--(% class="box infomessage" %)
--(((
++* (% style="color:#037691" %)**AT Command:**
++
  **AT+SETCNT=aa,(bb cc dd ee) **
--)))
  aa: 1: Set count1,
@@ -1255,51 +1255,42 @@
  Bb cc dd ee: number to be set
--* Downlink Payload (prefix 0xA8):
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):**
--(% class="box infomessage" %)
--(((
--**0x A8 aa bb cc dd ee     ~/~/ same as AT+SETCNT=aa,(bb cc dd ee)**
--)))
++**0x A8 aa bb cc dd ee     **~/~/ same as AT+SETCNT=aa,(bb cc dd ee)
++
  ==== 3.4.2.18 Counting ~-~- Clear Counting ====
++
  Clear counting for counting mode
--* AT Command:
++* (% style="color:#037691" %)**AT Command:**
--(% class="box infomessage" %)
--(((
--**AT+CLRCOUNT  ~/~/ clear all counting**
--)))
++**AT+CLRCOUNT ** ~/~/ clear all counting
--* Downlink Payload (prefix 0xA6):
--(% class="box infomessage" %)
--(((
--**0x A6 01     ~/~/ clear all counting,**
--)))
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):**
++**0x A6 01    ** ~/~/ clear all counting
++
++
  ==== 3.4.2.19 Counting ~-~- Change counting mode save time ====
--* AT Command:
--(% class="box infomessage" %)
--(((
--**AT+COUTIME=60  ~/~/ Set save time to 60 seconds. Device will save the counting result in internal flash every 60 seconds. (min value: 30)**
--)))
++* (% style="color:#037691" %)**AT Command:**
--* Downlink Payload (prefix 0xA7):
++**AT+COUTIME=60  **~/~/ Set save time to 60 seconds. Device will save the counting result in internal flash every 60 seconds. (min value: 30)
--(% class="box infomessage" %)
--(((
--**0x A7 aa bb cc     ~/~/ same as AT+COUTIME =aa bb cc,**
--)))
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):**
++
++**0x A7 aa bb cc     **~/~/ same as AT+COUTIME =aa bb cc,
++
  (((
  range: aa bb cc:0 to 16777215,  (unit:second)
@@ -1307,8 +1307,10 @@
  )))
++
  == 3.5 Integrate with Mydevice ==
++
  Mydevices provides a human friendly interface to show the sensor data, once we have data in TTN, we can use Mydevices to connect to TTN and see the data in Mydevices. Below are the steps:
  (((
@@ -1317,14 +1317,15 @@
  (((
  (% style="color:blue" %)**Step 2**(%%): To configure the Application to forward data to Mydevices you will need to add integration. To add the Mydevices integration, perform the following steps:
++
++
  )))
--[[image:1653356737703-362.png||height="232" width="732"]]
++[[image:image-20220719105525-1.png||height="377" width="677"]]
--[[image:image-20220524094641-11.png||height="390" width="723"]]
--[[image:image-20220524094641-12.png||height="402" width="718"]]
++[[image:image-20220719110247-2.png||height="388" width="683"]]
  (% style="color:blue" %)**Step 3**(%%): Create an account or log in Mydevices.
@@ -1357,8 +1357,10 @@
  == 3.6 Interface Detail ==
++
  === 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) ===
++
  Support NPN Type sensor
  [[image:1653356991268-289.png]]
@@ -1367,6 +1367,7 @@
  === 3.6.2 Digital Input Port: DI1/DI2 ( For LT-22222-L) ===
++
  (((
  The DI port of LT-22222-L can support NPN or PNP output sensor.
  )))
@@ -1373,7 +1373,9 @@
  (((
  (((
--Internal circuit as below, the NEC2501 is a photocoupler, the Active current (from NEC2501 pin 1 to pin 2 is 1ma and the max current is 50mA. When there is active current pass NEC2501 pin1 to pin2. The DI will be active high
++Internal circuit as below, the NEC2501 is a photocoupler, the Active current (from NEC2501 pin 1 to pin 2 is 1ma and the max current is 50mA. When there is active current pass NEC2501 pin1 to pin2. The DI will be active high.
++
++
  )))
  )))
@@ -1418,6 +1418,8 @@
  (((
++
++
  )))
  (((
@@ -1449,6 +1449,8 @@
  (((
++
++
  )))
  (((
@@ -1482,6 +1482,7 @@
  === 3.6.3 Digital Output Port: DO1/DO2 /DO3 ===
++
  NPN output: GND or Float. Max voltage can apply to output pin is 36v.
  [[image:1653357531600-905.png]]
@@ -1490,6 +1490,7 @@
  === 3.6.4 Analog Input Interface ===
++
  The analog input interface is as below. The LT will measure the IN2 voltage so to calculate the current pass the Load. The formula is:
@@ -1521,6 +1521,7 @@
  === 3.6.5 Relay Output ===
++
  (((
  The LT serial controller has two relay interfaces; each interface uses two pins of the screw terminal. User can connect other device’s Power Line to in serial of RO1_1 and RO_2. Such as below:
  )))
@@ -1533,13 +1533,17 @@
  == 3.7 LEDs Indicators ==
++
  [[image:image-20220524100748-11.png]]
++
  = 4. Use AT Command =
++
  == 4.1 Access AT Command ==
++
  LT supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to LT for using AT command, as below.
  [[image:1653358238933-385.png]]
@@ -1738,8 +1738,6 @@
  (((
  AT+CFG: Print all settings
--
--
  )))
@@ -1746,6 +1746,7 @@
  == 4.2 Common AT Command Sequence ==
++
  === 4.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
  (((
@@ -1785,8 +1785,6 @@
  (((
  (% style="background-color:#dcdcdc" %)ATZ
--
--
  )))
@@ -1871,13 +1871,16 @@
  === 4.2.3 Change to Class A ===
++
  If sensor JOINED
  (% style="background-color:#dcdcdc" %)AT+CLASS=A
  ATZ
++
  = 5. FAQ =
++
  == 5.1 How to upgrade the image? ==
@@ -1899,7 +1899,9 @@
  (% style="color:blue" %)**For LT-22222-L**(%%):
--Hold down the PRO button and then momentarily press the RST reset button and the **DO1 led** will change from OFF to ON. When **DO1 LED** is on, it means the device is in download mode.
++Hold down the PRO button and then momentarily press the RST reset button and the (% style="color:red" %)**DO1 led**(%%) will change from OFF to ON. When (% style="color:red" %)**DO1 LED**(%%) is on, it means the device is in download mode.
++
++
  )))
    [[image:image-20220524103407-12.png]]
@@ -1911,6 +1911,7 @@
  (% style="color:red" %)**Notice**(%%): In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
++
  [[image:1653360054704-518.png||height="186" width="745"]]
@@ -1919,6 +1919,8 @@
  == 5.2 How to change the LoRa Frequency Bands/Region? ==
++
++
  )))
  )))
@@ -1929,7 +1929,10 @@
  (((
++
  == 5.3 How to set up LT to work with Single Channel Gateway such as LG01/LG02? ==
++
++
  )))
  (((
@@ -1947,7 +1947,7 @@
  )))
  (((
--(% style="color:#4f81bd" %)**Step1**(%%): Log in TTN, Create an ABP device in the application and input the network session key (NETSKEY), app session key (APPSKEY) from the device.
++(% style="color:blue" %)**Step1**(%%):  Log in TTN, Create an ABP device in the application and input the network session key (NETSKEY), app session key (APPSKEY) from the device.
  )))
  (((
@@ -1955,12 +1955,12 @@
  )))
  (((
--(% style="color:red" %)Note: user just need to make sure above three keys match, User can change either in TTN or Device to make then match. In TTN, NETSKEY and APPSKEY can be configured by user in setting page, but Device Addr is generated by TTN.
++(% style="color:red" %)**Note: user just need to make sure above three keys match, User can change either in TTN or Device to make then match. In TTN, NETSKEY and APPSKEY can be configured by user in setting page, but Device Addr is generated by TTN.**
  )))
  (((
--(% style="color:#4f81bd" %)**Step2**(%%)**: **Run AT Command to make LT work in Single frequency & ABP mode. Below is the AT commands:
++(% style="color:blue" %)**Step2**(%%)**:  **Run AT Command to make LT work in Single frequency & ABP mode. Below is the AT commands:
  )))
  (((
@@ -1984,26 +1984,46 @@
  [[image:1653360498588-932.png||height="485" width="726"]]
++
  == 5.4 Can I see counting event in Serial? ==
++
  (((
--User can run AT+DEBUG command to see the counting event in serial. If firmware too old and doesn’t support AT+DEBUG. User can update to latest firmware first.
++User can run AT+DEBUG command to see the counting event in serial. If firmware too old and doesn't support AT+DEBUG. User can update to latest firmware first.
++
  == 5.5 Can i use point to point communication for LT-22222-L? ==
++
  Yes, please refer [[Point to Point Communication>>doc:Main. Point to Point Communication of LT-22222-L.WebHome]]
++
++
++
  )))
  (((
--
++== 5.6 Why does the relay output become the default and open relay after the lt22222 is powered off? ==
++
++If the device is not shut down, but directly powered off.
++
++It will default that this is a power-off state.
++
++In modes 2 to 5, DO RO status and pulse count are saved in flash.
++
++After restart, the status before power failure will be read from flash.
++
++
++
  = 6. Trouble Shooting =
  )))
  (((
  (((
--== 6.1 Downlink doesn’t work, how to solve it? ==
++== 6.1 Downlink doesn't work, how to solve it? ==
++
++
  )))
  )))
@@ -2014,7 +2014,10 @@
  (((
++
  == 6.2 Have trouble to upload image. ==
++
++
  )))
  (((
@@ -2024,7 +2024,10 @@
  (((
--== 6.3 Why I can’t join TTN in US915 /AU915 bands? ==
++
++== 6.3 Why I can't join TTN in US915 /AU915 bands? ==
++
++
  )))
  (((
@@ -2038,19 +2038,22 @@
  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
--
  (% style="color:#4f81bd" %)**XXX:**
--* (% style="color:#4f81bd" %)**EU433**(%%): LT with frequency bands EU433
--* (% style="color:#4f81bd" %)**EU868**(%%): LT with frequency bands EU868
--* (% style="color:#4f81bd" %)**KR920**(%%): LT with frequency bands KR920
--* (% style="color:#4f81bd" %)**CN470**(%%): LT with frequency bands CN470
--* (% style="color:#4f81bd" %)**AS923**(%%): LT with frequency bands AS923
--* (% style="color:#4f81bd" %)**AU915**(%%): LT with frequency bands AU915
--* (% style="color:#4f81bd" %)**US915**(%%): LT with frequency bands US915
--* (% style="color:#4f81bd" %)**IN865**(%%): LT with frequency bands IN865
--* (% style="color:#4f81bd" %)**CN779**(%%): LT with frequency bands CN779
++* (% style="color:red" %)**EU433**(%%):   LT with frequency bands EU433
++* (% style="color:red" %)**EU868**(%%):   LT with frequency bands EU868
++* (% style="color:red" %)**KR920**(%%):   LT with frequency bands KR920
++* (% style="color:red" %)**CN470**(%%):  LT with frequency bands CN470
++* (% style="color:red" %)**AS923**(%%):   LT with frequency bands AS923
++* (% style="color:red" %)**AU915**(%%):  LT with frequency bands AU915
++* (% style="color:red" %)**US915**(%%):  LT with frequency bands US915
++* (% style="color:red" %)**IN865**(%%):   LT with frequency bands IN865
++* (% style="color:red" %)**CN779**(%%):  LT with frequency bands CN779
++
++
++
++
  = 8. Packing Info =
@@ -2068,18 +2068,32 @@
  * Package Size / pcs : 14.5 x 8 x 5 cm
  * Weight / pcs : 170g
++
++
++
++
  = 9. Support =
++
  * (((
  Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
  )))
  * (((
  Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
++
++
++
++
++
  )))
  = 10. Reference =
++
  * LT-22222-L: [[http:~~/~~/www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html>>url:http://www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html]]
  * [[Image Download>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]]
  * [[AT Command Manual>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
  * [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]
++
++
++

image-20220714135731-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Bei

Size

...	...	@@ -1,0 +1,1 @@
	1	+54.1 KB

Content

image-20220719105525-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Bei

Size

...	...	@@ -1,0 +1,1 @@
	1	+165.5 KB

Content

image-20220719110247-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Bei

Size

...	...	@@ -1,0 +1,1 @@
	1	+52.9 KB

Content