Summary

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

Details

Page properties

Content

...	...	@@ -19,18 +19,30 @@
19	19	(((
20	20
21	21
	22	+(((
22	22	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	+)))
23	23
	26	+(((
24	24	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	+)))
25	25
	30	+(((
26	26	It detects the distance between the measured object and the sensor, and uploads the value via wireless to LoRaWAN IoT Server.
	32	+)))
27	27
	34	+(((
28	28	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	+)))
29	29
	38	+(((
30	30	LLDS12 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use up to 5 years.
	40	+)))
31	31
	42	+(((
32	32	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.
33	33	)))
	45	+)))
34	34
35	35
36	36	[[image:1654826306458-414.png]]
...	...	@@ -72,7 +72,6 @@
72	72	[[image:1654827224480-952.png]]
73	73
74	74
75		-
76	76	== 1.5 ​ Applications ==
77	77
78	78	* Horizontal distance measurement
...	...	@@ -89,8 +89,6 @@
89	89	[[image:1654827332142-133.png]]
90	90
91	91
92		-
93		-
94	94	= 2.  Configure LLDS12 to connect to LoRaWAN network =
95	95
96	96	== 2.1  How it works ==
...	...	@@ -100,7 +100,7 @@
100	100	)))
101	101
102	102	(((
103		-In case you can’t set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>||anchor="H6.UseATCommand"]]to set the keys in the LLDS12.
	112	+In case you can’t set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>||anchor="H6.A0UseATCommand"]]to set the keys in the LLDS12.
104	104	)))
105	105
106	106
...	...	@@ -191,14 +191,12 @@
191	191	|=(% style="width: 62.5px;" %)(((
192	192	**Size (bytes)**
193	193	)))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1**
194		-|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1BatteryInfo"]]|(% style="width:62.5px" %)(((
195		-[[Temperature>>||anchor="H2.3.2DS18B20Temperaturesensor"]]
196		-
197		-[[DS18B20>>||anchor="H2.3.2DS18B20Temperaturesensor"]]
198		-)))|[[Distance>>||anchor="H"]]|[[Distance signal strength>>||anchor="H2.3.4SoilTemperature"]]|(((
199		-[[Interrupt flag>>||anchor="H2.3.5InterruptPin"]]
200		-)))|[[LiDAR temp>>||anchor="H"]]|(((
201		-[[Message Type>>||anchor="H2.3.6MessageType"]]
	203	+|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)(((
	204	+[[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]]
	205	+)))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
	206	+[[Interrupt flag>>||anchor="H2.3.5A0InterruptPin"]]
	207	+)))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|(((
	208	+[[Message Type>>||anchor="H2.3.7A0MessageType"]]
202	202	)))
203	203
204	204	[[image:1654833689380-972.png]]
...	...	@@ -255,9 +255,9 @@
255	255
256	256	=== 2.3.5  Interrupt Pin ===
257	257
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.
	265	+This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H4.2A0SetInterruptMode"]] 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]].
	267	+Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
261	261
262	262	**Example:**
263	263
...	...	@@ -290,8 +290,8 @@
290	290
291	291	(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %)
292	292	|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
293		-|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]]
294		-|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H3.4GetFirmwareVersionInfo"]]
	300	+|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]]
	301	+|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]]
295	295
296	296
297	297
...	...	@@ -307,7 +307,7 @@
307	307	)))
308	308
309	309	(((
310		-LSPH01 TTN Payload Decoder: [[https:~~/~~/www.dragino.com/downloads/index.pHp?dir=LoRa_End_Node/LSPH01/Decoder/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSNPK01/Decoder/]]
	317	+LLDS12 TTN Payload Decoder: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LLDS12/Decoder/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LLDS12/Decoder/]]
311	311	)))
312	312
313	313
...	...	@@ -463,6 +463,9 @@
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
	473	+
	474	+
	475	+
466	466	=== 2.6.3  CN470-510 (CN470) ===
467	467
468	468	(((