Skip to Content
Last modified by Mengting Qiu on 2025/07/03 16:36
From version 70.1
edited by Mengting Qiu
on 2025/05/21 14:53
Change comment: There is no comment for this version
To version 72.1
edited by Mengting Qiu
on 2025/07/03 16:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,6 @@
1 1  (% style="display:none" %) (%%)
2 2  
3 -(% style="text-align:center" %)
4 -[[image:image-20240108161155-2.png]]
3 +[[image:image-20240108161155-2.png||data-xwiki-image-style-alignment="center"]]
5 5  
6 6  
7 7  
... ... @@ -128,16 +128,16 @@
128 128  
129 129  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
130 130  |=(% 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**
131 -|(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)(((
130 +|[[image:1749536870332-565.png]] 1~~3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)(((
132 132  If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once.
133 133  Meanwhile, BLE module will be active and user can connect via BLE to configure device.
134 134  )))
135 -|(% style="width:167px" %)Pressing ACT for more than 3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)(((
134 +|[[image:1749536872361-767.png]] >3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)(((
136 136  (% style="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.
137 137  (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network.
138 138  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.
139 139  )))
140 -|(% style="width:167px" %)Fast press ACT 5 times.|(% 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.
139 +|[[image:1749536881052-376.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.
141 141  
142 142  == 1.7 BLE connection ==
143 143  
... ... @@ -666,46 +666,54 @@
666 666  
667 667  == 2.5 Datalog Feature ==
668 668  
668 + Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, DS03A-LB/LS will store the reading for future retrieving purposes.
669 669  
670 -(% style="color:blue" %)**Datalog Feature** (%%)is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, DS03A-LB/LS will store the reading for future retrieving purposes.
671 671  
672 -(% style="color:red" %)**Note:After the device is reset,in cumulative counting mode,the last stored count value will be read as the initial value.**
671 +=== 2.5.1 How datalog works ===
673 673  
674 674  
675 -=== 2.5.1 Ways to get datalog via LoRaWAN ===
674 +DS03A-LB/LS will wait for ACK for every uplink, when there is no LoRaWAN network,DS03A-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.
676 676  
676 +* (((
677 +a) DS03A-LB/LS will do an ACK check for data records sending to make sure every data arrive server.
678 +)))
679 +* (((
680 +b) DS03A-LB/LS will send data in **CONFIRMED Mode**, but DS03A-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 DS03A-LB/LS gets a ACK, DS03A-LB/LS will consider there is a network connection and resend all NONE-ACK messages.
677 677  
678 -Set PNACKMD=1, DS03A-LB/LS will wait for ACK for every uplink, when there is no LoRaWAN network, DS03A-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.
682 +
683 +)))
679 679  
680 -* a) DS03A-LB/LS will do an ACK check for data records sending to make sure every data arrive server.
681 -* b) DS03A-LB/LS will send data in **CONFIRMED Mode** when PNACKMD=1, but DS03A-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 DS03A-LB/LS gets a ACK, DS03A-LB/LS will consider there is a network connection and resend all NONE-ACK Message.
685 +=== 2.5.2 Enable Datalog ===
682 682  
683 -=== 2.5.2 Unix TimeStamp ===
684 684  
688 +User need to make sure below two settings are enable to use datalog;
685 685  
686 -DS03A-LB/LS uses Unix TimeStamp format based on
690 +* (% 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.
691 +* (% 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.
687 687  
688 -[[image:image-20250331163638-7.jpeg]]
689 689  
690 -User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
691 691  
692 -Below is the converter example
695 +Once DS03A-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 DS03A-LB/LS. If DS03A-LB/LS fails to get the time from the server, DS03A-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).
693 693  
694 -[[image:image-20250331163648-8.jpeg]]
697 +(% 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.**
695 695  
696 -So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
697 697  
700 +=== 2.5.3 Unix TimeStamp ===
698 698  
699 -=== 2.5.3 Set Device Time ===
700 700  
703 +DS03A-LB/LS uses Unix TimeStamp format based on
701 701  
702 -User need to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via MAC command.
705 +[[image:image-20250331163638-7.jpeg]]
703 703  
704 -Once DS03A-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 DS03A-LB/LS. If DS03A-LB/LS fails to get the time from the server, DS03A-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).
707 +User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
705 705  
706 -(% 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 and loriot support but TTN 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 v2 if SYNCMOD=1.**
709 +Below is the converter example
707 707  
711 +[[image:image-20250331163648-8.jpeg]]
708 708  
713 +So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
714 +
715 +
709 709  == 2.6 ​Show Data in DataCake IoT Server ==
710 710  
711 711  
1749536870332-565.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +1.9 KB
Content
1749536872361-767.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +1.9 KB
Content
1749536881052-376.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +1.4 KB
Content