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

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

From 130.1 to 130.2 From 210.1 to 211.1

From version 130.2

edited by Xiaoling
on 2024/02/19 14:44

Change comment: There is no comment for this version

To version 210.1

edited by Dilisi S
on 2024/11/24 00:36

Change comment: fix toc

Raw
Rendered

Summary

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

Details

Page properties

Title

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

Author

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

Content

@@ -3,6 +3,10 @@
++
++
++
++
  **Table of Contents:**
  {{toc/}}
@@ -13,301 +13,311 @@
--= 1.Introduction =
++= 1. Introduction =
--== 1.1 What is LT Series I/O Controller ==
++== 1.1 What is the LT-22222-L I/O Controller? ==
  (((
--
--
  (((
--The Dragino (% style="color:blue" %)**LT series I/O Modules**(%%) are Long Range LoRaWAN I/O Controller. It contains different I/O Interfaces such as:** (% style="color:blue" %)analog current Input, analog voltage input(%%)**(% style="color:blue" %), **relay output**, **digital input**(%%) and (% style="color:blue" %)**digital output**(%%) etc. The LT I/O Modules are designed to simplify the installation of I/O monitoring.
--)))
--)))
++{{info}}
++**This manual is also applicable to the LT-33222-L.**
++{{/info}}
--(((
--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, building automation, and so on.
--)))
++The Dragino (% style="color:blue" %)**LT-22222-L I/O Controller**(%%) is an advanced LoRaWAN end 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 LT I/O Controllers is aiming to provide an (% style="color:blue" %)**easy and low cost installation** (%%)by using LoRa wireless technology.
++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 use environment includes:
  )))
  (((
--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.
++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.
  )))
  (((
--2) User can set up a LoRaWAN gateway locally and configure the controller to connect to the gateway via wireless.
++You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways:
--
++* If there is public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Stack Community 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.
  )))
  (((
--[[image:1653295757274-912.png]]
--
++
++The network diagram below illustrates how the LT-22222-L communicates with a typical LoRaWAN network.
  )))
++(% class="wikigeneratedid" %)
++[[image:lorawan-nw.jpg||height="354" width="900"]]
++
  == 1.2 Specifications ==
--(((
--
--
  (% style="color:#037691" %)**Hardware System:**
--)))
--* (((
--STM32L072xxxx 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.
--(% style="color:#037691" %)**Interface for Model: LT22222-L:**
--)))
++(% style="color:#037691" %)**LoRa Spec:**
--* (((
--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.
--)))
++* Frequency Range:
++** Band 1 (HF): 862 ~~ 1020 MHz
++** Band 2 (LF): 410 ~~ 528 MHz
++* 168 dB maximum link budget.
++* +20 dBm - 100 mW constant RF output vs.
++* +14 dBm high-efficiency PA.
++* Programmable bit rate up to 300 kbps.
++* High sensitivity: down to -148 dBm.
++* Bullet-proof front end: IIP3 = -12.5 dBm.
++* Excellent blocking immunity.
++* Low RX current of 10.3 mA, 200 nA register retention.
++* Fully integrated synthesizer with a resolution of 61 Hz.
++* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
++* Built-in bit synchronizer for clock recovery.
++* Preamble detection.
++* 127 dB Dynamic Range RSSI.
++* Automatic RF Sense and CAD with ultra-fast AFC.
++* Packet engine up to 256 bytes with CRC.
--(((
--
++== 1.3 Features ==
--(% style="color:#037691" %)**LoRa Spec:**
--)))
++* LoRaWAN Class A & Class C modes
++* Optional Customized LoRa Protocol
++* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
++* AT Commands to change parameters
++* Remotely configure parameters via LoRaWAN Downlink
++* Firmware upgradable via program port
++* Counting
--* (((
--(((
--Frequency Range:
--)))
++== 1.4 Applications ==
--* (((
--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.
++* Smart buildings & home automation
++* Logistics and supply chain management
++* Smart metering
++* Smart agriculture
++* Smart cities
++* Smart factory
++== 1.5 Hardware Variants ==
++(% style="width:524px" %)
++|(% style="width:94px" %)**Model**|(% style="width:98px" %)**Photo**|(% style="width:329px" %)**Description**
++|(% style="width:94px" %)**LT33222-L**|(% style="width:98px" %)(((
++)))|(% style="width:329px" %)(((
++* 2 x Digital Input (Bi-direction)
++* 2 x Digital Output
++* 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)
++* 1 x Counting Port
  )))
--== 1.3 Features ==
++== 2. Assembling the device ==
++== 2.1 Connecting the antenna ==
--* LoRaWAN Class A & Class C protocol
++Connect the LoRa antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper screw terminal block. Secure the antenna by tightening it clockwise.
--* Optional Customized LoRa Protocol
++{{warning}}
++**Warning! Do not power on the device without connecting the antenna.**
++{{/warning}}
--* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
++== 2.2 Terminals ==
--* AT Commands to change parameters
++The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals.
--* Remote configure parameters via LoRa Downlink
++**Upper screw terminal block (from left to right):**
--* Firmware upgradable via program port
++(% style="width:634px" %)
++|=(% style="width: 295px;" %)Screw 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
--* Counting
++**Lower screw terminal block (from left to right):**
--== 1.4 Applications ==
++(% style="width:633px" %)
++|=(% style="width: 296px;" %)Screw 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
++== 2.3 Connecting LT-22222-L to a Power Source ==
--* Smart Buildings & Home Automation
++The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your 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.
--* Logistics and Supply Chain Management
++{{warning}}
++**We recommend that you power on the LT-22222-L after configuring its registration information with a LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.**
++{{/warning}}
--* Smart Metering
--* Smart Agriculture
++[[image:1653297104069-180.png]]
--* Smart Cities
--* Smart Factory
++= 3. Registering LT-22222-L with a LoRaWAN Network Server =
--== 1.5 Hardware Variants ==
++The LT-22222-L supports both OTAA (Over-the-Air Activation) and ABP (Activation By Personalization) methods to activate with a LoRaWAN Network Server. However, OTAA is the most secure method for activating a device with a LoRaWAN Network Server. OTAA regenerates session keys upon initial registration and regenerates new session keys after any subsequent reboots. By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode.
--(% 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)
--* 2 x 0~~20mA Analog Input (res:0.01mA)
--* 2 x 0~~30V Analog Input (res:0.01v)
--* 1 x Counting Port
--)))
++=== 3.2.1 Prerequisites ===
--= 2. Power ON Device =
++The LT-22222-L comes with device registration information such as DevEUI, AppEUI, and AppKey that allows you to register it with a LoRaWAN network. These 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"]]
--(((
--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.
--)))
++{{info}}
++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.
++{{/info}}
--(((
--PWR will on when device is properly powered.
++The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
--
--)))
++=== 3.2.2 The Things Stack ===
--[[image:1653297104069-180.png]]
++This section guides you through how to register your LT-22222-L with The Things Stack Sandbox.
++{{info}}
++The Things Stack Sandbox was formally called The Things Stack Community Edition.
++{{/info}}
--= 3. Operation Mode =
--== 3.1 How it works? ==
++The network diagram below illustrates the connection between the LT-22222-L and The Things Stack, as well as how the data can be integrated with the ThingsEye IoT platform.
--(((
--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.
--)))
++[[image:dragino-lorawan-nw-lt-22222-n.jpg]]
--(((
--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.
--)))
++{{info}}
++ You can use a LoRaWAN gateway, such as the [[Dragino LPS8N>>https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]], to expand or create LoRaWAN coverage in your area.
++{{/info}}
--== 3.2 Example to join LoRaWAN network ==
++==== 3.2.2.1 Setting up ====
++* Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet.
++* Log in to your The Things Stack Sandbox account.
++* Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs).
++* Go to your application's page and click on the **End devices** in the left menu.
++* On the End devices page, click on **+ Register end device**. Two registration options are available:
--(((
--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.2.2 Using the LoRaWAN Device Repository ====
--
--)))
++* On the **Register end device** page:
++** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
++** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists.
++*** **End device brand**: Dragino Technology Co., Limited
++*** **Model**: LT22222-L I/O Controller
++*** **Hardware ver**: Unknown
++*** **Firmware ver**: 1.6.0
++*** **Profile (Region)**: Select the region that matches your device.
++** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
--[[image:image-20220523172350-1.png||height="266" width="864"]]
++[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
--(((
--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:
++* Register end device page continued...
++** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network'.
++** In the **DevEUI** field, enter the **DevEUI**.
++** In the **AppKey** field, enter the **AppKey.**
++** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
++** Under **After registration**, select the **View registered end device** option.
--
--)))
++[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
--(((
--(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LT IO controller.
--)))
--(((
--Each LT is shipped with a sticker with the default device EUI as below:
--)))
++==== 3.2.2.3 Adding device manually ====
--[[image:image-20230425173427-2.png||height="246" width="530"]]
++* On the **Register end device** page:
++** Select the option **Enter end device specifies manually** under **Input method**.
++** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
++** Select the **LoRaWAN version** as **LoRaWAN Specification 1.0.3**
++** Select the **Regional Parameters version** as** RP001 Regional Parameters 1.0.3 revision A**
++** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the hidden section.
++** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
++** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
++[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
--Input these keys in the LoRaWAN Server portal. Below is TTN screen shot:
--**Add APP EUI in the application.**
++* Register end device page continued...
++** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message '//**This end device can be registered on the network**//'
++** In the **DevEUI** field, enter the **DevEUI**.
++** In the **AppKey** field, enter the **AppKey**.
++** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
++** Under **After registration**, select the **View registered end device** option.
++** Click the **Register end device** button.
--[[image:1653297955910-247.png||height="321" width="716"]]
++[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
--**Add APP KEY and DEV EUI**
++You will be navigated to the **Device overview** page.
--[[image:1653298023685-319.png]]
++[[image:lt-22222-device-overview.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.
--
--)))
++==== 3.2.2.4 Joining ====
--[[image:1653298044601-602.png||height="405" width="709"]]
++On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
++Now power on your LT-22222-L. The **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** The Things Stack network server. The **TX LED** will be on for **5 seconds** after joining the network. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server.
--== 3.3 Uplink Payload ==
++[[image:lt-22222-join-network.png||height="625" width="1000"]]
--There are five working modes + one interrupt mode on LT for different type application:
--* (% style="color:blue" %)**MOD1**(%%): (default setting): 2 x ACI + 2AVI + DI + DO + RO
++==== 3.2.2.5 Uplinks ====
++
++After successfully joining, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**). When the LT-22222-L sends an uplink message to the server, the **TX LED** turns on for **1 second**. By default, you will receive an uplink data message from the device every 10 minutes.
++
++Click on one of a **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the decode_payload {} JSON object.
++
++[[image:lt-22222-ul-payload-decoded.png]]
++
++
++If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **Applications > your application > End devices** > **your  end device** > **Payload formatters** > **Uplink**. Then  select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
++
++{{info}}
++The Things Stack provides two levels of payload formatters: application level and device level. The device-level payload formatters **override **the application-level payload formatters.
++{{/info}}
++
++[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
++
++
++==== 3.2.2.6 Downlinks ====
++
++When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
++
++
++== 3.3 Working Modes and Uplink Payload formats ==
++
++
++The LT-22222-L has 5 **working 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.
++
++* (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 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
@@ -318,12 +318,19 @@
  * (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5
++The uplink messages are sent over LoRaWAN FPort=2. By default, an uplink message is sent every 10 minutes.
++
  === 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
--
  (((
--The uplink payload includes totally 9 bytes. Uplink packets use FPORT=2 and every 10 minutes send one uplink by default. (% style="display:none" %)
++This is the default mode.
++The uplink payload is 11 bytes long.
++
++(% style="color:red" %)**Note:The maximum count depends on the bytes number of bytes.
++The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
++It starts counting again when it reaches the maximum value.**(% style="display:none" wfd-invisible="true" %)
++
  (% 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|(((
@@ -334,29 +334,29 @@
  ACI1 Current
  )))|(((
  ACI2 Current
--)))|DIDORO*|(((
++)))|**DIDORO***|(((
  Reserve
  )))|MOD
  )))
  (((
--(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below
++(% 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.
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
--|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
--|RO1|RO2|DI3|DI2|DI1|DO3|DO2|DO1
++|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
++|RO1|RO2|--DI3--|DI2|DI1|--DO3--|DO2|DO1
  )))
--* 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.
++* 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.
--(% style="color:red" %)**Note: DI3 and DO3 bit are not valid for LT-22222-L**
++(% style="color:red" %)**Note: DI3 and DO3 bits are not valid for LT-22222-L**
--For example if payload is: [[image:image-20220523175847-2.png]]
++For example, if the payload is: [[image:image-20220523175847-2.png]]
--**The value for the interface is:  **
++**The interface values can be calculated as follows:  **
  AVI1 channel voltage is 0x04AB/1000=1195(DEC)/1000=1.195V
@@ -366,36 +366,41 @@
  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 and there is a load between DO1 and V+.
++** DO1 LED is OFF in both cases.
--**LT22222-L:**
++Reserve = 0
--* [1] DI2 channel is high input and DI2 LED is ON;
--* [0] DI1 channel is low input;
++MOD = 1
--* [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.
++**For LT-22222-L**: In this mode, **DI1 and DI2** are used as counting pins.
  )))
  (((
--Total : 11 bytes payload
++The uplink payload is 11 bytes long.
++(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
++The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
++It starts counting again when it reaches the maximum value.**
++
  (% 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*|(((
@@ -404,26 +404,26 @@
  )))
  (((
--(% 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, FIRST, Reserve, Reserve, DO3, DO2 and DO1, and its size is 1 byte long as shown below.
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
--|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
--|RO1|RO2|FIRST|Reserve|Reserve|DO3|DO2|DO1
++|**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.
++* RO is for the relay. ROx=1: CLOSED,  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.
++* 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.**
++(% 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:**
  )))
  (((
@@ -444,24 +444,27 @@
  (((
  **For LT22222-L:**
--(% style="color:blue" %)**AT+TRIG1=0,100**(%%)**    (set DI1 port to trigger on low level, valid signal is 100ms) **
++(% 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=1,100**(%%)**    (set DI1 port to trigger on high 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+TRIG2=0,100**(%%)**    (set DI2 port to trigger on low 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=1,100**(%%)**    (set DI2 port to trigger on high 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+SETCNT=1,60**(%%)**   (Set COUNT1 value to 60)**
++(% style="color:blue" %)**AT+SETCNT=1,60**(%%)** (sets the 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 ===
++(% style="color:red" %)**Note: The maximum count depends on the bytes it is.
++The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
++It starts counting again when it reaches the maximum value.**
--**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.
  (% 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**
@@ -472,24 +472,24 @@
  )))|DIDORO*|Reserve|MOD
  (((
--(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below
++(% 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" %)
--|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
--|RO1|RO2|FIRST|Reserve|Reserve|DO3|DO2|DO1
++|**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.
++* 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 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:**
  )))
  (((
@@ -502,19 +502,25 @@
  )))
  (((
--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 ===
++(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
++The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
++It starts counting again when it reaches the maximum value.**
++
  (((
--**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.
  )))
  (((
--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.
++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.
  (% 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**
@@ -524,25 +524,25 @@
  )))
  (((
--(% style="color:#4f81bd" %)**DIDORO **(%%)is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below
++(% 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" %)
--|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
--|RO1|RO2|FIRST|Reserve|Reserve|DO3|DO2|DO1
++|**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.
++* 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 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:**
  )))
  (((
@@ -555,27 +555,31 @@
  )))
  (((
--Other AT Commands for counting are similar to [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]].
++AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
  )))
  (((
--**Plus below command for AVI1 Counting:**
++**In addition to that,  below are the commands for AVI1 Counting:**
--(% style="color:blue" %)**AT+SETCNT=3,60**(%%)**            (set AVI Count to 60)**
++(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 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 **(%%)**(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,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 ===
++(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
++The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
++It starts counting again when it reaches the maximum value.**
--**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.
++
  (% 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|(((
@@ -589,25 +589,25 @@
  )))|MOD
  (((
--(% style="color:#4f81bd" %)**DIDORO**(%%) is a combination for RO1, RO2, DI3, DI2, DI1, DO3, DO2 and DO1. Totally 1bytes as below
++(% 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" %)
--|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
++|**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:**
  )))
  (((
@@ -620,29 +620,33 @@
  )))
  (((
--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) ===
++=== 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 __alongside__ with other modes.**
--For example, if user has configured below commands:
++For example, if you configure the following commands:
--* **AT+MOD=1 **            **~-~->**   The normal working mode
--* **AT+ADDMOD6=1**   **~-~->**   Enable trigger
++* **AT+MOD=1 **            **~-~->**   Sets the default working mode
++* **AT+ADDMOD6=1**   **~-~->**   Enables trigger mode
--LT will keep monitoring AV1/AV2/AC1/AC2 every 5 seconds; LT will send uplink packets in two cases:
++The LT-22222-L will continuously monitor AV1, AV2, AC1, and AC2 every 5 seconds. It will send uplink packets in two cases:
--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.**
++1. Periodic uplink: Based on TDC time. The payload is the same as in normal mode (MOD=1 as set above). These are (% style="color:#4f81bd" %)**unconfirmed**(%%) uplinks.
++1. (((
++Trigger uplink: sent when a trigger condition is met. In this case, LT will send two packets
--(% style="color:#037691" %)**AT Command to set Trigger Condition**:
++* 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.**
++)))
++(% style="color:#037691" %)**AT Commands to set Trigger Conditions**:
--(% style="color:#4f81bd" %)**Trigger base on voltage**:
++(% style="color:#4f81bd" %)**Trigger based on voltage**:
  Format: AT+AVLIM=<AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH>
@@ -649,27 +649,25 @@
  **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 AC1 current 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 >
@@ -678,39 +678,38 @@
  AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
--(% style="color:#037691" %)**Downlink Command to set Trigger Condition:**
++(% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
  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
  (% 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**
@@ -724,10 +724,10 @@
  MOD(6)
  )))
--(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if trigger is set for this part. Totally 1byte as below
++(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
--|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
++|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
  |(((
  AV1_LOW
  )))|(((
@@ -746,17 +746,17 @@
  AC2_HIGH
  )))
--* Each bits shows if the corresponding trigger has been configured.
++* Each bit 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 1byte as below
++(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
--|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
++|**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
  |(((
  AV1_LOW
  )))|(((
@@ -775,20 +775,20 @@
  AC2_HIGH
  )))
--* Each bits shows which status has been trigger on this uplink.
++* Each bit shows which status has been triggered 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
--(% 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
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:674px" %)
++|(% style="width:64px" %)**bit 7**|(% style="width:68px" %)**bit 6**|(% style="width:63px" %)**bit 5**|(% style="width:66px" %)**bit 4**|(% style="width:109px" %)**bit 3**|(% style="width:93px" %)**bit 2**|(% style="width:109px" %)**bit 1**|(% style="width:99px" %)**bit 0**
++|(% style="width:64px" %)N/A|(% style="width:68px" %)N/A|(% style="width:63px" %)N/A|(% style="width:66px" %)N/A|(% style="width:109px" %)DI2_STATUS|(% style="width:93px" %)DI2_FLAG|(% style="width:109px" %)DI1_STATUS|(% style="width:99px" %)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:**
@@ -815,230 +815,482 @@
  )))
--== 3.4 Configure LT via AT or Downlink ==
++== 3.4 Configure LT-22222-L via AT Commands or Downlinks ==
--
  (((
--User can configure LT I/O Controller via AT Commands or LoRaWAN Downlink Commands
++You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks.
  )))
  (((
  (((
--There are two kinds of Commands:
++There are two tytes of commands:
  )))
  )))
--* (% 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:blue" %)**Common commands**(%%):
--* (% style="color:blue" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L.  User can see these commands below:
++* (% style="color:blue" %)**Sensor-related commands**(%%):
--=== 3.4.1 Common Commands ===
++=== 3.4.1 Common commands ===
--
  (((
--They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.5.4, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
++These are available for each sensors and include actions 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]]s.
  )))
++=== 3.4.2 Sensor-related commands ===
--=== 3.4.2 Sensor related commands ===
++These commands are specially designed for the LT-22222-L. Commands can be sent to the device using options such as an AT command or a LoRaWAN downlink payload.
++
  ==== 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:**
++(% border="2" style="width:500px" %)
++|**Command**|AT+TDC=<time>
++|**Response**|
++|**Parameters**|**time** : uplink interval is in milliseconds
++|**Example**|(((
++AT+TDC=30000
--(% style="color:blue" %)**AT+TDC=N **
++Sets the uplink interval to 30,000 milliseconds (30 seconds)
++)))
++(% style="color:#037691" %)**Downlink payload**
--**Example: **AT+TDC=30000. Means set interval to 30 seconds
++(% border="2" style="width:500px" %)
++|**Payload**|(((
++<prefix><time>
++)))
++|**Parameters**|(((
++**prefix** : 0x01
++**time** : uplink interval is in milliseconds, represented by 3  bytes in hexadecimal.
++)))
++|**Example**|(((
++01 **00 75 30**
--* (% style="color:#037691" %)**Downlink Payload (prefix 0x01):**
++Sets the uplink interval to 30,000 milliseconds (30 seconds)
--(% style="color:blue" %)**0x01 aa bb cc  **(%%)**   ~/~/ Same as AT+TDC=0x(aa bb cc)**
++Conversion: 30000 (dec) = 00 75 30 (hex)
++See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]]
++)))
++==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
--==== 3.4.2.2 Set Work Mode (AT+MOD) ====
++Sets the working mode.
++(% style="color:#037691" %)**AT command**
--Set work mode.
++(% border="2" style="width:500px" %)
++|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE=<working_mode>
++|(% style="width:97px" %)**Response**|(% style="width:413px" %)
++|(% style="width:97px" %)**Parameters**|(% style="width:413px" %)(((
++**working_mode** :
--* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+MOD=N  **
++1 = (Default mode/factory set):  2ACI + 2AVI + DI + DO + RO
--**Example**: AT+MOD=2. Set work mode to Double DI counting mode
++2 = Double DI Counting + DO + RO
--* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A):**
++3 = Single DI Counting + 2 x ACI + DO + RO
--(% style="color:blue" %)**0x0A aa  **(%%)**  ** ~/~/ Same as AT+MOD=aa
++4 = Single DI Counting + 1 x Voltage Counting + DO + RO
++5 = Single DI Counting + 2 x AVI + 1 x ACI + DO + RO
++6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5
++)))
++|(% style="width:97px" %)**Example**|(% style="width:413px" %)(((
++AT+MOD=2
--==== 3.4.2.3 Poll an uplink ====
++Sets the device to working mode 2 (Double DI Counting + DO + RO)
++)))
++(% class="wikigeneratedid" %)
++(% style="color:#037691" %)**Downlink payload**
--* (% style="color:#037691" %)**AT Command:**(%%) There is no AT Command to poll uplink
++(% border="2" style="width:500px" %)
++|(% style="width:98px" %)**Payload**|(% style="width:400px" %)<prefix><working_mode>
++|(% style="width:98px" %)**Parameters**|(% style="width:400px" %)(((
++**prefix** : 0x0A
--* (% style="color:#037691" %)**Downlink Payload (prefix 0x08):**
++**working_mode** : Working mode, represented by 1 byte in hexadecimal.
++)))
++|(% style="width:98px" %)**Example**|(% style="width:400px" %)(((
++0A **02**
--(% style="color:blue" %)**0x08 FF  **(%%)**   **~/~/ Poll an uplink
++Sets the device to working mode 2 (Double DI Counting + DO + RO)
++)))
--**Example**: 0x08FF, ask device to send an Uplink
++==== 3.4.2.3 Poll an uplink ====
++Requests an uplink from LT-22222-L.
++(% style="color:#037691" %)**AT command**
--==== 3.4.2.4 Enable Trigger Mode ====
++There is no AT Command to request an uplink from LT-22222-L
++(% style="color:#037691" %)**Downlink payload**
--Use of trigger mode, please check [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
++(% border="2" style="width:500px" %)
++|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF
++|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08
++|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
++08 FF
--* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0**
++Requests an uplink from LT-22222-L.
++)))
--(% style="color:red" %)**1:** (%%)Enable Trigger Mode
++==== 3.4.2.4 Enable/Disable Trigger Mode ====
--(% style="color:red" %)**0: **(%%)Disable Trigger Mode
++Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
++(% style="color:#037691" %)**AT Command**
--* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A 06):**
++(% border="2" style="width:500px" %)
++|(% style="width:95px" %)**Command**|(% style="width:403px" %)AT+ADDMOD6=<enable/disable trigger_mode>
++|(% style="width:95px" %)**Response**|(% style="width:403px" %)
++|(% style="width:95px" %)**Parameters**|(% style="width:403px" %)(((
++**enable/disable trigger_mode** :
--(% style="color:blue" %)**0x0A 06 aa    **(%%)    ~/~/ Same as AT+ADDMOD6=aa
++1 = enable trigger mode
++0 = disable trigger mode
++)))
++|(% style="width:95px" %)**Example**|(% style="width:403px" %)(((
++AT+ADDMOD6=1
++Enable trigger mode for the current working mode
++)))
--==== 3.4.2.5 Poll trigger settings ====
++(% style="color:#037691" %)**Downlink payload**
++(% border="2" style="width:500px" %)
++|(% style="width:97px" %)**Payload**|(% style="width:401px" %)<prefix><enable/disable trigger_mode>
++|(% style="width:97px" %)**Parameters**|(% style="width:401px" %)(((
++**prefix** : 0x0A 06 (two bytes in hexadecimal)
--Poll trigger settings
++**working mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
++)))
++|(% style="width:97px" %)**Example**|(% style="width:401px" %)(((
++0A 06 **01**
--* (% style="color:#037691" %)**AT Command:**
++Enable trigger mode for the current working mode
++)))
++==== 3.4.2.5 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):**
++(% style="color:#037691" %)**Downlink Payload**
--(% style="color:blue" %)**0xAB 06  **  (%%)   ~/~/ Poll trigger settings, device will uplink trigger settings once receive this command
++(% border="2" style="width:500px" %)
++|(% style="width:95px" %)**Payload**|(% style="width:403px" %)<prefix>
++|(% style="width:95px" %)**Parameters**|(% style="width:403px" %)**prefix **: AB 06 (two bytes in hexadecimal)
++|(% style="width:95px" %)**Example**|(% style="width:403px" %)(((
++AB 06
++Uplinks the trigger settings.
++)))
++==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ====
--==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ====
++Enable or disable DI1/DI2/DI3 as a trigger.
++(% style="color:#037691" %)**AT Command**
--Enable Disable DI1/DI2/DI2 as trigger,
++(% border="2" style="width:500px" %)
++|(% style="width:98px" %)**Command**|(% style="width:400px" %)AT+DTRI=<DI1_trigger>,<DI2_trigger>
++|(% style="width:98px" %)**Response**|(% style="width:400px" %)
++|(% style="width:98px" %)**Parameters**|(% style="width:400px" %)(((
++**DI1_trigger:**
--* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
++1 = enable DI1 trigger
--**Example:** AT+ DTRI =1,0   (Enable DI1 trigger / disable DI2 trigger)
++0 = disable DI1 trigger
++**DI2 _trigger**
--* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 02):**
++1 = enable DI2 trigger
--(% style="color:blue" %)**0xAA 02 aa bb   **  (%%) ~/~/ Same as AT+DTRI=aa,bb
++0 = disable DI2 trigger
++)))
++|(% style="width:98px" %)**Example**|(% style="width:400px" %)(((
++AT+DTRI=1,0
++Enable DI1 trigger, disable DI2 trigger
++)))
++(% class="wikigeneratedid" %)
++(% style="color:#037691" %)**Downlink Payload**
--==== 3.4.2.7 Trigger1 – Set DI1 or DI3 as trigger ====
++(% border="2" style="width:500px" %)
++|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix><DI1_trigger><DI2_trigger>
++|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)(((
++**prefix :** AA 02 (two bytes in hexadecimal)
++**DI1_trigger:**
--Set DI1 or DI3(for LT-33222-L) trigger.
++1 = enable DI1 trigger, represented by 1 byte in hexadecimal.
--* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG1=a,b**
++0 = disable DI1 trigger, represented by 1 byte in hexadecimal.
--(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
++**DI2 _trigger**
--(% style="color:red" %)**b :** (%%)delay timing.
++1 = enable DI2 trigger, represented by 1 byte in hexadecimal.
--**Example:** AT+TRIG1=1,100(set DI1 port to trigger on high level, valid signal is 100ms )
++0 = disable DI2 trigger, represented by 1 byte in hexadecimal.
++)))
++|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
++AA 02 **01 00**
++Enable DI1 trigger, disable DI2 trigger
++)))
--* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 01 ):**
++==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ====
--(% style="color:blue" %)**0x09 01 aa bb cc    ** (%%)    ~/~/ same as AT+TRIG1=aa,0x(bb cc)
++Sets DI1 or DI3 (for LT-33222-L) as a trigger.
++(% style="color:#037691" %)**AT Command**
--==== 3.4.2.8 Trigger2 – Set DI2 as trigger ====
++(% border="2" style="width:500px" %)
++|(% style="width:101px" %)**Command**|(% style="width:397px" %)AT+TRIG1=<interrupt_mode>,<minimum_signal_duration>
++|(% style="width:101px" %)**Response**|(% style="width:397px" %)
++|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)(((
++**interrupt_mode** :  0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
++**minimum_signal_duration** : the **minimum signal duration** required for the DI1 port to recognize a valid trigger.
++)))
++|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
++AT+TRIG1=1,100
--Set DI2 trigger.
++Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms.
++)))
--* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b**
++(% class="wikigeneratedid" %)
++(% style="color:#037691" %)**Downlink Payload**
--(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
++(% border="2" style="width:500px" %)
++|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix><interrupt_mode><minimum_signal_duration>
++|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)(((
++**prefix** : 09 01 (hexadecimal)
--(% style="color:red" %)**b :** (%%)delay timing.
++**interrupt_mode** : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal.
--**Example:** AT+TRIG2=0,100(set DI1 port to trigger on low level, valid signal is 100ms )
++**minimum_signal_duration** : in milliseconds, represented two bytes in hexadecimal.
++)))
++|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
++09 01 **01 00 64**
++Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms.
++)))
--* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 02 ):**
++==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
--(% style="color:blue" %)**0x09 02 aa bb cc   **  (%%)~/~/ same as AT+TRIG2=aa,0x(bb cc)
++Sets DI2 as a trigger.
++(% style="color:#037691" %)**AT Command**
--==== 3.4.2.9 Trigger – Set AC (current) as trigger ====
++(% border="2" style="width:500px" %)
++|(% style="width:94px" %)**Command**|(% style="width:404px" %)AT+TRIG2=<interrupt_mode>,<minimum_signal_duration>
++|(% style="width:94px" %)**Response**|(% style="width:404px" %)
++|(% style="width:94px" %)**Parameters**|(% style="width:404px" %)(((
++**interrupt_mode **:  0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
++**minimum_signal_duration** : the **minimum signal duration** required for the DI1 port to recognize a valid trigger.
++)))
++|(% style="width:94px" %)**Example**|(% style="width:404px" %)(((
++AT+TRIG2=0,100
--Set current trigger , base on AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
++Set the DI1 port to trigger on a falling edge; the valid signal duration is 100 ms.
++)))
--* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ACLIM**
++(% style="color:#037691" %)**Downlink Payload**
--* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 01 )**
++(% border="2" style="width:500px" %)
++|(% style="width:96px" %)**Payload**|(% style="width:402px" %)<prefix><interrupt_mode><minimum_signal_duration>
++|(% style="width:96px" %)**Parameters**|(% style="width:402px" %)(((
++**prefix** : 09 02 (hexadecimal)
--(% 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"]]
++**interrupt_mode **: 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal.
++**minimum_signal_duration** : in milliseconds, represented two bytes in hexadecimal
++)))
++|(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64**
++
++==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
++
++Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
++
++(% style="color:#037691" %)**AT Command**
++
++(% border="2" style="width:500px" %)
++|(% style="width:104px" %)**Command**|(% style="width:394px" %)(((
++AT+ACLIM=<AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH>
++)))
++|(% style="width:104px" %)**Response**|(% style="width:394px" %)
++|(% style="width:104px" %)**Parameters**|(% style="width:394px" %)(((
++**AC1_LIMIT_LOW** : lower limit of the current to be checked
++
++**AC1_LIMIT_HIGH **: higher limit of the current to be checked
++
++**AC2_LIMIT_HIGH **: lower limit of the current to be checked
++
++**AC2_LIMIT_LOW** : higher limit of the current to be checked
++)))
++|(% style="width:104px" %)**Example**|(% style="width:394px" %)(((
++AT+ACLIM=10000,15000,0,0
++
++Triggers an uplink if AC1 current is lower than 10mA or higher than 15mA
++)))
++|(% style="width:104px" %)Note|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
++
++(% style="color:#037691" %)**Downlink Payload**
++
++(% border="2" style="width:500px" %)
++|(% style="width:104px" %)**Payload**|(% style="width:394px" %)<prefix><AC1_LIMIT_LOW>,< AC1_LIMIT_HIGH>,<AC2_LIMIT_LOW>,< AC2_LIMIT_HIGH>
++|(% style="width:104px" %)**Parameters**|(% style="width:394px" %)(((
++**prefix **: AA 01 (hexadecimal)
++
++**AC1_LIMIT_LOW** : lower limit of the current to be checked, two bytes in hexadecimal
++
++**AC1_LIMIT_HIGH **: higher limit of the current to be checked, two bytes in hexadecimal
++
++**AC2_LIMIT_HIGH **: lower limit of the current to be checked, two bytes in hexadecimal
++
++**AC2_LIMIT_LOW** : higher limit of the current to be checked, two bytes in hexadecimal
++)))
++|(% style="width:104px" %)**Example**|(% style="width:394px" %)(((
++AA 01 **27** **10 3A** **98** 00 00 00 00
++
++Triggers an uplink if AC1 current is lower than 10mA or higher than 15mA. Set all values to zero for AC2 limits because we are only checking AC1 limits.
++)))
++|(% style="width:104px" %)Note|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
++
  ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
++Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--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"]]**
++(% border="2" style="width:500px" %)
++|(% style="width:104px" %)**Command**|(% style="width:387px" %)AT+AVLIM= AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH>
++|(% style="width:104px" %)**Response**|(% style="width:387px" %)
++|(% style="width:104px" %)**Parameters**|(% style="width:387px" %)(((
++**AC1_LIMIT_LOW** : lower limit of the current to be checked
--* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 00 )**
++**AC1_LIMIT_HIGH **: higher limit of the current to be checked
--(% 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"]]
++**AC2_LIMIT_HIGH **: lower limit of the current to be checked
++**AC2_LIMIT_LOW** : higher limit of the current to be checked
++)))
++|(% style="width:104px" %)**Example**|(% style="width:387px" %)(((
++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
++)))
++|(% style="width:104px" %)**Note**|(% style="width:387px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--==== 3.4.2.11 Trigger – Set minimum interval ====
++(% style="color:#037691" %)**Downlink Payload**
++(% border="2" style="width:500px" %)
++|(% style="width:104px" %)**Payload**|(% style="width:394px" %)<prefix><AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH>
++|(% style="width:104px" %)**Parameters**|(% style="width:394px" %)(((
++**prefix **: AA 00 (hexadecimal)
--Set AV and AC trigger minimum interval, system won't response to the second trigger within this set time after the first trigger.
++**AV1_LIMIT_LOW** : lower limit of the voltage to be checked, two bytes in hexadecimal
--* (% 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.
++**AV1_LIMIT_HIGH **: higher limit of the voltage to be checked, two bytes in hexadecimal
--* (% style="color:#037691" %)**Downlink Payload (prefix 0xAC )**
++**AV2_LIMIT_HIGH **: lower limit of the voltage to be checked, two bytes in hexadecimal
--(% style="color:blue" %)**0x AC aa bb   **(%%) ~/~/ same as AT+ATDC=0x(aa bb)   . Unit (min)
++**AV2_LIMIT_LOW** : higher limit of the voltage to be checked, two bytes in hexadecimal
++)))
++|(% style="width:104px" %)**Example**|(% style="width:394px" %)(((
++AA 00 **0B B8 17 70 00 00 07 D0**
--(((
--(% style="color:red" %)**Note: ATDC setting must be more than 5min**
++Triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V.
  )))
++|(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
++==== 3.4.2.11 Trigger – Set minimum interval ====
++Sets the AV and AC trigger minimum interval. The device won't respond to a second trigger within this set time after the first trigger.
++(% style="color:#037691" %)**AT Command**
++
++(% border="2" style="width:500px" %)
++|(% style="width:113px" %)**Command**|(% style="width:385px" %)AT+ATDC=<time>
++|(% style="width:113px" %)**Response**|(% style="width:385px" %)
++|(% style="width:113px" %)**Parameters**|(% style="width:385px" %)(((
++**time** : in minutes
++)))
++|(% style="width:113px" %)**Example**|(% style="width:385px" %)(((
++AT+ATDC=5
++
++The device won't respond to the second trigger within 5 minutes after the first trigger.
++)))
++|(% style="width:113px" %)Note|(% style="width:385px" %)(% style="color:red" %)**The time must be greater than 5 minutes.**
++
++(% style="color:#037691" %)**Downlink Payload**
++
++(% border="2" style="width:500px" %)
++|(% style="width:112px" %)**Payload**|(% style="width:386px" %)<prefix><time>
++|(% style="width:112px" %)**Parameters**|(% style="width:386px" %)(((
++**prefix** : AC (hexadecimal)
++
++**time **: in minutes (two bytes in hexadecimal)
++)))
++|(% style="width:112px" %)**Example**|(% style="width:386px" %)(((
++AC **00 05**
++
++The device won't respond to the second trigger within 5 minutes after the first trigger.
++)))
++|(% style="width:112px" %)Note|(% style="width:386px" %)(% style="color:red" %)**The time must be greater than 5 minutes.**
++
  ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
++Controls the digital outputs DO1, DO2, and DO3
--* (% style="color:#037691" %)**AT Command**
++(% style="color:#037691" %)**AT Command**
--There is no AT Command to control Digital Output
++There is no AT Command to control the Digital Output.
--* (% style="color:#037691" %)**Downlink Payload (prefix 0x02)**
++(% style="color:#037691" %)**Downlink Payload**
--(% style="color:blue" %)**0x02 aa bb cc     ** (%%)~/~/ Set DO1/DO2/DO3 output
++(% border="2" style="width:500px" %)
++|(% style="width:115px" %)**Payload**|(% style="width:383px" %)<prefix><DO1><DO2><DO3>
++|(% style="width:115px" %)**Parameters**|(% style="width:383px" %)(((
++**prefix** : 02 (hexadecimal)
--(((
--If payload = 0x02010001, while there is load between V+ and DOx, it means set DO1 to low, DO2 to high and DO3 to low.
++**DOI** : 01: Low,  00: High, 11: No action (1 byte in hex)
++
++**DO2** : 01: Low,  00: High, 11: No action (1 byte in hex)
++
++**DO3 **: 01: Low,  00: High, 11: No action (1 byte in hex)
  )))
++|(% style="width:115px" %)**Examples**|(% style="width:383px" %)(((
++02 **01 00 01**
++If there is a load between V+ and DOx, it means DO1 is set to low, DO2 is set to high, and DO3 is set to low.
++
++**More examples:**
++
  (((
--01: Low,  00: High ,  11: No action
++01: 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**
@@ -1048,12 +1048,15 @@
  )))
  (((
--(% style="color:red" %)**Note: For LT-22222-L, there is no DO3, the last byte can use any value.**
++(((
++(% style="color:red" %)**Note: For the LT-22222-L, there is no DO3; the last byte can have any value.**
  )))
  (((
--(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
++(% style="color:red" %)**The device will upload a packet if downlink code executes successfully.**
  )))
++)))
++)))
@@ -1081,7 +1081,7 @@
 : DO pins will change to an inverter state after timeout
--(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Ports status:
++(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
  (% 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**
@@ -1089,7 +1089,7 @@
  |0x00|DO1 set to high
  |0x11|DO1 NO Action
--(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Ports status:
++(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:
  (% 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**
@@ -1097,7 +1097,7 @@
  |0x00|DO2 set to high
  |0x11|DO2 NO Action
--(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Ports status:
++(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:
  (% 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**
@@ -1105,16 +1105,16 @@
  |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, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)
  (% style="color:red" %)**Note: **
--   Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes
++   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.
++   Before firmware v1.6.0, the latch time only supported 2 bytes.
--(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
++(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
  **Example payload:**
@@ -1121,22 +1121,21 @@
  **~1. A9 01 01 01 01 07 D0**
--DO1 pin & DO2 pin & DO3 pin will be set to Low, last 2 seconds, then change back to original state.
++DO1 pin, DO2 pin, and DO3 pin will be set to low, last for 2 seconds, and then revert to their original state.
  **2. A9 01 00 01 11 07 D0**
--DO1 pin set high, DO2 pin set low, DO3 pin no action, last 2 seconds, then change back to original state.
++DO1 pin is set to high, DO2 pin is set to low, and DO3 pin takes no action. This lasts for 2 seconds and then reverts to the original state.
  **3. A9 00 00 00 00 07 D0**
--DO1 pin & DO2 pin & DO3 pin will be set to high, last 2 seconds, then both change to low.
++DO1 pin, DO2 pin, and DO3 pin will be set to high, last for 2 seconds, and then all change to low.
  **4. A9 00 11 01 00 07 D0**
--DO1 pin no action, DO2 pin set low, DO3 pin set high, last 2 seconds, then DO1 pin no action, DO2 pin set high, DO3 pin set low
++DO1 pin takes no action, DO2 pin is set to low, and DO3 pin is set to high. This lasts for 2 seconds, after which DO1 pin takes no action, DO2 pin is set to high, and DO3 pin is set to low.
--
  ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
@@ -1151,11 +1151,11 @@
  (((
--If payload = 0x030100, it means set RO1 to close and RO2 to open.
++If payload is 0x030100, it means setting RO1 to close and RO2 to open.
  )))
  (((
--01: Close ,  00: Open , 11: No action
++00: Close ,  01: Open , 11: No action
  (% 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**
@@ -1172,9 +1172,9 @@
  (% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
--
  ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
++Controls the relay output time.
  * (% style="color:#037691" %)**AT Command:**
@@ -1186,15 +1186,15 @@
  (% 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:
++This is to control the relay output time. It includes four bytes:
  (% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
  (% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
--01: Relays will change back to original state after timeout.
++01: Relays will change back to their original state after timeout.
--00: Relays will change to an inverter state after timeout
++00: Relays will change to the inverter state after timeout.
  (% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
@@ -1207,12 +1207,12 @@
  (% style="color:red" %)**Note:**
--   Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes
++   Since firmware v1.6.0, the latch time supports both 4 bytes and 2 bytes.
--   Before Firmwre v1.6.0 the latch time only suport 2 bytes.
++   Before firmware v1.6.0, the latch time only supported 2 bytes.
--(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
++(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
  **Example payload:**
@@ -1219,19 +1219,19 @@
  **~1. 05 01 11 07 D0**
--Relay1 and Relay 2 will be set to NC , last 2 seconds, then change back to original state.
++Relay1 and Relay2 will be set to NC, lasting 2 seconds, then revert to their original state
  **2. 05 01 10 07 D0**
--Relay1 will change to NC, Relay2 will change to NO, last 2 seconds, then both change back to original state.
++Relay1 will change to NC, Relay2 will change to NO, lasting 2 seconds, then both will revert to their original state.
  **3. 05 00 01 07 D0**
--Relay1 will change to NO, Relay2 will change to NC, last 2 seconds, then relay change to NC,Relay2 change to NO.
++Relay1 will change to NO, Relay2 will change to NC, lasting 2 seconds, then Relay1 will change to NC, and Relay2 will change to NO.
  **4. 05 00 00 07 D0**
--Relay 1 & relay2 will change to NO, last 2 seconds, then both change to NC.
++Relay1 and Relay2 will change to NO, lasting 2 seconds, then both will change to NC.
@@ -1238,7 +1238,7 @@
  ==== 3.4.2.16 Counting ~-~- Voltage threshold counting ====
--When voltage exceed the threshold, count. Feature see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
++When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX   ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
@@ -1247,15 +1247,76 @@
  (% style="color:blue" %)**0xA5 aa bb cc   ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc
++(% style="color:#037691" %)**AT Command**
++(% border="2" style="width:500px" %)
++|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage><logic>
++|(% style="width:137px" %)**Response**|(% style="width:361px" %)
++|(% style="width:137px" %)**Parameters**|(% style="width:361px" %)(((
++**voltage** : voltage threshold in mV
++
++**logic**:
++
++0 : lower than
++
++1: higher than
++
++if you leave logic parameter blank, it is considered 0
++)))
++|(% style="width:137px" %)**Examples**|(% style="width:361px" %)(((
++AT+VOLMAX=20000
++
++If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
++
++AT+VOLMAX=20000,0
++
++If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1
++
++AT+VOLMAX=20000,1
++
++If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
++)))
++
++(% style="color:#037691" %)**Downlink Payload**
++
++(% border="2" style="width:500px" %)
++|(% style="width:140px" %)**Payload**|(% style="width:358px" %)<prefix><voltage><logic>
++|(% style="width:140px" %)**Parameters**|(% style="width:358px" %)(((
++**prefix** : A5 (hex)
++
++**voltage** : voltage threshold in mV (2 bytes in hex)
++
++**logic**: (1 byte in hexadecimal)
++
++0 : lower than
++
++1: higher than
++
++if you leave logic parameter blank, it is considered 1 (higher than)
++)))
++|(% style="width:140px" %)**Example**|(% style="width:358px" %)(((
++A5 **4E 20**
++
++If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
++
++A5 **4E 20 00**
++
++If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1
++
++A5 **4E 20 01**
++
++If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
++)))
++
  ==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ====
++This command allows users to pre-configure specific count numbers for various counting parameters such as Count1, Count2, or AVI1 Count. Use the AT command to set the desired count number for each configuration.
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) **
  (% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count
--(% style="color:red" %)**bb cc dd ee: **(%%)number to be set
++(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):**
@@ -1263,12 +1263,55 @@
  (% style="color:blue" %)**0x A8 aa bb cc dd ee     ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee)
++(% style="color:#037691" %)**AT Command**
--==== 3.4.2.18 Counting ~-~- Clear Counting ====
++(% border="2" style="width:500px" %)
++|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter><number>
++|(% style="width:134px" %)**Response**|(% style="width:364px" %)
++|(% style="width:134px" %)**Parameters**|(% style="width:364px" %)(((
++**counting_parameter** :
++1: COUNT1
--Clear counting for counting mode
++2: COUNT2
++3: AVI1 Count
++
++**number** : Start number
++)))
++|(% style="width:134px" %)**Example**|(% style="width:364px" %)(((
++AT+SETCNT=1,10
++
++Sets the COUNT1 to 10.
++)))
++
++(% style="color:#037691" %)**Downlink Payload**
++
++(% border="2" style="width:500px" %)
++|(% style="width:135px" %)**Payload**|(% style="width:363px" %)<prefix><counting_parameter><number>
++|(% style="width:135px" %)**Parameters**|(% style="width:363px" %)(((
++prefix : A8 (hex)
++
++**counting_parameter** :  (1 byte in hexadecimal)
++
++1: COUNT1
++
++2: COUNT2
++
++3: AVI1 Count
++
++**number** : Start number, 4 bytes in hexadecimal
++)))
++|(% style="width:135px" %)**Example**|(% style="width:363px" %)(((
++A8 **01 00 00 00 0A**
++
++Sets the COUNT1 to 10.
++)))
++
++==== 3.4.2.18 Counting ~-~- Clear Counting ====
++
++This command clears the counting in counting mode.
++
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT         **(%%) ~/~/ clear all counting
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):**
@@ -1275,14 +1275,30 @@
  (% style="color:blue" %)**0x A6 01    ** (%%)~/~/ clear all counting
++(% style="color:#037691" %)**AT Command**
++(% border="2" style="width:500px" %)
++|(% style="width:142px" %)**Command**|(% style="width:356px" %)AT+CLRCOUNT
++|(% style="width:142px" %)**Response**|(% style="width:356px" %)-
--==== 3.4.2.19 Counting ~-~- Change counting mode save time ====
++(% style="color:#037691" %)**Downlink Payload**
++(% border="2" style="width:500px" %)
++|(% style="width:141px" %)**Payload**|(% style="width:357px" %)<prefix><clear?>
++|(% style="width:141px" %)**Parameters**|(% style="width:357px" %)(((
++prefix : A6 (hex)
++clear? : 01 (hex)
++)))
++|(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
++
++==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
++
++This command allows you to configure the device to save its counting result to internal flash memory at specified intervals. By setting a save time, the device will periodically store the counting data to prevent loss in case of power failure. The save interval can be adjusted to suit your requirements, with a minimum value of 30 seconds.
++
  * (% style="color:#037691" %)**AT Command:**
--(% 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:blue" %)**AT+COUTIME=60  **(%%)~/~/ Sets the save time to 60 seconds. The device will save the counting result in internal flash every 60 seconds. (Min value: 30 seconds)
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):**
@@ -1290,19 +1290,46 @@
  (% style="color:blue" %)**0x A7 aa bb cc     ** (%%)~/~/ same as AT+COUTIME =aa bb cc,
  (((
--range: aa bb cc:0 to 16777215,  (unit:second)
++Range: aa bb cc:0 to 16777215,  (unit: seconds)
  )))
++(% style="color:#037691" %)**AT Command**
++(% border="2" style="width:500px" %)
++|(% style="width:124px" %)**Command**|(% style="width:374px" %)AT+COUTIME=<time>
++|(% style="width:124px" %)**Response**|(% style="width:374px" %)
++|(% style="width:124px" %)**Parameters**|(% style="width:374px" %)time : seconds (0 to 16777215)
++|(% style="width:124px" %)**Example**|(% style="width:374px" %)(((
++AT+COUTIME=60
++
++Sets the device to save its counting results to the memory every 60 seconds.
++)))
++
++(% style="color:#037691" %)**Downlink Payload**
++
++(% border="2" style="width:500px" %)
++|(% style="width:123px" %)**Payload**|(% style="width:375px" %)<prefix><time>
++|(% style="width:123px" %)**Parameters**|(% style="width:375px" %)(((
++prefix : A7
++
++time : seconds, 3 bytes in hexadecimal
++)))
++|(% style="width:123px" %)**Example**|(% style="width:375px" %)(((
++A7 **00 00 3C**
++
++Sets the device to save its counting results to the memory every 60 seconds.
++)))
++
  ==== 3.4.2.20 Reset save RO DO state ====
++This command allows you to reset the saved relay output (RO) and digital output (DO) states when the device joins the network. By configuring this setting, you can control whether the device should retain or reset the relay states after a reset and rejoin to the network.
  * (% style="color:#037691" %)**AT Command:**
  (% style="color:blue" %)**AT+RODORESET=1    **(%%)~/~/ RODO will close when the device joining the network. (default)
--(% 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:blue" %)**AT+RODORESET=0    **(%%)~/~/ After the device is reset, the previously saved RODO state (only MOD2 to MOD5) is read, and its state will not change when the device reconnects to the network.
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):**
@@ -1310,9 +1310,50 @@
  (% style="color:blue" %)**0x AD aa      ** (%%)~/~/ same as AT+RODORET =aa
++(% border="2" style="width:500px" %)
++|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state>
++|(% style="width:127px" %)**Response**|(% style="width:371px" %)
++|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
++**state** :
++**0** : RODO will close when the device joins the network. (default)
++
++**1**: After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network.
++)))
++|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
++(% style="color:blue" %)**AT+RODORESET=1 **
++
++RODO will close when the device joins the network. (default)
++
++(% style="color:blue" %)**AT+RODORESET=0 **
++
++After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network.
++)))
++
++(% border="2" style="width:500px" %)
++|(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state>
++|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
++**prefix** : AD
++
++**state** :
++
++**0** : RODO will close when the device joins the network. (default), represents as 1 byte in hexadecimal.
++
++**1**: After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network. - represents as 1 byte in hexadecimal
++)))
++|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
++AD **01**
++
++RODO will close when the device joins the network. (default)
++
++AD **00**
++
++After the device is reset, the previously saved RODO state (limited to MOD2 to MOD5) is read, and it will not change when the device reconnects to the network.
++)))
++
  ==== 3.4.2.21 Encrypted payload ====
++This command allows you to configure whether the device should upload data in an encrypted format or in plaintext. By default, the device encrypts the payload before uploading. You can toggle this setting to either upload encrypted data or transmit it without encryption.
  * (% style="color:#037691" %)**AT Command:**
@@ -1321,21 +1321,67 @@
  (% style="color:blue" %)**AT+DECRYPT=0    **(%%)~/~/  Encrypt when uploading payload (default)
++(% border="2" style="width:500px" %)
++|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state>
++|(% style="width:127px" %)**Response**|(% style="width:371px" %)
++|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
++state :
++1 : The payload is uploaded without encryption
++
++0 : The payload is encrypted when uploaded (default)
++)))
++|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
++AT+DECRYPT=1
++
++The payload is uploaded without encryption
++
++AT+DECRYPT=0
++
++The payload is encrypted when uploaded (default)
++)))
++
++There is no downlink payload for this configuration.
++
++
  ==== 3.4.2.22 Get sensor value ====
++This command allows you to retrieve and optionally uplink sensor readings through the serial port.
  * (% style="color:#037691" %)**AT Command:**
--(% style="color:blue" %)**AT+GETSENSORVALUE=0    **(%%)~/~/ The serial port gets the reading of the current sensor
++(% style="color:blue" %)**AT+GETSENSORVALUE=0    **(%%)~/~/ The serial port retrieves the reading of the current sensor.
--(% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port gets the current sensor reading and uploads it.
++(% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it.
++(% border="2" style="width:500px" %)
++|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state>
++|(% style="width:127px" %)**Response**|(% style="width:371px" %)
++|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
++**state** :
--==== 3.4.2.23 Resets the downlink packet count ====
++**0 **: Retrieves the current sensor reading via the serial port.
++**1 **: Retrieves and uploads the current sensor reading via the serial port.
++)))
++|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
++AT+GETSENSORVALUE=0
++Retrieves the current sensor reading via the serial port.
++
++AT+GETSENSORVALUE=1
++
++Retrieves and uplinks the current sensor reading via the serial port.
++)))
++
++There is no downlink payload for this configuration.
++
++
++==== 3.4.2.23 Resetting the downlink packet count ====
++
++This command manages how the node handles mismatched downlink packet counts. It offers two modes: one disables the reception of further downlink packets if discrepancies occur, while the other resets the downlink packet count to align with the server, ensuring continued communication.
++
  * (% style="color:#037691" %)**AT Command:**
  (% 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)
@@ -1343,10 +1343,37 @@
  (% 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.
++(% border="2" style="width:500px" %)
++|(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state>
++|(% style="width:130px" %)**Response**|(% style="width:368px" %)(((
++
++)))
++|(% style="width:130px" %)**Parameters**|(% style="width:368px" %)(((
++**state **:
++**0** : When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node stops receiving further downlink packets (default).
++
++
++**1** : When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node resets its downlink packet count to match the server's, ensuring consistency.
++)))
++|(% style="width:130px" %)**Example**|(% style="width:368px" %)(((
++AT+DISFCNTCHECK=0
++
++When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node stops receiving further downlink packets (default).
++
++AT+DISFCNTCHECK=1
++
++When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node resets its downlink packet count to match the server's, ensuring consistency.
++)))
++
++There is no downlink payload for this configuration.
++
++
  ==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ====
++This command controls the behavior of the node when the combined size of the MAC commands (MACANS) from the server and the payload exceeds the allowed byte limit for the current data rate (DR). The command provides two modes: one enables splitting the data into batches to ensure compliance with the byte limit, while the other prioritizes the payload and ignores the MACANS in cases of overflow.
++
  * (% style="color:#037691" %)**AT Command:**
  (% 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)
@@ -1358,10 +1358,50 @@
  (% style="color:blue" %)**0x21 00 01 **   (%%)      ~/~/ Set  the DISMACANS=1
++(% style="color:#037691" %)**AT Command**
++(% border="2" style="width:500px" %)
++|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DISMACANS=<state>
++|(% style="width:127px" %)**Response**|(% style="width:371px" %)
++|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
++**state** :
++**0** : When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default)
++
++**1** : When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload.
++)))
++|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
++AT+DISMACANS=0
++
++When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default)
++
++AT+DISMACANS=1
++
++When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload.
++)))
++
++(% style="color:#037691" %)**Downlink Payload**
++
++(% border="2" style="width:500px" %)
++|(% style="width:126px" %)**Payload**|(% style="width:372px" %)<prefix><state>
++|(% style="width:126px" %)**Parameters**|(% style="width:372px" %)(((
++**prefix** : 21
++
++**state** : (2 bytes in hexadecimal)
++
++**0** : When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default)
++
++**1 **: When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload.
++)))
++|(% style="width:126px" %)**Example**|(% style="width:372px" %)(((
++21 **00 01**
++
++Set DISMACANS=1
++)))
++
  ==== 3.4.2.25 Copy downlink to uplink ====
++This command enables the device to immediately uplink the content of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100.
  * (% style="color:#037691" %)**AT Command**(%%)**:**
@@ -1374,8 +1374,22 @@
  For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
++(% border="2" style="width:500px" %)
++|(% style="width:122px" %)**Command**|(% style="width:376px" %)(((
++AT+RPL=5
++After receiving a downlink packet from the server, the node immediately uplinks the content of the packet back to the server using port number 100.
++)))
++|(% style="width:122px" %)**Example**|(% style="width:376px" %)(((
++Downlink:
++01 00 02 58
++
++Uplink:
++
++01 01 00 02 58
++)))
++
  [[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.
@@ -1382,14 +1382,16 @@
--==== 3.4.2.26 Query version number and frequency band 、TDC ====
++==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
++This command is used to query key information about the device, including its firmware version, frequency band, sub band, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device.
  * (((
  (% style="color:#037691" %)**Downlink Payload**(%%)**:**
--(% style="color:blue" %)**26 01  ** (%%)  ~/~/  Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.
++(% style="color:blue" %)**26 01  ** (%%)  ~/~/  The downlink payload 26 01 is used to query the device's firmware version, frequency band, sub band, and TDC time.
++
  )))
@@ -1398,74 +1398,152 @@
  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173929-8.png?width=1205&height=76&rev=1.1||alt="image-20220823173929-8.png"]]
--== 3.5 Integrate with Mydevice ==
++== 3.5 Integrating with ThingsEye.io ==
++The Things Stack application supports integration with ThingsEye.io. Once integrated, ThingsEye.io acts as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
--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:
++=== 3.5.1 Configuring The Things Stack ===
--(((
--(% style="color:blue" %)**Step 1**(%%): Be sure that your device is programmed and properly connected to the network at this time.
--)))
++We use The Things Stack Sandbox in this example:
--(((
--(% 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:
++* In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
++* Select **MQTT** under **Integrations** in the left menu.
++* In the **Connection information **section, under **Connection credentials**, The Things Stack displays an auto-generated **username**. You can use it or provide a new one.
++* Click the **Generate new API key** button to generate a password. You can view it by clicking on the **visibility toggle/eye** icon. The API key works as the password.
--
--)))
++{{info}}
++The username and  password (API key) you created here are required in the next section.
++{{/info}}
--[[image:image-20220719105525-1.png||height="377" width="677"]]
++[[image:tts-mqtt-integration.png||height="625" width="1000"]]
++=== 3.5.2 Configuring ThingsEye.io ===
++The ThingsEye.io IoT platform is not open for self-registration at the moment. If you are interested in testing the platform, please send your project information to admin@thingseye.io, and we will create an account for you.
--[[image:image-20220719110247-2.png||height="388" width="683"]]
++* 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:thingseye-io-step-1.png||height="625" width="1000"]]
--(% style="color:blue" %)**Step 3**(%%): Create an account or log in Mydevices.
--(% style="color:blue" %)**Step 4**(%%): Search LT-22222-L(for both LT-22222-L) and add DevEUI.(% style="display:none" %)
++On the **Add integration** window, configure the following:
--Search under The things network
++**Basic settings:**
--[[image:1653356838789-523.png||height="337" width="740"]]
++* 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.
++[[image:thingseye-io-step-2.png||height="625" width="1000"]]
--After added, the sensor data arrive TTN, it will also arrive and show in Mydevices.
--[[image:image-20220524094909-1.png||height="335" width="729"]]
++**Uplink data converter:**
++* 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 uplink 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:image-20220524094909-2.png||height="337" width="729"]]
++[[image:thingseye-io-step-3.png||height="625" width="1000"]]
--[[image:image-20220524094909-3.png||height="338" width="727"]]
++**Downlink data converter (this is an optional step):**
++* 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 downlink decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Downlink_Converter.js]].
++* Click the **Next** button. You will be navigated to the **Connection** tab.
--[[image:image-20220524094909-4.png||height="339" width="728"]](% style="display:none" %)
++[[image:thingseye-io-step-4.png||height="625" width="1000"]]
--[[image:image-20220524094909-5.png||height="341" width="734"]]
++**Connection:**
++* 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 **3.5.1 Configuring The Things Stack**).
++* Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
--== 3.6 Interface Detail ==
++[[image:message-1.png]]
--=== 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) ===
++* Click the **Add** button.
--Support NPN Type sensor
++[[image:thingseye-io-step-5.png||height="625" width="1000"]]
++
++Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings and correct any errors.
++
++
++[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
++
++
++==== 3.5.2.1 Viewing integration details ====
++
++Click on 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.
++
++[[image:integration-details.png||height="686" width="1000"]]
++
++
++If you want to edit the settings you have provided, click on the **Toggle edit mode** button. Once you have done click on the **Apply changes **button.
++
++{{info}}
++See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
++{{/info}}
++
++==== **3.5.2.2 Viewing events** ====
++
++The **Events **tab displays all the uplink messages from the LT-22222-L.
++
++* Select **Debug **from the **Event type** dropdown.
++* Select the** time frame** from the **time window**.
++
++[[image:thingseye-events.png||height="686" width="1000"]]
++
++
++* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
++
++[[image:thingseye-json.png||width="1000"]]
++
++
++==== **3.5.2.3 Deleting an integration** ====
++
++If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
++
++
++==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
++
++This will be added soon.
++
++
++== 3.6 Interface Details ==
++
++=== 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
++
++
++Supports NPN-type sensors.
++
  [[image:1653356991268-289.png]]
--=== 3.6.2 Digital Input Port: DI1/DI2 ( For LT-22222-L) ===
++=== 3.6.2 Digital Input Ports: DI1/DI2 ===
  (((
--The DI port of LT-22222-L can support **NPN** or **PNP** or **Dry Contact** 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). (% class="mark" %)When there is active current pass NEC2501 pin1 to pin2. The DI will be active high and DI LED status will change.
++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.
  )))
@@ -1475,7 +1475,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.
  )))
  )))
@@ -1484,22 +1484,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：
  )))
  (((
@@ -1507,7 +1507,7 @@
  )))
  (((
--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.
  )))
  (((
@@ -1515,22 +1515,22 @@
  )))
  (((
--(% 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:
  )))
  (((
@@ -1538,7 +1538,7 @@
  )))
  (((
--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.
  )))
  (((
@@ -1546,22 +1546,22 @@
  )))
  (((
--(% 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:
  )))
  (((
@@ -1569,38 +1569,37 @@
  )))
  (((
--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**(%%): Connect to Dry Contact sensor
++(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
--From above DI ports circuit, we can see that active the photocoupler will need to have a voltage difference between DI+ and DI- port. While the Dry Contact sensor is a passive component which can't provide this voltage difference.
++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, we can provide a power source to one pin of the Dry Contact. Below is a reference connection.
++To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram.
  [[image:image-20230616235145-1.png]]
--(% style="color:blue" %)**Example5**(%%): Connect to Open Colleactor
++(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
  [[image:image-20240219115718-1.png]]
++=== 3.6.3 Digital Output Ports: DO1/DO2 ===
--=== 3.6.3 Digital Output Port: DO1/DO2 /DO3 ===
++(% style="color:blue" %)**NPN output**(%%): GND or Float. The maximum voltage that can be applied to the output pin is 36V.
--(% style="color:blue" %)**NPN output**(%%): GND or Float. Max voltage can apply to output pin is 36v.
++(% style="color:red" %)**Note: The DO pins will float when the device is powered off.**
--(% style="color:red" %)**Note: DO pins go to float when device is power off.**
--
  [[image:1653357531600-905.png]]
--=== 3.6.4 Analog Input Interface ===
++=== 3.6.4 Analog Input Interfaces ===
--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:
++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**
@@ -1607,14 +1607,14 @@
  [[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.
  (% style="color:blue" %)**Specifications of the wind speed sensor:**
--(% style="color:red" %)**Red:      12~~24v**
++(% style="color:red" %)**Red:      12~~24V**
  (% style="color:#ffc000" %)**Yellow:  4~~20mA**
@@ -1627,7 +1627,7 @@
  [[image:1653357648330-671.png||height="155" width="733"]]
--Example connected to a regulated power supply to measure voltage
++Example: Connecting to a regulated power supply to measure voltage
  [[image:image-20230608101532-1.png||height="606" width="447"]]
@@ -1636,7 +1636,7 @@
  [[image:image-20230608101722-3.png||height="102" width="1139"]]
--(% style="color:blue; font-weight:bold" %)**Specifications of the regulated power**(%%) (% style="color:blue" %)**:**
++(% style="color:blue; font-weight:bold" %)**Specifications of the regulated power supply**(% style="color:blue" %)**:**
  (% style="color:red" %)**Red:      12~~24v**
@@ -1647,9 +1647,9 @@
  (((
--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**: RO pins go to Open(NO) when device is power off.
++**Note**: The ROx pins will be in the Open (NO) state when the LT-22222-L is powered off.
  )))
  [[image:image-20220524100215-9.png]]
@@ -1660,13 +1660,11 @@
  == 3.7 LEDs Indicators ==
++The table below lists the behavior of LED indicators for each port function.
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %)
--|(% style="background-color:#4f81bd; color:white; width:50px" %)**LEDs**|(% style="background-color:#4f81bd; color:white; width:470px" %)**Feature**
--|**PWR**|Always on if there is power
--|**SYS**|(((
--After device is powered on, the SYS will **fast blink in GREEN** for 5 times, means RS485-LN start to join LoRaWAN network. If join success, SYS will be **on GREEN for 5 seconds. **SYS will **blink Blue** on every upload and **blink Green** once receive a downlink message.
--)))
++(% 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 when there is power
  |**TX**|(((
  (((
  Device boot: TX blinks 5 times.
@@ -1673,7 +1673,7 @@
  )))
  (((
--Successful join network: TX ON for 5 seconds.
++Successful network join: TX remains ON for 5 seconds.
  )))
  (((
@@ -1680,40 +1680,34 @@
  Transmit a LoRa packet: TX blinks once
  )))
  )))
--|**RX**|RX blinks once when receive a packet.
--|**DO1**|
--|**DO2**|
--|**DO3**|
--|**DI2**|(((
--For LT-22222-L: ON when DI2 is high, LOW when DI2 is low
++|**RX**|RX blinks once when a packet is received.
++|**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, LOW when DI2 is low
++For LT-22222-L: ON when DI2 is high, OFF when DI2 is low
  )))
--|**DI2**|(((
--For LT-22222-L: ON when DI2 is high, LOW when DI2 is low
--)))
--|**RO1**|
--|**RO2**|
++|**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 Commands =
--== 4.1 Access AT Command ==
++The LT-22222-L supports programming using AT Commands.
++== 4.1 Connecting the LT-22222-L to a PC ==
  (((
--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.
--)))
++You can use a USB-to-TTL adapter along with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below.
--(((
--
++[[image:usb-ttl-programming.png]]
  )))
--[[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, you need to set the (% style="color:#4f81bd" %)**serial tool **(%%)(such as [[PuTTY>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]] or [[SecureCRT>>https://www.vandyke.com/cgi-bin/releases.php?product=securecrt]]) to a baud rate of (% style="color:green" %)**9600**(%%) to access the serial console of LT-22222-L. Access to AT commands is disabled by default, and a password (default: (% style="color:green" %)**123456**)(%%) must be entered to enable AT command access, as shown below:
  )))
  [[image:1653358355238-883.png]]
@@ -1720,194 +1720,63 @@
  (((
--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/]]
--(((
--AT+<CMD>?        : Help on <CMD>
++== 4.2 LT-22222-L related AT commands ==
  )))
  (((
--AT+<CMD>         : Run <CMD>
--)))
++The following is the list of all the AT commands related to the LT-22222-L, except for those used for switching between working modes.
--(((
--AT+<CMD>=<value> : Set the value
++* **##AT##+<CMD>?** : Help on <CMD>
++* **##AT##+<CMD>** : Run <CMD>
++* **##AT##+<CMD>=<value>** : Set the value
++* **##AT##+<CMD>=?** : Get the value
++* ##**ATZ**##: Trigger a reset of the MCU
++* ##**AT+FDR**##: Reset Parameters to factory default, reserve keys
++* **##AT+DEUI##**: Get or set the Device EUI (DevEUI)
++* **##AT+DADDR##**: Get or set the Device Address (DevAddr)
++* **##AT+APPKEY##**: Get or set the Application Key (AppKey)
++* ##**AT+NWKSKEY**##: Get or set the Network Session Key (NwkSKey)
++* **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
++* **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
++* **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
++* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
++* AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)
++* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
++* AT+PNM: Get or set the public network mode. (0: off, 1: on)
++* AT+RX2FQ: Get or set the Rx2 window frequency
++* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
++* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
++* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
++* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
++* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
++* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
++* AT+NWKID: Get or set the Network ID
++* AT+FCU: Get or set the Frame Counter Uplink (FCntUp)
++* AT+FCD: Get or set the Frame Counter Downlink (FCntDown)
++* AT+CLASS: Get or set the Device Class
++* AT+JOIN: Join network
++* AT+NJS: Get OTAA Join Status
++* AT+SENDB: Send hexadecimal data along with the application port
++* AT+SEND: Send text data along with the application port
++* AT+RECVB: Print last received data in binary format (with hexadecimal values)
++* AT+RECV: Print last received data in raw format
++* AT+VER: Get current image version and Frequency Band
++* AT+CFM: Get or Set the confirmation mode (0-1)
++* AT+CFS: Get confirmation status of the last AT+SEND (0-1)
++* AT+SNR: Get the SNR of the last received packet
++* AT+RSSI: Get the RSSI of the last received packet
++* AT+TDC: Get or set the application data transmission interval in ms
++* AT+PORT: Get or set the application port
++* AT+DISAT: Disable AT commands
++* AT+PWORD: Set password, max 9 digits
++* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode
++* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470
++* AT+CFG: Print all settings
  )))
--(((
--AT+<CMD>=?       :  Get the value
--)))
--(((
--ATZ: Trig a reset of the MCU
--)))
--
--(((
--AT+FDR: Reset Parameters to Factory Default, Keys Reserve
--)))
--
--(((
--AT+DEUI: Get or Set the Device EUI
--)))
--
--(((
--AT+DADDR: Get or Set the Device Address
--)))
--
--(((
--AT+APPKEY: Get or Set the Application Key
--)))
--
--(((
--AT+NWKSKEY: Get or Set the Network Session Key
--)))
--
--(((
--AT+APPSKEY:  Get or Set the Application Session Key
--)))
--
--(((
--AT+APPEUI:    Get or Set the Application EUI
--)))
--
--(((
--AT+ADR: Get or Set the Adaptive Data Rate setting. (0: off, 1: on)
--)))
--
--(((
--AT+TXP: Get or Set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Spec)
--)))
--
--(((
--AT+DR:  Get or Set the Data Rate. (0-7 corresponding to DR_X)
--)))
--
--(((
--AT+DCS: Get or Set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
--)))
--
--(((
--AT+PNM: Get or Set the public network mode. (0: off, 1: on)
--)))
--
--(((
--AT+RX2FQ: Get or Set the Rx2 window frequency
--)))
--
--(((
--AT+RX2DR: Get or Set the Rx2 window data rate (0-7 corresponding to DR_X)
--)))
--
--(((
--AT+RX1DL: Get or Set the delay between the end of the Tx and the Rx Window 1 in ms
--)))
--
--(((
--AT+RX2DL: Get or Set the delay between the end of the Tx and the Rx Window 2 in ms
--)))
--
--(((
--AT+JN1DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
--)))
--
--(((
--AT+JN2DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
--)))
--
--(((
--AT+NJM:    Get or Set the Network Join Mode. (0: ABP, 1: OTAA)
--)))
--
--(((
--AT+NWKID: Get or Set the Network ID
--)))
--
--(((
--AT+FCU: Get or Set the Frame Counter Uplink
--)))
--
--(((
--AT+FCD: Get or Set the Frame Counter Downlink
--)))
--
--(((
--AT+CLASS: Get or Set the Device Class
--)))
--
--(((
--AT+JOIN: Join network
--)))
--
--(((
--AT+NJS: Get OTAA Join Status
--)))
--
--(((
--AT+SENDB: Send hexadecimal data along with the application port
--)))
--
--(((
--AT+SEND: Send text data along with the application port
--)))
--
--(((
--AT+RECVB: Print last received data in binary format (with hexadecimal values)
--)))
--
--(((
--AT+RECV: Print last received data in raw format
--)))
--
--(((
--AT+VER:  Get current image version and Frequency Band
--)))
--
--(((
--AT+CFM: Get or Set the confirmation mode (0-1)
--)))
--
--(((
--AT+CFS:  Get confirmation status of the last AT+SEND (0-1)
--)))
--
--(((
--AT+SNR: Get the SNR of the last received packet
--)))
--
--(((
--AT+RSSI: Get the RSSI of the last received packet
--)))
--
--(((
--AT+TDC: Get or set the application data transmission interval in ms
--)))
--
--(((
--AT+PORT: Get or set the application port
--)))
--
--(((
--AT+DISAT: Disable AT commands
--)))
--
--(((
--AT+PWORD: Set password, max 9 digits
--)))
--
--(((
--AT+CHS: Get or Set Frequency (Unit: Hz) for Single Channel Mode
--)))
--
--(((
--AT+CHE: Get or Set eight channels mode, Only for US915, AU915, CN470
--)))
--
--(((
--AT+CFG: Print all settings
--)))
--
--
  == 4.2 Common AT Command Sequence ==
  === 4.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
@@ -1916,41 +1916,41 @@
  (((
--(% style="color:blue" %)**If device has not joined network yet:**
++(% style="color:blue" %)**If the device has not yet joined the network:**
  )))
  )))
  (((
--(% style="background-color:#dcdcdc" %)**123456**
++(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**##
  )))
  (((
--(% style="background-color:#dcdcdc" %)**AT+FDR**
++(% style="background-color:#dcdcdc" %)##**AT+FDR ~/~/Reset parameters to factory default, Reserve keys**##
  )))
  (((
--(% style="background-color:#dcdcdc" %)**123456**
++(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**##
  )))
  (((
--(% style="background-color:#dcdcdc" %)**AT+NJM=0**
++(% style="background-color:#dcdcdc" %)##**AT+NJM=0 ~/~/Set to ABP mode**##
  )))
  (((
--(% style="background-color:#dcdcdc" %)**ATZ**
++(% style="background-color:#dcdcdc" %)##**ATZ ~/~/Reset MCU**##
  )))
  (((
--(% style="color:blue" %)**If device already joined network:**
++(% style="color:blue" %)**If the device has already joined the 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**##
  )))
@@ -1960,20 +1960,20 @@
  (((
--(% style="background-color:#dcdcdc" %)**123456**(%%)        ~/~/ Enter Password to have AT access.
++(% style="background-color:#dcdcdc" %)**123456**(%%)        ~/~/ Enter password to enable AT commands 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, Reserve keys
  )))
  (((
--(% style="background-color:#dcdcdc" %)** 123456**(%%)       ~/~/ Enter Password to have AT access.
++(% style="background-color:#dcdcdc" %)** 123456**(%%)       ~/~/ Enter password to enable AT commands access
  )))
  (((
--(% style="background-color:#dcdcdc" %)** AT+CLASS=C**(%%)   ~/~/ Set to work in CLASS C
++(% style="background-color:#dcdcdc" %)** AT+CLASS=C**(%%)   ~/~/ Set to CLASS C mode
  )))
  (((
@@ -1993,19 +1993,19 @@
  )))
  (((
--(% 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.4 MHz
  )))
  (((
--(% 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 RX2 frequency to 868.4 MHz (according to the result from the 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 RX2 DR to match the downlink DR from the 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. The Device Address can be found in the application on the LoRaWAN NS.
  )))
  (((
@@ -2019,14 +2019,14 @@
  )))
  (((
--**~1. Make sure the device is set to ABP mode in the IoT Server.**
++**~1. Ensure that the device is set to ABP mode in the LoRaWAN Network Server.**
--**2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.**
++**2. Verify that the LG01/02 gateway RX frequency matches the AT+CHS setting exactly.**
--**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?
++**3. Make sure the SF/bandwidth settings in the LG01/LG02 match the settings of AT+DR. Refer to [[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.**
++**4. The commands AT+RX2FQ and AT+RX2DR enable downlink functionality. To set the correct parameters, you can check the actual downlink parameters to be used as shown below. Here, RX2FQ should be set to 868400000 and RX2DR should be set to 5.**
  )))
  (((
@@ -2038,7 +2038,7 @@
  (((
--(% style="color:blue" %)**If sensor JOINED:**
++(% style="color:blue" %)**If the sensor has JOINED:**
  (% style="background-color:#dcdcdc" %)**AT+CLASS=A**
@@ -2048,37 +2048,48 @@
  = 5. Case Study =
--== 5.1 Counting how many objects pass in Flow Line ==
++== 5.1 Counting how many objects pass through the flow line ==
++See [[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]]?
--Reference Link: [[How to set up to count objects pass in flow line>>How to set up to count objects pass in flow line]]?
--
  = 6. FAQ =
--== 6.1 How to upgrade the image? ==
++This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
--The LT LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to LT to:
++== 6.1 How to update the firmware? ==
++Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to:
++
  * Support new features
--* For bug fix
--* Change LoRaWAN bands.
++* Fix bugs
++* Change LoRaWAN frequency bands
--Below shows the hardware connection for how to upload an image to the LT:
++You will need the following things before proceeding:
--[[image:1653359603330-121.png]]
++* 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
++* USB to TTL adapter
++* Download and install the [[STM32 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]]. (replaced by STM32CubeProgrammer)
++* Download the latest firmware image from [[LT-22222-L firmware image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]]. Check the file name of the firmware to find the correct region.
++{{info}}
++As of this writing, the latest firmware version available for the LT-22222-L is v1.6.1.
++{{/info}}
--(((
--(% 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>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]].
--(% style="color:blue" %)**Step3**(%%)**:** Open flashloader; choose the correct COM port to update.
--
++Below is the hardware setup for uploading a firmware image to the LT-22222-L:
++[[image:usb-ttl-programming.png]]
++
++
++
++Start the STM32 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 briefly press the **RST** button. The **DO1** LED will change from OFF to ON. When the **DO1** LED is ON, it indicates that the device is in firmware download mode.
  )))
@@ -2093,7 +2093,7 @@
  [[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.5 mm cable. The pin mapping is as follows:
  [[image:1653360054704-518.png||height="186" width="745"]]
@@ -2100,33 +2100,29 @@
  (((
  (((
--== 6.2 How to change the LoRa Frequency Bands/Region? ==
--
--
++== 6.2 How to change the LoRaWAN frequency band/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 Single Channel Gateway such as LG01/LG02? ==
--
--
++== 6.3 How to setup LT-22222-L to work with a 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-22222-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.
++We assume you have an LG01/LG02 working on the frequency 868400000. Below are the steps.
  )))
@@ -2133,52 +2133,55 @@
  )))
  (((
--(% 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 account and create an ABP device in the application. To do this, use the manual registration option as explained in section 3.2.2.2, //Adding a Device Manually//. Select //Activation by Personalization (ABP)// under Activation Mode. Enter the DevEUI exactly as shown on the registration information sticker, then generate the Device Address, Application Session Key (AppSKey), and Network Session Key (NwkSKey).
--
++[[image:lt-22222-l-abp.png||height="686" width="1000"]]
  )))
  (((
--[[image:1653360231087-571.png||height="401" width="727"]]
--
  )))
--(((
--(% style="color:red" %)**Note: user just need to make sure above three keys match, User can change either in TTN or Device to make then match. In TTN, NETSKEY and APPSKEY can be configured by user in setting page, but Device Addr is generated by TTN.**
--)))
++{{warning}}
++Ensure that the Device Address (DevAddr) and the two keys match between the LT-22222-L and The Things Stack. You can modify them either in The Things Stack or on the LT-22222-L to make them align. In The Things Stack, you can configure the NwkSKey and AppSKey on the settings page, but note that the Device Address is generated by The Things Stack.
++{{/warning}}
--
  (((
--(% style="color:blue" %)**Step2**(%%)**:  **Run AT Command to make LT work in Single frequency & ABP mode. Below is the AT commands:
++(% style="color:blue" %)**Step 2**(%%)**:  **(% 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" %)Run AT commands to configure the LT-22222-L to operate in single-frequency and ABP mode. The AT commands are as follows:
  )))
  (((
--(% style="background-color:#dcdcdc" %)**123456** (%%)   :   Enter Password to have AT access.
++(% style="background-color:#dcdcdc" %)**123456** (%%) : Enter the password to enable 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, keeping keys reserved.
--(% 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** (%%) : Disable the Adaptive Data Rate (ADR).
--(% style="background-color:#dcdcdc" %)**AT+DR=5** (%%)    :   Set Data Rate (Set AT+DR=3 for 915 band)
++(% style="background-color:#dcdcdc" %)**AT+DR=5** (%%) : Set Data Rate (Use AT+DR=3 for the 915 MHz band).
--(% 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.4 MHz.
--(% style="background-color:#dcdcdc" %)**AT+DADDR=26 01 1A F1**(%%)  :  Set Device Address to 26 01 1A F1
++(% style="background-color:#dcdcdc" %)**AT+DADDR=xxxx**(%%) : Set the Device Address (DevAddr)
--(% style="background-color:#dcdcdc" %)**ATZ**        (%%)                              :  Reset MCU
++(% 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:700; text-decoration:none; white-space:pre-wrap" %)**AT+APPKEY=xxxx**(% 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" %): Get or set the Application Key (AppKey)
++
++(% 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" %)**AT+NWKSKEY=xxxx**: Get or set the Network Session Key (NwkSKey)
++
++(% 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" %)**AT+APPSKEY=xxxx**: Get or set the Application Session Key (AppSKey)
++
++(% style="background-color:#dcdcdc" %)**ATZ**        (%%) : Reset MCU.
  )))
  (((
--As shown in below:
++(% 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" %)The following figure shows the screenshot of the command set above, issued using a serial tool:
  )))
  [[image:1653360498588-932.png||height="485" width="726"]]
@@ -2186,156 +2186,137 @@
  == 6.4 How to change the uplink interval? ==
--
  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/]]
--== 6.5 Can I see counting event in Serial? ==
++== 6.5 Can I see the counting event in the serial output? ==
--
  (((
--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.
++You can run the AT command **AT+DEBUG** to view the counting event in the serial output. If the firmware is too old and doesn’t support AT+DEBUG, update to the latest firmware first.
--== 6.6 Can i use point to point communication for LT-22222-L? ==
++== 6.6 Can I use point-to-point communication with LT-22222-L? ==
++Yes, you can. Please refer to the [[Point-to-Point Communication of LT-22222-L>>https://wiki.dragino.com/xwiki/bin/view/Main/%20Point%20to%20Point%20Communication%20of%20LT-22222-L/]] page. The firmware that supports point-to-point communication can be found [[here>>https://github.com/dragino/LT-22222-L/releases]].
--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]].
--
  )))
  (((
--== 6.7 Why does the relay output become the default and open relay after the lt22222 is powered off? ==
++== 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
++* If the device is not properly shut down and is directly powered off.
++* It will default to a power-off state.
++* In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
++* After a restart, the status before the power failure will be read from flash.
--If the device is not shut down, but directly powered off.
++== 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
--It will default that this is a power-off state.
++The LT-22222-L's built-in relay is Normally Open (NO). You can use an external relay to achieve a Normally Closed (NC) configuration. The circuit diagram is shown below:
--In modes 2 to 5, DO RO status and pulse count are saved in flash.
--After restart, the status before power failure will be read from flash.
--
--
--== 6.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.9 Can the LT-22222-L save the RO state? ==
++To enable this feature, the firmware version must be 1.6.0 or higher.
--Firmware version needs to be no less than 1.6.0.
++== 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
--== 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 that the wire connected to the GND is loose.
--It is likely that the GND is not connected during the measurement, or the wire connected to the GND is loose.
++= 7. Troubleshooting =
++This section provides some known troubleshooting tips.
--= 7. Trouble Shooting =
++
  )))
  (((
  (((
--== 7.1 Downlink doesn't work, how to solve it? ==
--
--
++== 7.1 Downlink isn't working. How can I solve this? ==
  )))
  )))
  (((
--Please see this link for how to debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]]
++Please refer to this link for debugging instructions: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]]
  )))
  (((
--== 7.2 Have trouble to upload image. ==
--
--
++== 7.2 Having trouble uploading an image? ==
  )))
  (((
--See this link for trouble shooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
++Please refer to this link for troubleshooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
  )))
  (((
--== 7.3 Why I can't join TTN in US915 /AU915 bands? ==
--
--
++== 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
  )))
  (((
--It might be about the channels mapping. [[Please see this link for detail>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
++It might be related to the channel mapping. [[Please refer to this link for details.>>https://github.com/dragino/LT-22222-L/releases]]
  )))
--== 7.4 Why can LT22222 perform Uplink normally, but cannot receive Downlink? ==
++== 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? ==
++The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
++Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
--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. Ordering information =
--= 8. Order Info =
--
--
  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
  (% style="color:#4f81bd" %)**XXX:**
--* (% style="color:red" %)**EU433**(%%):   LT with frequency bands EU433
--* (% style="color:red" %)**EU868**(%%):   LT with frequency bands EU868
--* (% style="color:red" %)**KR920**(%%):   LT with frequency bands KR920
--* (% style="color:red" %)**CN470**(%%):  LT with frequency bands CN470
--* (% style="color:red" %)**AS923**(%%):   LT with frequency bands AS923
--* (% style="color:red" %)**AU915**(%%):  LT with frequency bands AU915
--* (% style="color:red" %)**US915**(%%):  LT with frequency bands US915
--* (% style="color:red" %)**IN865**(%%):   LT with frequency bands IN865
--* (% style="color:red" %)**CN779**(%%):  LT with frequency bands CN779
++* (% style="color:red" %)**EU433**(%%): LT with frequency bands EU433
++* (% style="color:red" %)**EU868**(%%): LT with frequency bands EU868
++* (% style="color:red" %)**KR920**(%%): LT with frequency bands KR920
++* (% style="color:red" %)**CN470**(%%): LT with frequency bands CN470
++* (% style="color:red" %)**AS923**(%%): LT with frequency bands AS923
++* (% style="color:red" %)**AU915**(%%): LT with frequency bands AU915
++* (% style="color:red" %)**US915**(%%): LT with frequency bands US915
++* (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865
++* (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779
--= 9. Packing Info =
++= 9. Package information =
++**Package includes**:
--**Package Includes**:
++* 1 x LT-22222-L I/O Controller
++* 1 x LoRa antenna matched to the frequency of the LT-22222-L
++* 1 x bracket for DIN rail mounting
++* 1 x 3.5 mm programming cable
--* LT-22222-L I/O Controller x 1
--* Stick Antenna for LoRa RF part x 1
--* Bracket for controller x1
--* Program cable x 1
--
  **Dimension and weight**:
  * Device Size: 13.5 x 7 x 3 cm
--* Device Weight: 105g
++* Device Weight: 105 g
  * Package Size / pcs : 14.5 x 8 x 5 cm
--* Weight / pcs : 170g
++* Weight / pcs : 170 g
  = 10. 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.
++Support is available Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different time zones, we cannot offer live support. However, your questions will be answered as soon as possible within the aforementioned 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.cc>>mailto:Support@dragino.cc]]
++Please provide as much information as possible regarding your inquiry (e.g., product models, a detailed description of the problem, steps to replicate it, etc.) and send an email to [[support@dragino.cc>>mailto:support@dragino.cc]]
--
  )))
  = 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]]

dragino-lorawan-nw-lt-22222-n.jpg

Author

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

Size

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

Content

dragino-ttn-te.jpg

Author

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

Size

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

Content

integration-details.png

Author

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

Size

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

Content

lorawan-nw.jpg

Author

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

Size

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

Content

lt-22222-device-overview.png

Author

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

Size

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

Content

lt-22222-join-network.png

Author

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

Size

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

Content

lt-22222-l-abp.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+321.4 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

lt-22222-ul-payload-decoded.png

Author

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

Size

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

Content

lt-22222-ul-payload-fmt.png

Author

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

Size

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

Content

message-1.png

Author

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

Size

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

Content

thingseye-events.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+530.6 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

thingseye-json.png

Author

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

Size

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

Content

thingseye.io_integrationsCenter_integrations-2.png

Author

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

Size

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

Content

thingseye.io_integrationsCenter_integrations.png

Author

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

Size

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

Content

tts-mqtt-integration.png

Author

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

Size

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

Content

usb-ttl-programming.png

Author

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

Size

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

Content