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 (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 4 removed)
Details
- Page properties
-
- Content
-
... ... @@ -54,10 +54,8 @@ 54 54 (% class="wikigeneratedid" %) 55 55 [[image:lorawan-nw.jpg||height="354" width="900"]] 56 56 57 - 58 58 == 1.2 Specifications == 59 59 60 - 61 61 (% style="color:#037691" %)**Hardware System:** 62 62 63 63 * STM32L072xxxx MCU ... ... @@ -118,15 +118,13 @@ 118 118 119 119 == 1.5 Hardware Variants == 120 120 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 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 130 130 * 2 x Relay Output (5A@250VAC / 30VDC) 131 131 * 2 x 0~~20mA Analog Input (res:0.01mA) 132 132 * 2 x 0~~30V Analog Input (res:0.01v) ... ... @@ -241,7 +241,7 @@ 241 241 *** **Profile (Region)**: Select the region that matches your device. 242 242 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list. 243 243 244 -[[image:lt-22222-l-dev-repo-reg-p1.png]] 240 +[[image:lt-22222-l-dev-repo-reg-p1.png||height="625" width="1000"]] 245 245 246 246 247 247 * Register end device page continued... ... ... @@ -251,7 +251,7 @@ 251 251 ** In the **End device ID** field, enter a unique name for your LT-22222-N within this application. 252 252 ** Under **After registration**, select the **View registered end device** option. 253 253 254 -[[image:lt-22222-l-dev-repo-reg-p2.png]] 250 +[[image:lt-22222-l-dev-repo-reg-p2.png||height="625" width="1000"]] 255 255 256 256 257 257 ==== 3.2.2.3 Adding device manually ==== ... ... @@ -265,7 +265,7 @@ 265 265 ** Select the option **Over the air activation (OTAA)** under the **Activation mode.** 266 266 ** Select **Class C (Continuous)** from the **Additional LoRaWAN class capabilities** dropdown list. 267 267 268 -[[image:lt-22222-l-manually-p1.png]] 264 +[[image:lt-22222-l-manually-p1.png||height="625" width="1000"]] 269 269 270 270 271 271 * Register end device page continued... ... ... @@ -276,13 +276,13 @@ 276 276 ** Under **After registration**, select the **View registered end device** option. 277 277 ** Click the **Register end device** button. 278 278 279 -[[image:lt-22222-l-manually-p2.png]] 275 +[[image:lt-22222-l-manually-p2.png||height="625" width="1000"]] 280 280 281 281 282 282 You will be navigated to the **Device overview** page. 283 283 284 284 285 -[[image:lt-22222-device-overview.png]] 281 +[[image:lt-22222-device-overview.png||height="625" width="1000"]] 286 286 287 287 288 288 ==== 3.2.2.4 Joining ==== ... ... @@ -292,10 +292,9 @@ 292 292 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. 293 293 294 294 295 -[[image:lt-22222- l-joining.png]]291 +[[image:lt-22222-join-network.png||height="625" width="1000"]] 296 296 297 297 298 - 299 299 ==== 3.2.2.5 Uplinks ==== 300 300 301 301 ... ... @@ -312,15 +312,9 @@ 312 312 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. 313 313 {{/info}} 314 314 315 -[[image:lt-22222-ul-payload-fmt.png]] 310 +[[image:lt-22222-ul-payload-fmt.png||height="686" width="1000"]] 316 316 317 317 318 -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]]: 319 - 320 -(% class="wikigeneratedid" %) 321 -[[image:lt-22222-l-js-custom-payload-formatter.png]] 322 - 323 - 324 324 ==== 3.2.2.6 Downlinks ==== 325 325 326 326 When the LT-22222-L receives a downlink message from the server, the **RX LED** turns on for **1 second**. ... ... @@ -609,11 +609,11 @@ 609 609 610 610 (% style="color:blue" %)**AT+SETCNT=3,60 **(%%)**(Sets AVI1 Count to 60)** 611 611 612 -(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If theAVI1 voltageishigher than VOLMAX (20000mV =20V),thecounter increasesby1)**601 +(% style="color:blue" %)**AT+VOLMAX=20000 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 613 613 614 -(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If theAVI1 voltageislower than VOLMAX (20000mV =20V), counter increasesby1)**603 +(% style="color:blue" %)**AT+VOLMAX=20000,0 **(%%)**(If AVI1 voltage lower than VOLMAX (20000mV =20v), counter increase 1)** 615 615 616 -(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If theAVI1 voltageishigher than VOLMAX (20000mV =20V), counter increasesby1)**605 +(% style="color:blue" %)**AT+VOLMAX=20000,1 **(%%)**(If AVI1 voltage higher than VOLMAX (20000mV =20v), counter increase 1)** 617 617 ))) 618 618 619 619 ... ... @@ -732,9 +732,9 @@ 732 732 733 733 (% style="color:#037691" %)**LoRaWAN Downlink Commands for Setting the Trigger Conditions:** 734 734 735 - **Type Code**: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM**724 +Type Code: 0xAA. Downlink command same as AT Command **AT+AVLIM, AT+ACLIM** 736 736 737 - **Format**: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4726 +Format: AA xx yy1 yy1 yy2 yy2 yy3 yy3 yy4 yy4 738 738 739 739 AA: Type Code for this downlink Command: 740 740 ... ... @@ -801,7 +801,7 @@ 801 801 802 802 **Example:** 803 803 804 -10100000: This means the systemis configuredto use the triggersAV1_LOW and AV2_LOW.793 +10100000: Means the system has configure to use the trigger: AV1_LOW and AV2_LOW 805 805 806 806 807 807 (% style="color:#4f81bd" %)**TRI Status1**(%%) is a combination to show which condition is trigger. Totally 1 byte as below ... ... @@ -830,7 +830,7 @@ 830 830 831 831 **Example:** 832 832 833 -10000000: The uplink is triggered by AV1_LOW,indicatingthatthe voltage is too low.822 +10000000: Means this uplink is triggered by AV1_LOW. That means the voltage is too low. 834 834 835 835 836 836 (% style="color:#4f81bd" %)**TRI_DI FLAG+STA **(%%)is a combination to show which condition is trigger. Totally 1byte as below ... ... @@ -839,22 +839,22 @@ 839 839 |(% 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** 840 840 |(% 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 841 841 842 -* Each bit shows which status has been triggered on this uplink. 831 +* Each bits shows which status has been triggered on this uplink. 843 843 844 844 **Example:** 845 845 846 -00000111: This means both DI1 and DI2 triggersare enabled,and this packet is trigger by DI1.835 +00000111: Means both DI1 and DI2 trigger are enabled and this packet is trigger by DI1. 847 847 848 -00000101: This means both DI1 and DI2 triggersare enabled.837 +00000101: Means both DI1 and DI2 trigger are enabled. 849 849 850 850 851 -(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable d. 0x00: MOD6 is disabled.840 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enable. 0x00: MOD6 is disable. 852 852 853 -Downlink command to poll /requestMOD6 status:842 +Downlink command to poll MOD6 status: 854 854 855 855 **AB 06** 856 856 857 -When device receivesthis command, it will send the MOD6 payload.846 +When device got this command, it will send the MOD6 payload. 858 858 859 859 860 860 === 3.3.7 Payload Decoder === ... ... @@ -978,13 +978,13 @@ 978 978 Sets the device to working mode 2 (Double DI Counting + DO + RO) 979 979 ))) 980 980 981 -==== 3.4.2.3 Requestan uplinkfrom the device====970 +==== 3.4.2.3 Poll an uplink ==== 982 982 983 -Requests an uplink from LT-22222-L. The content of the uplink payload varies based on the device's current working mode.972 +Requests an uplink from LT-22222-L. 984 984 985 985 (% style="color:#037691" %)**AT command** 986 986 987 -There is no AT Command available forthisfeature.976 +There is no AT Command to request an uplink from LT-22222-L 988 988 989 989 (% style="color:#037691" %)**Downlink payload** 990 990 ... ... @@ -992,7 +992,7 @@ 992 992 |(% style="width:101px" %)**Payload**|(% style="width:397px" %)<prefix>FF 993 993 |(% style="width:101px" %)**Parameters**|(% style="width:397px" %)**prefix** : 0x08 994 994 |(% style="width:101px" %)**Example**|(% style="width:397px" %)((( 995 -08 **FF**984 +08 FF 996 996 997 997 Requests an uplink from LT-22222-L. 998 998 ))) ... ... @@ -1026,7 +1026,7 @@ 1026 1026 |(% style="width:97px" %)**Parameters**|(% style="width:401px" %)((( 1027 1027 **prefix** : 0x0A 06 (two bytes in hexadecimal) 1028 1028 1029 -** enable/disable trigger_mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.1018 +**working mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal. 1030 1030 ))) 1031 1031 |(% style="width:97px" %)**Example**|(% style="width:401px" %)((( 1032 1032 0A 06 **01** ... ... @@ -1034,13 +1034,13 @@ 1034 1034 Enable trigger mode for the current working mode 1035 1035 ))) 1036 1036 1037 -==== 3.4.2.5 Requesttrigger settings ====1026 +==== 3.4.2.5 Poll trigger settings ==== 1038 1038 1039 - Requeststhe trigger settings.1028 +Polls the trigger settings. 1040 1040 1041 1041 (% style="color:#037691" %)**AT Command:** 1042 1042 1043 -There is no AT Command availablefor this feature.1032 +There is no AT Command for this feature. 1044 1044 1045 1045 (% style="color:#037691" %)**Downlink Payload** 1046 1046 ... ... @@ -1343,11 +1343,11 @@ 1343 1343 ((( 1344 1344 01: Low, 00: High, 11: No action 1345 1345 1346 -(% border="1" cellspacing=" 3" style="background-color:#f2f2f2; width:383px" %)1347 -|(% style="background-color:#4f81bd; color:white ; width:126px" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white; width:85px" %)**DO1**|(% style="background-color:#4f81bd; color:white; width:86px" %)**DO2**|(% style="background-color:#4f81bd; color:white; width:86px" %)**DO3**1348 -| (% style="width:126px" %)02 01 00 11|(% style="width:85px" %)Low|(% style="width:86px" %)High|(% style="width:86px" %)No Action1349 -| (% style="width:126px" %)02 00 11 01|(% style="width:85px" %)High|(% style="width:86px" %)No Action|(% style="width:86px" %)Low1350 -| (% style="width:126px" %)02 11 01 00|(% style="width:85px" %)No Action|(% style="width:86px" %)Low|(% style="width:86px" %)High1335 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 1336 +|(% style="background-color:#4f81bd; color:white" %)**Downlink Code**|(% style="background-color:#4f81bd; color:white" %)**DO1**|(% style="background-color:#4f81bd; color:white" %)**DO2**|(% style="background-color:#4f81bd; color:white" %)**DO3** 1337 +|02 01 00 11|Low|High|No Action 1338 +|02 00 11 01|High|No Action|Low 1339 +|02 11 01 00|No Action|Low|High 1351 1351 ))) 1352 1352 1353 1353 ((( ... ... @@ -1366,23 +1366,25 @@ 1366 1366 1367 1367 * (% style="color:#037691" %)**AT Command** 1368 1368 1369 -There is no AT command to controlthe digitaloutput.1358 +There is no AT Command to control Digital Output 1370 1370 1371 1371 1372 1372 * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)** 1373 1373 1374 -(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Set sDO1/DO2/DO3 outputswith time control1363 +(% style="color:blue" %)**0xA9 aa bb cc **(%%) ~/~/ Set DO1/DO2/DO3 output with time control 1375 1375 1365 + 1376 1376 This is to control the digital output time of DO pin. Include four bytes: 1377 1377 1378 -(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)1368 +(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9) 1379 1379 1380 -(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode1370 +(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode 1381 1381 1382 -**01:** DO pins revert to their original state after the timeout. 1383 -**00:** DO pins switch to an inverted state after the timeout. 1372 +01: DO pins will change back to original state after timeout. 1384 1384 1374 +00: DO pins will change to an inverter state after timeout 1385 1385 1376 + 1386 1386 (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status: 1387 1387 1388 1388 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) ... ... @@ -1391,7 +1391,7 @@ 1391 1391 |0x00|DO1 set to high 1392 1392 |0x11|DO1 NO Action 1393 1393 1394 -(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:1385 +(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status: 1395 1395 1396 1396 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1397 1397 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1399,7 +1399,7 @@ 1399 1399 |0x00|DO2 set to high 1400 1400 |0x11|DO2 NO Action 1401 1401 1402 -(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:1393 +(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status: 1403 1403 1404 1404 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %) 1405 1405 |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status** ... ... @@ -1407,7 +1407,7 @@ 1407 1407 |0x00|DO3 set to high 1408 1408 |0x11|DO3 NO Action 1409 1409 1410 -(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms)1401 +(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms) 1411 1411 1412 1412 1413 1413 (% style="color:red" %)**Note: ** ... ... @@ -1416,7 +1416,7 @@ 1416 1416 1417 1417 Before firmware v1.6.0, the latch time only supported 2 bytes. 1418 1418 1419 -(% style="color:red" %)** Thedevice will uplinka packet if the downlink code executes successfully.**1410 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.** 1420 1420 1421 1421 1422 1422 **Example payload:** ... ... @@ -1443,16 +1443,16 @@ 1443 1443 1444 1444 * (% style="color:#037691" %)**AT Command:** 1445 1445 1446 -There is no AT Command to control theRelay Output1437 +There is no AT Command to control Relay Output 1447 1447 1448 1448 1449 1449 * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):** 1450 1450 1451 -(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set sRO1/RO2 output1442 +(% style="color:blue" %)**0x03 aa bb ** (%%)~/~/ Set RO1/RO2 output 1452 1452 1453 1453 1454 1454 ((( 1455 -If thepayload is 0x030100, it means setting RO1 to close and RO2 to open.1446 +If payload is 0x030100, it means setting RO1 to close and RO2 to open. 1456 1456 ))) 1457 1457 1458 1458 ((( ... ... @@ -1470,7 +1470,7 @@ 1470 1470 |03 00 01|Open|Close 1471 1471 ))) 1472 1472 1473 -(% style="color:red" %)** Thedevice will uplinka packet ifthedownlink code executes successfully.**1464 +(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.** 1474 1474 1475 1475 1476 1476 ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ==== ... ... @@ -1479,19 +1479,19 @@ 1479 1479 1480 1480 * (% style="color:#037691" %)**AT Command:** 1481 1481 1482 -There is no AT Command to control theRelay Output1473 +There is no AT Command to control Relay Output 1483 1483 1484 1484 1485 1485 * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):** 1486 1486 1487 -(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set sRO1/RO2 relayswith time control1478 +(% style="color:blue" %)**0x05 aa bb cc dd ** (%%)~/~/ Set RO1/RO2 relay with time control 1488 1488 1489 1489 1490 -This control sthe relay output timeandincludes4bytes:1481 +This is to control the relay output time. It includes four bytes: 1491 1491 1492 -(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)1483 +(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05) 1493 1493 1494 -(% style="color:#4f81bd" %)**Second byte1485 +(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode 1495 1495 1496 1496 01: Relays will change back to their original state after timeout. 1497 1497 ... ... @@ -1498,12 +1498,12 @@ 1498 1498 00: Relays will change to the inverter state after timeout. 1499 1499 1500 1500 1501 -(% style="color:#4f81bd" %)**Third byte1492 +(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status: 1502 1502 1503 1503 [[image:image-20221008095908-1.png||height="364" width="564"]] 1504 1504 1505 1505 1506 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes1497 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms 1507 1507 1508 1508 1509 1509 (% style="color:red" %)**Note:** ... ... @@ -1513,7 +1513,7 @@ 1513 1513 Before firmware v1.6.0, the latch time only supported 2 bytes. 1514 1514 1515 1515 1516 -(% style="color:red" %)** Thedevice will uplinka packet if the downlink code executes successfully.**1507 +(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.** 1517 1517 1518 1518 1519 1519 **Example payload:** ... ... @@ -1541,10 +1541,17 @@ 1541 1541 1542 1542 When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]] 1543 1543 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 + 1544 1544 (% style="color:#037691" %)**AT Command** 1545 1545 1546 1546 (% border="2" style="width:500px" %) 1547 -|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage> ,<logic>1545 +|(% style="width:137px" %)**Command**|(% style="width:361px" %)AT+VOLMAX=<voltage><logic> 1548 1548 |(% style="width:137px" %)**Response**|(% style="width:361px" %) 1549 1549 |(% style="width:137px" %)**Parameters**|(% style="width:361px" %)((( 1550 1550 **voltage** : voltage threshold in mV ... ... @@ -1551,9 +1551,9 @@ 1551 1551 1552 1552 **logic**: 1553 1553 1554 - **0**: lower than1552 +0 : lower than 1555 1555 1556 - **1**: higher than1554 +1: higher than 1557 1557 1558 1558 if you leave logic parameter blank, it is considered 0 1559 1559 ))) ... ... @@ -1582,9 +1582,9 @@ 1582 1582 1583 1583 **logic**: (1 byte in hexadecimal) 1584 1584 1585 - **0**: lower than1583 +0 : lower than 1586 1586 1587 - **1**: higher than1585 +1: higher than 1588 1588 1589 1589 if you leave logic parameter blank, it is considered 1 (higher than) 1590 1590 ))) ... ... @@ -1606,10 +1606,22 @@ 1606 1606 1607 1607 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. 1608 1608 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 + 1609 1609 (% style="color:#037691" %)**AT Command** 1610 1610 1611 1611 (% border="2" style="width:500px" %) 1612 -|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter> ,<number>1622 +|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter><number> 1613 1613 |(% style="width:134px" %)**Response**|(% style="width:364px" %) 1614 1614 |(% style="width:134px" %)**Parameters**|(% style="width:364px" %)((( 1615 1615 **counting_parameter** : ... ... @@ -1655,6 +1655,12 @@ 1655 1655 1656 1656 This command clears the counting in counting mode. 1657 1657 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 + 1658 1658 (% style="color:#037691" %)**AT Command** 1659 1659 1660 1660 (% border="2" style="width:500px" %) ... ... @@ -1672,10 +1672,24 @@ 1672 1672 ))) 1673 1673 |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01** 1674 1674 1675 -==== 3.4.2.19 Counting ~-~- Set SavingIntervalfor 'CountingResult'====1691 +==== 3.4.2.19 Counting ~-~- Change counting mode to save time ==== 1676 1676 1677 1677 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. 1678 1678 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 + 1679 1679 (% style="color:#037691" %)**AT Command** 1680 1680 1681 1681 (% border="2" style="width:500px" %) ... ... @@ -1703,12 +1703,22 @@ 1703 1703 Sets the device to save its counting results to the memory every 60 seconds. 1704 1704 ))) 1705 1705 1706 -==== 3.4.2.20 Reset save dROandDO states====1736 +==== 3.4.2.20 Reset save RO DO state ==== 1707 1707 1708 1708 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. 1709 1709 1710 -(% style="color:#037691" %)**AT Command** 1740 +* (% style="color:#037691" %)**AT Command:** 1711 1711 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 + 1712 1712 (% border="2" style="width:500px" %) 1713 1713 |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state> 1714 1714 |(% style="width:127px" %)**Response**|(% style="width:371px" %) ... ... @@ -1729,8 +1729,6 @@ 1729 1729 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. 1730 1730 ))) 1731 1731 1732 -(% style="color:#037691" %)**Downlink Payload** 1733 - 1734 1734 (% border="2" style="width:500px" %) 1735 1735 |(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state> 1736 1736 |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( ... ... @@ -1756,17 +1756,22 @@ 1756 1756 1757 1757 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. 1758 1758 1759 -(% style="color:#037691" %)**AT Command:** 1797 +* (% style="color:#037691" %)**AT Command:** 1760 1760 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 + 1761 1761 (% border="2" style="width:500px" %) 1762 1762 |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state> 1763 1763 |(% style="width:127px" %)**Response**|(% style="width:371px" %) 1764 1764 |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)((( 1765 - **state**:1808 +state : 1766 1766 1767 - **1**: The payload is uploaded without encryption1810 +1 : The payload is uploaded without encryption 1768 1768 1769 - **0**: The payload is encrypted when uploaded (default)1812 +0 : The payload is encrypted when uploaded (default) 1770 1770 ))) 1771 1771 |(% style="width:127px" %)**Example**|(% style="width:371px" %)((( 1772 1772 AT+DECRYPT=1 ... ... @@ -1785,8 +1785,13 @@ 1785 1785 1786 1786 This command allows you to retrieve and optionally uplink sensor readings through the serial port. 1787 1787 1788 -(% style="color:#037691" %)**AT Command** 1831 +* (% style="color:#037691" %)**AT Command:** 1789 1789 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 + 1790 1790 (% border="2" style="width:500px" %) 1791 1791 |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state> 1792 1792 |(% style="width:127px" %)**Response**|(% style="width:371px" %) ... ... @@ -1814,8 +1814,13 @@ 1814 1814 1815 1815 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. 1816 1816 1817 -(% style="color:#037691" %)**AT Command** 1865 +* (% style="color:#037691" %)**AT Command:** 1818 1818 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 + 1819 1819 (% border="2" style="width:500px" %) 1820 1820 |(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state> 1821 1821 |(% style="width:130px" %)**Response**|(% style="width:368px" %)((( ... ... @@ -1847,6 +1847,17 @@ 1847 1847 1848 1848 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. 1849 1849 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 + 1850 1850 (% style="color:#037691" %)**AT Command** 1851 1851 1852 1852 (% border="2" style="width:500px" %) ... ... @@ -1890,13 +1890,13 @@ 1890 1890 1891 1891 ==== 3.4.2.25 Copy downlink to uplink ==== 1892 1892 1893 -This command enables the device to immediately uplink the payloadof a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100.1957 +This command enables the device to immediately uplink the content of a received downlink packet back to the server. The command allows for quick data replication from downlink to uplink, with a fixed port number of 100. 1894 1894 1895 -(% style="color:#037691" %)**AT Command**(%%)**:** 1959 +* (% style="color:#037691" %)**AT Command**(%%)**:** 1896 1896 1897 -(% style="color:blue" %)**AT+RPL=5** (%%) ~/~/ After receiving adownlinkpayloadfrom the server, thedevicewill immediately uplinkthe payload back to the serverusingport number 100.1961 +(% style="color:blue" %)**AT+RPL=5** (%%) ~/~/ After receiving the package from the server, it will immediately upload the content of the package to the server, the port number is 100. 1898 1898 1899 -Example:**aa xx xx xx xx** ~/~/ **aa**indicates whether the configuration has changed: **00** meansYES,and **01** meansNO. **xx xx xx xx**are the bytesuplinked back.1963 +Example:**aa xx xx xx xx** ~/~/ aa indicates whether the configuration has changed, 00 is yes, 01 is no; xx xx xx xx are the bytes sent. 1900 1900 1901 1901 1902 1902 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173747-6.png?width=1124&height=165&rev=1.1||alt="image-20220823173747-6.png"]] ... ... @@ -1903,16 +1903,28 @@ 1903 1903 1904 1904 For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77. 1905 1905 1906 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]] 1970 +(% border="2" style="width:500px" %) 1971 +|(% style="width:122px" %)**Command**|(% style="width:376px" %)((( 1972 +AT+RPL=5 1907 1907 1908 -For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. 1974 +After receiving a downlink packet from the server, the node immediately uplinks the content of the packet back to the server using port number 100. 1975 +))) 1976 +|(% style="width:122px" %)**Example**|(% style="width:376px" %)((( 1977 +Downlink: 1909 1909 1979 +01 00 02 58 1910 1910 1911 - (% style="color:#037691" %)**DownlinkPayload**(%%)**:**1981 +Uplink: 1912 1912 1913 -There is no downlink option available for this feature. 1983 +01 01 00 02 58 1984 +))) 1914 1914 1986 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]] 1915 1915 1988 +For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned. 1989 + 1990 + 1991 + 1916 1916 ==== 3.4.2.26 Query firmware version, frequency band, sub band, and TDC time ==== 1917 1917 1918 1918 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. ... ... @@ -1948,7 +1948,7 @@ 1948 1948 The username and password (API key) you created here are required in the next section. 1949 1949 {{/info}} 1950 1950 1951 -[[image:tts-mqtt-integration.png]] 2027 +[[image:tts-mqtt-integration.png||height="625" width="1000"]] 1952 1952 1953 1953 === 3.5.2 Configuring ThingsEye.io === 1954 1954 ... ... @@ -1958,7 +1958,7 @@ 1958 1958 * Under the **Integrations center**, click **Integrations**. 1959 1959 * Click the **Add integration** button (the button with the **+** symbol). 1960 1960 1961 -[[image:thingseye-io-step-1.png]] 2037 +[[image:thingseye-io-step-1.png||height="625" width="1000"]] 1962 1962 1963 1963 1964 1964 On the **Add integration** window, configure the following: ... ... @@ -1973,7 +1973,7 @@ 1973 1973 ** Allow create devices or assets 1974 1974 * Click the **Next** button. you will be navigated to the **Uplink data converter** tab. 1975 1975 1976 -[[image:thingseye-io-step-2.png]] 2052 +[[image:thingseye-io-step-2.png||height="625" width="1000"]] 1977 1977 1978 1978 1979 1979 **Uplink data converter:** ... ... @@ -1984,7 +1984,7 @@ 1984 1984 * 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]]. 1985 1985 * Click the **Next** button. You will be navigated to the **Downlink data converter **tab. 1986 1986 1987 -[[image:thingseye-io-step-3.png]] 2063 +[[image:thingseye-io-step-3.png||height="625" width="1000"]] 1988 1988 1989 1989 1990 1990 **Downlink data converter (this is an optional step):** ... ... @@ -1995,7 +1995,7 @@ 1995 1995 * 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]]. 1996 1996 * Click the **Next** button. You will be navigated to the **Connection** tab. 1997 1997 1998 -[[image:thingseye-io-step-4.png]] 2074 +[[image:thingseye-io-step-4.png||height="625" width="1000"]] 1999 1999 2000 2000 2001 2001 **Connection:** ... ... @@ -2010,13 +2010,13 @@ 2010 2010 2011 2011 * Click the **Add** button. 2012 2012 2013 -[[image:thingseye-io-step-5.png]] 2089 +[[image:thingseye-io-step-5.png||height="625" width="1000"]] 2014 2014 2015 2015 2016 2016 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. 2017 2017 2018 2018 2019 -[[image:thingseye.io_integrationsCenter_integrations.png]] 2095 +[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]] 2020 2020 2021 2021 2022 2022 ==== 3.5.2.1 Viewing integration details ==== ... ... @@ -2023,7 +2023,7 @@ 2023 2023 2024 2024 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. 2025 2025 2026 -[[image:integration-details.png]] 2102 +[[image:integration-details.png||height="686" width="1000"]] 2027 2027 2028 2028 2029 2029 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. ... ... @@ -2039,12 +2039,12 @@ 2039 2039 * Select **Debug **from the **Event type** dropdown. 2040 2040 * Select the** time frame** from the **time window**. 2041 2041 2042 -[[image:thingseye-events.png]] 2118 +[[image:thingseye-events.png||height="686" width="1000"]] 2043 2043 2044 2044 2045 2045 * To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message. 2046 2046 2047 -[[image:thingseye-json.png]] 2123 +[[image:thingseye-json.png||width="1000"]] 2048 2048 2049 2049 2050 2050 ==== **3.5.2.3 Deleting an integration** ==== ... ... @@ -2062,7 +2062,7 @@ 2062 2062 === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) === 2063 2063 2064 2064 2065 -Supports **NPN-type**sensors.2141 +Supports NPN-type sensors. 2066 2066 2067 2067 [[image:1653356991268-289.png]] 2068 2068 ... ... @@ -2184,15 +2184,15 @@ 2184 2184 ))) 2185 2185 2186 2186 2187 -(% style="color:blue" %)**Example aDry Contact sensor2263 +(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor 2188 2188 2189 -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.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. 2190 2190 2191 -To detect a Dry Contact, you can supply a power source to one of thepinsof the Dry Contact.Areference circuit diagramis shown below.2267 +To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram. 2192 2192 2193 2193 [[image:image-20230616235145-1.png]] 2194 2194 2195 -(% style="color:blue" %)**Example 2271 +(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector 2196 2196 2197 2197 [[image:image-20240219115718-1.png]] 2198 2198 ... ... @@ -2268,7 +2268,7 @@ 2268 2268 [[image:image-20220524100215-10.png||height="382" width="723"]] 2269 2269 2270 2270 2271 -== 3.7 LED Indicators == 2347 +== 3.7 LEDs Indicators == 2272 2272 2273 2273 The table below lists the behavior of LED indicators for each port function. 2274 2274 ... ... @@ -2307,14 +2307,13 @@ 2307 2307 == 4.1 Connecting the LT-22222-L to a PC == 2308 2308 2309 2309 ((( 2310 -You can use a USB-to-TTL adapter /converteralong with a 3.5mm Program Cable to connect the LT-22222-L to a PC, as shown below.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. 2311 2311 2312 -[[image:usb-ttl-audio-jack-connection.jpg]] 2313 - 2314 - 2388 +[[image:usb-ttl-programming.png]] 2315 2315 ))) 2316 2316 2317 2317 2392 + 2318 2318 ((( 2319 2319 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: 2320 2320 ))) ... ... @@ -2344,39 +2344,39 @@ 2344 2344 * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey) 2345 2345 * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI) 2346 2346 * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON) 2347 -* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)2348 -* **##AT+DR##**: Get or set the Data Rate. (0-7 corresponding to DR_X)2349 -* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing2350 -* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)2351 -* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency2352 -* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)2353 -* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms2354 -* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms2355 -* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms2356 -* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms2357 -* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)2358 -* ##**AT+NWKID**##: Get or set the Network ID2359 -* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)2360 -* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)2361 -* ##**AT+CLASS**##: Get or set the Device Class2362 -* ##**AT+JOIN**##: Join network2363 -* ##**AT+NJS**##: Get OTAA Join Status2364 -* ##**AT+SENDB**##: Send hexadecimal data along with the application port2365 -* ##**AT+SEND**##: Send text data along with the application port2366 -* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)2367 -* ##**AT+RECV**##: Print last received data in raw format2368 -* ##**AT+VER**##: Get current image version and Frequency Band2369 -* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)2370 -* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)2371 -* ##**AT+SNR**##: Get the SNR of the last received packet2372 -* ##**AT+RSSI**##: Get the RSSI of the last received packet2373 -* ##**AT+TDC**##: Get or set the application data transmission interval in ms2374 -* ##**AT+PORT**##: Get or set the application port2375 -* ##**AT+DISAT**##: Disable AT commands2376 -* ##**AT+PWORD**##: Set password, max 9 digits2377 -* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode2378 -* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN4702379 -* ##**AT+CFG**##: Print all settings2422 +* 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 2380 2380 ))) 2381 2381 2382 2382 ... ... @@ -2541,7 +2541,7 @@ 2541 2541 You will need the following things before proceeding: 2542 2542 2543 2543 * 3.5mm programming cable (included with the LT-22222-L as an additional accessory) 2544 -* USB to TTL adapter /converter2619 +* USB to TTL adapter 2545 2545 * 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) 2546 2546 * 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. 2547 2547 ... ... @@ -2551,7 +2551,7 @@ 2551 2551 2552 2552 Below is the hardware setup for uploading a firmware image to the LT-22222-L: 2553 2553 2554 -[[image:usb-ttl- audio-jack-connection.jpg]]2629 +[[image:usb-ttl-programming.png]] 2555 2555 2556 2556 2557 2557
- lt-22222-l-joining.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -301.9 KB - Content
- lt-22222-l-js-custom-payload-formatter.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -453.9 KB - Content
- lt33222-l.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.3 KB - Content
- usb-ttl-audio-jack-connection.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.pradeeka - Size
-
... ... @@ -1,1 +1,0 @@ 1 -394.4 KB - Content