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

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

From version < 177.1 >

edited by Dilisi S
on 2024/11/08 06:48

To version < 189.1 >

edited by Dilisi S
on 2024/11/12 04:05

Change comment: Uploaded new attachment "usb-ttl-programming.png", version {1}

Raw
Rendered

Summary

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

Details

Page properties

Title

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

Content

@@ -33,8 +33,6 @@
  With the LT-22222-L I/O Controller, users can transmit data over ultra-long distances with low power consumption using LoRa, a spread-spectrum modulation technique derived from chirp spread spectrum (CSS) technology that operates on license-free ISM bands.
  )))
--> The LT Series I/O Controllers are designed for easy, low-cost installation on LoRaWAN networks.
--
  (((
  You can connect the LT-22222-L I/O Controller to a LoRaWAN network service provider in several ways:
@@ -42,7 +42,9 @@
  * If there is no public LoRaWAN coverage in your area, you can set up a LoRaWAN gateway, or multiple gateways, and connect them to a LoRaWAN network server to create adequate coverage. Then, register the LT-22222-L I/O controller with this network.
  * Setup your own private LoRaWAN network.
--> You can use a LoRaWAN gateway, such as the Dragino LG308, to expand or create LoRaWAN coverage in your area.
++{{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}}
  )))
  (((
@@ -58,24 +58,24 @@
  * STM32L072xxxx MCU
  * SX1276/78 Wireless Chip
  * Power Consumption:
--** Idle: 4mA@12v
--** 20dB Transmit: 34mA@12v
++** Idle: 4mA@12V
++** 20dB Transmit: 34mA@12V
  * Operating Temperature: -40 ~~ 85 Degrees, No Dew
  (% style="color:#037691" %)**Interface for Model: LT22222-L:**
--* 2 x Digital dual direction Input (Detect High/Low signal, Max: 50v, or 220v with optional external resistor)
++* 2 x Digital dual direction Input (Detect High/Low signal, Max: 50V, or 220V with optional external resistor)
  * 2 x Digital Output (NPN output. Max pull-up voltage 36V,450mA)
  * 2 x Relay Output (5A@250VAC / 30VDC)
  * 2 x 0~~20mA Analog Input (res:0.01mA)
--* 2 x 0~~30V Analog Input (res:0.01v)
++* 2 x 0~~30V Analog Input (res:0.01V)
  * Power Input 7~~ 24V DC.
  (% style="color:#037691" %)**LoRa Spec:**
  * Frequency Range:
--** Band 1 (HF): 862 ~~ 1020 Mhz
--** Band 2 (LF): 410 ~~ 528 Mhz
++** Band 1 (HF): 862 ~~ 1020 MHz
++** Band 2 (LF): 410 ~~ 528 MHz
  * 168 dB maximum link budget.
  * +20 dBm - 100 mW constant RF output vs.
  * +14 dBm high-efficiency PA.
@@ -94,7 +94,7 @@
  == 1.3 Features ==
--* LoRaWAN Class A & Class C protocol
++* LoRaWAN Class A & Class C modes
  * Optional Customized LoRa Protocol
  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
  * AT Commands to change parameters
@@ -104,12 +104,12 @@
  == 1.4 Applications ==
--* Smart Buildings & Home Automation
--* Logistics and Supply Chain Management
--* Smart Metering
--* Smart Agriculture
--* Smart Cities
--* Smart Factory
++* Smart buildings & home automation
++* Logistics and supply chain management
++* Smart metering
++* Smart agriculture
++* Smart cities
++* Smart factory
  == 1.5 Hardware Variants ==
@@ -128,21 +128,20 @@
  * 1 x Counting Port
  )))
--= 2. Assembling the Device =
++= 2. Assembling the device =
--== 2.1 What is included in the package? ==
++== 2.1 Connecting the antenna ==
--The package includes the following items:
++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.
--* 1 x LT-22222-L I/O Controller
--* 1 x LoRaWAN antenna matched to the frequency of the LT-22222-L
--* 1 x bracket for wall mounting
--* 1 x programming cable
++{{warning}}
++Warning! Do not power on the device without connecting the antenna.
++{{/warning}}
--Attach the LoRaWAN antenna to the antenna connector, ANT,** **located on the top right side of the device, next to the upper terminal block. Secure the antenna by tightening it clockwise.
--
  == 2.2 Terminals ==
++The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 terminals and the lower screw terminal block has 10 terminals.
++
  Upper screw terminal block (from left to right):
  (% style="width:634px" %)
@@ -169,28 +169,30 @@
  |(% style="width:296px" %)DO2|(% style="width:334px" %)Digital Output 2
  |(% style="width:296px" %)DO1|(% style="width:334px" %)Digital Output 1
--== 2.3 Powering the LT-22222-L ==
++== 2.3 Powering the device ==
--The LT-22222-L I/O Controller can be powered by a 7–24V DC power source. Connect the power supply’s positive wire to the VIN and the negative wire to the GND screw terminals. The power indicator (PWR) LED will turn on when the device is properly powered.
++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.
--[[image:1653297104069-180.png]]
++{{warning}}
++We recommend that you power on the LT-22222-L after configuring its registration information with a LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.
++{{/warning}}
--= 3. Operation Mode =
++[[image:1653297104069-180.png]]
--== 3.1 How does it work? ==
++= 3. Registering 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.
--For LT-22222-L, the LED will show the Join status: After powering on, the TX LED will fast-blink 5 times which means the LT-22222-L will enter the working mode and start to JOIN the LoRaWAN network. The TX LED will be on for 5 seconds after joining the network. When there is a message from the server, the RX LED will be on for 1 second.
++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.
--== 3.2 Registering with a LoRaWAN network server ==
++The network diagram below shows how the LT-22222-L is connected to a typical LoRaWAN network.
--The diagram below shows how the LT-22222-L connects to a typical LoRaWAN network.
--
  [[image:image-20220523172350-1.png||height="266" width="864"]]
  === 3.2.1 Prerequisites ===
@@ -203,49 +203,60 @@
  === 3.2.2 The Things Stack Sandbox (TTSS) ===
++The Things Stack Sandbox was formally called The Things Stack Community Edition.
++
  * Log in to your [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] account.
--* Create an application if you do not have one yet.
--* Register LT-22222-L with that application. Two registration options are available:
++* 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:
--==== Using the LoRaWAN Device Repository: ====
++==== 3.2.2.1 Using the LoRaWAN Device Repository ====
--* Go to your application and click on the **Register end device** button.
  * On the **Register end device** page:
--** Select the option **Select the end device in the LoRaWAN Device Repository**.
--** Choose the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)**.
--** Select the **Frequency plan** that matches your device.
++** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
++** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists.
++*** **End device brand**: Dragino Technology Co., Limited
++*** **Model**: LT22222-L I/O Controller
++*** **Hardware ver**: Unknown
++*** **Firmware ver**: 1.6.0
++*** **Profile (Region)**: Select the region that matches your device.
++** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
  [[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
--*
--** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
--** Enter the **DevEUI** in the **DevEUI** field.
--** Enter the **AppKey** in the **AppKey** field.
--** In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
++
++* Register end device page continued...
++** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network'.
++** In the **DevEUI** field, enter the **DevEUI**.
++** In the **AppKey** field, enter the **AppKey.**
++** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
  ** Under **After registration**, select the **View registered end device** option.
  [[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
--==== Entering device information manually: ====
++====   ====
++==== 3.2.2.2 Adding device manually ====
++
  * On the **Register end device** page:
--** Select the **Enter end device specifies manually** option as the input method.
--** Select the **Frequency plan** that matches your device.
--** Select the **LoRaWAN version**.
--** Select the **Regional Parameters version**.
--** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the section.
--** Select **Over the air activation (OTAA)** option under the **Activation mode**
--** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities**.
++** Select the option **Enter end device specifies manually** under **Input method**.
++** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
++** Select the **LoRaWAN version** as **LoRaWAN Specification 1.0.3**
++** Select the **Regional Parameters version** as** RP001 Regional Parameters 1.0.3 revision A**
++** Click **Show advanced activation, LoRaWAN class and cluster settings** link to expand the hidden section.
++** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
++** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
  [[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
--* Enter **AppEUI** in the **JoinEUI** field and click the **Confirm** button.
--* Enter **DevEUI** in the **DevEUI** field.
--* Enter **AppKey** in the **AppKey** field.
--* In the **End device ID** field, enter a unique name within this application for your LT-22222-N.
--* Under **After registration**, select the **View registered end device** option.
--* Click the **Register end device** button.
++* Register end device page continued...
++** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network'
++** In the **DevEUI** field, enter the **DevEUI**.
++** In the **AppKey** field, enter the **AppKey**.
++** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
++** Under **After registration**, select the **View registered end device** option.
++** Click the **Register end device** button.
  [[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
@@ -252,30 +252,40 @@
  You will be navigated to the **Device overview** page.
++
  [[image:lt-22222-device-overview.png||height="625" width="1000"]]
--==== Joining ====
++==== 3.2.2.3 Joining ====
--Click on **Live data** in the left navigation. Then, power on LT-22222-L. It will join The Things Stack LoRaWAN network server. You can see the **join request**, **join accept**, followed by **uplink data messages** form the device showing in the **Live data** panel.
++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**).
++
++
  [[image:lt-22222-join-network.png||height="625" width="1000"]]
--Click on a message with the messge type, **Forward uplink data message**. You can see the  decoded uplink payload as shown below.
++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.
++{{info}}
++The Things Stack provides two levels of payload formatters: application level and device level. The device-level payload formatters **override **the application-level payload formatters.
++{{/info}}
++
  [[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
--== 3.3 Work Modes and their Uplink Payload formats ==
++== 3.3 Work Modes and Uplink Payload formats ==
--The LT-22222-L has 5 **work modes**. It also has an interrupt/trigger mode for different types of applications that can be used together with any working mode as an additional feature. The default mode is MOD1 and you can switch between these modes using AT commands.
++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.
  * (% style="color:blue" %)**MOD1**(%%): (default mode/factory set): 2ACI + 2AVI + DI + DO + RO
@@ -289,11 +289,19 @@
  * (% style="color:blue" %)**ADDMOD6**(%%): Trigger Mode, Optional, used together with MOD1 ~~ MOD5
++The uplink messages are sent over LoRaWAN FPort 2. By default, an uplink message is sent every 10 minutes.
++
  === 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
  (((
--The uplink payload is 11 bytes long. Uplink messages are sent over LoRaWAN FPort 2. By default, one uplink is sent every 10 minutes. (% style="display:none" wfd-invisible="true" %)
++This is the default mode.
++The uplink payload is 11 bytes long.
++
++(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
++The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
++It starts counting again when it reaches the maximum value.**(% style="display:none" wfd-invisible="true" %)
++
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
  |(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**2**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**
  |Value|(((
@@ -340,13 +340,13 @@
  * [1] The RO1 relay channel is CLOSED, and the RO1 LED is ON.
  * [0] The RO2 relay channel is OPEN, and the RO2 LED is OFF.
--* [1] DI3 - not used for LT-22222-L.
++* **[1] DI3 - not used for LT-22222-L.**
  * [0] DI2 channel input is LOW, and the DI2 LED is OFF.
  * [1] DI1 channel input state:
  ** DI1 is FLOATING when no sensor is connected between DI1+ and DI1-.
  ** DI1 is HIGH when a sensor is connected between DI1- and DI1+ and the sensor is ACTIVE.
  ** DI1 LED is ON in both cases.
--* [0] DO3 - not used for LT-22222-L.
++* **[0] DO3 - not used for LT-22222-L.**
  * [1] DO2 channel output is LOW, and the DO2 LED is ON.
  * [0] DO1 channel output state:
  ** DO1 is FLOATING when there is no load between DO1 and V+.
@@ -363,6 +363,10 @@
  (((
  The uplink payload is 11 bytes long.
++(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
++The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
++It starts counting again when it reaches the maximum value.**
++
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
  |(% style="background-color:#4f81bd; color:white" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white" %)**4**|(% style="background-color:#4f81bd; color:white" %)**4**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**|(% style="background-color:#4f81bd; color:white" %)**1**
  |Value|COUNT1|COUNT2 |DIDORO*|(((
@@ -371,7 +371,7 @@
  )))
  (((
--(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, DO3, DO2 and DO1, and its size is 1 byte long as shown below.
++(% style="color:#4f81bd" %)***DIDORO**(%%) is a combination of RO1, RO2, FIRST, Reserve, Reserve, DO3, DO2 and DO1, and its size is 1 byte long as shown below.
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
@@ -427,6 +427,9 @@
  === 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI ===
++(% style="color:red" %)**Note: The maximum count depends on the bytes it is.
++The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
++It starts counting again when it reaches the maximum value.**
  **LT22222-L**: In this mode, the DI1 is used as a counting pin.
@@ -477,7 +477,11 @@
  === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting ===
++(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
++The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
++It starts counting again when it reaches the maximum value.**
++
  (((
  **LT22222-L**: In this mode, the DI1 is used as a counting pin.
  )))
@@ -530,19 +530,23 @@
  (((
  **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 AVI Count to 60)**
--(% style="color:blue" %)**AT+VOLMAX=20000**(%%)**       (If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
++(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
--(% style="color:blue" %)**AT+VOLMAX=20000,0**(%%)**    (If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
++(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
--(% style="color:blue" %)**AT+VOLMAX=20000,1**(%%)**    (If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
++(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
  )))
  === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI ===
++(% style="color:red" %)**Note:The maximum count depends on the bytes it is.
++The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
++It starts counting again when it reaches the maximum value.**
++
  **LT22222-L**: In this mode, the DI1 is used as a counting pin.
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
@@ -600,15 +600,17 @@
  For example, if you configured the following commands:
--* **AT+MOD=1 **            **~-~->**   The normal working 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. LT will send uplink packets in two cases:
 . Periodically uplink (Based on TDC time). The payload is the same as in normal mode (MOD=1 for the commands above). These are (% style="color:#4f81bd" %)**unconfirmed**(%%) uplinks.
--1. Trigger uplink when the trigger condition is met. LT will send two packets in this case. The first uplink uses the payload specified in trigger mode (MOD=6). The second packet uses the normal mode payload (MOD=1 as set above). Both are (% style="color:#4f81bd" %)**CONFIRMED uplinks.**
++1. (((
++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 Command to set Trigger Condition**:
++(% style="color:#037691" %)**AT Commands to set Trigger Condition**:
  (% style="color:#4f81bd" %)**Trigger based on voltage**:
@@ -780,50 +780,68 @@
  )))
--== 3.4 Configure LT via AT Commands or Downlinks ==
++== 3.4 Configure LT-22222-L via AT Commands or Downlinks ==
--
  (((
--User can configure LT I/O Controller via AT Commands or LoRaWAN Downlinks.
++You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks.
  )))
  (((
  (((
--There are two kinds of Commands:
++There are two tytes of commands:
  )))
  )))
--* (% style="color:blue" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.5.4, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
++* (% style="color:blue" %)**Common commands**(%%):
--* (% style="color:blue" %)**Sensor Related Commands**(%%): These commands are special designed for LT-22222-L.  User can see these commands below:
++* (% style="color:blue" %)**Sensor-related commands**(%%):
--=== 3.4.1 Common Commands ===
++=== 3.4.1 Common commands ===
  (((
--These commands should be available for all Dragino sensors, such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]].
++These are available for each sensors and include actions such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]s.
  )))
++=== 3.4.2 Sensor-related commands ===
--=== 3.4.2 Sensor related commands ===
++These commands are specially designed for the LT-22222-L. Commands can be sent to the device using options such as an AT command or a LoRaWAN downlink payload.
  ==== 3.4.2.1 Set Transmit Interval ====
  Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
--* (% style="color:#037691" %)**AT command:**
++(% style="color:#037691" %)**AT command**
--(% style="color:blue" %)**AT+TDC=N**
++(% style="width:500px" %)
++|**Command**|AT+TDC<time>
++|**Response**|
++|**Parameters**|<time> uplink interval is in milliseconds
++|**Example**|(((
++AT+TDC=30000
--where N is the time in milliseconds.
++Sets the uplink interval to 30,000 milliseconds (30 seconds)
++)))
--**Example: **AT+TDC=30000. This will set the uplink interval to 30 seconds
++(% style="color:#037691" %)**Downlink payload**
++(% style="width:500px" %)
++|**Payload**|(((
++<prefix><time>
++)))
++|**Parameters**|(((
++<prefix> 0x01
--* (% style="color:#037691" %)**Downlink payload (prefix 0x01):**
++<time> uplink interval is in milliseconds, represented by 3  bytes in hexadecimal.
++)))
++|**Example**|(((
++01 **00 75 30**
--(% style="color:blue" %)**0x01 aa bb cc  **(%%)**   ~/~/ Same as AT+TDC=0x(aa bb cc)**
++Sets the uplink interval to 30,000 milliseconds (30 seconds)
++Conversion: 30000 (dec) = 00 75 30 (hex)
++See [[RapidTables>>https://www.rapidtables.com/convert/number/decimal-to-hex.html?x=30000]]
++)))
  ==== 3.4.2.2 Set the Work Mode (AT+MOD) ====
@@ -845,8 +845,8 @@
  ==== 3.4.2.3 Poll an uplink ====
++Requests the device to send an uplink.
--Asks the device to send an uplink.
  * (% style="color:#037691" %)**AT command:**(%%) There is no AT Command to poll uplink
@@ -860,7 +860,6 @@
  ==== 3.4.2.4 Enable/Disable Trigger Mode ====
--
  Enable or disable the trigger mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ADDMOD6=1 or 0**
@@ -878,9 +878,8 @@
  ==== 3.4.2.5 Poll trigger settings ====
++Polls the trigger settings.
--Polls the trigger settings
--
  * (% style="color:#037691" %)**AT Command:**
  There is no AT Command for this feature.
@@ -891,11 +891,10 @@
--==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as trigger ====
++==== 3.4.2.6 Enable / Disable DI1/DI2/DI3 as a trigger ====
++Enable or disable DI1/DI2/DI2 as a trigger.
--Enable or Disable DI1/DI2/DI2 as trigger,
--
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**Format: AT+DTRI=<DI1_TIRGGER_FlAG>,< DI2_TIRGGER_FlAG >**
  **Example:** AT+ DTRI =1,0 (Enable DI1 trigger / disable DI2 trigger)
@@ -907,11 +907,10 @@
--==== 3.4.2.7 Trigger1 – Set DI1 or DI3 as trigger ====
++==== 3.4.2.7 Trigger1 – Set DI or DI3 as a trigger ====
++Sets DI1 or DI3 (for LT-33222-L) as a trigger.
--Set DI1 or DI3(for LT-33222-L) trigger.
--
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG1=a,b**
  (% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge(for MOD=1).
@@ -926,12 +926,10 @@
  (% style="color:blue" %)**0x09 01 aa bb cc    ** (%%)    ~/~/ same as AT+TRIG1=aa,0x(bb cc)
++==== 3.4.2.8 Trigger2 – Set DI2 as a trigger ====
--==== 3.4.2.8 Trigger2 – Set DI2 as trigger ====
++Sets DI2 as a trigger.
--
--Sets DI2 trigger.
--
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+TRIG2=a,b**
  (% style="color:red" %)**a :** (%%)Interrupt mode. 0: falling edge; 1: rising edge, 2: falling and raising edge (for MOD=1).
@@ -946,12 +946,10 @@
  (% style="color:blue" %)**0x09 02 aa bb cc   **  (%%)~/~/ same as AT+TRIG2=aa,0x(bb cc)
++==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
--==== 3.4.2.9 Trigger – Set AC (current) as trigger ====
++Sets the current trigger based on the AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--
--Set current trigger , base on AC port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--
  * (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+ACLIM**
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 01 )**
@@ -962,9 +962,8 @@
  ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
++Sets the current trigger based on the AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--Set current trigger , base on AV port. See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--
  * (% style="color:#037691" %)**AT Command**(%%): (% style="color:blue" %)**AT+AVLIM    **(%%)**        See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]**
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xAA 00 )**
@@ -972,10 +972,8 @@
  (% style="color:blue" %)**0x AA 00 aa bb cc dd ee ff gg hh    ** (%%) ~/~/ same as AT+AVLIM See [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--
  ==== 3.4.2.11 Trigger – Set minimum interval ====
--
  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:blue" %)**AT+ATDC=5        ** ~/~/ (%%)Device won't response the second trigger within 5 minute after the first trigger.
@@ -992,6 +992,7 @@
  ==== 3.4.2.12 DO ~-~- Control Digital Output DO1/DO2/DO3 ====
++Controls the digital outputs DO1, DO2, and DO3
  * (% style="color:#037691" %)**AT Command**
@@ -1369,25 +1369,25 @@
  == 3.5 Integrating with ThingsEye.io ==
--The Things Stack applications can be integrated with ThingsEye.io. Once integrated, ThingsEye.io works as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
++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 MQTT Connection Information with The Things Stack Sandbox ===
++=== 3.5.1 Configuring The Things Stack ===
--We use The Things Stack Sandbox for demonstating the configuration but  other
++We use The Things Stack Sandbox in this example:
--* In **The Things Stack Sandbox**, select your application under **Applications**.
--* Select **MQTT** under **Integrations**.
--* In the **Connection information **section, for **Username**, The Things Stack displays an auto-generated username. You can use it or provide a new one.
--* For the **Password**, click the **Generate new API key** button to generate a password. You can see it by clicking on the **eye** button. The API key works as the password.
++* In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
++* Select **MQTT** under **Integrations** in the left menu.
++* In the **Connection information **section, under **Connection credentials**, The Things Stack displays an auto-generated **username**. You can use it or provide a new one.
++* Click the **Generate new API key** button to generate a password. You can view it by clicking on the **visibility toggle/eye** icon. The API key works as the password.
--NOTE. The username and  password (API key) you created here are required in the next section.
++{{info}}
++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"]]
  === 3.5.2 Configuring ThingsEye.io ===
--This section guides you on how to create an integration in ThingsEye to connect with The Things Stack MQTT server.
--
  * Login to your [[ThingsEye.io >>https://thingseye.io]]account.
  * Under the **Integrations center**, click **Integrations**.
  * Click the **Add integration** button (the button with the **+** symbol).
@@ -1424,9 +1424,9 @@
  **Downlink data converter (this is an optional step):**
  * Click the **Create new** button if it is not selected by default.
--* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name
++* Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name.
  * Click the **JavaScript** button.
--* Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found here.
++* 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"]]
@@ -1436,7 +1436,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 MQTT Connection information with The Things Stack Sandbox).
++* 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]]
@@ -1455,7 +1455,7 @@
  **Viewing integration details**:
--Click on your integration from the list. The Integration details window will appear with the Details tab selected. The Details tab shows all the settings you have provided for this integration.
++Click on your integration from the list. The **Integration details** window will appear with the **Details **tab selected. The **Details **tab shows all the settings you have provided for this integration.
  [[image:integration-details.png||height="686" width="1000"]]
@@ -1462,24 +1462,25 @@
  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.
--Note: See also ThingsEye documentation.
++{{info}}
++See also ThingsEye documentation.
++{{/info}}
--
  **Viewing events:**
--This tab  displays all the uplink messages from the LT-22222-L.
++The **Events **tab displays all the uplink messages from the LT-22222-L.
--* Click on the **Events **tab.
  * Select **Debug **from the **Event type** dropdown.
--* Select the** time frame** from the **time window**.
++* Select the** time frame** from the **time window**.
--[insert image]
++[[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.
--[insert image]
++* 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"]]
++
  **Deleting the integration**:
  If you want to delete this integration, click the **Delete integratio**n button.
@@ -1698,10 +1698,11 @@
  == 3.7 LEDs Indicators ==
++The table below lists the behavior of LED indicators for each port function.
  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
  |(% style="background-color:#4f81bd; color:white; width:50px" %)**LEDs**|(% style="background-color:#4f81bd; color:white; width:460px" %)**Feature**
--|**PWR**|Always on if there is power
++|**PWR**|Always on when there is power
  |**TX**|(((
  (((
  Device boot: TX blinks 5 times.
@@ -1708,7 +1708,7 @@
  )))
  (((
--Successful join network: TX ON for 5 seconds.
++Successful network join: TX remains ON for 5 seconds.
  )))
  (((
@@ -1715,7 +1715,7 @@
  Transmit a LoRa packet: TX blinks once
  )))
  )))
--|**RX**|RX blinks once when receiving a packet.
++|**RX**|RX blinks once when a packet is received.
  |**DO1**|For LT-22222-L: ON when DO1 is low, OFF when DO1 is high
  |**DO2**|For LT-22222-L: ON when DO2 is low, OFF when DO2 is high
  |**DI1**|(((
@@ -1727,13 +1727,14 @@
  |**RO1**|For LT-22222-L: ON when RO1 is closed, OFF when RO1 is open
  |**RO2**|For LT-22222-L: ON when RO2 is closed, OFF when RO2 is open
--= 4. Using AT Command =
++= 4. Using AT Commands =
--== 4.1 Connecting the LT-22222-L to a computer ==
++The LT-22222-L supports programming using AT Commands.
++== 4.1 Connecting the LT-22222-L to a PC ==
  (((
--The LT-22222-L supports programming using AT Commands. You can use a USB-to-TTL adapter along with a 3.5mm Program Cable to connect the LT-22222-L to a computer, as shown below.
++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:1653358238933-385.png]]
@@ -1740,7 +1740,7 @@
  (((
--On the PC, the user needs to set the (% style="color:#4f81bd" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) to a baud rate of (% style="color:green" %)**9600**(%%) to access to access serial console of LT-22222-L. The AT commands are disabled by default, and a password (default:(% style="color:green" %)**123456**)(%%) must be entered to active them, as shown below:
++On the PC, you need to set the (% style="color:#4f81bd" %)**serial tool **(%%)(such as [[PuTTY>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]] or [[SecureCRT>>https://www.vandyke.com/cgi-bin/releases.php?product=securecrt]]) to a baud rate of (% style="color:green" %)**9600**(%%) to access the serial console of LT-22222-L. Access to AT commands is disabled by default, and a password (default: (% style="color:green" %)**123456**)(%%) must be entered to enable AT command access, as shown below:
  )))
  [[image:1653358355238-883.png]]
@@ -1748,195 +1748,62 @@
  (((
  You can find more details in the [[AT Command Manual>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
--)))
--(((
--The following table lists all the AT commands related to the LT-22222-L, except for those used for switching between modes.
--
--AT+<CMD>?        : Help on <CMD>
++== 4.2 LT-22222-L related AT commands ==
  )))
  (((
--AT+<CMD>         : Run <CMD>
--)))
++The following is the list of all the AT commands related to the LT-22222-L, except for those used for switching between work modes.
--(((
--AT+<CMD>=<value> : Set the value
++* AT+<CMD>? : Help on <CMD>
++* AT+<CMD> : Run <CMD>
++* AT+<CMD>=<value> : Set the value
++* AT+<CMD>=? : Get the value
++* ATZ: Trigger a reset of the MCU
++* ##**AT+FDR**##: Reset Parameters to factory default, reserve keys
++* **##AT+DEUI##**: Get or set the Device EUI (DevEUI)
++* **##AT+DADDR##**: Get or set the Device Address (DevAddr)
++* **##AT+APPKEY##**: Get or set the Application Key (AppKey)
++* AT+NWKSKEY: Get or set the Network Session Key (NwkSKey)
++* AT+APPSKEY: Get or set the Application Session Key (AppSKey)
++* AT+APPEUI: Get or set the Application EUI (AppEUI)
++* AT+ADR: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
++* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
++* AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)
++* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
++* AT+PNM: Get or set the public network mode. (0: off, 1: on)
++* AT+RX2FQ: Get or set the Rx2 window frequency
++* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
++* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
++* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
++* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
++* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
++* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
++* AT+NWKID: Get or set the Network ID
++* AT+FCU: Get or set the Frame Counter Uplink (FCntUp)
++* AT+FCD: Get or set the Frame Counter Downlink (FCntDown)
++* AT+CLASS: Get or set the Device Class
++* AT+JOIN: Join network
++* AT+NJS: Get OTAA Join Status
++* AT+SENDB: Send hexadecimal data along with the application port
++* AT+SEND: Send text data along with the application port
++* AT+RECVB: Print last received data in binary format (with hexadecimal values)
++* AT+RECV: Print last received data in raw format
++* AT+VER: Get current image version and Frequency Band
++* AT+CFM: Get or Set the confirmation mode (0-1)
++* AT+CFS: Get confirmation status of the last AT+SEND (0-1)
++* AT+SNR: Get the SNR of the last received packet
++* AT+RSSI: Get the RSSI of the last received packet
++* AT+TDC: Get or set the application data transmission interval in ms
++* AT+PORT: Get or set the application port
++* AT+DISAT: Disable AT commands
++* AT+PWORD: Set password, max 9 digits
++* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode
++* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470
++* AT+CFG: Print all settings
  )))
--(((
--AT+<CMD>=?       :  Get the value
--)))
--(((
--ATZ: Trig a reset of the MCU
--)))
--
--(((
--AT+FDR: Reset Parameters to Factory Default, Keys Reserve
--)))
--
--(((
--AT+DEUI: Get or Set the Device EUI
--)))
--
--(((
--AT+DADDR: Get or Set the Device Address
--)))
--
--(((
--AT+APPKEY: Get or Set the Application Key
--)))
--
--(((
--AT+NWKSKEY: Get or Set the Network Session Key
--)))
--
--(((
--AT+APPSKEY:  Get or Set the Application Session Key
--)))
--
--(((
--AT+APPEUI:    Get or Set the Application EUI
--)))
--
--(((
--AT+ADR: Get or Set the Adaptive Data Rate setting. (0: off, 1: on)
--)))
--
--(((
--AT+TXP: Get or Set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Spec)
--)))
--
--(((
--AT+DR:  Get or Set the Data Rate. (0-7 corresponding to DR_X)
--)))
--
--(((
--AT+DCS: Get or Set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
--)))
--
--(((
--AT+PNM: Get or Set the public network mode. (0: off, 1: on)
--)))
--
--(((
--AT+RX2FQ: Get or Set the Rx2 window frequency
--)))
--
--(((
--AT+RX2DR: Get or Set the Rx2 window data rate (0-7 corresponding to DR_X)
--)))
--
--(((
--AT+RX1DL: Get or Set the delay between the end of the Tx and the Rx Window 1 in ms
--)))
--
--(((
--AT+RX2DL: Get or Set the delay between the end of the Tx and the Rx Window 2 in ms
--)))
--
--(((
--AT+JN1DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
--)))
--
--(((
--AT+JN2DL: Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
--)))
--
--(((
--AT+NJM:    Get or Set the Network Join Mode. (0: ABP, 1: OTAA)
--)))
--
--(((
--AT+NWKID: Get or Set the Network ID
--)))
--
--(((
--AT+FCU: Get or Set the Frame Counter Uplink
--)))
--
--(((
--AT+FCD: Get or Set the Frame Counter Downlink
--)))
--
--(((
--AT+CLASS: Get or Set the Device Class
--)))
--
--(((
--AT+JOIN: Join network
--)))
--
--(((
--AT+NJS: Get OTAA Join Status
--)))
--
--(((
--AT+SENDB: Send hexadecimal data along with the application port
--)))
--
--(((
--AT+SEND: Send text data along with the application port
--)))
--
--(((
--AT+RECVB: Print last received data in binary format (with hexadecimal values)
--)))
--
--(((
--AT+RECV: Print last received data in raw format
--)))
--
--(((
--AT+VER:  Get current image version and Frequency Band
--)))
--
--(((
--AT+CFM: Get or Set the confirmation mode (0-1)
--)))
--
--(((
--AT+CFS:  Get confirmation status of the last AT+SEND (0-1)
--)))
--
--(((
--AT+SNR: Get the SNR of the last received packet
--)))
--
--(((
--AT+RSSI: Get the RSSI of the last received packet
--)))
--
--(((
--AT+TDC: Get or set the application data transmission interval in ms
--)))
--
--(((
--AT+PORT: Get or set the application port
--)))
--
--(((
--AT+DISAT: Disable AT commands
--)))
--
--(((
--AT+PWORD: Set password, max 9 digits
--)))
--
--(((
--AT+CHS: Get or Set Frequency (Unit: Hz) for Single Channel Mode
--)))
--
--(((
--AT+CHE: Get or Set eight channels mode, Only for US915, AU915, CN470
--)))
--
--(((
--AT+CFG: Print all settings
--)))
--
--
  == 4.2 Common AT Command Sequence ==
  === 4.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
@@ -1945,41 +1945,41 @@
  (((
--(% style="color:blue" %)**If device has not joined network yet:**
++(% style="color:blue" %)**If the device has not joined the network yet:**
  )))
  )))
  (((
--(% style="background-color:#dcdcdc" %)**123456**
++(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**##
  )))
  (((
--(% style="background-color:#dcdcdc" %)**AT+FDR**
++(% style="background-color:#dcdcdc" %)##**AT+FDR ~/~/reset parameters to factory default, reserve keys**##
  )))
  (((
--(% style="background-color:#dcdcdc" %)**123456**
++(% style="background-color:#dcdcdc" %)##**123456 ~/~/enable AT commands access**##
  )))
  (((
--(% style="background-color:#dcdcdc" %)**AT+NJM=0**
++(% style="background-color:#dcdcdc" %)##**AT+NJM=0 ~/~/set to ABP mode**##
  )))
  (((
--(% style="background-color:#dcdcdc" %)**ATZ**
++(% style="background-color:#dcdcdc" %)##**ATZ ~/~/reset MCU**##
  )))
  (((
--(% style="color:blue" %)**If device already joined network:**
++(% style="color:blue" %)**If the device has already joined the network:**
  )))
  (((
--(% style="background-color:#dcdcdc" %)**AT+NJM=0**
++(% style="background-color:#dcdcdc" %)##**AT+NJM=0**##
  )))
  (((
--(% style="background-color:#dcdcdc" %)**ATZ**
++(% style="background-color:#dcdcdc" %)##**ATZ**##
  )))
@@ -2079,35 +2079,48 @@
  == 5.1 Counting how many objects pass through the flow Line ==
++See [[How to set up to setup counting for objects passing through the flow line>>How to set up to count objects pass in flow line]]?
--Reference Link: [[How to set up to setup counting for objects passing through the flow line>>How to set up to count objects pass in flow line]]?
--
  = 6. FAQ =
--== 6.1 How to upgrade the image? ==
++This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
--The LT-22222-L I/O Controller is shipped with a 3.5mm cable, which is used to upload an image to LT in order to:
++== 6.1 How to update the firmware? ==
--* Support new features.
--* Fix bugs.
--* Change LoRaWAN bands.
++Dragino frequently releases firmware updates for the LT-22222-L.
--Below is the hardware connection setup for uploading an image to the LT:
++Updating your LT-22222-L with the latest firmware version helps to:
++* Support new features
++* Fix bugs
++* Change LoRaWAN frequency bands
++
++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
++* Download and install the [[STM32 Flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]]. (replaced by STM32CubeProgrammer)
++* Download the latest firmware image from [[LT-22222-L firmware image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]]. Check the file name of the firmware to find the correct region.
++
++{{info}}
++As of this writing, the latest firmware version available for the LT-22222-L is v1.6.1.
++{{/info}}
++
++Below is the hardware setup for uploading a firmware image to the LT-22222-L:
++
++
  [[image:1653359603330-121.png]]
--(((
--(% style="color:#0000ff" %)**Step 1**(%%)**:** Download the F[[lash Loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]].
--(% style="color:#0000ff" %)**Step 2**(%%)**:** Download the [[LT Image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]].
--(% style="color:#0000ff" %)**Step 3**(%%)**:** Open the Flash Loader and choose the correct COM port to update.
--
++Start the STM32 Flash Loader and choose the correct COM port to update.
  (((
++(((
  (% style="color:blue" %)**For LT-22222-L**(%%):
--Hold down the PRO button, then momentarily press the RST reset button. The (% style="color:red" %)**DO1 LED**(%%) will change from OFF to ON. When the (% style="color:red" %)**DO1 LED**(%%) is ON, it indicates that the device is in download mode.
++
++Hold down the **PRO** button, then briefly press the **RST** button. The **DO1** LED will change from OFF to ON. When the **DO1** LED is ON, it indicates that the device is in firmware download mode.
  )))
@@ -2129,9 +2129,7 @@
  (((
  (((
--== 6.2 How to change the LoRa Frequency Bands/Region? ==
--
--
++== 6.2 How to change the LoRaWAN frequency band/region? ==
  )))
  )))
@@ -2142,9 +2142,7 @@
  (((
--== 6.3 How to set up LT to work with a Single Channel Gateway, such as LG01/LG02? ==
--
--
++== 6.3 How to setup LT to work with a Single Channel Gateway, such as LG01/LG02? ==
  )))
  (((
@@ -2215,156 +2215,137 @@
  == 6.4 How to change the uplink interval? ==
--
  Please see this link: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/]]
--== 6.5 Can I see the counting event in Serial? ==
++== 6.5 Can I see the counting event in the serial output? ==
--
  (((
--User can run AT+DEBUG command to see the counting event in serial. If firmware too old and doesn't support AT+DEBUG. User can update to latest firmware first.
++You can run the AT command AT+DEBUG to view the counting event in the serial output. If the firmware is too old and doesn’t support AT+DEBUG, update to the latest firmware first.
  == 6.6 Can I use point-to-point communication with LT-22222-L? ==
++Yes, you can. Please refer to the [[Point-to-Point Communication of LT-22222-L>>https://wiki.dragino.com/xwiki/bin/view/Main/%20Point%20to%20Point%20Communication%20of%20LT-22222-L/]] page. The firmware that supports point-to-point communication can be found [[here>>https://github.com/dragino/LT-22222-L/releases]].
--Yes, please refer [[Point to Point Communication>>doc:Main. Point to Point Communication of LT-22222-L.WebHome]]. this is [[firmware>>https://github.com/dragino/LT-22222-L/releases]].
--
  )))
  (((
--== 6.7 Why does the relay output become the default and open relay after the lt22222 is powered off? ==
++== 6.7 Why does the relay output default to an open relay after the LT-22222-L is powered off? ==
++* If the device is not properly shut down and is directly powered off.
++* It will default to a power-off state.
++* In modes 2 to 5, the DO/RO status and pulse count are saved to flash memory.
++* After a restart, the status before the power failure will be read from flash.
--If the device is not shut down, but directly powered off.
++== 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
--It will default that this is a power-off state.
++The LT-22222-L's built-in relay is Normally Open (NO). You can use an external relay to achieve a Normally Closed (NC) configuration. The circuit diagram is shown below:
--In modes 2 to 5, DO RO status and pulse count are saved in flash.
--After restart, the status before power failure will be read from flash.
--
--
--== 6.8 Can i set up LT-22222-L as a NC(Normal Close) Relay? ==
--
--
--LT-22222-L built-in relay is NO (Normal Open). User can use an external relay to achieve Normal Close purpose. Diagram as below:
--
--
  [[image:image-20221006170630-1.png||height="610" width="945"]]
--== 6.9 Can LT22222-L save RO state? ==
++== 6.9 Can the LT-22222-L save the RO state? ==
++The firmware version must be at least 1.6.0.
--Firmware version needs to be no less than 1.6.0.
++== 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
--== 6.10 Why does the LT22222 always report 15.585V when measuring AVI? ==
++It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
--It is likely that the GND is not connected during the measurement, or the wire connected to the GND is loose.
++= 7. Troubleshooting =
++This section provides some known troubleshooting tips.
--= 7. Trouble Shooting =
++
  )))
  (((
  (((
--== 7.1 Downlink doesn't work, how to solve it? ==
--
--
++== 7.1 Downlink isn't working. How can I solve this? ==
  )))
  )))
  (((
--Please see this link for how to debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]]
++Please refer to this link for debugging instructions: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H5.1Howitwork"]]
  )))
  (((
--== 7.2 Have trouble to upload image. ==
--
--
++== 7.2 Having trouble uploading an image? ==
  )))
  (((
--See this link for trouble shooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
++Please refer to this link for troubleshooting: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
  )))
  (((
--== 7.3 Why I can't join TTN in US915 /AU915 bands? ==
--
--
++== 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
  )))
  (((
--It might be about the channels mapping. [[Please see this link for detail>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
++It might be related to the channel mapping. [[Please refer to this link for details.>>https://github.com/dragino/LT-22222-L/releases]]
  )))
--== 7.4 Why can LT22222 perform Uplink normally, but cannot receive Downlink? ==
++== 7.4 Why can the LT-22222-L perform Uplink normally, but cannot receive Downlink? ==
++The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
++Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
--The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue state.
--Use this command to bring their counts back together: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
++= 8. Ordering information =
--= 8. Order Info =
--
--
  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
  (% style="color:#4f81bd" %)**XXX:**
--* (% style="color:red" %)**EU433**(%%):   LT with frequency bands EU433
--* (% style="color:red" %)**EU868**(%%):   LT with frequency bands EU868
--* (% style="color:red" %)**KR920**(%%):   LT with frequency bands KR920
--* (% style="color:red" %)**CN470**(%%):  LT with frequency bands CN470
--* (% style="color:red" %)**AS923**(%%):   LT with frequency bands AS923
--* (% style="color:red" %)**AU915**(%%):  LT with frequency bands AU915
--* (% style="color:red" %)**US915**(%%):  LT with frequency bands US915
--* (% style="color:red" %)**IN865**(%%):   LT with frequency bands IN865
--* (% style="color:red" %)**CN779**(%%):  LT with frequency bands CN779
++* (% style="color:red" %)**EU433**(%%): LT with frequency bands EU433
++* (% style="color:red" %)**EU868**(%%): LT with frequency bands EU868
++* (% style="color:red" %)**KR920**(%%): LT with frequency bands KR920
++* (% style="color:red" %)**CN470**(%%): LT with frequency bands CN470
++* (% style="color:red" %)**AS923**(%%): LT with frequency bands AS923
++* (% style="color:red" %)**AU915**(%%): LT with frequency bands AU915
++* (% style="color:red" %)**US915**(%%): LT with frequency bands US915
++* (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865
++* (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779
--= 9. Packing Info =
++= 9. Packing information =
++**Package includes**:
--**Package Includes**:
++* 1 x LT-22222-L I/O Controller
++* 1 x LoRa antenna matched to the frequency of the LT-22222-L
++* 1 x bracket for DIN rail mounting
++* 1 x 3.5mm programming cable
--* LT-22222-L I/O Controller x 1
--* Stick Antenna for LoRa RF part x 1
--* Bracket for controller x1
--* Program cable x 1
--
  **Dimension and weight**:
  * Device Size: 13.5 x 7 x 3 cm
--* Device Weight: 105g
++* Device Weight: 105 g
  * Package Size / pcs : 14.5 x 8 x 5 cm
--* Weight / pcs : 170g
++* Weight / pcs : 170 g
  = 10. Support =
--
  * (((
--Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
++Support is available Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different time zones, we cannot offer live support. However, your questions will be answered as soon as possible within the aforementioned schedule.
  )))
  * (((
--Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[Support@dragino.cc>>mailto:Support@dragino.cc]]
++Please provide as much information as possible regarding your inquiry (e.g., product models, a detailed description of the problem, steps to replicate it, etc.) and send an email to [[support@dragino.cc>>mailto:support@dragino.cc]]
--
  )))
  = 11. Reference =
--
  * LT-22222-L: [[http:~~/~~/www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html>>url:http://www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html]]
  * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]]
  * [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]

thingseye-events.png

Author

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

Size

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

Content

thingseye-json.png

Author

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

Size

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

Content

usb-ttl-programming.png

Author

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

Size

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

Content

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

Summary

Details

Applications

Navigation