Skip to Content
Last modified by Mengting Qiu on 2025/07/08 11:11
From version 239.1
edited by Xiaoling
on 2025/06/10 16:05
Change comment: There is no comment for this version
To version 239.2
edited by Mengting Qiu
on 2025/07/08 11:11
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
... ... @@ -891,18 +891,35 @@
891 891  Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, LDS25-LB/LS will store the reading for future retrieving purposes.
892 892  
893 893  
894 -=== 2.6.1 Ways to get datalog via LoRaWAN ===
894 +=== 2.5.1 How datalog works ===
895 895  
896 896  
897 -Set PNACKMD=1, LDS25-LB/LS will wait for ACK for every uplink, when there is no LoRaWAN network, LDS25-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.
897 +LDS25-LB/LS will wait for ACK for every uplink, when there is no LoRaWAN network,LDS25-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.
898 898  
899 899  * (((
900 900  a) LDS25-LB/LS will do an ACK check for data records sending to make sure every data arrive server.
901 901  )))
902 902  * (((
903 -b) LDS25-LB/LS will send data in **CONFIRMED Mode** when PNACKMD=1, but LDS25-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 LDS25-LB/LS gets a ACK, LDS25-LB/LS will consider there is a network connection and resend all NONE-ACK messages.
903 +b) LDS25-LB/LS will send data in **CONFIRMED Mode**, but LDS25-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 LDS25-LB/LS gets a ACK, LDS25-LB/LS will consider there is a network connection and resend all NONE-ACK messages.
904 +
905 +
904 904  )))
905 905  
908 +=== 2.5.2 Enable Datalog ===
909 +
910 +
911 +User need to make sure below two settings are enable to use datalog;
912 +
913 +* (% 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.
914 +* (% 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.
915 +
916 +
917 +
918 +Once LDS25-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 LDS25-LB/LS. If LDS25-LB/LS fails to get the time from the server, LDS25-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).
919 +
920 +(% 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.**
921 +
922 +
906 906  === 2.6.2 Unix Timestamp ===
907 907  
908 908  
... ... @@ -963,6 +963,8 @@
963 963  
964 964  
965 965  
983 +
984 +
966 966  == 2.7 Frequency Plans ==
967 967  
968 968