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

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

From 199.1 to 200.1 From 230.16 to 231.1

From version 200.1

edited by Dilisi S
on 2024/11/18 04:06

Change comment: Nov 17 - AT Commands edit - part 3

To version 230.16

edited by Xiaoling
on 2024/12/09 10:58

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Author

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

Content

@@ -21,6 +21,7 @@
  == 1.1 What is the LT-22222-L I/O Controller? ==
++
  (((
  (((
  {{info}}
@@ -27,7 +27,7 @@
  **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,23 +40,24 @@
  (((
  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 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 Stack Community Network), you can select a network and register the LT-22222-L I/O controller with it.
  * If there is no public LoRaWAN coverage in your area, you can set up a LoRaWAN gateway, or multiple gateways, and connect them to a LoRaWAN network server to create adequate coverage. Then, register the LT-22222-L I/O controller with this network.
  * Setup your own private LoRaWAN network.
--
--{{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}}
  )))
  (((
--[[image:1653295757274-912.png]]
--
++
++The network diagram below illustrates how the LT-22222-L communicates with a typical LoRaWAN network.
  )))
++(% class="wikigeneratedid" %)
++[[image:lorawan-nw.jpg||height="354" width="900"]]
++
++
  == 1.2 Specifications ==
++
  (% style="color:#037691" %)**Hardware System:**
  * STM32L072xxxx MCU
@@ -98,6 +98,7 @@
  == 1.3 Features ==
++
  * LoRaWAN Class A & Class C modes
  * Optional Customized LoRa Protocol
  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
@@ -108,6 +108,7 @@
  == 1.4 Applications ==
++
  * Smart buildings & home automation
  * Logistics and supply chain management
  * Smart metering
@@ -115,54 +115,74 @@
  * Smart cities
  * Smart factory
--== 2. Assembling the device ==
++== 1.5 Hardware Variants ==
++
++(% border="1" cellspacing="3" style="width:510px" %)
++|(% style="background-color:#4f81bd; color:white; width:94px" %)**Model**|(% style="background-color:#4f81bd; color:white; width:172px" %)**Photo**|(% style="background-color:#4f81bd; color:white; width:244px" %)**Description**
++|(% style="width:94px" %)**LT-22222-L**|(% style="width:172px" %)(((
++(% style="text-align:center" %)
++[[image:lt33222-l.jpg||height="110" width="95"]]
++)))|(% style="width:256px" %)(((
++* 2 x Digital Input (Bi-direction)
++* 2 x Digital Output
++* 2 x Relay Output (5A@250VAC / 30VDC)
++* 2 x 0~~20mA Analog Input (res:0.01mA)
++* 2 x 0~~30V Analog Input (res:0.01v)
++* 1 x Counting Port
++)))
++
++= 2. Assembling the device =
++
  == 2.1 Connecting the antenna ==
++
  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.
  {{warning}}
--Warning! Do not power on the device without connecting the antenna.
++**Warning! Do not power on the device without connecting the antenna.**
  {{/warning}}
++
  == 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):
++The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals.
--(% style="width:634px" %)
--|=(% style="width: 295px;" %)Terminal|=(% style="width: 338px;" %)Function
--|(% style="width:295px" %)GND|(% style="width:338px" %)Ground
--|(% style="width:295px" %)VIN|(% style="width:338px" %)Input Voltage
--|(% style="width:295px" %)AVI2|(% style="width:338px" %)Analog Voltage Input Terminal 2
--|(% style="width:295px" %)AVI1|(% style="width:338px" %)Analog Voltage Input Terminal 1
--|(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2
--|(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1
++**Upper screw terminal block (from left to right):**
--Lower screw terminal block (from left to right):
++(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:381px" %)
++|=(% style="width: 139px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 242px;background-color:#4f81bd;color:white" %)Function
++|(% style="width:139px" %)GND|(% style="width:242px" %)Ground
++|(% style="width:139px" %)VIN|(% style="width:242px" %)Input Voltage
++|(% style="width:139px" %)AVI2|(% style="width:242px" %)Analog Voltage Input Terminal 2
++|(% style="width:139px" %)AVI1|(% style="width:242px" %)Analog Voltage Input Terminal 1
++|(% style="width:139px" %)ACI2|(% style="width:242px" %)Analog Current Input Terminal 2
++|(% style="width:139px" %)ACI1|(% style="width:242px" %)Analog Current Input Terminal 1
--(% style="width:633px" %)
--|=(% style="width: 296px;" %)Terminal|=(% style="width: 334px;" %)Function
--|(% style="width:296px" %)RO1-2|(% style="width:334px" %)Relay Output 1
--|(% style="width:296px" %)RO1-1|(% style="width:334px" %)Relay Output 1
--|(% style="width:296px" %)RO2-2|(% style="width:334px" %)Relay Output 2
--|(% style="width:296px" %)RO2-1|(% style="width:334px" %)Relay Output 2
--|(% style="width:296px" %)DI2+|(% style="width:334px" %)Digital Input 2
--|(% style="width:296px" %)DI2-|(% style="width:334px" %)Digital Input 2
--|(% style="width:296px" %)DI1+|(% style="width:334px" %)Digital Input 1
--|(% style="width:296px" %)DI1-|(% style="width:334px" %)Digital Input 1
--|(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
--|(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
++**Lower screw terminal block (from left to right):**
--== 2.3 Powering the device ==
++(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:253px" %)
++|=(% style="width: 125px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 128px;background-color:#4f81bd;color:white" %)Function
++|(% style="width:125px" %)RO1-2|(% style="width:128px" %)Relay Output 1
++|(% style="width:125px" %)RO1-1|(% style="width:128px" %)Relay Output 1
++|(% style="width:125px" %)RO2-2|(% style="width:128px" %)Relay Output 2
++|(% style="width:125px" %)RO2-1|(% style="width:128px" %)Relay Output 2
++|(% style="width:125px" %)DI2+|(% style="width:128px" %)Digital Input 2
++|(% style="width:125px" %)DI2-|(% style="width:128px" %)Digital Input 2
++|(% style="width:125px" %)DI1+|(% style="width:128px" %)Digital Input 1
++|(% style="width:125px" %)DI1-|(% style="width:128px" %)Digital Input 1
++|(% style="width:125px" %)DO2|(% style="width:128px" %)Digital Output 2
++|(% style="width:125px" %)DO1|(% style="width:128px" %)Digital Output 1
--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.
--Once powered, 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. The **TX LED** will be on for **5 seconds** after joining the network. When there is a **downlink** message from the server, the **RX LED** 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.
++== 2.3 Connecting LT-22222-L to a Power Source ==
++
++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.
++
  {{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.
++**We recommend that you power on the LT-22222-L after adding its registration information to the LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.**
  {{/warning}}
@@ -169,37 +169,59 @@
  [[image:1653297104069-180.png]]
--= 3. Registering with a LoRaWAN Network Server =
++= 3. Registering LT-22222-L with a LoRaWAN Network Server =
--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.
--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 LED** 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 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.
--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.
--The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
--
--[[image:image-20220523172350-1.png||height="266" width="864"]]
--
  === 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 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.2 The Things Stack Sandbox (TTSS) ===
++=== 3.2.2 The Things Stack ===
++
++
++This section guides you through how to register your LT-22222-L with The Things Stack Sandbox.
++
++{{info}}
  The Things Stack Sandbox was formally called The Things Stack Community Edition.
++{{/info}}
--* Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account.
--* Create an application with The Things Stack if you do not have one yet.
--* Go to your application page and click on the **End devices** in the left menu.
++
++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:dragino-lorawan-nw-lt-22222-n.jpg||height="374" width="1400"]]
++
++{{info}}
++ You can use a LoRaWAN gateway, such as the [[Dragino LPS8N>>https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]], to expand or create LoRaWAN coverage in your area.
++{{/info}}
++
++
++==== 3.2.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 ====
++
++
  * 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.
@@ -210,7 +210,7 @@
  *** **Profile (Region)**: Select the region that matches your device.
  ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
--[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
++[[image:lt-22222-l-dev-repo-reg-p1.png]]
  * Register end device page continued...
@@ -220,12 +220,12 @@
  ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
  ** Under **After registration**, select the **View registered end device** option.
--[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
++[[image:lt-22222-l-dev-repo-reg-p2.png]]
--====   ====
--==== 3.2.2.2 Adding device manually ====
++==== 3.2.2.3 Adding device 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.
@@ -235,11 +235,11 @@
  ** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
  ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
--[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
++[[image:lt-22222-l-manually-p1.png]]
  * 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'
++** 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.
@@ -246,41 +246,57 @@
  ** Under **After registration**, select the **View registered end device** option.
  ** Click the **Register end device** button.
--[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
++[[image:lt-22222-l-manually-p2.png]]
  You will be navigated to the **Device overview** page.
--[[image:lt-22222-device-overview.png||height="625" width="1000"]]
++[[image:lt-22222-device-overview.png]]
--==== 3.2.2.3 Joining ====
++==== 3.2.2.4 Joining ====
--On the Device overview page, click on **Live data** tab. The Live data panel for your device will display.
--Now power on your LT-22222-L. It will begin joining The Things Stack. 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**).
++On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
++Now power on your LT-22222-L. The **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** The Things Stack network server. The **TX LED** will be on for **5 seconds** after joining the network. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server.
--[[image:lt-22222-join-network.png||height="625" width="1000"]]
++[[image:lt-22222-l-joining.png]]
--By default, you will receive an uplink data message from the device every 10 minutes.
++==== 3.2.2.5 Uplinks ====
++
++
++After successfully joining, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**). When the LT-22222-L sends an uplink message to the server, the **TX LED** turns on for **1 second**. By default, you will receive an uplink data message from the device every 10 minutes.
++
  Click on one of a **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the decode_payload {} JSON object.
  [[image:lt-22222-ul-payload-decoded.png]]
--If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **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.
++If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **Applications > your application > End devices** > **your  end device** > **Payload formatters** > **Uplink**. Then  select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
  {{info}}
  The Things Stack provides two levels of payload formatters: application level and device level. The device-level payload formatters **override **the application-level payload formatters.
  {{/info}}
--[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
++[[image:lt-22222-ul-payload-fmt.png]]
++We also have a payload formatter that resolves some decoding issues present in the Device Repository formatter. You can add it under the Custom JavaScript formatter. It can be found [[here>>https://github.com/dragino/dragino-end-node-decoder/blob/main/LT22222-L/v1.6_decoder_ttn%20.txt]]:
++
++(% class="wikigeneratedid" %)
++[[image:lt-22222-l-js-custom-payload-formatter.png]]
++
++
++==== 3.2.2.6 Downlinks ====
++
++
++When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
++
++
  == 3.3 Working Modes and Uplink Payload formats ==
@@ -300,8 +300,10 @@
  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 ===
++
  (((
  This is the default mode.
@@ -374,6 +374,7 @@
  MOD = 1
++
  === 3.3.2 AT+MOD~=2, (Double DI Counting) ===
@@ -452,6 +452,7 @@
  === 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.**
@@ -505,6 +505,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.**
@@ -556,24 +556,25 @@
  )))
  (((
--Other AT Commands for counting are similar to the [[MOD2 Counting Command>>||anchor="H3.3.2AT2BMOD3D22C28DoubleDICounting29"]]s.
++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 AVI Count to 60)**
++(% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)**
--(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
++(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), the counter increases by 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 the AVI1 voltage is lower than VOLMAX (20000mV =20V), counter increases by 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 the AVI1 voltage is higher than VOLMAX (20000mV =20V), counter increases by 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.**
@@ -687,9 +687,9 @@
  (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
--Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
++**Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
--Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
++**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
    AA: Type Code for this downlink Command:
@@ -718,7 +718,7 @@
  MOD6 Payload: total of 11 bytes
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
++(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
  |(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:69px" %)**1**|(% style="background-color:#4f81bd; color:white; width:69px" %)**1**|(% style="background-color:#4f81bd; color:white; width:109px" %)**1**|(% style="background-color:#4f81bd; color:white; width:49px" %)**6**|(% style="background-color:#4f81bd; color:white; width:109px" %)**1**|(% style="background-color:#4f81bd; color:white; width:50px" %)**1**
  |Value|(((
  TRI_A FLAG
@@ -732,7 +732,7 @@
  (% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
++(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
  |(((
  AV1_LOW
@@ -756,12 +756,12 @@
  **Example:**
--10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW
++10100000: This means the system is configured to use the triggers AV1_LOW and AV2_LOW.
  (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
++(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
  |(((
  AV1_LOW
@@ -785,31 +785,31 @@
  **Example:**
--10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.
++10000000: The uplink is triggered by AV1_LOW, indicating that the voltage is too low.
  (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width: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="3" style="background-color:#f2f2f2; width:515px" %)
++|(% style="width:50px" %)**bit 7**|(% style="width:50px" %)**bit 6**|(% style="width:50px" %)**bit 5**|(% style="width:50px" %)**bit 4**|(% style="width:90px" %)**bit 3**|(% style="width:80px" %)**bit 2**|(% style="width:90px" %)**bit 1**|(% style="width:95px" %)**bit 0**
++|(% style="width:49px" %)N/A|(% style="width:53px" %)N/A|(% style="width:53px" %)N/A|(% style="width:55px" %)N/A|(% style="width:99px" %)DI2_STATUS|(% style="width:83px" %)DI2_FLAG|(% style="width:98px" %)DI1_STATUS|(% style="width:85px" %)DI1_FLAG
--* Each bits shows which status has been triggered on this uplink.
++* Each bit shows which status has been triggered on this uplink.
  **Example:**
--00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
++00000111: This means both DI1 and DI2 triggers are enabled, and this packet is trigger by DI1.
--00000101: Means both DI1 and DI2 trigger are enabled.
++00000101: This means both DI1 and DI2 triggers are enabled.
--(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable.
++(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled.
--Downlink command to poll MOD6 status:
++Downlink command to poll/request MOD6 status:
  **AB 06**
--When device got this command, it will send the MOD6 payload.
++When device receives this command, it will send the MOD6 payload.
  === 3.3.7 Payload Decoder ===
@@ -823,6 +823,7 @@
  == 3.4 Configure LT-22222-L via AT Commands or Downlinks ==
++
  (((
  You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks.
  )))
@@ -837,19 +837,25 @@
  * (% style="color:blue" %)**Sensor-related 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.
++
++
  )))
  === 3.4.2 Sensor-related commands ===
++
  These commands are specially designed for the LT-22222-L. Commands can be sent to the device using options such as an AT command or a LoRaWAN downlink payload.
--==== 3.4.2.1 Set Transmit Interval ====
++==== 3.4.2.1 Set Transmit/Uplink Interval ====
++
  Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
  (% style="color:#037691" %)**AT command**
@@ -856,12 +856,19 @@
  (% border="2" style="width:500px" %)
  |**Command**|AT+TDC=<time>
--|**Response**|
--|**Parameters**|**time** : uplink interval is in milliseconds
++|**Parameters**|**time **: uplink interval in milliseconds
++|**Get**|AT+TDC=?
++|**Response**|(((
++current uplink interval
++
++OK
++)))
++|**Set**|AT+TDC=<time>
++|**Response**|OK
  |**Example**|(((
  AT+TDC=30000
--Sets the uplink interval to 30,000 milliseconds (30 seconds)
++Sets the uplink interval to **30 seconds** (30000 milliseconds)
  )))
  (% style="color:#037691" %)**Downlink payload**
@@ -873,27 +873,29 @@
  |**Parameters**|(((
  **prefix** : 0x01
--**time** : uplink interval is in milliseconds, represented by 3  bytes in hexadecimal.
++**time** : uplink interval in **seconds**, represented by **3  bytes** in **hexadecimal**.
  )))
  |**Example**|(((
--01 **00 75 30**
++01 **00 00 1E**
--Sets the uplink interval to 30,000 milliseconds (30 seconds)
++Sets the uplink interval to **30 seconds**
--Conversion: 30000 (dec) = 00 75 30 (hex)
++Conversion: 30 (dec) = 00 00 1E (hex)
--See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]]
++See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30]]
++
++[[image:Screenshot 2024-11-23 at 18.27.11.png]]
  )))
  ==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
++
  Sets the working mode.
  (% style="color:#037691" %)**AT command**
  (% 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" %)**Command**|(% style="width:413px" %)AT+MOD=<working_mode>
  |(% style="width:97px" %)**Parameters**|(% style="width:413px" %)(((
  **working_mode** :
@@ -909,6 +909,18 @@
 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5
  )))
++|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=?
++|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
++Current working mode
++
++OK
++)))
++|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode>
++|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
++Attention:Take effect after ATZ
++
++OK
++)))
  |(% style="width:97px" %)**Example**|(% style="width:413px" %)(((
  AT+MOD=2
@@ -931,13 +931,14 @@
  Sets the device to working mode 2 (Double DI Counting + DO + RO)
  )))
--==== 3.4.2.3 Poll an uplink ====
++==== 3.4.2.3 Request an uplink from the device ====
--Requests an uplink from LT-22222-L.
++Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.
++
  (% style="color:#037691" %)**AT command**
--There is no AT Command to request an uplink from LT-22222-L
++There is no AT Command available for this feature.
  (% style="color:#037691" %)**Downlink payload**
@@ -945,7 +945,7 @@
  |(% 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
++08 **FF**
  Requests an uplink from LT-22222-L.
  )))
@@ -952,6 +952,7 @@
  ==== 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**
@@ -979,7 +979,7 @@
  |(% style="width:97px" %)**Parameters**|(% style="width:401px" %)(((
  **prefix** : 0x0A 06 (two bytes in hexadecimal)
--**working mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
++**enable/disable trigger_mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
  )))
  |(% style="width:97px" %)**Example**|(% style="width:401px" %)(((
 A 06 **01**
@@ -987,13 +987,14 @@
  Enable trigger mode for the current working mode
  )))
--==== 3.4.2.5 Poll trigger settings ====
++==== 3.4.2.5 Request trigger settings ====
--Polls the trigger settings.
++Requests the trigger settings.
++
  (% style="color:#037691" %)**AT Command:**
--There is no AT Command for this feature.
++There is no AT Command available for this feature.
  (% style="color:#037691" %)**Downlink Payload**
@@ -1008,6 +1008,7 @@
  ==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ====
++
  Enable or disable DI1/DI2/DI3 as a trigger.
  (% style="color:#037691" %)**AT Command**
@@ -1062,9 +1062,9 @@
  ==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ====
++
  Sets DI1 or DI3 (for LT-33222-L) as a trigger.
--
  (% style="color:#037691" %)**AT Command**
  (% border="2" style="width:500px" %)
@@ -1101,9 +1101,9 @@
  ==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
++
  Sets DI2 as a trigger.
--
  (% style="color:#037691" %)**AT Command**
  (% border="2" style="width:500px" %)
@@ -1133,11 +1133,9 @@
  )))
  |(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64**
--(% class="wikigeneratedid" %)
--====   ====
--
  ==== 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**
@@ -1187,6 +1187,7 @@
  ==== 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**
@@ -1210,7 +1210,6 @@
  )))
  |(% 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" %)
@@ -1233,9 +1233,9 @@
  )))
  |(% 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**
@@ -1269,9 +1269,9 @@
  )))
  |(% 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**
@@ -1302,11 +1302,11 @@
  (((
 : Low,  00: High,  11: No action
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
--|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**DO1**|(% style="background-color:#4f81bd; color:white" %)**DO2**|(% style="background-color:#4f81bd; color:white" %)**DO3**
--|02  01  00  11|Low|High|No Action
--|02  00  11  01|High|No Action|Low
--|02  11  01  00|No Action|Low|High
++(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:383px" %)
++|(% style="background-color:#4f81bd; color:white; width:126px" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white; width:85px" %)**DO1**|(% style="background-color:#4f81bd; color:white; width:86px" %)**DO2**|(% style="background-color:#4f81bd; color:white; width:86px" %)**DO3**
++|(% style="width:126px" %)02  01  00  11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action
++|(% style="width:126px" %)02  00  11  01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low
++|(% style="width:126px" %)02  11  01  00|(% style="width:85px" %)No Action|(% style="width:86px" %)Low|(% style="width:86px" %)High
  )))
  (((
@@ -1320,33 +1320,28 @@
  )))
  )))
--(% class="wikigeneratedid" %)
--====   ====
--
  ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
  * (% style="color:#037691" %)**AT Command**
--There is no AT Command to control Digital Output
++There is no AT command to control the digital output.
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
--(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Set DO1/DO2/DO3 output with time control
++(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control
--
  This is to control the digital output time of DO pin. Include four bytes:
--(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
++(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)
--(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode
++(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode
--01: DO pins will change back to original state after timeout.
++**01:** DO pins revert to their original state after the timeout.
++**00:** DO pins switch to an inverted state after the timeout.
--00: DO pins will change to an inverter state after timeout
--
  (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
@@ -1355,7 +1355,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 Port status:
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
  |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
@@ -1363,7 +1363,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 Port status:
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
  |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
@@ -1371,7 +1371,7 @@
  |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, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms)
  (% style="color:red" %)**Note: **
@@ -1380,7 +1380,7 @@
     Before firmware v1.6.0, the latch time only supported 2 bytes.
--(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
++(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
  **Example payload:**
@@ -1407,16 +1407,16 @@
  * (% style="color:#037691" %)**AT Command:**
--There is no AT Command to control Relay Output
++There is no AT Command to control the Relay Output
  * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
--(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Set RO1/RO2 output
++(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Sets RO1/RO2 output
  (((
--If payload is 0x030100, it means setting RO1 to close and RO2 to open.
++If the payload is 0x030100, it means setting RO1 to close and RO2 to open.
  )))
  (((
@@ -1434,28 +1434,29 @@
  |03  00  01|Open|Close
  )))
--(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
++(% style="color:red" %)**The device will uplink a packet if the 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:**
--There is no AT Command to control Relay Output
++There is no AT Command to control the Relay Output
  * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
--(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Set RO1/RO2 relay with time control
++(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
--This is to control the relay output time. It includes four bytes:
++This controls the relay output time and includes 4 bytes:
--(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
++(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)
--(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
++(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode
 : Relays will change back to their original state after timeout.
@@ -1462,12 +1462,12 @@
 : Relays will change to the inverter state after timeout.
--(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
++(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status:
  [[image:image-20221008095908-1.png||height="364" width="564"]]
--(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms
++(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes (cc)**(%%): Latching time. Unit: ms
  (% style="color:red" %)**Note:**
@@ -1477,7 +1477,7 @@
     Before firmware v1.6.0, the latch time only supported 2 bytes.
--(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
++(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
  **Example payload:**
@@ -1505,159 +1505,395 @@
  When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
--* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX   ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
++(% style="color:#037691" %)**AT Command**
--* (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):**
++(% 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
--(% style="color:blue" %)**0xA5 aa bb cc   ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc
++**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 AV1 count. Use the AT command to set the desired count number for each configuration.
++This command allows users to pre-configure specific count numbers for various counting parameters such as Count1, Count2, or AVI1 Count. Use the AT command to set the desired count number for each configuration.
--* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) **
++(% style="color:#037691" %)**AT Command**
--(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count
++(% 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** :
--(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set
++1: COUNT1
++2: COUNT2
--* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):**
++3: AVI1 Count
--(% style="color:blue" %)**0x A8 aa bb cc dd ee     ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee)
++**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.
++This command clears the counting in counting mode.
--* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT         **(%%) ~/~/ clear all counting
++(% style="color:#037691" %)**AT Command**
--* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):**
++(% border="2" style="width:500px" %)
++|(% style="width:142px" %)**Command**|(% style="width:356px" %)AT+CLRCOUNT
++|(% style="width:142px" %)**Response**|(% style="width:356px" %)-
--(% style="color:blue" %)**0x A6 01    ** (%%)~/~/ clear all counting
++(% 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 ====
++==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ====
--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:**
++This command allows you to configure the device to save its counting result to internal flash memory at specified intervals. By setting a save time, the device will periodically store the counting data to prevent loss in case of power failure. The save interval can be adjusted to suit your requirements, with a minimum value of 30 seconds.
--(% style="color:blue" %)**AT+COUTIME=60  **(%%)~/~/ Sets the save time to 60 seconds. The device will save the counting result in internal flash every 60 seconds. (Min value: 30 seconds)
++(% style="color:#037691" %)**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
--* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):**
++Sets the device to save its counting results to the memory every 60 seconds.
++)))
--(% style="color:blue" %)**0x A7 aa bb cc     ** (%%)~/~/ same as AT+COUTIME =aa bb cc,
++(% style="color:#037691" %)**Downlink Payload**
--(((
--Range: aa bb cc:0 to 16777215,  (unit: seconds)
++(% 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 saved RO and DO states ====
--==== 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.
++This command allows you to reset the saved relay output (RO) and digital output (DO) states when the device joins the network. By configuring this setting, you can control whether the device should retain or reset the relay states after a reset and rejoin to the network.
--* (% style="color:#037691" %)**AT Command:**
++(% style="color:#037691" %)**AT Command**
--(% style="color:blue" %)**AT+RODORESET=1    **(%%)~/~/ RODO will close when the device joining the network. (default)
++(% 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** :
--(% 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.
++**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 **
--* (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):**
++RODO will close when the device joins the network. (default)
--(% style="color:blue" %)**0x AD aa      ** (%%)~/~/ same as AT+RODORET =aa
++(% 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.
++)))
++(% style="color:#037691" %)**Downlink Payload**
++(% 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:**
++This command allows you to configure whether the device should upload data in an encrypted format or in plaintext. By default, the device encrypts the payload before uploading. You can toggle this setting to either upload encrypted data or transmit it without encryption.
--(% style="color:blue" %)**AT+DECRYPT=1  **   (%%)~/~/ The payload is uploaded without encryption
++(% style="color:#037691" %)**AT Command:**
--(% style="color:blue" %)**AT+DECRYPT=0    **(%%)~/~/  Encrypt when uploading payload (default)
++(% border="2" style="width:500px" %)
++|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state>
++|(% style="width:127px" %)**Response**|(% style="width:371px" %)
++|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
++**state** :
++**1** : The payload is uploaded without encryption
++**0** : The payload is encrypted when uploaded (default)
++)))
++|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
++AT+DECRYPT=1
++The payload is uploaded without encryption
++
++AT+DECRYPT=0
++
++The payload is encrypted when uploaded (default)
++)))
++
++There is no downlink payload for this configuration.
++
++
  ==== 3.4.2.22 Get sensor value ====
--* (% style="color:#037691" %)**AT Command:**
++This command allows you to retrieve and optionally uplink sensor readings through the serial port.
--(% style="color:blue" %)**AT+GETSENSORVALUE=0    **(%%)~/~/ The serial port retrieves the reading of the current sensor.
++(% style="color:#037691" %)**AT Command**
--(% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it.
++(% border="2" style="width:500px" %)
++|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state>
++|(% style="width:127px" %)**Response**|(% style="width:371px" %)
++|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
++**state** :
++**0 **: Retrieves the current sensor reading via the serial port.
++**1 **: Retrieves and uploads the current sensor reading via the serial port.
++)))
++|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
++AT+GETSENSORVALUE=0
--==== 3.4.2.23 Resets the downlink packet count ====
++Retrieves the current sensor reading via the serial port.
++AT+GETSENSORVALUE=1
--* (% style="color:#037691" %)**AT Command:**
++Retrieves and uplinks the current sensor reading via the serial port.
++)))
--(% style="color:blue" %)**AT+DISFCNTCHECK=0   **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node will no longer receive downlink packets (default)
++There is no downlink payload for this configuration.
--(% style="color:blue" %)**AT+DISFCNTCHECK=1   **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node resets the downlink packet count and keeps it consistent with the server downlink packet count.
++==== 3.4.2.23 Resetting the downlink packet count ====
++This command manages how the node handles mismatched downlink packet counts. It offers two modes: one disables the reception of further downlink packets if discrepancies occur, while the other resets the downlink packet count to align with the server, ensuring continued communication.
++
++(% style="color:#037691" %)**AT Command**
++
++(% border="2" style="width:500px" %)
++|(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state>
++|(% style="width:130px" %)**Response**|(% style="width:368px" %)(((
++
++)))
++|(% style="width:130px" %)**Parameters**|(% style="width:368px" %)(((
++**state **:
++
++**0** : When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node stops receiving further downlink packets (default).
++
++
++**1** : When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node resets its downlink packet count to match the server's, ensuring consistency.
++)))
++|(% style="width:130px" %)**Example**|(% style="width:368px" %)(((
++AT+DISFCNTCHECK=0
++
++When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node stops receiving further downlink packets (default).
++
++AT+DISFCNTCHECK=1
++
++When the downlink packet count sent by the server is less than the node's downlink packet count or exceeds 16,384, the node resets its downlink packet count to match the server's, ensuring consistency.
++)))
++
++There is no downlink payload for this configuration.
++
++
  ==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ====
--* (% style="color:#037691" %)**AT Command:**
++This command controls the behavior of the node when the combined size of the MAC commands (MACANS) from the server and the payload exceeds the allowed byte limit for the current data rate (DR). The command provides two modes: one enables splitting the data into batches to ensure compliance with the byte limit, while the other prioritizes the payload and ignores the MACANS in cases of overflow.
--(% style="color:blue" %)**AT+DISMACANS=0**   (%%)  ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of 11 bytes (DR0 of US915, DR2 of AS923, DR2 of AU195), the node will send a packet with a payload of 00 and a port of 4. (default)
++(% style="color:#037691" %)**AT Command**
--(% style="color:blue" %)**AT+DISMACANS=1**  (%%)    ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of the DR, the node will ignore the MACANS and not reply, and only upload the payload part.
++(% border="2" style="width:500px" %)
++|(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DISMACANS=<state>
++|(% style="width:127px" %)**Response**|(% style="width:371px" %)
++|(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
++**state** :
++**0** : When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default)
--* (% style="color:#037691" %)**Downlink Payload **(%%)**:**
++**1** : When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload.
++)))
++|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
++AT+DISMACANS=0
--(% style="color:blue" %)**0x21 00 01 **   (%%)      ~/~/ Set  the DISMACANS=1
++When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default)
++AT+DISMACANS=1
++When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload.
++)))
++(% style="color:#037691" %)**Downlink Payload**
++
++(% border="2" style="width:500px" %)
++|(% style="width:126px" %)**Payload**|(% style="width:372px" %)<prefix><state>
++|(% style="width:126px" %)**Parameters**|(% style="width:372px" %)(((
++**prefix** : 21
++
++**state** : (2 bytes in hexadecimal)
++
++**0** : When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default)
++
++**1 **: When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload.
++)))
++|(% style="width:126px" %)**Example**|(% style="width:372px" %)(((
++21 **00 01**
++
++Set DISMACANS=1
++)))
++
  ==== 3.4.2.25 Copy downlink to uplink ====
--* (% style="color:#037691" %)**AT Command**(%%)**:**
++This command enables the device to immediately uplink the payload of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100.
--(% style="color:blue" %)**AT+RPL=5**   (%%)  ~/~/ After receiving the package from the server, it will immediately upload the content of the package to the server, the port number is 100.
++(% style="color:#037691" %)**AT Command**(%%)**:**
--Example：**aa xx xx xx xx**         ~/~/ aa indicates whether the configuration has changed, 00 is yes, 01 is no; xx xx xx xx are the bytes sent.
++(% style="color:blue" %)**AT+RPL=5**   (%%)  ~/~/ After receiving a downlink payload from the server, the device will immediately uplink the payload back to the server using port number 100.
++Example：**aa xx xx xx xx**         ~/~/ **aa** indicates whether the configuration has changed: **00** means YES, and **01** means NO. **xx xx xx xx** are the bytes uplinked back.
++
  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173747-6.png?width=1124&height=165&rev=1.1||alt="image-20220823173747-6.png"]]
  For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
--
--
  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]]
  For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
++(% style="color:#037691" %)**Downlink Payload**(%%)**:**
--==== 3.4.2.26 Query version number and frequency band 、TDC ====
++There is no downlink option available for this feature.
++==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
++
++
++This command is used to query key information about the device, including its firmware version, frequency band, sub band, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device.
++
  * (((
  (% style="color:#037691" %)**Downlink Payload**(%%)**:**
--(% style="color:blue" %)**26 01  ** (%%)  ~/~/  Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.
++(% style="color:blue" %)**26 01  ** (%%)  ~/~/  The downlink payload 26 01 is used to query the device's firmware version, frequency band, sub band, and TDC time.
++
  )))
@@ -1668,10 +1668,13 @@
  == 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.
++
  === 3.5.1 Configuring The Things Stack ===
++
  We use The Things Stack Sandbox in this example:
  * In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
@@ -1683,15 +1683,19 @@
  The username and  password (API key) you created here are required in the next section.
  {{/info}}
--[[image:tts-mqtt-integration.png||height="625" width="1000"]]
++[[image:tts-mqtt-integration.png]]
++
  === 3.5.2 Configuring ThingsEye.io ===
++
++The ThingsEye.io IoT platform is not open for self-registration at the moment. If you are interested in testing the platform, please send your project information to admin@thingseye.io, and we will create an account for you.
++
  * Login to your [[ThingsEye.io >>https://thingseye.io]]account.
  * Under the **Integrations center**, click **Integrations**.
  * Click the **Add integration** button (the button with the **+** symbol).
--[[image:thingseye-io-step-1.png||height="625" width="1000"]]
++[[image:thingseye-io-step-1.png]]
  On the **Add integration** window, configure the following:
@@ -1706,7 +1706,7 @@
  ** Allow create devices or assets
  * Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
--[[image:thingseye-io-step-2.png||height="625" width="1000"]]
++[[image:thingseye-io-step-2.png]]
  **Uplink data converter:**
@@ -1717,7 +1717,7 @@
  * Paste the uplink decoder function into the text area (first, delete the default code). The demo uplink decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Uplink_Converter.js]].
  * Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
--[[image:thingseye-io-step-3.png||height="625" width="1000"]]
++[[image:thingseye-io-step-3.png]]
  **Downlink data converter (this is an optional step):**
@@ -1728,7 +1728,7 @@
  * Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Downlink_Converter.js]].
  * Click the **Next** button. You will be navigated to the **Connection** tab.
--[[image:thingseye-io-step-4.png||height="625" width="1000"]]
++[[image:thingseye-io-step-4.png]]
  **Connection:**
@@ -1735,7 +1735,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 **3.5.1 Configuring The Things Stack**).
  * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
  [[image:message-1.png]]
@@ -1743,54 +1743,64 @@
  * Click the **Add** button.
--[[image:thingseye-io-step-5.png||height="625" width="1000"]]
++[[image:thingseye-io-step-5.png]]
--Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings.
++Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings and correct any errors.
--[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
++[[image:thingseye.io_integrationsCenter_integrations.png]]
  ==== 3.5.2.1 Viewing integration details ====
++
  Click on your integration from the list. The **Integration details** window will appear with the **Details **tab selected. The **Details **tab shows all the settings you have provided for this integration.
--[[image:integration-details.png||height="686" width="1000"]]
++[[image:integration-details.png]]
  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.
++See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
  {{/info}}
--==== **3.5.2.2 Viewing events** ====
++==== 3.5.2.2 Viewing events ====
++
++
  The **Events **tab displays all the uplink messages from the LT-22222-L.
  * Select **Debug **from the **Event type** dropdown.
  * Select the** time frame** from the **time window**.
--[[image:thingseye-events.png||height="686" width="1000"]]
++[[image:thingseye-events.png]]
--* 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.
--[[image:thingseye-json.png||width="1000"]]
++[[image:thingseye-json.png]]
--==== **3.5.2.3 Deleting an integration** ====
++==== 3.5.2.3 Deleting an integration ====
++
  If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
++==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
++
++
++This will be added soon.
++
++
  == 3.6 Interface Details ==
  === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
--Supports NPN-type sensors.
++Supports** NPN-type **sensors.
  [[image:1653356991268-289.png]]
@@ -1912,15 +1912,15 @@
  )))
--(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
++(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor
--From the DI port circuit above, you can see that activating the photocoupler requires a voltage difference between the DI+ and DI- ports. However, the Dry Contact sensor is a passive component and cannot provide this voltage difference.
++From the DI port circuit above, activating the photocoupler requires a voltage difference between the DI+ and DI- ports. However, the Dry Contact sensor is a passive component and cannot provide this voltage difference on its own.
--To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram.
++To detect a Dry Contact, you can supply a power source to one of the pins of the Dry Contact. A reference circuit diagram is shown below.
  [[image:image-20230616235145-1.png]]
--(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
++(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector
  [[image:image-20240219115718-1.png]]
@@ -1996,8 +1996,9 @@
  [[image:image-20220524100215-10.png||height="382" width="723"]]
--== 3.7 LEDs Indicators ==
++== 3.7 LED Indicators ==
++
  The table below lists the behavior of LED indicators for each port function.
  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
@@ -2030,18 +2030,22 @@
  = 4. Using AT Commands =
++
  The LT-22222-L supports programming using AT Commands.
++
  == 4.1 Connecting the LT-22222-L to a PC ==
++
  (((
--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.
++You can use a USB-to-TTL adapter/converter 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:usb-ttl-audio-jack-connection.jpg]]
++
++
  )))
--
  (((
  On the PC, you need to set the (% style="color:#4f81bd" %)**serial tool **(%%)(such as [[PuTTY>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]] or [[SecureCRT>>https://www.vandyke.com/cgi-bin/releases.php?product=securecrt]]) to a baud rate of (% style="color:green" %)**9600**(%%) to access the serial console of LT-22222-L. Access to AT commands is disabled by default, and a password (default: (% style="color:green" %)**123456**)(%%) must be entered to enable AT command access, as shown below:
  )))
@@ -2052,7 +2052,10 @@
  (((
  You can find more details in the [[AT Command Manual>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
++
  == 4.2 LT-22222-L related AT commands ==
++
++
  )))
  (((
@@ -2071,39 +2071,39 @@
  * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
  * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
  * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
--* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
--* AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)
--* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
--* AT+PNM: Get or set the public network mode. (0: off, 1: on)
--* AT+RX2FQ: Get or set the Rx2 window frequency
--* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
--* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
--* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
--* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
--* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
--* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
--* AT+NWKID: Get or set the Network ID
--* AT+FCU: Get or set the Frame Counter Uplink (FCntUp)
--* AT+FCD: Get or set the Frame Counter Downlink (FCntDown)
--* AT+CLASS: Get or set the Device Class
--* AT+JOIN: Join network
--* AT+NJS: Get OTAA Join Status
--* AT+SENDB: Send hexadecimal data along with the application port
--* AT+SEND: Send text data along with the application port
--* AT+RECVB: Print last received data in binary format (with hexadecimal values)
--* AT+RECV: Print last received data in raw format
--* AT+VER: Get current image version and Frequency Band
--* AT+CFM: Get or Set the confirmation mode (0-1)
--* AT+CFS: Get confirmation status of the last AT+SEND (0-1)
--* AT+SNR: Get the SNR of the last received packet
--* AT+RSSI: Get the RSSI of the last received packet
--* AT+TDC: Get or set the application data transmission interval in ms
--* AT+PORT: Get or set the application port
--* AT+DISAT: Disable AT commands
--* AT+PWORD: Set password, max 9 digits
--* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode
--* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470
--* AT+CFG: Print all settings
++* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
++* **##AT+DR##**:  Get or set the Data Rate. (0-7 corresponding to DR_X)
++* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
++* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)
++* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency
++* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
++* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
++* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
++* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
++* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
++* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
++* ##**AT+NWKID**##: Get or set the Network ID
++* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)
++* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)
++* ##**AT+CLASS**##: Get or set the Device Class
++* ##**AT+JOIN**##: Join network
++* ##**AT+NJS**##: Get OTAA Join Status
++* ##**AT+SENDB**##: Send hexadecimal data along with the application port
++* ##**AT+SEND**##: Send text data along with the application port
++* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)
++* ##**AT+RECV**##: Print last received data in raw format
++* ##**AT+VER**##: Get current image version and Frequency Band
++* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)
++* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)
++* ##**AT+SNR**##: Get the SNR of the last received packet
++* ##**AT+RSSI**##: Get the RSSI of the last received packet
++* ##**AT+TDC**##: Get or set the application data transmission interval in ms
++* ##**AT+PORT**##: Get or set the application port
++* ##**AT+DISAT**##: Disable AT commands
++* ##**AT+PWORD**##: Set password, max 9 digits
++* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode
++* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN470
++* ##**AT+CFG**##: Print all settings
  )))
@@ -2249,16 +2249,19 @@
  == 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]]?
  = 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:
  * Support new features
@@ -2268,7 +2268,7 @@
  You will need the following things before proceeding:
  * 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
--* USB to TTL adapter
++* USB to TTL adapter/converter
  * Download and install the [[STM32 Flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]]. (replaced by STM32CubeProgrammer)
  * Download the latest firmware image from [[LT-22222-L firmware image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]]. Check the file name of the firmware to find the correct region.
@@ -2278,7 +2278,7 @@
  Below is the hardware setup for uploading a firmware image to the LT-22222-L:
--[[image:usb-ttl-programming.png]]
++[[image:usb-ttl-audio-jack-connection.jpg]]
@@ -2311,6 +2311,8 @@
  (((
  (((
  == 6.2 How to change the LoRaWAN frequency band/region? ==
++
++
  )))
  )))
@@ -2322,6 +2322,8 @@
  == 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
++
++
  )))
  (((
@@ -2395,11 +2395,13 @@
  == 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.
@@ -2406,6 +2406,7 @@
  == 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]].
@@ -2414,6 +2414,7 @@
  (((
  == 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.
@@ -2421,6 +2421,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:
@@ -2429,16 +2429,19 @@
  == 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.
  == 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.
@@ -2447,6 +2447,8 @@
  (((
  (((
  == 7.1 Downlink isn't working. How can I solve this? ==
++
++
  )))
  )))
@@ -2458,6 +2458,8 @@
  == 7.2 Having trouble uploading an image? ==
++
++
  )))
  (((
@@ -2468,6 +2468,8 @@
  == 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
++
++
  )))
  (((
@@ -2477,6 +2477,7 @@
  == 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"]]
@@ -2483,6 +2483,7 @@
  = 8. Ordering information =
++
  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
  (% style="color:#4f81bd" %)**XXX:**
@@ -2499,6 +2499,7 @@
  = 9. Package information =
++
  **Package includes**:
  * 1 x LT-22222-L I/O Controller
@@ -2515,6 +2515,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.
  )))
@@ -2526,6 +2526,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]]

Screenshot 2024-11-23 at 18.27.11.png

Author

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

Size

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

Content

Screenshot 2024-12-08 193946.png

Author

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

Size

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

Content

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

Author

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

Size

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

Content

dragino-ttn-te.jpg

Author

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

Size

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

Content

lorawan-nw.jpg

Author

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

Size

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

Content

lt-22222-l-joining.png

Author

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

Size

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

Content

lt-22222-l-js-custom-payload-formatter.png

Author

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

Size

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

Content

lt33222-l.jpg

Author

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

Size

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

Content

usb-ttl-audio-jack-connection.jpg

Author

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

Size

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

Content