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

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

From 217.1 to 218.1 From 230.12 to 230.13

From version 218.1

edited by Dilisi S
on 2024/11/25 01:50

Change comment: Uploaded new attachment "lt-22222-l-joining.png", version {1}

To version 230.12

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Author

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

Content

@@ -21,6 +21,7 @@
  == 1.1 What is the LT-22222-L I/O Controller? ==
++
  (((
  (((
  {{info}}
@@ -54,8 +54,10 @@
  (% class="wikigeneratedid" %)
  [[image:lorawan-nw.jpg||height="354" width="900"]]
++
  == 1.2 Specifications ==
++
  (% style="color:#037691" %)**Hardware System:**
  * STM32L072xxxx MCU
@@ -95,8 +95,11 @@
  * Automatic RF Sense and CAD with ultra-fast AFC.
  * Packet engine up to 256 bytes with CRC.
++
++
  == 1.3 Features ==
++
  * LoRaWAN Class A & Class C modes
  * Optional Customized LoRa Protocol
  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/RU864/IN865/MA869
@@ -105,8 +105,11 @@
  * Firmware upgradable via program port
  * Counting
++
++
  == 1.4 Applications ==
++
  * Smart buildings & home automation
  * Logistics and supply chain management
  * Smart metering
@@ -114,13 +114,17 @@
  * Smart cities
  * Smart factory
++
++
  == 1.5 Hardware Variants ==
--(% style="width:524px" %)
--|(% style="width:94px" %)**Model**|(% style="width:98px" %)**Photo**|(% style="width:329px" %)**Description**
--|(% style="width:94px" %)**LT33222-L**|(% style="width:98px" %)(((
--
--)))|(% style="width:329px" %)(((
++
++(% border="1" cellspacing="3" style="width:510px" %)
++|(% style="background-color:#4f81bd; color:white; width:94px" %)**Model**|(% style="background-color:#4f81bd; color:white; width:172px" %)**Photo**|(% style="background-color:#4f81bd; color:white; width:244px" %)**Description**
++|(% style="width:94px" %)**LT-22222-L**|(% style="width:172px" %)(((
++(% style="text-align:center" %)
++[[image:lt33222-l.jpg||height="116" width="100"]]
++)))|(% style="width:256px" %)(((
  * 2 x Digital Input (Bi-direction)
  * 2 x Digital Output
  * 2 x Relay Output (5A@250VAC / 30VDC)
@@ -174,7 +174,7 @@
  The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s **positive wire** to the **VIN** and the **negative wire** to the **GND** screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered.
  {{warning}}
--**We recommend that you power on the LT-22222-L after configuring its registration information with a LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.**
++**We recommend that you power on the LT-22222-L after adding its registration information to the LoRaWAN network server. Otherwise, the device will continuously send join-request messages to attempt to join a LoRaWAN network but will fail.**
  {{/warning}}
@@ -237,7 +237,7 @@
  *** **Profile (Region)**: Select the region that matches your device.
  ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
--[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]]
++[[image:lt-22222-l-dev-repo-reg-p1.png]]
  * Register end device page continued...
@@ -247,7 +247,7 @@
  ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application.
  ** Under **After registration**, select the **View registered end device** option.
--[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]]
++[[image:lt-22222-l-dev-repo-reg-p2.png]]
  ==== 3.2.2.3 Adding device manually ====
@@ -261,7 +261,7 @@
  ** Select the option **Over the air activation (OTAA)** under the **Activation mode.**
  ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list.
--[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]]
++[[image:lt-22222-l-manually-p1.png]]
  * Register end device page continued...
@@ -272,13 +272,13 @@
  ** Under **After registration**, select the **View registered end device** option.
  ** Click the **Register end device** button.
--[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]]
++[[image:lt-22222-l-manually-p2.png]]
  You will be navigated to the **Device overview** page.
--[[image:lt-22222-device-overview.png||height="625" width="1000"]]
++[[image:lt-22222-device-overview.png]]
  ==== 3.2.2.4 Joining ====
@@ -288,9 +288,10 @@
  Now power on your LT-22222-L. The **TX LED** will **fast-blink 5 times** which means the LT-22222-L will enter the **work mode** and start to **join** The Things Stack network server. The **TX LED** will be on for **5 seconds** after joining the network. In the **Live data** panel, you can see the **join-request** and **join-accept** messages exchanged between the device and the network server.
--[[image:lt-22222-join-network.png||height="625" width="1000"]]
++[[image:lt-22222-l-joining.png]]
++
  ==== 3.2.2.5 Uplinks ====
@@ -307,9 +307,15 @@
  The Things Stack provides two levels of payload formatters: application level and device level. The device-level payload formatters **override **the application-level payload formatters.
  {{/info}}
--[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]]
++[[image:lt-22222-ul-payload-fmt.png]]
++We also have a payload formatter that resolves some decoding issues present in the Device Repository formatter. You can add it under the Custom JavaScript formatter. It can be found [[here>>https://github.com/dragino/dragino-end-node-decoder/blob/main/LT22222-L/v1.6_decoder_ttn%20.txt]]:
++
++(% class="wikigeneratedid" %)
++[[image:lt-22222-l-js-custom-payload-formatter.png]]
++
++
  ==== 3.2.2.6 Downlinks ====
  When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
@@ -598,11 +598,11 @@
  (% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)**
--(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
++(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), the counter increases by 1)**
--(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)**
++(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If the AVI1 voltage is lower than VOLMAX (20000mV =20V), counter increases by 1)**
--(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)**
++(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), counter increases by 1)**
  )))
@@ -721,9 +721,9 @@
  (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:**
--Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
++**Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**
--Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
++**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4
    AA: Type Code for this downlink Command:
@@ -752,7 +752,7 @@
  MOD6 Payload: total of 11 bytes
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
++(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
  |(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:69px" %)**1**|(% style="background-color:#4f81bd; color:white; width:69px" %)**1**|(% style="background-color:#4f81bd; color:white; width:109px" %)**1**|(% style="background-color:#4f81bd; color:white; width:49px" %)**6**|(% style="background-color:#4f81bd; color:white; width:109px" %)**1**|(% style="background-color:#4f81bd; color:white; width:50px" %)**1**
  |Value|(((
  TRI_A FLAG
@@ -766,7 +766,7 @@
  (% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
++(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
  |(((
  AV1_LOW
@@ -790,12 +790,12 @@
  **Example:**
--10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW
++10100000: This means the system is configured to use the triggers AV1_LOW and AV2_LOW.
  (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:515px" %)
++(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
  |**bit 7**|**bit 6**|**bit 5**|**bit 4**|**bit 3**|**bit 2**|**bit 1**|**bit 0**
  |(((
  AV1_LOW
@@ -819,31 +819,31 @@
  **Example:**
--10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.
++10000000: The uplink is triggered by AV1_LOW, indicating that the voltage is too low.
  (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:674px" %)
--|(% style="width:64px" %)**bit 7**|(% style="width:68px" %)**bit 6**|(% style="width:63px" %)**bit 5**|(% style="width:66px" %)**bit 4**|(% style="width:109px" %)**bit 3**|(% style="width:93px" %)**bit 2**|(% style="width:109px" %)**bit 1**|(% style="width:99px" %)**bit 0**
--|(% style="width:64px" %)N/A|(% style="width:68px" %)N/A|(% style="width:63px" %)N/A|(% style="width:66px" %)N/A|(% style="width:109px" %)DI2_STATUS|(% style="width:93px" %)DI2_FLAG|(% style="width:109px" %)DI1_STATUS|(% style="width:99px" %)DI1_FLAG
++(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
++|(% style="width:50px" %)**bit 7**|(% style="width:50px" %)**bit 6**|(% style="width:50px" %)**bit 5**|(% style="width:50px" %)**bit 4**|(% style="width:90px" %)**bit 3**|(% style="width:80px" %)**bit 2**|(% style="width:90px" %)**bit 1**|(% style="width:95px" %)**bit 0**
++|(% style="width:49px" %)N/A|(% style="width:53px" %)N/A|(% style="width:53px" %)N/A|(% style="width:55px" %)N/A|(% style="width:99px" %)DI2_STATUS|(% style="width:83px" %)DI2_FLAG|(% style="width:98px" %)DI1_STATUS|(% style="width:85px" %)DI1_FLAG
--* Each bits shows which status has been triggered on this uplink.
++* Each bit shows which status has been triggered on this uplink.
  **Example:**
--00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.
++00000111: This means both DI1 and DI2 triggers are enabled, and this packet is trigger by DI1.
--00000101: Means both DI1 and DI2 trigger are enabled.
++00000101: This means both DI1 and DI2 triggers are enabled.
--(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable.
++(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled.
--Downlink command to poll MOD6 status:
++Downlink command to poll/request MOD6 status:
  **AB 06**
--When device got this command, it will send the MOD6 payload.
++When device receives this command, it will send the MOD6 payload.
  === 3.3.7 Payload Decoder ===
@@ -857,6 +857,7 @@
  == 3.4 Configure LT-22222-L via AT Commands or Downlinks ==
++
  (((
  You can configure LT-22222-L I/O Controller via AT Commands or LoRaWAN Downlinks.
  )))
@@ -871,19 +871,25 @@
  * (% style="color:blue" %)**Sensor-related commands**(%%):
++
  === 3.4.1 Common commands ===
++
  (((
  These are available for each sensors and include actions such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]s.
++
++
  )))
  === 3.4.2 Sensor-related commands ===
++
  These commands are specially designed for the LT-22222-L. Commands can be sent to the device using options such as an AT command or a LoRaWAN downlink payload.
  ==== 3.4.2.1 Set Transmit/Uplink Interval ====
++
  Sets the uplink interval of the device. The default uplink transmission interval is 10 minutes.
  (% style="color:#037691" %)**AT command**
@@ -890,8 +890,15 @@
  (% border="2" style="width:500px" %)
  |**Command**|AT+TDC=<time>
--|**Response**|
--|**Parameters**|**time** : uplink interval is in **milliseconds**
++|**Parameters**|**time **: uplink interval in milliseconds
++|**Get**|AT+TDC=?
++|**Response**|(((
++current uplink interval
++
++OK
++)))
++|**Set**|AT+TDC=<time>
++|**Response**|OK
  |**Example**|(((
  AT+TDC=30000
@@ -907,7 +907,7 @@
  |**Parameters**|(((
  **prefix** : 0x01
--**time** : uplink interval is in **seconds**, represented by **3  bytes** in **hexadecimal**.
++**time** : uplink interval in **seconds**, represented by **3  bytes** in **hexadecimal**.
  )))
  |**Example**|(((
 **00 00 1E**
@@ -923,13 +923,13 @@
  ==== 3.4.2.2 Set the Working Mode (AT+MOD) ====
++
  Sets the working mode.
  (% style="color:#037691" %)**AT command**
  (% border="2" style="width:500px" %)
--|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MODE=<working_mode>
--|(% style="width:97px" %)**Response**|(% style="width:413px" %)
++|(% style="width:97px" %)**Command**|(% style="width:413px" %)AT+MOD=<working_mode>
  |(% style="width:97px" %)**Parameters**|(% style="width:413px" %)(((
  **working_mode** :
@@ -945,6 +945,18 @@
 = Trigger Mode, Optional, used together with MOD1 ~~ MOD5
  )))
++|(% style="width:97px" %)**Get**|(% style="width:413px" %)AT+MOD=?
++|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
++Current working mode
++
++OK
++)))
++|(% style="width:97px" %)**Set**|(% style="width:413px" %)AT+MOD=<working_mode>
++|(% style="width:97px" %)**Response**|(% style="width:413px" %)(((
++Attention:Take effect after ATZ
++
++OK
++)))
  |(% style="width:97px" %)**Example**|(% style="width:413px" %)(((
  AT+MOD=2
@@ -967,8 +967,10 @@
  Sets the device to working mode 2 (Double DI Counting + DO + RO)
  )))
--==== 3.4.2.3 Poll an uplink ====
++==== 3.4.2.3 Request an uplink from the device ====
++
++
  Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.
  (% style="color:#037691" %)**AT command**
@@ -986,8 +986,10 @@
  Requests an uplink from LT-22222-L.
  )))
++
  ==== 3.4.2.4 Enable/Disable Trigger Mode ====
++
  Enable or disable the trigger mode for the current working mode (see also [[ADDMOD6>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]).
  (% style="color:#037691" %)**AT Command**
@@ -1023,10 +1023,12 @@
  Enable trigger mode for the current working mode
  )))
--==== 3.4.2.5 Poll trigger settings ====
--Polls the trigger settings.
++==== 3.4.2.5 Request trigger settings ====
++
++Requests the trigger settings.
++
  (% style="color:#037691" %)**AT Command:**
  There is no AT Command available for this feature.
@@ -1042,8 +1042,10 @@
  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.
  (% style="color:#037691" %)**AT Command**
@@ -1096,11 +1096,12 @@
  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**
  (% border="2" style="width:500px" %)
@@ -1135,11 +1135,12 @@
  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**
  (% border="2" style="width:500px" %)
@@ -1169,8 +1169,10 @@
  )))
  |(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64**
++
  ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
++
  Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
  (% style="color:#037691" %)**AT Command**
@@ -1218,8 +1218,10 @@
  )))
  |(% style="width:104px" %)Note|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
++
  ==== 3.4.2.10 Trigger – Set AV (voltage) as trigger ====
++
  Sets the current trigger based on the AV port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
  (% style="color:#037691" %)**AT Command**
@@ -1265,8 +1265,10 @@
  )))
  |(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
++
  ==== 3.4.2.11 Trigger – Set minimum interval ====
++
  Sets the AV and AC trigger minimum interval. The device won't respond to a second trigger within this set time after the first trigger.
  (% style="color:#037691" %)**AT Command**
@@ -1300,8 +1300,10 @@
  )))
  |(% 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**
@@ -1332,11 +1332,11 @@
  (((
 : Low,  00: High,  11: No action
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
--|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**DO1**|(% style="background-color:#4f81bd; color:white" %)**DO2**|(% style="background-color:#4f81bd; color:white" %)**DO3**
--|02  01  00  11|Low|High|No Action
--|02  00  11  01|High|No Action|Low
--|02  11  01  00|No Action|Low|High
++(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:383px" %)
++|(% style="background-color:#4f81bd; color:white; width:126px" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white; width:85px" %)**DO1**|(% style="background-color:#4f81bd; color:white; width:86px" %)**DO2**|(% style="background-color:#4f81bd; color:white; width:86px" %)**DO3**
++|(% style="width:126px" %)02  01  00  11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action
++|(% style="width:126px" %)02  00  11  01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low
++|(% style="width:126px" %)02  11  01  00|(% style="width:85px" %)No Action|(% style="width:86px" %)Low|(% style="width:86px" %)High
  )))
  (((
@@ -1350,30 +1350,29 @@
  )))
  )))
++
  ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
  * (% style="color:#037691" %)**AT Command**
--There is no AT Command to control Digital Output
++There is no AT command to control the digital output.
  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
--(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Set DO1/DO2/DO3 output with time control
++(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control
--
  This is to control the digital output time of DO pin. Include four bytes:
--(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
++(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)
--(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode
++(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode
--01: DO pins will change back to original state after timeout.
++**01:** DO pins revert to their original state after the timeout.
++**00:** DO pins switch to an inverted state after the timeout.
--00: DO pins will change to an inverter state after timeout
--
  (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
@@ -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 Port status:
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
  |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
@@ -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 Port status:
  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
  |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
@@ -1398,7 +1398,7 @@
  |0x00|DO3 set to high
  |0x11|DO3 NO Action
--(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)
++(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms)
  (% style="color:red" %)**Note: **
@@ -1407,7 +1407,7 @@
     Before firmware v1.6.0, the latch time only supported 2 bytes.
--(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
++(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
  **Example payload:**
@@ -1434,16 +1434,16 @@
  * (% style="color:#037691" %)**AT Command:**
--There is no AT Command to control Relay Output
++There is no AT Command to control the Relay Output
  * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
--(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Set RO1/RO2 output
++(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Sets RO1/RO2 output
  (((
--If payload is 0x030100, it means setting RO1 to close and RO2 to open.
++If the payload is 0x030100, it means setting RO1 to close and RO2 to open.
  )))
  (((
@@ -1461,28 +1461,29 @@
  |03  00  01|Open|Close
  )))
--(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
++(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
  ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
++
  Controls the relay output time.
  * (% style="color:#037691" %)**AT Command:**
--There is no AT Command to control Relay Output
++There is no AT Command to control the Relay Output
  * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
--(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Set RO1/RO2 relay with time control
++(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
--This is to control the relay output time. It includes four bytes:
++This controls the relay output time and includes 4 bytes:
--(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
++(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)
--(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
++(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode
 : Relays will change back to their original state after timeout.
@@ -1489,12 +1489,12 @@
 : Relays will change to the inverter state after timeout.
--(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
++(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status:
  [[image:image-20221008095908-1.png||height="364" width="564"]]
--(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms
++(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes (cc)**(%%): Latching time. Unit: ms
  (% style="color:red" %)**Note:**
@@ -1504,7 +1504,7 @@
     Before firmware v1.6.0, the latch time only supported 2 bytes.
--(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
++(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
  **Example payload:**
@@ -1663,8 +1663,10 @@
  )))
  |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
--==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
++==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ====
++
++
  This 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**
@@ -1694,8 +1694,10 @@
  Sets the device to save its counting results to the memory every 60 seconds.
  )))
--==== 3.4.2.20 Reset save RO DO state ====
++==== 3.4.2.20 Reset saved RO and DO states ====
++
++
  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**
@@ -1743,8 +1743,10 @@
  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:**
@@ -1774,6 +1774,7 @@
  ==== 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**
@@ -1803,6 +1803,7 @@
  ==== 3.4.2.23 Resetting the downlink packet count ====
++
  This command manages how the node handles mismatched downlink packet counts. It offers two modes: one disables the reception of further downlink packets if discrepancies occur, while the other resets the downlink packet count to align with the server, ensuring continued communication.
  (% style="color:#037691" %)**AT Command**
@@ -1879,45 +1879,36 @@
  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**(%%)**:**
++This command enables the device to immediately uplink the payload of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100.
--(% style="color:blue" %)**AT+RPL=5**   (%%)  ~/~/ After receiving the package from the server, it will immediately upload the content of the package to the server, the port number is 100.
++(% style="color:#037691" %)**AT Command**(%%)**:**
--Example：**aa xx xx xx xx**         ~/~/ aa indicates whether the configuration has changed, 00 is yes, 01 is no; xx xx xx xx are the bytes sent.
++(% style="color:blue" %)**AT+RPL=5**   (%%)  ~/~/ After receiving a downlink payload from the server, the device will immediately uplink the payload back to the server using port number 100.
++Example：**aa xx xx xx xx**         ~/~/ **aa** indicates whether the configuration has changed: **00** means YES, and **01** means NO. **xx xx xx xx** are the bytes uplinked back.
++
  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173747-6.png?width=1124&height=165&rev=1.1||alt="image-20220823173747-6.png"]]
  For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
--(% 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.
++(% style="color:#037691" %)**Downlink Payload**(%%)**:**
++There is no downlink option available for this feature.
++
++
  ==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
++
  This command is used to query key information about the device, including its firmware version, frequency band, sub band, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device.
  * (((
@@ -1936,10 +1936,13 @@
  == 3.5 Integrating with ThingsEye.io ==
++
  The Things Stack application supports integration with ThingsEye.io. Once integrated, ThingsEye.io acts as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
++
  === 3.5.1 Configuring The Things Stack ===
++
  We use The Things Stack Sandbox in this example:
  * In **The Things Stack Sandbox**, go to the **Application **for the LT-22222-L you added.
@@ -1951,10 +1951,12 @@
  The username and  password (API key) you created here are required in the next section.
  {{/info}}
--[[image:tts-mqtt-integration.png||height="625" width="1000"]]
++[[image:tts-mqtt-integration.png]]
++
  === 3.5.2 Configuring ThingsEye.io ===
++
  The ThingsEye.io IoT platform is not open for self-registration at the moment. If you are interested in testing the platform, please send your project information to admin@thingseye.io, and we will create an account for you.
  * Login to your [[ThingsEye.io >>https://thingseye.io]]account.
@@ -1961,7 +1961,7 @@
  * Under the **Integrations center**, click **Integrations**.
  * Click the **Add integration** button (the button with the **+** symbol).
--[[image:thingseye-io-step-1.png||height="625" width="1000"]]
++[[image:thingseye-io-step-1.png]]
  On the **Add integration** window, configure the following:
@@ -1976,7 +1976,7 @@
  ** Allow create devices or assets
  * Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
--[[image:thingseye-io-step-2.png||height="625" width="1000"]]
++[[image:thingseye-io-step-2.png]]
  **Uplink data converter:**
@@ -1987,7 +1987,7 @@
  * Paste the uplink decoder function into the text area (first, delete the default code). The demo uplink decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Uplink_Converter.js]].
  * Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
--[[image:thingseye-io-step-3.png||height="625" width="1000"]]
++[[image:thingseye-io-step-3.png]]
  **Downlink data converter (this is an optional step):**
@@ -1998,7 +1998,7 @@
  * Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found [[here>>https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Downlink_Converter.js]].
  * Click the **Next** button. You will be navigated to the **Connection** tab.
--[[image:thingseye-io-step-4.png||height="625" width="1000"]]
++[[image:thingseye-io-step-4.png]]
  **Connection:**
@@ -2013,20 +2013,21 @@
  * Click the **Add** button.
--[[image:thingseye-io-step-5.png||height="625" width="1000"]]
++[[image:thingseye-io-step-5.png]]
  Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings and correct any errors.
--[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
++[[image:thingseye.io_integrationsCenter_integrations.png]]
  ==== 3.5.2.1 Viewing integration details ====
++
  Click on your integration from the list. The **Integration details** window will appear with the **Details **tab selected. The **Details **tab shows all the settings you have provided for this integration.
--[[image:integration-details.png||height="686" width="1000"]]
++[[image:integration-details.png]]
  If you want to edit the settings you have provided, click on the **Toggle edit mode** button. Once you have done click on the **Apply changes **button.
@@ -2035,28 +2035,32 @@
  See also [[ThingsEye documentation>>https://wiki.thingseye.io/xwiki/bin/view/Main/]].
  {{/info}}
--==== **3.5.2.2 Viewing events** ====
++==== 3.5.2.2 Viewing events ====
++
++
  The **Events **tab displays all the uplink messages from the LT-22222-L.
  * Select **Debug **from the **Event type** dropdown.
  * Select the** time frame** from the **time window**.
--[[image:thingseye-events.png||height="686" width="1000"]]
++[[image:thingseye-events.png]]
  * To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
--[[image:thingseye-json.png||width="1000"]]
++[[image:thingseye-json.png]]
--==== **3.5.2.3 Deleting an integration** ====
++==== 3.5.2.3 Deleting an integration ====
++
  If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
  ==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
++
  This will be added soon.
@@ -2065,7 +2065,7 @@
  === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
--Supports** NPN-type **sensors.
++Supports** NPN-type **sensors.
  [[image:1653356991268-289.png]]
@@ -2273,6 +2273,7 @@
  == 3.7 LED Indicators ==
++
  The table below lists the behavior of LED indicators for each port function.
  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
@@ -2303,12 +2303,16 @@
  |**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 Commands =
++
  The LT-22222-L supports programming using AT Commands.
++
  == 4.1 Connecting the LT-22222-L to a PC ==
++
  (((
  You can use a USB-to-TTL adapter/converter along with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below.
@@ -2328,7 +2328,10 @@
  (((
  You can find more details in the [[AT Command Manual>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
++
  == 4.2 LT-22222-L related AT commands ==
++
++
  )))
  (((
@@ -2525,16 +2525,19 @@
  == 5.1 Counting how many objects pass through the flow line ==
++
  See [[How to set up to setup counting for objects passing through the flow line>>How to set up to count objects pass in flow line]]?
  = 6. FAQ =
++
  This section contains some frequently asked questions, which can help you resolve common issues and find solutions quickly.
  == 6.1 How to update the firmware? ==
++
  Dragino frequently releases firmware updates for the LT-22222-L. Updating your LT-22222-L with the latest firmware version helps to:
  * Support new features
@@ -2587,6 +2587,8 @@
  (((
  (((
  == 6.2 How to change the LoRaWAN frequency band/region? ==
++
++
  )))
  )))
@@ -2598,6 +2598,8 @@
  == 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
++
++
  )))
  (((
@@ -2671,11 +2671,13 @@
  == 6.4 How to change the uplink interval? ==
++
  Please see this link: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/]]
  == 6.5 Can I see the counting event in the serial output? ==
++
  (((
  You can run the AT command **AT+DEBUG** to view the counting event in the serial output. If the firmware is too old and doesn’t support AT+DEBUG, update to the latest firmware first.
@@ -2682,6 +2682,7 @@
  == 6.6 Can I use point-to-point communication with LT-22222-L? ==
++
  Yes, you can. Please refer to the [[Point-to-Point Communication of LT-22222-L>>https://wiki.dragino.com/xwiki/bin/view/Main/%20Point%20to%20Point%20Communication%20of%20LT-22222-L/]] page. The firmware that supports point-to-point communication can be found [[here>>https://github.com/dragino/LT-22222-L/releases]].
@@ -2690,13 +2690,16 @@
  (((
  == 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.
++
  == 6.8 Can I setup LT-22222-L as a NC (Normally Closed) relay? ==
++
  The LT-22222-L's built-in relay is Normally Open (NO). You can use an external relay to achieve a Normally Closed (NC) configuration. The circuit diagram is shown below:
@@ -2705,16 +2705,19 @@
  == 6.9 Can the LT-22222-L save the RO state? ==
++
  To enable this feature, the firmware version must be 1.6.0 or higher.
  == 6.10 Why does the LT-22222-L always report 15.585V when measuring the AVI? ==
++
  It is likely that the GND is not connected during the measurement, or that the wire connected to the GND is loose.
  = 7. Troubleshooting =
++
  This section provides some known troubleshooting tips.
@@ -2723,6 +2723,8 @@
  (((
  (((
  == 7.1 Downlink isn't working. How can I solve this? ==
++
++
  )))
  )))
@@ -2734,6 +2734,8 @@
  == 7.2 Having trouble uploading an image? ==
++
++
  )))
  (((
@@ -2744,6 +2744,8 @@
  == 7.3 Why can't I join TTN in the US915 /AU915 bands? ==
++
++
  )))
  (((
@@ -2753,6 +2753,7 @@
  == 7.4 Why can the LT-22222-L perform uplink normally, but cannot receive downlink? ==
++
  The FCD count of the gateway is inconsistent with the FCD count of the node, causing the downlink to remain in the queue.
  Use this command to synchronize their counts: [[Resets the downlink packet count>>||anchor="H3.4.2.23Resetsthedownlinkpacketcount"]]
@@ -2759,6 +2759,7 @@
  = 8. Ordering information =
++
  (% style="color:#4f81bd" %)**LT-22222-L-XXX:**
  (% style="color:#4f81bd" %)**XXX:**
@@ -2773,8 +2773,11 @@
  * (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865
  * (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779
++
++
  = 9. Package information =
++
  **Package includes**:
  * 1 x LT-22222-L I/O Controller
@@ -2789,8 +2789,11 @@
  * Package Size / pcs : 14.5 x 8 x 5 cm
  * Weight / pcs : 170 g
++
++
  = 10. Support =
++
  * (((
  Support is available Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different time zones, we cannot offer live support. However, your questions will be answered as soon as possible within the aforementioned schedule.
  )))
@@ -2802,6 +2802,7 @@
  = 11. Reference =
++
  * LT-22222-L: [[http:~~/~~/www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html>>url:http://www.dragino.com/products/lora-lorawan-end-node/item/156-lt-22222-l.html]]
  * [[Datasheet, Document Base>>https://www.dropbox.com/sh/gxxmgks42tqfr3a/AACEdsj_mqzeoTOXARRlwYZ2a?dl=0]]
  * [[Hardware Source>>url:https://github.com/dragino/Lora/tree/master/LT/LT-33222-L/v1.0]]

lt-22222-l-joining.png

Size

@@ -1,1 +1,1 @@
--274.1 KB
++301.9 KB

Content

Screenshot 2024-12-08 193946.png

Author

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

Size

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

Content

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

Author

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

Size

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

Content

lt33222-l.jpg

Author

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

Size

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

Content