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 ==
...	...	@@ -19,30 +19,18 @@
19	19	(((
20	20
21	21
22		-(((
23	23	The Dragino LLDS12 is a (% style="color:blue" %)**LoRaWAN LiDAR ToF (Time of Flight) Distance Sensor**(%%) for Internet of Things solution. It is capable to measure the distance to an object as close as 10 centimeters (+/- 5cm up to 6m) and as far as 12 meters (+/-1% starting at 6m)!. The LiDAR probe uses laser induction technology for distance measurement.
24		-)))
25	25
26		-(((
27	27	The LLDS12 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
28		-)))
29	29
30		-(((
31	31	It detects the distance between the measured object and the sensor, and uploads the value via wireless to LoRaWAN IoT Server.
32		-)))
33	33
34		-(((
35	35	The LoRa wireless technology used in LLDS12 allows device to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption.
36		-)))
37	37
38		-(((
39	39	LLDS12 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use up to 5 years.
40		-)))
41	41
42		-(((
43	43	Each LLDS12 is pre-load with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect after power on.
44	44	)))
45		-)))
46	46
47	47
48	48	[[image:1654826306458-414.png]]
...	...	@@ -228,7 +228,7 @@
228	228
229	229
230	230
231		-=== 2.3.2  DS18B20 Temperature sensor ===
	217	+=== 2.3.2 DS18B20 Temperature sensor ===
232	232
233	233	This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
234	234
...	...	@@ -241,35 +241,33 @@
241	241
242	242
243	243
244		-=== 2.3.3  Distance ===
	230	+=== 2.3.3 Soil pH ===
245	245
246		-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
247	247
	234	+**Example:**
248	248
249		-**Example**:
	236	+(% style="color:#037691" %)** 0x02B7(H) = 695(D) = 6.95pH**
250	250
251		-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.
252	252
253	253
	240	+=== 2.3.4 Soil Temperature ===
254	254
255		-=== 2.3.4  Distance signal strength ===
	242	+Get Soil Temperature
256	256
257		-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.
258	258
259		-
260	260	**Example**:
261	261
262		-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
263	263
264		-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.
265	265
266	266
267	267
268		-=== 2.3.5  Interrupt Pin ===
	253	+=== 2.3.5 Interrupt Pin ===
269	269
270	270	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.
271	271
272		-Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>path:#pins]].
273	273
274	274	**Example:**
275	275
...	...	@@ -279,18 +279,8 @@
279	279
280	280
281	281
282		-=== 2.3.6  LiDAR temp ===
	266	+=== 2.3.6 Message Type ===
283	283
284		-Characterize the internal temperature value of the sensor.
285		-
286		-**Example: **
287		-If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
288		-If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
289		-
290		-
291		-
292		-=== 2.3.7  Message Type ===
293		-
294	294	(((
295	295	For a normal uplink payload, the message type is always 0x01.
296	296	)))
...	...	@@ -304,11 +304,10 @@
304	304	|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
305	305	|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]]
306	306	|(% 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"]]
307	307
	283	+=== 2.3.7 Decode payload in The Things Network ===
308	308
309		-
310		-=== 2.3.8  Decode payload in The Things Network ===
311		-
312	312	While using TTN network, you can add the payload format to decode the payload.
313	313
314	314
...	...	@@ -475,7 +475,7 @@
475	475	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
476	476	* 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)
477	477
478		-=== 2.6.3  CN470-510 (CN470) ===
	451	+=== 2.6.3 CN470-510 (CN470) ===
479	479
480	480	(((
481	481	Used in China, Default use CHE=1
...	...	@@ -564,7 +564,7 @@
564	564
565	565
566	566
567		-=== 2.6.4  AU915-928(AU915) ===
	540	+=== 2.6.4 AU915-928(AU915) ===
568	568
569	569	(((
570	570	Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
...	...	@@ -585,7 +585,7 @@
585	585	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
586	586	* 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)
587	587
588		-=== 2.6.5  AS920-923 & AS923-925 (AS923) ===
	561	+=== 2.6.5 AS920-923 & AS923-925 (AS923) ===
589	589
590	590	(((
591	591	(% style="color:blue" %)**Default Uplink channel:**
...	...	@@ -694,7 +694,7 @@
694	694
695	695
696	696
697		-=== 2.6.6  KR920-923 (KR920) ===
	670	+=== 2.6.6 KR920-923 (KR920) ===
698	698
699	699	(((
700	700	(% style="color:blue" %)**Default channel:**
...	...	@@ -767,7 +767,7 @@
767	767
768	768
769	769
770		-=== 2.6.7  IN865-867 (IN865) ===
	743	+=== 2.6.7 IN865-867 (IN865) ===
771	771
772	772	(((
773	773	(% style="color:blue" %)**Uplink:**