Skip to Content
Last modified by Mengting Qiu on 2025/07/01 15:58
From version 103.3
edited by Xiaoling
on 2025/06/13 11:53
Change comment: There is no comment for this version
To version 104.6
edited by Edwin Chen
on 2025/06/27 11:05
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
... ... @@ -419,21 +419,33 @@
419 419  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.
420 420  
421 421  
422 -=== 2.5.1 Ways to get datalog via LoRaWAN ===
422 +=== 2.5.1 How datalog works ===
423 423  
424 424  
425 -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.
426 426  
427 427  * (((
428 428  a) S31x-LB/LS will do an ACK check for data records sending to make sure every data arrive server.
429 429  )))
430 430  * (((
431 -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 +
432 432  )))
433 433  
434 -=== 2.5.2 Unix TimeStamp ===
436 +=== 2.5.2 Enable Datalog ===
435 435  
436 436  
439 +User need to make sure below two settings are enable to use datalog;
440 +
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 +
444 +
445 +
446 +=== 2.5.3 Unix TimeStamp ===
447 +
448 +
437 437  S31x-LB/LS uses Unix TimeStamp format based on
438 438  
439 439  [[image:image-20250328173339-5.jpeg]]
... ... @@ -445,12 +445,10 @@
445 445  [[image:image-20250328173355-6.jpeg]]
446 446  
447 447  
448 -So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
449 449  
461 +=== 2.5.4 Set Device Time ===
450 450  
451 -=== 2.5.3 Set Device Time ===
452 452  
453 -
454 454  User need to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via MAC command.
455 455  
456 456  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).