Summary

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

Details

Page properties

Content

...	...	@@ -401,17 +401,10 @@
401	401
402	402	== 2.6 Datalog Feature ==
403	403
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.
	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.
405	405
406		-=== 2.6.1 Ways to get datalog via LoRaWAN ===
	406	+=== 2.6.1 Unix TimeStamp ===
407	407
408		-There are two methods:
409		-
410		-1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>poll the value||anchor="H2.6.4Pollsensorvalue"]].
411		-1.
412		-
413		-=== 2.6.2 Unix TimeStamp ===
414		-
415	415	LHT65N uses Unix TimeStamp format based on
416	416
417	417	[[image:image-20220523001219-11.png||height="97" width="627"]]
...	...	@@ -429,7 +429,7 @@
429	429
430	430	So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
431	431
432		-=== 2.6.3 Set Device Time ===
	425	+=== 2.6.2 Set Device Time ===
433	433
434	434	(((
435	435	There are two ways to set device’s time:
...	...	@@ -463,7 +463,7 @@
463	463	User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
464	464	)))
465	465
466		-=== 2.6.4 Poll sensor value ===
	459	+=== 2.6.3 Poll sensor value ===
467	467
468	468	User can poll sensor value based on timestamps from the server. Below is the downlink command.
469	469
...	...	@@ -486,7 +486,7 @@
486	486	)))
487	487
488	488
489		-=== 2.6.5 Datalog Uplink payload ===
	482	+=== 2.6.4 Datalog Uplink payload ===
490	490
491	491	The Datalog poll reply uplink will use below payload format.
492	492