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]]
...	...	@@ -63,8 +63,6 @@
63	63	* Downlink to change configure
64	64	* 8500mAh Battery for long term use
65	65
66		-
67		-
68	68	== 1.3  Probe Specification ==
69	69
70	70	* Storage temperature ：-20℃~~75℃
...	...	@@ -80,8 +80,6 @@
80	80	* Material of enclosure - ABS+PC
81	81	* Wire length - 25cm
82	82
83		-
84		-
85	85	== 1.4  Probe Dimension ==
86	86
87	87
...	...	@@ -88,6 +88,7 @@
88	88	[[image:1654827224480-952.png]]
89	89
90	90
	73	+
91	91	== 1.5 ​ Applications ==
92	92
93	93	* Horizontal distance measurement
...	...	@@ -98,8 +98,6 @@
98	98	* Automatic control
99	99	* Sewer
100	100
101		-
102		-
103	103	== 1.6  Pin mapping and power on ==
104	104
105	105
...	...	@@ -107,6 +107,7 @@
107	107
108	108
109	109
	91	+
110	110	= 2.  Configure LLDS12 to connect to LoRaWAN network =
111	111
112	112	== 2.1  How it works ==
...	...	@@ -309,6 +309,9 @@
309	309	|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]]
310	310	|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H3.4GetFirmwareVersionInfo"]]
311	311
	294	+
	295	+
	296	+
312	312	=== 2.3.8  Decode payload in The Things Network ===
313	313
314	314	While using TTN network, you can add the payload format to decode the payload.
...	...	@@ -477,7 +477,7 @@
477	477	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
478	478	* 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)
479	479
480		-=== 2.6.3  CN470-510 (CN470) ===
	465	+=== 2.6.3 CN470-510 (CN470) ===
481	481
482	482	(((
483	483	Used in China, Default use CHE=1
...	...	@@ -566,7 +566,7 @@
566	566
567	567
568	568
569		-=== 2.6.4  AU915-928(AU915) ===
	554	+=== 2.6.4 AU915-928(AU915) ===
570	570
571	571	(((
572	572	Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
...	...	@@ -587,7 +587,7 @@
587	587	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
588	588	* 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)
589	589
590		-=== 2.6.5  AS920-923 & AS923-925 (AS923) ===
	575	+=== 2.6.5 AS920-923 & AS923-925 (AS923) ===
591	591
592	592	(((
593	593	(% style="color:blue" %)**Default Uplink channel:**
...	...	@@ -696,7 +696,7 @@
696	696
697	697
698	698
699		-=== 2.6.6  KR920-923 (KR920) ===
	684	+=== 2.6.6 KR920-923 (KR920) ===
700	700
701	701	(((
702	702	(% style="color:blue" %)**Default channel:**
...	...	@@ -769,7 +769,7 @@
769	769
770	770
771	771
772		-=== 2.6.7  IN865-867 (IN865) ===
	757	+=== 2.6.7 IN865-867 (IN865) ===
773	773
774	774	(((
775	775	(% style="color:blue" %)**Uplink:**