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

Summary

Details

Page properties
Content
... ... @@ -624,19 +624,19 @@
624 624  == 2.6 Datalog Feature (Since V1.1) ==
625 625  
626 626  
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.
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, PS-LB will store the reading for future retrieving purposes.
628 628  
629 629  
630 630  === 2.5.1 How datalog works ===
631 631  
632 632  
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.
633 +PS-LB will wait for ACK for every uplink, when there is no LoRaWAN network,PS-LB 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.
634 634  
635 635  * (((
636 -a) PS-LB/LS will do an ACK check for data records sending to make sure every data arrive server.
636 +a) PS-LB will do an ACK check for data records sending to make sure every data arrive server.
637 637  )))
638 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.
639 +b) PS-LB will send data in **CONFIRMED Mode**, but PS-LB 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 gets a ACK, PS-LB will consider there is a network connection and resend all NONE-ACK messages.
640 640  
641 641  
642 642  )))
... ... @@ -651,7 +651,7 @@
651 651  
652 652  
653 653  
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).
654 +Once PS-LB Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to PS-LB. If PS-LB fails to get the time from the server, PS-LB will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
655 655  
656 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.**
657 657