Skip to Content
Last modified by Mengting Qiu on 2025/07/01 15:58
From version 106.2
edited by Mengting Qiu
on 2025/07/01 14:52
Change comment: There is no comment for this version
To version 103.4
edited by Xiaoling
on 2025/06/13 11:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Xiaoling
Content
... ... @@ -383,7 +383,7 @@
383 383  
384 384  ==== (% style="color:#4472c4" %)**Humidity**(%%) ====
385 385  
386 -Read:0x(0197)=412    Value:  407 / 10=40.7, So 40.7%
386 +Read:0x(0197)=412    Value:  412 / 10=41.2, So 41.2%
387 387  
388 388  
389 389  ==== (% style="color:#4472c4" %)**Alarm Flag & MOD & Level of PA8**(%%) ====
... ... @@ -419,49 +419,45 @@
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 How datalog works ===
422 +=== 2.5.1 Ways to get datalog via LoRaWAN ===
423 423  
424 424  
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.
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.
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**, 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 -
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.
434 434  )))
435 435  
436 -=== 2.5.2 Enable Datalog ===
434 +=== 2.5.2 Unix TimeStamp ===
437 437  
438 438  
439 -User need to make sure below two settings are enable to use datalog;
437 +S31x-LB/LS uses Unix TimeStamp format based on
440 440  
441 -* (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via LoRaWAN MAC command
442 -* (% style="color:blue" %)**PNACKMD=1**(%%)** **to enable datalog feature
439 +[[image:image-20250328173339-5.jpeg]]
443 443  
441 +User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
444 444  
443 +Below is the converter example
445 445  
446 -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).
445 +[[image:image-20250328173355-6.jpeg]]
447 447  
448 -(% 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.**
449 449  
448 +So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
450 450  
451 -=== 2.5.3 Unix TimeStamp ===
452 452  
451 +=== 2.5.3 Set Device Time ===
453 453  
454 -S31x-LB/LS uses Unix TimeStamp format based on
455 455  
456 -[[image:image-20250328173339-5.jpeg]]
454 +User need to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via MAC command.
457 457  
458 -User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
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).
459 459  
460 -Below is the converter example
458 +(% 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.**
461 461  
462 -[[image:image-20250328173355-6.jpeg]]
463 463  
464 -
465 465  === 2.5.4 Datalog Uplink payload (FPORT~=3) ===
466 466  
467 467