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

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

From 231.1 to 230.16 From 235.1 to 234.1

From version 234.1

edited by Dilisi S
on 2024/12/17 04:57

Change comment: Dec 16 edits - minor edits

To version 231.1

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Author

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

Content

@@ -179,6 +179,7 @@
  |(% style="width:125px" %)DO2|(% style="width:128px" %)Digital Output 2
  |(% style="width:125px" %)DO1|(% style="width:128px" %)Digital Output 1
++
  == 2.3 Connecting LT-22222-L to a Power Source ==
@@ -198,7 +198,7 @@
  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.1 Prerequisites ==
++=== 3.2.1 Prerequisites ===
  The LT-22222-L comes with device registration information such as DevEUI, AppEUI, and AppKey that allows you to register it with a LoRaWAN network. These registration information can be found on a sticker that can be found inside the package. Please keep the **registration information** sticker in a safe place for future reference.
@@ -206,13 +206,13 @@
  [[image:image-20230425173427-2.png||height="246" width="530"]]
  {{info}}
--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.
++In case you can't set the root key and other identifiers in the network server and must use them from the server, you can use [[AT Commands>>||anchor="H4.UseATCommand"]] to configure them on the device.
  {{/info}}
  The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
--== 3.2 The Things Stack ==
++=== 3.2.2 The Things Stack ===
  This section guides you through how to register your LT-22222-L with The Things Stack Sandbox.
@@ -232,7 +232,7 @@
  {{/info}}
--=== 3.2.1 Setting up ===
++==== 3.2.2.1 Setting up ====
  * Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet.
@@ -241,9 +241,10 @@
  * 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.1.1 Using the LoRaWAN Device Repository ====
++==== 3.2.2.2 Using the LoRaWAN Device Repository ====
++
  * On the **Register end device** page:
  ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
  ** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists.
@@ -267,7 +267,7 @@
  [[image:lt-22222-l-dev-repo-reg-p2.png]]
--==== 3.2.1.2 Adding device manually ====
++==== 3.2.2.3 Adding device manually ====
  * On the **Register end device** page:
@@ -299,7 +299,7 @@
  [[image:lt-22222-device-overview.png]]
--=== 3.2.2 Joining ===
++==== 3.2.2.4 Joining ====
  On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
@@ -310,7 +310,7 @@
  [[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 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.
@@ -335,7 +335,7 @@
  [[image:lt-22222-l-js-custom-payload-formatter.png]]
--=== 3.2.4 Downlinks ===
++==== 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**.
@@ -904,6 +904,7 @@
  * (% style="color:blue" %)**Sensor-related commands**(%%):
++
  === 3.4.1 Common commands ===
@@ -1418,82 +1418,80 @@
  ==== 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**
++* (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
++(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control
--(% 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.
++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" %)**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.
--**DO1_control_method_and_port_status **- 1 byte in hex
++(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
--0x01 :  DO1 set to low
++(% 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
--0x00 :  DO1 set to high
++(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:
--0x11 :  DO1 NO action
++(% 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
++(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:
--**DO2_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|DO3 set to low
++|0x00|DO3 set to high
++|0x11|DO3 NO Action
--0x01 :  DO2 set to low
++(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms)
--0x00 :  DO2 set to high
--0x11 :  DO2 NO action
--
--
--**DO3_control_method_and_port_status **- 1 byte in hex
--
--0x01 :  DO3 set to low
--
--0x00 :  DO3 set to high
--
--0x11 :  DO3 NO action
--
--
--**latching_time** : 4 bytes in hex
--
  (% style="color:red" %)**Note: **
--   Since firmware v1.6.0, the latch time support 4 bytes or 2 bytes
++   Since firmware v1.6.0, the latch time support 4 bytes and 2 bytes
     Before firmware v1.6.0, the latch time only supported 2 bytes.
  (% 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.
++**Example payload:**
--**A9 01 00 01 11 07 D0**
++**~1. A9 01 01 01 01 07 D0**
--DO1 pin is set to high, DO2 pin is set to low, and DO3 pin takes no action. This lasts for 2 seconds and then reverts to the original state.
++DO1 pin, 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 00 00 00 00 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**
++
  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**
--**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.
--)))
++
  ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
@@ -2114,7 +2114,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]]
@@ -2125,16 +2125,12 @@
  If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
--==== 3.5.2.4 Viewing sensor data on a dashboard ====
++==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
--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.
++This will be added soon.
--
--[[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) ===

lt-22222-l-dashboard.png

Author

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

Size

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

Content

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

Summary

Details

Applications

Navigation