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

Last modified by Saxer Lin on 2025/04/15 17:24

From version < 207.1 >

edited by Dilisi S
on 2024/11/22 04:26

To version < 181.1 >

edited by Dilisi S
on 2024/11/10 05:03

Change comment: Uploaded new attachment "thingseye-events.png", version {1}

Raw
Rendered

Summary

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

Details

Page properties

Title

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

Content

@@ -23,12 +23,8 @@
  (((
  (((
--{{info}}
--**This manual is also applicable to the LT-33222-L.**
--{{/info}}
++The Dragino (% style="color:blue" %)**LT-22222-L I/O Controller**(%%) is an advanced LoRaWAN device designed to provide seamless wireless long-range connectivity with various I/O options, including analog current and voltage inputs, digital inputs and outputs, and relay outputs.
--The Dragino (% style="color:blue" %)**LT-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-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.
  )))
  )))
@@ -40,24 +40,19 @@
  (((
  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 public LoRaWAN network coverage in the area where you plan to install the device (e.g., The Things Network), you can select a network and register the LT-22222-L I/O controller with it.
  * If there is no public LoRaWAN coverage in your area, you can set up a LoRaWAN gateway, or multiple gateways, and connect them to a LoRaWAN network server to create adequate coverage. Then, register the LT-22222-L I/O controller with this network.
  * Setup your own private LoRaWAN network.
--{{info}}
-- You can use a LoRaWAN gateway, such as the [[Dragino LG308>>https://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], to expand or create LoRaWAN coverage in your area.
--{{/info}}
++> You can use a LoRaWAN gateway, such as the Dragino LG308, to expand or create LoRaWAN coverage in your area.
  )))
  (((
--
++[[image:1653295757274-912.png]]
--The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
++
  )))
--(% class="wikigeneratedid" %)
--[[image:lorawan-nw.jpg||height="354" width="900"]]
--
  == 1.2 Specifications ==
  (% style="color:#037691" %)**Hardware System:**
@@ -65,13 +65,13 @@
  * STM32L072xxxx MCU
  * SX1276/78 Wireless Chip
  * Power Consumption:
--** Idle: 4mA@12V
++** Idle: 4mA@12v
  ** 20dB Transmit: 34mA@12V
  * Operating Temperature: -40 ~~ 85 Degrees, No Dew
  (% 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 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)
@@ -81,8 +81,8 @@
  (% style="color:#037691" %)**LoRa Spec:**
  * Frequency Range:
--** Band 1 (HF): 862 ~~ 1020 MHz
--** Band 2 (LF): 410 ~~ 528 MHz
++** 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.
@@ -101,7 +101,7 @@
  == 1.3 Features ==
--* LoRaWAN Class A & Class C modes
++* LoRaWAN Class A & Class C protocol
  * Optional Customized LoRa Protocol
  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
  * AT Commands to change parameters
@@ -111,20 +111,22 @@
  == 1.4 Applications ==
--* Smart buildings & home automation
--* Logistics and supply chain management
--* Smart metering
--* Smart agriculture
--* Smart cities
--* Smart factory
++* 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" %)(((
++
++(% 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)
@@ -133,20 +133,21 @@
  * 1 x Counting Port
  )))
--== 2. Assembling the device ==
++= 2. Assembling the Device =
--== 2.1 Connecting the antenna ==
++== 2.1 What is included in the package? ==
--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.
++The package includes the following items:
--{{warning}}
--Warning! Do not power on the device without connecting the antenna.
--{{/warning}}
++* 1 x LT-22222-L I/O Controller
++* 1 x LoRaWAN antenna matched to the frequency of the LT-22222-L
++* 1 x bracket for DIN rail mounting
++* 1 x programming cable
++Attach the LoRaWAN antenna to the antenna connector, **ANT**,** **located on the top right side of the device, next to the upper terminal block. Secure the antenna by tightening it clockwise.
++
  == 2.2 Terminals ==
--The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 terminals and the lower screw terminal block has 10 terminals.
--
  Upper screw terminal block (from left to right):
  (% style="width:634px" %)
@@ -173,79 +173,62 @@
  |(% 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 ==
++== 2.3 Powering the LT-22222-L ==
--The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect 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.
++The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect the power supply’s positive wire to the VIN and the negative wire to the GND screw terminals. The power indicator (PWR) LED will turn on when the device is properly powered.
--{{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}}
--
  [[image:1653297104069-180.png]]
--= 3. Registering LT-22222-L with a LoRaWAN Network Server =
++= 3. Operation Mode =
--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.
++== 3.1 How does it work? ==
++By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode. It supports OTAA (Over-the-Air Activation), the most secure method for activating a device with a LoRaWAN network server. The LT-22222-L comes with device registration information that allows you to register it with a LoRaWAN network, enabling the device to perform OTAA activation with the network server upon initial power-up and after any subsequent reboots.
--=== 3.2.1 Prerequisites ===
++After powering on, the **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** the LoRaWAN network. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LE**D will be on for **1 second**. When the device is sending an uplink message to the server, the **TX LED** will be on for **1 second**. See also LED status.
--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"]]
--
--{{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}}
--The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
++== 3.2 Registering with a LoRaWAN network server ==
--=== 3.2.2 The Things Stack ===
++The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
--This section guides you through how to register your LT-22222-L with The Things Stack Sandbox.
++[[image:image-20220523172350-1.png||height="266" width="864"]]
--{{info}}
--The Things Stack Sandbox was formally called The Things Stack Community Edition.
--{{/info}}
++=== 3.2.1 Prerequisites ===
++Make sure you have the device registration information such as DevEUI, AppEUI, and AppKey with you. The registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference.
--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.
++[[image:image-20230425173427-2.png||height="246" width="530"]]
--[[image:dragino-ttn-te.jpg]]
++The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
++=== 3.2.2 The Things Stack Sandbox (TTSS) ===
++* Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account.
++* Create an application if you do not have one yet.
++* Register LT-22222-L with that application. Two registration options are available:
--==== 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:
++==== 3.2.2.1 Using the LoRaWAN Device Repository ====
--
--==== 3.2.2.2 Using the LoRaWAN Device Repository ====
--
++* Go to your application and click on the **Register end device** button.
  * On the **Register end device** page:
--** Select the option **Select the end device in the LoRaWAN Device Repository **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.
++** Select the option **Select the end device in the LoRaWAN Device Repository**.
++** Choose the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)**.
++** Select the **Frequency plan** that matches your device.
  [[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
--* 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.
++* Page continued...
++** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
++** Enter the **DevEUI** in the **DevEUI** field.
++** Enter the **AppKey** in the **AppKey** field.
++** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
  ** Under **After registration**, select the **View registered end device** option.
  [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
@@ -252,25 +252,25 @@
  ====   ====
--==== 3.2.2.3 Adding device manually ====
++==== 3.2.2.2 Entering device information manually ====
  * 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.
++** Select the **Enter end device specifies manually** option as the input method.
++** Select the **Frequency plan** that matches your device.
++** Select the **LoRaWAN version**.
++** Select the **Regional Parameters version**.
++** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the section.
++** Select **Over the air activation (OTAA)** option under the **Activation mode**
++** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities**.
  [[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
--* 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.
++* Page continued...
++** Enter **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
++** Enter **DevEUI** in the **DevEUI** field.
++** Enter **AppKey** in the **AppKey** field.
++** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
  ** Under **After registration**, select the **View registered end device** option.
  ** Click the **Register end device** button.
@@ -283,21 +283,18 @@
  [[image:lt-22222-device-overview.png||height="625" width="1000"]]
--==== 3.2.2.4 Joining ====
++==== 3.2.2.3 Joining ====
--On the Device overview page, click on **Live data** tab. The Live data panel for your device will display.
++Click on **Live data** in the left navigation. The Live data panel for your application 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.
++Power on your LT-22222-L. It will begin joining The Things Stack LoRaWAN network server. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server. Once successfully joined, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**).
  [[image:lt-22222-join-network.png||height="625" width="1000"]]
--==== 3.2.2.5 Uplinks ====
++By default, you will receive an uplink data message every 10 minutes.
--
--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]]
@@ -305,23 +305,14 @@
  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 **End devices** > **LT-22222-L** > **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 ====
++== 3.3 Work Modes and their Uplink Payload formats ==
--When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
++The LT-22222-L has 5 **work modes**. It also has an interrupt/trigger mode for different types of applications that can be used together with any work mode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands.
--== 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
@@ -334,7 +334,7 @@
  * (% 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.
++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 ===
@@ -341,12 +341,8 @@
  (((
  This is the default mode.
--The uplink payload is 11 bytes long.
++The uplink payload is 11 bytes long. (% style="display:none" wfd-invisible="true" %)
--(% 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|(((
@@ -403,13 +403,9 @@
  * [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 is HIGH when there is a load between DO1 and V+.
  ** DO1 LED is OFF in both cases.
--Reserve = 0
--
--MOD = 1
--
  === 3.3.2 AT+MOD~=2, (Double DI Counting) ===
@@ -420,10 +420,6 @@
  (((
  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*|(((
@@ -488,9 +488,6 @@
  === 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**: In this mode, the DI1 is used as a counting pin.
@@ -541,11 +541,7 @@
  === 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**: In this mode, the DI1 is used as a counting pin.
  )))
@@ -592,29 +592,25 @@
  )))
  (((
--AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
++Other AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
  )))
  (((
  **In addition to that,  below are the commands for AVI1 Counting:**
--(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)**
++(% style="color:blue" %)**AT+SETCNT=3,60**(%%)**           (Sets AVI Count to 60)**
--(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
++(% style="color:blue" %)**AT+VOLMAX=20000**(%%)**       (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 higher 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**: In this mode, the DI1 is used as a counting pin.
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
@@ -665,28 +665,23 @@
  )))
--=== 3.3.6 AT+ADDMOD~=6 (Trigger Mode, Optional) ===
++=== 3.3.6 AT+ADDMOD~=6. (Trigger Mode, Optional) ===
--(% style="color:#4f81bd" %)**This mode is optional and intended for trigger purposes. It can operate __alongside__ with other modes.**
++(% style="color:#4f81bd" %)**This mode is optional and intended for trigger purposes. It can operate together with other modes.**
--For example, if you configure the following commands:
++For example, if you configured the following commands:
--* **AT+MOD=1 **            **~-~->**   Sets the default working mode
--* **AT+ADDMOD6=1**   **~-~->**   Enables trigger mode
++* **AT+MOD=1 **            **~-~->**   The normal working mode
++* **AT+ADDMOD6=1**   **~-~->**   Enable trigger mode
--The LT-22222-L will continuously monitor AV1, AV2, AC1, and AC2 every 5 seconds. It will send uplink packets in two cases:
++The LT-22222-L will continuously monitor AV1, AV2, AC1, and AC2 every 5 seconds. LT will send uplink packets in two cases:
--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
++1. Periodically uplink (Based on TDC time). The payload is the same as in normal mode (MOD=1 for the commands above). These are (% style="color:#4f81bd" %)**unconfirmed**(%%) uplinks.
++1. Trigger uplink when the trigger condition is met. LT will send two packets in this case. The first uplink uses the payload specified in trigger mode (MOD=6). The second packet uses the normal mode payload (MOD=1 as set above). Both are (% style="color:#4f81bd" %)**CONFIRMED uplinks.**
--* 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 Command to set Trigger Condition**:
--(% style="color:#037691" %)**AT Commands to set Trigger Conditions**:
--
  (% style="color:#4f81bd" %)**Trigger based on voltage**:
  Format: AT+AVLIM=<AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH>
@@ -694,9 +694,9 @@
  **Example:**
--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=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 (triggers an uplink if AVI1 voltage lower than 5V. Use 0 for parameters that are not in use)
++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**:
@@ -706,7 +706,7 @@
  **Example:**
--AT+ACLIM=10000,15000,0,0 (triggers an uplink if AC1 current is lower than 10mA or higher than 15mA)
++AT+ACLIM=10000,15000,0,0   (triggers an uplink if ACI1 voltage is lower than 10mA or higher than 15mA)
  (% style="color:#4f81bd" %)**Trigger based on DI status**:
@@ -826,9 +826,9 @@
  (% 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: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
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
++|**bit7**|**bit6**|**bit5**|**bit4**|**bit3**|**bit2**|**bit1**|**bit0**
++|N/A|N/A|N/A|N/A|DI2_STATUS|DI2_FLAG|DI1_STATUS|DI1_FLAG
  * Each bits shows which status has been triggered on this uplink.
@@ -857,482 +857,234 @@
  )))
--== 3.4 Configure LT-22222-L via AT Commands or Downlinks ==
++== 3.4 Configure LT via AT Commands or Downlinks ==
++
  (((
--You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks.
++User can configure LT I/O Controller via AT Commands or LoRaWAN Downlinks.
  )))
  (((
  (((
--There are two tytes of commands:
++There are two kinds of Commands:
  )))
  )))
--* (% style="color:blue" %)**Common 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" %)**Sensor-related commands**(%%):
++* (% style="color:blue" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L.  User can see these commands below:
--=== 3.4.1 Common commands ===
++=== 3.4.1 Common Commands ===
  (((
--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.
++These commands should be available for all Dragino sensors, such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]].
  )))
--=== 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 Sensor related commands ===
--
  ==== 3.4.2.1 Set Transmit Interval ====
  Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
--(% 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)
--)))
++where N is the time in milliseconds.
--(% style="color:#037691" %)**Downlink payload**
++**Example: **AT+TDC=30000. This will set the uplink 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 the Work Mode (AT+MOD) ====
--Sets the working mode.
--(% style="color:#037691" %)**AT command**
++Sets the 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
++Where N is the work mode.
--2 = Double DI Counting + DO + RO
++**Example**: AT+MOD=2. This will set the work mode to Double DI counting mode.
--3 = Single DI Counting + 2 x ACI + DO + RO
--4 = Single DI Counting + 1 x Voltage Counting + DO + RO
++* (% style="color:#037691" %)**Downlink payload (prefix 0x0A):**
--5 = Single DI Counting + 2 x AVI + 1 x ACI + DO + RO
++(% style="color:blue" %)**0x0A aa  **(%%)**  ** ~/~/ Same as AT+MOD=aa
--6 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5
--)))
--|(% style="width:97px" %)**Example**|(% style="width:413px" %)(((
--AT+MOD=2
--Sets the device to working mode 2 (Double DI Counting + DO + RO)
--)))
--(% class="wikigeneratedid" %)
--(% style="color:#037691" %)**Downlink payload**
++==== 3.4.2.3 Poll an 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
--**working_mode** : Working mode, represented by 1 byte in hexadecimal.
--)))
--|(% style="width:98px" %)**Example**|(% style="width:400px" %)(((
--0A **02**
++Asks the device to send an uplink.
--Sets the device to working mode 2 (Double DI Counting + DO + RO)
--)))
++* (% style="color:#037691" %)**AT command:**(%%) There is no AT Command to poll uplink
--==== 3.4.2.3 Poll an uplink ====
++* (% style="color:#037691" %)**Downlink payload (prefix 0x08):**
--Requests an uplink from LT-22222-L.
++(% style="color:blue" %)**0x08 FF  **(%%)**   **~/~/ Poll an uplink
--(% style="color:#037691" %)**AT command**
++**Example**: 0x08FF, ask device to send an Uplink
--There is no AT Command to request an uplink from LT-22222-L
--(% style="color:#037691" %)**Downlink payload**
--(% 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
--
--Requests an uplink from LT-22222-L.
--)))
--
  ==== 3.4.2.4 Enable/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**
++Enable or disable the trigger mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
--(% 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:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0**
--1 = enable trigger mode
++(% style="color:red" %)**1:** (%%)Enable the trigger mode
--0 = disable trigger mode
--)))
--|(% style="width:95px" %)**Example**|(% style="width:403px" %)(((
--AT+ADDMOD6=1
++(% style="color:red" %)**0: **(%%)Disable the trigger mode
--Enable trigger mode for the current working mode
--)))
--(% style="color:#037691" %)**Downlink payload**
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A 06):**
--(% 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)
++(% style="color:blue" %)**0x0A 06 aa    **(%%)    ~/~/ Same as AT+ADDMOD6=aa
--**working mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
--)))
--|(% style="width:97px" %)**Example**|(% style="width:401px" %)(((
--0A 06 **01**
--Enable trigger mode for the current working mode
--)))
  ==== 3.4.2.5 Poll trigger settings ====
--Polls the trigger settings.
--(% style="color:#037691" %)**AT Command:**
++Polls the trigger settings
++* (% style="color:#037691" %)**AT Command:**
++
  There is no AT Command for this feature.
--(% style="color:#037691" %)**Downlink Payload**
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x AB 06):**
--(% 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
++(% style="color:blue" %)**0xAB 06  **  (%%)   ~/~/ Poll the trigger settings. Device will uplink trigger settings once receive this command
--Uplinks the trigger settings.
--)))
--==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ====
--Enable or disable DI1/DI2/DI3 as a trigger.
++==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ====
--(% style="color:#037691" %)**AT Command**
--(% 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:**
++Enable or Disable DI1/DI2/DI2 as trigger,
--1 = enable DI1 trigger
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
--0 = disable DI1 trigger
++**Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
--**DI2 _trigger**
--1 = enable DI2 trigger
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 02):**
--0 = disable DI2 trigger
--)))
--|(% style="width:98px" %)**Example**|(% style="width:400px" %)(((
--AT+DTRI=1,0
++(% style="color:blue" %)**0xAA 02 aa bb   **  (%%) ~/~/ Same as AT+DTRI=aa,bb
--Enable DI1 trigger, disable DI2 trigger
--)))
--(% class="wikigeneratedid" %)
--(% style="color:#037691" %)**Downlink Payload**
--(% 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)
++==== 3.4.2.7 Trigger1 – Set DI1 or DI3 as trigger ====
--**DI1_trigger:**
--1 = enable DI1 trigger, represented by 1 byte in hexadecimal.
++Set DI1 or DI3(for LT-33222-L) trigger.
--0 = disable DI1 trigger, represented by 1 byte in hexadecimal.
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG1=a,b**
--**DI2 _trigger**
++(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
--1 = enable DI2 trigger, represented by 1 byte in hexadecimal.
++(% style="color:red" %)**b :** (%%)delay timing.
--0 = disable DI2 trigger, represented by 1 byte in hexadecimal.
--)))
--|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
--AA 02 **01 00**
++**Example:** AT+TRIG1=1,100(set DI1 port to trigger on high level, valid signal is 100ms )
--Enable DI1 trigger, disable DI2 trigger
--)))
--==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ====
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 01 ):**
--Sets DI1 or DI3 (for LT-33222-L) as a trigger.
++(% style="color:blue" %)**0x09 01 aa bb cc    ** (%%)    ~/~/ same as AT+TRIG1=aa,0x(bb cc)
--(% style="color:#037691" %)**AT Command**
--(% 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).
++==== 3.4.2.8 Trigger2 – Set DI2 as trigger ====
--**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 the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms.
--)))
++Sets DI2 trigger.
--(% class="wikigeneratedid" %)
--(% style="color:#037691" %)**Downlink Payload**
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b**
--(% 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" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
--**interrupt_mode** : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal.
++(% style="color:red" %)**b :** (%%)delay timing.
--**minimum_signal_duration** : in milliseconds, represented two bytes in hexadecimal.
--)))
--|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
--09 01 **01 00 64**
++**Example:** AT+TRIG2=0,100 (set DI1 port to trigger on low level, valid signal is 100ms )
--Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms.
--)))
--==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 02 ):**
--Sets DI2 as a trigger.
++(% style="color:blue" %)**0x09 02 aa bb cc   **  (%%)~/~/ same as AT+TRIG2=aa,0x(bb cc)
--(% style="color:#037691" %)**AT Command**
--(% 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).
++==== 3.4.2.9 Trigger – Set AC (current) as trigger ====
--**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 the DI1 port to trigger on a falling edge; the valid signal duration is 100 ms.
--)))
++Set current trigger , base on AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--(% style="color:#037691" %)**Downlink Payload**
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ACLIM**
--(% 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:#037691" %)**Downlink Payload (prefix 0xAA 01 )**
--**interrupt_mode **: 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in 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"]]
--**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"]]
--(% style="color:#037691" %)**AT Command**
++Set current trigger , base on AV port. 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" %)**AT Command**(%%): (% style="color:blue" %)**AT+AVLIM    **(%%)**        See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]**
--**AC1_LIMIT_HIGH **: higher limit of the current to be checked
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 00 )**
--**AC2_LIMIT_HIGH **: lower 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_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"]]
--(% 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)
--
--**AV1_LIMIT_LOW** : lower limit of the voltage to be checked, two bytes in hexadecimal
--
--**AV1_LIMIT_HIGH **: higher limit of the voltage to be checked, two bytes in hexadecimal
--
--**AV2_LIMIT_HIGH **: lower limit of the voltage to be checked, two bytes in hexadecimal
--
--**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**
--
--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**
++Sets AV and AC trigger minimum interval.  Device won't response to the second trigger within this set time after the first trigger.
--(% 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
++* (% 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.
--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 (prefix 0xAC )**
--(% style="color:#037691" %)**Downlink Payload**
++(% style="color:blue" %)**0x AC aa bb   **(%%) ~/~/ same as AT+ATDC=0x(aa bb)   . Unit (min)
--(% 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="color:red" %)**Note: ATDC setting must be more than 5min**
  )))
--|(% 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 the Digital Output.
++There is no AT Command to control Digital Output
--(% style="color:#037691" %)**Downlink Payload**
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x02)**
--(% 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)
++(% style="color:blue" %)**0x02 aa bb cc     ** (%%)~/~/ Set DO1/DO2/DO3 output
--**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)
++(((
++If payload = 0x02010001, while there is load between V+ and DOx, it means set DO1 to low, DO2 to high and DO3 to low.
  )))
--|(% 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**
@@ -1342,18 +1342,15 @@
  )))
  (((
--(((
--(% style="color:red" %)**Note: For the LT-22222-L, there is no DO3; the last byte can have any value.**
++(% style="color:red" %)**Note: For LT-22222-L, there is no DO3, the last byte can use any value.**
  )))
  (((
--(% style="color:red" %)**The device will upload a packet if downlink code executes successfully.**
++(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
  )))
--)))
--)))
--====   ====
++
  ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
@@ -1378,7 +1378,7 @@
 : DO pins will change to an inverter state after timeout
--(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
++(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Ports 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**
@@ -1386,7 +1386,7 @@
  |0x00|DO1 set to high
  |0x11|DO1 NO Action
--(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:
++(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Ports 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**
@@ -1394,7 +1394,7 @@
  |0x00|DO2 set to high
  |0x11|DO2 NO Action
--(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:
++(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Ports 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**
@@ -1402,16 +1402,16 @@
  |0x00|DO3 set to high
  |0x11|DO3 NO Action
--(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)
++(% style="color:#4f81bd" %)**Sixth and Seventh and Eighth and Ninth Byte**:(%%) Latching time. Unit: ms
  (% style="color:red" %)**Note: **
--   Since firmware v1.6.0, the latch time support 4 bytes and 2 bytes
++   Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes
--   Before firmware v1.6.0, the latch time only supported 2 bytes.
++   Before Firmwre v1.6.0 the latch time only suport 2 bytes.
--(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
++(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
  **Example payload:**
@@ -1418,21 +1418,22 @@
  **~1. A9 01 01 01 01 07 D0**
--DO1 pin, DO2 pin, and DO3 pin will be set to low, last for 2 seconds, and then revert to their original state.
++DO1 pin & DO2 pin & DO3 pin will be set to Low, last 2 seconds, then change back to original state.
  **2. A9 01 00 01 11 07 D0**
--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.
++DO1 pin set high, DO2 pin set low, DO3 pin no action, last 2 seconds, then change back to original state.
  **3. A9 00 00 00 00 07 D0**
--DO1 pin, DO2 pin, and DO3 pin will be set to high, last for 2 seconds, and then all change to low.
++DO1 pin & DO2 pin & DO3 pin will be set to high, last 2 seconds, then both change to low.
  **4. A9 00 11 01 00 07 D0**
--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.
++DO1 pin no action, DO2 pin set low, DO3 pin set high, last 2 seconds, then DO1 pin no action, DO2 pin set high, DO3 pin set low
++
  ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
@@ -1447,11 +1447,11 @@
  (((
--If payload is 0x030100, it means setting RO1 to close and RO2 to open.
++If payload = 0x030100, it means set RO1 to close and RO2 to open.
  )))
  (((
--00: Close ,  01: Open , 11: No action
++00: Closed ,  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**
@@ -1468,9 +1468,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:**
@@ -1482,15 +1482,15 @@
  (% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Set RO1/RO2 relay with time control
--This is to control the relay output time. It includes four bytes:
++This is to control the relay output time of relay. Include four bytes:
  (% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
  (% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
--01: Relays will change back to their original state after timeout.
++01: Relays will change back to original state after timeout.
--00: Relays will change to the inverter state after timeout.
++00: Relays will change to an inverter state after timeout
  (% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
@@ -1503,12 +1503,12 @@
  (% style="color:red" %)**Note:**
--   Since firmware v1.6.0, the latch time supports both 4 bytes and 2 bytes.
++   Since Firmware v1.6.0, the latch time support 4 bytes and 2 bytes
--   Before firmware v1.6.0, the latch time only supported 2 bytes.
++   Before Firmwre v1.6.0 the latch time only suport 2 bytes.
--(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
++(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
  **Example payload:**
@@ -1515,19 +1515,19 @@
  **~1. 05 01 11 07 D0**
--Relay1 and Relay2 will be set to NC, lasting 2 seconds, then revert to their original state
++Relay1 and Relay 2 will be set to NC , last 2 seconds, then change back to original state.
  **2. 05 01 10 07 D0**
--Relay1 will change to NC, Relay2 will change to NO, lasting 2 seconds, then both will revert to their original state.
++Relay1 will change to NC, Relay2 will change to NO, last 2 seconds, then both change back to original state.
  **3. 05 00 01 07 D0**
--Relay1 will change to NO, Relay2 will change to NC, lasting 2 seconds, then Relay1 will change to NC, and Relay2 will change to NO.
++Relay1 will change to NO, Relay2 will change to NC, last 2 seconds, then relay change to NC,Relay2 change to NO.
  **4. 05 00 00 07 D0**
--Relay1 and Relay2 will change to NO, lasting 2 seconds, then both will change to NC.
++Relay 1 & relay2 will change to NO, last 2 seconds, then both change to NC.
@@ -1534,7 +1534,7 @@
  ==== 3.4.2.16 Counting ~-~- Voltage threshold counting ====
--When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
++When voltage exceed the threshold, count. Feature see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX   ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
@@ -1543,76 +1543,15 @@
  (% 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 feature 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: **(%%)The number to be set
++(% style="color:red" %)**bb cc dd ee: **(%%)number to be set
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):**
@@ -1620,55 +1620,12 @@
  (% style="color:blue" %)**0x A8 aa bb cc dd ee     ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee)
--(% style="color:#037691" %)**AT Command**
--(% 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
--
--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 feature clears the counting in counting mode.
++Clear counting for counting mode
++
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT         **(%%) ~/~/ clear all counting
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):**
@@ -1675,30 +1675,14 @@
  (% 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" %)-
--(% 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 feature 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  **(%%)~/~/ 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:blue" %)**AT+COUTIME=60  **(%%)~/~/ Set save time to 60 seconds. Device will save the counting result in internal flash every 60 seconds. (min value: 30)
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):**
@@ -1706,47 +1706,19 @@
  (% style="color:blue" %)**0x A7 aa bb cc     ** (%%)~/~/ same as AT+COUTIME =aa bb cc,
  (((
--Range: aa bb cc:0 to 16777215,  (unit: seconds)
++range: aa bb cc:0 to 16777215,  (unit:second)
  )))
--(% 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 feature 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 will not change when the device reconnects to the network.
++(% style="color:blue" %)**AT+RODORESET=0    **(%%)~/~/ After the device is reset, the previously saved RODO state (only MOD2 to MOD5) is read, and its state is not changed when it is reconnected to the network.
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):**
@@ -1754,52 +1754,9 @@
  (% 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 feature 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:**
@@ -1814,9 +1814,9 @@
  * (% style="color:#037691" %)**AT Command:**
--(% style="color:blue" %)**AT+GETSENSORVALUE=0    **(%%)~/~/ The serial port retrieves the reading of the current sensor.
++(% style="color:blue" %)**AT+GETSENSORVALUE=0    **(%%)~/~/ The serial port gets the reading of the current sensor
--(% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it.
++(% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port gets the current sensor reading and uploads it.
@@ -1887,25 +1887,25 @@
  == 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.
++The Things Stack applications can be integrated with ThingsEye.io. Once integrated, ThingsEye.io works as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
--=== 3.5.1 Configuring The Things Stack ===
++=== 3.5.1 Configuring MQTT Connection Information with The Things Stack Sandbox ===
--We use The Things Stack Sandbox in this example:
++We use The Things Stack Sandbox for demonstating the configuration but  other
--* 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.
++* In **The Things Stack Sandbox**, select your application under **Applications**.
++* Select **MQTT** under **Integrations**.
++* In the **Connection information **section, for **Username**, The Things Stack displays an auto-generated username. You can use it or provide a new one.
++* For the **Password**, click the **Generate new API key** button to generate a password. You can see it by clicking on the **eye** button. The API key works as the password.
--{{info}}
--The username and  password (API key) you created here are required in the next section.
--{{/info}}
++NOTE. The username and  password (API key) you created here are required in the next section.
  [[image:tts-mqtt-integration.png||height="625" width="1000"]]
  === 3.5.2 Configuring ThingsEye.io ===
++This section guides you on how to create an integration in ThingsEye to connect with The Things Stack MQTT server.
++
  * 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).
@@ -1942,9 +1942,9 @@
  **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.
++* 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]].
++* Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found here.
  * Click the **Next** button. You will be navigated to the **Connection** tab.
  [[image:thingseye-io-step-4.png||height="625" width="1000"]]
@@ -1954,7 +1954,7 @@
  * Choose **Region** from the **Host type**.
  * Enter the **cluster** of your **The Things Stack** in the **Region** textbox. You can find the cluster in the url (e.g., https:~/~/**eu1**.cloud.thethings.network/...).
--* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The **username **and **password **can be found on the MQTT integration page of your The Things Stack account (see Configuring The Things Stack).
++* Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The username and password can be found on the MQTT integration page of your The Things Stack account (see Configuring MQTT Connection information with The Things Stack Sandbox).
  * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
  [[image:message-1.png]]
@@ -1971,9 +1971,9 @@
  [[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
--==== 3.5.2.1 Viewing integration details ====
++**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.
++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"]]
@@ -1980,41 +1980,40 @@
  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.
--{{/info}}
++Note: See also ThingsEye documentation.
--==== **3.5.2.2 Viewing events** ====
--The **Events **tab displays all the uplink messages from the LT-22222-L.
++**Viewing events:**
++This tab  displays all the uplink messages from the LT-22222-L.
++
++* Click on the **Events **tab.
  * Select **Debug **from the **Event type** dropdown.
  * Select the** time frame** from the **time window**.
--[[image:thingseye-events.png||height="686" width="1000"]]
++[insert image]
++- To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
--* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
++[insert image]
--[[image:thingseye-json.png||width="1000"]]
++**Deleting the integration**:
--==== **3.5.2.3 Deleting an integration** ====
++If you want to delete this integration, click the **Delete integratio**n button.
--If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
--
  == 3.6 Interface Details ==
--=== 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
++=== 3.6.1 Digital Input Port: DI1/DI2 /DI3 ( For LT-33222-L, low active ) ===
--Supports NPN-type sensors.
++Support NPN-type sensor
  [[image:1653356991268-289.png]]
--=== 3.6.2 Digital Input Ports: DI1/DI2 ===
++=== 3.6.2 Digital Input Ports: DI1/DI2 ( For LT-22222-L) ===
  (((
@@ -2144,7 +2144,7 @@
  [[image:image-20240219115718-1.png]]
--=== 3.6.3 Digital Output Ports: DO1/DO2 ===
++=== 3.6.3 Digital Output Ports: DO1/DO2 /DO3 ===
  (% style="color:blue" %)**NPN output**(%%): GND or Float. The maximum voltage that can be applied to the output pin is 36V.
@@ -2217,11 +2217,10 @@
  == 3.7 LEDs Indicators ==
--The table below lists the behavior of LED indicators for each port function.
  (% 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
++|**PWR**|Always on if there is power
  |**TX**|(((
  (((
  Device boot: TX blinks 5 times.
@@ -2228,7 +2228,7 @@
  )))
  (((
--Successful network join: TX remains ON for 5 seconds.
++Successful join network: TX ON for 5 seconds.
  )))
  (((
@@ -2235,7 +2235,7 @@
  Transmit a LoRa packet: TX blinks once
  )))
  )))
--|**RX**|RX blinks once when a packet is received.
++|**RX**|RX blinks once when receiving a packet.
  |**DO1**|For LT-22222-L: ON when DO1 is low, OFF when DO1 is high
  |**DO2**|For LT-22222-L: ON when DO2 is low, OFF when DO2 is high
  |**DI1**|(((
@@ -2255,10 +2255,9 @@
  (((
  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]]
  (((
@@ -2275,21 +2275,21 @@
  )))
  (((
--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.
++The following is the list of all the AT commands related to the LT-22222-L, except for those used for switching between work modes.
--* **##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+<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+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
@@ -2334,28 +2334,28 @@
  (((
--(% style="color:blue" %)**If the device has not yet joined the network:**
++(% style="color:blue" %)**If the device has not joined the network yet:**
  )))
  )))
  (((
--(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**##
++(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**##
  )))
  (((
--(% style="background-color:#dcdcdc" %)##**AT+FDR ~/~/Reset parameters to factory default, Reserve keys**##
++(% style="background-color:#dcdcdc" %)##**AT+FDR ~/~/reset parameters to factory default, reserve keys**##
  )))
  (((
--(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**##
++(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**##
  )))
  (((
--(% 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" %)##**ATZ ~/~/Reset MCU**##
++(% style="background-color:#dcdcdc" %)##**ATZ ~/~/reset MCU**##
  )))
@@ -2378,20 +2378,20 @@
  (((
--(% style="background-color:#dcdcdc" %)**123456**(%%)        ~/~/ Enter password to enable AT commands access
++(% style="background-color:#dcdcdc" %)**123456**(%%)        ~/~/ Enter Password to have AT access.
  )))
  )))
  (((
--(% style="background-color:#dcdcdc" %)** AT+FDR**(%%)     ~/~/ Reset parameters to Factory Default, Reserve keys
++(% style="background-color:#dcdcdc" %)** AT+FDR**(%%)     ~/~/ Reset Parameters to Factory Default, Keys Reserve
  )))
  (((
--(% style="background-color:#dcdcdc" %)** 123456**(%%)       ~/~/ Enter password to enable AT commands access
++(% style="background-color:#dcdcdc" %)** 123456**(%%)       ~/~/ Enter Password to have AT access.
  )))
  (((
--(% style="background-color:#dcdcdc" %)** AT+CLASS=C**(%%)   ~/~/ Set to CLASS C mode
++(% style="background-color:#dcdcdc" %)** AT+CLASS=C**(%%)   ~/~/ Set to work in CLASS C
  )))
  (((
@@ -2411,19 +2411,19 @@
  )))
  (((
--(% style="background-color:#dcdcdc" %)** AT+CHS=868400000**(%%)     ~/~/ Set transmit frequency to 868.4 MHz
++(% style="background-color:#dcdcdc" %)** AT+CHS=868400000**(%%)     ~/~/ Set transmit frequency to 868.4Mhz
  )))
  (((
--(% 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+RX2FQ=868400000**(%%)    ~/~/ Set RX2Frequency to 868.4Mhz (according to the result from server)
  )))
  (((
--(% 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+RX2DR=5**(%%)** **                   ~/~/ Set RX2DR to match the downlink DR from server. see below
  )))
  (((
--(% style="background-color:#dcdcdc" %)** AT+DADDR=26 01 1A F1** (%%)     ~/~/ Set Device Address. The Device Address can be found in the application on the LoRaWAN NS.
++(% 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.
  )))
  (((
@@ -2437,14 +2437,14 @@
  )))
  (((
--**~1. Ensure that the device is set to ABP mode in the LoRaWAN Network Server.**
++**~1. Make sure the device is set to ABP mode in the IoT Server.**
--**2. Verify that the LG01/02 gateway RX frequency matches the AT+CHS setting exactly.**
++**2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.**
--**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?
++**3. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?
  dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.**
--**4. The 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.**
++**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.**
  )))
  (((
@@ -2456,7 +2456,7 @@
  (((
--(% style="color:blue" %)**If the sensor has JOINED:**
++(% style="color:blue" %)**If sensor JOINED:**
  (% style="background-color:#dcdcdc" %)**AT+CLASS=A**
@@ -2466,20 +2466,22 @@
  = 5. Case Study =
--== 5.1 Counting how many objects pass through the 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 setup counting for objects passing through the flow line>>How to set up to count objects pass in flow line]]?
++
  = 6. FAQ =
  This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
--
  == 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:
++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
  * Fix bugs
  * Change LoRaWAN frequency bands
@@ -2497,8 +2497,8 @@
  Below is the hardware setup for uploading a firmware image to the LT-22222-L:
--[[image:usb-ttl-programming.png]]
++[[image:1653359603330-121.png]]
  Start the STM32 Flash Loader and choose the correct COM port to update.
@@ -2522,7 +2522,7 @@
  [[image:image-20220524104033-15.png]]
--(% 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:
++(% style="color:red" %)**Note**(%%): If you have lost the programming cable, you can make one from a 3.5mm cable. The pin mapping is as follows:
  [[image:1653360054704-518.png||height="186" width="745"]]
@@ -2530,6 +2530,8 @@
  (((
  (((
  == 6.2 How to change the LoRaWAN frequency band/region? ==
++
++
  )))
  )))
@@ -2540,18 +2540,20 @@
  (((
--== 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
++== 6.3 How to setup LT to work with a Single Channel Gateway, such as LG01/LG02? ==
++
++
  )))
  (((
  (((
--In this case, you need to set the LT-22222-L to work in ABP mode and transmit on only one frequency.
++In this case, you need to set the LT-33222-L to work in ABP mode and transmit on only one frequency.
  )))
  )))
  (((
  (((
--We assume you have an LG01/LG02 working on the frequency 868400000. Below are the steps.
++Assume you have an LG02 working on the frequency 868400000. Below are the steps.
  )))
@@ -2558,55 +2558,52 @@
  )))
  (((
--(% 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).
++(% style="color:#0000ff" %)**Step 1**(%%):  Log in to The Things Stack SANDBOX, create an ABP device in the application, and input the Network Session key (NwkSKey), App session key (AppSKey) of the device.
--[[image:lt-22222-l-abp.png||height="686" width="1000"]]
++
  )))
  (((
++[[image:1653360231087-571.png||height="401" width="727"]]
++
  )))
--{{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:red" %)**Note: user just need to make sure above three keys match, User can change either in TTN or Device to make then match. In TTN, NETSKEY and APPSKEY can be configured by user in setting page, but Device Addr is generated by TTN.**
++)))
++
  (((
--(% style="color: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="color:blue" %)**Step2**(%%)**:  **Run AT Command to make LT work in Single frequency & ABP mode. Below is the AT commands:
  )))
  (((
--(% style="background-color:#dcdcdc" %)**123456** (%%) : Enter the password to enable AT access.
++(% style="background-color:#dcdcdc" %)**123456** (%%)   :   Enter Password to have AT access.
--(% style="background-color:#dcdcdc" %)**AT+FDR**(%%) : Reset parameters to factory default, keeping keys reserved.
++(% style="background-color:#dcdcdc" %)**AT+FDR**(%%)   :   Reset Parameters to Factory Default, Keys Reserve
--(% style="background-color:#dcdcdc" %)**AT+NJM=0** (%%) : Set to ABP mode.
++(% style="background-color:#dcdcdc" %)**AT+NJM=0** (%%) :   Set to ABP mode
--(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%) : Disable the Adaptive Data Rate (ADR).
++(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)  :  Set the Adaptive Data Rate Off
--(% style="background-color:#dcdcdc" %)**AT+DR=5** (%%) : Set Data Rate (Use AT+DR=3 for the 915 MHz band).
++(% style="background-color:#dcdcdc" %)**AT+DR=5** (%%)    :   Set Data Rate (Set AT+DR=3 for 915 band)
--(% style="background-color:#dcdcdc" %)**AT+TDC=60000 **(%%)  : Set transmit interval to 60 seconds.
++(% style="background-color:#dcdcdc" %)**AT+TDC=60000 **(%%)   :      Set transmit interval to 60 seconds
--(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) : Set transmit frequency to 868.4 MHz.
++(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) : Set transmit frequency to 868.4Mhz
--(% style="background-color:#dcdcdc" %)**AT+DADDR=xxxx**(%%) : Set the Device Address (DevAddr)
++(% style="background-color:#dcdcdc" %)**AT+DADDR=26 01 1A F1**(%%)  :  Set Device Address to 26 01 1A F1
--(% 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.
++(% 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:400; text-decoration:none; white-space:pre-wrap" %)The following figure shows the screenshot of the command set above, issued using a serial tool:
++As shown in below:
  )))
  [[image:1653360498588-932.png||height="485" width="726"]]
@@ -2614,25 +2614,27 @@
  == 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 the counting event in the serial output? ==
++
  (((
--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.
++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 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, 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]].
  )))
  (((
  == 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.
@@ -2640,6 +2640,7 @@
  == 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
++
  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:
@@ -2648,24 +2648,24 @@
  == 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.
++The firmware version must be at least 1.6.0.
++
  == 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
++
  It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
  = 7. Troubleshooting =
--
--This section provides some known troubleshooting tips.
--
--
  )))
  (((
  (((
  == 7.1 Downlink isn't working. How can I solve this? ==
++
++
  )))
  )))
@@ -2677,6 +2677,8 @@
  == 7.2 Having trouble uploading an image? ==
++
++
  )))
  (((
@@ -2687,6 +2687,8 @@
  == 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
++
++
  )))
  (((
@@ -2694,8 +2694,9 @@
  )))
--== 7.4 Why can the LT-22222-L 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"]]
@@ -2702,6 +2702,7 @@
  = 8. Ordering information =
++
  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
  (% style="color:#4f81bd" %)**XXX:**
@@ -2716,14 +2716,15 @@
  * (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865
  * (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779
--= 9. Package information =
++= 9. Packing information =
++
  **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
++* 3.5mm Programming cable x 1
  **Dimension and weight**:
@@ -2734,6 +2734,7 @@
  = 10. Support =
++
  * (((
  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.
  )))
@@ -2745,6 +2745,7 @@
  = 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,1 +1,0 @@
1		-XWiki.pradeeka

Size

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

Content

dragino-ttn-te.jpg

Author

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

Size

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

Content

lorawan-nw.jpg

Author

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

Size

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

Content

lt-22222-l-abp.png

Author

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

Size

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

Content

thingseye-json.png

Author

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

Size

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

Content

usb-ttl-programming.png

Author

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

Size

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

Content

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

Summary

Details

Applications

Navigation