Skip to Content
Last modified by Mengting Qiu on 2025/07/01 15:58
From version 103.1
edited by Mengting Qiu
on 2025/06/13 09:59
Change comment: There is no comment for this version
To version 105.2
edited by Bei Jinggeng
on 2025/06/28 15:29
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
... ... @@ -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,7 +139,6 @@
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  
145 145  == 1.8 Wiring of DS18B20 temperature sensor ==
... ... @@ -178,7 +178,6 @@
178 178  (% style="display:none" %)
179 179  
180 180  
181 -
182 182  == 1.10 Mechanical ==
183 183  
184 184  === 1.10.1 for LB version ===
... ... @@ -185,9 +185,6 @@
185 185  
186 186  [[image:image-20250409174350-1.jpeg]]
187 187  
188 -
189 -
190 -
191 191  === 1.10.2 for LS version ===
192 192  
193 193  
... ... @@ -386,7 +386,7 @@
386 386  
387 387  ==== (% style="color:#4472c4" %)**Humidity**(%%) ====
388 388  
389 -Read:0x(0197)=412    Value:  412 / 10=41.2, So 41.2%
386 +Read:0x(0197)=412    Value:  407 / 10=40.7, So 40.7%
390 390  
391 391  
392 392  ==== (% style="color:#4472c4" %)**Alarm Flag & MOD & Level of PA8**(%%) ====
... ... @@ -422,45 +422,49 @@
422 422  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.
423 423  
424 424  
425 -=== 2.5.1 Ways to get datalog via LoRaWAN ===
422 +=== 2.5.1 How datalog works ===
426 426  
427 427  
428 -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.
429 429  
430 430  * (((
431 431  a) S31x-LB/LS will do an ACK check for data records sending to make sure every data arrive server.
432 432  )))
433 433  * (((
434 -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 +
435 435  )))
436 436  
437 -=== 2.5.2 Unix TimeStamp ===
436 +=== 2.5.2 Enable Datalog ===
438 438  
439 439  
440 -S31x-LB/LS uses Unix TimeStamp format based on
439 +User need to make sure below two settings are enable to use datalog;
441 441  
442 -[[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
443 443  
444 -User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
445 445  
446 -Below is the converter example
447 447  
448 -[[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).
449 449  
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.**
450 450  
451 -So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
452 452  
451 +=== 2.5.3 Unix TimeStamp ===
453 453  
454 -=== 2.5.3 Set Device Time ===
455 455  
454 +S31x-LB/LS uses Unix TimeStamp format based on
456 456  
457 -User need to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via MAC command.
456 +[[image:image-20250328173339-5.jpeg]]
458 458  
459 -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/]] :
460 460  
461 -(% 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
462 462  
462 +[[image:image-20250328173355-6.jpeg]]
463 463  
464 +
464 464  === 2.5.4 Datalog Uplink payload (FPORT~=3) ===
465 465  
466 466