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

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

From 99.1 to 100.1 From 167.1 to 168.1

From version 100.1

edited by Bei Jinggeng
on 2022/10/08 09:59

Change comment: Uploaded new attachment "image-20221008095908-1.png", version {1}

To version 167.1

edited by Dilisi S
on 2024/11/07 23:09

Change comment: Edits on Nov 7 - Part 1

Raw
Rendered

Summary

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

Details

Page properties

Title

@@ -1,1 +1,1 @@
--LT-22222-L LoRa IO Controller User Manual
++LT-22222-L -- LoRa IO Controller User Manual

Author

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

Content

@@ -3,6 +3,10 @@
++
++
++
++
  **Table of Contents:**
  {{toc/}}
@@ -13,37 +13,32 @@
--= 1.Introduction =
++= 1. Introduction =
++== 1.1 What is the LT-22222-L I/O Controller? ==
--== 1.1 What is LT Series I/O Controller ==
--
  (((
--
++(((
++The Dragino (% style="color:blue" %)**LT-22222-L I/O Controller**(%%) is an advanced LoRaWAN device designed to provide seamless wireless long-range connectivity with various I/O options, including analog current and voltage inputs, digital inputs and outputs, and relay outputs.
--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.
++The LT-22222-L I/O Controller simplifies and enhances I/O monitoring and controlling. It is ideal for professional applications in wireless sensor networks, including irrigation systems, smart metering, smart cities, building automation, and more. These controllers are designed for easy, cost-effective deployment using LoRa wireless technology.
  )))
--
--(((
--The LT I/O Controllers allows the user to send data and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, smartphone detection, building automation, and so on.
  )))
  (((
--The LT I/O Controllers is aiming to provide an (% style="color:blue" %)**easy and low cost installation** (%%)by using LoRa wireless technology.
++With the LT-22222-L I/O Controller, users can transmit data over ultra-long distances with low power consumption using LoRa, a spread-spectrum modulation technique derived from chirp spread spectrum (CSS) technology that operates on license-free ISM bands.
  )))
--(((
--The use environment includes:
--)))
++> The LT Series I/O Controllers are designed for easy, low-cost installation on LoRaWAN networks.
  (((
--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.
--)))
++You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways:
--(((
--2) User can set up a LoRaWAN gateway locally and configure the controller to connect to the gateway via wireless.
++* If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Network), you can select a network and register the LT-22222-L I/O controller with it.
++* If there is no public LoRaWAN coverage in your area, you can set up a LoRaWAN gateway, or multiple gateways, and connect them to a LoRaWAN network server to create adequate coverage. Then, register the LT-22222-L I/O controller with this network.
++* Setup your own private LoRaWAN network.
--
++> You can use a LoRaWAN gateway, such as the Dragino LG308, to expand or create LoRaWAN coverage in your area.
  )))
  (((
@@ -52,143 +52,59 @@
  )))
++== 1.2 Specifications ==
--== 1.2  Specifications ==
--
--(((
--
--
  (% style="color:#037691" %)**Hardware System:**
--)))
--* (((
--STM32L072CZT6 MCU
--)))
--* (((
--SX1276/78 Wireless Chip
--)))
--* (((
--(((
--Power Consumption:
--)))
++* STM32L072xxxx MCU
++* SX1276/78 Wireless Chip
++* Power Consumption:
++** Idle: 4mA@12v
++** 20dB Transmit: 34mA@12v
++* Operating Temperature: -40 ~~ 85 Degrees, No Dew
--* (((
--Idle: 4mA@12v
--)))
--* (((
--20dB Transmit: 34mA@12v
--)))
--)))
--
--(((
--
--
  (% style="color:#037691" %)**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.
--(((
--
--
  (% style="color:#037691" %)**LoRa Spec:**
--)))
--* (((
--(((
--Frequency Range:
--)))
++* 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.
--* (((
--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
  * Optional Customized LoRa Protocol
  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
  * AT Commands to change parameters
--* Remote configure parameters via LoRa Downlink
++* Remotely configure parameters via LoRaWAN Downlink
  * Firmware upgradable via program port
  * Counting
++== 1.4 Applications ==
--
--== 1.4  Applications ==
--
--
  * Smart Buildings & Home Automation
  * Logistics and Supply Chain Management
  * Smart Metering
@@ -196,14 +196,15 @@
  * Smart Cities
  * Smart Factory
--
--
  == 1.5 Hardware Variants ==
--(% border="1" style="background-color:#f7faff; width:500px" %)
--|(% style="width:103px" %)**Model**|(% style="width:131px" %)**Photo**|(% style="width:334px" %)**Description**
--|(% style="width:103px" %)**LT22222-L**|(% style="width:131px" %)[[image:1653296302983-697.png]]|(% style="width:334px" %)(((
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %)
++|(% style="background-color:#4f81bd; color:white; width:103px" %)**Model**|(% style="background-color:#4f81bd; color:white; width:131px" %)**Photo**|(% style="background-color:#4f81bd; color:white; width:266px" %)**Description**
++|(% style="width:103px" %)**LT22222-L**|(% style="width:131px" %)(((
++(% style="text-align:center" %)
++[[image:image-20230424115112-1.png||height="106" width="58"]]
++)))|(% style="width:334px" %)(((
  * 2 x Digital Input (Bi-direction)
  * 2 x Digital Output
  * 2 x Relay Output (5A@250VAC / 30VDC)
@@ -212,132 +212,192 @@
  * 1 x Counting Port
  )))
++= 2. Assembling the Device =
++== 2.1 What is included in the package? ==
--= 2. Power ON Device =
++The package includes the following items:
++* 1 x LT-22222-L I/O Controller
++* 1 x LoRaWAN antenna matched to the frequency of the LT-22222-L
++* 1 x bracket for wall mounting
++* 1 x programming cable
--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.
++Attach the LoRaWAN antenna to the antenna connector, ANT,** **located on the top right side of the device, next to the upper terminal block. Secure the antenna by tightening it clockwise.
--(((
--PWR will on when device is properly powered.
++== 2.2 Terminals ==
--
--)))
++Upper screw terminal block (from left to right):
--[[image:1653297104069-180.png]]
++(% style="width:634px" %)
++|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function
++|(% style="width:295px" %)GND|(% style="width:338px" %)Ground
++|(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage
++|(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2
++|(% style="width:295px" %)AVI1|(% style="width:338px" %)Analog Voltage Input Terminal 1
++|(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2
++|(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1
++Lower screw terminal block (from left to right):
++(% style="width:633px" %)
++|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function
++|(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1
++|(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1
++|(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2
++|(% style="width:296px" %)RO2-1|(% style="width:334px" %)Relay Output 2
++|(% style="width:296px" %)DI2+|(% style="width:334px" %)Digital Input 2
++|(% style="width:296px" %)DI2-|(% style="width:334px" %)Digital Input 2
++|(% style="width:296px" %)DI1+|(% style="width:334px" %)Digital Input 1
++|(% style="width:296px" %)DI1-|(% style="width:334px" %)Digital Input 1
++|(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
++|(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
--= 3. Operation Mode =
++== 2.3 Powering the LT-22222-L ==
++The LT-22222-L I/O Controller can be powered by a 7–24V DC power source. Connect the power supply’s positive wire to the VIN and the negative wire to the GND screw terminals. The power indicator (PWR) LED will turn on when the device is properly powered.
--== 3.1 How it works? ==
++[[image:1653297104069-180.png]]
--(((
--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.
--)))
++= 3. Operation Mode =
++== 3.1 How does it work? ==
++By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode. It supports OTAA (Over-the-Air Activation), the most secure method for activating a device with a LoRaWAN network server. The LT-22222-L comes with device registration information that allows you to register it with a LoRaWAN network, enabling the device to perform OTAA activation with the network server upon initial power-up and after any subsequent reboots.
--== 3.2 Example to join LoRaWAN network ==
++For LT-22222-L, the LED will show the Join status: After powering on, the TX LED will fast-blink 5 times which means the LT-22222-L will enter the working mode and start to JOIN the LoRaWAN network. The TX LED will be on for 5 seconds after joining the network. When there is a message from the server, the RX LED will be on for 1 second.
++In case you can't set the root key and other identifiers in the network server and must use them from the server, you can use [[AT Commands>>||anchor="H4.UseATCommand"]] to configure them on the device.
--(((
--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.
++== 3.2 Registering with a LoRaWAN network server ==
--
--)))
++The diagram below shows how the LT-22222-L connects to a typical LoRaWAN network.
  [[image:image-20220523172350-1.png||height="266" width="864"]]
++=== 3.2.1 Prerequisites ===
--(((
--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:
++Make sure you have the device registration information such as DevEUI, AppEUI, and AppKey with you. The registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference.
--
--)))
++[[image:image-20230425173427-2.png||height="246" width="530"]]
--(((
--(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LT IO controller.
--)))
++The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
--(((
--Each LT is shipped with a sticker with the default device EUI as below:
--)))
++=== 3.2.2 The Things Stack Sandbox (TTSS) ===
--[[image:1653297924498-393.png]]
++* Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account.
++* Create an application if you do not have one yet.
++* Register LT-22222-L with that application. Two registration options are available:
++==== Using the LoRaWAN Device Repository: ====
--Input these keys in the LoRaWAN Server portal. Below is TTN screen shot:
++* Go to your application and click on the **Register end device** button.
++* On the **Register end device** page:
++** Select the option **Select the end device in the LoRaWAN Device Repository**.
++** Choose the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)**.
++** Select the **Frequency plan** that matches your device.
--Add APP EUI in the application.
++[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
--[[image:1653297955910-247.png||height="321" width="716"]]
++*
++** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
++** Enter the **DevEUI** in the **DevEUI** field.
++** Enter the **AppKey** in the **AppKey** field.
++** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
++** Under **After registration**, select the **View registered end device** option.
++[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
--Add APP KEY and DEV EUI
++==== Entering device information manually: ====
--[[image:1653298023685-319.png]]
++* On the **Register end device** page:
++** Select the **Enter end device specifies manually** option as the input method.
++** Select the **Frequency plan** that matches your device.
++** Select the **LoRaWAN version**.
++** Select the **Regional Parameters version**.
++** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the section.
++** Select **Over the air activation (OTAA)** option under the **Activation mode**
++** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities**.
++[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
--(((
--(% 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.
--)))
++* Enter **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
++* Enter **DevEUI** in the **DevEUI** field.
++* Enter **AppKey** in the **AppKey** field.
++* In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
++* Under **After registration**, select the **View registered end device** option.
++[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
++
++
++==== Joining ====
++
++Click on **Live Data** in the left navigation. Then, power on the device, and it will join The Things Stack Sandbox. You can see the join request, join accept, followed by uplink messages form the device showing in the Live Data panel.
++
  [[image:1653298044601-602.png||height="405" width="709"]]
++== 3.3 Work Modes and their Uplink Payload formats ==
--== 3.3 Uplink Payload ==
++The LT-22222-L has 5 **work modes**. It also has an interrupt/trigger mode for different types of applications that can be used together with any working mode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands.
--There are five working modes + one interrupt mode on LT for different type application:
++* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO
--* (% 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 is 11 bytes long. Uplink messages are sent over LoRaWAN FPort 2. By default, one uplink is sent every 10 minutes. (% style="display:none" wfd-invisible="true" %)
--The uplink payload includes totally 9 bytes. Uplink packets use FPORT=2 and every 10 minutes send one uplink by default.
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
++|(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**
++|Value|(((
++AVI1 voltage
++)))|(((
++AVI2 voltage
++)))|(((
++ACI1 Current
++)))|(((
++ACI2 Current
++)))|**DIDORO***|(((
++Reserve
++)))|MOD
++)))
--[[image:image-20220523174024-3.png]]
--
  (((
--
++(% style="color:#4f81bd" %)*** DIDORO**(%%) is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, and its size is1 byte long as shown below.
--(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
++|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
++|RO1|RO2|--DI3--|DI2|DI1|--DO3--|DO2|DO1
  )))
--[[image:image-20220523174254-4.png]]
++* RO is for the relay. ROx=1: CLOSED, ROx=0 always OPEN.
++* DI is for digital input. DIx=1: HIGH or FLOATING, DIx=0: LOW.
++* DO is for reverse digital output. DOx=1: LOW, DOx=0: HIGH or FLOATING.
--* RO is for relay. ROx=1 : close，ROx=0 always open.
--* 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 bits are not valid for LT-22222-L**
++For example, if the payload is: [[image:image-20220523175847-2.png]]
--(% 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]]
++**The interface values can be calculated as follows:  **
++AVI1 channel voltage is 0x04AB/1000=1195(DEC)/1000=1.195V
--**The value for the interface is:  **
--
--AVI1 channel voltage is 0x04AB/1000=1195（DEC）/1000=1.195V
--
  AVI2 channel voltage is 0x04AC/1000=1.196V
  ACI1 channel current is 0x1310/1000=4.880mA
@@ -344,65 +344,66 @@
  ACI2 channel current is 0x1300/1000=4.864mA
--The last byte 0xAA= 10101010(B) means
++The last byte 0xAA= **10101010**(b) means,
--* [1] RO1 relay channel is close and the RO1 LED is ON.
--* [0] RO2 relay channel is open and RO2 LED is OFF;
++* [1] The RO1 relay channel is CLOSED, and the RO1 LED is ON.
++* [0] The RO2 relay channel is OPEN, and the RO2 LED is OFF.
++* [1] DI3 - not used for LT-22222-L.
++* [0] DI2 channel input is LOW, and the DI2 LED is OFF.
++* [1] DI1 channel input state:
++** DI1 is FLOATING when no sensor is connected between DI1+ and DI1-.
++** DI1 is HIGH when a sensor is connected between DI1- and DI1+ and the sensor is ACTIVE.
++** DI1 LED is ON in both cases.
++* [0] DO3 - not used for LT-22222-L.
++* [1] DO2 channel output is LOW, and the DO2 LED is ON.
++* [0] DO1 channel output state:
++** DO1 is FLOATING when there is no load between DO1 and V+.
++** DO1 is HIGH when there is a load between DO1 and V+.
++** DO1 LED is OFF in both cases.
--
--**LT22222-L:**
--
--* [1] DI2 channel is high input and DI2 LED is ON;
--* [0] DI1 channel is low input;
--
--* [0] DO3 channel output state
--** DO3 is float in case no load between DO3 and V+.;
--** DO3 is high in case there is load between DO3 and V+.
--** DO3 LED is off in both case
--* [1] DO2 channel output is low and DO2 LED is ON.
--* [0] DO1 channel output state
--** DO1 is float in case no load between DO1 and V+.;
--** DO1 is high in case there is load between DO1 and V+.
--** DO1 LED is off in both case
--
--
--
--
  === 3.3.2 AT+MOD~=2, (Double DI Counting) ===
--**For LT-22222-L**: this mode the **DI1 and DI2** are used as counting pins.
--
  (((
--Total : 11 bytes payload
++**For LT-22222-L**: In this mode, **DI1 and DI2** are used as counting pins.
  )))
--[[image:image-20220523180452-3.png]]
++(((
++The uplink payload is 11 bytes long.
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
++|(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**4**|(% style="background-color:#4f81bd; color:white" %)**4**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**
++|Value|COUNT1|COUNT2 |DIDORO*|(((
++Reserve
++)))|MOD
++)))
  (((
--(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DO3, DO2 and DO1. Totally 1bytes as below
--)))
++(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, DO3, DO2 and DO1, and its size is 1 byte long as shown below.
--[[image:image-20220523180506-4.png]]
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
++|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
++|RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1
--* 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.
--
--(((
--(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L.**
++* RO is for the relay. ROx=1: CLOSED,  ROx=0 always OPEN.
  )))
++* FIRST: Indicates that this is the first packet after joining the network.
++* DO is for reverse digital output. DOx=1: LOW, DOx=0: HIGH or FLOATING.
++
  (((
++(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L**
++
++)))
--**To use counting mode, please run:**
++(((
++**To activate this mode, run the following AT commands:**
  )))
++(((
  (% class="box infomessage" %)
  (((
--(((
  **AT+MOD=2**
  **ATZ**
@@ -413,60 +413,62 @@
  (% style="color:#4f81bd" %)**AT Commands for counting:**
--
--
  )))
  (((
  **For LT22222-L:**
++(% style="color:blue" %)**AT+TRIG1=0,100**(%%)** (sets the DI1 port to trigger on a LOW level. The valid signal duration is 100ms) **
--(% style="color:blue" %)**AT+TRIG1=0,100**(%%)**    (set DI1 port to trigger on low level, valid signal is 100ms) **
++(% style="color:blue" %)**AT+TRIG1=1,100**(%%)** (sets the DI1 port to trigger on a HIGH level. The valid signal duration is 100ms) **
--(% style="color:blue" %)**AT+TRIG1=1,100**(%%)**    (set DI1 port to trigger on high level, valid signal is 100ms ) **
++(% style="color:blue" %)**AT+TRIG2=0,100**(%%)** (sets the DI2 port to trigger on a LOW level. The valid signal duration is 100ms) **
--(% style="color:blue" %)**AT+TRIG2=0,100**(%%)**    (set DI2 port to trigger on low level, valid signal is 100ms) **
++(% style="color:blue" %)**AT+TRIG2=1,100**(%%)** (sets the DI2 port to trigger on a HIGH level. The valid signal duration is 100ms) **
--(% style="color:blue" %)**AT+TRIG2=1,100**(%%)**    (set DI2 port to trigger on high level, valid signal is 100ms ) **
++(% style="color:blue" %)**AT+SETCNT=1,60**(%%)** (sets the COUNT1 value to 60)**
--(% style="color:blue" %)**AT+SETCNT=1,60**(%%)**   (Set COUNT1 value to 60)**
--
--(% style="color:blue" %)**AT+SETCNT=2,60**(%%)**   (Set COUNT2 value to 60)**
++(% style="color:blue" %)**AT+SETCNT=2,60 **(%%)**(sets the 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.
++**LT22222-L**: In this mode, the DI1 is used as a counting pin.
--[[image:image-20220523181246-5.png]]
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
++|(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**4**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**
++|Value|COUNT1|(((
++ACI1 Current
++)))|(((
++ACI2 Current
++)))|DIDORO*|Reserve|MOD
  (((
--
++(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below.
--(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
++|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
++|RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1
  )))
--[[image:image-20220523181301-6.png]]
++* RO is for the relay. ROx=1: closed, ROx=0 always open.
++* FIRST: Indicates that this is the first packet after joining the network.
++* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.
--* 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.
--
  (((
--(% style="color:red" %)**Note: DO3 is not valid for LT-22222-L.**
++(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L.**
  )))
  (((
--**To use counting mode, please run:**
++**To activate this mode, run the following AT commands:**
  )))
++(((
  (% class="box infomessage" %)
  (((
--(((
  **AT+MOD=3**
  **ATZ**
@@ -474,44 +474,54 @@
  )))
  (((
--Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]].
++AT Commands for counting:
++
++The AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
  )))
--
  === 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.
--
--The AVI1 is also used for counting. AVI1 is used to monitor the voltage. It will check the voltage **every 60s**, if voltage is higher or lower than VOLMAX mV, the AVI1 Counting increase 1, so AVI1 counting can be used to measure a machine working hour.
--
--[[image:image-20220523181903-8.png]]
--
--
  (((
--(% style="color:#4f81bd" %)**DIDORO **(%%)is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below
++**LT22222-L**: In this mode, the DI1 is used as a counting pin.
  )))
--[[image:image-20220523181727-7.png]]
++(((
++The AVI1 is also used for counting. It monitors the voltage and checks it every **60 seconds**. If the voltage is higher or lower than VOLMAX mV, the AVI1 count increases by 1, allowing AVI1 counting to be used to measure a machine's working hours.
--* 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.
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
++|(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**4**|(% style="background-color:#4f81bd; color:white" %)**4**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**
++|Value|COUNT1|AVI1 Counting|DIDORO*|(((
++Reserve
++)))|MOD
++)))
  (((
--(% style="color:red" %)**Note: DO3 is not valid for LT-22222-L.**
++(% style="color:#4f81bd" %)**DIDORO **(%%)is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below.
++
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
++|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
++|RO1|RO2|FIRST|Reserve|Reserve|--DO3--|DO2|DO1
  )))
++* RO is for the relay. ROx=1: closed, ROx=0 always open.
++* FIRST: Indicates that this is the first packet after joining the network.
++* DO is for reverse digital output. DOx=1: output low, DOx=0: high or floating.
++
  (((
++(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L.**
++
++)))
--**To use this mode, please run:**
++(((
++**To activate this mode, run the following AT commands:**
  )))
++(((
  (% class="box infomessage" %)
  (((
--(((
  **AT+MOD=4**
  **ATZ**
@@ -518,61 +518,65 @@
  )))
  )))
--
--
  (((
--Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]].
++Other AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
  )))
  (((
--
++**In addition to that,  below are the commands for AVI1 Counting:**
--**Plus below command for AVI1 Counting:**
++(% style="color:blue" %)**AT+SETCNT=3,60**(%%)**           (Sets AVI Count to 60)**
--
--(% style="color:blue" %)**AT+SETCNT=3,60**(%%)**            (set AVI Count to 60)**
--
  (% style="color:blue" %)**AT+VOLMAX=20000**(%%)**       (If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
  (% style="color:blue" %)**AT+VOLMAX=20000,0**(%%)**    (If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
--(% style="color:blue" %)**AT+VOLMAX=20000,1**(%%)**    (If AVI1 voltage higer than VOLMAX (20000mV =20v), counter increase 1)**
++(% style="color:blue" %)**AT+VOLMAX=20000,1**(%%)**    (If AVI1 voltage higher 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.
++**LT22222-L**: In this mode, the DI1 is used as a counting pin.
--[[image:image-20220523182334-9.png]]
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
++|(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**
++|Value|(((
++AVI1 voltage
++)))|(((
++AVI2 voltage
++)))|(((
++ACI1 Current
++)))|COUNT1|DIDORO*|(((
++Reserve
++)))|MOD
  (((
--
++(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination of RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1, for a total of 1 byte, as shown below.
--(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
++|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
++|RO1|RO2|FIRST|Reserve|Reserve|DO3|DO2|DO1
  )))
--* RO is for relay. ROx=1 : close，ROx=0 always open.
--* FIRST: Indicate this is the first packet after join network.
++* RO is for the relay. ROx=1: closed, ROx=0 always open.
++* FIRST: Indicates that this is the first packet after joining the 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 floating.
  )))
  (((
--(% style="color:red" %)**Note: DO3 is not valid for LT-22222-L.**
++(% style="color:red" %)**Note: DO3 bit is not valid for LT-22222-L.**
  )))
  (((
--
--
--**To use this mode, please run:**
++**To activate this mode, run the following AT commands:**
  )))
++(((
  (% class="box infomessage" %)
  (((
--(((
  **AT+MOD=5**
  **ATZ**
@@ -580,60 +580,53 @@
  )))
  (((
--Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]].
++Other AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
  )))
--
  === 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.**
++(% style="color:#4f81bd" %)**This mode is optional and intended for trigger purposes. It can operate together with other modes.**
--For example, if user has configured below commands:
++For example, if you configured the following commands:
  * **AT+MOD=1 **            **~-~->**   The normal working mode
--* **AT+ADDMOD6=1**   **~-~->**   Enable trigger
++* **AT+ADDMOD6=1**   **~-~->**   Enable trigger mode
++The LT-22222-L will continuously monitor AV1, AV2, AC1, and AC2 every 5 seconds. LT will send uplink packets in two cases:
--LT will keep monitoring AV1/AV2/AC1/AC2 every 5 seconds; LT will send uplink packets in two cases:
++1. Periodically uplink (Based on TDC time). The payload is the same as in normal mode (MOD=1 for the commands above). These are (% style="color:#4f81bd" %)**unconfirmed**(%%) uplinks.
++1. Trigger uplink when the trigger condition is met. LT will send two packets in this case. The first uplink uses the payload specified in trigger mode (MOD=6). The second packet uses the normal mode payload (MOD=1 as set above). Both are (% style="color:#4f81bd" %)**CONFIRMED uplinks.**
--1. Periodically uplink (Base on TDC time). Payload is same as the normal MOD (MOD 1 for above command). This uplink uses LoRaWAN (% style="color:#4f81bd" %)**unconfirmed**(%%) data type
--1. Trigger uplink when meet the trigger condition. LT will sent two packets in this case, the first uplink use payload specify in this mod (mod=6), the second packets use the normal mod payload(MOD=1 for above settings). Both Uplinks use LoRaWAN (% style="color:#4f81bd" %)**CONFIRMED data type.**
--
--
--
  (% style="color:#037691" %)**AT Command to set Trigger Condition**:
++(% style="color:#4f81bd" %)**Trigger based on voltage**:
--(% 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)
++AT+AVLIM=3000,6000,0,2000   (triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V)
--AT+AVLIM=5000,0,0,0   (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore)
++AT+AVLIM=5000,0,0,0   (triggers an uplink if AVI1 voltage lower than 5V. Use 0 for parameters that are not in use)
++(% style="color:#4f81bd" %)**Trigger based on current**:
--(% style="color:#4f81bd" %)**Trigger base on current**:
--
  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)
++AT+ACLIM=10000,15000,0,0   (triggers an uplink if ACI1 voltage is lower than 10mA or higher than 15mA)
++(% style="color:#4f81bd" %)**Trigger based on DI status**:
--(% style="color:#4f81bd" %)**Trigger base on DI status**:
++DI status triggers Flag.
--DI status trigger Flag.
--
  Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >
@@ -642,77 +642,117 @@
  AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
++(% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
--(% style="color:#037691" %)**Downlink Command to set Trigger Condition:**
--
  Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
  Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
--  AA: Code for this downlink Command:
++  AA: Type Code for this downlink Command:
--  xx: 0: Limit for AV1 and AV2;  1: limit for AC1 and AC2 ; 2 DI1, DI2 trigger enable/disable
++  xx: **0**: Limit for AV1 and AV2; **1**: limit for AC1 and AC2; **2**: DI1and DI2 trigger enable/disable.
--  yy1 yy1: AC1 or AV1 low limit or DI1/DI2 trigger status.
++  yy1 yy1: AC1 or AV1 LOW limit or DI1/DI2 trigger status.
--  yy2 yy2: AC1 or AV1 high limit.
++  yy2 yy2: AC1 or AV1 HIGH limit.
--  yy3 yy3: AC2 or AV2 low limit.
++  yy3 yy3: AC2 or AV2 LOW limit.
--  Yy4 yy4: AC2 or AV2 high limit.
++  Yy4 yy4: AC2 or AV2 HIGH limit.
--**Example1**: AA 00 13 88 00 00 00 00 00 00
++**Example 1**: AA 00 13 88 00 00 00 00 00 00
--Same as AT+AVLIM=5000,0,0,0   (If AVI1 voltage lower than 5V , trigger uplink, 0 means ignore)
++Same as AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage is lower than 5V. Use 0s for parameters that are not in use)
--**Example2**: AA 02 01 00
++**Example 2**: AA 02 01 00
--Same as AT+ DTRI =1,0  (Enable DI1 trigger / disable DI2 trigger)
++Same as AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
--
  (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:**
--MOD6 Payload : total 11 bytes payload
++MOD6 Payload: total of 11 bytes
--[[image:image-20220524085923-1.png]]
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
++|(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:69px" %)**1**|(% style="background-color:#4f81bd; color:white; width:69px" %)**1**|(% style="background-color:#4f81bd; color:white; width:109px" %)**1**|(% style="background-color:#4f81bd; color:white; width:49px" %)**6**|(% style="background-color:#4f81bd; color:white; width:109px" %)**1**|(% style="background-color:#4f81bd; color:white; width:50px" %)**1**
++|Value|(((
++TRI_A FLAG
++)))|(((
++TRI_A Status
++)))|(((
++TRI_DI FLAG+STA
++)))|Reserve|Enable/Disable MOD6|(((
++MOD(6)
++)))
++(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
--(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if trigger is set for this part. Totally 1byte as below
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
++|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
++|(((
++AV1_LOW
++)))|(((
++AV1_HIGH
++)))|(((
++AV2_LOW
++)))|(((
++AV2_HIGH
++)))|(((
++AC1_LOW
++)))|(((
++AC1_HIGH
++)))|(((
++AC2_LOW
++)))|(((
++AC2_HIGH
++)))
--[[image:image-20220524090106-2.png]]
++* Each bit shows if the corresponding trigger has been configured.
--* 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
++10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW
++(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
--(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1byte as below
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
++|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
++|(((
++AV1_LOW
++)))|(((
++AV1_HIGH
++)))|(((
++AV2_LOW
++)))|(((
++AV2_HIGH
++)))|(((
++AC1_LOW
++)))|(((
++AC1_HIGH
++)))|(((
++AC2_LOW
++)))|(((
++AC2_HIGH
++)))
--[[image:image-20220524090249-3.png]]
++* Each bit shows which status has been triggered on this uplink.
--* 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.
++10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is 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]]
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
++|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
++|N/A|N/A|N/A|N/A|DI2_STATUS|DI2_FLAG|DI1_STATUS|DI1_FLAG
--* Each bits shows which status has been trigger on this uplink.
++* Each bits shows which status has been triggered on this uplink.
--
  **Example:**
  00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
@@ -720,7 +720,6 @@
  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:
@@ -730,268 +730,225 @@
  When device got this command, it will send the MOD6 payload.
--
--
  === 3.3.7 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]]
++**Decoder for TTN/loraserver/ChirpStack**:  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]
  )))
++== 3.4 Configure LT via AT Commands or Downlinks ==
--== 3.4 Configure LT via AT or Downlink ==
++(((
++User can configure LT I/O Controller via AT Commands or LoRaWAN Downlinks.
++)))
--User can configure LT I/O Controller via AT Commands or LoRaWAN Downlink Commands
--
  (((
++(((
  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: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
++* (% style="color:blue" %)**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:
++* (% style="color:blue" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L.  User can see these commands below:
--
--
  === 3.4.1 Common Commands ===
++(((
++These commands should be available for all Dragino sensors, such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]].
++)))
--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 ====
++Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
--Set device uplink interval.
++* (% style="color:#037691" %)**AT command:**
--* (% style="color:#037691" %)**AT Command:**
++(% style="color:blue" %)**AT+TDC=N**
--**AT+TDC=N **
++where N is the time in milliseconds.
++**Example: **AT+TDC=30000. This will set the uplink interval to 30 seconds
--**Example: **AT+TDC=30000. Means set interval to 30 seconds
++* (% style="color:#037691" %)**Downlink payload (prefix 0x01):**
--* (% style="color:#037691" %)**Downlink Payload (prefix 0x01):**
++(% style="color:blue" %)**0x01 aa bb cc  **(%%)**   ~/~/ Same as AT+TDC=0x(aa bb cc)**
--**0x01 aa bb cc     ~/~/ Same as AT+TDC=0x(aa bb cc)**
++==== 3.4.2.2 Set the Work Mode (AT+MOD) ====
--==== 3.4.2.2 Set Work Mode (AT+MOD) ====
++Sets the work mode.
++* (% style="color:#037691" %)**AT command:**(%%) (% style="color:blue" %)**AT+MOD=N  **
--Set work mode.
++Where N is the work mode.
--* (% style="color:#037691" %)**AT Command:**
++**Example**: AT+MOD=2. This will set the work mode to Double DI counting mode.
--**AT+MOD=N  **
++* (% style="color:#037691" %)**Downlink payload (prefix 0x0A):**
--**Example**: AT+MOD=2. Set work mode to Double DI counting mode
++(% style="color:blue" %)**0x0A aa  **(%%)**  ** ~/~/ Same as AT+MOD=aa
--* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A):**
--**0x0A aa    ** ~/~/ Same as AT+MOD=aa
--
--
--
--
  ==== 3.4.2.3 Poll an uplink ====
--* (% style="color:#037691" %)**AT Command:**
++Asks the device to send an uplink.
--There is no AT Command to poll uplink
++* (% 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):**
++(% style="color:blue" %)**0x08 FF  **(%%)**   **~/~/ Poll an uplink
--**0x08 FF     **~/~/ Poll an uplink
--
--
  **Example**: 0x08FF, ask device to send an Uplink
++==== 3.4.2.4 Enable/Disable Trigger Mode ====
--==== 3.4.2.4 Enable Trigger Mode ====
++Enable or disable the trigger mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
--Use of trigger mode, please check [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0**
--* (% style="color:#037691" %)**AT Command:**
++(% style="color:red" %)**1:** (%%)Enable the trigger mode
--**AT+ADDMOD6=1 or 0**
++(% style="color:red" %)**0: **(%%)Disable the trigger mode
--1: Enable Trigger Mode
--0: Disable Trigger Mode
--
--
  * (% style="color:#037691" %)**Downlink Payload (prefix 0x0A 06):**
--**0x0A 06 aa    ** ~/~/ Same as AT+ADDMOD6=aa
++(% style="color:blue" %)**0x0A 06 aa    **(%%)    ~/~/ Same as AT+ADDMOD6=aa
--
  ==== 3.4.2.5 Poll trigger settings ====
--Poll trigger settings,
++Polls the trigger settings
  * (% style="color:#037691" %)**AT Command:**
  There is no AT Command for this feature.
--
  * (% style="color:#037691" %)**Downlink Payload (prefix 0x AB 06):**
--**0xAB 06         **~/~/ Poll trigger settings, device will uplink trigger settings once receive this command
++(% style="color:blue" %)**0xAB 06  **  (%%)   ~/~/ Poll the 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,
++Enable or Disable DI1/DI2/DI2 as trigger,
--* (% style="color:#037691" %)**AT Command:**
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
--**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
++**Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
--**Example:**
--
--AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
--
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 02):**
--**0xAA 02 aa bb        **~/~/ Same as AT+DTRI=aa,bb
++(% style="color:blue" %)**0xAA 02 aa bb   **  (%%) ~/~/ Same as AT+DTRI=aa,bb
--
  ==== 3.4.2.7 Trigger1 – Set DI1 or DI3 as trigger ====
  Set DI1 or DI3(for LT-33222-L) trigger.
--* (% style="color:#037691" %)**AT Command:**
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG1=a,b**
--**AT+TRIG1=a,b**
++(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
--a : Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
++(% style="color:red" %)**b :** (%%)delay timing.
--b : delay timing.
++**Example:** AT+TRIG1=1,100(set DI1 port to trigger on high level, valid signal is 100ms )
--**Example:**
--
--AT+TRIG1=1,100(set DI1 port to trigger on high level, valid signal is 100ms )
--
--
  * (% style="color:#037691" %)**Downlink Payload (prefix 0x09 01 ):**
--* **0x09 01 aa bb cc    **     ~/~/ same as AT+TRIG1=aa,0x(bb cc)
++(% style="color:blue" %)**0x09 01 aa bb cc    ** (%%)    ~/~/ same as AT+TRIG1=aa,0x(bb cc)
++
  ==== 3.4.2.8 Trigger2 – Set DI2 as trigger ====
--Set DI2 trigger.
++Sets DI2 trigger.
--* (% style="color:#037691" %)**AT Command:**
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b**
--**AT+TRIG2=a,b**
++(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
++(% style="color:red" %)**b :** (%%)delay timing.
--a : Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
++**Example:** AT+TRIG2=0,100 (set DI1 port to trigger on low level, valid signal is 100ms )
--b : delay timing.
--
--**Example:**
--
--AT+TRIG2=0,100(set DI1 port to trigger on low level, valid signal is 100ms )
--
--
  * (% style="color:#037691" %)**Downlink Payload (prefix 0x09 02 ):**
--**0x09 02 aa bb cc           **~/~/ same as AT+TRIG1=aa,0x(bb cc)
++(% style="color:blue" %)**0x09 02 aa bb cc   **  (%%)~/~/ same as AT+TRIG2=aa,0x(bb cc)
--
  ==== 3.4.2.9 Trigger – Set AC (current) as trigger ====
  Set current trigger , base on AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--* (% style="color:#037691" %)**AT Command**
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ACLIM**
--**AT+ACLIM**
--
--
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 01 )**
--**0x AA 01 aa bb cc dd ee ff gg hh        **   ~/~/ same as AT+ACLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
++(% style="color:blue" %)**0x AA 01 aa bb cc dd ee ff gg hh        ** (%%)  ~/~/ same as AT+ACLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--
  ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
  Set current trigger , base on AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--* (% style="color:#037691" %)**AT Command**
++* (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+AVLIM    **(%%)**        See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]**
--**AT+AVLIM            See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]**
--
--
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 00 )**
--**0x AA 00 aa bb cc dd ee ff gg hh    ** ~/~/ same as AT+AVLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
++(% style="color:blue" %)**0x AA 00 aa bb cc dd ee ff gg hh    ** (%%) ~/~/ same as AT+AVLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--
  ==== 3.4.2.11 Trigger – Set minimum interval ====
--Set AV and AC trigger minimum interval, system won't response to the second trigger within this set time after the first trigger.
++Sets AV and AC trigger minimum interval.  Device won't response to the second trigger within this set time after the first trigger.
--* (% style="color:#037691" %)**AT Command**
++* (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**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 )**
--**0x AC aa bb   ** ~/~/ same as AT+ATDC=0x(aa bb)   . Unit (min)
++(% style="color:blue" %)**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 ====
@@ -1001,8 +1001,9 @@
  * (% style="color:#037691" %)**Downlink Payload (prefix 0x02)**
--* **0x02 aa bb cc     **~/~/ Set DO1/DO2/DO3 output
++(% style="color:blue" %)**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.
  )))
@@ -1009,10 +1009,14 @@
  (((
 : Low,  00: High ,  11: No action
++
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
++|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**DO1**|(% style="background-color:#4f81bd; color:white" %)**DO2**|(% style="background-color:#4f81bd; color:white" %)**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]]
--
  (((
  (% style="color:red" %)**Note: For LT-22222-L, there is no DO3, the last byte can use any value.**
  )))
@@ -1023,7 +1023,6 @@
--
  ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
@@ -1034,7 +1034,7 @@
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
--**0xA9 aa bb cc     **~/~/ Set DO1/DO2/DO3 output with time control
++(% style="color:blue" %)**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:
@@ -1050,23 +1050,37 @@
  (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Ports status:
--[[image:image-20220524093238-6.png]]
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
++|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**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:
--[[image:image-20220524093328-7.png]]
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
++|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**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:
--[[image:image-20220524093351-8.png]]
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
++|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
++|0x01|DO3 set to low
++|0x00|DO3 set to high
++|0x11|DO3 NO Action
++(% style="color:#4f81bd" %)**Sixth and Seventh and Eighth and Ninth Byte**:(%%) Latching time. Unit: ms
--(% style="color:#4f81bd" %)**Sixth and Seventh and Eighth and Ninth Byte**:
--         Latching time. Unit: ms
++(% style="color:red" %)**Note: **
++   Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes
++
++   Before Firmwre v1.6.0 the latch time only suport 2 bytes.
++
  (% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
@@ -1090,7 +1090,6 @@
--
  ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
@@ -1101,7 +1101,7 @@
  * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
--**0x03 aa bb     **~/~/ Set RO1/RO2 output
++(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Set RO1/RO2 output
  (((
@@ -1109,11 +1109,18 @@
  )))
  (((
--01: Close ,  00: Open , 11: No action
--)))
++00: Closed ,  01: Open , 11: No action
--(((
--[[image:image-20220524093724-9.png]]
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %)
++|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**RO1**|(% style="background-color:#4f81bd; color:white" %)**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
  )))
  (% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
@@ -1120,7 +1120,6 @@
--
  ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
@@ -1131,7 +1131,7 @@
  * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
--**0x05 aa bb cc dd     **~/~/ Set RO1/RO2 relay with time control
++(% style="color:blue" %)**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:
@@ -1147,17 +1147,25 @@
  (% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
--[[image:image-20220714135731-1.png||height="406" width="627"]]
++[[image:image-20221008095908-1.png||height="364" width="564"]]
  (% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms
++
++(% style="color:red" %)**Note:**
++
++   Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes
++
++   Before Firmwre v1.6.0 the latch time only suport 2 bytes.
++
++
  (% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
  **Example payload:**
--**~1. 05 01 11 07 D**
++**~1. 05 01 11 07 D0**
  Relay1 and Relay 2 will be set to NC , last 2 seconds, then change back to original state.
@@ -1180,163 +1180,142 @@
  When voltage exceed the threshold, count. Feature see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
--* (% style="color:#037691" %)**AT Command:**
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX   ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
--**AT+VOLMAX   ** ~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
--
--
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):**
--**0xA5 aa bb cc   **~/~/ Same as AT+VOLMAX=(aa bb),cc
++(% style="color:blue" %)**0xA5 aa bb cc   ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc
--
  ==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ====
--* (% style="color:#037691" %)**AT Command:**
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) **
--**AT+SETCNT=aa,(bb cc dd ee) **
++(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count
--aa: 1: Set count1,
++(% style="color:red" %)**bb cc dd ee: **(%%)number to be set
--2: Set count2,
--3: Set AV1 count
--
--Bb cc dd ee: number to be set
--
--
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):**
--**0x A8 aa bb cc dd ee     **~/~/ same as AT+SETCNT=aa,(bb cc dd ee)
++(% style="color:blue" %)**0x A8 aa bb cc dd ee     ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee)
--
  ==== 3.4.2.18 Counting ~-~- Clear Counting ====
  Clear counting for counting mode
--* (% style="color:#037691" %)**AT Command:**
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT         **(%%) ~/~/ clear all counting
--**AT+CLRCOUNT ** ~/~/ clear all counting
--
--
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):**
--**0x A6 01    ** ~/~/ clear all counting
++(% style="color:blue" %)**0x A6 01    ** (%%)~/~/ clear all counting
++==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
--==== 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)
++(% style="color:blue" %)**AT+COUTIME=60  **(%%)~/~/ Set save time to 60 seconds. Device will save the counting result in internal flash every 60 seconds. (min value: 30)
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):**
--**0x A7 aa bb cc     **~/~/ same as AT+COUTIME =aa bb cc,
++(% style="color:blue" %)**0x A7 aa bb cc     ** (%%)~/~/ same as AT+COUTIME =aa bb cc,
  (((
  range: aa bb cc:0 to 16777215,  (unit:second)
++)))
--
--)))
++==== 3.4.2.20 Reset save RO DO state ====
--==== 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)
++(% style="color:blue" %)**AT+RODORESET=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:blue" %)**AT+RODORESET=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
++(% style="color:blue" %)**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
++(% style="color:blue" %)**AT+DECRYPT=1  **   (%%)~/~/ The payload is uploaded without encryption
--**AT+DECRYPT=0  **~/~/Encrypt when uploading payload (default)
++(% style="color:blue" %)**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
++(% style="color:blue" %)**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.
++(% style="color:blue" %)**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)
++(% style="color:blue" %)**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.
++(% style="color:blue" %)**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)
++(% style="color:blue" %)**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:blue" %)**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
++(% style="color:blue" %)**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.
++(% style="color:blue" %)**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.
@@ -1349,7 +1349,7 @@
  * (((
  (% style="color:#037691" %)**Downlink Payload**(%%)**:**
--**26 01  **  ~/~/ Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.
++(% style="color:blue" %)**26 01  ** (%%)  ~/~/  Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.
  )))
@@ -1359,81 +1359,131 @@
  [[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 Integrating with ThingsEye.io ==
--== 3.5 Integrate with Mydevice ==
++If you are using one of The Things Stack plans, you can integrate ThingsEye.io with your application. Once integrated, ThingsEye.io works as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
++=== 3.5.1 Configuring MQTT Connection Information with The Things Stack Sandbox ===
--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:
++* In **The Things Stack Sandbox**, select your application under **Applications**.
++* Select **MQTT** under **Integrations**.
++* In the **Connection information **section, for **Username**, The Things Stack displays an auto-generated username. You can use it or provide a new one.
++* For the **Password**, click the **Generate new API key** button to generate a password. You can see it by clicking on the **eye** button.
--(((
--(% style="color:blue" %)**Step 1**(%%): Be sure that your device is programmed and properly connected to the network at this time.
--)))
++[[image:tts-mqtt-integration.png||height="625" width="1000"]]
--(((
--(% 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:
++=== 3.5.2 Configuring ThingsEye.io ===
--
--)))
++* Login to your [[ThingsEye.io >>https://thingseye.io]]account.
++* Under the **Integrations center**, click **Integrations**.
++* Click the **Add integration** button (the button with the **+** symbol).
--[[image:image-20220719105525-1.png||height="377" width="677"]]
++[[image:thingseye-io-step-1.png||height="625" width="1000"]]
++On the **Add integration** window, configure the following:
--[[image:image-20220719110247-2.png||height="388" width="683"]]
++~1. **Basic settings:**
++* Select **The Things Stack Community** from the **Integration type** list.
++* Enter a suitable name for your integration in the **Name **text** **box or keep the default name.
++* Ensure the following options are turned on.
++** Enable integration
++** Debug mode
++** Allow create devices or assets
++* Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
--(% style="color:blue" %)**Step 3**(%%): Create an account or log in Mydevices.
++[[image:thingseye-io-step-2.png||height="625" width="1000"]]
--(% style="color:blue" %)**Step 4**(%%): Search LT-22222-L(for both LT-22222-L / LT-33222-L) and add DevEUI.(% style="display:none" %)
--Search under The things network
++2. **Uplink data converter:**
--[[image:1653356838789-523.png||height="337" width="740"]]
++* Click the **Create new** button if it is not selected by default.
++* Enter a suitable name for the uplink data converter in the **Name **text** **box or keep the default name.
++* Click the **JavaScript** button.
++* Paste the uplink decoder function into the text area (first, delete the default code). The demo decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Uplink_Converter.js]].
++* Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
++[[image:thingseye-io-step-3.png||height="625" width="1000"]]
++3.** Downlink data converter (this is an optional step):**
--After added, the sensor data arrive TTN, it will also arrive and show in Mydevices.
++* Click the **Create new** button if it is not selected by default.
++* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name
++* Click the **JavaScript** button.
++* Paste the downlink decoder function into the text area (first, delete the default code). The demo decoder function can be found here.
++* Click the **Next** button. You will be navigated to the **Connection** tab.
--[[image:image-20220524094909-1.png||height="335" width="729"]]
++[[image:thingseye-io-step-4.png||height="625" width="1000"]]
++4. **Connection:**
--[[image:image-20220524094909-2.png||height="337" width="729"]]
++* Choose **Region** from the **Host type**.
++* Enter the **cluster** of your **The Things Stack** in the **Region** textbox. You can find the cluster in the url (e.g., https:~/~/**eu1**.cloud.thethings.network/...).
++* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The username and password can be found on the MQTT integration page of your The Things Stack account (see Configuring MQTT Connection information with The Things Stack Sandbox).
++* Click the **Check connection** button to test the connection. If the connection is successful, you can see the message saying **Connected**.
++* Click the **Add** button.
++[[image:thingseye-io-step-5.png||height="625" width="1000"]]
--[[image:image-20220524094909-3.png||height="338" width="727"]]
++Your integration is added to the** Integrations** list and it will display on the **Integrations** page. Check whether the status is showing as 'Active'. if not, check your configuration settings again.
--[[image:image-20220524094909-4.png||height="339" width="728"]](% style="display:none" %)
++[[image:thingseye-io-step-6.png||height="625" width="1000"]]
--[[image:image-20220524094909-5.png||height="341" width="734"]]
++Viewing integration details:
++Click on the your integration from the list. The Integration details window will appear with the Details tab selected. The Details tab shows all the settings you have provided for this integration.
++[add image here]
--== 3.6 Interface Detail ==
++If you want to edit the settings you have provided, click on the Toggle edit mode button.
++[add image here]
++Once you have done click on the Apply changes button.
++
++Note: See also ThingsEye documentation.
++
++Click on the Events tab.
++
++- Select Debug from the Event type dropdown.
++
++- Select the time frame from the time window.
++
++[insert image]
++
++- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
++
++[insert image]
++
++
++Deleting the integration:
++
++If you want to delete this integration, click the Delete integration button.
++
++
++== 3.6 Interface Details ==
++
  === 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) ===
--Support NPN Type sensor
++Support NPN-type sensor
  [[image:1653356991268-289.png]]
++=== 3.6.2 Digital Input Ports: DI1/DI2 ( For LT-22222-L) ===
--=== 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.
++The DI ports of the LT-22222-L can support **NPN**, **PNP**, or **dry contact** output sensors.
  )))
  (((
  (((
--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.
++The part of the internal circuit of the LT-22222-L shown below includes the NEC2501 photocoupler. The active current from NEC2501 pin 1 to pin 2 is 1 mA, with a maximum allowable current of 50 mA. When active current flows from NEC2501 pin 1 to pin 2, the DI becomes active HIGH and the DI LED status changes.
  )))
@@ -1443,7 +1443,7 @@
  (((
  (((
--When use need to connect a device to the DI port, both DI1+ and DI1- must be connected.
++(% style="color:#000000; font-family:Arial,sans-serif; font-size:11pt; font-style:normal; font-variant-alternates:normal; font-variant-east-asian:normal; font-variant-ligatures:normal; font-variant-numeric:normal; font-variant-position:normal; font-weight:400; text-decoration:none; white-space:pre-wrap" %)When connecting a device to the DI port, both DI1+ and DI1- must be connected.
  )))
  )))
@@ -1452,22 +1452,22 @@
  )))
  (((
--(% style="color:blue" %)**Example1**(%%): Connect to a Low active sensor.
++(% style="color:#0000ff" %)**Example 1**(%%): Connecting to a low-active sensor.
  )))
  (((
--This type of sensor will output a low signal GND when active.
++This type of sensor outputs a low (GND) signal when active.
  )))
  * (((
--Connect sensor's output to DI1-
++Connect the sensor's output to DI1-
  )))
  * (((
--Connect sensor's VCC to DI1+.
++Connect the sensor's VCC to DI1+.
  )))
  (((
--So when sensor active, the current between NEC2501 pin1 and pin2 is：
++When the sensor is active, the current between NEC2501 pin 1 and pin 2 will be：
  )))
  (((
@@ -1475,32 +1475,30 @@
  )))
  (((
--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.
++For example, if** DI1+ **= **12V**, the resulting current is [[image:1653968155772-850.png||height="23" width="19"]]= 12mA. Therefore, the LT-22222-L will be able to detect this active signal.
  )))
  (((
--
--
  )))
  (((
--(% style="color:blue" %)**Example2**(%%): Connect to a High active sensor.
++(% style="color:#0000ff" %)**Example 2**(%%): Connecting to a high-active sensor.
  )))
  (((
--This type of sensor will output a high signal (example 24v) when active.
++This type of sensor outputs a high signal (e.g., 24V) when active.
  )))
  * (((
--Connect sensor's output to DI1+
++Connect the sensor's output to DI1+
  )))
  * (((
--Connect sensor's GND DI1-.
++Connect the sensor's GND DI1-.
  )))
  (((
--So when sensor active, the current between NEC2501 pin1 and pin2 is:
++When the sensor is active, the current between NEC2501 pin1 and pin2 will be:
  )))
  (((
@@ -1508,32 +1508,30 @@
  )))
  (((
--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.
++If **DI1+ = 24V**, the resulting current[[image:1653968155772-850.png||height="23" width="19"]] is 24mA, Therefore, the LT-22222-L will detect this high-active signal.
  )))
  (((
--
--
  )))
  (((
--(% style="color:blue" %)**Example3**(%%): Connect to a 220v high active sensor.
++(% style="color:#0000ff" %)**Example 3**(%%): Connecting to a 220V high-active sensor.
  )))
  (((
--Assume user want to monitor an active signal higher than 220v, to make sure not burn the photocoupler
++Assume that you want to monitor an active signal higher than 220V without damaging the photocoupler
  )))
  * (((
--Connect sensor's output to DI1+ with a serial 50K resistor
++Connect the sensor's output to DI1+ with a 50K resistor in series.
  )))
  * (((
--Connect sensor's GND DI1-.
++Connect the sensor's GND DI1-.
  )))
  (((
--So when sensor active, the current between NEC2501 pin1 and pin2 is:
++When the sensor is active, the current between NEC2501 pin1 and pin2 will be:
  )))
  (((
@@ -1541,44 +1541,56 @@
  )))
  (((
--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.
++If the sensor output is 220V, then [[image:1653968155772-850.png||height="23" width="19"]](% id="cke_bm_243359S" style="display:none" wfd-invisible="true" %)[[image:image-20220524095628-8.png]](%%) = DI1+ / 51K  = 4.3mA. Therefore, the LT-22222-L will be able to safely detect this high-active signal.
  )))
++(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
--=== 3.6.3 Digital Output Port: DO1/DO2 /DO3 ===
++From the DI port circuit above, you can see that activating the photocoupler requires a voltage difference between the DI+ and DI- ports. However, the Dry Contact sensor is a passive component and cannot provide this voltage difference.
++To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram.
--NPN output: GND or Float. Max voltage can apply to output pin is 36v.
++[[image:image-20230616235145-1.png]]
--[[image:1653357531600-905.png]]
++(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
++[[image:image-20240219115718-1.png]]
--=== 3.6.4 Analog Input Interface ===
++=== 3.6.3 Digital Output Ports: DO1/DO2 /DO3 ===
--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:
++(% style="color:blue" %)**NPN output**(%%): GND or Float. The maximum voltage that can be applied to the output pin is 36V.
++(% style="color:red" %)**Note: The DO pins will float when the device is powered off.**
++[[image:1653357531600-905.png]]
++
++
++=== 3.6.4 Analog Input Interfaces ===
++
++
++The analog input interface is shown below. The LT-22222-L will measure the IN2 voltage to calculate the current passing through the load. The formula is:
++
++
  (% style="color:blue" %)**AC2 = (IN2 voltage )/12**
  [[image:1653357592296-182.png]]
--Example to connect a 4~~20mA sensor
++Example:  Connecting a 4~~20mA sensor
--We take the wind speed sensor as an example for reference only.
++We will use the wind speed sensor as an example for reference only.
--**Specifications of the wind speed sensor:**
++(% style="color:blue" %)**Specifications of the wind speed sensor:**
--Red:      12~~24v
++(% style="color:red" %)**Red:      12~~24V**
--Yellow:  4~~20mA
++(% style="color:#ffc000" %)**Yellow:  4~~20mA**
--Black:   GND
++**Black:   GND**
--
  **Connection diagram:**
  [[image:1653357640609-758.png]]
@@ -1586,12 +1586,29 @@
  [[image:1653357648330-671.png||height="155" width="733"]]
++Example: Connecting to a regulated power supply to measure voltage
++[[image:image-20230608101532-1.png||height="606" width="447"]]
++
++[[image:image-20230608101608-2.jpeg||height="379" width="284"]]
++
++[[image:image-20230608101722-3.png||height="102" width="1139"]]
++
++
++(% style="color:blue; font-weight:bold" %)**Specifications of the regulated power supply**(% style="color:blue" %)**:**
++
++(% style="color:red" %)**Red:      12~~24v**
++
++**Black:   GND**
++
++
  === 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:
++The LT-22222-L has two relay interfaces, RO1 and RO2, each using two pins of the screw terminal (ROx-1 and ROx-2 where x is the port number, 1 or 2). You can connect a device's power line in series with one of the relay interfaces (e.g., RO1-1 and RO1-2 screw terminals). See the example below:
++
++**Note**: The ROx pins will be in the Open (NO) state when the LT-22222-L is powered off.
  )))
  [[image:image-20220524100215-9.png]]
@@ -1600,27 +1600,51 @@
  [[image:image-20220524100215-10.png||height="382" width="723"]]
--
  == 3.7 LEDs Indicators ==
--[[image:image-20220524100748-11.png]]
++(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
++|(% style="background-color:#4f81bd; color:white; width:50px" %)**LEDs**|(% style="background-color:#4f81bd; color:white; width:460px" %)**Feature**
++|**PWR**|Always on if there is power
++|**TX**|(((
++(((
++Device boot: TX blinks 5 times.
++)))
++(((
++Successful join network: TX ON for 5 seconds.
++)))
++(((
++Transmit a LoRa packet: TX blinks once
++)))
++)))
++|**RX**|RX blinks once when receiving a packet.
++|**DO1**|For LT-22222-L: ON when DO1 is low, OFF when DO1 is high
++|**DO2**|For LT-22222-L: ON when DO2 is low, OFF when DO2 is high
++|**DI1**|(((
++For LT-22222-L: ON when DI1 is high, OFF when DI1 is low
++)))
++|**DI2**|(((
++For LT-22222-L: ON when DI2 is high, OFF when DI2 is low
++)))
++|**RO1**|For LT-22222-L: ON when RO1 is closed, OFF when RO1 is open
++|**RO2**|For LT-22222-L: ON when RO2 is closed, OFF when RO2 is open
--= 4. Use AT Command =
++= 4. Using AT Command =
++== 4.1 Connecting the LT-22222-L to a computer ==
--== 4.1 Access AT Command ==
++(((
++The LT-22222-L supports programming using AT Commands. You can use a USB-to-TTL adapter along with a 3.5mm Program Cable to connect the LT-22222-L to a computer, as shown below.
++)))
--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]]
  (((
--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:
++On the PC, the user needs to set the (% style="color:#4f81bd" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) to a baud rate of (% style="color:green" %)**9600**(%%) to access to access serial console of LT-22222-L. The AT commands are disabled by default, and a password (default:(% style="color:green" %)**123456**)(%%) must be entered to active them, as shown below:
  )))
  [[image:1653358355238-883.png]]
@@ -1627,10 +1627,12 @@
  (((
--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/]]
++You can find more details in the [[AT Command Manual>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
  )))
  (((
++The following table lists all the AT commands related to the LT-22222-L, except for those used for switching between modes.
++
  AT+<CMD>?        : Help on <CMD>
  )))
@@ -1643,7 +1643,7 @@
  )))
  (((
--AT+<CMD>=?       : Get the value
++AT+<CMD>=?       :  Get the value
  )))
  (((
@@ -1671,11 +1671,11 @@
  )))
  (((
--AT+APPSKEY: Get or Set the Application Session Key
++AT+APPSKEY:  Get or Set the Application Session Key
  )))
  (((
--AT+APPEUI: Get or Set the Application EUI
++AT+APPEUI:    Get or Set the Application EUI
  )))
  (((
@@ -1687,7 +1687,7 @@
  )))
  (((
--AT+DR: Get or Set the Data Rate. (0-7 corresponding to DR_X)
++AT+DR:  Get or Set the Data Rate. (0-7 corresponding to DR_X)
  )))
  (((
@@ -1723,7 +1723,7 @@
  )))
  (((
--AT+NJM: Get or Set the Network Join Mode. (0: ABP, 1: OTAA)
++AT+NJM:    Get or Set the Network Join Mode. (0: ABP, 1: OTAA)
  )))
  (((
@@ -1767,7 +1767,7 @@
  )))
  (((
--AT+VER: Get current image version and Frequency Band
++AT+VER:  Get current image version and Frequency Band
  )))
  (((
@@ -1775,7 +1775,7 @@
  )))
  (((
--AT+CFS: Get confirmation status of the last AT+SEND (0-1)
++AT+CFS:  Get confirmation status of the last AT+SEND (0-1)
  )))
  (((
@@ -1815,107 +1815,108 @@
  )))
--
  == 4.2 Common AT Command Sequence ==
--
  === 4.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
  (((
--**If device has not joined network yet:**
++(((
++(% style="color:blue" %)**If device has not joined network yet:**
  )))
++)))
  (((
--(% style="background-color:#dcdcdc" %)123456
++(% style="background-color:#dcdcdc" %)**123456**
  )))
  (((
--(% style="background-color:#dcdcdc" %)AT+FDR
++(% style="background-color:#dcdcdc" %)**AT+FDR**
  )))
  (((
--(% style="background-color:#dcdcdc" %)123456
++(% style="background-color:#dcdcdc" %)**123456**
  )))
  (((
--(% style="background-color:#dcdcdc" %)AT+NJM=0
++(% style="background-color:#dcdcdc" %)**AT+NJM=0**
  )))
  (((
--(% style="background-color:#dcdcdc" %)ATZ
++(% style="background-color:#dcdcdc" %)**ATZ**
  )))
  (((
--**If device already joined network:**
++(% style="color:blue" %)**If device already joined network:**
  )))
  (((
--(% style="background-color:#dcdcdc" %)AT+NJM=0
++(% style="background-color:#dcdcdc" %)**AT+NJM=0**
  )))
  (((
--(% style="background-color:#dcdcdc" %)ATZ
++(% style="background-color:#dcdcdc" %)**ATZ**
  )))
--
  === 4.2.2 Single-channel ABP mode (Use with LG01/LG02) ===
  (((
--(% style="background-color:#dcdcdc" %)123456(%%)     Enter Password to have AT access.
++(((
++(% 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" %)** AT+FDR**(%%)     ~/~/ Reset Parameters to Factory Default, Keys Reserve
  )))
  (((
--(% style="background-color:#dcdcdc" %) 123456(%%)     Enter Password to have AT access.
++(% style="background-color:#dcdcdc" %)** 123456**(%%)       ~/~/ Enter Password to have AT access.
  )))
  (((
--(% style="background-color:#dcdcdc" %) AT+CLASS=C(%%) Set to work in CLASS C
++(% style="background-color:#dcdcdc" %)** AT+CLASS=C**(%%)   ~/~/ Set to work in CLASS C
  )))
  (((
--(% style="background-color:#dcdcdc" %) AT+NJM=0(%%)    Set to ABP mode
++(% 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+ADR=0**(%%)     ~/~/ Set the Adaptive Data Rate Off
  )))
  (((
--(% style="background-color:#dcdcdc" %) AT+DR=5(%%)       Set Data Rate
++(% style="background-color:#dcdcdc" %)** AT+DR=5**(%%)       ~/~/ Set Data Rate
  )))
  (((
--(% style="background-color:#dcdcdc" %) AT+TDC=60000(%%)              Set transmit interval to 60 seconds
++(% 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+CHS=868400000**(%%)     ~/~/ Set transmit frequency to 868.4Mhz
  )))
  (((
--(% style="background-color:#dcdcdc" %) AT+RX2FQ=868400000(%%)  Set RX2Frequency to 868.4Mhz (according to the result from server)
++(% style="background-color:#dcdcdc" %)** AT+RX2FQ=868400000**(%%)    ~/~/ Set RX2Frequency to 868.4Mhz (according to the result from server)
  )))
  (((
--(% style="background-color:#dcdcdc" %) AT+RX2DR=5(%%)                  Set RX2DR to match the downlink DR from server. see below
++(% style="background-color:#dcdcdc" %)** AT+RX2DR=5**(%%)** **                   ~/~/ Set RX2DR to match the downlink DR from server. see below
  )))
  (((
--(% 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.
++(% 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.
  )))
  (((
--(% style="background-color:#dcdcdc" %) ATZ         (%%)                             Reset MCU
++(% style="background-color:#dcdcdc" %)** ATZ**         (%%)                                 ~/~/ Reset MCU
  )))
@@ -1925,12 +1925,14 @@
  )))
  (((
--(% 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
++**~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.**
  )))
  (((
@@ -1937,45 +1937,53 @@
  [[image:1653359097980-169.png||height="188" width="729"]]
  )))
++
++=== 4.2.3 Change to Class A ===
++
++
  (((
--
--)))
++(% style="color:blue" %)**If sensor JOINED:**
++(% style="background-color:#dcdcdc" %)**AT+CLASS=A**
--=== 4.2.3 Change to Class A ===
++(% style="background-color:#dcdcdc" %)**ATZ**
++)))
--If sensor JOINED
--(% style="background-color:#dcdcdc" %)AT+CLASS=A
--ATZ
++= 5. Case Study =
++== 5.1 Counting how many objects pass through the flow Line ==
--= 5. FAQ =
++Reference Link: [[How to set up to setup counting for objects passing through the flow line>>How to set up to count objects pass in flow line]]?
--== 5.1 How to upgrade the image? ==
++= 6. FAQ =
++== 6.1 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
++The LT-22222-L I/O Controller is shipped with a 3.5mm cable, which is used to upload an image to LT in order to:
++
++* Support new features.
++* Fix bugs.
  * Change LoRaWAN bands.
--Below shows the hardware connection for how to upload an image to the LT:
++Below is the hardware connection setup for uploading an image to the LT:
  [[image:1653359603330-121.png]]
  (((
--(% 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: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:#0000ff" %)**Step 1**(%%)**:** Download the F[[lash 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:#0000ff" %)**Step 2**(%%)**:** Download the [[LT Image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]].
++(% style="color:#0000ff" %)**Step 3**(%%)**:** Open the Flash Loader and 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 (% 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.
++Hold down the PRO button, then momentarily press the RST reset button. The (% style="color:red" %)**DO1 LED**(%%) will change from OFF to ON. When the (% style="color:red" %)**DO1 LED**(%%) is ON, it indicates that the device is in download mode.
++)))
  )))
@@ -1982,57 +1982,54 @@
    [[image:image-20220524103407-12.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:
++(% style="color:red" %)**Note**(%%): If you have lost the programming cable, you can make one from a 3.5mm cable. The pin mapping is as follows:
--
  [[image:1653360054704-518.png||height="186" width="745"]]
  (((
  (((
--
++== 6.2 How to change the LoRa Frequency Bands/Region? ==
--== 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.
++You can follow the introductions on [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloading, select the required image file.
  )))
  (((
++== 6.3 How to set up LT to work with a Single Channel Gateway, such as LG01/LG02? ==
--== 5.3 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.
++In this case, you need to set the LT-33222-L to work in ABP mode and transmit on only one frequency.
  )))
  )))
  (((
  (((
--Assume we have a LG02 working in the frequency 868400000 now , below is the step.
++Assume you have an LG02 working on the frequency 868400000. Below are the steps.
--
  )))
  )))
  (((
--(% 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.
++(% style="color:#0000ff" %)**Step 1**(%%):  Log in to The Things Stack SANDBOX, create an ABP device in the application, and input the Network Session key (NwkSKey), App session key (AppSKey) of the device.
  )))
@@ -2056,16 +2056,23 @@
  )))
  (((
--(% 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
++(% 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" %)**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
  )))
@@ -2076,26 +2076,29 @@
  [[image:1653360498588-932.png||height="485" width="726"]]
++== 6.4 How to change the uplink interval? ==
--== 5.4 Can I see counting event in Serial? ==
++Please see this link: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/]]
--(((
--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.5 Can I see the counting event in Serial? ==
--== 5.5 Can i use point to point communication for LT-22222-L? ==
++(((
++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.
--Yes, please refer [[Point to Point Communication>>doc:Main. Point to Point Communication of LT-22222-L.WebHome]]
++== 6.6 Can I use point-to-point communication with LT-22222-L? ==
++Yes, please refer [[Point to Point Communication>>doc:Main. Point to Point Communication of LT-22222-L.WebHome]]. this is [[firmware>>https://github.com/dragino/LT-22222-L/releases]].
++
  )))
  (((
--== 5.6 Why does the relay output become the default and open relay after the lt22222 is powered off? ==
++== 6.7 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.
@@ -2107,23 +2107,33 @@
  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? ==
++== 6.8 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.9 Can LT22222-L save RO state? ==
--= 6. Trouble Shooting =
++Firmware version needs to be no less than 1.6.0.
--
++
++== 6.10 Why does the LT22222 always report 15.585V when measuring AVI? ==
++
++
++It is likely that the GND is not connected during the measurement, or the wire connected to the GND is loose.
++
++
++= 7. Trouble Shooting =
  )))
  (((
  (((
--== 6.1 Downlink doesn't work, how to solve it? ==
++== 7.1 Downlink doesn't work, how to solve it? ==
  )))
@@ -2136,9 +2136,8 @@
  (((
++== 7.2 Have trouble to upload image. ==
--== 6.2 Have trouble to upload image. ==
--
  )))
@@ -2149,9 +2149,8 @@
  (((
++== 7.3 Why I can't join TTN in US915 /AU915 bands? ==
--== 6.3 Why I can't join TTN in US915 /AU915 bands? ==
--
  )))
@@ -2160,10 +2160,16 @@
  )))
++== 7.4 Why can LT22222 perform Uplink normally, but cannot receive Downlink? ==
--= 7. Order Info =
++The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue state.
++Use this command to bring their counts back together: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
++
++= 8. Order Info =
++
++
  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
  (% style="color:#4f81bd" %)**XXX:**
@@ -2178,11 +2178,9 @@
  * (% style="color:red" %)**IN865**(%%):   LT with frequency bands IN865
  * (% style="color:red" %)**CN779**(%%):  LT with frequency bands CN779
++= 9. Packing Info =
--= 8. Packing Info =
--
--
  **Package Includes**:
  * LT-22222-L I/O Controller x 1
@@ -2197,26 +2197,22 @@
  * Package Size / pcs : 14.5 x 8 x 5 cm
  * Weight / pcs : 170g
++= 10. Support =
--= 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]]
++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.cc>>mailto:Support@dragino.cc]]
--
  )))
--= 10. Reference =
++= 11. 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]]
  * [[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-20221112174847-1.png

Author

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

Size

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

Content

image-20230424115112-1.png

Author

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

Size

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

Content

image-20230425173351-1.png

Author

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

Size

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

Content

image-20230425173427-2.png

Author

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

Size

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

Content

image-20230426161322-1.png

Author

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

Size

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

Content

image-20230608101532-1.png

Author

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

Size

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

Content

image-20230608101608-2.jpeg

Author

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

Size

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

Content

image-20230608101722-3.png

Author

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

Size

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

Content

image-20230616235145-1.png

Author

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

Size

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

Content

image-20240219115718-1.png

Author

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

Size

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

Content

lt-22222-l-dev-repo-p1.png

Author

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

Size

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

Content

lt-22222-l-dev-repo-reg-p1.png

Author

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

Size

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

Content

lt-22222-l-dev-repo-reg-p2.png

Author

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

Size

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

Content

lt-22222-l-manually-p1.png

Author

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

Size

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

Content

lt-22222-l-manually-p2.png

Author

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

Size

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

Content

thingseye-io-step-1.png

Author

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

Size

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

Content

thingseye-io-step-2.png

Author

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

Size

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

Content

thingseye-io-step-3.png

Author

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

Size

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

Content

thingseye-io-step-4.png

Author

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

Size

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

Content

thingseye-io-step-5.png

Author

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

Size

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

Content

thingseye-io-step-6.png

Author

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

Size

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

Content

tts-mqtt-integration.png

Author

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

Size

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

Content