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

From version 230.16
edited by Xiaoling
on 2024/12/09 10:58
Change comment: There is no comment for this version
To version 233.1
edited by Dilisi S
on 2024/12/17 04:56
Change comment: Uploaded new attachment "lt-22222-l-dashboard.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.pradeeka
Content
... ... @@ -179,7 +179,6 @@
179 179  |(% style="width:125px" %)DO2|(% style="width:128px" %)Digital Output 2
180 180  |(% style="width:125px" %)DO1|(% style="width:128px" %)Digital Output 1
181 181  
182 -
183 183  == 2.3 Connecting LT-22222-L to a Power Source ==
184 184  
185 185  
... ... @@ -199,7 +199,7 @@
199 199  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.
200 200  
201 201  
202 -=== 3.2.1 Prerequisites ===
201 +== 3.1 Prerequisites ==
203 203  
204 204  
205 205  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.
... ... @@ -207,13 +207,13 @@
207 207  [[image:image-20230425173427-2.png||height="246" width="530"]]
208 208  
209 209  {{info}}
210 -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.
209 +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.
211 211  {{/info}}
212 212  
213 213  The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
214 214  
215 215  
216 -=== 3.2.2 The Things Stack ===
215 +== 3.2 The Things Stack ==
217 217  
218 218  
219 219  This section guides you through how to register your LT-22222-L with The Things Stack Sandbox.
... ... @@ -233,7 +233,7 @@
233 233  {{/info}}
234 234  
235 235  
236 -==== 3.2.2.1 Setting up ====
235 +=== 3.2.1 Setting up ===
237 237  
238 238  
239 239  * Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet.
... ... @@ -243,7 +243,7 @@
243 243  * On the End devices page, click on **+ Register end device**. Two registration options are available:
244 244  
245 245  
246 -==== 3.2.2.2 Using the LoRaWAN Device Repository ====
245 +==== 3.2.1.1 Using the LoRaWAN Device Repository ====
247 247  
248 248  
249 249  * On the **Register end device** page:
... ... @@ -269,7 +269,7 @@
269 269  [[image:lt-22222-l-dev-repo-reg-p2.png]]
270 270  
271 271  
272 -==== 3.2.2.3 Adding device manually ====
271 +==== 3.2.1.2 Adding device manually ====
273 273  
274 274  
275 275  * On the **Register end device** page:
... ... @@ -301,7 +301,7 @@
301 301  [[image:lt-22222-device-overview.png]]
302 302  
303 303  
304 -==== 3.2.2.4 Joining ====
303 +=== 3.2.2 Joining ===
305 305  
306 306  
307 307  On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
... ... @@ -312,7 +312,7 @@
312 312  [[image:lt-22222-l-joining.png]]
313 313  
314 314  
315 -==== 3.2.2.5 Uplinks ====
314 +=== 3.2.3 Uplinks ===
316 316  
317 317  
318 318  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.
... ... @@ -337,7 +337,7 @@
337 337  [[image:lt-22222-l-js-custom-payload-formatter.png]]
338 338  
339 339  
340 -==== 3.2.2.6 Downlinks ====
339 +=== 3.2.4 Downlinks ===
341 341  
342 342  
343 343  When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
... ... @@ -906,7 +906,6 @@
906 906  
907 907  * (% style="color:blue" %)**Sensor-related commands**(%%):
908 908  
909 -
910 910  === 3.4.1 Common commands ===
911 911  
912 912  
... ... @@ -1421,78 +1421,81 @@
1421 1421  ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
1422 1422  
1423 1423  
1424 -* (% style="color:#037691" %)**AT Command**
1422 +(% style="color:#037691" %)**AT command**
1425 1425  
1426 1426  There is no AT command to control the digital output.
1427 1427  
1428 1428  
1429 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
1427 +(% style="color:#037691" %)**Downlink payload**
1430 1430  
1431 -(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control
1432 1432  
1433 -This is to control the digital output time of DO pin. Include four bytes:
1430 +(% border="2" style="width:500px" %)
1431 +|(% style="width:116px" %)**Prefix**|(% style="width:382px" %)0xA9
1432 +|(% style="width:116px" %)**Parameters**|(% style="width:382px" %)(((
1433 +**inverter_mode**: 1 byte in hex.
1434 1434  
1435 -(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)
1436 -
1437 -(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode
1438 -
1439 1439  **01:** DO pins revert to their original state after the timeout.
1440 1440  **00:** DO pins switch to an inverted state after the timeout.
1441 1441  
1442 1442  
1443 -(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
1439 +**DO1_control_method_and_port_status **- 1 byte in hex
1444 1444  
1445 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1446 -|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
1447 -|0x01|DO1 set to low
1448 -|0x00|DO1 set to high
1449 -|0x11|DO1 NO Action
1441 +0x01 : DO1 set to low
1450 1450  
1451 -(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:
1443 +0x00 : DO1 set to high
1452 1452  
1453 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1454 -|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
1455 -|0x01|DO2 set to low
1456 -|0x00|DO2 set to high
1457 -|0x11|DO2 NO Action
1445 +0x11 : DO1 NO action
1458 1458  
1459 -(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:
1460 1460  
1461 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1462 -|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
1463 -|0x01|DO3 set to low
1464 -|0x00|DO3 set to high
1465 -|0x11|DO3 NO Action
1448 +**DO2_control_method_and_port_status** - 1 byte in hex
1466 1466  
1467 -(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms)
1450 +0x01 : DO2 set to low
1468 1468  
1452 +0x00 : DO2 set to high
1469 1469  
1470 -(% style="color:red" %)**Note: **
1454 +0x11 : DO2 NO action
1471 1471  
1472 - Since firmware v1.6.0, the latch time support 4 bytes and 2 bytes
1473 1473  
1474 - Before firmware v1.6.0, the latch time only supported 2 bytes.
1457 +**DO3_control_method_and_port_status **- 1 byte in hex
1475 1475  
1476 -(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1459 +0x01 : DO3 set to low
1477 1477  
1461 +0x00 : DO3 set to high
1478 1478  
1479 -**Example payload:**
1463 +0x11 : DO3 NO action
1480 1480  
1481 -**~1. A9 01 01 01 01 07 D0**
1482 1482  
1466 +**latching_time** : 4 bytes in hex
1467 +
1468 +(% style="color:red" %)**Note: **
1469 +
1470 + Since firmware v1.6.0, the latch time support 4 bytes or 2 bytes
1471 +
1472 + Before firmware v1.6.0, the latch time only supported 2 bytes.
1473 +
1474 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1475 +)))
1476 +|(% 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>
1477 +|(% style="width:116px" %)**Example**|(% style="width:382px" %)(((
1478 +**A9 01 01 01 01 07 D0**
1479 +
1483 1483  DO1 pin, DO2 pin, and DO3 pin will be set to low, last for 2 seconds, and then revert to their original state.
1484 1484  
1485 -**2. A9 01 00 01 11 07 D0**
1486 1486  
1483 +**A9 01 00 01 11 07 D0**
1484 +
1487 1487  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.
1488 1488  
1489 -**3. A9 00 00 00 00 07 D0**
1490 1490  
1488 +**A9 00 00 00 00 07 D0**
1489 +
1491 1491  DO1 pin, DO2 pin, and DO3 pin will be set to high, last for 2 seconds, and then all change to low.
1492 1492  
1493 -**4. A9 00 11 01 00 07 D0**
1494 1494  
1493 +**A9 00 11 01 00 07 D0**
1494 +
1495 1495  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.
1496 +)))
1496 1496  
1497 1497  
1498 1498  ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
lt-22222-l-dashboard.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.pradeeka
Size
... ... @@ -1,0 +1,1 @@
1 +352.8 KB
Content