Changes for page LT-22222-L -- LoRa I/O Controller User Manual
Last modified by Mengting Qiu on 2025/06/04 18:42
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 3 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. pradeeka1 +XWiki.Xiaoling - Content
-
... ... @@ -54,8 +54,10 @@ 54 54 (% class="wikigeneratedid" %) 55 55 [[image:lorawan-nw.jpg||height="354" width="900"]] 56 56 57 + 57 57 == 1.2 Specifications == 58 58 60 + 59 59 (% style="color:#037691" %)**Hardware System:** 60 60 61 61 * STM32L072xxxx MCU ... ... @@ -116,13 +116,15 @@ 116 116 117 117 == 1.5 Hardware Variants == 118 118 119 -(% style="width:524px" %) 120 -|(% style="width:94px" %)**Model**|(% style="width:98px" %)**Photo**|(% style="width:329px" %)**Description** 121 -|(% style="width:94px" %)**LT33222-L**|(% style="width:98px" %)((( 122 - 123 -)))|(% style="width:329px" %)((( 124 -* 2 x Digital Input (Bi-direction) 125 -* 2 x Digital Output 121 + 122 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) 123 +|(% 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** 124 +|(% style="width:94px" %)**LT-22222-L**|(% style="width:172px" %)((( 125 +(% style="text-align:center" %) 126 +[[image:lt33222-l.jpg||height="116" width="100"]] 127 +)))|(% style="width:256px" %)((( 128 +* 3 x Digital Input (Bi-direction) 129 +* 3 x Digital Output 126 126 * 2 x Relay Output (5A@250VAC / 30VDC) 127 127 * 2 x 0~~20mA Analog Input (res:0.01mA) 128 128 * 2 x 0~~30V Analog Input (res:0.01v) ... ... @@ -237,7 +237,7 @@ 237 237 *** **Profile (Region)**: Select the region that matches your device. 238 238 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 239 239 240 -[[image:lt-22222-l-dev-repo-reg-p1.png ||height="625" width="1000"]]244 +[[image:lt-22222-l-dev-repo-reg-p1.png]] 241 241 242 242 243 243 * Register end device page continued... ... ... @@ -247,7 +247,7 @@ 247 247 ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. 248 248 ** Under **After registration**, select the **View registered end device** option. 249 249 250 -[[image:lt-22222-l-dev-repo-reg-p2.png ||height="625" width="1000"]]254 +[[image:lt-22222-l-dev-repo-reg-p2.png]] 251 251 252 252 253 253 ==== 3.2.2.3 Adding device manually ==== ... ... @@ -261,7 +261,7 @@ 261 261 ** Select the option **Over the air activation (OTAA)** under the **Activation mode.** 262 262 ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list. 263 263 264 -[[image:lt-22222-l-manually-p1.png ||height="625" width="1000"]]268 +[[image:lt-22222-l-manually-p1.png]] 265 265 266 266 267 267 * Register end device page continued... ... ... @@ -272,13 +272,13 @@ 272 272 ** Under **After registration**, select the **View registered end device** option. 273 273 ** Click the **Register end device** button. 274 274 275 -[[image:lt-22222-l-manually-p2.png ||height="625" width="1000"]]279 +[[image:lt-22222-l-manually-p2.png]] 276 276 277 277 278 278 You will be navigated to the **Device overview** page. 279 279 280 280 281 -[[image:lt-22222-device-overview.png ||height="625" width="1000"]]285 +[[image:lt-22222-device-overview.png]] 282 282 283 283 284 284 ==== 3.2.2.4 Joining ==== ... ... @@ -288,9 +288,10 @@ 288 288 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. 289 289 290 290 291 -[[image:lt-22222-join -network.png||height="625" width="1000"]]295 +[[image:lt-22222-l-joining.png]] 292 292 293 293 298 + 294 294 ==== 3.2.2.5 Uplinks ==== 295 295 296 296 ... ... @@ -307,7 +307,7 @@ 307 307 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. 308 308 {{/info}} 309 309 310 -[[image:lt-22222-ul-payload-fmt.png ||height="686" width="1000"]]315 +[[image:lt-22222-ul-payload-fmt.png]] 311 311 312 312 313 313 ==== 3.2.2.6 Downlinks ==== ... ... @@ -598,11 +598,11 @@ 598 598 599 599 (% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)** 600 600 601 -(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20 v), counter increase 1)**606 +(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), the counter increases by 1)** 602 602 603 -(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20 v), counter increase 1)**608 +(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If the AVI1 voltage is lower than VOLMAX (20000mV =20V), counter increases by 1)** 604 604 605 -(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20 v), counter increase 1)**610 +(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If the AVI1 voltage is higher than VOLMAX (20000mV =20V), counter increases by 1)** 606 606 ))) 607 607 608 608 ... ... @@ -721,9 +721,9 @@ 721 721 722 722 (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:** 723 723 724 -Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 729 +**Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 725 725 726 -Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4 731 +**Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4 727 727 728 728 AA: Type Code for this downlink Command: 729 729 ... ... @@ -790,7 +790,7 @@ 790 790 791 791 **Example:** 792 792 793 -10100000: Means the systemhas configure to use the trigger:AV1_LOW and AV2_LOW798 +10100000: This means the system is configured to use the triggers AV1_LOW and AV2_LOW. 794 794 795 795 796 796 (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below ... ... @@ -819,7 +819,7 @@ 819 819 820 820 **Example:** 821 821 822 -10000000: Meansthisuplink is triggered by AV1_LOW.Thatmeansthe voltage is too low.827 +10000000: The uplink is triggered by AV1_LOW, indicating that the voltage is too low. 823 823 824 824 825 825 (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below ... ... @@ -828,22 +828,22 @@ 828 828 |(% 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** 829 829 |(% 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 830 830 831 -* Each bit sshows which status has been triggered on this uplink.836 +* Each bit shows which status has been triggered on this uplink. 832 832 833 833 **Example:** 834 834 835 -00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1.840 +00000111: This means both DI1 and DI2 triggers are enabled, and this packet is trigger by DI1. 836 836 837 -00000101: Means both DI1 and DI2 trigger are enabled.842 +00000101: This means both DI1 and DI2 triggers are enabled. 838 838 839 839 840 -(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable. 845 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled. 841 841 842 -Downlink command to poll MOD6 status: 847 +Downlink command to poll/request MOD6 status: 843 843 844 844 **AB 06** 845 845 846 -When device gotthis command, it will send the MOD6 payload.851 +When device receives this command, it will send the MOD6 payload. 847 847 848 848 849 849 === 3.3.7 Payload Decoder === ... ... @@ -967,13 +967,13 @@ 967 967 Sets the device to working mode 2 (Double DI Counting + DO + RO) 968 968 ))) 969 969 970 -==== 3.4.2.3 Pollan uplink ====975 +==== 3.4.2.3 Request an uplink from the device ==== 971 971 972 -Requests an uplink from LT-22222-L. 977 +Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode. 973 973 974 974 (% style="color:#037691" %)**AT command** 975 975 976 -There is no AT Command torequestan uplinkfrom LT-22222-L981 +There is no AT Command available for this feature. 977 977 978 978 (% style="color:#037691" %)**Downlink payload** 979 979 ... ... @@ -981,7 +981,7 @@ 981 981 |(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF 982 982 |(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08 983 983 |(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 984 -08 FF 989 +08 **FF** 985 985 986 986 Requests an uplink from LT-22222-L. 987 987 ))) ... ... @@ -1015,7 +1015,7 @@ 1015 1015 |(% style="width:97px" %)**Parameters**|(% style="width:401px" %)((( 1016 1016 **prefix** : 0x0A 06 (two bytes in hexadecimal) 1017 1017 1018 -** working1023 +**enable/disable trigger_mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal. 1019 1019 ))) 1020 1020 |(% style="width:97px" %)**Example**|(% style="width:401px" %)((( 1021 1021 0A 06 **01** ... ... @@ -1023,13 +1023,13 @@ 1023 1023 Enable trigger mode for the current working mode 1024 1024 ))) 1025 1025 1026 -==== 3.4.2.5 Polltrigger settings ====1031 +==== 3.4.2.5 Request trigger settings ==== 1027 1027 1028 - Polls the trigger settings.1033 +Requests the trigger settings. 1029 1029 1030 1030 (% style="color:#037691" %)**AT Command:** 1031 1031 1032 -There is no AT Command for this feature. 1037 +There is no AT Command available for this feature. 1033 1033 1034 1034 (% style="color:#037691" %)**Downlink Payload** 1035 1035 ... ... @@ -1355,25 +1355,23 @@ 1355 1355 1356 1356 * (% style="color:#037691" %)**AT Command** 1357 1357 1358 -There is no AT Command to controlDigitalOutput1363 +There is no AT command to control the digital output. 1359 1359 1360 1360 1361 1361 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)** 1362 1362 1363 -(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Set DO1/DO2/DO3 output with time control 1368 +(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control 1364 1364 1365 - 1366 1366 This is to control the digital output time of DO pin. Include four bytes: 1367 1367 1368 -(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)1372 +(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9) 1369 1369 1370 -(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode1374 +(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode 1371 1371 1372 -01: DO pins will change back to original state after timeout. 1376 +**01:** DO pins revert to their original state after the timeout. 1377 +**00:** DO pins switch to an inverted state after the timeout. 1373 1373 1374 -00: DO pins will change to an inverter state after timeout 1375 1375 1376 - 1377 1377 (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status: 1378 1378 1379 1379 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) ... ... @@ -1382,7 +1382,7 @@ 1382 1382 |0x00|DO1 set to high 1383 1383 |0x11|DO1 NO Action 1384 1384 1385 -(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:1388 +(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status: 1386 1386 1387 1387 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1388 1388 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1390,7 +1390,7 @@ 1390 1390 |0x00|DO2 set to high 1391 1391 |0x11|DO2 NO Action 1392 1392 1393 -(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:1396 +(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status: 1394 1394 1395 1395 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1396 1396 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1398,7 +1398,7 @@ 1398 1398 |0x00|DO3 set to high 1399 1399 |0x11|DO3 NO Action 1400 1400 1401 -(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)1404 +(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms) 1402 1402 1403 1403 1404 1404 (% style="color:red" %)**Note: ** ... ... @@ -1407,7 +1407,7 @@ 1407 1407 1408 1408 Before firmware v1.6.0, the latch time only supported 2 bytes. 1409 1409 1410 -(% style="color:red" %)** Device will uploada packet if the downlink code executes successfully.**1413 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.** 1411 1411 1412 1412 1413 1413 **Example payload:** ... ... @@ -1434,16 +1434,16 @@ 1434 1434 1435 1435 * (% style="color:#037691" %)**AT Command:** 1436 1436 1437 -There is no AT Command to control Relay Output 1440 +There is no AT Command to control the Relay Output 1438 1438 1439 1439 1440 1440 * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):** 1441 1441 1442 -(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set RO1/RO2 output 1445 +(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Sets RO1/RO2 output 1443 1443 1444 1444 1445 1445 ((( 1446 -If payload is 0x030100, it means setting RO1 to close and RO2 to open. 1449 +If the payload is 0x030100, it means setting RO1 to close and RO2 to open. 1447 1447 ))) 1448 1448 1449 1449 ((( ... ... @@ -1461,7 +1461,7 @@ 1461 1461 |03 00 01|Open|Close 1462 1462 ))) 1463 1463 1464 -(% style="color:red" %)** Device will uploada packet if downlink code executes successfully.**1467 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.** 1465 1465 1466 1466 1467 1467 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== ... ... @@ -1470,19 +1470,19 @@ 1470 1470 1471 1471 * (% style="color:#037691" %)**AT Command:** 1472 1472 1473 -There is no AT Command to control Relay Output 1476 +There is no AT Command to control the Relay Output 1474 1474 1475 1475 1476 1476 * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):** 1477 1477 1478 -(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set RO1/RO2 relay with time control 1481 +(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Sets RO1/RO2 relays with time control 1479 1479 1480 1480 1481 -This is tocontrol the relay output time.Itincludesfourbytes:1484 +This controls the relay output time and includes 4 bytes: 1482 1482 1483 -(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)1486 +(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05) 1484 1484 1485 -(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode1488 +(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode 1486 1486 1487 1487 01: Relays will change back to their original state after timeout. 1488 1488 ... ... @@ -1489,12 +1489,12 @@ 1489 1489 00: Relays will change to the inverter state after timeout. 1490 1490 1491 1491 1492 -(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:1495 +(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status: 1493 1493 1494 1494 [[image:image-20221008095908-1.png||height="364" width="564"]] 1495 1495 1496 1496 1497 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms1500 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes (cc)**(%%): Latching time. Unit: ms 1498 1498 1499 1499 1500 1500 (% style="color:red" %)**Note:** ... ... @@ -1504,7 +1504,7 @@ 1504 1504 Before firmware v1.6.0, the latch time only supported 2 bytes. 1505 1505 1506 1506 1507 -(% style="color:red" %)** Device will uploada packet if the downlink code executes successfully.**1510 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.** 1508 1508 1509 1509 1510 1510 **Example payload:** ... ... @@ -1532,17 +1532,10 @@ 1532 1532 1533 1533 When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1534 1534 1535 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1536 - 1537 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):** 1538 - 1539 -(% style="color:blue" %)**0xA5 aa bb cc ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc 1540 - 1541 - 1542 1542 (% style="color:#037691" %)**AT Command** 1543 1543 1544 1544 (% border="2" style="width:500px" %) 1545 -|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage><logic> 1541 +|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage>,<logic> 1546 1546 |(% style="width:137px" %)**Response**|(% style="width:361px" %) 1547 1547 |(% style="width:137px" %)**Parameters**|(% style="width:361px" %)((( 1548 1548 **voltage** : voltage threshold in mV ... ... @@ -1549,9 +1549,9 @@ 1549 1549 1550 1550 **logic**: 1551 1551 1552 -0 : lower than 1548 +**0** : lower than 1553 1553 1554 -1: higher than 1550 +**1**: higher than 1555 1555 1556 1556 if you leave logic parameter blank, it is considered 0 1557 1557 ))) ... ... @@ -1580,9 +1580,9 @@ 1580 1580 1581 1581 **logic**: (1 byte in hexadecimal) 1582 1582 1583 -0 : lower than 1579 +**0** : lower than 1584 1584 1585 -1: higher than 1581 +**1**: higher than 1586 1586 1587 1587 if you leave logic parameter blank, it is considered 1 (higher than) 1588 1588 ))) ... ... @@ -1604,22 +1604,10 @@ 1604 1604 1605 1605 This command allows users to pre-configure specific count numbers for various counting parameters such as Count1, Count2, or AVI1 Count. Use the AT command to set the desired count number for each configuration. 1606 1606 1607 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) ** 1608 - 1609 -(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count 1610 - 1611 -(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set 1612 - 1613 - 1614 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):** 1615 - 1616 -(% style="color:blue" %)**0x A8 aa bb cc dd ee ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee) 1617 - 1618 - 1619 1619 (% style="color:#037691" %)**AT Command** 1620 1620 1621 1621 (% border="2" style="width:500px" %) 1622 -|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter><number> 1606 +|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter>,<number> 1623 1623 |(% style="width:134px" %)**Response**|(% style="width:364px" %) 1624 1624 |(% style="width:134px" %)**Parameters**|(% style="width:364px" %)((( 1625 1625 **counting_parameter** : ... ... @@ -1665,12 +1665,6 @@ 1665 1665 1666 1666 This command clears the counting in counting mode. 1667 1667 1668 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT **(%%) ~/~/ clear all counting 1669 - 1670 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):** 1671 - 1672 -(% style="color:blue" %)**0x A6 01 ** (%%)~/~/ clear all counting 1673 - 1674 1674 (% style="color:#037691" %)**AT Command** 1675 1675 1676 1676 (% border="2" style="width:500px" %) ... ... @@ -1688,24 +1688,10 @@ 1688 1688 ))) 1689 1689 |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01** 1690 1690 1691 -==== 3.4.2.19 Counting ~-~- Changecountingmodetosavetime====1669 +==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ==== 1692 1692 1693 1693 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. 1694 1694 1695 -* (% style="color:#037691" %)**AT Command:** 1696 - 1697 -(% style="color:blue" %)**AT+COUTIME=60 **(%%)~/~/ Sets the save time to 60 seconds. The device will save the counting result in internal flash every 60 seconds. (Min value: 30 seconds) 1698 - 1699 - 1700 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):** 1701 - 1702 -(% style="color:blue" %)**0x A7 aa bb cc ** (%%)~/~/ same as AT+COUTIME =aa bb cc, 1703 - 1704 -((( 1705 -Range: aa bb cc:0 to 16777215, (unit: seconds) 1706 -))) 1707 - 1708 - 1709 1709 (% style="color:#037691" %)**AT Command** 1710 1710 1711 1711 (% border="2" style="width:500px" %) ... ... @@ -1733,22 +1733,12 @@ 1733 1733 Sets the device to save its counting results to the memory every 60 seconds. 1734 1734 ))) 1735 1735 1736 -==== 3.4.2.20 Reset save RO DO state ==== 1700 +==== 3.4.2.20 Reset saved RO and DO states ==== 1737 1737 1738 1738 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. 1739 1739 1740 - *(% style="color:#037691" %)**AT Command:**1704 +(% style="color:#037691" %)**AT Command** 1741 1741 1742 -(% style="color:blue" %)**AT+RODORESET=1 **(%%)~/~/ RODO will close when the device joining the network. (default) 1743 - 1744 -(% style="color:blue" %)**AT+RODORESET=0 **(%%)~/~/ After the device is reset, the previously saved RODO state (only MOD2 to MOD5) is read, and its state will not change when the device reconnects to the network. 1745 - 1746 - 1747 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):** 1748 - 1749 -(% style="color:blue" %)**0x AD aa ** (%%)~/~/ same as AT+RODORET =aa 1750 - 1751 - 1752 1752 (% border="2" style="width:500px" %) 1753 1753 |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state> 1754 1754 |(% style="width:127px" %)**Response**|(% style="width:371px" %) ... ... @@ -1769,6 +1769,8 @@ 1769 1769 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. 1770 1770 ))) 1771 1771 1726 +(% style="color:#037691" %)**Downlink Payload** 1727 + 1772 1772 (% border="2" style="width:500px" %) 1773 1773 |(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state> 1774 1774 |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( ... ... @@ -1794,22 +1794,17 @@ 1794 1794 1795 1795 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. 1796 1796 1797 - *(% style="color:#037691" %)**AT Command:**1753 +(% style="color:#037691" %)**AT Command:** 1798 1798 1799 -(% style="color:blue" %)**AT+DECRYPT=1 ** (%%)~/~/ The payload is uploaded without encryption 1800 - 1801 -(% style="color:blue" %)**AT+DECRYPT=0 **(%%)~/~/ Encrypt when uploading payload (default) 1802 - 1803 - 1804 1804 (% border="2" style="width:500px" %) 1805 1805 |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state> 1806 1806 |(% style="width:127px" %)**Response**|(% style="width:371px" %) 1807 1807 |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1808 -state : 1759 +**state** : 1809 1809 1810 -1 : The payload is uploaded without encryption 1761 +**1** : The payload is uploaded without encryption 1811 1811 1812 -0 : The payload is encrypted when uploaded (default) 1763 +**0** : The payload is encrypted when uploaded (default) 1813 1813 ))) 1814 1814 |(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1815 1815 AT+DECRYPT=1 ... ... @@ -1828,13 +1828,8 @@ 1828 1828 1829 1829 This command allows you to retrieve and optionally uplink sensor readings through the serial port. 1830 1830 1831 - *(% style="color:#037691" %)**AT Command:**1782 +(% style="color:#037691" %)**AT Command** 1832 1832 1833 -(% style="color:blue" %)**AT+GETSENSORVALUE=0 **(%%)~/~/ The serial port retrieves the reading of the current sensor. 1834 - 1835 -(% style="color:blue" %)**AT+GETSENSORVALUE=1 **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it. 1836 - 1837 - 1838 1838 (% border="2" style="width:500px" %) 1839 1839 |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state> 1840 1840 |(% style="width:127px" %)**Response**|(% style="width:371px" %) ... ... @@ -1862,13 +1862,8 @@ 1862 1862 1863 1863 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. 1864 1864 1865 - *(% style="color:#037691" %)**AT Command:**1811 +(% style="color:#037691" %)**AT Command** 1866 1866 1867 -(% style="color:blue" %)**AT+DISFCNTCHECK=0 **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node will no longer receive downlink packets (default) 1868 - 1869 -(% style="color:blue" %)**AT+DISFCNTCHECK=1 **(%%)~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node resets the downlink packet count and keeps it consistent with the server downlink packet count. 1870 - 1871 - 1872 1872 (% border="2" style="width:500px" %) 1873 1873 |(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state> 1874 1874 |(% style="width:130px" %)**Response**|(% style="width:368px" %)((( ... ... @@ -1900,17 +1900,6 @@ 1900 1900 1901 1901 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. 1902 1902 1903 -* (% style="color:#037691" %)**AT Command:** 1904 - 1905 -(% style="color:blue" %)**AT+DISMACANS=0** (%%) ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of 11 bytes (DR0 of US915, DR2 of AS923, DR2 of AU195), the node will send a packet with a payload of 00 and a port of 4. (default) 1906 - 1907 -(% style="color:blue" %)**AT+DISMACANS=1** (%%) ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of the DR, the node will ignore the MACANS and not reply, and only upload the payload part. 1908 - 1909 - 1910 -* (% style="color:#037691" %)**Downlink Payload **(%%)**:** 1911 - 1912 -(% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set the DISMACANS=1 1913 - 1914 1914 (% style="color:#037691" %)**AT Command** 1915 1915 1916 1916 (% border="2" style="width:500px" %) ... ... @@ -2024,7 +2024,7 @@ 2024 2024 The username and password (API key) you created here are required in the next section. 2025 2025 {{/info}} 2026 2026 2027 -[[image:tts-mqtt-integration.png ||height="625" width="1000"]]1957 +[[image:tts-mqtt-integration.png]] 2028 2028 2029 2029 === 3.5.2 Configuring ThingsEye.io === 2030 2030 ... ... @@ -2034,7 +2034,7 @@ 2034 2034 * Under the **Integrations center**, click **Integrations**. 2035 2035 * Click the **Add integration** button (the button with the **+** symbol). 2036 2036 2037 -[[image:thingseye-io-step-1.png ||height="625" width="1000"]]1967 +[[image:thingseye-io-step-1.png]] 2038 2038 2039 2039 2040 2040 On the **Add integration** window, configure the following: ... ... @@ -2049,7 +2049,7 @@ 2049 2049 ** Allow create devices or assets 2050 2050 * Click the **Next** button. you will be navigated to the **Uplink data converter** tab. 2051 2051 2052 -[[image:thingseye-io-step-2.png ||height="625" width="1000"]]1982 +[[image:thingseye-io-step-2.png]] 2053 2053 2054 2054 2055 2055 **Uplink data converter:** ... ... @@ -2060,7 +2060,7 @@ 2060 2060 * 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]]. 2061 2061 * Click the **Next** button. You will be navigated to the **Downlink data converter **tab. 2062 2062 2063 -[[image:thingseye-io-step-3.png ||height="625" width="1000"]]1993 +[[image:thingseye-io-step-3.png]] 2064 2064 2065 2065 2066 2066 **Downlink data converter (this is an optional step):** ... ... @@ -2071,7 +2071,7 @@ 2071 2071 * 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]]. 2072 2072 * Click the **Next** button. You will be navigated to the **Connection** tab. 2073 2073 2074 -[[image:thingseye-io-step-4.png ||height="625" width="1000"]]2004 +[[image:thingseye-io-step-4.png]] 2075 2075 2076 2076 2077 2077 **Connection:** ... ... @@ -2086,13 +2086,13 @@ 2086 2086 2087 2087 * Click the **Add** button. 2088 2088 2089 -[[image:thingseye-io-step-5.png ||height="625" width="1000"]]2019 +[[image:thingseye-io-step-5.png]] 2090 2090 2091 2091 2092 2092 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. 2093 2093 2094 2094 2095 -[[image:thingseye.io_integrationsCenter_integrations.png ||height="686" width="1000"]]2025 +[[image:thingseye.io_integrationsCenter_integrations.png]] 2096 2096 2097 2097 2098 2098 ==== 3.5.2.1 Viewing integration details ==== ... ... @@ -2099,7 +2099,7 @@ 2099 2099 2100 2100 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. 2101 2101 2102 -[[image:integration-details.png ||height="686" width="1000"]]2032 +[[image:integration-details.png]] 2103 2103 2104 2104 2105 2105 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. ... ... @@ -2115,12 +2115,12 @@ 2115 2115 * Select **Debug **from the **Event type** dropdown. 2116 2116 * Select the** time frame** from the **time window**. 2117 2117 2118 -[[image:thingseye-events.png ||height="686" width="1000"]]2048 +[[image:thingseye-events.png]] 2119 2119 2120 2120 2121 2121 * To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message. 2122 2122 2123 -[[image:thingseye-json.png ||width="1000"]]2053 +[[image:thingseye-json.png]] 2124 2124 2125 2125 2126 2126 ==== **3.5.2.3 Deleting an integration** ==== ... ... @@ -2138,7 +2138,7 @@ 2138 2138 === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) === 2139 2139 2140 2140 2141 -Supports 2071 +Supports** NPN-type **sensors. 2142 2142 2143 2143 [[image:1653356991268-289.png]] 2144 2144 ... ... @@ -2260,15 +2260,15 @@ 2260 2260 ))) 2261 2261 2262 2262 2263 -(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor 2193 +(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor 2264 2264 2265 -From the DI port circuit above, you can see that activating the photocoupler requires a voltage difference between the DI+ and DI- ports. However, the Dry Contact sensor is a passive component and cannot provide this voltage difference.2195 +From the DI port circuit above, activating the photocoupler requires a voltage difference between the DI+ and DI- ports. However, the Dry Contact sensor is a passive component and cannot provide this voltage difference on its own. 2266 2266 2267 -To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Belowis areference circuit diagram.2197 +To detect a Dry Contact, you can supply a power source to one of the pins of the Dry Contact. A reference circuit diagram is shown below. 2268 2268 2269 2269 [[image:image-20230616235145-1.png]] 2270 2270 2271 -(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector 2201 +(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector 2272 2272 2273 2273 [[image:image-20240219115718-1.png]] 2274 2274 ... ... @@ -2344,7 +2344,7 @@ 2344 2344 [[image:image-20220524100215-10.png||height="382" width="723"]] 2345 2345 2346 2346 2347 -== 3.7 LED sIndicators ==2277 +== 3.7 LED Indicators == 2348 2348 2349 2349 The table below lists the behavior of LED indicators for each port function. 2350 2350 ... ... @@ -2383,13 +2383,14 @@ 2383 2383 == 4.1 Connecting the LT-22222-L to a PC == 2384 2384 2385 2385 ((( 2386 -You can use a USB-to-TTL adapter along with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below. 2316 +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. 2387 2387 2388 -[[image:usb-ttl-programming.png]] 2318 +[[image:usb-ttl-audio-jack-connection.jpg]] 2319 + 2320 + 2389 2389 ))) 2390 2390 2391 2391 2392 - 2393 2393 ((( 2394 2394 On the PC, you need to set the (% style="color:#4f81bd" %)**serial tool **(%%)(such as [[PuTTY>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]] or [[SecureCRT>>https://www.vandyke.com/cgi-bin/releases.php?product=securecrt]]) to a baud rate of (% style="color:green" %)**9600**(%%) to access the serial console of LT-22222-L. Access to AT commands is disabled by default, and a password (default: (% style="color:green" %)**123456**)(%%) must be entered to enable AT command access, as shown below: 2395 2395 ))) ... ... @@ -2419,39 +2419,39 @@ 2419 2419 * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey) 2420 2420 * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI) 2421 2421 * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON) 2422 -* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification) 2423 -* AT+DR: Get or set the Data Rate. (0-7 corresponding to DR_X) 2424 -* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing 2425 -* AT+PNM: Get or set the public network mode. (0: off, 1: on) 2426 -* AT+RX2FQ: Get or set the Rx2 window frequency 2427 -* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X) 2428 -* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms 2429 -* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms 2430 -* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms 2431 -* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms 2432 -* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA) 2433 -* AT+NWKID: Get or set the Network ID 2434 -* AT+FCU: Get or set the Frame Counter Uplink (FCntUp) 2435 -* AT+FCD: Get or set the Frame Counter Downlink (FCntDown) 2436 -* AT+CLASS: Get or set the Device Class 2437 -* AT+JOIN: Join network 2438 -* AT+NJS: Get OTAA Join Status 2439 -* AT+SENDB: Send hexadecimal data along with the application port 2440 -* AT+SEND: Send text data along with the application port 2441 -* AT+RECVB: Print last received data in binary format (with hexadecimal values) 2442 -* AT+RECV: Print last received data in raw format 2443 -* AT+VER: Get current image version and Frequency Band 2444 -* AT+CFM: Get or Set the confirmation mode (0-1) 2445 -* AT+CFS: Get confirmation status of the last AT+SEND (0-1) 2446 -* AT+SNR: Get the SNR of the last received packet 2447 -* AT+RSSI: Get the RSSI of the last received packet 2448 -* AT+TDC: Get or set the application data transmission interval in ms 2449 -* AT+PORT: Get or set the application port 2450 -* AT+DISAT: Disable AT commands 2451 -* AT+PWORD: Set password, max 9 digits 2452 -* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode 2453 -* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470 2454 -* AT+CFG: Print all settings 2353 +* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification) 2354 +* **##AT+DR##**: Get or set the Data Rate. (0-7 corresponding to DR_X) 2355 +* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing 2356 +* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on) 2357 +* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency 2358 +* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X) 2359 +* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms 2360 +* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms 2361 +* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms 2362 +* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms 2363 +* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA) 2364 +* ##**AT+NWKID**##: Get or set the Network ID 2365 +* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp) 2366 +* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown) 2367 +* ##**AT+CLASS**##: Get or set the Device Class 2368 +* ##**AT+JOIN**##: Join network 2369 +* ##**AT+NJS**##: Get OTAA Join Status 2370 +* ##**AT+SENDB**##: Send hexadecimal data along with the application port 2371 +* ##**AT+SEND**##: Send text data along with the application port 2372 +* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values) 2373 +* ##**AT+RECV**##: Print last received data in raw format 2374 +* ##**AT+VER**##: Get current image version and Frequency Band 2375 +* ##**AT+CFM**##: Get or Set the confirmation mode (0-1) 2376 +* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1) 2377 +* ##**AT+SNR**##: Get the SNR of the last received packet 2378 +* ##**AT+RSSI**##: Get the RSSI of the last received packet 2379 +* ##**AT+TDC**##: Get or set the application data transmission interval in ms 2380 +* ##**AT+PORT**##: Get or set the application port 2381 +* ##**AT+DISAT**##: Disable AT commands 2382 +* ##**AT+PWORD**##: Set password, max 9 digits 2383 +* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode 2384 +* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN470 2385 +* ##**AT+CFG**##: Print all settings 2455 2455 ))) 2456 2456 2457 2457 ... ... @@ -2616,7 +2616,7 @@ 2616 2616 You will need the following things before proceeding: 2617 2617 2618 2618 * 3.5mm programming cable (included with the LT-22222-L as an additional accessory) 2619 -* USB to TTL adapter 2550 +* USB to TTL adapter/converter 2620 2620 * Download and install the [[STM32 Flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]]. (replaced by STM32CubeProgrammer) 2621 2621 * Download the latest firmware image from [[LT-22222-L firmware image files>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACrbrDN0AqLHbBat0ViWx5Da/LT-22222-L/Firmware?dl=0&subfolder_nav_tracking=1]]. Check the file name of the firmware to find the correct region. 2622 2622 ... ... @@ -2626,7 +2626,7 @@ 2626 2626 2627 2627 Below is the hardware setup for uploading a firmware image to the LT-22222-L: 2628 2628 2629 -[[image:usb-ttl- programming.png]]2560 +[[image:usb-ttl-audio-jack-connection.jpg]] 2630 2630 2631 2631 2632 2632
- lt-22222-l-joining.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +301.9 KB - Content
- lt33222-l.jpg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +31.3 KB - Content
- usb-ttl-audio-jack-connection.jpg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.pradeeka - Size
-
... ... @@ -1,0 +1,1 @@ 1 +394.4 KB - Content