Changes for page LHT52 - LoRaWAN Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/30 14:27
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -649,6 +649,8 @@ 649 649 (% _mstvisible="1" %) 650 650 [[image:image-20220523000825-10.png||_mstalt="450619" _mstvisible="3" height="413" width="728"]] 651 651 652 + 653 + 652 652 (% _mstvisible="1" %) 653 653 == (% _msthash="350454" _msttexthash="323544" _mstvisible="3" %)2.6 Datalog Feature(%%) == 654 654 ... ... @@ -655,6 +655,7 @@ 655 655 (% _msthash="315262" _msttexthash="32283004" _mstvisible="1" %) 656 656 Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, LHT65N will store the reading for future retrieving purposes. There are two ways for IoT servers to get datalog from LHT65N. 657 657 660 + 658 658 (% _mstvisible="1" %) 659 659 === (% _msthash="886158" _msttexthash="842426" _mstvisible="3" %)2.6.1 Ways to get datalog via LoRaWAN(%%) === 660 660 ... ... @@ -665,6 +665,8 @@ 665 665 1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specify time range. 666 666 1. Set [[PNACKMD=1>>||anchor="H4.13AutoSendNone-ACKmessages"]], LHT65N will wait for ACK for every uplink, when there is no LoRaWAN network, LHT65N will store the sensor data, and it will send all messages after network recover. 667 667 671 + 672 + 668 668 (% _mstvisible="1" %) 669 669 === (% _msthash="369915" _msttexthash="342797" _mstvisible="3" %)2.6.2 Unix TimeStamp(%%) === 670 670 ... ... @@ -693,6 +693,7 @@ 693 693 (% _msthash="315265" _msttexthash="15137317" _mstvisible="1" %) 694 694 So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25 695 695 701 + 696 696 (% _mstvisible="1" %) 697 697 === (% _msthash="359294" _msttexthash="332748" _mstvisible="3" %)2.6.3 Set Device Time(%%) === 698 698 ... ... @@ -742,6 +742,9 @@ 742 742 ((( 743 743 (% _msthash="506076" _msttexthash="7889297" _mstvisible="2" %) 744 744 User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server. 751 + 752 +(% _msthash="506076" _msttexthash="7889297" _mstvisible="2" %) 753 + 745 745 ))) 746 746 747 747 (% _mstvisible="1" %)