Skip to Content
Last modified by Mengting Qiu on 2025/07/03 15:42
From version 169.1
edited by Mengting Qiu
on 2025/06/09 13:41
Change comment: Uploaded new attachment "image-20250609134137-1.png", version {1}
To version 176.1
edited by Bei Jinggeng
on 2025/06/13 15:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Bei
Content
... ... @@ -1,7 +1,6 @@
1 1  
2 2  
3 -(% style="text-align:center" %)
4 -[[image:image-20240103165259-3.png||height="433" width="591"]]
3 +[[image:image-20240103165259-3.png||data-xwiki-image-style-alignment="center" height="433" width="591"]]
5 5  
6 6  
7 7  
... ... @@ -139,16 +139,16 @@
139 139  
140 140  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
141 141  |=(% style="width: 167px;background-color:#4F81BD;color:white" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 226px;background-color:#4F81BD;color:white" %)**Action**
142 -|(% style="background-color:#f2f2f2; width:167px" %)Pressing ACT between 1s < time < 3s|(% style="background-color:#f2f2f2; width:117px" %)Send an uplink|(% style="background-color:#f2f2f2; width:225px" %)(((
141 +|[[image:1749523850351-927.png]] 1~~3s|(% style="background-color:#f2f2f2; width:117px" %)Send an uplink|(% style="background-color:#f2f2f2; width:225px" %)(((
143 143  If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once.
144 144  Meanwhile, BLE module will be active and user can connect via BLE to configure device.
145 145  )))
146 -|(% style="background-color:#f2f2f2; width:167px" %)Pressing ACT for more than 3s|(% style="background-color:#f2f2f2; width:117px" %)Active Device|(% style="background-color:#f2f2f2; width:225px" %)(((
145 +|[[image:1749523852387-583.png]] >3s|(% style="background-color:#f2f2f2; width:117px" %)Active Device|(% style="background-color:#f2f2f2; width:225px" %)(((
147 147  (% style="background-color:#f2f2f2; color:green" %)**Green led**(%%) will fast blink 5 times, device will enter (% style="color:#037691" %)**OTA mode**(%%) for 3 seconds. And then start to JOIN LoRaWAN network.
148 148  (% style="background-color:#f2f2f2; color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network.
149 149  Once sensor is active, BLE module will be active and user can connect via BLE to configure device, no matter if device join or not join LoRaWAN network.
150 150  )))
151 -|(% style="background-color:#f2f2f2; width:167px" %)Fast press ACT 5 times.|(% style="background-color:#f2f2f2; width:117px" %)Deactivate Device|(% style="background-color:#f2f2f2; width:225px" %)(% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means SDI-12-LB/LS is in Deep Sleep Mode.
150 +|[[image:1749523825515-716.png]] x5|(% style="background-color:#f2f2f2; width:117px" %)Deactivate Device|(% style="background-color:#f2f2f2; width:225px" %)(% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means SDI-12-LB/LS is in Deep Sleep Mode.
152 152  
153 153  == 1.7 Pin Mapping ==
154 154  
... ... @@ -513,7 +513,7 @@
513 513  
514 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" %)**(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.)**
515 +(% 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 a device is connected to two sensors with different addresses, and both sensors are to use concurrent measurements, then both sensors can be measured at the same time without the second one having to wait until after the first one.)**
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  
... ... @@ -710,22 +710,21 @@
710 710  * Example 1: Downlink Payload: AC 01 01 02 02 02  ~/~/  AT+DATACONV1=1,2+2,2 
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 -
714 -
715 715  **For example:**
716 716  
717 717  This is my configuration:
718 718  
719 -[[image:image-20250605091006-1.png]]
716 +[[image:image-20250609134137-1.png]]
720 720  
721 721  
722 -* 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.
723 -* 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)
724 -* AT+COMMAND3=0D0!,0,0,0  Query the data measured by device 0
719 +* AT+COMMAND1=0C!,0,2,0  Use concurrent measurement commands without intercepting the returned data.
720 +* AT+COMMAND2=1C!,1,2,0  Use concurrent measurement commands without intercepting the returned data, with a second parameter to be set at the last concurrent command (the second parameter takes the maximum transition time between the two sensors)
721 +* AT+COMMAND3=0D0!,0,0,0  Query the data measured by device 0
722 +* AT+COMMAND4=1D0!,0,0,0  Query the data measured by device 1
725 725  
726 726  This is the data obtained:
727 727  
728 -[[image:image-20250516145402-2.png]]
726 +[[image:image-20250609134901-2.png]]
729 729  
730 730  
731 731  When using the AT+DATACONVx command,
... ... @@ -733,20 +733,31 @@
733 733  The data of RETURN3 will be converted into 2 data, the first data is +95, and the second data is +260.
734 734  
735 735  * 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:
734 +* (((
735 +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:
736 +)))
736 736  
737 -[[image:image-20250516144559-1.png]]
738 +[[image:image-20250609141343-1.png]]
738 738  
739 -0C90 01 005F 0104
740 +**For example,the uplink payload as below:**
740 740  
741 -(% style="color:#037691" %)**BAT**(%%): 0x0c90 = 3216mV = 3.216V
742 +0CE4 01 00C6 0103 02DB99 00FD 0001
742 742  
744 +(% style="color:#037691" %)**BAT**(%%): 0x0CE4 = 3300mV = 3.300V
745 +
743 743  (% style="color:#037691" %)**Payload Version**(%%): 0x01, Means: v1.0 version
744 744  
745 -(% style="color:#037691" %)**Data 1: **(%%)0x005F(H) = 95(D) / 100 = 0.95
748 +(% style="color:#037691" %)**Data 1: **(%%)0x00C6(H) = 198(D) / 100 = 19.8
746 746  
747 -(% style="color:#037691" %)**Data 2: **(%%)0x0104(H) = 260(D) / 10 = 26.0
750 +(% style="color:#037691" %)**Data 2: **(%%)0x0103(H) = 259(D) / 10 = 25.9
748 748  
752 +(% style="color:#037691" %)**Data 3: **(%%)0x02DB99(H) = 187289(D) / 100 = 1872.89
749 749  
754 +(% style="color:#037691" %)**Data 4: **(%%)0x00FD(H) = 253(D) / 10 = 25.3
755 +
756 +(% style="color:#037691" %)**Data 5: **(%%)0x0001(H) = 1(D) = 1
757 +
758 +
750 750  == 2.4 Uplink Payload ==
751 751  
752 752  === 2.4.1 Device Payload, FPORT~=5 ===
... ... @@ -1852,6 +1852,9 @@
1852 1852  
1853 1853  * Example: 0xA90D09  ~/~/  Same as AT+SDITIMING=13,9
1854 1854  
1864 +
1865 +
1866 +
1855 1855  == 3.11 add Pulse_count, VDC_input, IDC_input(Since firmware V1.3.0) ==
1856 1856  
1857 1857  
... ... @@ -1947,6 +1947,45 @@
1947 1947  
1948 1948  
1949 1949  
1962 +== 3.12 Cut data separation processing(Since firmware V1.3.2) ==
1963 +
1964 +
1965 +AT+NEWLINE command, which only takes effect when AT+DATAUP=1 or AT+DATAUP=1, timeout.
1966 +
1967 +When not set, each part of AT+DATAUP is sent according to the maximum number of bytes of DR.
1968 +
1969 +When setting, each part of AT+DATAUP is sent according to the value set by AT+NEWLINE.
1970 +
1971 +
1972 +* (((
1973 +(% style="color:#037691" %)** AT Command:**
1974 +)))
1975 +
1976 +(% style="color:#4472c4" %)//**AT+NEWLINE=ALL**//(%%)//   //The data cut out by each AT+COMMANDx command is sent separately as an uplink.
1977 +
1978 +(% style="color:#4472c4" %)//**AT+NEWLINE=ALL**//(%%)//   equal：  (% style="color:#4472c4" %)**AT+NEWLINE=1+2+3+4+5+6+7+8+9+10+11+12+13+14+15**//
1979 +
1980 +
1981 +(% style="color:#4472c4" %)//**AT+NEWLINE=a+b+c**//(%%)//  //The data returned by all commands is divided into three parts, COMMAND(1~~a) is the first part, COMMAND(a+1~~b) is the second part,COMMAND(b+1~~c) is the third part.
1982 +
1983 +
1984 +(% style="color:#4472c4" %)//**AT+NEWLINE=NULL**//(%%)//  //Turn off the functionality of this AT command.
1985 +
1986 +
1987 +* (((
1988 +(% style="color:#037691" %)** Downlink Payload:**
1989 +)))
1990 +
1991 +//AT+NEWLINE=ALL  ~-~-->  (% style="color:#4472c4" %)**0xA5 01**//
1992 +
1993 +// AT+NEWLINE= NULL  ~-~-->  (% style="color:#4472c4" %)**0xA5 00**//
1994 +
1995 +//AT+NEWLINE= a+b+c   ~-~-->  (% style="color:#4472c4" %)**0xA5 number of bytes a b c**//
1996 +
1997 +//AT+NEWLINE= 1+5+15 ~-~-->  (% style="color:#4472c4" %)**0xA5 03 01 05 0F**//
1998 +
1999 +
2000 +
1950 1950  = 4. Battery & Power Consumption =
1951 1951  
1952 1952  
... ... @@ -1969,12 +1969,22 @@
1969 1969  
1970 1970  = 6. OTA firmware update =
1971 1971  
2023 +User can change firmware TS01-LB/LS to:
1972 1972  
1973 -Please see this link for how to do OTA firmware update.
2025 +* Change Frequency band/ region.
2026 +* Update with new features.
2027 +* Fix bugs.
1974 1974  
1975 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/]]
2029 +Firmware and changelog can be downloaded from : **Firmware download link**
1976 1976  
2031 +Methods to Update Firmware:
1977 1977  
2033 +* (Recommanded way) OTA firmware update via wireless : **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/]]**
2034 +
2035 +* Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]]**.
2036 +
2037 += =
2038 +
1978 1978  = 7. FAQ =
1979 1979  
1980 1980  == 7.1 How to use AT Command  via UART to access device? ==
1749523825515-716.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +1.4 KB
Content
1749523850351-927.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +1.9 KB
Content
1749523852387-583.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +1.9 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