Summary

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

Details

Page properties

Content

...	...	@@ -4,7 +4,6 @@
4	4
5	5	**Contents:**
6	6
7		-{{toc/}}
8	8
9	9
10	10
...	...	@@ -11,7 +11,6 @@
11	11
12	12
13	13
14		-
15	15	= 1.  Introduction =
16	16
17	17	== 1.1 ​ What is LoRaWAN LiDAR ToF Distance Sensor ==
...	...	@@ -216,7 +216,7 @@
216	216
217	217
218	218
219		-=== 2.3.2  DS18B20 Temperature sensor ===
	217	+=== 2.3.2 DS18B20 Temperature sensor ===
220	220
221	221	This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
222	222
...	...	@@ -229,35 +229,33 @@
229	229
230	230
231	231
232		-=== 2.3.3  Distance ===
	230	+=== 2.3.3 Soil pH ===
233	233
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.
	232	+Range: 0 ~~ 14 pH
235	235
	234	+**Example:**
236	236
237		-**Example**:
	236	+(% style="color:#037691" %)** 0x02B7(H) = 695(D) = 6.95pH**
238	238
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.
240	240
241	241
	240	+=== 2.3.4 Soil Temperature ===
242	242
243		-=== 2.3.4  Distance signal strength ===
	242	+Get Soil Temperature
244	244
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.
246	246
247		-
248	248	**Example**:
249	249
250		-If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
	247	+If payload is: **0105H**:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
251	251
252		-Customers can judge whether they need to adjust the environment based on the signal strength.
	249	+If payload is: **FF3FH** :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
253	253
254	254
255	255
256		-=== 2.3.5  Interrupt Pin ===
	253	+=== 2.3.5 Interrupt Pin ===
257	257
258	258	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.
259	259
260		-Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>path:#pins]].
261	261
262	262	**Example:**
263	263
...	...	@@ -267,18 +267,8 @@
267	267
268	268
269	269
270		-=== 2.3.6  LiDAR temp ===
	266	+=== 2.3.6 Message Type ===
271	271
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		-
282	282	(((
283	283	For a normal uplink payload, the message type is always 0x01.
284	284	)))
...	...	@@ -292,11 +292,10 @@
292	292	|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
293	293	|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]]
294	294	|(% 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"]]
295	295
	283	+=== 2.3.7 Decode payload in The Things Network ===
296	296
297		-
298		-=== 2.3.8  Decode payload in The Things Network ===
299		-
300	300	While using TTN network, you can add the payload format to decode the payload.
301	301
302	302
...	...	@@ -463,7 +463,7 @@
463	463	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
464	464	* 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)
465	465
466		-=== 2.6.3  CN470-510 (CN470) ===
	451	+=== 2.6.3 CN470-510 (CN470) ===
467	467
468	468	(((
469	469	Used in China, Default use CHE=1
...	...	@@ -552,7 +552,7 @@
552	552
553	553
554	554
555		-=== 2.6.4  AU915-928(AU915) ===
	540	+=== 2.6.4 AU915-928(AU915) ===
556	556
557	557	(((
558	558	Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
...	...	@@ -573,7 +573,7 @@
573	573	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
574	574	* 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)
575	575
576		-=== 2.6.5  AS920-923 & AS923-925 (AS923) ===
	561	+=== 2.6.5 AS920-923 & AS923-925 (AS923) ===
577	577
578	578	(((
579	579	(% style="color:blue" %)**Default Uplink channel:**
...	...	@@ -682,7 +682,7 @@
682	682
683	683
684	684
685		-=== 2.6.6  KR920-923 (KR920) ===
	670	+=== 2.6.6 KR920-923 (KR920) ===
686	686
687	687	(((
688	688	(% style="color:blue" %)**Default channel:**
...	...	@@ -755,7 +755,7 @@
755	755
756	756
757	757
758		-=== 2.6.7  IN865-867 (IN865) ===
	743	+=== 2.6.7 IN865-867 (IN865) ===
759	759
760	760	(((
761	761	(% style="color:blue" %)**Uplink:**