Skip to Content
Last modified by Mengting Qiu on 2025/07/03 15:42
From version 179.1
edited by Mengting Qiu
on 2025/07/03 15:41
Change comment: There is no comment for this version
To version 174.1
edited by Mengting Qiu
on 2025/06/13 15:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -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.
731 +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  
738 +[[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
742 +0CE4 01 00C6 0103 02DB99 00FD 0001
745 745  
746 -(% style="color:#037691" %)**BAT**(%%): 0x0CFC = 3324mV = 3.324V
744 +(% 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
748 +(% 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
750 +(% 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
752 +(% 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
754 +(% 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  
... ... @@ -1267,37 +1267,26 @@
1267 1267  == 2.9 Datalog Feature(Since v1.3.0) ==
1268 1268  
1269 1269  
1270 -Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, SDI-12-LB will store the reading for future retrieving purposes.
1271 -
1272 -
1273 -=== 2.5.1 How datalog works ===
1274 -
1275 -
1276 -SDI-12-LB will wait for ACK for every uplink, when there is no LoRaWAN network,SDI-12-LB will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
1277 -
1278 -* (((
1279 -a) SDI-12-LB will do an ACK check for data records sending to make sure every data arrive server.
1268 +(((
1269 +Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, SDI-12-LB will store the reading for future retrieving purposes. There are two ways for IoT servers to get datalog from SDI-12-LB.
1280 1280  )))
1281 -* (((
1282 -b) SDI-12-LB will send data in **CONFIRMED Mode**, but SDI-12-LB won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink if SDI-12-LB gets a ACK, SDI-12-LB will consider there is a network connection and resend all NONE-ACK messages.
1283 1283  
1284 -
1285 -)))
1286 1286  
1287 -=== 2.5.2 Enable Datalog ===
1273 +=== 2.9.1 Ways to get datalog via LoRaWAN ===
1288 1288  
1289 1289  
1290 -User need to make sure below two settings are enable to use datalog;
1276 +There are two methods:
1291 1291  
1292 -* (% style="color:blue" %)**SYNCMOD=1(Default)**(%%) to enable sync time via LoRaWAN MAC command, click here ([[AT+SYNCMOD>>https://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H4.6Settimesynchronizationmethod28ThenetworkservermustsupportLoRaWANv1.0.329]]) for detailed instructions.
1293 -* (% style="color:blue" %)**PNACKMD=1**(%%)** **to enable datalog feature, click here ([[AT+PNACKMD>>https://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.26RequesttheservertosendanACK]]) for detailed instructions.
1278 +(% style="color:blue" %)**Method 1:** (%%)IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.8.4Pollsensorvalue"]] for specified time range.
1294 1294  
1295 1295  
1281 +(% style="color:blue" %)**Method 2: **(%%)Set PNACKMD=1, SDI-12-LB will wait for ACK for every uplink, when there is no LoRaWAN network, SDI-12-LB will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
1296 1296  
1297 -Once SDI-12-LB Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to SDI-12-LB. If SDI-12-LB fails to get the time from the server, SDI-12-LB will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
1298 1298  
1299 -(% style="color:red" %)**Note: LoRaWAN Server need to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature, Chirpstack,TTN V3 v3 and loriot support but TTN V3 v2 doesn't support. If server doesn't support this command, it will through away uplink packet with this command, so user will lose the packet with time request for TTN V3 v2 if SYNCMOD=1.**
1284 +(% style="color:red" %)**Note for method 2:**
1300 1300  
1286 +* a) SDI-12-LB will do an ACK check for data records sending to make sure every data arrive server.
1287 +* b) SDI-12-LB will send data in **CONFIRMED Mode** when PNACKMD=1, but SDI-12-LB won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink if SDI-12-LB gets a ACK, SDI-12-LB will consider there is a network connection and resend all NONE-ACK Message.
1301 1301  
1302 1302  === 2.9.2 Unix TimeStamp ===
1303 1303  
... ... @@ -1316,6 +1316,39 @@
1316 1316  So, we can use AT+TIMESTAMP=1742889625 or downlink 3067E26299 to set the current time 2025 – March ~-~- 25 Tuesday  08:00:25
1317 1317  
1318 1318  
1306 +=== 2.9.3 Set Device Time ===
1307 +
1308 +
1309 +(((
1310 +(% style="color:blue" %)**There are two ways to set device's time:**
1311 +)))
1312 +
1313 +(((
1314 +**1.  Through LoRaWAN MAC Command (Default settings)**
1315 +)))
1316 +
1317 +(((
1318 +User need to set SYNCMOD=1 to enable sync time via MAC command.
1319 +)))
1320 +
1321 +(((
1322 +Once SDI-12-LB Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to SDI-12-LB. If SDI-12-LB fails to get the time from the server, SDI-12-LB will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
1323 +)))
1324 +
1325 +(((
1326 +(% style="color:red" %)**Note: LoRaWAN Server need to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature, Chirpstack,TTN V3 v3 and loriot support but TTN V3 v2 doesn't support. If server doesn't support this command, it will through away uplink packet with this command, so user will lose the packet with time request for TTN V3 v2 if SYNCMOD=1.**
1327 +)))
1328 +
1329 +
1330 +(((
1331 +**2. Manually Set Time**
1332 +)))
1333 +
1334 +(((
1335 +User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
1336 +)))
1337 +
1338 +
1319 1319  === 2.9.4 Poll sensor value ===
1320 1320  
1321 1321  
... ... @@ -1939,7 +1939,7 @@
1939 1939  
1940 1940  
1941 1941  
1942 -== 3.12 Cut data separation processing(Since firmware V1.3.2) ==
1962 +== 3.12 Cut data separation processing ==
1943 1943  
1944 1944  
1945 1945  AT+NEWLINE command, which only takes effect when AT+DATAUP=1 or AT+DATAUP=1, timeout.
... ... @@ -2000,22 +2000,12 @@
2000 2000  
2001 2001  = 6. OTA firmware update =
2002 2002  
2003 -User can change firmware TS01-LB/LS to:
2004 2004  
2005 -* Change Frequency band/ region.
2006 -* Update with new features.
2007 -* Fix bugs.
2024 +Please see this link for how to do OTA firmware update.
2008 2008  
2009 -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]]
2026 +[[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/]]
2010 2010  
2011 -Methods to Update Firmware:
2012 2012  
2013 -* (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/]]**
2014 -
2015 -* 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]]**.
2016 -
2017 -
2018 -
2019 2019  = 7. FAQ =
2020 2020  
2021 2021  == 7.1 How to use AT Command  via UART to access device? ==