Last modified by Mengting Qiu on 2025/07/03 15:42

From version 154.2
edited by Mengting Qiu
on 2025/05/16 14:47
Change comment: There is no comment for this version
To version 144.2
edited by Mengting Qiu
on 2025/05/15 09:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -498,7 +498,7 @@
498 498  === 2.3.4 Define periodically SDI-12 commands and uplink. ===
499 499  
500 500  
501 -AT+COMMANDx & AT+DATACUTx**&AT+DATACONVx**
501 +AT+COMMANDx & AT+DATACUTx
502 502  
503 503  User can define max 15 SDI-12 Commands (AT+COMMAND1 ~~ AT+COMMANDF). On each uplink period (TDC time, default 20 minutes), SDI-12-LB/LS will send these SDI-12 commands and wait for return from SDI-12 sensors. SDI-12-LB/LS will then combine these returns and uplink via LoRaWAN.
504 504  
... ... @@ -511,7 +511,7 @@
511 511  
512 512  (% style="color:red" %)**var2**(%%): Wait timeout for return. (unit: second)
513 513  
514 -(% style="color:red" %)**var3**(%%): Whether to send //addrD0!// to get return after var2 timeout. 0: Don't Send //addrD0! //; 1: Send //addrD0!//. (% style="color:red" %)**2: The returned data will not be clipped.(since v1.3.0)**
514 +(% style="color:red" %)**var3**(%%): Whether to send //addrD0!// to get return after var2 timeout. 0: Don't Send //addrD0! //; 1: Send //addrD0!//.
515 515  
516 516  (% style="color:red" %)**var4**(%%): validation check for return. If return invalid, SDI-12-LB/LS will resend this command. Max 3 retries.
517 517  
... ... @@ -654,53 +654,6 @@
654 654  (% style="color:red" %)**When AT+DATAUP=1 and AT+ADR=0, the maximum number of bytes of each payload is determined by the DR value.**
655 655  
656 656  
657 -
658 -(% style="color:blue" %)**Automatically converts polled data to hex format for uplinking(Since v1.3.0)**
659 -
660 -
661 -This command can retrieve the returned data, convert the number after the positive or negative sign into a data, and then set the number of bytes to upload the data.
662 -
663 -
664 -* (% style="color:blue" %)**AT Command:**
665 -
666 -The maximum number can be set to 5 groups and the format of the command is as follows:
667 -
668 -(% style="color:#037691" %)**Example 1:AT+DATACONVx=var1, var2**
669 -
670 -(% style="color:#037691" %)**Example 2:AT+DATACONVx=var1, var2+ var3, var4**
671 -
672 -(% style="color:#037691" %)**Example 3:AT+DATACONVx=var1, var2+ var3, var4+ var5, var6**
673 -
674 -(% style="color:#037691" %)**Example 4:AT+DATACONVx=var1, var2+ var3, var4+ var5, var6+ var7, var8**
675 -
676 -(% style="color:#037691" %)**Example 5:AT+DATACONVx=var1, var2+ var3, var4+ var5, var6+ var7, var8+ var9, var10**
677 -
678 -(% style="color:red" %)**Notice: Among them, var1, var3, var5, var7, and var9 are the data to be selected for conversion, and var2, var4, var6, var8, and var10 are the number of bytes to be uploaded. The values of var2, var4, var6, var8, and var10 range from 1 to 4.**
679 -
680 -
681 -**For example:**
682 -
683 -This is my configuration:
684 -
685 -[[image:image-20250516103205-2.png]]
686 -
687 -
688 -* AT+COMMAND1=0C!,0,2,0  After sending the concurrent command of device 0, the data will not be cut, and the next command will be sent immediately.
689 -* AT+COMMAND2=0M!,1,2,0  After sending the concurrent command of device 0, do not cut the data and wait for one second. (The last concurrent command needs to wait for the measurement time of all sensors)
690 -* AT+COMMAND3=0D0!,0,0,0  Query the data measured by device 0
691 -
692 -This is the data obtained:
693 -
694 -[[image:image-20250516103652-3.png]]
695 -
696 -
697 -When using the AT+DATACONVx command,
698 -
699 -The data of RETURN3 will be converted into 2 data, the first data is +101, and the second data is +263.
700 -
701 -* AT+DATACONV3=1,2+2,2  The first data is uploaded as 2 bytes and the second data is uploaded as 2 bytes. The form converted to hexadecimal is as shown above,as below:
702 -
703 -
704 704  == 2.4 Uplink Payload ==
705 705  
706 706  === 2.4.1 Device Payload, FPORT~=5 ===
... ... @@ -1294,9 +1294,9 @@
1294 1294  
1295 1295  Timestamp start and Timestamp end use Unix TimeStamp format as mentioned above. Devices will reply with all data log during this time period, use the uplink interval.
1296 1296  
1297 -For example, downlink command (% _mstmutation="1" %)**31 68253B6E 68253E23 05**(%%)
1250 +For example, downlink command (% _mstmutation="1" %)**31 67E24660 67E26280 05**(%%)
1298 1298  
1299 -Is to check 2025/05/15 00:55:10 to 2025/05/15 01:06:43's data
1252 +Is to check 2025/03/25 06:00:00 to 2025/03/25 08:00:00's data
1300 1300  
1301 1301  Uplink Internal =5s, means SDI-12-LB will send one packet every 5s.
1302 1302  
... ... @@ -1359,31 +1359,31 @@
1359 1359  2025/3/25 08:16:30
1360 1360  )))|(% style="width:82px" %)5|(% style="width:86px" %)0c ae|(% style="width:92px" %)01|(% style="width:131px" %)08 22
1361 1361  
1362 -If user sends below downlink command: (% style="background-color:yellow" %)3168253B6E68253E2305
1315 +If user sends below downlink command: (% style="background-color:yellow" %)3167E264BA67E2665E05
1363 1363  
1364 -Where : Start time: (% _mstmutation="1" %)68253B6E (%%)= time 2025/05/15 00:55:10
1317 +Where : Start time: 67E264BA = time 2025/3/25 08:09:30
1365 1365  
1366 - Stop time: (% _mstmutation="1" %)68253E23 (%%)= time 2025/05/15 01:06:43
1319 + Stop time: 67E2665E= time 2025/3/25 08:16:30
1367 1367  
1368 1368  
1369 1369  **SDI-12-LB will uplink this payload.**
1370 1370  
1371 -**68253B6E 12 0C7801F10D302B312E31372B32362E390D0A **68253C5D120C7801F10D302B312E31372B32372E340D0A68253D33120C7201F10D302B312E31352B32382E390D0A68253DAB120C7201F10D302B312E31342B32392E340D0A68253E23120C7201F10D302B312E31332B33302E300D0A
1324 +**67E264BA 05 0CA8 01 0821** 67E264F6050CAE01082267E26532050CAE01082267E2656E050CAE01082267E265AA050CB401082367E265E6050CAE01082267E26622050CB401082367E2665E050CAE010822
1372 1372  
1373 1373  
1374 -Where the first 23 bytes is for the first entry:
1327 +Where the first 10 bytes is for the first entry:
1375 1375  
1376 -**68253B6E 12 0C7801F10D302B312E31372B32362E390D0A**
1329 +67E264BA050CA8010821
1377 1377  
1378 -Unix Time Stamp: 68253B6E(H)=1747270510(D)  ~-~->  time=2025-05-15 8:55:00
1331 +Unix Time Stamp: 67E264BA(H)=1742890170(D)  ~-~->  time=2025-03-25 8:09:30
1379 1379  
1380 -Payload Length: 0x12(H)=18 bytes
1333 +Payload Length: 0x05(H)=5 bytes
1381 1381  
1382 -Battery voltage: 0x0C78(H)=3192 mV
1335 +Battery voltage: 0x0CA8(H)=3240 mV
1383 1383  
1384 1384  Payload Version:  01
1385 1385  
1386 -Value: For the distance sensor used for testing, this value is the mm distance value, 0xF10D302B312E31372B32362E390D0A(H)
1339 +Value: For the distance sensor used for testing, this value is the mm distance value, 0x0821(H)=2081mm.
1387 1387  
1388 1388  
1389 1389  
... ... @@ -1622,9 +1622,10 @@
1622 1622  * Example 1: Downlink Payload: AE 01  ~/~/  AT+PAYVER=1
1623 1623  * Example 2: Downlink Payload: AE 05  ~/~/  AT+PAYVER=5
1624 1624  
1625 -=== 3.7 Print data entries base on page(Since v1.3.0) ===
1626 1626  
1579 +=== 3.7 Print data entries base on page ===
1627 1627  
1581 +
1628 1628  Feature: Print the sector data from start page to stop page (max is 416 pages).
1629 1629  
1630 1630  (% style="color:#4f81bd" %)**AT Command: AT+PDTA**
... ... @@ -1635,29 +1635,42 @@
1635 1635  AT+PDTA=1,2
1636 1636  Print page 1 to 2
1637 1637  )))|(% style="width:311px" %)(((
1638 -Stop Tx and RTP events when read sensor data
1592 +Stop Tx events when read sensor data
1639 1639  
1640 -8033330 2025/5/14 12:27:32 18 0c 84 01 f1 0d 30 2b 31 2e 30
1594 +8032000 2025/3/25 06:36:49 5 0c a8 01 08 1e
1641 1641  
1642 -8033340 38 2b 32 34 2e 36 0d 0a
1596 +8032010 2025/3/25 06:37:49 5 0c ae 01 08 20
1643 1643  
1644 -8033350 2025/5/14 12:29:32 18 0c 72 01 f1 0d 30 2b 31 2e 30
1598 +8032020 2025/3/25 06:38:49 5 0c ae 01 08 24
1645 1645  
1646 -8033360 38 2b 32 34 2e 36 0d 0a
1600 +8032030 2025/3/25 06:39:49 5 0c ae 01 08 1f
1647 1647  
1648 -8033370 2025/5/14 12:31:32 18 0c 78 01 f1 0d 30 2b 31 2e 30
1602 +8032040 2025/3/25 06:40:49 5 0c a8 01 08 24
1649 1649  
1650 -8033380 38 2b 32 34 2e 36 0d 0a
1604 +8032050 2025/3/25 06:42:11 5 0c a8 01 08 22
1651 1651  
1652 -8033390 2025/5/14 12:33:32 18 0c 72 01 f1 0d 30 2b 31 2e 30
1606 +8032060 2025/3/25 06:43:11 5 0c a8 01 08 23
1653 1653  
1654 -80333A0 38 2b 32 34 2e 36 0d 0a
1608 +8032070 2025/3/25 06:44:11 5 0c ae 01 08 22
1655 1655  
1656 -80333B0 2025/5/14 12:35:32 18 0c 72 01 f1 0d 30 2b 31 2e 30
1610 +8032080 2025/3/25 06:45:11 5 0c ae 01 08 1e
1657 1657  
1658 -80333C0 38 2b 32 34 2e 36 0d 0a
1612 +8032090 2025/3/25 06:46:11 5 0c b4 01 08 1e
1659 1659  
1614 +80320A0 2025/3/25 06:47:11 5 0c a8 01 08 1d
1660 1660  
1616 +80320B0 2025/3/25 06:48:11 5 0c ae 01 08 22
1617 +
1618 +80320C0 2025/3/25 06:49:11 5 0c b4 01 08 24
1619 +
1620 +80320D0 2025/3/25 06:50:11 5 0c a8 01 08 23
1621 +
1622 +80320E0 2025/3/25 06:51:11 5 0c a8 01 08 23
1623 +
1624 +80320F0 2025/3/25 06:52:11 5 0c ae 01 08 22
1625 +
1626 +Start Tx events
1627 +
1661 1661  OK
1662 1662  )))
1663 1663  
... ... @@ -1666,7 +1666,7 @@
1666 1666  No downlink commands for feature
1667 1667  
1668 1668  
1669 -=== 3.8 Print last few data entries(Since v1.3.0) ===
1636 +=== 3.8 Print last few data entries ===
1670 1670  
1671 1671  
1672 1672  Feature: Print the last few data entries
... ... @@ -1701,7 +1701,7 @@
1701 1701  No downlink commands for feature
1702 1702  
1703 1703  
1704 -=== 3.9 Clear Flash Record(Since v1.3.0) ===
1671 +=== 3.9 Clear Flash Record ===
1705 1705  
1706 1706  
1707 1707  Feature: Clear flash storage for data log feature.
... ... @@ -1721,31 +1721,6 @@
1721 1721  * Example: 0xA301  ~/~/  Same as AT+CLRDTA
1722 1722  
1723 1723  
1724 -== 3.10 SDI12 timing(Since v1.3.0) ==
1725 -
1726 -
1727 -Feature: Get or set the time of SDI12 timing.
1728 -
1729 -[[image:1747289896656-580.png||height="414" width="566"]]
1730 -
1731 -(% style="color:#4f81bd" %)**AT Command: AT+SDITIMING**
1732 -
1733 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:503px" %)
1734 -|(% style="background-color:#4f81bd; color:white; width:157px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:167px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:177px" %)**Response**
1735 -|(% style="width:155px" %)(((
1736 -AT+SDITIMING=13,9
1737 -
1738 -
1739 -)))|(% style="width:167px" %)Get or set the time of SDI12 timing|(% style="width:177px" %)(((
1740 -OK
1741 -
1742 -Default: 13,9
1743 -)))
1744 -
1745 -(% style="color:#4f81bd" %)**Downlink Command: 0xA9**
1746 -
1747 -* Example: 0xA90D09  ~/~/  Same as AT+SDITIMING=13,9
1748 -
1749 1749  = 4. Battery & Power Consumption =
1750 1750  
1751 1751  
1747289896656-580.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -37.0 KB
Content
image-20250516100849-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -37.2 KB
Content
image-20250516103205-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -37.3 KB
Content
image-20250516103652-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -14.5 KB
Content
image-20250516144559-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -55.1 KB
Content