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

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

From 192.1 to 191.1 From 216.1 to 215.1

From version 215.1

edited by Dilisi S
on 2024/11/24 05:05

Change comment: fix formatting

To version 192.1

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

Change comment: Nov 13 - part 1 save

Raw
Rendered

Summary

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

Details

Page properties

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,20 +40,21 @@
  (((
  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}}
  )))
  (((
--
++[[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:**
@@ -114,21 +114,6 @@
  * Smart cities
  * Smart factory
--== 1.5 Hardware Variants ==
--
--(% style="width:524px" %)
--|(% style="width:94px" %)**Model**|(% style="width:98px" %)**Photo**|(% style="width:329px" %)**Description**
--|(% style="width:94px" %)**LT33222-L**|(% style="width:98px" %)(((
--
--)))|(% style="width:329px" %)(((
--* 2 x Digital Input (Bi-direction)
--* 2 x Digital Output
--* 2 x Relay Output (5A@250VAC / 30VDC)
--* 2 x 0~~20mA Analog Input (res:0.01mA)
--* 2 x 0~~30V Analog Input (res:0.01v)
--* 1 x Counting Port
--)))
--
  = 2. Assembling the device =
  == 2.1 Connecting the antenna ==
@@ -136,17 +136,17 @@
  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 screw terminals and the lower screw terminal block has 10 screw 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):**
++Upper screw terminal block (from left to right):
  (% style="width:634px" %)
--|=(% style="width: 295px;" %)Screw Terminal|=(% style="width: 338px;" %)Function
++|=(% 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
@@ -154,10 +154,10 @@
  |(% style="width:295px" %)ACI2|(% style="width:338px" %)Analog Current Input Terminal 2
  |(% style="width:295px" %)ACI1|(% style="width:338px" %)Analog Current Input Terminal 1
--**Lower screw terminal block (from left to right):**
++Lower screw terminal block (from left to right):
  (% style="width:633px" %)
--|=(% style="width: 296px;" %)Screw Terminal|=(% style="width: 334px;" %)Function
++|=(% 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
@@ -169,12 +169,14 @@
  |(% 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 device ==
--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 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.
++
  {{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 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}}
@@ -181,51 +181,36 @@
  [[image:1653297104069-180.png]]
--= 3. Registering LT-22222-L with a LoRaWAN Network Server =
++= 3. Registering with a LoRaWAN Network Server =
--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.
++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.
++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 ===
--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.
++Make sure you have the device registration information such as DevEUI, AppEUI, and AppKey with you. The registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference.
  [[image:image-20230425173427-2.png||height="246" width="530"]]
--{{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 ===
++=== 3.2.2 The Things Stack Sandbox (TTSS) ===
--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}}
--
--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]]
--
--{{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.
++* 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.
  * On the End devices page, click on **+ Register end device**. Two registration options are available:
--==== 3.2.2.2 Using the LoRaWAN Device Repository ====
++==== 3.2.2.1 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**.
@@ -249,8 +249,9 @@
  [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
++====   ====
--==== 3.2.2.3 Adding device manually ====
++==== 3.2.2.2 Adding device manually ====
  * On the **Register end device** page:
  ** Select the option **Enter end device specifies manually** under **Input method**.
@@ -265,7 +265,7 @@
  * 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.
@@ -281,27 +281,24 @@
  [[image:lt-22222-device-overview.png||height="625" width="1000"]]
--==== 3.2.2.4 Joining ====
++==== 3.2.2.3 Joining ====
--On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
++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. 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.
++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**).
  [[image:lt-22222-join-network.png||height="625" width="1000"]]
--==== 3.2.2.5 Uplinks ====
++By default, you will receive an uplink data message from the device 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]]
--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.
++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.
@@ -310,16 +310,11 @@
  [[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
--==== 3.2.2.6 Downlinks ====
++== 3.3 Work Modes and 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
@@ -332,7 +332,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,7 +341,7 @@
  The uplink payload is 11 bytes long.
--(% style="color:red" %)**Note:The maximum count depends on the bytes number of bytes.
++(% 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.**(% style="display:none" wfd-invisible="true" %)
@@ -401,13 +401,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) ===
@@ -590,13 +590,13 @@
  )))
  (((
--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)**
@@ -663,27 +663,24 @@
  )))
--=== 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 default work 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. 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.
 . (((
--Trigger uplink: sent when a trigger condition is met. In this case, LT will send two packets
--
--* 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.**
++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.**
  )))
--(% style="color:#037691" %)**AT Commands to set Trigger Conditions**:
++(% style="color:#037691" %)**AT Commands to set Trigger Condition**:
  (% style="color:#4f81bd" %)**Trigger based on voltage**:
@@ -692,9 +692,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**:
@@ -704,7 +704,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**:
@@ -824,9 +824,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.
@@ -881,456 +881,216 @@
  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**
--(% border="2" style="width:500px" %)
--|**Command**|AT+TDC=<time>
++(% style="width:500px" %)
++|**Command**|AT+TDC<time>
  |**Response**|
--|**Parameters**|**time** : uplink interval is in **milliseconds**
++|**Parameters**|<time> uplink interval is in milliseconds
  |**Example**|(((
  AT+TDC=30000
--Sets the uplink interval to **30 seconds** (30000 milliseconds)
++Sets the uplink interval to 30,000 milliseconds (30 seconds)
  )))
  (% style="color:#037691" %)**Downlink payload**
--(% border="2" style="width:500px" %)
++(% style="width:500px" %)
  |**Payload**|(((
  <prefix><time>
  )))
  |**Parameters**|(((
--**prefix** : 0x01
++<prefix> 0x01
--**time** : uplink interval is in **seconds**, represented by **3  bytes** in **hexadecimal**.
++<time> uplink interval is in milliseconds, represented by 3  bytes in hexadecimal.
  )))
  |**Example**|(((
--01 **00 00 1E**
++01 **00 75 30**
--Sets the uplink interval to **30 seconds**
++Sets the uplink interval to 30,000 milliseconds (30 seconds)
--Conversion: 30 (dec) = 00 00 1E (hex)
++Conversion: 30000 (dec) = 00 75 30 (hex)
--See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30]]
--
--[[image:Screenshot 2024-11-23 at 18.27.11.png]]
++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
++Requests the device to send an uplink.
--**working_mode** : Working mode, represented by 1 byte in hexadecimal.
--)))
--|(% style="width:98px" %)**Example**|(% style="width:400px" %)(((
--0A **02**
--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. The content of the uplink payload varies based on the device's current working mode.
++(% 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 available for this feature.
--(% 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"]]).
++Enable or disable the trigger mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
--(% style="color:#037691" %)**AT Command**
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0**
--(% 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:red" %)**1:** (%%)Enable the trigger mode
--1 = enable trigger mode
++(% style="color:red" %)**0: **(%%)Disable the trigger mode
--0 = disable trigger mode
--)))
--|(% style="width:95px" %)**Example**|(% style="width:403px" %)(((
--AT+ADDMOD6=1
--Enable trigger mode for the current working mode
--)))
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x0A 06):**
--(% style="color:#037691" %)**Downlink payload**
++(% style="color:blue" %)**0x0A 06 aa    **(%%)    ~/~/ Same as AT+ADDMOD6=aa
--(% 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)
--**enable/disable trigger_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:**
++* (% style="color:#037691" %)**AT Command:**
--There is no AT Command available for this feature.
++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 a trigger ====
--(% style="color:#037691" %)**AT Command**
++Enable or disable DI1/DI2/DI2 as a trigger.
--(% border="2" style="width:500px" %)
--|(% style="width:98px" %)**Command**|(% style="width:400px" %)AT+DTRI=<DI1_trigger>,<DI2_trigger>
--|(% style="width:98px" %)**Response**|(% style="width:400px" %)
--|(% style="width:98px" %)**Parameters**|(% style="width:400px" %)(((
--**DI1_trigger:**
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
--1 = enable DI1 trigger
++**Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
--0 = disable DI1 trigger
--**DI2 _trigger**
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 02):**
--1 = enable DI2 trigger
++(% style="color:blue" %)**0xAA 02 aa bb   **  (%%) ~/~/ Same as AT+DTRI=aa,bb
--0 = disable DI2 trigger
--)))
--|(% style="width:98px" %)**Example**|(% style="width:400px" %)(((
--AT+DTRI=1,0
--Enable DI1 trigger, disable DI2 trigger
--)))
--(% class="wikigeneratedid" %)
--(% style="color:#037691" %)**Downlink Payload**
--
--(% border="2" style="width:500px" %)
--|(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix><DI1_trigger><DI2_trigger>
--|(% style="width:101px" %)**Parameters**|(% style="width:397px" %)(((
--**prefix :** AA 02 (two bytes in hexadecimal)
--
--**DI1_trigger:**
--
--1 = enable DI1 trigger, represented by 1 byte in hexadecimal.
--
--0 = disable DI1 trigger, represented by 1 byte in hexadecimal.
--
--**DI2 _trigger**
--
--1 = enable DI2 trigger, represented by 1 byte in hexadecimal.
--
--0 = disable DI2 trigger, represented by 1 byte in hexadecimal.
--)))
--|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
--AA 02 **01 00**
--
--Enable DI1 trigger, disable DI2 trigger
--)))
--
  ==== 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:**(%%) (% style="color:blue" %)**AT+TRIG1=a,b**
--(% style="color:#037691" %)**AT Command**
++(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
--(% border="2" style="width:500px" %)
--|(% style="width:101px" %)**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).
++(% style="color:red" %)**b :** (%%)delay timing.
--**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
++**Example:** AT+TRIG1=1,100(set DI1 port to trigger on high level, valid signal is 100ms )
--Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms.
--)))
--(% class="wikigeneratedid" %)
--(% style="color:#037691" %)**Downlink Payload**
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 01 ):**
--(% 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:blue" %)**0x09 01 aa bb cc    ** (%%)    ~/~/ same as AT+TRIG1=aa,0x(bb cc)
--**interrupt_mode** : 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal.
--**minimum_signal_duration** : in milliseconds, represented two bytes in hexadecimal.
--)))
--|(% style="width:101px" %)**Example**|(% style="width:397px" %)(((
--09 01 **01 00 64**
--
--Set the DI1 port to trigger on a rising edge; the valid signal duration is 100 ms.
--)))
--
  ==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
  Sets DI2 as a trigger.
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b**
--(% style="color:#037691" %)**AT Command**
++(% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
--(% border="2" style="width:500px" %)
--|(% style="width: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).
++(% style="color:red" %)**b :** (%%)delay timing.
--**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
++**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 falling edge; the valid signal duration is 100 ms.
--)))
--(% style="color:#037691" %)**Downlink Payload**
++* (% style="color:#037691" %)**Downlink Payload (prefix 0x09 02 ):**
--(% border="2" style="width:500px" %)
--|(% style="width:96px" %)**Payload**|(% style="width:402px" %)<prefix><interrupt_mode><minimum_signal_duration>
--|(% style="width:96px" %)**Parameters**|(% style="width:402px" %)(((
--**prefix** : 09 02 (hexadecimal)
++(% style="color:blue" %)**0x09 02 aa bb cc   **  (%%)~/~/ same as AT+TRIG2=aa,0x(bb cc)
--**interrupt_mode **: 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1), represented by 1 byte in hexadecimal.
--**minimum_signal_duration** : in milliseconds, represented two bytes in hexadecimal
--)))
--|(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64**
--
  ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
--Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
++Sets the current trigger based on the AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--(% style="color:#037691" %)**AT Command**
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ACLIM**
--(% 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
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 01 )**
--**AC1_LIMIT_HIGH **: higher limit of the current to be checked
++(% 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"]]
--**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"]]
++Sets the current trigger based on the AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--(% style="color:#037691" %)**AT Command**
++* (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+AVLIM    **(%%)**        See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]**
--(% border="2" style="width:500px" %)
--|(% style="width:104px" %)**Command**|(% style="width:387px" %)AT+AVLIM= AV1_LIMIT_LOW>,< AV1_LIMIT_HIGH>,<AV2_LIMIT_LOW>,< AV2_LIMIT_HIGH>
--|(% style="width:104px" %)**Response**|(% style="width:387px" %)
--|(% style="width:104px" %)**Parameters**|(% style="width:387px" %)(((
--**AC1_LIMIT_LOW** : lower limit of the current to be checked
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 00 )**
--**AC1_LIMIT_HIGH **: higher limit of the current to be checked
++(% style="color:blue" %)**0x AA 00 aa bb cc dd ee ff gg hh    ** (%%) ~/~/ same as AT+AVLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--**AC2_LIMIT_HIGH **: lower limit of the current to be checked
--**AC2_LIMIT_LOW** : higher limit of the current to be checked
--)))
--|(% style="width:104px" %)**Example**|(% style="width:387px" %)(((
--AT+AVLIM=3000,6000,0,2000
--
--Triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V
--)))
--|(% style="width:104px" %)**Note**|(% style="width:387px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--
--(% 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.
++Sets AV and AC trigger minimum interval.  Device won't response to the second trigger within this set time after the first trigger.
--(% style="color:#037691" %)**AT Command**
++* (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+ATDC=5        ** ~/~/ (%%)Device won't response the second trigger within 5 minute after the first trigger.
--(% 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" %)**Downlink Payload (prefix 0xAC )**
--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:blue" %)**0x AC aa bb   **(%%) ~/~/ same as AT+ATDC=0x(aa bb)   . Unit (min)
--(% style="color:#037691" %)**Downlink Payload**
--
--(% border="2" style="width:500px" %)
--|(% style="width:112px" %)**Payload**|(% style="width:386px" %)<prefix><time>
--|(% style="width:112px" %)**Parameters**|(% style="width:386px" %)(((
--**prefix** : AC (hexadecimal)
--
--**time **: in minutes (two bytes in hexadecimal)
++(((
++(% style="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**
@@ -1340,16 +1340,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 ====
@@ -1374,7 +1374,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**
@@ -1382,7 +1382,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**
@@ -1390,7 +1390,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**
@@ -1398,16 +1398,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:**
@@ -1414,21 +1414,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 ====
@@ -1443,11 +1443,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**
@@ -1464,9 +1464,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:**
@@ -1478,15 +1478,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:
@@ -1499,12 +1499,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:**
@@ -1511,19 +1511,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.
@@ -1530,359 +1530,130 @@
  ==== 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:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX   ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
--(% 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:#037691" %)**Downlink Payload (prefix 0xA5):**
--**logic**:
++(% style="color:blue" %)**0xA5 aa bb cc   ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc
--**0** : lower than
--**1**: higher than
--if you leave logic parameter blank, it is considered 0
--)))
--|(% style="width:137px" %)**Examples**|(% style="width:361px" %)(((
--AT+VOLMAX=20000
--
--If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
--
--AT+VOLMAX=20000,0
--
--If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1
--
--AT+VOLMAX=20000,1
--
--If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
--)))
--
--(% style="color:#037691" %)**Downlink Payload**
--
--(% border="2" style="width:500px" %)
--|(% style="width:140px" %)**Payload**|(% style="width:358px" %)<prefix><voltage><logic>
--|(% style="width:140px" %)**Parameters**|(% style="width:358px" %)(((
--**prefix** : A5 (hex)
--
--**voltage** : voltage threshold in mV (2 bytes in hex)
--
--**logic**: (1 byte in hexadecimal)
--
--**0** : lower than
--
--**1**: higher than
--
--if you leave logic parameter blank, it is considered 1 (higher than)
--)))
--|(% style="width:140px" %)**Example**|(% style="width:358px" %)(((
--A5 **4E 20**
--
--If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
--
--A5 **4E 20 00**
--
--If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1
--
--A5 **4E 20 01**
--
--If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1
--)))
--
  ==== 3.4.2.17 Counting ~-~- Pre-configure the Count Number ====
--This command allows users to pre-configure specific count numbers for various counting parameters such as Count1, Count2, or AVI1 Count. Use the AT command to set the desired count number for each configuration.
--(% style="color:#037691" %)**AT Command**
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) **
--(% 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" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count
--1: COUNT1
++(% style="color:red" %)**bb cc dd ee: **(%%)number to be set
--2: COUNT2
--3: AVI1 Count
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):**
--**number** : Start number
--)))
--|(% style="width:134px" %)**Example**|(% style="width:364px" %)(((
--AT+SETCNT=1,10
++(% style="color:blue" %)**0x A8 aa bb cc dd ee     ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee)
--Sets the COUNT1 to 10.
--)))
--(% style="color:#037691" %)**Downlink Payload**
--(% border="2" style="width:500px" %)
--|(% style="width:135px" %)**Payload**|(% style="width:363px" %)<prefix><counting_parameter><number>
--|(% style="width:135px" %)**Parameters**|(% style="width:363px" %)(((
--prefix : A8 (hex)
--
--**counting_parameter** :  (1 byte in hexadecimal)
--
--1: COUNT1
--
--2: COUNT2
--
--3: AVI1 Count
--
--**number** : Start number, 4 bytes in hexadecimal
--)))
--|(% style="width:135px" %)**Example**|(% style="width:363px" %)(((
--A8 **01 00 00 00 0A**
--
--Sets the COUNT1 to 10.
--)))
--
  ==== 3.4.2.18 Counting ~-~- Clear Counting ====
--This command clears the counting in counting mode.
--(% style="color:#037691" %)**AT Command**
++Clear counting for counting mode
--(% border="2" style="width:500px" %)
--|(% style="width:142px" %)**Command**|(% style="width:356px" %)AT+CLRCOUNT
--|(% style="width:142px" %)**Response**|(% style="width:356px" %)-
++* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT         **(%%) ~/~/ clear all counting
--(% style="color:#037691" %)**Downlink Payload**
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):**
--(% border="2" style="width:500px" %)
--|(% style="width:141px" %)**Payload**|(% style="width:357px" %)<prefix><clear?>
--|(% style="width:141px" %)**Parameters**|(% style="width:357px" %)(((
--prefix : A6 (hex)
++(% style="color:blue" %)**0x A6 01    ** (%%)~/~/ clear all counting
--clear? : 01 (hex)
--)))
--|(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
++
  ==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
--This command allows you to configure the device to save its counting result to internal flash memory at specified intervals. By setting a save time, the device will periodically store the counting data to prevent loss in case of power failure. The save interval can be adjusted to suit your requirements, with a minimum value of 30 seconds.
--(% style="color:#037691" %)**AT Command**
++* (% style="color:#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: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)
--Sets the device to save its counting results to the memory every 60 seconds.
--)))
--(% style="color:#037691" %)**Downlink Payload**
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):**
--(% border="2" style="width:500px" %)
--|(% style="width:123px" %)**Payload**|(% style="width:375px" %)<prefix><time>
--|(% style="width:123px" %)**Parameters**|(% style="width:375px" %)(((
--prefix : A7
++(% style="color:blue" %)**0x A7 aa bb cc     ** (%%)~/~/ same as AT+COUTIME =aa bb cc,
--time : seconds, 3 bytes in hexadecimal
++(((
++range: aa bb cc:0 to 16777215,  (unit:second)
  )))
--|(% style="width:123px" %)**Example**|(% style="width:375px" %)(((
--A7 **00 00 3C**
--Sets the device to save its counting results to the memory every 60 seconds.
--)))
++
  ==== 3.4.2.20 Reset save RO DO state ====
--This command allows you to reset the saved relay output (RO) and digital output (DO) states when the device joins the network. By configuring this setting, you can control whether the device should retain or reset the relay states after a reset and rejoin to the network.
--(% style="color:#037691" %)**AT Command**
++* (% style="color:#037691" %)**AT Command:**
--(% 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=1    **(%%)~/~/ RODO will close when the device joining the network. (default)
--**0** : 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 (only MOD2 to MOD5) is read, and its state is not changed when it is reconnected to the network.
--**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:#037691" %)**Downlink Payload (prefix 0xAD):**
--(% style="color:blue" %)**AT+RODORESET=0 **
++(% style="color:blue" %)**0x AD aa      ** (%%)~/~/ same as AT+RODORET =aa
--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 command allows you to configure whether the device should upload data in an encrypted format or in plaintext. By default, the device encrypts the payload before uploading. You can toggle this setting to either upload encrypted data or transmit it without encryption.
--(% style="color:#037691" %)**AT Command:**
++* (% style="color:#037691" %)**AT Command:**
--(% 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** :
++(% style="color:blue" %)**AT+DECRYPT=1  **   (%%)~/~/ The payload is uploaded without encryption
--**1** : The payload is uploaded without encryption
++(% style="color:blue" %)**AT+DECRYPT=0    **(%%)~/~/  Encrypt when uploading payload (default)
--**0** : The payload is encrypted when uploaded (default)
--)))
--|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
--AT+DECRYPT=1
--The payload is uploaded without encryption
--AT+DECRYPT=0
--
--The payload is encrypted when uploaded (default)
--)))
--
--There is no downlink payload for this configuration.
--
--
  ==== 3.4.2.22 Get sensor value ====
--This command allows you to retrieve and optionally uplink sensor readings through the serial port.
--(% style="color:#037691" %)**AT Command**
++* (% style="color:#037691" %)**AT Command:**
--(% 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** :
++(% style="color:blue" %)**AT+GETSENSORVALUE=0    **(%%)~/~/ The serial port gets the reading of the current sensor
--**0 **: Retrieves the current sensor reading via the serial port.
++(% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port gets the current sensor reading and uploads it.
--**1 **: Retrieves and uploads the current sensor reading via the serial port.
--)))
--|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
--AT+GETSENSORVALUE=0
--Retrieves the current sensor reading via the serial port.
--AT+GETSENSORVALUE=1
++==== 3.4.2.23 Resets the downlink packet count ====
--Retrieves and uplinks the current sensor reading via the serial port.
--)))
--There is no downlink payload for this configuration.
++* (% style="color:#037691" %)**AT Command:**
++(% style="color:blue" %)**AT+DISFCNTCHECK=0   **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node will no longer receive downlink packets (default)
--==== 3.4.2.23 Resetting the downlink packet count ====
++(% style="color:blue" %)**AT+DISFCNTCHECK=1   **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node resets the downlink packet count and keeps it consistent with the server downlink packet count.
--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 ====
--This command controls the behavior of the node when the combined size of the MAC commands (MACANS) from the server and the payload exceeds the allowed byte limit for the current data rate (DR). The command provides two modes: one enables splitting the data into batches to ensure compliance with the byte limit, while the other prioritizes the payload and ignores the MACANS in cases of overflow.
++* (% style="color:#037691" %)**AT Command:**
--(% style="color:#037691" %)**AT Command**
++(% style="color:blue" %)**AT+DISMACANS=0**   (%%)  ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of 11 bytes (DR0 of US915, DR2 of AS923, DR2 of AU195), the node will send a packet with a payload of 00 and a port of 4. (default)
--(% 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** :
++(% 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.
--**0** : When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default)
--**1** : When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload.
--)))
--|(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
--AT+DISMACANS=0
++* (% style="color:#037691" %)**Downlink Payload **(%%)**:**
--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:blue" %)**0x21 00 01 **   (%%)      ~/~/ Set  the DISMACANS=1
--AT+DISMACANS=1
--When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload.
--)))
--(% style="color:#037691" %)**Downlink Payload**
--
--(% border="2" style="width:500px" %)
--|(% style="width:126px" %)**Payload**|(% style="width:372px" %)<prefix><state>
--|(% style="width:126px" %)**Parameters**|(% style="width:372px" %)(((
--**prefix** : 21
--
--**state** : (2 bytes in hexadecimal)
--
--**0** : When the combined size of the MACANS from the server and the payload exceeds the byte limit (11 bytes for DR0 of US915, DR2 of AS923, DR2 of AU915), the node sends a packet with a payload of 00 and a port of 4. (default)
--
--**1 **: When the combined size of the MACANS from the server and the payload exceeds the byte limit for the current DR, the node ignores the MACANS and only uploads the payload.
--)))
--|(% style="width:126px" %)**Example**|(% style="width:372px" %)(((
--21 **00 01**
--
--Set DISMACANS=1
--)))
--
  ==== 3.4.2.25 Copy downlink to uplink ====
--This command enables the device to immediately uplink the content of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100.
  * (% style="color:#037691" %)**AT Command**(%%)**:**
@@ -1895,22 +1895,8 @@
  For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
--(% border="2" style="width:500px" %)
--|(% style="width:122px" %)**Command**|(% style="width:376px" %)(((
--AT+RPL=5
--After receiving a downlink packet from the server, the node immediately uplinks the content of the packet back to the server using port number 100.
--)))
--|(% style="width:122px" %)**Example**|(% style="width:376px" %)(((
--Downlink:
--01 00 02 58
--
--Uplink:
--
--01 01 00 02 58
--)))
--
  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]]
  For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
@@ -1917,16 +1917,14 @@
--==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
++==== 3.4.2.26 Query version number and frequency band 、TDC ====
--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  ** (%%)  ~/~/  The downlink payload 26 01 is used to query the device's firmware version, frequency band, sub band, and TDC time.
++(% style="color:blue" %)**26 01  ** (%%)  ~/~/  Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.
--
  )))
@@ -1956,8 +1956,6 @@
  === 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).
@@ -2006,7 +2006,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 **3.5.1 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 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]]
@@ -2017,13 +2017,13 @@
  [[image:thingseye-io-step-5.png||height="625" width="1000"]]
--Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings and correct any errors.
++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.
  [[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.
@@ -2033,10 +2033,10 @@
  If you want to edit the settings you have provided, click on the **Toggle edit mode** button. Once you have done click on the **Apply changes **button.
  {{info}}
--See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
++See also ThingsEye documentation.
  {{/info}}
--==== **3.5.2.2 Viewing events** ====
++**Viewing events:**
  The **Events **tab displays all the uplink messages from the LT-22222-L.
@@ -2046,32 +2046,27 @@
  [[image:thingseye-events.png||height="686" width="1000"]]
--* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
++* To view the JSON payload of a message, click on the three dots (...) in the Message column of the desired message.
  [[image:thingseye-json.png||width="1000"]]
--==== **3.5.2.3 Deleting an integration** ====
++**Deleting the integration**:
--If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
++If you want to delete this integration, click the **Delete integratio**n button.
--==== 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) ===
++=== 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) ===
  (((
@@ -2201,7 +2201,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.
@@ -2312,10 +2312,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]]
  (((
@@ -2332,21 +2332,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
@@ -2391,28 +2391,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**##
  )))
@@ -2435,20 +2435,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
  )))
  (((
@@ -2468,19 +2468,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.
  )))
  (((
@@ -2494,14 +2494,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.**
  )))
  (((
@@ -2513,7 +2513,7 @@
  (((
--(% style="color:blue" %)**If the sensor has JOINED:**
++(% style="color:blue" %)**If sensor JOINED:**
  (% style="background-color:#dcdcdc" %)**AT+CLASS=A**
@@ -2523,7 +2523,7 @@
  = 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]]?
@@ -2535,8 +2535,10 @@
  == 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
@@ -2554,8 +2554,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.
@@ -2579,7 +2579,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"]]
@@ -2773,6 +2773,7 @@
  * (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865
  * (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779
++
  = 9. Package information =
  **Package includes**:
@@ -2789,6 +2789,7 @@
  * Package Size / pcs : 14.5 x 8 x 5 cm
  * Weight / pcs : 170 g
++
  = 10. Support =
  * (((

Screenshot 2024-11-23 at 18.27.11.png

Author

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

Size

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

Content

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