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**
...	...	@@ -6,7 +6,6 @@
6	6
7	7
8	8
9		-
10	10	**Table of Contents：**
11	11
12	12	{{toc/}}
...	...	@@ -13,9 +13,8 @@
13	13
14	14
15	15
	15	+= 1.Introduction =
16	16
17		-= 1. Introduction =
18		-
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"]]
	135	+[[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]] #
	220	+[[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	)))
...	...	@@ -300,7 +300,7 @@
300	300
301	301	Timestamp mode is designed for LHT65N with E3 probe, it will send the uplink payload with Unix timestamp. With the limitation of 11 bytes (max distance of AU915/US915/AS923 band), the time stamp mode will be lack of BAT voltage field, instead, it shows the battery status. The payload is as below:
302	302
303		-(% border="1" style="background-color:#ffffcc; color:green; width:510px" %)
	301	+(% border="1" style="background-color:#ffffcc; color:green; width:468px" %)
304	304	|(% style="width:96px" %)(((
305	305	**Size(bytes)**
306	306	)))|(% style="width:71px" %)(((
...	...	@@ -401,18 +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.
	402	+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 ===
	404	+=== 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>PollSensorValue].
411		-1.
412		-
413		-
414		-=== 2.6.2 Unix TimeStamp ===
415		-
416	416	LHT65N uses Unix TimeStamp format based on
417	417
418	418	[[image:image-20220523001219-11.png||height="97" width="627"]]
...	...	@@ -430,7 +430,7 @@
430	430
431	431	So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
432	432
433		-=== 2.6.3 Set Device Time ===
	423	+=== 2.6.2 Set Device Time ===
434	434
435	435	(((
436	436	There are two ways to set device’s time:
...	...	@@ -464,7 +464,7 @@
464	464	User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
465	465	)))
466	466
467		-=== [[2.6.4 Poll sensor value>>2.6.4 Poll sensor value||anchor="PollSensorValue"]] ===
	457	+=== 2.6.3 Poll sensor value ===
468	468
469	469	User can poll sensor value based on timestamps from the server. Below is the downlink command.
470	470
...	...	@@ -475,7 +475,7 @@
475	475	)))
476	476
477	477	(((
478		-For example, downlink command (% style="display:none" %) (%%)**31 5FC5F350 5FC6 0160 05**
	468	+For example, downlink command **31 5FC5F350 5FC6 0160 05**
479	479	)))
480	480
481	481	(((
...	...	@@ -487,7 +487,7 @@
487	487	)))
488	488
489	489
490		-=== 2.6.5 Datalog Uplink payload ===
	480	+=== 2.6.4 Datalog Uplink payload ===
491	491
492	492	The Datalog poll reply uplink will use below payload format.
493	493
...	...	@@ -495,7 +495,7 @@
495	495	**Retrieval data payload**
496	496	)))
497	497
498		-(% border="1" style="background-color:#ffffcc; color:green; width:510px" %)
	488	+(% border="1" style="background-color:#ffffcc; color:green; width:469px" %)
499	499	|(% style="width:93px" %)(((
500	500	(((
501	501	**Size(bytes)**