Skip to Content
Last modified by Mengting Qiu on 2025/06/04 18:42
From version 212.1
edited by Dilisi S
on 2024/11/24 01:31
Change comment: Fix uplink interval in dl payload
To version 223.1
edited by Dilisi S
on 2024/11/26 05:20
Change comment: Nov 25 edits

Summary

Details

Page properties
Content
... ... @@ -116,13 +116,13 @@
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
119 +(% style="width:650px" %)
120 +|(% style="width:94px" %)**Model**|(% style="width:172px" %)**Photo**|(% style="width:256px" %)**Description**
121 +|(% style="width:94px" %)**LT-33222-L**|(% style="width:172px" %)(((
122 +[[image:lt33222-l.jpg]]
123 +)))|(% style="width:256px" %)(((
124 +* 3 x Digital Input (Bi-direction)
125 +* 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"]]
240 +[[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"]]
250 +[[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"]]
264 +[[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"]]
275 +[[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"]]
281 +[[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"]]
291 +[[image:lt-22222-l-joining.png]]
292 292  
293 293  
294 +
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"]]
311 +[[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 =20v), counter increase 1)**
602 +(% 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 =20v), counter increase 1)**
604 +(% 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 =20v), counter increase 1)**
606 +(% 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**
725 +**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
727 +**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 system has configure to use the trigger: AV1_LOW and AV2_LOW
794 +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: Means this uplink is triggered by AV1_LOW. That means the voltage is too low.
823 +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 bits shows which status has been triggered on this uplink.
832 +* 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.
836 +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.
838 +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.
841 +(% style="color:#4f81bd" %)**Enable/Disable MOD6 **(%%): 0x01: MOD6 is enabled. 0x00: MOD6 is disabled.
841 841  
842 -Downlink command to poll MOD6 status:
843 +Downlink command to poll/request MOD6 status:
843 843  
844 844  **AB 06**
845 845  
846 -When device got this command, it will send the MOD6 payload.
847 +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 Poll an uplink ====
971 +==== 3.4.2.3 Request an uplink from the device ====
971 971  
972 -Requests an uplink from LT-22222-L.
973 +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 to request an uplink from LT-22222-L
977 +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
985 +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 -**working mode** : enable (1) or disable (0), represented by 1 byte in hexadecimal.
1019 +**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 Poll trigger settings ====
1027 +==== 3.4.2.5 Request trigger settings ====
1027 1027  
1028 -Polls the trigger settings.
1029 +Requests the trigger settings.
1029 1029  
1030 1030  (% style="color:#037691" %)**AT Command:**
1031 1031  
1032 -There is no AT Command for this feature.
1033 +There is no AT Command available for this feature.
1033 1033  
1034 1034  (% style="color:#037691" %)**Downlink Payload**
1035 1035  
... ... @@ -1169,7 +1169,6 @@
1169 1169  )))
1170 1170  |(% style="width:96px" %)**Example**|(% style="width:402px" %)09 02 **00 00 64**
1171 1171  
1172 -
1173 1173  ==== 3.4.2.9 Trigger – Set AC (current) as a trigger ====
1174 1174  
1175 1175  Sets the current trigger based on the AC port. See also [[trigger mode>>||anchor="H3.3.6AT2BADDMOD3D6.28TriggerMode2COptional29"]]
... ... @@ -1351,31 +1351,28 @@
1351 1351  )))
1352 1352  )))
1353 1353  
1354 -
1355 1355  ==== 3.4.2.13 DO ~-~- Control Digital Output DO1/DO2/DO3 with time control ====
1356 1356  
1357 1357  
1358 1358  * (% style="color:#037691" %)**AT Command**
1359 1359  
1360 -There is no AT Command to control Digital Output
1359 +There is no AT command to control the digital output.
1361 1361  
1362 1362  
1363 1363  * (% style="color:#037691" %)**Downlink Payload (prefix 0xA9)**
1364 1364  
1365 -(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Set DO1/DO2/DO3 output with time control
1364 +(% style="color:blue" %)**0xA9 aa bb cc     **(%%) ~/~/ Sets DO1/DO2/DO3 outputs with time control
1366 1366  
1367 -
1368 1368  This is to control the digital output time of DO pin. Include four bytes:
1369 1369  
1370 -(% style="color:#4f81bd" %)**First Byte**(%%)**:** Type code (0xA9)
1368 +(% style="color:#4f81bd" %)**First byte**(%%)**:** Type code (0xA9)
1371 1371  
1372 -(% style="color:#4f81bd" %)**Second Byte**(%%): Inverter Mode
1370 +(% style="color:#4f81bd" %)**Second byte**(%%): Inverter Mode
1373 1373  
1374 -01: DO pins will change back to original state after timeout.
1372 +**01:** DO pins revert to their original state after the timeout.
1373 +**00:** DO pins switch to an inverted state after the timeout.
1375 1375  
1376 -00: DO pins will change to an inverter state after timeout 
1377 1377  
1378 -
1379 1379  (% style="color:#4f81bd" %)**Third Byte**(%%): Control Method and Port status:
1380 1380  
1381 1381  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
... ... @@ -1384,7 +1384,7 @@
1384 1384  |0x00|DO1 set to high
1385 1385  |0x11|DO1 NO Action
1386 1386  
1387 -(% style="color:#4f81bd" %)**Fourth Byte**(%%): Control Method and Port status:
1384 +(% style="color:#4f81bd" %)**Fourth byte**(%%): Control Method and Port status:
1388 1388  
1389 1389  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1390 1390  |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
... ... @@ -1392,7 +1392,7 @@
1392 1392  |0x00|DO2 set to high
1393 1393  |0x11|DO2 NO Action
1394 1394  
1395 -(% style="color:#4f81bd" %)**Fifth Byte**(%%): Control Method and Port status:
1392 +(% style="color:#4f81bd" %)**Fifth byte**(%%): Control Method and Port status:
1396 1396  
1397 1397  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:300px" %)
1398 1398  |(% style="background-color:#4f81bd; color:white" %)**Second Byte**|(% style="background-color:#4f81bd; color:white" %)**Status**
... ... @@ -1400,7 +1400,7 @@
1400 1400  |0x00|DO3 set to high
1401 1401  |0x11|DO3 NO Action
1402 1402  
1403 -(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth Bytes**:(%%) Latching time (Unit: ms)
1400 +(% style="color:#4f81bd" %)**Sixth, Seventh, Eighth, and Ninth bytes**:(%%) Latching time (Unit: ms)
1404 1404  
1405 1405  
1406 1406  (% style="color:red" %)**Note: **
... ... @@ -1409,7 +1409,7 @@
1409 1409  
1410 1410   Before firmware v1.6.0, the latch time only supported 2 bytes.
1411 1411  
1412 -(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1409 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1413 1413  
1414 1414  
1415 1415  **Example payload:**
... ... @@ -1436,16 +1436,16 @@
1436 1436  
1437 1437  * (% style="color:#037691" %)**AT Command:**
1438 1438  
1439 -There is no AT Command to control Relay Output
1436 +There is no AT Command to control the Relay Output
1440 1440  
1441 1441  
1442 1442  * (% style="color:#037691" %)**Downlink Payload (prefix 0x03):**
1443 1443  
1444 -(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Set RO1/RO2 output
1441 +(% style="color:blue" %)**0x03 aa bb     ** (%%)~/~/ Sets RO1/RO2 output
1445 1445  
1446 1446  
1447 1447  (((
1448 -If payload is 0x030100, it means setting RO1 to close and RO2 to open.
1445 +If the payload is 0x030100, it means setting RO1 to close and RO2 to open.
1449 1449  )))
1450 1450  
1451 1451  (((
... ... @@ -1463,7 +1463,7 @@
1463 1463  |03  00  01|Open|Close
1464 1464  )))
1465 1465  
1466 -(% style="color:red" %)**Device will upload a packet if downlink code executes successfully.**
1463 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1467 1467  
1468 1468  
1469 1469  ==== 3.4.2.15 Relay ~-~- Control Relay Output RO1/RO2 with time control ====
... ... @@ -1472,19 +1472,19 @@
1472 1472  
1473 1473  * (% style="color:#037691" %)**AT Command:**
1474 1474  
1475 -There is no AT Command to control Relay Output
1472 +There is no AT Command to control the Relay Output
1476 1476  
1477 1477  
1478 1478  * (% style="color:#037691" %)**Downlink Payload (prefix 0x05):**
1479 1479  
1480 -(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Set RO1/RO2 relay with time control
1477 +(% style="color:blue" %)**0x05 aa bb cc dd     ** (%%)~/~/ Sets RO1/RO2 relays with time control
1481 1481  
1482 1482  
1483 -This is to control the relay output time. It includes four bytes:
1480 +This controls the relay output time and includes 4 bytes:
1484 1484  
1485 -(% style="color:#4f81bd" %)**First Byte **(%%)**:** Type code (0x05)
1482 +(% style="color:#4f81bd" %)**First byte **(%%)**:** Type code (0x05)
1486 1486  
1487 -(% style="color:#4f81bd" %)**Second Byte(aa)**(%%): Inverter Mode
1484 +(% style="color:#4f81bd" %)**Second byte (aa)**(%%): Inverter Mode
1488 1488  
1489 1489  01: Relays will change back to their original state after timeout.
1490 1490  
... ... @@ -1491,12 +1491,12 @@
1491 1491  00: Relays will change to the inverter state after timeout.
1492 1492  
1493 1493  
1494 -(% style="color:#4f81bd" %)**Third Byte(bb)**(%%): Control Method and Ports status:
1491 +(% style="color:#4f81bd" %)**Third byte (bb)**(%%): Control Method and Ports status:
1495 1495  
1496 1496  [[image:image-20221008095908-1.png||height="364" width="564"]]
1497 1497  
1498 1498  
1499 -(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh Bytes(cc)**(%%): Latching time. Unit: ms
1496 +(% style="color:#4f81bd" %)**Fourth/Fifth/Sixth/Seventh bytes (cc)**(%%): Latching time. Unit: ms
1500 1500  
1501 1501  
1502 1502  (% style="color:red" %)**Note:**
... ... @@ -1506,7 +1506,7 @@
1506 1506   Before firmware v1.6.0, the latch time only supported 2 bytes.
1507 1507  
1508 1508  
1509 -(% style="color:red" %)**Device will upload a packet if the downlink code executes successfully.**
1506 +(% style="color:red" %)**The device will uplink a packet if the downlink code executes successfully.**
1510 1510  
1511 1511  
1512 1512  **Example payload:**
... ... @@ -1534,17 +1534,10 @@
1534 1534  
1535 1535  When the voltage exceeds the threshold, counting begins. For details, see [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
1536 1536  
1537 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+VOLMAX   ** (%%)~/~/ See [[MOD4>>||anchor="H3.3.4AT2BMOD3D42CSingleDICounting2B1xVoltageCounting"]]
1538 -
1539 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA5):**
1540 -
1541 -(% style="color:blue" %)**0xA5 aa bb cc   ** (%%)~/~/ Same as AT+VOLMAX=(aa bb),cc
1542 -
1543 -
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>
1537 +|(% 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 than
1544 +**0** : lower than
1555 1555  
1556 -1: higher than
1546 +**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 than
1575 +**0** : lower than
1586 1586  
1587 -1: higher than
1577 +**1**: higher than
1588 1588  
1589 1589  if you leave logic parameter blank, it is considered 1 (higher than)
1590 1590  )))
... ... @@ -1606,22 +1606,10 @@
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  
1609 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+SETCNT=aa,(bb cc dd ee) **
1610 -
1611 -(% style="color:red" %)**aa:**(%%) 1: Set count1; 2: Set count2; 3: Set AV1 count
1612 -
1613 -(% style="color:red" %)**bb cc dd ee: **(%%)The number to be set
1614 -
1615 -
1616 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA8):**
1617 -
1618 -(% style="color:blue" %)**0x A8 aa bb cc dd ee     ** (%%)~/~/ same as AT+SETCNT=aa,(bb cc dd ee)
1619 -
1620 -
1621 1621  (% style="color:#037691" %)**AT Command**
1622 1622  
1623 1623  (% border="2" style="width:500px" %)
1624 -|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter><number>
1602 +|(% style="width:134px" %)**Command**|(% style="width:364px" %)AT+SETCNT=<counting_parameter>,<number>
1625 1625  |(% style="width:134px" %)**Response**|(% style="width:364px" %)
1626 1626  |(% style="width:134px" %)**Parameters**|(% style="width:364px" %)(((
1627 1627  **counting_parameter** :
... ... @@ -1667,12 +1667,6 @@
1667 1667  
1668 1668  This command clears the counting in counting mode.
1669 1669  
1670 -* (% style="color:#037691" %)**AT Command:**(%%) (% style="color:blue" %)**AT+CLRCOUNT         **(%%) ~/~/ clear all counting
1671 -
1672 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA6):**
1673 -
1674 -(% style="color:blue" %)**0x A6 01    ** (%%)~/~/ clear all counting
1675 -
1676 1676  (% style="color:#037691" %)**AT Command**
1677 1677  
1678 1678  (% border="2" style="width:500px" %)
... ... @@ -1690,24 +1690,10 @@
1690 1690  )))
1691 1691  |(% style="width:141px" %)**Example**|(% style="width:357px" %)A6 **01**
1692 1692  
1693 -==== 3.4.2.19 Counting ~-~- Change counting mode to save time ====
1665 +==== 3.4.2.19 Counting ~-~- Set Saving Interval for 'Counting Result' ====
1694 1694  
1695 1695  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.
1696 1696  
1697 -* (% style="color:#037691" %)**AT Command:**
1698 -
1699 -(% 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)
1700 -
1701 -
1702 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xA7):**
1703 -
1704 -(% style="color:blue" %)**0x A7 aa bb cc     ** (%%)~/~/ same as AT+COUTIME =aa bb cc,
1705 -
1706 -(((
1707 -Range: aa bb cc:0 to 16777215,  (unit: seconds)
1708 -)))
1709 -
1710 -
1711 1711  (% style="color:#037691" %)**AT Command**
1712 1712  
1713 1713  (% border="2" style="width:500px" %)
... ... @@ -1735,22 +1735,12 @@
1735 1735  Sets the device to save its counting results to the memory every 60 seconds.
1736 1736  )))
1737 1737  
1738 -==== 3.4.2.20 Reset save RO DO state ====
1696 +==== 3.4.2.20 Reset saved RO and DO states ====
1739 1739  
1740 1740  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.
1741 1741  
1742 -* (% style="color:#037691" %)**AT Command:**
1700 +(% style="color:#037691" %)**AT Command**
1743 1743  
1744 -(% style="color:blue" %)**AT+RODORESET=1    **(%%)~/~/ RODO will close when the device joining the network. (default)
1745 -
1746 -(% 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.
1747 -
1748 -
1749 -* (% style="color:#037691" %)**Downlink Payload (prefix 0xAD):**
1750 -
1751 -(% style="color:blue" %)**0x AD aa      ** (%%)~/~/ same as AT+RODORET =aa
1752 -
1753 -
1754 1754  (% border="2" style="width:500px" %)
1755 1755  |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+RODORESET=<state>
1756 1756  |(% style="width:127px" %)**Response**|(% style="width:371px" %)
... ... @@ -1771,6 +1771,8 @@
1771 1771  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.
1772 1772  )))
1773 1773  
1722 +(% style="color:#037691" %)**Downlink Payload**
1723 +
1774 1774  (% border="2" style="width:500px" %)
1775 1775  |(% style="width:127px" %)**Payload**|(% style="width:371px" %)<prefix><state>
1776 1776  |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
... ... @@ -1796,22 +1796,17 @@
1796 1796  
1797 1797  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.
1798 1798  
1799 -* (% style="color:#037691" %)**AT Command:**
1749 +(% style="color:#037691" %)**AT Command:**
1800 1800  
1801 -(% style="color:blue" %)**AT+DECRYPT=1  ** (%%)~/~/ The payload is uploaded without encryption
1802 -
1803 -(% style="color:blue" %)**AT+DECRYPT=0    **(%%)~/~/  Encrypt when uploading payload (default)
1804 -
1805 -
1806 1806  (% border="2" style="width:500px" %)
1807 1807  |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+DECRYPT=<state>
1808 1808  |(% style="width:127px" %)**Response**|(% style="width:371px" %)
1809 1809  |(% style="width:127px" %)**Parameters**|(% style="width:371px" %)(((
1810 -state :
1755 +**state** :
1811 1811  
1812 -1 : The payload is uploaded without encryption
1757 +**1** : The payload is uploaded without encryption
1813 1813  
1814 -0 : The payload is encrypted when uploaded (default)
1759 +**0** : The payload is encrypted when uploaded (default)
1815 1815  )))
1816 1816  |(% style="width:127px" %)**Example**|(% style="width:371px" %)(((
1817 1817  AT+DECRYPT=1
... ... @@ -1830,13 +1830,8 @@
1830 1830  
1831 1831  This command allows you to retrieve and optionally uplink sensor readings through the serial port.
1832 1832  
1833 -* (% style="color:#037691" %)**AT Command:**
1778 +(% style="color:#037691" %)**AT Command**
1834 1834  
1835 -(% style="color:blue" %)**AT+GETSENSORVALUE=0    **(%%)~/~/ The serial port retrieves the reading of the current sensor.
1836 -
1837 -(% style="color:blue" %)**AT+GETSENSORVALUE=1    **(%%)~/~/ The serial port retrieves the current sensor reading and uploads it.
1838 -
1839 -
1840 1840  (% border="2" style="width:500px" %)
1841 1841  |(% style="width:127px" %)**Command**|(% style="width:371px" %)AT+GETSENSORVALUE=<state>
1842 1842  |(% style="width:127px" %)**Response**|(% style="width:371px" %)
... ... @@ -1864,13 +1864,8 @@
1864 1864  
1865 1865  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.
1866 1866  
1867 -* (% style="color:#037691" %)**AT Command:**
1807 +(% style="color:#037691" %)**AT Command**
1868 1868  
1869 -(% 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)
1870 -
1871 -(% 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.
1872 -
1873 -
1874 1874  (% border="2" style="width:500px" %)
1875 1875  |(% style="width:130px" %)**Command**|(% style="width:368px" %)AT+DISFCNTCHECK=<state>
1876 1876  |(% style="width:130px" %)**Response**|(% style="width:368px" %)(((
... ... @@ -1902,17 +1902,6 @@
1902 1902  
1903 1903  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.
1904 1904  
1905 -* (% style="color:#037691" %)**AT Command:**
1906 -
1907 -(% 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)
1908 -
1909 -(% 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.
1910 -
1911 -
1912 -* (% style="color:#037691" %)**Downlink Payload **(%%)**:**
1913 -
1914 -(% style="color:blue" %)**0x21 00 01 ** (%%) ~/~/ Set  the DISMACANS=1
1915 -
1916 1916  (% style="color:#037691" %)**AT Command**
1917 1917  
1918 1918  (% border="2" style="width:500px" %)
... ... @@ -2026,7 +2026,7 @@
2026 2026  The username and  password (API key) you created here are required in the next section.
2027 2027  {{/info}}
2028 2028  
2029 -[[image:tts-mqtt-integration.png||height="625" width="1000"]]
1953 +[[image:tts-mqtt-integration.png]]
2030 2030  
2031 2031  === 3.5.2 Configuring ThingsEye.io ===
2032 2032  
... ... @@ -2036,7 +2036,7 @@
2036 2036  * Under the **Integrations center**, click **Integrations**.
2037 2037  * Click the **Add integration** button (the button with the **+** symbol).
2038 2038  
2039 -[[image:thingseye-io-step-1.png||height="625" width="1000"]]
1963 +[[image:thingseye-io-step-1.png]]
2040 2040  
2041 2041  
2042 2042  On the **Add integration** window, configure the following:
... ... @@ -2051,7 +2051,7 @@
2051 2051  ** Allow create devices or assets
2052 2052  * Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
2053 2053  
2054 -[[image:thingseye-io-step-2.png||height="625" width="1000"]]
1978 +[[image:thingseye-io-step-2.png]]
2055 2055  
2056 2056  
2057 2057  **Uplink data converter:**
... ... @@ -2062,7 +2062,7 @@
2062 2062  * 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]].
2063 2063  * Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
2064 2064  
2065 -[[image:thingseye-io-step-3.png||height="625" width="1000"]]
1989 +[[image:thingseye-io-step-3.png]]
2066 2066  
2067 2067  
2068 2068  **Downlink data converter (this is an optional step):**
... ... @@ -2073,7 +2073,7 @@
2073 2073  * 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]].
2074 2074  * Click the **Next** button. You will be navigated to the **Connection** tab.
2075 2075  
2076 -[[image:thingseye-io-step-4.png||height="625" width="1000"]]
2000 +[[image:thingseye-io-step-4.png]]
2077 2077  
2078 2078  
2079 2079  **Connection:**
... ... @@ -2088,13 +2088,13 @@
2088 2088  
2089 2089  * Click the **Add** button.
2090 2090  
2091 -[[image:thingseye-io-step-5.png||height="625" width="1000"]]
2015 +[[image:thingseye-io-step-5.png]]
2092 2092  
2093 2093  
2094 2094  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.
2095 2095  
2096 2096  
2097 -[[image:thingseye.io_integrationsCenter_integrations.png||height="686" width="1000"]]
2021 +[[image:thingseye.io_integrationsCenter_integrations.png]]
2098 2098  
2099 2099  
2100 2100  ==== 3.5.2.1 Viewing integration details ====
... ... @@ -2101,7 +2101,7 @@
2101 2101  
2102 2102  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.
2103 2103  
2104 -[[image:integration-details.png||height="686" width="1000"]]
2028 +[[image:integration-details.png]]
2105 2105  
2106 2106  
2107 2107  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.
... ... @@ -2117,12 +2117,12 @@
2117 2117  * Select **Debug **from the **Event type** dropdown.
2118 2118  * Select the** time frame** from the **time window**.
2119 2119  
2120 -[[image:thingseye-events.png||height="686" width="1000"]]
2044 +[[image:thingseye-events.png]]
2121 2121  
2122 2122  
2123 2123  * To view the **JSON payload** of a message, click on the **three dots (...)** in the Message column of the desired message.
2124 2124  
2125 -[[image:thingseye-json.png||width="1000"]]
2049 +[[image:thingseye-json.png]]
2126 2126  
2127 2127  
2128 2128  ==== **3.5.2.3 Deleting an integration** ====
... ... @@ -2140,7 +2140,7 @@
2140 2140  === 3.6.1 Digital Input Ports: DI1/DI2/DI3 (For LT-33222-L, Low Active) ===
2141 2141  
2142 2142  
2143 -Supports NPN-type sensors.
2067 +Supports** NPN-type **sensors.
2144 2144  
2145 2145  [[image:1653356991268-289.png]]
2146 2146  
... ... @@ -2262,15 +2262,15 @@
2262 2262  )))
2263 2263  
2264 2264  
2265 -(% style="color:blue" %)**Example4**(%%): Connecting to Dry Contact sensor
2189 +(% style="color:blue" %)**Example 4**(%%): Connecting to a Dry Contact sensor
2266 2266  
2267 -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.
2191 +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.
2268 2268  
2269 -To detect a Dry Contact, you can supply a power source to one pin of the Dry Contact. Below is a reference circuit diagram.
2193 +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.
2270 2270  
2271 2271  [[image:image-20230616235145-1.png]]
2272 2272  
2273 -(% style="color:blue" %)**Example5**(%%): Connecting to an Open Collector
2197 +(% style="color:blue" %)**Example 5**(%%): Connecting to an Open Collector
2274 2274  
2275 2275  [[image:image-20240219115718-1.png]]
2276 2276  
... ... @@ -2346,7 +2346,7 @@
2346 2346  [[image:image-20220524100215-10.png||height="382" width="723"]]
2347 2347  
2348 2348  
2349 -== 3.7 LEDs Indicators ==
2273 +== 3.7 LED Indicators ==
2350 2350  
2351 2351  The table below lists the behavior of LED indicators for each port function.
2352 2352  
... ... @@ -2385,13 +2385,14 @@
2385 2385  == 4.1 Connecting the LT-22222-L to a PC ==
2386 2386  
2387 2387  (((
2388 -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.
2312 +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.
2389 2389  
2390 -[[image:usb-ttl-programming.png]]
2314 +[[image:usb-ttl-audio-jack-connection.jpg]]
2315 +
2316 +
2391 2391  )))
2392 2392  
2393 2393  
2394 -
2395 2395  (((
2396 2396  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:
2397 2397  )))
... ... @@ -2421,39 +2421,39 @@
2421 2421  * **##AT+APPSKEY##**: Get or set the Application Session Key (AppSKey)
2422 2422  * **##AT+APPEUI##**: Get or set the Application EUI (AppEUI)
2423 2423  * **##AT+ADR##**: Get or set the Adaptive Data Rate setting. (0: OFF, 1: ON)
2424 -* AT+TXP: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2425 -* AT+DR:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
2426 -* AT+DCS: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2427 -* AT+PNM: Get or set the public network mode. (0: off, 1: on)
2428 -* AT+RX2FQ: Get or set the Rx2 window frequency
2429 -* AT+RX2DR: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2430 -* AT+RX1DL: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2431 -* AT+RX2DL: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2432 -* AT+JN1DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2433 -* AT+JN2DL: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2434 -* AT+NJM: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2435 -* AT+NWKID: Get or set the Network ID
2436 -* AT+FCU: Get or set the Frame Counter Uplink (FCntUp)
2437 -* AT+FCD: Get or set the Frame Counter Downlink (FCntDown)
2438 -* AT+CLASS: Get or set the Device Class
2439 -* AT+JOIN: Join network
2440 -* AT+NJS: Get OTAA Join Status
2441 -* AT+SENDB: Send hexadecimal data along with the application port
2442 -* AT+SEND: Send text data along with the application port
2443 -* AT+RECVB: Print last received data in binary format (with hexadecimal values)
2444 -* AT+RECV: Print last received data in raw format
2445 -* AT+VER: Get current image version and Frequency Band
2446 -* AT+CFM: Get or Set the confirmation mode (0-1)
2447 -* AT+CFS: Get confirmation status of the last AT+SEND (0-1)
2448 -* AT+SNR: Get the SNR of the last received packet
2449 -* AT+RSSI: Get the RSSI of the last received packet
2450 -* AT+TDC: Get or set the application data transmission interval in ms
2451 -* AT+PORT: Get or set the application port
2452 -* AT+DISAT: Disable AT commands
2453 -* AT+PWORD: Set password, max 9 digits
2454 -* AT+CHS: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2455 -* AT+CHE: Get or set eight channels mode, Only for US915, AU915, CN470
2456 -* AT+CFG: Print all settings
2349 +* ##**AT+TXP**##: Get or set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Specification)
2350 +* **##AT+DR##**:  Get or set the Data Rate. (0-7 corresponding to DR_X)  
2351 +* **##AT+DCS##**: Get or set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
2352 +* ##**AT+PNM**##: Get or set the public network mode. (0: off, 1: on)
2353 +* ##**AT+RX2FQ**##: Get or set the Rx2 window frequency
2354 +* ##**AT+RX2DR**##: Get or set the Rx2 window data rate (0-7 corresponding to DR_X)
2355 +* ##**AT+RX1DL**##: Get or set the delay between the end of the Tx and the Rx Window 1 in ms
2356 +* ##**AT+RX2DL**##: Get or set the delay between the end of the Tx and the Rx Window 2 in ms
2357 +* ##**AT+JN1DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
2358 +* ##**AT+JN2DL**##: Get or set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
2359 +* ##**AT+NJM**##: Get or set the Network Join Mode. (0: ABP, 1: OTAA)
2360 +* ##**AT+NWKID**##: Get or set the Network ID
2361 +* ##**AT+FCU**##: Get or set the Frame Counter Uplink (FCntUp)
2362 +* ##**AT+FCD**##: Get or set the Frame Counter Downlink (FCntDown)
2363 +* ##**AT+CLASS**##: Get or set the Device Class
2364 +* ##**AT+JOIN**##: Join network
2365 +* ##**AT+NJS**##: Get OTAA Join Status
2366 +* ##**AT+SENDB**##: Send hexadecimal data along with the application port
2367 +* ##**AT+SEND**##: Send text data along with the application port
2368 +* ##**AT+RECVB**##: Print last received data in binary format (with hexadecimal values)
2369 +* ##**AT+RECV**##: Print last received data in raw format
2370 +* ##**AT+VER**##: Get current image version and Frequency Band
2371 +* ##**AT+CFM**##: Get or Set the confirmation mode (0-1)
2372 +* ##**AT+CFS**##: Get confirmation status of the last AT+SEND (0-1)
2373 +* ##**AT+SNR**##: Get the SNR of the last received packet
2374 +* ##**AT+RSSI**##: Get the RSSI of the last received packet
2375 +* ##**AT+TDC**##: Get or set the application data transmission interval in ms
2376 +* ##**AT+PORT**##: Get or set the application port
2377 +* ##**AT+DISAT**##: Disable AT commands
2378 +* ##**AT+PWORD**##: Set password, max 9 digits
2379 +* ##**AT+CHS**##: Get or set the Frequency (Unit: Hz) for Single Channel Mode
2380 +* ##**AT+CHE**##: Get or set eight channels mode, Only for US915, AU915, CN470
2381 +* ##**AT+CFG**##: Print all settings
2457 2457  )))
2458 2458  
2459 2459  
... ... @@ -2618,7 +2618,7 @@
2618 2618  You will need the following things before proceeding:
2619 2619  
2620 2620  * 3.5mm programming cable (included with the LT-22222-L as an additional accessory)
2621 -* USB to TTL adapter
2546 +* USB to TTL adapter/converter
2622 2622  * 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)
2623 2623  * 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.
2624 2624  
... ... @@ -2628,7 +2628,7 @@
2628 2628  
2629 2629  Below is the hardware setup for uploading a firmware image to the LT-22222-L:
2630 2630  
2631 -[[image:usb-ttl-programming.png]]
2556 +[[image:usb-ttl-audio-jack-connection.jpg]]
2632 2632  
2633 2633  
2634 2634  
Screenshot 2024-11-23 at 18.27.11.png
Size
... ... @@ -1,1 +1,1 @@
1 -134.9 KB
1 +143.4 KB
Content
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