Skip to Content
Last modified by Mengting Qiu on 2025/07/01 15:58
From version 101.1
edited by Xiaoling
on 2025/06/10 10:45
Change comment: There is no comment for this version
To version 105.1
edited by Edwin Chen
on 2025/06/27 11:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -108,6 +108,7 @@
108 108  
109 109  [[image:image-20250416143859-1.jpeg]]
110 110  
111 +
111 111  (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
112 112  |=(% 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**
113 113  |[[image:1749523489553-702.png]] 1~~3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)(((
... ... @@ -121,12 +121,13 @@
121 121  )))
122 122  |[[image:1749523524280-815.png]] x5|(% style="width:117px" %)Deactivate Device|(% style="width:225px" %)(% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means device is in Deep Sleep Mode.
123 123  
125 +
126 +
124 124  == 1.6 BLE connection ==
125 125  
126 126  
127 127  S31x-LB/LS support BLE remote configure.
128 128  
129 -
130 130  BLE can be used to configure the parameter of sensor or see the console output from sensor. BLE will be only activate on below case:
131 131  
132 132  * Press button to send an uplink
... ... @@ -139,13 +139,18 @@
139 139  == 1.7 Pin Definitions ==
140 140  
141 141  
142 -
143 143  [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/image-20240926134323-1.png?rev=1.1||alt="image-20240926134323-1.png"]]
144 144  
146 +== 1.8 Wiring of DS18B20 temperature sensor ==
145 145  
146 -== 1.8 Hardware Variant ==
148 +The S31x-LB supports connection to the external temperature sensor DS18B20. The wiring method is as follows:
147 147  
150 +[[image:1749779850163-145.jpg||height="408" width="651"]]
148 148  
152 +
153 +== 1.9 Hardware Variant ==
154 +
155 +
149 149  (% border="1" cellspacing="3" style="width:460px" %)
150 150  |=(% style="width: 102px;background-color:#4F81BD;color:white" %)Model|=(% style="width: 182px; background-color:#4F81BD;color:white" %)Photo|=(% style="width: 176px; background-color:#4F81BD;color:white" %)Probe Info
151 151  |(% style="width:102px" %)(((
... ... @@ -172,19 +172,15 @@
172 172  (% style="display:none" %)
173 173  
174 174  
182 +== 1.10 Mechanical ==
175 175  
176 -== 1.9 Mechanical ==
184 +=== 1.10.1 for LB version ===
177 177  
178 -=== 1.9.1 for LB version ===
179 -
180 180  [[image:image-20250409174350-1.jpeg]]
181 181  
188 +=== 1.10.2 for LS version ===
182 182  
183 183  
184 -
185 -=== 1.9.2 for LS version ===
186 -
187 -
188 188  [[image:image-20250409174410-2.jpeg]]
189 189  
190 190  
... ... @@ -416,45 +416,49 @@
416 416  Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, S31x-LB/LS will store the reading for future retrieving purposes.
417 417  
418 418  
419 -=== 2.5.1 Ways to get datalog via LoRaWAN ===
422 +=== 2.5.1 How datalog works ===
420 420  
421 421  
422 -Set PNACKMD=1, S31x-LB/LS will wait for ACK for every uplink, when there is no LoRaWAN network,S31x-LB/LS 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.
425 +S31x-LB/LS will wait for ACK for every uplink, when there is no LoRaWAN network,S31x-LB/LS 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.
423 423  
424 424  * (((
425 425  a) S31x-LB/LS will do an ACK check for data records sending to make sure every data arrive server.
426 426  )))
427 427  * (((
428 -b) S31x-LB/LS will send data in **CONFIRMED Mode** when PNACKMD=1, but S31x-LB/LS 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 S31x-LB/LS gets a ACK, S31x-LB/LS will consider there is a network connection and resend all NONE-ACK messages.
431 +b) S31x-LB/LS will send data in **CONFIRMED Mode**, but S31x-LB/LS 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 S31x-LB/LS gets a ACK, S31x-LB/LS will consider there is a network connection and resend all NONE-ACK messages.
432 +
433 +
429 429  )))
430 430  
431 -=== 2.5.2 Unix TimeStamp ===
436 +=== 2.5.2 Enable Datalog ===
432 432  
433 433  
434 -S31x-LB/LS uses Unix TimeStamp format based on
439 +User need to make sure below two settings are enable to use datalog;
435 435  
436 -[[image:image-20250328173339-5.jpeg]]
441 +* (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via LoRaWAN MAC command
442 +* (% style="color:blue" %)**PMACKMD=1**(%%)** **to enable datalog feature
437 437  
438 -User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
439 439  
440 -Below is the converter example
441 441  
442 -[[image:image-20250328173355-6.jpeg]]
446 +Once S31x-LB/LS Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to S31x-LB/LS. If S31x-LB/LS fails to get the time from the server, S31x-LB/LS will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
443 443  
448 +(% 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.**
444 444  
445 -So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
446 446  
451 +=== 2.5.3 Unix TimeStamp ===
447 447  
448 -=== 2.5.3 Set Device Time ===
449 449  
454 +S31x-LB/LS uses Unix TimeStamp format based on
450 450  
451 -User need to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via MAC command.
456 +[[image:image-20250328173339-5.jpeg]]
452 452  
453 -Once S31x-LB/LS Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to S31x-LB/LS. If S31x-LB/LS fails to get the time from the server, S31x-LB/LS will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
458 +User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
454 454  
455 -(% 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.**
460 +Below is the converter example
456 456  
462 +[[image:image-20250328173355-6.jpeg]]
457 457  
464 +
458 458  === 2.5.4 Datalog Uplink payload (FPORT~=3) ===
459 459  
460 460  
1749779850163-145.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +252.1 KB
Content