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

From version 235.1
edited by Dilisi S
on 2024/12/17 06:12
Change comment: Dec 16 edits
To version 230.15
edited by Xiaoling
on 2024/12/09 10:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.pradeeka
1 +XWiki.Xiaoling
Content
... ... @@ -98,6 +98,7 @@
98 98  * Automatic RF Sense and CAD with ultra-fast AFC.
99 99  * Packet engine up to 256 bytes with CRC.
100 100  
101 +
101 101  == 1.3 Features ==
102 102  
103 103  
... ... @@ -109,6 +109,7 @@
109 109  * Firmware upgradable via program port
110 110  * Counting
111 111  
113 +
112 112  == 1.4 Applications ==
113 113  
114 114  
... ... @@ -119,6 +119,7 @@
119 119  * Smart cities
120 120  * Smart factory
121 121  
124 +
122 122  == 1.5 Hardware Variants ==
123 123  
124 124  
... ... @@ -136,6 +136,7 @@
136 136  * 1 x Counting Port
137 137  )))
138 138  
142 +
139 139  = 2. Assembling the device =
140 140  
141 141  == 2.1 Connecting the antenna ==
... ... @@ -155,7 +155,7 @@
155 155  
156 156  **Upper screw terminal block (from left to right):**
157 157  
158 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:381px" %)
162 +(% border="1" cellspacing="3" style="width:381px;background-color:#f2f2f2" %)
159 159  |=(% style="width: 139px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 242px;background-color:#4f81bd;color:white" %)Function
160 160  |(% style="width:139px" %)GND|(% style="width:242px" %)Ground
161 161  |(% style="width:139px" %)VIN|(% style="width:242px" %)Input Voltage
... ... @@ -166,7 +166,7 @@
166 166  
167 167  **Lower screw terminal block (from left to right):**
168 168  
169 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:253px" %)
173 +(% border="1" cellspacing="3" style="width:253px;background-color:#f2f2f2" %)
170 170  |=(% style="width: 125px;background-color:#4f81bd;color:white" %)Screw Terminal|=(% style="width: 128px;background-color:#4f81bd;color:white" %)Function
171 171  |(% style="width:125px" %)RO1-2|(% style="width:128px" %)Relay Output 1
172 172  |(% style="width:125px" %)RO1-1|(% style="width:128px" %)Relay Output 1
... ... @@ -181,7 +181,6 @@
181 181  
182 182  == 2.3 Connecting LT-22222-L to a Power Source ==
183 183  
184 -
185 185  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.
186 186  
187 187  {{warning}}
... ... @@ -194,27 +194,23 @@
194 194  
195 195  = 3. Registering LT-22222-L with a LoRaWAN Network Server =
196 196  
197 -
198 198  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.
199 199  
200 200  
201 -== 3.1 Prerequisites ==
203 +=== 3.2.1 Prerequisites ===
202 202  
203 -
204 204  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.
205 205  
206 206  [[image:image-20230425173427-2.png||height="246" width="530"]]
207 207  
208 208  {{info}}
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.
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.
210 210  {{/info}}
211 211  
212 212  The following subsections explain how to register the LT-22222-L with different LoRaWAN network server providers.
213 213  
215 +=== 3.2.2 The Things Stack ===
214 214  
215 -== 3.2 The Things Stack ==
216 -
217 -
218 218  This section guides you through how to register your LT-22222-L with The Things Stack Sandbox.
219 219  
220 220  {{info}}
... ... @@ -225,7 +225,7 @@
225 225  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.
226 226  
227 227  
228 -[[image:dragino-lorawan-nw-lt-22222-n.jpg||height="374" width="1400"]]
227 +[[image:dragino-lorawan-nw-lt-22222-n.jpg]]
229 229  
230 230  {{info}}
231 231   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.
... ... @@ -232,9 +232,8 @@
232 232  {{/info}}
233 233  
234 234  
235 -=== 3.2.1 Setting up ===
234 +==== 3.2.2.1 Setting up ====
236 236  
237 -
238 238  * Sign up for a free account with [[The Things Stack Sandbox>>https://eu1.cloud.thethings.network]] if you do not have one yet.
239 239  * Log in to your The Things Stack Sandbox account.
240 240  * Create an **application** with The Things Stack if you do not have one yet (E.g., dragino-docs).
... ... @@ -241,9 +241,8 @@
241 241  * Go to your application's page and click on the **End devices** in the left menu.
242 242  * On the End devices page, click on **+ Register end device**. Two registration options are available:
243 243  
244 -==== 3.2.1.1 Using the LoRaWAN Device Repository ====
242 +==== 3.2.2.2 Using the LoRaWAN Device Repository ====
245 245  
246 -
247 247  * On the **Register end device** page:
248 248  ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
249 249  ** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists.
... ... @@ -267,9 +267,8 @@
267 267  [[image:lt-22222-l-dev-repo-reg-p2.png]]
268 268  
269 269  
270 -==== 3.2.1.2 Adding device manually ====
267 +==== 3.2.2.3 Adding device manually ====
271 271  
272 -
273 273  * On the **Register end device** page:
274 274  ** Select the option **Enter end device specifies manually** under **Input method**.
275 275  ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
... ... @@ -299,9 +299,8 @@
299 299  [[image:lt-22222-device-overview.png]]
300 300  
301 301  
302 -=== 3.2.2 Joining ===
298 +==== 3.2.2.4 Joining ====
303 303  
304 -
305 305  On the Device's page, click on **Live data** tab. The Live data panel for your device will display.
306 306  
307 307  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.
... ... @@ -310,9 +310,10 @@
310 310  [[image:lt-22222-l-joining.png]]
311 311  
312 312  
313 -=== 3.2.3 Uplinks ===
314 314  
309 +==== 3.2.2.5 Uplinks ====
315 315  
311 +
316 316  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.
317 317  
318 318  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.
... ... @@ -335,9 +335,8 @@
335 335  [[image:lt-22222-l-js-custom-payload-formatter.png]]
336 336  
337 337  
338 -=== 3.2.4 Downlinks ===
334 +==== 3.2.2.6 Downlinks ====
339 339  
340 -
341 341  When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**.
342 342  
343 343  
... ... @@ -360,10 +360,8 @@
360 360  
361 361  The uplink messages are sent over LoRaWAN FPort=2. By default, an uplink message is sent every 10 minutes.
362 362  
363 -
364 364  === 3.3.1 AT+MOD~=1, 2ACI+2AVI ===
365 365  
366 -
367 367  (((
368 368  This is the default mode.
369 369  
... ... @@ -436,7 +436,6 @@
436 436  
437 437  MOD = 1
438 438  
439 -
440 440  === 3.3.2 AT+MOD~=2, (Double DI Counting) ===
441 441  
442 442  
... ... @@ -515,7 +515,6 @@
515 515  
516 516  === 3.3.3 AT+MOD~=3, Single DI Counting + 2 x ACI ===
517 517  
518 -
519 519  (% style="color:red" %)**Note: The maximum count depends on the bytes it is.
520 520  The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
521 521  It starts counting again when it reaches the maximum value.**
... ... @@ -569,7 +569,6 @@
569 569  
570 570  === 3.3.4 AT+MOD~=4, Single DI Counting + 1 x Voltage Counting ===
571 571  
572 -
573 573  (% style="color:red" %)**Note:The maximum count depends on the bytes it is.
574 574  The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
575 575  It starts counting again when it reaches the maximum value.**
... ... @@ -639,7 +639,6 @@
639 639  
640 640  === 3.3.5 AT+MOD~=5, Single DI Counting + 2 x AVI + 1 x ACI ===
641 641  
642 -
643 643  (% style="color:red" %)**Note:The maximum count depends on the bytes it is.
644 644  The maximum count for four bytes is FFFFFFFF (hex) = 4294967295 (dec).
645 645  It starts counting again when it reaches the maximum value.**
... ... @@ -1418,127 +1418,113 @@
1418 1418  ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
1419 1419  
1420 1420  
1421 -(% style="color:#037691" %)**AT command**
1410 +* (% style="color:#037691" %)**AT Command**
1422 1422  
1423 1423  There is no AT command to control the digital output.
1424 1424  
1425 1425  
1426 -(% style="color:#037691" %)**Downlink payload**
1415 +* (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
1427 1427  
1417 +(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control
1428 1428  
1429 -(% border="2" style="width:500px" %)
1430 -|(% style="width:116px" %)**Prefix**|(% style="width:382px" %)0xA9
1431 -|(% style="width:116px" %)**Parameters**|(% style="width:382px" %)(((
1432 -**inverter_mode**: 1 byte in hex.
1419 +This is to control the digital output time of DO pin. Include four bytes:
1433 1433  
1421 +(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)
1422 +
1423 +(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode
1424 +
1434 1434  **01:** DO pins revert to their original state after the timeout.
1435 1435  **00:** DO pins switch to an inverted state after the timeout.
1436 1436  
1437 1437  
1438 -**DO1_control_method_and_port_status **- 1 byte in hex
1429 +(% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
1439 1439  
1440 -0x01 : DO1 set to low
1431 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1432 +|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
1433 +|0x01|DO1 set to low
1434 +|0x00|DO1 set to high
1435 +|0x11|DO1 NO Action
1441 1441  
1442 -0x00 : DO1 set to high
1437 +(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:
1443 1443  
1444 -0x11 : DO1 NO action
1439 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1440 +|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
1441 +|0x01|DO2 set to low
1442 +|0x00|DO2 set to high
1443 +|0x11|DO2 NO Action
1445 1445  
1445 +(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:
1446 1446  
1447 -**DO2_control_method_and_port_status** - 1 byte in hex
1447 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1448 +|(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
1449 +|0x01|DO3 set to low
1450 +|0x00|DO3 set to high
1451 +|0x11|DO3 NO Action
1448 1448  
1449 -0x01 : DO2 set to low
1453 +(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms)
1450 1450  
1451 -0x00 : DO2 set to high
1452 1452  
1453 -0x11 : DO2 NO action
1454 -
1455 -
1456 -**DO3_control_method_and_port_status **- 1 byte in hex
1457 -
1458 -0x01 : DO3 set to low
1459 -
1460 -0x00 : DO3 set to high
1461 -
1462 -0x11 : DO3 NO action
1463 -
1464 -
1465 -**latching_time** : 4 bytes in hex
1466 -
1467 1467  (% style="color:red" %)**Note: **
1468 1468  
1469 - Since firmware v1.6.0, the latch time support 4 bytes or 2 bytes
1458 + Since firmware v1.6.0, the latch time support 4 bytes and 2 bytes
1470 1470  
1471 1471   Before firmware v1.6.0, the latch time only supported 2 bytes.
1472 1472  
1473 1473  (% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1474 -)))
1475 -|(% 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>
1476 -|(% style="width:116px" %)**Example**|(% style="width:382px" %)(((
1477 -**A9 01 01 01 01 07 D0**
1478 1478  
1479 -DO1 pin, DO2 pin, and DO3 pin will be set to low, last for 2 seconds, and then revert to their original state.
1480 1480  
1465 +**Example payload:**
1481 1481  
1482 -**A9 01 00 01 11 07 D0**
1467 +**~1. A9 01 01 01 01 07 D0**
1483 1483  
1484 -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.
1469 +DO1 pin, DO2 pin, and DO3 pin will be set to low, last for 2 seconds, and then revert to their original state.
1485 1485  
1471 +**2. A9 01 00 01 11 07 D0**
1486 1486  
1487 -**A9 00 00 00 00 07 D0**
1473 +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  
1475 +**3. A9 00 00 00 00 07 D0**
1476 +
1489 1489  DO1 pin, DO2 pin, and DO3 pin will be set to high, last for 2 seconds, and then all change to low.
1490 1490  
1479 +**4. A9 00 11 01 00 07 D0**
1491 1491  
1492 -**A9 00 11 01 00 07 D0**
1493 -
1494 1494  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.
1495 -)))
1496 1496  
1483 +
1497 1497  ==== 3.4.2.14 Relay ~-~- Control Relay Output RO1/RO2 ====
1498 1498  
1499 1499  
1500 -(% style="color:#037691" %)**AT Command:**
1487 +* (% style="color:#037691" %)**AT Command:**
1501 1501  
1502 -There is no AT Command to control the Relay Output.
1489 +There is no AT Command to control the Relay Output
1503 1503  
1504 1504  
1505 -(% style="color:#037691" %)**Downlink Payload**
1492 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
1506 1506  
1507 -(% border="2" style="width:500px" %)
1508 -|(% style="width:113px" %)**Prefix**|(% style="width:384px" %)0x03
1509 -|(% style="width:113px" %)**Parameters**|(% style="width:384px" %)(((
1510 -**RO1_status** : 1 byte in hex
1494 +(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Sets RO1/RO2 output
1511 1511  
1512 -00: Close
1513 1513  
1514 -01: Open
1497 +(((
1498 +If the payload is 0x030100, it means setting RO1 to close and RO2 to open.
1499 +)))
1515 1515  
1516 -11: No action
1501 +(((
1502 +00: Close ,  01: Open , 11: No action
1517 1517  
1518 -
1519 -**RO2_status** : 1 byte in hex
1520 -
1521 -00: Close
1522 -
1523 -01: Open
1524 -
1525 -11: No action
1504 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:320px" %)
1505 +|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**RO1**|(% style="background-color:#4f81bd; color:white" %)**RO2**
1506 +|03  00  11|Open|No Action
1507 +|03  01  11|Close|No Action
1508 +|03  11  00|No Action|Open
1509 +|03  11  01|No Action|Close
1510 +|03  00  00|Open|Open
1511 +|03  01  01|Close|Close
1512 +|03  01  00|Close|Open
1513 +|03  00  01|Open|Close
1526 1526  )))
1527 -|(% style="width:113px" %)**Payload format**|(% style="width:384px" %)<prefix><RO1_status><RO2_status>
1528 -|(% style="width:113px" %)**Example**|(% style="width:384px" %)(((
1529 -(% border="2" %)
1530 -|=Payload|=RO1|=RO2
1531 -|03  00  11|Open|No action
1532 -|03  01  11|Close|No action
1533 -|03 11  00|No action|Open
1534 -|03 11 10|No action|Close
1535 -|03 00 00|Open|Open
1536 -|03 01 01|Close|Close
1537 -|03 01 00|Close|Open
1538 -|03 00 01|Open|Close
1539 1539  
1540 -(% style="color:red" %)**The device will transmit an uplink packet if the downlink payload is executed successfully.**
1541 -)))
1516 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1542 1542  
1543 1543  
1544 1544  ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
... ... @@ -1546,13 +1546,12 @@
1546 1546  
1547 1547  Controls the relay output time.
1548 1548  
1524 +* (% style="color:#037691" %)**AT Command:**
1549 1549  
1550 -(% style="color:#037691" %)**AT Command:**
1551 -
1552 1552  There is no AT Command to control the Relay Output
1553 1553  
1554 1554  
1555 -(% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1529 +* (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1556 1556  
1557 1557  (% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
1558 1558  
... ... @@ -2127,7 +2127,7 @@
2127 2127  [[image:thingseye-events.png]]
2128 2128  
2129 2129  
2130 -* To view the **JSON payload** of a message, click on the **three dots (...)** in the **Message** column of the desired message.
2104 +* To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
2131 2131  
2132 2132  [[image:thingseye-json.png]]
2133 2133  
... ... @@ -2138,16 +2138,12 @@
2138 2138  If you want to delete an integration, click the **Delete integratio**n button on the Integrations page.
2139 2139  
2140 2140  
2141 -==== 3.5.2.4 Viewing sensor data on a dashboard ====
2115 +==== 3.5.2.4 Creating a Dashboard to Display and Analyze LT-22222-L Data ====
2142 2142  
2143 2143  
2144 -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.
2118 +This will be added soon.
2145 2145  
2146 2146  
2147 -
2148 -[[image:lt-22222-l-dashboard.png]]
2149 -
2150 -
2151 2151  == 3.6 Interface Details ==
2152 2152  
2153 2153  === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
... ... @@ -2891,6 +2891,7 @@
2891 2891  * (% style="color:red" %)**IN865**(%%): LT with frequency bands IN865
2892 2892  * (% style="color:red" %)**CN779**(%%): LT with frequency bands CN779
2893 2893  
2864 +
2894 2894  = 9. Package information =
2895 2895  
2896 2896  
... ... @@ -2908,6 +2908,7 @@
2908 2908  * Package Size / pcs : 14.5 x 8 x 5 cm
2909 2909  * Weight / pcs : 170 g
2910 2910  
2882 +
2911 2911  = 10. Support =
2912 2912  
2913 2913  
lt-22222-l-dashboard.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.pradeeka
Size
... ... @@ -1,1 +1,0 @@
1 -352.8 KB
Content