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

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

From 27.2 to 27.3 From 77.6 to 77.7

From version 27.3

edited by Xiaoling
on 2022/05/24 09:18

Change comment: There is no comment for this version

To version 77.6

edited by Xiaoling
on 2022/06/10 08:38

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -11,12 +11,15 @@
++
++
++
  = 1.Introduction =
  == 1.1 What is LT Series I/O Controller ==
  (((
--The Dragino LT series I/O Modules are Long Range LoRaWAN I/O Controller. It contains different I/O Interfaces such as: analog current Input, analog voltage input, relay output, digital input and digital output etc. The LT I/O Modules are designed to simplify the installation of I/O monitoring.
++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.
  )))
  (((
@@ -24,7 +24,7 @@
  )))
  (((
--The LT I/O Controllers is aiming to provide a simple plug and play, low cost installation by using LoRaWAN wireless technology.
++The LT I/O Controllers is aiming to provide an (% style="color:blue" %)**easy and low cost installation** (%%)by using LoRa wireless technology.
  )))
  (((
@@ -41,48 +41,128 @@
  (((
  [[image:1653295757274-912.png]]
++
++
  )))
  == 1.2  Specifications ==
++(((
++
++
  **Hardware System:**
++)))
--* STM32L072CZT6 MCU
--* SX1276/78 Wireless Chip
--* Power Consumption:
--** Idle: 4mA@12v
--** 20dB Transmit: 34mA@12v
++* (((
++STM32L072CZT6 MCU
++)))
++* (((
++SX1276/78 Wireless Chip
++)))
++* (((
++(((
++Power Consumption:
++)))
++* (((
++Idle: 4mA@12v
++)))
++* (((
++20dB Transmit: 34mA@12v
++)))
++)))
++
++
++(((
  **Interface for Model: LT22222-L:**
++)))
--* 2 x Digital dual direction Input (Detect High/Low signal, Max: 50v, or 220v with optional external resistor)
--* 2 x Digital Output (NPN output. Max pull up voltage 36V,450mA)
--* 2 x Relay Output (5A@250VAC / 30VDC)
--* 2 x 0~~20mA Analog Input (res:0.01mA)
--* 2 x 0~~30V Analog Input (res:0.01v)
--* Power Input 7~~ 24V DC.
++* (((
++2 x Digital dual direction Input (Detect High/Low signal, Max: 50v, or 220v with optional external resistor)
++)))
++* (((
++2 x Digital Output (NPN output. Max pull up voltage 36V,450mA)
++)))
++* (((
++2 x Relay Output (5A@250VAC / 30VDC)
++)))
++* (((
++2 x 0~~20mA Analog Input (res:0.01mA)
++)))
++* (((
++2 x 0~~30V Analog Input (res:0.01v)
++)))
++* (((
++Power Input 7~~ 24V DC.
++)))
++
++(((
  **LoRa Spec:**
++)))
--* Frequency Range:
--** Band 1 (HF): 862 ~~ 1020 Mhz
--** Band 2 (LF): 410 ~~ 528 Mhz
--* 168 dB maximum link budget.
--* +20 dBm - 100 mW constant RF output vs.
--* +14 dBm high efficiency PA.
--* Programmable bit rate up to 300 kbps.
--* High sensitivity: down to -148 dBm.
--* Bullet-proof front end: IIP3 = -12.5 dBm.
--* Excellent blocking immunity.
--* Low RX current of 10.3 mA, 200 nA register retention.
--* Fully integrated synthesizer with a resolution of 61 Hz.
--* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
--* Built-in bit synchronizer for clock recovery.
--* Preamble detection.
--* 127 dB Dynamic Range RSSI.
--* Automatic RF Sense and CAD with ultra-fast AFC.
--* Packet engine up to 256 bytes with CRC.
++* (((
++(((
++Frequency Range:
++)))
++* (((
++Band 1 (HF): 862 ~~ 1020 Mhz
++)))
++* (((
++Band 2 (LF): 410 ~~ 528 Mhz
++)))
++)))
++* (((
++168 dB maximum link budget.
++)))
++* (((
+++20 dBm - 100 mW constant RF output vs.
++)))
++* (((
+++14 dBm high efficiency PA.
++)))
++* (((
++Programmable bit rate up to 300 kbps.
++)))
++* (((
++High sensitivity: down to -148 dBm.
++)))
++* (((
++Bullet-proof front end: IIP3 = -12.5 dBm.
++)))
++* (((
++Excellent blocking immunity.
++)))
++* (((
++Low RX current of 10.3 mA, 200 nA register retention.
++)))
++* (((
++Fully integrated synthesizer with a resolution of 61 Hz.
++)))
++* (((
++FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
++)))
++* (((
++Built-in bit synchronizer for clock recovery.
++)))
++* (((
++Preamble detection.
++)))
++* (((
++127 dB Dynamic Range RSSI.
++)))
++* (((
++Automatic RF Sense and CAD with ultra-fast AFC.
++)))
++* (((
++Packet engine up to 256 bytes with CRC.
++
++
++)))
++
++
++
  == 1.3 Features ==
  * LoRaWAN Class A & Class C protocol
@@ -93,6 +93,8 @@
  * Firmware upgradable via program port
  * Counting
++
++
  == 1.4  Applications ==
  * Smart Buildings & Home Automation
@@ -102,6 +102,8 @@
  * Smart Cities
  * Smart Factory
++
++
  == 1.5 Hardware Variants ==
  (% border="1" style="background-color:#f7faff; width:500px" %)
@@ -115,6 +115,8 @@
  * 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.
@@ -125,21 +125,29 @@
  [[image:1653297104069-180.png]]
++
  = 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.
++)))
--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>>path:#AT_Command]] 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
++
++)))
++== 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:
  )))
@@ -160,10 +160,12 @@
  [[image:1653297955910-247.png||height="321" width="716"]]
++
  Add APP KEY and DEV EUI
  [[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.
  )))
@@ -170,6 +170,7 @@
  [[image:1653298044601-602.png||height="405" width="709"]]
++
  == 3.3 Uplink Payload ==
  There are five working modes + one interrupt mode on LT for different type application:
@@ -235,7 +235,9 @@
  **For LT-22222-L**: this mode the **DI1 and DI2** are used as counting pins.
++(((
  Total : 11 bytes payload
++)))
  [[image:image-20220523180452-3.png]]
@@ -249,54 +249,79 @@
  * FIRST: Indicate this is the first packet after join network.
  * 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.
++)))
++(((
  **To use counting mode, please run:**
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+MOD=2**
  )))
++)))
  (% class="box infomessage" %)
  (((
++(((
  **ATZ**
  )))
++)))
++(((
  (% style="color:#4f81bd" %)**AT Commands for counting:**
++)))
++(((
  **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 ) **
  )))
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+TRIG2=0,100 (set DI2 port to trigger on low level, valid signal is 100ms) **
  )))
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+TRIG2=1,100 (set DI2 port to trigger on high level, valid signal is 100ms ) **
  )))
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+SETCNT=1,60   (Set COUNT1 value to 60)**
  )))
++)))
  (% class="box infomessage" %)
  (((
++(((
  **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.
@@ -313,22 +313,34 @@
  * FIRST: Indicate this is the first packet after join network.
  * 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.
++)))
++(((
  **To use counting mode, please run:**
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+MOD=3**
  )))
++)))
  (% class="box infomessage" %)
  (((
++(((
  **ATZ**
  )))
++)))
--Other AT Commands for counting are similar to [[MOD2 Counting Command>>path:#COUNT_COMMAND]].
++(((
++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 ===
  **LT22222-L**: This mode the DI1 is used as a counting pin.
@@ -347,45 +347,69 @@
  * FIRST: Indicate this is the first packet after join network.
  * 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.
++)))
++(((
  **To use this mode, please run:**
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+MOD=4**
  )))
++)))
  (% class="box infomessage" %)
  (((
++(((
  **ATZ**
  )))
++)))
++(((
++
++)))
--Other AT Commands for counting are similar to [[MOD2 Counting Command>>path:#COUNT_COMMAND]].
++(((
++Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]].
++)))
++(((
  **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)**
  )))
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+VOLMAX=20000,0   (If AVI1 voltage lower 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)**
  )))
++)))
++
  === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI ===
  **LT22222-L**: This mode the DI1 is used as a counting pin.
@@ -398,24 +398,38 @@
  * RO is for relay. ROx=1 : close，ROx=0 always open.
  * FIRST: Indicate this is the first packet after join network.
--* DO is for reverse digital output. DOx=1: output low, DOx=0: high or float.
++* (((
++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.
++)))
++(((
  **To use this mode, please run:**
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+MOD=5**
  )))
++)))
  (% class="box infomessage" %)
  (((
++(((
  **ATZ**
  )))
++)))
--Other AT Commands for counting are similar to [[MOD2 Counting Command>>path:#COUNT_COMMAND]].
++(((
++Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]].
++
++)))
++
  === 3.3.6 AT+ADDMOD~=6. (Trigger Mode, Optional) ===
  (% style="color:#4f81bd" %)**This mode is an optional mode for trigger purpose. It can run together with other mode.**
@@ -442,6 +442,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>
@@ -450,6 +450,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.
@@ -463,7 +463,7 @@
  **Downlink Command to set Trigger Condition**
--Type Code: 0xAA. Downlink command same as AT Command [[AT+AVLIM, AT+ACLIM>>path:#AT_Trigger]]
++Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
  Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
@@ -483,7 +483,7 @@
  Same as AT+AVLIM=5000,0,0,0   (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore)
--Example2: AA 02 01 00
++**Example2**: AA 02 01 00
  Same as AT+ DTRI =1,0  (Enable DI1 trigger / disable DI2 trigger)
@@ -536,10 +536,13 @@
  When device got this command, it will send the MOD6 payload.
++
  === 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/]]
++
++
  )))
  == 3.4 Configure LT via AT or Downlink ==
@@ -550,14 +550,15 @@
  There are two kinds of Commands:
  )))
--* (% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.5.4, user can find what common commands it supports: http:~/~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands
++* (% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, 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]]
  * (% 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>>http://8.211.40.43:8080/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
++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]]
++
  === 3.4.2 Sensor related commands ===
  ==== 3.4.2.1 Set Transmit Interval ====
@@ -601,6 +601,7 @@
  **0x0A aa     ~/~/ Same as AT+MOD=aa**
  )))
++
  ==== 3.4.2.3 Poll an uplink ====
  * AT Command:
@@ -619,7 +619,7 @@
  ==== 3.4.2.4 Enable Trigger Mode ====
--Use of trigger mode, please check [[ADDMOD6>>path:http://8.211.40.43:8080/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LT-22222-L/#H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29]]
++Use of trigger mode, please check [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
  * AT Command:
@@ -632,13 +632,15 @@
 : Disable Trigger Mode
--
  * Downlink Payload (prefix 0x0A 06):
--0x0A 06 aa     ~/~/ Same as AT+ADDMOD6=aa,
++(% class="box infomessage" %)
++(((
++**0x0A 06 aa     ~/~/ Same as AT+ADDMOD6=aa,**
++)))
--==== Poll trigger settings ====
++==== 3.4.2.5 Poll trigger settings ====
  Poll trigger settings,
@@ -646,339 +646,347 @@
  There is no AT Command for this feature.
--
  * Downlink Payload (prefix 0x AB 06):
--0xAB 06  ~/~/ Poll trigger settings, device will uplink [[trigger settings>>path:#Trigger_Settings]] once receive this command
++(% class="box infomessage" %)
++(((
++**0xAB 06  ~/~/ Poll trigger settings, device will uplink trigger settings once receive this command**
++)))
--==== Enable / Disable DI1/DI2/DI3 as trigger ====
++==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ====
  Enable Disable DI1/DI2/DI2 as trigger,
  * AT Command:
--Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >
++(% class="box infomessage" %)
++(((
++**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
++)))
--Example:
++**Example:**
  AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
--
--
  * Downlink Payload (prefix 0xAA 02):
--0xAA 02 aa bb  ~/~/ Same as AT+DTRI=aa,bb
++(% class="box infomessage" %)
++(((
++**0xAA 02 aa bb  ~/~/ Same as AT+DTRI=aa,bb**
++)))
++==== 3.4.2.7 Trigger1 – Set DI1 or DI3 as trigger ====
--==== Trigger1 – Set DI1 or DI3 as trigger ====
--
  Set DI1 or DI3(for LT-33222-L) trigger.
  * AT Command:
--AT+TRIG1=a,b
++(% class="box infomessage" %)
++(((
++**AT+TRIG1=a,b**
++)))
  a : Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
  b : delay timing.
--Example:
++**Example:**
  AT+TRIG1=1,100(set DI1 port to trigger on high level, valid signal is 100ms )
--
  * 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)**
++)))
--==== Trigger2 – Set DI2 as trigger ====
++==== 3.4.2.8 Trigger2 – Set DI2 as trigger ====
  Set DI2 trigger.
  * AT Command:
--AT+TRIG2=a,b
++(% 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.
--Example:
++**Example:**
  AT+TRIG2=0,100(set DI1 port to trigger on low level, valid signal is 100ms )
--
  * Downlink Payload (prefix 0x09 02 ):
--0x09 02 aa bb cc ~/~/ same as AT+TRIG1=aa,0x(bb cc)
++(% class="box infomessage" %)
++(((
++**0x09 02 aa bb cc ~/~/ same as AT+TRIG1=aa,0x(bb cc)**
++)))
--==== Trigger – Set AC (current) as trigger ====
++==== 3.4.2.9 Trigger – Set AC (current) as trigger ====
--Set current trigger , base on AC port. See [[trigger mode>>path:#MOD6]]
++Set current trigger , base on AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
  * AT Command:
--AT+ACLIM. See [[trigger mode>>path:#MOD6]]
++(% class="box infomessage" %)
++(((
++**AT+ACLIM. **
++)))
--
  * Downlink Payload (prefix 0xAA 01 ):
--0x AA 01 aa bb cc dd ee ff gg hh ~/~/ same as AT+ACLIM See [[trigger mode>>path:#MOD6]]
++(% 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"]]**
++)))
--==== Trigger – Set AV (voltage) as trigger ====
++==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
--Set current trigger , base on AV port. See [[trigger mode>>path:#MOD6]]
++Set current trigger , base on AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
  * AT Command:
--AT+AVLIM. See [[trigger mode>>path:#MOD6]]
++(% class="box infomessage" %)
++(((
++**AT+AVLIM. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]**
++)))
--
  * Downlink Payload (prefix 0xAA 00 ):
--0x AA 00 aa bb cc dd ee ff gg hh ~/~/ same as AT+AVLIM See [[trigger mode>>path:#MOD6]]
++(% 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"]] **
++)))
--==== Trigger – Set minimum interval ====
++==== 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:
--AT+ATDC=5. Device won’t response the second trigger within 5 minute after the first trigger.
++(% class="box infomessage" %)
++(((
++**AT+ATDC=5. Device won’t response the second trigger within 5 minute after the first trigger.**
++)))
--
  * Downlink Payload (prefix 0xAC ):
--0x AC aa bb ~/~/ same as AT+ATDC=0x(aa bb)   . Unit (min)
++(% class="box infomessage" %)
++(((
++**0x AC aa bb ~/~/ same as AT+ATDC=0x(aa bb)   . Unit (min)**
++)))
--==== DO ~-~- Control Digital Output DO1/DO2/DO3 ====
++==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
  * AT Command:
  There is no AT Command to control Digital Output
--
  * 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.
++)))
++(((
 : Low,  00: High ,  11: No action
++)))
--(% border="1" style="background-color:#f7faff" %)
--|Downlink Code|DO1|DO2|DO3
--|02  01  00  11|Low|High|No Action
--|02  00  11  01|High|No Action|Low
--|02  11  01  00|No Action|Low|High
++[[image:image-20220524092754-5.png]]
--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.
++)))
--Device will upload a packet if downlink code executes successfully.
++(((
++(% style="color:red" %)Device will upload a packet if downlink code executes successfully.
++)))
++==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
--
--
--==== DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
--
  * AT Command:
  There is no AT Command to control Digital Output
--
  * Downlink Payload (prefix 0xA9):
--0xA9 aa bb cc     ~/~/ Set DO1/DO2/DO3 output with time control
++(% class="box infomessage" %)
++(((
++(((
++**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:
--**First Byte:** Type code (0xA9)
++(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
--**Second Byte**: Inverter Mode
++(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode
 : DO pins will change back to original state after timeout.
 : DO pins will change to an inverter state after timeout
++(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Ports status:
--**Third Byte**: Control Method and Ports status:
++[[image:image-20220524093238-6.png]]
--(% border="1" style="background-color:#f7faff" %)
--|Second Byte|Status
--|0x01|DO1 set to low
--|0x00|DO1 set to high
--|0x11|DO1 NO Action
++(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Ports status:
--**Fourth Byte**: Control Method and Ports status:
++[[image:image-20220524093328-7.png]]
--(% border="1" style="background-color:#f7faff" %)
--|Second Byte|Status
--|0x01|DO2 set to low
--|0x00|DO2 set to high
--|0x11|DO2 NO Action
++(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Ports status:
--**Fifth Byte**: Control Method and Ports status:
++[[image:image-20220524093351-8.png]]
--(% border="1" style="background-color:#f7faff" %)
--|Second Byte|Status
--|0x01|DO3 set to low
--|0x00|DO3 set to high
--|0x11|DO3 NO Action
++(% style="color:#4f81bd" %)**Sixth and Seventh Byte**:
--**Sixth and Seventh Byte**:
--
           Latching time. Unit: ms
  Device will upload a packet if downlink code executes successfully.
++**Example payload:**
++**~1. A9 01 01 01 01 07 D0**
--Example payload:
--
--1. A9 01 01 01 01 07 D0
--
  DO1 pin & DO2 pin & DO3 pin will be set to Low, last 2 seconds, then change back to original state.
++**2. A9 01 00 01 11 07 D0**
--1. A9 01 00 01 11 07 D0
--
  DO1 pin set high, DO2 pin set low, DO3 pin no action, last 2 seconds, then change back to original state.
++**3. A9 00 00 00 00 07 D0**
--1. A9 00 00 00 00 07 D0
--
  DO1 pin & DO2 pin & DO3 pin will be set to high, last 2 seconds, then both change to low.
++**4. A9 00 11 01 00 07 D0**
--1. A9 00 11 01 00 07 D0
--
  DO1 pin no action, DO2 pin set low, DO3 pin set high, last 2 seconds, then DO1 pin no action, DO2 pin set high, DO3 pin set low
++=== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ===
--
--==== Relay ~-~- Control Relay Output RO1/RO2 ====
--
  * AT Command:
  There is no AT Command to control Relay Output
--
  * Downlink Payload (prefix 0x03):
--0x03 aa bb     ~/~/ Set RO1/RO2 output
++(% class="box infomessage" %)
++(((
++**0x03 aa bb     ~/~/ Set RO1/RO2 output**
++)))
++(((
  If payload = 0x030100, it means set RO1 to close and RO2 to open.
++)))
++(((
 : Close ,  00: Open , 11: No action
++)))
--(% border="1" style="background-color:#f7faff" %)
--|Downlink Code|RO1|RO2
--|03  00  11|Open|No Action
--|03  01  11|Close|No Action
--|03  11  00|No Action|Open
--|03  11  01|No Action|Close
--|03  00  00|Open|Open
--|03  01  01|Close|Close
--|03  01  00|Close|Open
--|03  00  01|Open|Close
++(((
++[[image:image-20220524093724-9.png]]
++)))
  Device will upload a packet if downlink code executes successfully.
--==== Relay ~-~- Control Relay Output RO1/RO2 with time control ====
++==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
  * AT Command:
  There is no AT Command to control Relay Output
--
  * Downlink Payload (prefix 0x05):
--0x05 aa bb cc dd     ~/~/ Set RO1/RO2 relay with time control:
++(% class="box infomessage" %)
++(((
++**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:
--**First Byte:** Type code (0x05)
++(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
--**Second Byte(aa)**: Inverter Mode
++(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
 : Relays will change back to original state after timeout.
 : Relays will change to an inverter state after timeout
++(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
--**Third Byte(bb)**: Control Method and Ports status:
++[[image:image-20220524093831-10.png]]
--(% border="1" style="background-color:#f7faff" %)
--|Value|Status
--|0x11|RO1 and RO2 to NO
--|0x10|RO2 to NO, RO1 to NC
--|0x01|RO2 to NC, RO1 to NO
--|0x00|RO1 and RO2 to NC.
--|0x20|RO1 No Action, RO2 to NC
--|0x21|RO1 No Action, RO2 to NO
--|0x02|RO1 to NC, RO2 No Action
--|0x12|RO1 to NO, RO2 No Action
++(% style="color:#4f81bd" %)**Fourth/Fifth Bytes(cc)**(%%): Latching time. Unit: ms
--**Fourth / Fifth Bytes (cc)**: Latching time. Unit: ms
--
  Device will upload a packet if downlink code executes successfully.
--
--
  **Example payload:**
--1. 05 01 11 07 D0
++**~1. 05 01 11 07 D0**
  Relay1 and Relay 2 will be set to NO , last 2 seconds, then change back to original state.
++**2. 05 01 10 07 D0**
--1. 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.
++**3. 05 00 01 07 D0**
--1. 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.
++**4. 05 00 00 07 D0**
--1. 05 00 00 07 D0
--
  Relay 1 & relay2 will change to NC, last 2 seconds, then both change to NO.
++==== 3.4.2.16 Counting ~-~- Voltage threshold counting ====
++When voltage exceed the threshold, count. Feature see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
--
--
--==== Counting ~-~- Voltage threshold counting ====
--
--When voltage exceed the threshold, count. Feature see [[MOD4>>path:#MOD4]]
--
  * AT Command:
--AT+VOLMAX    ~/~/ See [[MOD4>>path:#MOD4]]
++(% class="box infomessage" %)
++(((
++**AT+VOLMAX    ~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]**
++)))
--
  * Downlink Payload (prefix 0xA5):
--0xA5 aa bb cc   ~/~/ Same as AT+VOLMAX=(aa bb),cc
++(% class="box infomessage" %)
++(((
++**0xA5 aa bb cc   ~/~/ Same as AT+VOLMAX=(aa bb),cc**
++)))
--==== Counting ~-~- Pre-configure the Count Number ====
++==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ====
  * AT Command:
--AT+SETCNT=aa,(bb cc dd ee)
++(% class="box infomessage" %)
++(((
++**AT+SETCNT=aa,(bb cc dd ee) **
++)))
  aa: 1: Set count1,
@@ -988,182 +988,234 @@
  Bb cc dd ee: number to be set
--
  * Downlink Payload (prefix 0xA8):
--0x A8 aa bb cc dd ee     ~/~/ same as AT+SETCNT=aa,(bb cc dd ee)
++(% class="box infomessage" %)
++(((
++**0x A8 aa bb cc dd ee     ~/~/ same as AT+SETCNT=aa,(bb cc dd ee)**
++)))
++==== 3.4.2.18 Counting ~-~- Clear Counting ====
--
--
--==== Counting ~-~- Clear Counting ====
--
  Clear counting for counting mode
  * AT Command:
--AT+CLRCOUNT  ~/~/ clear all counting
++(% class="box infomessage" %)
++(((
++**AT+CLRCOUNT  ~/~/ clear all counting**
++)))
--
  * Downlink Payload (prefix 0xA6):
--0x A6 01     ~/~/ clear all counting,
++(% class="box infomessage" %)
++(((
++**0x A6 01     ~/~/ clear all counting,**
++)))
++==== 3.4.2.19 Counting ~-~- Change counting mode save time ====
--
--==== Counting ~-~- Change counting mode save time ====
--
  * 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)
++(% 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)**
++)))
--
  * Downlink Payload (prefix 0xA7):
--0x A7 aa bb cc     ~/~/ same as AT+COUTIME =aa bb cc,
++(% class="box infomessage" %)
++(((
++**0x A7 aa bb cc     ~/~/ same as AT+COUTIME =aa bb cc,**
++)))
++(((
  range: aa bb cc:0 to 16777215,  (unit:second)
++
++)))
++== 3.5 Integrate with Mydevice ==
--
--1.
--11. 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:
++(((
++**Step 1**: Be sure that your device is programmed and properly connected to the network at this time.
++)))
--Step 1: Be sure that your device is programmed and properly connected to the network at this time.
++(((
++**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:
++)))
--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-20220524094641-11.png||height="390" width="723"]]
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image010.png]]
++[[image:image-20220524094641-12.png||height="402" width="718"]]
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.png]]
++**Step 3**: Create an account or log in Mydevices.
++**Step 4**: Search LT-22222-L(for both LT-22222-L / LT-33222-L) and add DevEUI.(% style="display:none" %)
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image012.png]]
--
--
--
--Step 3: Create an account or log in Mydevices.
--
--Step 4: Search LT-22222-L(for both LT-22222-L / LT-33222-L) and add DevEUI.
--
  Search under The things network
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
++[[image:1653356838789-523.png||height="337" width="740"]]
  After added, the sensor data arrive TTN, it will also arrive and show in Mydevices.
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
++[[image:image-20220524094909-1.png||height="335" width="729"]]
++[[image:image-20220524094909-2.png||height="337" width="729"]]
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
++[[image:image-20220524094909-3.png||height="338" width="727"]]
++[[image:image-20220524094909-4.png||height="339" width="728"]](% style="display:none" %)
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
++[[image:image-20220524094909-5.png||height="341" width="734"]]
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
++== 3.6 Interface Detail ==
++=== 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) ===
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
--
--
--1.
--11. Interface Detail
--111. Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active )
--
  Support NPN Type sensor
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
++[[image:1653356991268-289.png]]
++=== 3.6.2 Digital Input Port: DI1/DI2 ( For LT-22222-L) ===
--1.
--11.
--111. Digital Input Port: DI1/DI2 ( For LT-22222-L)
--
++(((
  The DI port of LT-22222-L can support NPN or PNP output sensor.
++)))
++(((
++(((
  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
++)))
++)))
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
++[[image:1653357170703-587.png]]
++(((
++(((
  When use need to connect a device to the DI port, both DI1+ and DI1- must be connected.
++)))
++)))
++(((
++
++)))
++(((
  **Example1**: Connect to a Low active sensor.
++)))
++(((
  This type of sensor will output a low signal GND when active.
++)))
--* Connect sensor’s output to DI1-
--* Connect sensor’s VCC to DI1+.
++* (((
++Connect sensor’s output to DI1-
++)))
++* (((
++Connect sensor’s VCC to DI1+.
++)))
--So when sensor active, the current between NEC2501 pin1 and pin2 is:
++(((
++So when sensor active, the current between NEC2501 pin1 and pin2 is：
++)))
--  //IF//[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]  = DI1+ / 1K.
++(((
++[[image:1653968155772-850.png||height="23" width="19"]]**= DI1+ / 1K.**
++)))
--If DI1+ = 12v, the //IF//[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]  = 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.
++)))
++(((
++
++)))
++(((
  **Example2**: Connect to a High active sensor.
++)))
++(((
  This type of sensor will output a high signal (example 24v) when active.
++)))
--* Connect sensor’s output to DI1+
--* Connect sensor’s GND DI1-.
++* (((
++Connect sensor’s output to DI1+
++)))
++* (((
++Connect sensor’s GND DI1-.
++)))
++(((
  So when sensor active, the current between NEC2501 pin1 and pin2 is:
++)))
--  //IF//[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]  = DI1+ / 1K.
++(((
++[[image:1653968155772-850.png||height="23" width="19"]]**= DI1+ / 1K.**
++)))
--If DI1+ = 24v, the //IF//[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]  = 24mA , So the LT-22222-L will be able to detect this high active signal.
++(((
++If **DI1+ = 24v**, the[[image:1653968155772-850.png||height="23" width="19"]] 24mA , So the LT-22222-L will be able to detect this high active signal.
++)))
++(((
++
++)))
--**Example3**: Connect to a 220v high active sensor.公司测试一下
++(((
++**Example3**: Connect to a 220v high active sensor.
++)))
++(((
  Assume user want to monitor an active signal higher than 220v, to make sure not burn the photocoupler
++)))
--* Connect sensor’s output to DI1+ with a serial 50K resistor
--* Connect sensor’s GND DI1-.
++* (((
++Connect sensor’s output to DI1+ with a serial 50K resistor
++)))
++* (((
++Connect sensor’s GND DI1-.
++)))
++(((
  So when sensor active, the current between NEC2501 pin1 and pin2 is:
++)))
--  //IF//[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]  = DI1+ / 51K.
++(((
++   [[image:1653968155772-850.png||height="23" width="19"]]**= DI1+ / 51K.**
++)))
--If sensor output is 220v, the //IF//[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]  = 4.3mA , So the LT-22222-L will be able to detect this high active signal safely.
++(((
++If sensor output is 220v, the [[image:1653968155772-850.png||height="23" width="19"]](% id="cke_bm_243359S" style="display:none" %)[[image:image-20220524095628-8.png]](%%) = DI1+ / 51K.  = 4.3mA , So the LT-22222-L will be able to detect this high active signal safely.
++)))
--1.
--11.
--111. Digital Output Port: DO1/DO2 /DO3
++=== 3.6.3 Digital Output Port: DO1/DO2 /DO3 ===
  NPN output: GND or Float. Max voltage can apply to output pin is 36v.
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
++[[image:1653357531600-905.png]]
++=== 3.6.4 Analog Input Interface ===
--
--1.
--11.
--111. 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:
--AC2 = (IN2 voltage )/12
++**AC2 = (IN2 voltage )/12**
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
++[[image:1653357592296-182.png]]
--
--
  Example to connect a 4~~20mA sensor
  We take the wind speed sensor as an example for reference only.
@@ -1179,423 +1179,639 @@
  Connection diagram:
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.jpg]]
++[[image:1653357640609-758.png]]
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
++[[image:1653357648330-671.png||height="155" width="733"]]
++=== 3.6.5 Relay Output ===
--1.
--11.
--111. 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:
++)))
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
++[[image:image-20220524100215-9.png]]
++[[image:image-20220524100215-10.png||height="382" width="723"]]
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
++== 3.7 LEDs Indicators ==
++[[image:image-20220524100748-11.png]]
++= 4. Use AT Command =
--1.
--11. LEDs Indicators
++== 4.1 Access AT Command ==
--(% border="1" style="background-color:#f7faff" %)
--|**LEDs**|**Feature**
--|**PWR**|Always on if there is power
--|**SYS**|After device is powered on, the SYS will **fast blink in GREEN** for 5 times, means RS485-LN start to join LoRaWAN network. If join success, SYS will be **on GREEN for 5 seconds. **SYS will **blink Blue** on every upload and **blink Green** once receive a downlink message.
--|**TX**|(((
--Device boot: TX blinks 5 times.
++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.
--Successful join network: TX ON for 5 seconds.
++[[image:1653358238933-385.png]]
--Transmit a LoRa packet: TX blinks once
++(((
++In PC, User needs to set (% style="color:#4f81bd" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600**(%%) to access to access serial console for LT. The AT commands are disable by default and need to enter password (default:(% style="color:green" %)**123456**)(%%) to active it. As shown below:
  )))
--|**RX**|RX blinks once when receive a packet.
--|**DO1**|
--|**DO2**|
--|**DO3**|
--|**DI2**|(((
--For LT-22222-L: ON when DI2 is high, LOW when DI2 is low
--For LT-33222-L: ON when DI2 is low, LOW when DI2 is high
--)))
--|**DI2**|(((
--For LT-22222-L: ON when DI2 is high, LOW when DI2 is low
++[[image:1653358355238-883.png]]
--For LT-33222-L: ON when DI2 is low, LOW when DI2 is high
++(((
++More detail AT Command manual can be found at [[AT Command Manual>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
  )))
--|**DI3**|For LT-33222-L ONLY: ON when DI3 is low, LOW when DI3 is high
--|**DI2**|(((
--For LT-22222-L: ON when DI2 is high, LOW when DI2 is low
--For LT-33222-L: ON when DI2 is low, LOW when DI2 is high
++(((
++AT+<CMD>?        : Help on <CMD>
  )))
--|**RO1**|
--|**RO2**|
--1. Use AT Command
--11. 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:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
--
--
--In PC, User needs to set **serial tool**(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to **9600** to access to access serial console for LT. The AT commands are disable by default and need to enter password (default:**123456**) to active it. As shown below:
--
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
--
--
--More detail AT Command manual can be found at [[AT Command Manual>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
--
--AT+<CMD>?        : Help on <CMD>
--
++(((
  AT+<CMD>         : Run <CMD>
++)))
++(((
  AT+<CMD>=<value> : Set the value
++)))
++(((
  AT+<CMD>=?       : Get the value
++)))
++(((
  ATZ: Trig a reset of the MCU
++)))
++(((
  AT+FDR: Reset Parameters to Factory Default, Keys Reserve
++)))
++(((
  AT+DEUI: Get or Set the Device EUI
++)))
++(((
  AT+DADDR: Get or Set the Device Address
++)))
++(((
  AT+APPKEY: Get or Set the Application Key
++)))
++(((
  AT+NWKSKEY: Get or Set the Network Session Key
++)))
++(((
  AT+APPSKEY: Get or Set the Application Session Key
++)))
++(((
  AT+APPEUI: Get or Set the Application EUI
++)))
++(((
  AT+ADR: Get or Set the Adaptive Data Rate setting. (0: off, 1: on)
++)))
++(((
  AT+TXP: Get or Set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Spec)
++)))
++(((
  AT+DR: Get or Set the Data Rate. (0-7 corresponding to DR_X)
++)))
++(((
  AT+DCS: Get or Set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
++)))
++(((
  AT+PNM: Get or Set the public network mode. (0: off, 1: on)
++)))
++(((
  AT+RX2FQ: Get or Set the Rx2 window frequency
++)))
++(((
  AT+RX2DR: Get or Set the Rx2 window data rate (0-7 corresponding to DR_X)
++)))
++(((
  AT+RX1DL: Get or Set the delay between the end of the Tx and the Rx Window 1 in ms
++)))
++(((
  AT+RX2DL: Get or Set the delay between the end of the Tx and the Rx Window 2 in ms
++)))
++(((
  AT+JN1DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
++)))
++(((
  AT+JN2DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
++)))
++(((
  AT+NJM: Get or Set the Network Join Mode. (0: ABP, 1: OTAA)
++)))
++(((
  AT+NWKID: Get or Set the Network ID
++)))
++(((
  AT+FCU: Get or Set the Frame Counter Uplink
++)))
++(((
  AT+FCD: Get or Set the Frame Counter Downlink
++)))
++(((
  AT+CLASS: Get or Set the Device Class
++)))
++(((
  AT+JOIN: Join network
++)))
++(((
  AT+NJS: Get OTAA Join Status
++)))
++(((
  AT+SENDB: Send hexadecimal data along with the application port
++)))
++(((
  AT+SEND: Send text data along with the application port
++)))
++(((
  AT+RECVB: Print last received data in binary format (with hexadecimal values)
++)))
++(((
  AT+RECV: Print last received data in raw format
++)))
++(((
  AT+VER: Get current image version and Frequency Band
++)))
++(((
  AT+CFM: Get or Set the confirmation mode (0-1)
++)))
++(((
  AT+CFS: Get confirmation status of the last AT+SEND (0-1)
++)))
++(((
  AT+SNR: Get the SNR of the last received packet
++)))
++(((
  AT+RSSI: Get the RSSI of the last received packet
++)))
++(((
  AT+TDC: Get or set the application data transmission interval in ms
++)))
++(((
  AT+PORT: Get or set the application port
++)))
++(((
  AT+DISAT: Disable AT commands
++)))
++(((
  AT+PWORD: Set password, max 9 digits
++)))
++(((
  AT+CHS: Get or Set Frequency (Unit: Hz) for Single Channel Mode
++)))
++(((
  AT+CHE: Get or Set eight channels mode, Only for US915, AU915, CN470
++)))
++(((
  AT+CFG: Print all settings
++
++)))
++== 4.2 Common AT Command Sequence ==
--1.
--11. Common AT Command Sequence
--111. Multi-channel ABP mode (Use with SX1301/LG308)
++=== 4.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
++(((
  If device has not joined network yet:
++)))
--123456
++(((
++(% style="background-color:#dcdcdc" %)123456
++)))
--AT+FDR
++(((
++(% style="background-color:#dcdcdc" %)AT+FDR
++)))
--123456
++(((
++(% style="background-color:#dcdcdc" %)123456
++)))
--AT+NJM=0
++(((
++(% style="background-color:#dcdcdc" %)AT+NJM=0
++)))
--ATZ
++(((
++(% style="background-color:#dcdcdc" %)ATZ
++)))
++(((
  If device already joined network:
++)))
--AT+NJM=0
++(((
++(% style="background-color:#dcdcdc" %)AT+NJM=0
++)))
--ATZ
++(((
++(% style="background-color:#dcdcdc" %)ATZ
--1.
--11.
--111. Single-channel ABP mode (Use with LG01/LG02)
++
++)))
--123456   Enter Password to have AT access.
++=== 4.2.2 Single-channel ABP mode (Use with LG01/LG02) ===
--AT+FDR   Reset Parameters to Factory Default, Keys Reserve
++(((
++(% style="background-color:#dcdcdc" %) 123456(%%)   Enter Password to have AT access.
++)))
--123456   Enter Password to have AT access.
++(((
++(% style="background-color:#dcdcdc" %) AT+FDR(%%)   Reset Parameters to Factory Default, Keys Reserve
++)))
--AT+CLASS=C Set to work in CLASS C
++(((
++(% style="background-color:#dcdcdc" %) 123456(%%)   Enter Password to have AT access.
++)))
--AT+NJM=0 Set to ABP mode
++(((
++(% style="background-color:#dcdcdc" %) AT+CLASS=C(%%) Set to work in CLASS C
++)))
--AT+ADR=0 Set the Adaptive Data Rate Off
++(((
++(% style="background-color:#dcdcdc" %) AT+NJM=0(%%) Set to ABP mode
++)))
--AT+DR=5  Set Data Rate
++(((
++(% style="background-color:#dcdcdc" %) AT+ADR=0(%%) Set the Adaptive Data Rate Off
++)))
--AT+TDC=60000  Set transmit interval to 60 seconds
++(((
++(% style="background-color:#dcdcdc" %) AT+DR=5(%%)  Set Data Rate
++)))
--AT+CHS=868400000 Set transmit frequency to 868.4Mhz
++(((
++(% style="background-color:#dcdcdc" %) AT+TDC=60000(%%)  Set transmit interval to 60 seconds
++)))
--AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
++(((
++(% style="background-color:#dcdcdc" %) AT+CHS=868400000(%%) Set transmit frequency to 868.4Mhz
++)))
--AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
++(((
++(% style="background-color:#dcdcdc" %) AT+RX2FQ=868400000(%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
++)))
--AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
++(((
++(% style="background-color:#dcdcdc" %) AT+RX2DR=5(%%)  Set RX2DR to match the downlink DR from server. see below
++)))
--ATZ          Reset MCU
++(((
++(% style="background-color:#dcdcdc" %) AT+DADDR=26 01 1A F1 (%%)Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
++)))
--**Note:**
++(((
++(% style="background-color:#dcdcdc" %) ATZ         (%%) Reset MCU
++)))
--1. Make sure the device is set to ABP mode in the IoT Server.
--1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
--1. 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.
--1. 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
++(((
++(% style="color:red" %)**Note:**
++)))
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]]
++(((
++(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
++2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
++3. 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.
++4. 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
++)))
++(((
++[[image:1653359097980-169.png||height="188" width="729"]]
++)))
--1.
--11.
--111. Change to Class A
++(((
++
++)))
--If sensor JOINED
++=== 4.2.3 Change to Class A ===
--AT+CLASS=A
--
++If sensor JOINED
++(% style="background-color:#dcdcdc" %)AT+CLASS=A
  ATZ
++= 5. FAQ =
++== 5.1 How to upgrade the image? ==
--
--1. FAQ
--
--1.
--11. How to upgrade the image?
--
  The LT LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to LT to:
  * Support new features
  * For bug fix
  * Change LoRaWAN bands.
--
  Below shows the hardware connection for how to upload an image to the LT:
++* [[image:1653359603330-121.png]]
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
--
--
++(((
  **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]].
--
  **Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
--
  **Step3: **Open flashloader; choose the correct COM port to update.
--
--**For LT-33222-L**:
--
--Hold down the PRO button and then momentarily press the RST reset button and the **DO2 led** will change from OFF to ON. When **DO2 LED** is on, it means the device is in download mode.
--
  **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.
--
--
--
--|(((
--Board detected
  )))
--|(((
--
--)))
++  [[image:image-20220524103407-12.png]]
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image032.png]]            [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image033.png]]
++[[image:image-20220524103429-13.png]]
++[[image:image-20220524104033-15.png]]
++(% 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:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image034.png]]           [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image035.png]]
++[[image:1653360054704-518.png||height="186" width="745"]]
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image036.png]]   [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image037.png]]
++(((
++(((
++== 5.2 How to change the LoRa Frequency Bands/Region? ==
++)))
++)))
++(((
++User can follow the introduction for [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
--**Notice**: In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
++
++)))
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image038.png]]
++(((
++== 5.3 How to set up LT to work with Single Channel Gateway such as LG01/LG02? ==
++)))
--
--1.
--11. How to change the LoRa Frequency Bands/Region?
--
--User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
--
--
--1.
--11. How to set up LT to work with Single Channel Gateway such as LG01/LG02?
--
++(((
++(((
  In this case, users need to set LT-33222-L to work in ABP mode & transmit in only one frequency.
++)))
++)))
++(((
++(((
  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.
++)))
--**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"]]
++)))
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image039.png]]
++(((
++(% 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.
++)))
--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="background-color:#dcdcdc" %)123456 (%%)  Enter Password to have AT access.
++(% style="background-color:#dcdcdc" %)AT+FDR  (%%) Reset Parameters to Factory Default, Keys Reserve
++(% style="background-color:#dcdcdc" %)123456  (%%) Enter Password to have AT access.
++(% style="background-color:#dcdcdc" %)AT+NJM=0 (%%)Set to ABP mode
++(% style="background-color:#dcdcdc" %)AT+ADR=0 (%%)Set the Adaptive Data Rate Off
++(% style="background-color:#dcdcdc" %)AT+DR=5 (%%) Set Data Rate (Set AT+DR=3 for 915 band)
++(% style="background-color:#dcdcdc" %)AT+TDC=60000  (%%)Set transmit interval to 60 seconds
++(% style="background-color:#dcdcdc" %)AT+CHS=868400000 (%%)Set transmit frequency to 868.4Mhz
++(% style="background-color:#dcdcdc" %)AT+DADDR=26 01 1A F1(%%) Set Device Address to 26 01 1A F1
++(% style="background-color:#dcdcdc" %)ATZ                (%%)Reset MCU
++)))
--**Step2: **Run AT Command to make LT work in Single frequency & ABP mode. Below is the AT commands:
++(((
++As shown in below:
++)))
--123456   Enter Password to have AT access.
++[[image:1653360498588-932.png||height="485" width="726"]]
--AT+FDR   Reset Parameters to Factory Default, Keys Reserve
--123456   Enter Password to have AT access.
++== 5.4 Can I see counting event in Serial? ==
--AT+NJM=0 Set to ABP mode
++(((
++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.
--AT+ADR=0 Set the Adaptive Data Rate Off
--AT+DR=5  Set Data Rate (Set AT+DR=3 for 915 band)
++== 5.5 Can i use point to point communication for LT-22222-L? ==
--AT+TDC=60000  Set transmit interval to 60 seconds
++Yes, please refer [[Point to Point Communication>>doc:Main. Point to Point Communication of LT-22222-L.WebHome]]
--AT+CHS=868400000 Set transmit frequency to 868.4Mhz
++
++)))
--AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1
++(((
++= 6. Trouble Shooting =
++)))
--ATZ                Reset MCU
++(((
++(((
++== 6.1 Downlink doesn’t work, how to solve it? ==
++)))
++)))
--As shown in below:
++(((
++Please see this link for how to debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]]
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image040.png]]
++
++)))
++(((
++== 6.2 Have trouble to upload image. ==
++)))
++(((
++See this link for trouble shooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
++)))
--1.
--11. 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.
++(((
++== 6.3 Why I can’t join TTN in US915 /AU915 bands? ==
++)))
++(((
++It might be about the channels mapping. [[Please see this link for detail>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
++)))
++(((
++
++)))
++(((
++= 7. Order Info =
++)))
--1. Trouble Shooting
--11. Downlink doesn’t work, how to solve it?
++(((
++(((
++(% style="color:#4f81bd" %)**LT-22222-L-XXX:**
++)))
++)))
--Please see this link for how to debug:
++(((
++(((
++(% style="color:#4f81bd" %)**XXX:**
++)))
++)))
--[[http:~~/~~/wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#How_it_work>>url:http://wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#How_it_work]]
++(((
++* (((
++(% style="color:#4f81bd" %)**EU433**(%%): LT with frequency bands EU433
++)))
++)))
++(((
++* (((
++(% style="color:#4f81bd" %)**EU868**(%%): LT with frequency bands EU868
++)))
++)))
--1.
--11. Have trouble to upload image.
++(((
++* (((
++(% style="color:#4f81bd" %)**KR920**(%%): LT with frequency bands KR920
++)))
++)))
--See this link for trouble shooting:
++(((
++* (((
++(% style="color:#4f81bd" %)**CN470**(%%): LT with frequency bands CN470
++)))
++)))
--[[http:~~/~~/wiki.dragino.com/index.php?title=Firmware_Upgrade_Trouble_Shooting#UART_upgrade_trouble_shooting>>url:http://wiki.dragino.com/index.php?title=Firmware_Upgrade_Trouble_Shooting#UART_upgrade_trouble_shooting]]
++(((
++* (((
++(% style="color:#4f81bd" %)**AS923**(%%): LT with frequency bands AS923
++)))
++)))
++(((
++* (((
++(% style="color:#4f81bd" %)**AU915**(%%): LT with frequency bands AU915
++)))
++)))
--1.
--11. Why I can’t join TTN in US915 /AU915 bands?
++(((
++* (((
++(% style="color:#4f81bd" %)**US915**(%%): LT with frequency bands US915
++)))
++)))
--It might be about the channels mapping. Please see this link for detail:
++(((
++* (((
++(% style="color:#4f81bd" %)**IN865**(%%): LT with frequency bands IN865
++)))
++)))
--[[http:~~/~~/wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band>>url:http://wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band]]
++(((
++* (((
++(% style="color:#4f81bd" %)**CN779**(%%): LT with frequency bands CN779
++
++)))
++= 8. Packing Info =
++)))
--
--1. Order Info
--
--**For LT-33222-L-XXX or LT-22222-L-XXX:**
--
--**XXX:**
--
--* **EU433**: LT with frequency bands EU433
--* **EU868**: LT with frequency bands EU868
--* **KR920**: LT with frequency bands KR920
--* **CN470**: LT with frequency bands CN470
--* **AS923**: LT with frequency bands AS923
--* **AU915**: LT with frequency bands AU915
--* **US915**: LT with frequency bands US915
--* **IN865**: LT with frequency bands IN865
--* **CN779**: LT with frequency bands CN779
--
--1. Packing Info
--
++(((
++(((
  **Package Includes**:
++)))
++)))
--* LT I/O Controller x 1
++(((
++(((
++* LT-22222-L I/O Controller x 1
  * Stick Antenna for LoRa RF part x 1
  * Bracket for controller x1
  * Program cable x 1
++)))
++)))
++(((
++(((
  **Dimension and weight**:
++)))
++)))
++(((
++(((
  * Device Size: 13.5 x 7 x 3 cm
  * Device Weight: 105g
  * Package Size / pcs : 14.5 x 8 x 5 cm
  * Weight / pcs : 170g
--1. 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
++(((
++= 9. Support =
++)))
--[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
++* (((
++(((
++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 =
++
++* Product Page:
++
++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]]
++)))
++)))

1653356737703-362.png

Author

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

Size

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

Content

1653356838789-523.png

Author

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

Size

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

Content

1653356991268-289.png

Author

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

Size

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

Content

1653357170703-587.png

Author

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

Size

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

Content

1653357531600-905.png

Author

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

Size

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

Content

1653357592296-182.png

Author

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

Size

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

Content

1653357640609-758.png

Author

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

Size

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

Content

1653357648330-671.png

Author

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

Size

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

Content

1653358238933-385.png

Author

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

Size

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

Content

1653358355238-883.png

Author

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

Size

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

Content

1653359097980-169.png

Author

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

Size

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

Content

1653359603330-121.png

Author

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

Size

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

Content

1653360054704-518.png

Author

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

Size

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

Content

1653360231087-571.png

Author

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

Size

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

Content

1653360498588-932.png

Author

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

Size

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

Content

1653968155772-850.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+886 bytes

Content

1653968164738-884.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+886 bytes

Content

1653968172068-832.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+886 bytes

Content

image-20220524092754-5.png

Author

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

Size

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

Content

image-20220524093238-6.png

Author

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

Size

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

Content

image-20220524093328-7.png

Author

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

Size

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

Content

image-20220524093351-8.png

Author

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

Size

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

Content

image-20220524093724-9.png

Author

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

Size

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

Content

image-20220524093831-10.png

Author

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

Size

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

Content

image-20220524094641-11.png

Author

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

Size

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

Content

image-20220524094641-12.png

Author

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

Size

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

Content

image-20220524094909-1.png

Author

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

Size

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

Content

image-20220524094909-2.png

Author

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

Size

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

Content

image-20220524094909-3.png

Author

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

Size

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

Content

image-20220524094909-4.png

Author

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

Size

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

Content

image-20220524094909-5.png

Author

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

Size

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

Content

image-20220524095400-6.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+172 bytes

Content

image-20220524095438-7.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+158 bytes

Content

image-20220524095628-8.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+264 bytes

Content

image-20220524100215-10.png

Author

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

Size

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

Content

image-20220524100215-9.png

Author

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

Size

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

Content

image-20220524100748-11.png

Author

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

Size

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

Content

image-20220524103407-12.png

Author

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

Size

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

Content

image-20220524103429-13.png

Author

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

Size

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

Content

image-20220524103652-14.png

Author

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

Size

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

Content

image-20220524104033-15.png

Author

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

Size

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

Content

image-20220531113415-1.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+172 bytes

Content