Skip to Content
Last modified by Mengting Qiu on 2025/07/03 15:42
From version 178.1
edited by Saxer Lin
on 2025/06/30 15:11
Change comment: There is no comment for this version
To version 171.2
edited by Mengting Qiu
on 2025/06/09 14:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Saxer
1 +XWiki.ting
Content
... ... @@ -1,6 +1,7 @@
1 1  
2 2  
3 -[[image:image-20240103165259-3.png||data-xwiki-image-style-alignment="center" height="433" width="591"]]
3 +(% style="text-align:center" %)
4 +[[image:image-20240103165259-3.png||height="433" width="591"]]
4 4  
5 5  
6 6  
... ... @@ -138,16 +138,16 @@
138 138  
139 139  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
140 140  |=(% 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**
141 -|[[image:1749523850351-927.png]] 1~~3s|(% style="background-color:#f2f2f2; width:117px" %)Send an uplink|(% style="background-color:#f2f2f2; width:225px" %)(((
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" %)(((
142 142  If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once.
143 143  Meanwhile, BLE module will be active and user can connect via BLE to configure device.
144 144  )))
145 -|[[image:1749523852387-583.png]] >3s|(% style="background-color:#f2f2f2; width:117px" %)Active Device|(% style="background-color:#f2f2f2; width:225px" %)(((
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" %)(((
146 146  (% 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.
147 147  (% style="background-color:#f2f2f2; color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network.
148 148  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.
149 149  )))
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.
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.
151 151  
152 152  == 1.7 Pin Mapping ==
153 153  
... ... @@ -512,7 +512,7 @@
512 512  
513 513  (% 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)**
514 514  
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.)**
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.)**
516 516  
517 517  (% style="color:red" %)**var4**(%%): validation check for return. If return invalid, SDI-12-LB/LS will resend this command. Max 3 retries.
518 518  
... ... @@ -709,6 +709,7 @@
709 709  * Example 1: Downlink Payload: AC 01 01 02 02 02  ~/~/  AT+DATACONV1=1,2+2,2 
710 710  * Example 2: Downlink Payload: AC 02 01 02 02 02 03 02  ~/~/  AT+DATACONV2=1,2+2,2+3,2
711 711  
713 +
712 712  **For example:**
713 713  
714 714  This is my configuration:
... ... @@ -716,8 +716,8 @@
716 716  [[image:image-20250609134137-1.png]]
717 717  
718 718  
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+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.
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.)
721 721  * AT+COMMAND3=0D0!,0,0,0  Query the data measured by device 0
722 722  * AT+COMMAND4=1D0!,0,0,0  Query the data measured by device 1
723 723  
... ... @@ -728,32 +728,30 @@
728 728  
729 729  When using the AT+DATACONVx command,
730 730  
731 -The data of RETURN3 will be converted into 2 data, the first data is +192, and the second data is +258.
733 +The data of RETURN3 will be converted into 2 data, the first data is +95, and the second data is +260.
732 732  
733 -The data of RETURN4 will be converted into 3 data, the first data is +187716, and the second data is +252, and the third data is +1.
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:
736 736  * (((
737 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  )))
739 739  
740 +[[image:image-20250609141343-1.png]]
740 740  
741 -
742 742  **For example,the uplink payload as below:**
743 743  
744 -0CFC 01 00C0 0102 02DD44 00FC 0001
744 +0CE4 01 00C6 0103 02DB99 00FD 0001
745 745  
746 -(% style="color:#037691" %)**BAT**(%%): 0x0CFC = 3324mV = 3.324V
746 +(% style="color:#037691" %)**BAT**(%%): 0x0CE4 = 3300mV = 3.300V
747 747  
748 748  (% style="color:#037691" %)**Payload Version**(%%): 0x01, Means: v1.0 version
749 749  
750 -(% style="color:#037691" %)**Data 1: **(%%)0x00C0(H) = 192(D) / 100 = 19.2
750 +(% style="color:#037691" %)**Data 1: **(%%)0x00C6(H) = 198(D) / 100 = 19.8
751 751  
752 -(% style="color:#037691" %)**Data 2: **(%%)0x0102(H) = 258(D) / 10 = 25.8
752 +(% style="color:#037691" %)**Data 2: **(%%)0x0103(H) = 259(D) / 10 = 25.9
753 753  
754 -(% style="color:#037691" %)**Data 3: **(%%)0x02DD44(H) = 187716(D) / 100 = 1877.16
754 +(% style="color:#037691" %)**Data 3: **(%%)0x02DB99(H) = 187289(D) / 100 = 1872.89
755 755  
756 -(% style="color:#037691" %)**Data 4: **(%%)0x00FC(H) = 252(D) / 10 = 25.2
756 +(% style="color:#037691" %)**Data 4: **(%%)0x00FD(H) = 253(D) / 10 = 25.3
757 757  
758 758  (% style="color:#037691" %)**Data 5: **(%%)0x0001(H) = 1(D) = 1
759 759  
... ... @@ -1863,9 +1863,6 @@
1863 1863  
1864 1864  * Example: 0xA90D09  ~/~/  Same as AT+SDITIMING=13,9
1865 1865  
1866 -
1867 -
1868 -
1869 1869  == 3.11 add Pulse_count, VDC_input, IDC_input(Since firmware V1.3.0) ==
1870 1870  
1871 1871  
... ... @@ -1961,45 +1961,6 @@
1961 1961  
1962 1962  
1963 1963  
1964 -== 3.12 Cut data separation processing(Since firmware V1.3.2) ==
1965 -
1966 -
1967 -AT+NEWLINE command, which only takes effect when AT+DATAUP=1 or AT+DATAUP=1, timeout.
1968 -
1969 -When not set, each part of AT+DATAUP is sent according to the maximum number of bytes of DR.
1970 -
1971 -When setting, each part of AT+DATAUP is sent according to the value set by AT+NEWLINE.
1972 -
1973 -
1974 -* (((
1975 -(% style="color:#037691" %)** AT Command:**
1976 -)))
1977 -
1978 -(% style="color:#4472c4" %)//**AT+NEWLINE=ALL**//(%%)//   //The data cut out by each AT+COMMANDx command is sent separately as an uplink.
1979 -
1980 -(% 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**//
1981 -
1982 -
1983 -(% 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.
1984 -
1985 -
1986 -(% style="color:#4472c4" %)//**AT+NEWLINE=NULL**//(%%)//  //Turn off the functionality of this AT command.
1987 -
1988 -
1989 -* (((
1990 -(% style="color:#037691" %)** Downlink Payload:**
1991 -)))
1992 -
1993 -//AT+NEWLINE=ALL  ~-~-->  (% style="color:#4472c4" %)**0xA5 01**//
1994 -
1995 -// AT+NEWLINE= NULL  ~-~-->  (% style="color:#4472c4" %)**0xA5 00**//
1996 -
1997 -//AT+NEWLINE= a+b+c   ~-~-->  (% style="color:#4472c4" %)**0xA5 number of bytes a b c**//
1998 -
1999 -//AT+NEWLINE= 1+5+15 ~-~-->  (% style="color:#4472c4" %)**0xA5 03 01 05 0F**//
2000 -
2001 -
2002 -
2003 2003  = 4. Battery & Power Consumption =
2004 2004  
2005 2005  
... ... @@ -2022,22 +2022,12 @@
2022 2022  
2023 2023  = 6. OTA firmware update =
2024 2024  
2025 -User can change firmware TS01-LB/LS to:
2026 2026  
2027 -* Change Frequency band/ region.
2028 -* Update with new features.
2029 -* Fix bugs.
1984 +Please see this link for how to do OTA firmware update.
2030 2030  
2031 -Firmware and changelog can be downloaded from : [[**Firmware download link**>>https://www.dropbox.com/scl/fo/ztlw35a9xbkomu71u31im/AMbGiR5K1fLcUTLbp44o22Q/LoRaWAN%20End%20Node/SDI-12-LB/Firmware?rlkey=ojjcsw927eaow01dgooldq3nu&subfolder_nav_tracking=1&dl=0]]
1986 +[[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/]]
2032 2032  
2033 -Methods to Update Firmware:
2034 2034  
2035 -* (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/]]**
2036 -
2037 -* 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]]**.
2038 -
2039 -
2040 -
2041 2041  = 7. FAQ =
2042 2042  
2043 2043  == 7.1 How to use AT Command  via UART to access device? ==
1749523825515-716.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -1.4 KB
Content
1749523850351-927.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -1.9 KB
Content
1749523852387-583.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -1.9 KB
Content