Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -205,10 +205,10 @@
205	205	|(% style="width:97px" %)(((
206	206	**Value**
207	207	)))|(% style="width:39px" %)(((
208		-[[BAT>>path:http://8.211.40.43/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/#H2.4.2BAT-BatteryInfo]]
	208	+[[BAT>>||anchor="H2.4.2BAT-BatteryInfo"]]
209	209	)))|(% style="width:100px" %)(((
210	210	(((
211		-[[Built-In Temperature>>http://8.211.40.43/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/#H2.4.3Built-inTemperature]]
	211	+[[Built-In Temperature>>||anchor="H2.4.3Built-inTemperature"]]
212	212	)))
213	213	)))|(% style="width:77px" %)(((
214	214	(((
...	...	@@ -401,10 +401,17 @@
401	401
402	402	== 2.6 Datalog Feature ==
403	403
404		-This feature is always enabled. When user wants to retrieve the sensor value, he can send a poll command from the IoT platform to ask LHT65N to send the value in the required time slot.
	404	+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.
405	405
406		-=== 2.6.1 Unix TimeStamp ===
	406	+=== 2.6.1 Ways to get datalog via LoRaWAN ===
407	407
	408	+There are two methods:
	409	+
	410	+1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specify time range.
	411	+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.
	412	+
	413	+=== 2.6.2 Unix TimeStamp ===
	414	+
408	408	LHT65N uses Unix TimeStamp format based on
409	409
410	410	[[image:image-20220523001219-11.png||height="97" width="627"]]
...	...	@@ -422,7 +422,7 @@
422	422
423	423	So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
424	424
425		-=== 2.6.2 Set Device Time ===
	432	+=== 2.6.3 Set Device Time ===
426	426
427	427	(((
428	428	There are two ways to set device’s time:
...	...	@@ -456,7 +456,7 @@
456	456	User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
457	457	)))
458	458
459		-=== 2.6.3 Poll sensor value ===
	466	+=== 2.6.4 Poll sensor value ===
460	460
461	461	User can poll sensor value based on timestamps from the server. Below is the downlink command.
462	462
...	...	@@ -479,7 +479,7 @@
479	479	)))
480	480
481	481
482		-=== 2.6.4 Datalog Uplink payload ===
	489	+=== 2.6.5 Datalog Uplink payload ===
483	483
484	484	The Datalog poll reply uplink will use below payload format.
485	485
...	...	@@ -989,6 +989,22 @@
989	989
990	990	* Example: 0xA301 ~/~/Same as AT+CLRDTA
991	991
	999	+== 4.13 Auto Send None-ACK messages ==
	1000	+
	1001	+Feature: LHT65N will wait for ACK for each uplink, If LHT65N doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. LHT65N keeps sending messages in normal periodically. Once LHT65N gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
	1002	+
	1003	+
	1004	+**AT Command: AT+PNACKMD**
	1005	+
	1006	+The default factory setting is 0
	1007	+
	1008	+|**Command Example**|**Function**|**Response**
	1009	+|AT+PNACKMD=1|Poll None-ACK message|OK
	1010	+
	1011	+**Downlink Command: 0x34**
	1012	+
	1013	+* Example: 0x3401 ~/~/Same as AT+PNACKMD=1
	1014	+
992	992	= 5. Battery & How to replace =
993	993
994	994	== 5.1 Battery Type ==