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

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

From 82.25 to 82.26 From 99.1 to 100.1

From version 82.26

edited by Xiaoling
on 2022/06/20 12:00

Change comment: There is no comment for this version

To version 99.1

edited by Edwin Chen
on 2022/10/06 17:06

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 4 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.Xiaoling
++XWiki.Edwin

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:**
@@ -16,6 +16,7 @@
  = 1.Introduction =
++
  == 1.1 What is LT Series I/O Controller ==
  (((
@@ -37,11 +37,13 @@
  )))
  (((
--1) If user’s area has LoRaWAN service coverage, they can just install the I/O controller and configure it to connect the LoRaWAN provider via wireless.
++1) If user's area has LoRaWAN service coverage, they can just install the I/O controller and configure it to connect the LoRaWAN provider via wireless.
  )))
  (((
 ) User can set up a LoRaWAN gateway locally and configure the controller to connect to the gateway via wireless.
++
++
  )))
  (((
@@ -56,7 +56,7 @@
  (((
--**Hardware System:**
++(% style="color:#037691" %)**Hardware System:**
  )))
  * (((
@@ -81,7 +81,7 @@
  (((
--**Interface for Model: LT22222-L:**
++(% style="color:#037691" %)**Interface for Model: LT22222-L:**
  )))
  * (((
@@ -106,7 +106,7 @@
  (((
--**LoRa Spec:**
++(% style="color:#037691" %)**LoRa Spec:**
  )))
  * (((
@@ -173,9 +173,10 @@
  == 1.3 Features ==
++
  * LoRaWAN Class A & Class C protocol
  * Optional Customized LoRa Protocol
--* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865
++* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
  * AT Commands to change parameters
  * Remote configure parameters via LoRa Downlink
  * Firmware upgradable via program port
@@ -182,8 +182,10 @@
  * Counting
++
  == 1.4  Applications ==
++
  * Smart Buildings & Home Automation
  * Logistics and Supply Chain Management
  * Smart Metering
@@ -192,8 +192,10 @@
  * 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" %)(((
@@ -207,13 +207,15 @@
--
  = 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.
  (((
  PWR will on when device is properly powered.
++
++
  )))
  [[image:1653297104069-180.png]]
@@ -222,21 +222,27 @@
  = 3. Operation Mode =
++
  == 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.
  )))
++
  == 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"]]
@@ -244,6 +244,8 @@
  (((
  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:
++
++
  )))
  (((
@@ -269,6 +269,7 @@
  [[image:1653298023685-319.png]]
++
  (((
  (% 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.
  )))
@@ -279,18 +279,21 @@
  == 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]]
@@ -307,8 +307,9 @@
  * DI is for digital input. DIx=1: high or float, DIx=0: low.
  * DO is for reverse digital output. DOx=1: output low, DOx=0: high or float.
--(% style="color:red" %)Note: DI3 and DO3 bit are not valid for LT-22222-L
++(% style="color:red" %)**Note: DI3 and DO3 bit are not valid for LT-22222-L**
++
  For example if payload is: [[image:image-20220523175847-2.png]]
@@ -327,6 +327,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;
@@ -343,6 +343,8 @@
  ** DO1 LED is off in both case
++
++
  === 3.3.2 AT+MOD~=2, (Double DI Counting) ===
@@ -366,7 +366,7 @@
  * DO is for reverse digital output. DOx=1: output low, DOx=0: high or float.
  (((
--(% style="color:red" %)Note: DO3 bit is not valid for LT-22222-L.
++(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L.**
  )))
  (((
@@ -388,6 +388,8 @@
  (% style="color:#4f81bd" %)**AT Commands for counting:**
++
++
  )))
  (((
@@ -394,17 +394,17 @@
  **For LT22222-L:**
--**AT+TRIG1=0,100    (set DI1 port to trigger on low level, valid signal is 100ms) **
++(% style="color:blue" %)**AT+TRIG1=0,100**(%%)**    (set DI1 port to trigger on low level, valid signal is 100ms) **
--**AT+TRIG1=1,100    (set DI1 port to trigger on high level, valid signal is 100ms ) **
++(% style="color:blue" %)**AT+TRIG1=1,100**(%%)**    (set DI1 port to trigger on high level, valid signal is 100ms ) **
--**AT+TRIG2=0,100    (set DI2 port to trigger on low level, valid signal is 100ms) **
++(% style="color:blue" %)**AT+TRIG2=0,100**(%%)**    (set DI2 port to trigger on low level, valid signal is 100ms) **
--**AT+TRIG2=1,100    (set DI2 port to trigger on high level, valid signal is 100ms ) **
++(% style="color:blue" %)**AT+TRIG2=1,100**(%%)**    (set DI2 port to trigger on high level, valid signal is 100ms ) **
--**AT+SETCNT=1,60   (Set COUNT1 value to 60)**
++(% style="color:blue" %)**AT+SETCNT=1,60**(%%)**   (Set COUNT1 value to 60)**
--**AT+SETCNT=2,60   (Set COUNT2 value to 60)**
++(% style="color:blue" %)**AT+SETCNT=2,60**(%%)**   (Set COUNT2 value to 60)**
  )))
@@ -411,11 +411,14 @@
  === 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
  )))
@@ -426,9 +426,10 @@
  * DO is for reverse digital output. DOx=1: output low, DOx=0: high or float.
  (((
--(% style="color:red" %)Note: DO3 is not valid for LT-22222-L.
++(% style="color:red" %)**Note: DO3 is not valid for LT-22222-L.**
  )))
++
  (((
  **To use counting mode, please run:**
  )))
@@ -469,7 +469,7 @@
  * DO is for reverse digital output. DOx=1: output low, DOx=0: high or float.
  (((
--(% style="color:red" %)Note: DO3 is not valid for LT-22222-L.
++(% style="color:red" %)**Note: DO3 is not valid for LT-22222-L.**
  )))
  (((
@@ -530,7 +530,7 @@
  )))
  (((
--(% style="color:red" %)Note: DO3 is not valid for LT-22222-L.
++(% style="color:red" %)**Note: DO3 is not valid for LT-22222-L.**
  )))
  (((
@@ -561,9 +561,10 @@
  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
@@ -570,12 +570,15 @@
 . 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**:
++
  (% style="color:#4f81bd" %)**Trigger base on voltage**:
  Format: AT+AVLIM=<AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH>
++
  **Example:**
  AT+AVLIM=3000,6000,0,2000   (If AVI1 voltage lower than 3v or higher than 6v.  or AV2 voltage is higher than 2v, LT will trigger Uplink)
@@ -588,6 +588,7 @@
  Format: AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH>
++
  **Example:**
  AT+ACLIM=10000,15000,0,0   (If ACI1 voltage lower than 10mA or higher than 15mA, trigger an uplink)
@@ -606,6 +606,7 @@
  AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
++
  (% style="color:#037691" %)**Downlink Command to set Trigger Condition:**
  Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
@@ -649,11 +649,13 @@
  * 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
++
  (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1byte as below
  [[image:image-20220524090249-3.png]]
@@ -660,11 +660,13 @@
  * 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.
++
  (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
  [[image:image-20220524090456-4.png]]
@@ -671,6 +671,7 @@
  * 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.
@@ -678,6 +678,7 @@
  00000101: Means both DI1 and DI2 trigger are enabled.
++
  (% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable.
  Downlink command to poll MOD6 status:
@@ -688,19 +688,20 @@
++
  === 3.3.7 Payload Decoder ===
  (((
--**Decoder for TTN/loraserver/ChirpStack**: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/Payload_decoder/>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/Payload_decoder/]]
--
--
++**Decoder for TTN/loraserver/ChirpStack**:  [[https:~~/~~/www.dropbox.com/sh/wtrzu7avdtkmn3z/AACK5NwOMkU9jnvf1uCMuqrVa?dl=0>>https://www.dropbox.com/sh/wtrzu7avdtkmn3z/AACK5NwOMkU9jnvf1uCMuqrVa?dl=0]]
  )))
++
  == 3.4 Configure LT via AT or Downlink ==
++
  User can configure LT I/O Controller via AT Commands or LoRaWAN Downlink Commands
  (((
@@ -712,8 +712,10 @@
  * (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L.  User can see these commands below:
++
  === 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]]
@@ -720,80 +720,73 @@
  === 3.4.2 Sensor related commands ===
++
  ==== 3.4.2.1 Set Transmit Interval ====
++
  Set device uplink interval.
  * (% style="color:#037691" %)**AT Command:**
--(% class="box infomessage" %)
--(((
  **AT+TDC=N **
--)))
++
  **Example: **AT+TDC=30000. Means set interval to 30 seconds
  * (% 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.
  * (% style="color:#037691" %)**AT Command:**
--(% class="box infomessage" %)
--(((
  **AT+MOD=N  **
--)))
++
  **Example**: AT+MOD=2. Set work mode to Double DI counting mode
  * (% 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 ====
--* (% style="color:#037691" %)AT Command:
++* (% style="color:#037691" %)**AT Command:**
++
  There is no AT Command to poll uplink
--* (% style="color:#037691" %)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"]]
--* (% style="color:#037691" %)AT Command:
++* (% style="color:#037691" %)**AT Command:**
--(% class="box infomessage" %)
--(((
  **AT+ADDMOD6=1 or 0**
--)))
 : Enable Trigger Mode
@@ -800,38 +800,36 @@
 : Disable Trigger Mode
--* (% style="color:#037691" %)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,
--* (% style="color:#037691" %)AT Command:
++* (% style="color:#037691" %)**AT Command:**
  There is no AT Command for this feature.
--* (% style="color:#037691" %)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,
--* (% style="color:#037691" %)AT Command:
++* (% style="color:#037691" %)**AT Command:**
  **Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
@@ -840,7 +840,7 @@
  AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
--* (% style="color:#037691" %)Downlink Payload (prefix 0xAA 02):
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 02):**
  **0xAA 02 aa bb        **~/~/ Same as AT+DTRI=aa,bb
@@ -849,9 +849,10 @@
  ==== 3.4.2.7 Trigger1 – Set DI1 or DI3 as trigger ====
++
  Set DI1 or DI3(for LT-33222-L) trigger.
--* (% style="color:#037691" %)AT Command:
++* (% style="color:#037691" %)**AT Command:**
  **AT+TRIG1=a,b**
@@ -872,6 +872,7 @@
  ==== 3.4.2.8 Trigger2 – Set DI2 as trigger ====
++
  Set DI2 trigger.
  * (% style="color:#037691" %)**AT Command:**
@@ -898,6 +898,7 @@
  ==== 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"]]
  * (% style="color:#037691" %)**AT Command**
@@ -914,6 +914,7 @@
  ==== 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"]]
  * (% style="color:#037691" %)**AT Command**
@@ -930,11 +930,12 @@
  ==== 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.
++Set AV and AC trigger minimum interval, system won't response to the second trigger within this set time 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.**
++**AT+ATDC=5        ** Device won't response the second trigger within 5 minute after the first trigger.
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAC )**
@@ -941,11 +941,18 @@
  **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 ====
++
  * (% style="color:#037691" %)**AT Command**
  There is no AT Command to control Digital Output
@@ -965,11 +965,11 @@
  [[image:image-20220524092754-5.png]]
  (((
--(% style="color:red" %)Note: For LT-22222-L, there is no DO3, the last byte can use any value.
++(% style="color:red" %)**Note: For LT-22222-L, there is no DO3, the last byte can use any value.**
  )))
  (((
--(% style="color:red" %)Device will upload a packet if downlink code executes successfully.
++(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
  )))
@@ -977,6 +977,7 @@
  ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
++
  * (% style="color:#037691" %)**AT Command**
  There is no AT Command to control Digital Output
@@ -1013,11 +1013,11 @@
  [[image:image-20220524093351-8.png]]
--(% style="color:#4f81bd" %)**Sixth and Seventh Byte**:
++(% style="color:#4f81bd" %)**Sixth and Seventh and Eighth and Ninth Byte**:
           Latching time. Unit: ms
--Device will upload a packet if downlink code executes successfully.
++(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
  **Example payload:**
@@ -1043,6 +1043,7 @@
  ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
++
  * (% style="color:#037691" %)**AT Command:**
  There is no AT Command to control Relay Output
@@ -1065,7 +1065,7 @@
  [[image:image-20220524093724-9.png]]
  )))
--Device will upload a packet if downlink code executes successfully.
++(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
@@ -1072,6 +1072,7 @@
  ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
++
  * (% style="color:#037691" %)**AT Command:**
  There is no AT Command to control Relay Output
@@ -1095,37 +1095,37 @@
  (% 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
++(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms
--Device will upload a packet if downlink code executes successfully.
++(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
  **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"]]
  * (% style="color:#037691" %)**AT Command:**
@@ -1142,9 +1142,10 @@
  ==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ====
++
  * (% style="color:#037691" %)**AT Command:**
--(% style="color:#037691" %)****(%%)**AT+SETCNT=aa,(bb cc dd ee) **
++**AT+SETCNT=aa,(bb cc dd ee) **
  aa: 1: Set count1,
@@ -1164,11 +1164,12 @@
  ==== 3.4.2.18 Counting ~-~- Clear Counting ====
++
  Clear counting for counting mode
  * (% style="color:#037691" %)**AT Command:**
--(% style="color:#037691" %)(%%)**AT+CLRCOUNT ** ~/~/ clear all counting
++**AT+CLRCOUNT ** ~/~/ clear all counting
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):**
@@ -1180,6 +1180,7 @@
  ==== 3.4.2.19 Counting ~-~- Change counting mode save time ====
++
  * (% style="color:#037691" %)**AT Command:**
  **AT+COUTIME=60  **~/~/ Set save time to 60 seconds. Device will save the counting result in internal flash every 60 seconds. (min value: 30)
@@ -1192,13 +1192,124 @@
  (((
  range: aa bb cc:0 to 16777215,  (unit:second)
++
++
  )))
++==== 3.4.2.20 Reset save DR DO state ====
++* (% style="color:#037691" %)**AT Command:**
++
++**AT+RODORET=1  **~/~/ RODO will close when the device joining the network. (default)
++
++**AT+RODORET=0  **~/~/After the device is reset, the previously saved RODO state (only MOD2 to MOD5) is read, and its state is not changed when it is reconnected to the network.
++
++
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):**
++
++**0x AD aa      **~/~/ same as AT+RODORET =aa
++
++(((
++
++
++
++
++==== 3.4.2.21 Encrypted payload ====
++
++
++* (% style="color:#037691" %)**AT Command:**
++
++**AT+DECRYPT=1  **~/~/ The payload is uploaded without encryption
++
++**AT+DECRYPT=0  **~/~/Encrypt when uploading payload (default)
++
++
++
++
++==== 3.4.2.22 Get sensor value ====
++
++
++* (% style="color:#037691" %)**AT Command:**
++
++**AT+GETSENSORVALUE=0  **~/~/ The serial port gets the reading of the current sensor
++
++**AT+GETSENSORVALUE=1  **~/~/The serial port gets the current sensor reading and uploads it.
++
++
++
++
++==== 3.4.2.23 Resets the downlink packet count ====
++
++
++* (% style="color:#037691" %)**AT Command:**
++
++**AT+DISFCNTCHECK=0  **~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node will no longer receive downlink packets (default)
++
++**AT+DISFCNTCHECK=1  **~/~/When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node resets the downlink packet count and keeps it consistent with the server downlink packet count.
++
++
++
++
++==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ====
++
++
++* (% style="color:#037691" %)**AT Command:**
++
++       **AT+DISMACANS=0**     ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of 11 bytes (DR0 of US915, DR2 of AS923, DR2 of AU195), the node will send a packet with a payload of 00 and a port of 4. (default)
++
++       **AT+DISMACANS=1**      ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of the DR, the node will ignore the MACANS and not reply, and only upload the payload part.
++
++
++* (% style="color:#037691" %)**Downlink Payload **(%%)**:**
++
++**0x21 00 01 **         ~/~/ Set  the DISMACANS=1
++
++
++
++
++==== 3.4.2.25 Copy downlink to uplink ====
++
++
++* (% style="color:#037691" %)**AT Command**(%%)**:**
++
++       **AT+RPL=5**     ~/~/ After receiving the package from the server, it will immediately upload the content of the package to the server, the port number is 100.
++
++Example：**aa xx xx xx xx**         ~/~/ aa indicates whether the configuration has changed, 00 is yes, 01 is no; xx xx xx xx are the bytes sent.
++
++[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173747-6.png?width=1124&height=165&rev=1.1||alt="image-20220823173747-6.png"]]
++
++For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
++
++[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]]
++
++For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
++
++
++
++==== 3.4.2.26 Query version number and frequency band 、TDC ====
++
++
++* (((
++(% style="color:#037691" %)**Downlink Payload**(%%)**:**
++
++**26 01  **  ~/~/ Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.
++
++
++)))
++
++**Example：**
++
++[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173929-8.png?width=1205&height=76&rev=1.1||alt="image-20220823173929-8.png"]]
++
++
++
++)))
++
  == 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:
  (((
@@ -1207,14 +1207,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.
@@ -1247,8 +1247,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]]
@@ -1257,6 +1257,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.
  )))
@@ -1263,7 +1263,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.
++
++
  )))
  )))
@@ -1288,10 +1288,10 @@
  )))
  * (((
--Connect sensor’s output to DI1-
++Connect sensor's output to DI1-
  )))
  * (((
--Connect sensor’s VCC to DI1+.
++Connect sensor's VCC to DI1+.
  )))
  (((
@@ -1299,15 +1299,17 @@
  )))
  (((
--[[image:1653968155772-850.png||height="23" width="19"]]**= DI1+ / 1K.**
++[[image:1653968155772-850.png||height="23" width="19"]]**= DI1**+** / 1K.**
  )))
  (((
--If DI1+ = 12v, the [[image:1653968155772-850.png||height="23" width="19"]]= 12mA , So the LT-22222-L will be able to detect this active signal.
++If** DI1+ **= **12v**, the [[image:1653968155772-850.png||height="23" width="19"]]= 12mA , So the LT-22222-L will be able to detect this active signal.
  )))
  (((
++
++
  )))
  (((
@@ -1319,10 +1319,10 @@
  )))
  * (((
--Connect sensor’s output to DI1+
++Connect sensor's output to DI1+
  )))
  * (((
--Connect sensor’s GND DI1-.
++Connect sensor's GND DI1-.
  )))
  (((
@@ -1339,6 +1339,8 @@
  (((
++
++
  )))
  (((
@@ -1350,10 +1350,10 @@
  )))
  * (((
--Connect sensor’s output to DI1+ with a serial 50K resistor
++Connect sensor's output to DI1+ with a serial 50K resistor
  )))
  * (((
--Connect sensor’s GND DI1-.
++Connect sensor's GND DI1-.
  )))
  (((
@@ -1372,6 +1372,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]]
@@ -1380,6 +1380,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:
@@ -1411,6 +1411,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:
  )))
@@ -1417,6 +1417,7 @@
  [[image:image-20220524100215-9.png]]
++
  [[image:image-20220524100215-10.png||height="382" width="723"]]
@@ -1423,13 +1423,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]]
@@ -1628,8 +1628,6 @@
  (((
  AT+CFG: Print all settings
--
--
  )))
@@ -1636,6 +1636,7 @@
  == 4.2 Common AT Command Sequence ==
++
  === 4.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
  (((
@@ -1675,8 +1675,6 @@
  (((
  (% style="background-color:#dcdcdc" %)ATZ
--
--
  )))
@@ -1748,6 +1748,8 @@
 . Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
 . Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.
 . The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5
++
++
  )))
  (((
@@ -1761,13 +1761,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? ==
@@ -1784,12 +1784,14 @@
  (((
  (% style="color:blue" %)**Step1**(%%)**:** Download [[flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]].
--(% style="color:blue" %)**Step2**(%%)**:** Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
++(% style="color:blue" %)**Step2**(%%)**:** Download the [[LT Image files>>url:https://www.dropbox.com/sh/g99v0fxcltn9r1y/AADKXQ2v5ZT-S3sxdmbvE7UAa/LT-22222-L/image?dl=0&subfolder_nav_tracking=1]].
  (% style="color:blue" %)**Step3**(%%)**:** Open flashloader; choose the correct COM port to update.
  (% 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]]
@@ -1801,6 +1801,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"]]
@@ -1809,6 +1809,8 @@
  == 5.2 How to change the LoRa Frequency Bands/Region? ==
++
++
  )))
  )))
@@ -1819,7 +1819,10 @@
  (((
++
  == 5.3 How to set up LT to work with Single Channel Gateway such as LG01/LG02? ==
++
++
  )))
  (((
@@ -1832,25 +1832,33 @@
  (((
  Assume we have a LG02 working in the frequency 868400000 now , below is the step.
++
  )))
  )))
  (((
--(% 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.
++
++
  )))
  (((
  [[image:1653360231087-571.png||height="401" width="727"]]
++
++
  )))
  (((
--(% 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:
++
++
  )))
  (((
@@ -1874,20 +1874,28 @@
  [[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.
@@ -1896,12 +1896,26 @@
  After restart, the status before power failure will be read from flash.
++
++== 5.7 Can i set up LT-22222-L as a NC(Normal Close) Relay? ==
++
++LT-22222-L built-in relay is NO (Normal Open). User can use an external relay to achieve Normal Close purpose. Diagram as below:
++
++[[image:image-20221006170630-1.png||height="610" width="945"]]
++
++
++
++
  = 6. Trouble Shooting =
++
++
  )))
  (((
  (((
--== 6.1 Downlink doesn’t work, how to solve it? ==
++== 6.1 Downlink doesn't work, how to solve it? ==
++
++
  )))
  )))
@@ -1912,7 +1912,10 @@
  (((
++
  == 6.2 Have trouble to upload image. ==
++
++
  )))
  (((
@@ -1922,7 +1922,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? ==
++
++
  )))
  (((
@@ -1936,19 +1936,20 @@
  (% 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 =
@@ -1966,18 +1966,26 @@
  * 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/]]
++* [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]]
  * [[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

image-20221006170630-1.png

Author

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

Size

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

Content