Skip to Content
Last modified by Xiaoling on 2025/07/10 16:21
From version 142.2
edited by Xiaoling
on 2025/06/10 15:26
Change comment: There is no comment for this version
To version 146.2
edited by Mengting Qiu
on 2025/07/08 10:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.ting
Content
... ... @@ -245,20 +245,16 @@
245 245  
246 246  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
247 247  |=(% 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
248 -|[[image:1749521239729-288.png]] 1~~3s|(% style="background-color:#f2f2f2; width:117px" %)Send an uplink|(% style="background-color:#f2f2f2; width:225px" %)(((
249 -
250 -
248 +|[[image:1749540420016-961.png]] 1~~3s|(% style="background-color:#f2f2f2; width:117px" %)Send an uplink|(% style="background-color:#f2f2f2; width:225px" %)(((
251 251  If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, blue led will blink once.
252 252  Meanwhile, BLE module will be active and user can connect via BLE to configure device.
253 253  )))
254 -|[[image:1749521245437-170.png]] >3s|(% style="background-color:#f2f2f2; width:117px" %)Active Device|(% style="background-color:#f2f2f2; width:225px" %)(((
255 -
256 -
252 +|[[image:1749540423574-437.png]] >3s|(% style="background-color:#f2f2f2; width:117px" %)Active Device|(% style="background-color:#f2f2f2; width:225px" %)(((
257 257  Green led will fast blink 5 times, device will enter OTA mode for 3 seconds. And then start to JOIN LoRaWAN network.
258 258  Green led will solidly turn on for 5 seconds after joined in network.
259 259  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.
260 260  )))
261 -|[[image:1749521282079-419.png]] x5|(% style="background-color:#f2f2f2; width:117px" %)Deactivate Device|(% style="background-color:#f2f2f2; width:225px" %)Red led will solid on for 5 seconds. Means PS-LB is in Deep Sleep Mode.
257 +|[[image:1749540397649-875.png]] x5|(% style="background-color:#f2f2f2; width:117px" %)Deactivate Device|(% style="background-color:#f2f2f2; width:225px" %)Red led will solid on for 5 seconds. Means PS-LB is in Deep Sleep Mode.
262 262  
263 263  == 1.8 Pin Mapping ==
264 264  
... ... @@ -628,43 +628,52 @@
628 628  == 2.6 Datalog Feature (Since V1.1) ==
629 629  
630 630  
631 -When a user wants to retrieve sensor value, he can send a poll command from the IoT platform to ask the sensor to send value in the required time slot.
627 +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.
632 632  
633 633  
634 -=== 2.6.1 Unix TimeStamp ===
630 +=== 2.5.1 How datalog works ===
635 635  
636 636  
637 -PS-LB uses Unix TimeStamp format based on
633 +PS-LB/LS will wait for ACK for every uplink, when there is no LoRaWAN network,PS-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.
638 638  
639 -[[image:image-20250401163826-3.jpeg]]
635 +* (((
636 +a) PS-LB/LS will do an ACK check for data records sending to make sure every data arrive server.
637 +)))
638 +* (((
639 +b) PS-LB/LS will send data in **CONFIRMED Mode**, but PS-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 PS-LB/LS gets a ACK, PS-LB/LS will consider there is a network connection and resend all NONE-ACK messages.
640 640  
641 -Users can get this time from the link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
641 +
642 +)))
642 642  
643 -Below is the converter example:
644 +=== 2.5.2 Enable Datalog ===
644 644  
645 -[[image:image-20250401163906-4.jpeg]]
646 646  
647 +User need to make sure below two settings are enable to use datalog;
647 647  
648 -=== 2.6.2 Set Device Time ===
649 +* (% 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.
650 +* (% 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.
649 649  
650 650  
651 -There are two ways to set the device's time:
652 652  
654 +Once PS-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).
653 653  
654 -~1. Through LoRaWAN MAC Command (Default settings)
656 +(% 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.**
655 655  
656 -Users need to set SYNCMOD=1 to enable sync time via the MAC command.
657 657  
658 -Once CPL01 Joined the LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to CPL01. If CPL01 fails to get the time from the server, CPL01 will use the internal time and wait for the next time request ~[[[via Device Status (FPORT=5)>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.1DeviceStatus2CFPORT3D5]]].
659 +=== 2.6.1 Unix TimeStamp ===
659 659  
660 -Note: LoRaWAN Server needs to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature.
661 661  
662 +PS-LB uses Unix TimeStamp format based on
662 662  
663 - 2. Manually Set Time
664 +[[image:image-20250401163826-3.jpeg]]
664 664  
665 -Users need to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
666 +Users can get this time from the link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
666 666  
668 +Below is the converter example:
667 667  
670 +[[image:image-20250401163906-4.jpeg]]
671 +
672 +
668 668  === 2.6.3 Poll sensor value ===
669 669  
670 670  Users can poll sensor values based on timestamps. Below is the downlink command.
1749540397649-875.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +1.4 KB
Content
1749540420016-961.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +1.9 KB
Content
1749540423574-437.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +1.9 KB
Content