Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Edwin
	1	+XWiki.Xiaoling

Content

...	...	@@ -1,5 +1,5 @@
1	1	(% style="text-align:center" %)
2		-[[image:image-20220523115324-1.jpeg||height="317" width="317"]]
	2	+[[image:image-20220523115324-1.jpeg||height="500" width="500"]]
3	3
4	4
5	5	**LHT65N LoRaWAN Temperature & Humidity Sensor Manual**
...	...	@@ -7,6 +7,10 @@
7	7
8	8
9	9
	10	+
	11	+
	12	+
	13	+
10	10	**Table of Contents：**
11	11
12	12	{{toc/}}
...	...	@@ -14,8 +14,9 @@
14	14
15	15
16	16
17		-= 1. Introduction =
18	18
	22	+= 1.Introduction =
	23	+
19	19	== 1.1 What is LHT65N Temperature & Humidity Sensor ==
20	20
21	21	(((
...	...	@@ -134,7 +134,7 @@
134	134
135	135	[[image:image-20220515123819-1.png||height="379" width="317"]]
136	136
137		-[[image:image-20220523153201-19.png||height="180" width="818"]]
	142	+[[image:image-20220523153201-19.png||height="163" width="739"]]
138	138
139	139	== 2.3 Example to join LoRaWAN network ==
140	140
...	...	@@ -219,7 +219,7 @@
219	219	[[Humidity>>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.4Built-inHumidity]]
220	220	)))
221	221	)))|(% style="width:47px" %)(((
222		-[[Ext>>path:http://8.211.40.43:8080/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/#H2.4.5Ext23]] #
	227	+[[Ext>>path:#Extension_Sensor]] #
223	223	)))|(% style="width:51px" %)(((
224	224	[[Ext value>>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.6Extvalue]]
225	225	)))
...	...	@@ -401,14 +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.
	409	+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 ===
	411	+=== 2.6.1 Unix TimeStamp ===
407	407
408		-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.
409		-
410		-=== 2.6.2 Unix TimeStamp ===
411		-
412	412	LHT65N uses Unix TimeStamp format based on
413	413
414	414	[[image:image-20220523001219-11.png||height="97" width="627"]]
...	...	@@ -426,7 +426,7 @@
426	426
427	427	So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
428	428
429		-=== 2.6.3 Set Device Time ===
	430	+=== 2.6.2 Set Device Time ===
430	430
431	431	(((
432	432	There are two ways to set device’s time:
...	...	@@ -460,7 +460,7 @@
460	460	User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
461	461	)))
462	462
463		-=== 2.6.4 Poll sensor value ===
	464	+=== 2.6.3 Poll sensor value ===
464	464
465	465	User can poll sensor value based on timestamps from the server. Below is the downlink command.
466	466
...	...	@@ -471,7 +471,7 @@
471	471	)))
472	472
473	473	(((
474		-For example, downlink command (% style="display:none" %) (%%)**31 5FC5F350 5FC6 0160 05**
	475	+For example, downlink command **31 5FC5F350 5FC6 0160 05**
475	475	)))
476	476
477	477	(((
...	...	@@ -483,7 +483,7 @@
483	483	)))
484	484
485	485
486		-=== 2.6.5 Datalog Uplink payload ===
	487	+=== 2.6.4 Datalog Uplink payload ===
487	487
488	488	The Datalog poll reply uplink will use below payload format.
489	489