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

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

From 230.14 to 230.15 From 237.1 to 238.1

From version 230.15

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

Change comment: There is no comment for this version

To version 237.1

edited by Dilisi S
on 2024/12/23 05:13

Change comment: Dec 22 - fix typos

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 1 added, 0 removed)
- lt-22222-l-dashboard.png

Details

Page properties

Author

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

Content

@@ -98,7 +98,6 @@
  * Automatic RF Sense and CAD with ultra-fast AFC.
  * Packet engine up to 256 bytes with CRC.
--
  == 1.3 Features ==
@@ -110,7 +110,6 @@
  * Firmware upgradable via program port
  * Counting
--
  == 1.4 Applications ==
@@ -121,13 +121,12 @@
  * Smart cities
  * Smart factory
--
  == 1.5 Hardware Variants ==
  (% border="1" cellspacing="3" style="width:510px" %)
  |(% style="background-color:#4f81bd; color:white; width:94px" %)**Model**|(% style="background-color:#4f81bd; color:white; width:172px" %)**Photo**|(% style="background-color:#4f81bd; color:white; width:244px" %)**Description**
--|(% style="width:94px" %)**LT-22222-L**|(% style="width:172px" %)(((
++|(% style="width:94px" %)**LT-33222-L**|(% style="width:172px" %)(((
  (% style="text-align:center" %)
  [[image:lt33222-l.jpg||height="110" width="95"]]
  )))|(% style="width:256px" %)(((
@@ -139,7 +139,6 @@
  * 1 x Counting Port
  )))
--
  = 2. Assembling the device =
  == 2.1 Connecting the antenna ==
@@ -155,11 +155,11 @@
  == 2.2 Terminals ==
--The  LT-22222-L has two screw terminal blocks. The upper screw treminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals.
++The  LT-22222-L has two screw terminal blocks. The upper screw terminal block has 6 screw terminals and the lower screw terminal block has 10 screw terminals.
  **Upper screw terminal block (from left to right):**
--(% border="1" cellspacing="3" style="width:381px;background-color:#f2f2f2" %)
++(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:381px" %)
  |=(% style="width: 139px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 242px;background-color:#4f81bd;color:white" %)Function
  |(% style="width:139px" %)GND|(% style="width:242px" %)Ground
  |(% style="width:139px" %)VIN|(% style="width:242px" %)Input Voltage
@@ -170,7 +170,7 @@
  **Lower screw terminal block (from left to right):**
--(% border="1" cellspacing="3" style="width:253px;background-color:#f2f2f2" %)
++(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:253px" %)
  |=(% style="width: 125px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 128px;background-color:#4f81bd;color:white" %)Function
  |(% style="width:125px" %)RO1-2|(% style="width:128px" %)Relay Output 1
  |(% style="width:125px" %)RO1-1|(% style="width:128px" %)Relay Output 1
@@ -185,6 +185,7 @@
  == 2.3 Connecting LT-22222-L to a Power Source ==
++
  The LT-22222-L I/O Controller can be powered by a **7–24V DC** power source. Connect your power supply’s **positive wire** to the **VIN** and the **negative wire** to the **GND** screw terminals. The power indicator **(PWR) LED** will turn on when the device is properly powered.
  {{warning}}
@@ -197,23 +197,27 @@
  = 3. Registering LT-22222-L with a LoRaWAN Network Server =
++
  The LT-22222-L supports both OTAA (Over-the-Air Activation) and ABP (Activation By Personalization) methods to activate with a LoRaWAN Network Server. However, OTAA is the most secure method for activating a device with a LoRaWAN Network Server. OTAA regenerates session keys upon initial registration and regenerates new session keys after any subsequent reboots. By default, the LT-22222-L is configured to operate in LoRaWAN Class C mode.
--=== 3.2.1 Prerequisites ===
++== 3.1 Prerequisites ==
--The LT-22222-L comes with device registration information such as DevEUI, AppEUI, and AppKey that allows you to register it with a LoRaWAN network. These registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference.
++The LT-22222-L comes with device registration information such as DevEUI, AppEUI, and AppKey which allows you to register it with a LoRaWAN network. This registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference.
++
  [[image:image-20230425173427-2.png||height="246" width="530"]]
  {{info}}
--In case you can't set the root key and other identifiers in the network server and must use them from the server, you can use [[AT Commands>>||anchor="H4.UseATCommand"]] to configure them on the device.
++If you are unable to set the provided root key and other identifiers in the network server, you must generate new keys and identifiers with the network server and configure the device with them using AT commands.
  {{/info}}
  The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
--=== 3.2.2 The Things Stack ===
++== 3.2 The Things Stack ==
++
++
  This section guides you through how to register your LT-22222-L with The Things Stack Sandbox.
  {{info}}
@@ -224,7 +224,7 @@
  The network diagram below illustrates the connection between the LT-22222-L and The Things Stack, as well as how the data can be integrated with the ThingsEye IoT platform.
--[[image:dragino-lorawan-nw-lt-22222-n.jpg]]
++[[image:dragino-lorawan-nw-lt-22222-n.jpg||height="374" width="1400"]]
  {{info}}
   You can use a LoRaWAN gateway, such as the [[Dragino LPS8N>>https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]], to expand or create LoRaWAN coverage in your area.
@@ -231,8 +231,9 @@
  {{/info}}
--==== 3.2.2.1 Setting up ====
++=== 3.2.1 Setting up ===
++
  * Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet.
  * Log in to your The Things Stack Sandbox account.
  * Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs).
@@ -239,8 +239,9 @@
  * Go to your application's page and click on the **End devices** in the left menu.
  * On the End devices page, click on **+ Register end device**. Two registration options are available:
--==== 3.2.2.2 Using the LoRaWAN Device Repository ====
++==== 3.2.1.1 Using the LoRaWAN Device Repository ====
++
  * On the **Register end device** page:
  ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
  ** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists.
@@ -264,8 +264,9 @@
  [[image:lt-22222-l-dev-repo-reg-p2.png]]
--==== 3.2.2.3 Adding device manually ====
++==== 3.2.1.2 Adding device manually ====
++
  * On the **Register end device** page:
  ** Select the option **Enter end device specifies manually** under **Input method**.
  ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
@@ -295,10 +295,11 @@
  [[image:lt-22222-device-overview.png]]
--==== 3.2.2.4 Joining ====
++=== 3.2.2 Joining ===
--On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
++On the end device's page (in this case, lt-22222-l), click on **Live data** tab. The Live data panel for your device will display. Initially, it is blank.
++
  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.
@@ -305,18 +305,17 @@
  [[image:lt-22222-l-joining.png]]
++=== 3.2.3 Uplinks ===
--==== 3.2.2.5 Uplinks ====
++After successfully joining, the device will send its first **uplink data message** to The Things Stack application it belongs to (in this example, it is **dragino-docs**). When the LT-22222-L sends an uplink message to the server, the **TX LED** turns on for **1 second**. By default, you will receive an uplink data message from the device every 10 minutes.
--After successfully joining, the device will send its first **uplink data message** to the application it belongs to (in this example, **dragino-docs**). When the LT-22222-L sends an uplink message to the server, the **TX LED** turns on for **1 second**. By default, you will receive an uplink data message from the device every 10 minutes.
++Click on one of the **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the **decode_payload {}** JSON object.
--Click on one of a **Forward uplink data messages **to see its payload content. The payload content is encapsulated within the decode_payload {} JSON object.
--
  [[image:lt-22222-ul-payload-decoded.png]]
--If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **Applications > your application > End devices** > **your  end device** > **Payload formatters** > **Uplink**. Then  select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
++If you can't see the decoded payload, it is because you haven't added the uplink formatter code. To add the uplink formatter code, select **Applications > [your application] > End devices** > [**your  end device]** > **Payload formatters** > **Uplink**. Then select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
  {{info}}
  The Things Stack provides two levels of payload formatters: application level and device level. The device-level payload formatters **override **the application-level payload formatters.
@@ -325,17 +325,18 @@
  [[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]]:
++We have written a payload formatter that resolves some decoding issues present in The Things Stack Device Repository payload 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 ====
++=== 3.2.4 Downlinks ===
--When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
++When the LT-22222-L receives a downlink message from the LoRaWAN Network Server, the **RX LED** turns on for **1 second**.
++
  == 3.3 Working Modes and Uplink Payload formats ==
@@ -355,8 +355,10 @@
  The uplink messages are sent over LoRaWAN FPort=2. By default, an uplink message is sent every 10 minutes.
++
  === 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
++
  (((
  This is the default mode.
@@ -429,6 +429,7 @@
  MOD = 1
++
  === 3.3.2 AT+MOD~=2, (Double DI Counting) ===
@@ -507,6 +507,7 @@
  === 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI ===
++
  (% style="color:red" %)**Note: The maximum count depends on the bytes it is.
  The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
  It starts counting again when it reaches the maximum value.**
@@ -560,6 +560,7 @@
  === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting ===
++
  (% style="color:red" %)**Note:The maximum count depends on the bytes it is.
  The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
  It starts counting again when it reaches the maximum value.**
@@ -629,6 +629,7 @@
  === 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.**
@@ -715,7 +715,7 @@
  AT+AVLIM=3000,6000,0,2000 (triggers an uplink if AVI1 voltage is lower than 3V or higher than 6V, or if AV2 voltage is higher than 2V)
--AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage lower than 5V. Use 0 for parameters that are not in use)
++AT+AVLIM=5000,0,0,0 (triggers an uplink if AVI1 voltage is lower than 5V. Use 0 for parameters that are not in use)
  (% style="color:#4f81bd" %)**Trigger based on current**:
@@ -771,7 +771,7 @@
  (% style="color:#4f81bd" %)**Trigger Settings Payload Explanation:**
--MOD6 Payload: total of 11 bytes
++MOD6 Payload: a total of 11 bytes
  (% 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**
@@ -785,7 +785,7 @@
  MOD(6)
  )))
--(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Totally 1 byte as below
++(% style="color:#4f81bd" %)**TRI FLAG1**(%%) is a combination to show if the trigger is set for this part. Total 1 byte as below.
  (% 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**
@@ -814,7 +814,7 @@
  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
++(% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is triggered. Total 1 byte as below.
  (% 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**
@@ -843,7 +843,7 @@
  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
++(% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is triggered. Total 1 byte as below.
  (% 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**
@@ -853,7 +853,7 @@
  **Example:**
--00000111: This means both DI1 and DI2 triggers are enabled, and this packet is trigger by DI1.
++00000111: This means both DI1 and DI2 triggers are enabled, and this packet is triggered by DI1.
  00000101: This means both DI1 and DI2 triggers are enabled.
@@ -864,7 +864,7 @@
  **AB 06**
--When device receives this command, it will send the MOD6 payload.
++When the device receives this command, it will send the MOD6 payload.
  === 3.3.7 Payload Decoder ===
@@ -885,7 +885,7 @@
  (((
  (((
--There are two tytes of commands:
++There are two types of commands:
  )))
  )))
@@ -897,7 +897,7 @@
  (((
--These are available for each sensors and include actions such as changing the uplink interval or resetting the device. For firmware v1.5.4, you can find the supported common commands under: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]s.
++These are available for each sensor 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.
  )))
@@ -1088,7 +1088,7 @@
  |(% style="width:95px" %)**Example**|(% style="width:403px" %)(((
  AB 06
--Uplinks the trigger settings.
++Uplink the trigger settings.
  )))
  ==== 3.4.2.6 Enable/Disable DI1/DI2/DI3 as a trigger ====
@@ -1317,7 +1317,7 @@
  )))
  |(% style="width:104px" %)**Note**|(% style="width:394px" %)See also, [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
--==== 3.4.2.11 Trigger – Set minimum interval ====
++==== 3.4.2.11 Trigger – Set the 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.
@@ -1407,126 +1407,140 @@
  ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
--* (% style="color:#037691" %)**AT Command**
++(% style="color:#037691" %)**AT command**
  There is no AT command to control the digital output.
--* (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
++(% style="color:#037691" %)**Downlink payload**
--(% 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:
++(% border="2" style="width:500px" %)
++|(% style="width:116px" %)**Prefix**|(% style="width:382px" %)0xA9
++|(% style="width:116px" %)**Parameters**|(% style="width:382px" %)(((
++**inverter_mode**: 1 byte in hex.
--(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)
--
--(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode
--
  **01:** DO pins revert to their original state after the timeout.
  **00:** DO pins switch to an inverted state after the timeout.
--(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
++**DO1_control_method_and_port_status **- 1 byte in hex
--(% 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**
--|0x01|DO1 set to low
--|0x00|DO1 set to high
--|0x11|DO1 NO Action
++0x01 :  DO1 set to low
--(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:
++0x00 :  DO1 set to high
--(% 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**
--|0x01|DO2 set to low
--|0x00|DO2 set to high
--|0x11|DO2 NO Action
++0x11 :  DO1 NO action
--(% 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**
--|0x01|DO3 set to low
--|0x00|DO3 set to high
--|0x11|DO3 NO Action
++**DO2_control_method_and_port_status** - 1 byte in hex
--(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms)
++0x01 :  DO2 set to low
++0x00 :  DO2 set to high
--(% style="color:red" %)**Note: **
++0x11 :  DO2 NO action
--   Since firmware v1.6.0, the latch time support 4 bytes and 2 bytes
--   Before firmware v1.6.0, the latch time only supported 2 bytes.
++**DO3_control_method_and_port_status **- 1 byte in hex
--(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
++0x01 :  DO3 set to low
++0x00 :  DO3 set to high
--**Example payload:**
++0x11 :  DO3 NO action
--**~1. A9 01 01 01 01 07 D0**
++**latching_time** : 4 bytes in hex
++
++(% style="color:red" %)**Note: **
++
++   Since firmware v1.6.0, the latch time supports 4 bytes or 2 bytes
++
++   Before firmware v1.6.0, the latch time only supported 2 bytes.
++
++(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
++)))
++|(% style="width:116px" %)**Payload format**|(% style="width:382px" %)<prefix><inverter_mode><DO1_control_method_and_port_status><DO2_control_method_and_port_status><DO2_control_method_and_port_status><latching_time>
++|(% style="width:116px" %)**Example**|(% style="width:382px" %)(((
++**A9 01 01 01 01 07 D0**
++
  DO1 pin, DO2 pin, and DO3 pin will be set to low, last for 2 seconds, and then revert to their original state.
--**2. A9 01 00 01 11 07 D0**
++**A9 01 00 01 11 07 D0**
++
  DO1 pin is set to high, DO2 pin is set to low, and DO3 pin takes no action. This lasts for 2 seconds and then reverts to the original state.
--**3. A9 00 00 00 00 07 D0**
++**A9 00 00 00 00 07 D0**
++
  DO1 pin, DO2 pin, and DO3 pin will be set to high, last for 2 seconds, and then all change to low.
--**4. A9 00 11 01 00 07 D0**
--DO1 pin takes no action, DO2 pin is set to low, and DO3 pin is set to high. This lasts for 2 seconds, after which DO1 pin takes no action, DO2 pin is set to high, and DO3 pin is set to low.
++**A9 00 11 01 00 07 D0**
++DO1 pin takes no action, DO2 pin is set to low, and DO3 pin is set to high. This lasts for 2 seconds, after which the DO1 pin takes no action, the DO2 pin is set to high, and the DO3 pin is set to low.
++)))
  ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
--* (% style="color:#037691" %)**AT Command:**
++(% style="color:#037691" %)**AT Command:**
--There is no AT Command to control the Relay Output
++There is no AT Command to control the Relay Output.
--* (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
++(% style="color:#037691" %)**Downlink Payload**
--(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Sets RO1/RO2 output
++(% border="2" style="width:500px" %)
++|(% style="width:113px" %)**Prefix**|(% style="width:384px" %)0x03
++|(% style="width:113px" %)**Parameters**|(% style="width:384px" %)(((
++**RO1_status** : 1 byte in hex
++00: Close
--(((
--If the payload is 0x030100, it means setting RO1 to close and RO2 to open.
--)))
++01: Open
--(((
--00: Close ,  01: Open , 11: No action
++11: No action
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %)
--|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**RO1**|(% style="background-color:#4f81bd; color:white" %)**RO2**
--|03  00  11|Open|No Action
--|03  01  11|Close|No Action
--|03  11  00|No Action|Open
--|03  11  01|No Action|Close
--|03  00  00|Open|Open
--|03  01  01|Close|Close
--|03  01  00|Close|Open
--|03  00  01|Open|Close
--)))
--(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
++**RO2_status** : 1 byte in hex
++00: Close
++01: Open
++
++11: No action
++)))
++|(% style="width:113px" %)**Payload format**|(% style="width:384px" %)<prefix><RO1_status><RO2_status>
++|(% style="width:113px" %)**Example**|(% style="width:384px" %)(((
++(% border="2" %)
++|=Payload|=RO1|=RO2
++|03  00  11|Open|No action
++|03  01  11|Close|No action
++|03  11  00|No action|Open
++|03  11  10|No action|Close
++|03  00  00|Open|Open
++|03  01  01|Close|Close
++|03  01  00|Close|Open
++|03  00  01|Open|Close
++
++(% style="color:red" %)**The device will transmit an uplink packet if the downlink payload is executed successfully.**
++)))
++
  ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
  Controls the relay output time.
--* (% style="color:#037691" %)**AT Command:**
++(% style="color:#037691" %)**AT Command:**
++
  There is no AT Command to control the Relay Output
--* (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
++(% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
  (% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
@@ -1537,9 +1537,9 @@
  (% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode
--01: Relays will change back to their original state after timeout.
++01: Relays will change back to their original state after a timeout.
--00: Relays will change to the inverter state after timeout.
++00: Relays will change to the inverter state after a timeout.
  (% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status:
@@ -1568,7 +1568,7 @@
  **2. 05 01 10 07 D0**
--Relay1 will change to NC, Relay2 will change to NO, lasting 2 seconds, then both will revert to their original state.
++Relay1 will change to NC, Relay2 will change to NO, lasting 2 seconds, and then both will revert to their original state.
  **3. 05 00 01 07 D0**
@@ -1599,7 +1599,7 @@
  **1**: higher than
--if you leave logic parameter blank, it is considered 0
++if you leave the logic parameter blank, it is considered 0
  )))
  |(% style="width:137px" %)**Examples**|(% style="width:361px" %)(((
  AT+VOLMAX=20000
@@ -1630,7 +1630,7 @@
  **1**: higher than
--if you leave logic parameter blank, it is considered 1 (higher than)
++if you leave the logic parameter blank, it is considered 1 (higher than)
  )))
  |(% style="width:140px" %)**Example**|(% style="width:358px" %)(((
  A5 **4E 20**
@@ -1894,7 +1894,7 @@
  ==== 3.4.2.24 When the limit bytes are exceeded, upload in batches ====
--This command controls the behavior of the node when the combined size of the MAC commands (MACANS) from the server and the payload exceeds the allowed byte limit for the current data rate (DR). The command provides two modes: one enables splitting the data into batches to ensure compliance with the byte limit, while the other prioritizes the payload and ignores the MACANS in cases of overflow.
++This command controls the behavior of the node when the combined size of the MAC commands (MACANS) from the server and the payload exceed the allowed byte limit for the current data rate (DR). The command provides two modes: one enables splitting the data into batches to ensure compliance with the byte limit, while the other prioritizes the payload and ignores the MACANS in cases of overflow.
  (% style="color:#037691" %)**AT Command**
@@ -1963,15 +1963,15 @@
  There is no downlink option available for this feature.
--==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ====
++==== 3.4.2.26 Query firmware version, frequency band, subband, 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.
++This command is used to query key information about the device, including its firmware version, frequency band, subband, and TDC time. By sending the specified payload as a downlink, the server can retrieve this essential data from the device.
  * (((
  (% style="color:#037691" %)**Downlink Payload**(%%)**:**
--(% style="color:blue" %)**26 01  ** (%%)  ~/~/  The downlink payload 26 01 is used to query the device's firmware version, frequency band, sub band, and TDC time.
++(% style="color:blue" %)**26 01  ** (%%)  ~/~/  The downlink payload 26 01 is used to query the device's firmware version, frequency band, subband, and TDC time.
@@ -2026,7 +2026,7 @@
  * Ensure the following options are turned on.
  ** Enable integration
  ** Debug mode
--** Allow create devices or assets
++** Allow creating devices or assets
  * Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
  [[image:thingseye-io-step-2.png]]
@@ -2101,7 +2101,7 @@
  [[image:thingseye-events.png]]
--* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
++* To view the **JSON payload** of a message, click on the **three dots (...)** in the **Message** column of the desired message.
  [[image:thingseye-json.png]]
@@ -2112,12 +2112,16 @@
  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 ====
++==== 3.5.2.4 Viewing sensor data on a dashboard ====
--This will be added soon.
++You can create a dashboard with ThingsEye to visualize the sensor data coming from the LHT65N-VIB. The following image shows a dashboard created for the LT-22222-L. See **Creating a dashboard** in ThingsEye documentation for more information.
++
++[[image:lt-22222-l-dashboard.png]]
++
++
  == 3.6 Interface Details ==
  === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
@@ -2332,7 +2332,7 @@
  == 3.7 LED Indicators ==
--The table below lists the behavior of LED indicators for each port function.
++The table below lists the behaviour 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**
@@ -2339,11 +2339,11 @@
  |**PWR**|Always on when there is power
  |**TX**|(((
  (((
--Device boot: TX blinks 5 times.
++Device booting: TX blinks 5 times.
  )))
  (((
--Successful network join: TX remains ON for 5 seconds.
++Successful network joins: TX remains ON for 5 seconds.
  )))
  (((
@@ -2427,13 +2427,13 @@
  * ##**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+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+RECVB**##: Print the last received data in binary format (with hexadecimal values)
++* ##**AT+RECV**##: Print the last received data in raw format
++* ##**AT+VER**##: Get the 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
@@ -2461,7 +2461,7 @@
  )))
  (((
--(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**##
++(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT command access**##
  )))
  (((
@@ -2469,7 +2469,7 @@
  )))
  (((
--(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT commands access**##
++(% style="background-color:#dcdcdc" %)##**123456 ~/~/Enter the password to enable AT command access**##
  )))
  (((
@@ -2500,7 +2500,7 @@
  (((
--(% style="background-color:#dcdcdc" %)**123456**(%%)        ~/~/ Enter password to enable AT commands access
++(% style="background-color:#dcdcdc" %)**123456**(%%)        ~/~/ Enter the password to enable AT commands access
  )))
  )))
@@ -2509,7 +2509,7 @@
  )))
  (((
--(% style="background-color:#dcdcdc" %)** 123456**(%%)       ~/~/ Enter password to enable AT commands access
++(% style="background-color:#dcdcdc" %)** 123456**(%%)       ~/~/ Enter the password to enable AT command access
  )))
  (((
@@ -2591,7 +2591,7 @@
  == 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]]?
++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 =
@@ -2661,13 +2661,13 @@
  )))
  (((
--You can follow the introductions on [[how to upgrade image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloading, select the required image file.
++You can follow the introductions on [[how to upgrade the image>>||anchor="H5.1Howtoupgradetheimage3F"]]. When downloading, select the required image file.
  )))
  (((
--== 6.3 How to setup LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
++== 6.3 How to set up LT-22222-L to work with a Single Channel Gateway, such as LG01/LG02? ==
  )))
@@ -2769,9 +2769,9 @@
  * 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.
++* 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? ==
++== 6.8 Can I set up LT-22222-L as an 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:
@@ -2861,7 +2861,6 @@
  * (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865
  * (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779
--
  = 9. Package information =
@@ -2879,7 +2879,6 @@
  * Package Size / pcs : 14.5 x 8 x 5 cm
  * Weight / pcs : 170 g
--
  = 10. Support =

lt-22222-l-dashboard.png

Author

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

Size

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

Content