Summary

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

Details

Page properties

Content

...	...	@@ -4,6 +4,7 @@
4	4
5	5	**Contents:**
6	6
	7	+{{toc/}}
7	7
8	8
9	9
...	...	@@ -10,6 +10,7 @@
10	10
11	11
12	12
	14	+
13	13	= 1.  Introduction =
14	14
15	15	== 1.1 ​ What is LoRaWAN LiDAR ToF Distance Sensor ==
...	...	@@ -214,7 +214,7 @@
214	214
215	215
216	216
217		-=== 2.3.2 DS18B20 Temperature sensor ===
	219	+=== 2.3.2  DS18B20 Temperature sensor ===
218	218
219	219	This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
220	220
...	...	@@ -227,33 +227,35 @@
227	227
228	228
229	229
230		-=== 2.3.3 Soil pH ===
	232	+=== 2.3.3  Distance ===
231	231
232		-Range: 0 ~~ 14 pH
	234	+Represents the distance value of the measurement output, the default unit is cm, and the value range parsed as a decimal number is 0-1200. In actual use, when the signal strength value Strength.
233	233
234		-**Example:**
235	235
236		-(% style="color:#037691" %)** 0x02B7(H) = 695(D) = 6.95pH**
	237	+**Example**:
237	237
	239	+If the data you get from the register is 0x0B 0xEA, the distance between the sensor and the measured object is 0BEA(H) = 3050 (D)/10 = 305cm.
238	238
239	239
240		-=== 2.3.4 Soil Temperature ===
241	241
242		-Get Soil Temperature
	243	+=== 2.3.4  Distance signal strength ===
243	243
	245	+Refers to the signal strength, the default output value will be between 0-65535. When the distance measurement gear is fixed, the farther the distance measurement is, the lower the signal strength; the lower the target reflectivity, the lower the signal strength. When Strength is greater than 100 and not equal to 65535, the measured value of Dist is considered credible.
244	244
	247	+
245	245	**Example**:
246	246
247		-If payload is: **0105H**:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
	250	+If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
248	248
249		-If payload is: **FF3FH** :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
	252	+Customers can judge whether they need to adjust the environment based on the signal strength.
250	250
251	251
252	252
253		-=== 2.3.5 Interrupt Pin ===
	256	+=== 2.3.5  Interrupt Pin ===
254	254
255	255	This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H3.2SetInterruptMode"]] for the hardware and software set up.
256	256
	260	+Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>path:#pins]].
257	257
258	258	**Example:**
259	259
...	...	@@ -263,8 +263,18 @@
263	263
264	264
265	265
266		-=== 2.3.6 Message Type ===
	270	+=== 2.3.6  LiDAR temp ===
267	267
	272	+Characterize the internal temperature value of the sensor.
	273	+
	274	+**Example: **
	275	+If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
	276	+If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
	277	+
	278	+
	279	+
	280	+=== 2.3.7  Message Type ===
	281	+
268	268	(((
269	269	For a normal uplink payload, the message type is always 0x01.
270	270	)))
...	...	@@ -278,10 +278,11 @@
278	278	|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
279	279	|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]]
280	280	|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H3.4GetFirmwareVersionInfo"]]
281		-|(% style="width:160px" %)0x03|(% style="width:163px" %)Reply Calibration Info|(% style="width:173px" %)[[Calibration Payload>>||anchor="H2.7Calibration"]]
282	282
283		-=== 2.3.7 Decode payload in The Things Network ===
284	284
	297	+
	298	+=== 2.3.8  Decode payload in The Things Network ===
	299	+
285	285	While using TTN network, you can add the payload format to decode the payload.
286	286
287	287
...	...	@@ -448,7 +448,7 @@
448	448	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
449	449	* Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include)
450	450
451		-=== 2.6.3 CN470-510 (CN470) ===
	466	+=== 2.6.3  CN470-510 (CN470) ===
452	452
453	453	(((
454	454	Used in China, Default use CHE=1
...	...	@@ -537,7 +537,7 @@
537	537
538	538
539	539
540		-=== 2.6.4 AU915-928(AU915) ===
	555	+=== 2.6.4  AU915-928(AU915) ===
541	541
542	542	(((
543	543	Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
...	...	@@ -558,7 +558,7 @@
558	558	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
559	559	* Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include)
560	560
561		-=== 2.6.5 AS920-923 & AS923-925 (AS923) ===
	576	+=== 2.6.5  AS920-923 & AS923-925 (AS923) ===
562	562
563	563	(((
564	564	(% style="color:blue" %)**Default Uplink channel:**
...	...	@@ -667,7 +667,7 @@
667	667
668	668
669	669
670		-=== 2.6.6 KR920-923 (KR920) ===
	685	+=== 2.6.6  KR920-923 (KR920) ===
671	671
672	672	(((
673	673	(% style="color:blue" %)**Default channel:**
...	...	@@ -740,7 +740,7 @@
740	740
741	741
742	742
743		-=== 2.6.7 IN865-867 (IN865) ===
	758	+=== 2.6.7  IN865-867 (IN865) ===
744	744
745	745	(((
746	746	(% style="color:blue" %)**Uplink:**