Changes for page SDI-12-LB/LS -- SDI-12 to LoRaWAN Converter User Manual
Last modified by Mengting Qiu on 2025/07/03 15:42
From version 166.2
edited by Mengting Qiu
on 2025/06/07 09:44
on 2025/06/07 09:44
Change comment:
There is no comment for this version
To version 171.2
edited by Mengting Qiu
on 2025/06/09 14:18
on 2025/06/09 14:18
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 3 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -511,9 +511,9 @@ 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: Thereturneddatawill 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!//. (% style="color:red" %)**2: When set to 2, AT+ALDATAMOD=1 does not intercept data returned by the current COMMAND command.(since v1.3.0)** 515 515 516 -(% style="color:red" %)**( When set to 2,AT+ALDATAMOD=1does notintercept data returned by the currentCOMMANDcommand.)**516 +(% style="color:red" %)**(Function set to 2: When the device is connected to more than two sensors with different sampling addresses, concurrent measurement can be used to reduce data acquisition time and save battery power; for example, when the device is connected to two sensors with different addresses, the concurrent measurement function can be used and the two sensors can collect data at the same time.)** 517 517 518 518 (% style="color:red" %)**var4**(%%): validation check for return. If return invalid, SDI-12-LB/LS will resend this command. Max 3 retries. 519 519 ... ... @@ -711,23 +711,21 @@ 711 711 * Example 2: Downlink Payload: AC 02 01 02 02 02 03 02 ~/~/ AT+DATACONV2=1,2+2,2+3,2 712 712 713 713 714 - 715 - 716 - 717 717 **For example:** 718 718 719 719 This is my configuration: 720 720 721 -[[image:image-2025060 5091006-1.png]]718 +[[image:image-20250609134137-1.png]] 722 722 723 723 724 724 * 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. 725 -* 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) 726 -* AT+COMMAND3=0D0!,0,0,0 Query the data measured by device 0 722 +* AT+COMMAND2=1C!,1,2,0 After sending a concurrent command to device 1, do not truncate the data and wait for one second. (Concurrent commands will be sampled with the command with the longest waiting time; for example, if the waiting time in the current device is set to 1s, the concurrent command will default to a maximum waiting time of 1s.) 723 +* AT+COMMAND3=0D0!,0,0,0 Query the data measured by device 0 724 +* AT+COMMAND4=1D0!,0,0,0 Query the data measured by device 1 727 727 728 728 This is the data obtained: 729 729 730 -[[image:image-20250 516145402-2.png]]728 +[[image:image-20250609134901-2.png]] 731 731 732 732 733 733 When using the AT+DATACONVx command, ... ... @@ -735,20 +735,31 @@ 735 735 The data of RETURN3 will be converted into 2 data, the first data is +95, and the second data is +260. 736 736 737 737 * 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: 736 +* ((( 737 +AT+DATACONV4=1,3+2,2+3,2 The first data uploads 3 bytes, the second data also uploads 2 bytes, and the third data also uploads 2 bytes. The hexadecimal form is shown above and as shown in the following figure: 738 +))) 738 738 739 -[[image:image-20250 516144559-1.png]]740 +[[image:image-20250609141343-1.png]] 740 740 741 - 0C9001005F0104742 +**For example,the uplink payload as below:** 742 742 743 - (%style="color:#037691"%)**BAT**(%%):0x0c90=3216mV=3.216V744 +0CE4 01 00C6 0103 02DB99 00FD 0001 744 744 746 +(% style="color:#037691" %)**BAT**(%%): 0x0CE4 = 3300mV = 3.300V 747 + 745 745 (% style="color:#037691" %)**Payload Version**(%%): 0x01, Means: v1.0 version 746 746 747 -(% style="color:#037691" %)**Data 1: **(%%)0x00 5F(H) = 95(D) / 100 =0.95750 +(% style="color:#037691" %)**Data 1: **(%%)0x00C6(H) = 198(D) / 100 = 19.8 748 748 749 -(% style="color:#037691" %)**Data 2: **(%%)0x010 4(H) = 260(D) / 10 = 26.0752 +(% style="color:#037691" %)**Data 2: **(%%)0x0103(H) = 259(D) / 10 = 25.9 750 750 754 +(% style="color:#037691" %)**Data 3: **(%%)0x02DB99(H) = 187289(D) / 100 = 1872.89 751 751 756 +(% style="color:#037691" %)**Data 4: **(%%)0x00FD(H) = 253(D) / 10 = 25.3 757 + 758 +(% style="color:#037691" %)**Data 5: **(%%)0x0001(H) = 1(D) = 1 759 + 760 + 752 752 == 2.4 Uplink Payload == 753 753 754 754 === 2.4.1 Device Payload, FPORT~=5 === ... ... @@ -1809,7 +1809,7 @@ 1809 1809 No downlink commands for feature 1810 1810 1811 1811 1812 -== =3.9 Clear Flash Record(Since v1.3.0) ===1821 +== 3.9 Clear Flash Record(Since v1.3.0) == 1813 1813 1814 1814 1815 1815 Feature: Clear flash storage for data log feature.
- image-20250609134137-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.ting - Size
-
... ... @@ -1,0 +1,1 @@ 1 +48.0 KB - Content
- image-20250609134901-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.ting - Size
-
... ... @@ -1,0 +1,1 @@ 1 +16.6 KB - Content
- image-20250609141343-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.ting - Size
-
... ... @@ -1,0 +1,1 @@ 1 +76.1 KB - Content