Changes for page LDDS45 - LoRaWAN Distance Detection Sensor User Manual

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 17 removed)
  • 1654850511545-399.png
  • 1654850829385-439.png
  • 1654851029373-510.png
  • 1654852175653-550.png
  • 1654852253176-749.png
  • 1654912614655-664.png
  • 1654912858581-740.png
  • image-20220610165129-11.png
  • image-20220610172003-1.png
  • image-20220610172003-2.png
  • image-20220610172400-3.png
  • image-20220610172924-4.png
  • image-20220610172924-5.png
  • image-20220610172924-6.png
  • image-20220610173409-7.png
  • image-20220610174836-8.png
  • image-20220610174917-9.png

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-LDDS45 - LoRaWAN Distance Detection Sensor User Manual
	1	+LDDS75 - LoRaWAN Distance Detection Sensor User Manual

Content

...	...	@@ -1,9 +1,8 @@
1	1	(% style="text-align:center" %)
2		-[[image:1654912614655-664.png||height="530" width="628"]]
	2	+[[image:1654846127817-788.png]]
3	3
4	4	**Contents:**
5	5
6		-{{toc/}}
7	7
8	8
9	9
...	...	@@ -11,7 +11,6 @@
11	11
12	12
13	13
14		-
15	15	= 1.  Introduction =
16	16
17	17	== 1.1 ​ What is LoRaWAN Distance Detection Sensor ==
...	...	@@ -20,56 +20,27 @@
20	20
21	21
22	22	(((
23		-(((
24		-The Dragino LDDS45 is a (% style="color:#4472c4" %)** LoRaWAN Distance Detection Sensor**(%%) for Internet of Things solution. It is used to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses (% style="color:#4472c4" %)** ultrasonic sensing** (%%)technology for distance measurement, and (% style="color:#4472c4" %)** temperature compensation**(%%) is performed internally to improve the reliability of data. The LDDS45 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc.
25		-)))
	21	+The Dragino LDDS75 is a (% style="color:#4472c4" %)** LoRaWAN Distance Detection Sensor**(%%) for Internet of Things solution. It is used to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses (% style="color:#4472c4" %)** ultrasonic sensing** (%%)technology for distance measurement, and (% style="color:#4472c4" %)** temperature compensation**(%%) is performed internally to improve the reliability of data. The LDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc.
26	26
27		-(((
28		-
29		-)))
30	30
31		-(((
32	32	It detects the distance** (% style="color:#4472c4" %) between the measured object and the sensor(%%)**, and uploads the value via wireless to LoRaWAN IoT Server.
33		-)))
34	34
35		-(((
36		-
37		-)))
38	38
39		-(((
40		-The LoRa wireless technology used in LDDS45 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.
41		-)))
	27	+The LoRa wireless technology used in LDDS75 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.
42	42
43		-(((
44		-
45		-)))
46	46
47		-(((
48		-LDDS45 is powered by (% style="color:#4472c4" %)** 8500mAh Li-SOCI2 battery**(%%); It is designed for long term use up to 10 years*.
49		-)))
	30	+LDDS75 is powered by (% style="color:#4472c4" %)** 4000mA or 8500mAh Li-SOCI2 battery**(%%); It is designed for long term use up to 10 years*.
50	50
51		-(((
52		-
53		-)))
54	54
55		-(((
56		-Each LDDS45 pre-loads with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect if there is network coverage, after power on.
57		-)))
	33	+Each LDDS75 pre-loads with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect if there is network coverage, after power on.
58	58
59		-(((
60		-
61		-)))
62	62
63		-(((
64		-(% style="color:#4472c4" %) * (%%)Actually lifetime depends on network coverage and uplink interval and other factors.
65		-
66		-
	36	+(% style="color:#4472c4" %) * (%%)Actually lifetime depends on network coverage and uplink interval and other factors
67	67	)))
68	68	)))
69		-)))
70	70
71		-[[image:1654912858581-740.png]]
72	72
	41	+[[image:1654847051249-359.png]]
73	73
74	74
75	75
...	...	@@ -88,8 +88,6 @@
88	88	* IP66 Waterproof Enclosure
89	89	* 4000mAh or 8500mAh Battery for long term use
90	90
91		-
92		-
93	93	== 1.3  Specification ==
94	94
95	95	=== 1.3.1  Rated environmental conditions ===
...	...	@@ -96,31 +96,23 @@
96	96
97	97	[[image:image-20220610154839-1.png]]
98	98
99		-(((
100		-**Remarks: (1) a. When the ambient temperature is 0-39 ℃, the maximum humidity is 90% (non-condensing);  b. When the ambient temperature is 40-50 ℃, the highest humidity is the highest humidity in the natural world at the current temperature (no condensation)**
101		-)))
	66	+**Remarks: (1) a. When the ambient temperature is 0-39 ℃, the maximum humidity is 90% (non-condensing);**
102	102
	68	+**b. When the ambient temperature is 40-50 ℃, the highest humidity is the highest humidity in the natural world at the current temperature (no condensation)**
103	103
104	104
	71	+
105	105	=== 1.3.2  Effective measurement range Reference beam pattern ===
106	106
107		-**(1) The tested object is a white cylindrical tube made of PVC, with a height of 100cm and a diameter of 7.5cm.**
	74	+**(1) The tested object is a white cylindrical tube made of PVC, with a height of 100cm and a diameter of 7.5cm.**[[image:image-20220610155021-2.png||height="440" width="1189"]]
108	108
109	109
110	110
111		-[[image:1654852253176-749.png]]
	78	+**(2)** The object to be tested is a "corrugated cardboard box" perpendicular to the central axis of 0 °, and the length * width is 60cm * 50cm.[[image:image-20220610155021-3.png||height="437" width="1192"]]
112	112
	80	+(% style="display:none" %) (%%)
113	113
114	114
115		-(((
116		-**(2)** **The object to be tested is a "corrugated cardboard box" perpendicular to the central axis of 0 °, and the length * width is 60cm * 50cm.**
117		-)))
118		-
119		-
120		-[[image:1654852175653-550.png]](% style="display:none" %) ** **
121		-
122		-
123		-
124	124	== 1.5 ​ Applications ==
125	125
126	126	* Horizontal distance measurement
...	...	@@ -134,7 +134,6 @@
134	134	* Bottom water level monitoring
135	135
136	136
137		-
138	138	== 1.6  Pin mapping and power on ==
139	139
140	140
...	...	@@ -141,7 +141,6 @@
141	141	[[image:1654847583902-256.png]]
142	142
143	143
144		-
145	145	= 2.  Configure LDDS75 to connect to LoRaWAN network =
146	146
147	147	== 2.1  How it works ==
...	...	@@ -155,7 +155,6 @@
155	155	)))
156	156
157	157
158		-
159	159	== 2.2  ​Quick guide to connect to LoRaWAN server (OTAA) ==
160	160
161	161	(((
...	...	@@ -181,17 +181,11 @@
181	181	[[image:image-20220607170145-1.jpeg]]
182	182
183	183
184		-(((
185	185	For OTAA registration, we need to set **APP EUI/ APP KEY/ DEV EUI**. Some server might no need to set APP EUI.
186		-)))
187	187
188		-(((
189	189	Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
190		-)))
191	191
192		-(((
193	193	**Add APP EUI in the application**
194		-)))
195	195
196	196	[[image:image-20220610161353-4.png]]
197	197
...	...	@@ -234,15 +234,11 @@
234	234	== 2.3  ​Uplink Payload ==
235	235
236	236	(((
237		-(((
238		-LDDS75 will uplink payload via LoRaWAN with below payload format:
239		-)))
	187	+LDDS75 will uplink payload via LoRaWAN with below payload format:
240	240
241		-(((
242	242	Uplink payload includes in total 4 bytes.
243	243	Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance
244	244	)))
245		-)))
246	246
247	247	(((
248	248
...	...	@@ -253,14 +253,14 @@
253	253	**Size (bytes)**
254	254	)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1**
255	255	|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(((
256		-[[Distance>>||anchor="H2.3.2A0Distance"]]
	202	+[[Distance>>||anchor="H2.3.3A0Distance"]]
257	257
258	258	(unit: mm)
259		-)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.3A0InterruptPin"]]|(((
260		-[[Temperature (Optional )>>||anchor="H2.3.4A0DS18B20Temperaturesensor"]]
261		-)))|[[Sensor Flag>>||anchor="H2.3.5A0SensorFlag"]]
	205	+)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
	206	+[[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]]
	207	+)))|[[Sensor Flag>>path:#Sensor_Flag]]
262	262
263		-[[image:1654850511545-399.png]]
	209	+[[image:1654833689380-972.png]]
264	264
265	265
266	266
...	...	@@ -267,7 +267,7 @@
267	267	=== 2.3.1  Battery Info ===
268	268
269	269
270		-Check the battery voltage for LDDS75.
	216	+Check the battery voltage for LLDS12.
271	271
272	272	Ex1: 0x0B45 = 2885mV
273	273
...	...	@@ -275,71 +275,96 @@
275	275
276	276
277	277
278		-=== 2.3.2  Distance ===
	224	+=== 2.3.2  DS18B20 Temperature sensor ===
279	279
280		-(((
281		-Get the distance. Flat object range 280mm - 7500mm.
282		-)))
	226	+This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
283	283
284		-(((
285		-For example, if the data you get from the register is 0x0B 0x05, the distance between the sensor and the measured object is(% style="color:#4472c4" %)** 0B05(H) = 2821 (D) = 2821 mm.**
286		-)))
287	287
	229	+**Example**:
288	288
289		-* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
290		-* If the sensor value lower than 0x0118 (280mm), the sensor value will be invalid. Since v1.1.4, all value lower than 280mm will be set to 0x0014(20mm) which means the value is invalid.
	231	+If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
291	291
	233	+If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
292	292
293	293
294		-=== 2.3.3  Interrupt Pin ===
295	295
296		-This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H3.3A0SetInterruptMode"]] for the hardware and software set up.
	237	+=== 2.3.3  Distance ===
297	297
298		-**Example:**
	239	+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.
299	299
300		-0x00: Normal uplink packet.
301	301
302		-0x01: Interrupt Uplink Packet.
	242	+**Example**:
303	303
	244	+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.
304	304
305	305
306		-=== 2.3.4  DS18B20 Temperature sensor ===
307	307
308		-This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
	248	+=== 2.3.4  Distance signal strength ===
309	309
	250	+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.
	251	+
	252	+
310	310	**Example**:
311	311
312		-If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
	255	+If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
313	313
314		-If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
	257	+Customers can judge whether they need to adjust the environment based on the signal strength.
315	315
316		-(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
317	317
318	318
	261	+=== 2.3.5  Interrupt Pin ===
319	319
320		-=== 2.3.5  Sensor Flag ===
	263	+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.
321	321
	265	+Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
	266	+
	267	+**Example:**
	268	+
	269	+0x00: Normal uplink packet.
	270	+
	271	+0x01: Interrupt Uplink Packet.
	272	+
	273	+
	274	+
	275	+=== 2.3.6  LiDAR temp ===
	276	+
	277	+Characterize the internal temperature value of the sensor.
	278	+
	279	+**Example: **
	280	+If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
	281	+If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
	282	+
	283	+
	284	+
	285	+=== 2.3.7  Message Type ===
	286	+
322	322	(((
323		-0x01: Detect Ultrasonic Sensor
	288	+For a normal uplink payload, the message type is always 0x01.
324	324	)))
325	325
326	326	(((
327		-0x00: No Ultrasonic Sensor
	292	+Valid Message Type:
328	328	)))
329	329
330	330
	296	+(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %)
	297	+|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
	298	+|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]]
	299	+|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]]
331	331
332		-=== 2.3.6  Decode payload in The Things Network ===
	301	+=== 2.3.8  Decode payload in The Things Network ===
333	333
334	334	While using TTN network, you can add the payload format to decode the payload.
335	335
336	336
337		-[[image:1654850829385-439.png]]
	306	+[[image:1654592762713-715.png]]
338	338
339		-The payload decoder function for TTN V3 is here:
	308	+(((
	309	+The payload decoder function for TTN is here:
	310	+)))
340	340
341	341	(((
342		-LDDS75 TTN V3 Payload Decoder: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LDDS75/Payload_Decoder/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Payload_Decoder/]]
	313	+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/]]
343	343	)))
344	344
345	345
...	...	@@ -346,7 +346,7 @@
346	346
347	347	== 2.4  Uplink Interval ==
348	348
349		-The LDDS75 by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[Change Uplink Interval>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H4.1ChangeUplinkInterval"]]
	320	+The LLDS12 by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[Change Uplink Interval>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H4.1ChangeUplinkInterval"]]
350	350
351	351
352	352
...	...	@@ -377,25 +377,47 @@
377	377
378	378	(% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
379	379
380		-(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
	351	+(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
381	381
382		-[[image:1654851029373-510.png]]
	353	+[[image:1654832691989-514.png]]
383	383
384	384
385		-After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
	356	+[[image:1654592833877-762.png]]
386	386
387		-[[image:image-20220610165129-11.png||height="595" width="1088"]]
388	388
	359	+[[image:1654832740634-933.png]]
389	389
390	390
391		-== 2.6  Frequency Plans ==
392	392
393	393	(((
394		-The LDDS75 uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets.
	364	+(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
395	395	)))
396	396
	367	+(((
	368	+
	369	+)))
397	397
	371	+[[image:1654833065139-942.png]]
398	398
	373	+
	374	+
	375	+[[image:1654833092678-390.png]]
	376	+
	377	+
	378	+
	379	+After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
	380	+
	381	+[[image:1654833163048-332.png]]
	382	+
	383	+
	384	+
	385	+== 2.6  Frequency Plans ==
	386	+
	387	+(((
	388	+The LLDS12 uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets.
	389	+)))
	390	+
	391	+
399	399	=== 2.6.1  EU863-870 (EU868) ===
400	400
401	401	(((
...	...	@@ -459,51 +459,20 @@
459	459	=== 2.6.2  US902-928(US915) ===
460	460
461	461	(((
462		-Used in USA, Canada and South America. Default use CHE=2
	455	+Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
	456	+)))
463	463
464		-(% style="color:blue" %)**Uplink:**
	458	+(((
	459	+To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join.
	460	+)))
465	465
466		-903.9 - SF7BW125 to SF10BW125
467		-
468		-904.1 - SF7BW125 to SF10BW125
469		-
470		-904.3 - SF7BW125 to SF10BW125
471		-
472		-904.5 - SF7BW125 to SF10BW125
473		-
474		-904.7 - SF7BW125 to SF10BW125
475		-
476		-904.9 - SF7BW125 to SF10BW125
477		-
478		-905.1 - SF7BW125 to SF10BW125
479		-
480		-905.3 - SF7BW125 to SF10BW125
481		-
482		-
483		-(% style="color:blue" %)**Downlink:**
484		-
485		-923.3 - SF7BW500 to SF12BW500
486		-
487		-923.9 - SF7BW500 to SF12BW500
488		-
489		-924.5 - SF7BW500 to SF12BW500
490		-
491		-925.1 - SF7BW500 to SF12BW500
492		-
493		-925.7 - SF7BW500 to SF12BW500
494		-
495		-926.3 - SF7BW500 to SF12BW500
496		-
497		-926.9 - SF7BW500 to SF12BW500
498		-
499		-927.5 - SF7BW500 to SF12BW500
500		-
501		-923.3 - SF12BW500(RX2 downlink only)
502		-
503		-
504		-
	462	+(((
	463	+After Join success, the end node will switch to the correct sub band by:
505	505	)))
506	506
	466	+* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
	467	+* 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)
	468	+
507	507	=== 2.6.3  CN470-510 (CN470) ===
508	508
509	509	(((
...	...	@@ -592,54 +592,28 @@
592	592
593	593
594	594
	557	+
595	595	=== 2.6.4  AU915-928(AU915) ===
596	596
597	597	(((
598		-Default use CHE=2
	561	+Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
	562	+)))
599	599
600		-(% style="color:blue" %)**Uplink:**
	564	+(((
	565	+To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join.
	566	+)))
601	601
602		-916.8 - SF7BW125 to SF12BW125
603		-
604		-917.0 - SF7BW125 to SF12BW125
605		-
606		-917.2 - SF7BW125 to SF12BW125
607		-
608		-917.4 - SF7BW125 to SF12BW125
609		-
610		-917.6 - SF7BW125 to SF12BW125
611		-
612		-917.8 - SF7BW125 to SF12BW125
613		-
614		-918.0 - SF7BW125 to SF12BW125
615		-
616		-918.2 - SF7BW125 to SF12BW125
617		-
618		-
619		-(% style="color:blue" %)**Downlink:**
620		-
621		-923.3 - SF7BW500 to SF12BW500
622		-
623		-923.9 - SF7BW500 to SF12BW500
624		-
625		-924.5 - SF7BW500 to SF12BW500
626		-
627		-925.1 - SF7BW500 to SF12BW500
628		-
629		-925.7 - SF7BW500 to SF12BW500
630		-
631		-926.3 - SF7BW500 to SF12BW500
632		-
633		-926.9 - SF7BW500 to SF12BW500
634		-
635		-927.5 - SF7BW500 to SF12BW500
636		-
637		-923.3 - SF12BW500(RX2 downlink only)
638		-
639		-
	568	+(((
640	640
641	641	)))
642	642
	572	+(((
	573	+After Join success, the end node will switch to the correct sub band by:
	574	+)))
	575	+
	576	+* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
	577	+* 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)
	578	+
643	643	=== 2.6.5  AS920-923 & AS923-925 (AS923) ===
644	644
645	645	(((
...	...	@@ -748,6 +748,7 @@
748	748
749	749
750	750
	687	+
751	751	=== 2.6.6  KR920-923 (KR920) ===
752	752
753	753	(((
...	...	@@ -820,6 +820,7 @@
820	820
821	821
822	822
	760	+
823	823	=== 2.6.7  IN865-867 (IN865) ===
824	824
825	825	(((
...	...	@@ -856,95 +856,95 @@
856	856
857	857
858	858
	797	+
859	859	== 2.7  LED Indicator ==
860	860
861		-The LDDS75 has an internal LED which is to show the status of different state.
	800	+The LLDS12 has an internal LED which is to show the status of different state.
862	862
863		-
864		-* Blink once when device power on.
865		-* The device detects the sensor and flashes 5 times.
866		-* Solid ON for 5 seconds once device successful Join the network.
	802	+* The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
867	867	* Blink once when device transmit a packet.
868	868
869		-
870		-
871	871	== 2.8  ​Firmware Change Log ==
872	872
873	873
874		-(((
875		-**Firmware download link: **[[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/]]
876		-)))
	808	+**Firmware download link: **[[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LLDS12/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LLDS12/Firmware/]]
877	877
878		-(((
879		-
880		-)))
881	881
882		-(((
883	883	**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
884		-)))
885	885
886	886
887	887
888		-== 2.9  Mechanical ==
	815	+= 3.  LiDAR ToF Measurement =
889	889
	817	+== 3.1 Principle of Distance Measurement ==
890	890
891		-[[image:image-20220610172003-1.png]]
	819	+The LiDAR probe is based on TOF, namely, Time of Flight principle. To be specific, the product emits modulation wave of near infrared ray on a periodic basis, which will be reflected after contacting object. The product obtains the time of flight by measuring round-trip phase difference and then calculates relative range between the product and the detection object, as shown below.
892	892
	821	+[[image:1654831757579-263.png]]
893	893
894		-[[image:image-20220610172003-2.png]]
895	895
896	896
	825	+== 3.2 Distance Measurement Characteristics ==
897	897
898		-== 2.10  Battery Analysis ==
	827	+With optimization of light path and algorithm, The LiDAR probe has minimized influence from external environment on distance measurement performance. Despite that, the range of distance measurement may still be affected by the environment illumination intensity and the reflectivity of detection object. As shown in below:
899	899
900		-=== 2.10.1  Battery Type ===
	829	+[[image:1654831774373-275.png]]
901	901
902		-The LDDS75 battery is a combination of a 4000mAh or 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
903	903
	832	+(((
	833	+(% style="color:blue" %)**① **(%%)Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable.
	834	+)))
904	904
905		-The battery related documents as below:
	836	+(((
	837	+(% style="color:blue" %)**② **(%%)Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m.
	838	+)))
906	906
907		-* (((
908		-[[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
	840	+(((
	841	+(% style="color:blue" %)**③ **(%%)Represents the operating range of The LiDAR probe detecting white target with 90% reflectivity, 0.1-12m.
909	909	)))
910		-* (((
911		-[[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
912		-)))
913		-* (((
914		-[[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC_1520_datasheet.jpg]], [[Tech Spec>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC1520%20Technical%20Specification20171123.pdf]]
915		-)))
916	916
917		- [[image:image-20220610172400-3.png]]
918	918
	845	+(((
	846	+Vertical Coordinates: Represents the radius of light spot for The LiDAR probe at the different distances. The diameter of light spot depends on the FOV of The LiDAR probe (the term of FOV generally refers to the smaller value between the receiving angle and the transmitting angle), which is calculated as follows:
	847	+)))
919	919
920	920
921		-=== 2.10.2  Replace the battery ===
	850	+[[image:1654831797521-720.png]]
922	922
923		-(((
924		-You can change the battery in the LDDS75.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board.
925		-)))
926	926
927	927	(((
928		-
	854	+In the formula above, d is the diameter of light spot; D is detecting range; β is the value of the receiving angle of The LiDAR probe, 3.6°. Correspondence between the diameter of light spot and detecting range is given in Table below.
929	929	)))
930	930
	857	+[[image:1654831810009-716.png]]
	858	+
	859	+
931	931	(((
932		-The default battery pack of LDDS75 includes a ER18505 plus super capacitor. If user can't find this pack locally, they can find ER18505 or equivalence, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes)
	861	+If the light spot reaches two objects with different distances, as shown in Figure 3, the output distance value will be a value between the actual distance values of the two objects. For a high accuracy requirement in practice, the above situation should be noticed to avoid the measurement error.
933	933	)))
934	934
935	935
936	936
937		-= 3.  Configure LDDS75 via AT Command or LoRaWAN Downlink =
	866	+== 3.3 Notice of usage: ==
938	938
	868	+Possible invalid /wrong reading for LiDAR ToF tech:
	869	+
	870	+* Measure high reflectivity object such as: Mirror, Smooth ceramic tile, static milk surface, will have possible wrong readings.
	871	+* While there is transparent object such as glass, water drop between the measured object and the LiDAR sensor, the reading might wrong.
	872	+* The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
	873	+* The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window.
	874	+
	875	+= 4.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
	876	+
939	939	(((
940	940	(((
941		-Use can configure LDDS75 via AT Command or LoRaWAN Downlink.
	879	+Use can configure LLDS12 via AT Command or LoRaWAN Downlink.
942	942	)))
943	943	)))
944	944
945	945	* (((
946	946	(((
947		-AT Command Connection: See [[FAQ>>||anchor="H4.A0FAQ"]].
	885	+AT Command Connection: See [[FAQ>>||anchor="H7.A0FAQ"]].
948	948	)))
949	949	)))
950	950	* (((
...	...	@@ -959,7 +959,7 @@
959	959	)))
960	960
961	961	(((
962		-There are two kinds of commands to configure LDDS75, they are:
	900	+There are two kinds of commands to configure LLDS12, they are:
963	963	)))
964	964	)))
965	965
...	...	@@ -1000,159 +1000,351 @@
1000	1000
1001	1001	* (((
1002	1002	(((
1003		-(% style="color:#4f81bd" %)** Commands special design for LDDS75**
	941	+(% style="color:#4f81bd" %)** Commands special design for LLDS12**
1004	1004	)))
1005	1005	)))
1006	1006
1007	1007	(((
1008	1008	(((
1009		-These commands only valid for LDDS75, as below:
	947	+These commands only valid for LLDS12, as below:
1010	1010	)))
1011	1011	)))
1012	1012
1013	1013
1014	1014
1015		-== 3.1  Access AT Commands ==
	953	+== 4.1  Set Transmit Interval Time ==
1016	1016
1017		-LDDS75 supports AT Command set in the stock firmware. You can use a USB to TTL adapter to connect to LDDS75 for using AT command, as below.
	955	+Feature: Change LoRaWAN End Node Transmit Interval.
1018	1018
1019		-[[image:image-20220610172924-4.png||height="483" width="988"]]
	957	+(% style="color:#037691" %)**AT Command: AT+TDC**
1020	1020
	959	+[[image:image-20220607171554-8.png]]
1021	1021
1022		-Or if you have below board, use below connection:
1023	1023
	962	+(((
	963	+(% style="color:#037691" %)**Downlink Command: 0x01**
	964	+)))
1024	1024
1025		-[[image:image-20220610172924-5.png]]
	966	+(((
	967	+Format: Command Code (0x01) followed by 3 bytes time value.
	968	+)))
1026	1026
	970	+(((
	971	+If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
	972	+)))
1027	1027
	974	+* (((
	975	+Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
	976	+)))
	977	+* (((
	978	+Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
	979	+)))
	980	+
	981	+== 4.2  Set Interrupt Mode ==
	982	+
	983	+Feature, Set Interrupt mode for GPIO_EXIT.
	984	+
	985	+(% style="color:#037691" %)**AT Command: AT+INTMOD**
	986	+
	987	+[[image:image-20220610105806-2.png]]
	988	+
	989	+
1028	1028	(((
1029		-In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LDDS75. LDDS75 will output system info once power on as below:
	991	+(% style="color:#037691" %)**Downlink Command: 0x06**
1030	1030	)))
1031	1031
	994	+(((
	995	+Format: Command Code (0x06) followed by 3 bytes.
	996	+)))
1032	1032
1033		- [[image:image-20220610172924-6.png||height="601" width="860"]]
	998	+(((
	999	+This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
	1000	+)))
1034	1034
	1002	+* (((
	1003	+Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
	1004	+)))
	1005	+* (((
	1006	+Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
	1007	+)))
1035	1035
	1009	+== 4.3  Get Firmware Version Info ==
1036	1036
1037		-== 3.2  Set Transmit Interval Time ==
	1011	+Feature: use downlink to get firmware version.
1038	1038
1039		-Feature: Change LoRaWAN End Node Transmit Interval.
	1013	+(% style="color:#037691" %)**Downlink Command: 0x26**
1040	1040
1041		-(% style="color:#037691" %)**AT Command: AT+TDC**
	1015	+[[image:image-20220607171917-10.png]]
1042	1042
1043		-[[image:image-20220610173409-7.png]]
	1017	+* Reply to the confirmation package: 26 01
	1018	+* Reply to non-confirmed packet: 26 00
1044	1044
	1020	+Device will send an uplink after got this downlink command. With below payload:
1045	1045
	1022	+Configures info payload:
	1023	+
	1024	+(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
	1025	+|=(((
	1026	+**Size(bytes)**
	1027	+)))|=**1**|=**1**|=**1**|=**1**|=**1**|=**5**|=**1**
	1028	+|**Value**|Software Type|(((
	1029	+Frequency
	1030	+
	1031	+Band
	1032	+)))|Sub-band|(((
	1033	+Firmware
	1034	+
	1035	+Version
	1036	+)))|Sensor Type|Reserve|(((
	1037	+[[Message Type>>||anchor="H2.3.7A0MessageType"]]
	1038	+Always 0x02
	1039	+)))
	1040	+
	1041	+**Software Type**: Always 0x03 for LLDS12
	1042	+
	1043	+
	1044	+**Frequency Band**:
	1045	+
	1046	+*0x01: EU868
	1047	+
	1048	+*0x02: US915
	1049	+
	1050	+*0x03: IN865
	1051	+
	1052	+*0x04: AU915
	1053	+
	1054	+*0x05: KZ865
	1055	+
	1056	+*0x06: RU864
	1057	+
	1058	+*0x07: AS923
	1059	+
	1060	+*0x08: AS923-1
	1061	+
	1062	+*0x09: AS923-2
	1063	+
	1064	+*0xa0: AS923-3
	1065	+
	1066	+
	1067	+**Sub-Band**: value 0x00 ~~ 0x08
	1068	+
	1069	+
	1070	+**Firmware Version**: 0x0100, Means: v1.0.0 version
	1071	+
	1072	+
	1073	+**Sensor Type**:
	1074	+
	1075	+0x01: LSE01
	1076	+
	1077	+0x02: LDDS75
	1078	+
	1079	+0x03: LDDS20
	1080	+
	1081	+0x04: LLMS01
	1082	+
	1083	+0x05: LSPH01
	1084	+
	1085	+0x06: LSNPK01
	1086	+
	1087	+0x07: LLDS12
	1088	+
	1089	+
	1090	+
	1091	+= 5.  Battery & How to replace =
	1092	+
	1093	+== 5.1  Battery Type ==
	1094	+
1046	1046	(((
1047		-(% style="color:#037691" %)**Downlink Command: 0x01**
	1096	+LLDS12 is equipped with a [[8500mAH ER26500 Li-SOCI2 battery>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]. The battery is un-rechargeable battery with low discharge rate targeting for 8~~10 years use. This type of battery is commonly used in IoT target for long-term running, such as water meter.
1048	1048	)))
1049	1049
1050	1050	(((
	1100	+The discharge curve is not linear so can’t simply use percentage to show the battery level. Below is the battery performance.
	1101	+)))
	1102	+
	1103	+[[image:1654593587246-335.png]]
	1104	+
	1105	+
	1106	+Minimum Working Voltage for the LLDS12:
	1107	+
	1108	+LLDS12:  2.45v ~~ 3.6v
	1109	+
	1110	+
	1111	+
	1112	+== 5.2  Replace Battery ==
	1113	+
1051	1051	(((
1052		-Format: Command Code (0x01) followed by 3 bytes time value.
	1115	+Any battery with range 2.45 ~~ 3.6v can be a replacement. We recommend to use Li-SOCl2 Battery.
	1116	+)))
1053	1053
1054	1054	(((
1055		-If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
	1119	+And make sure the positive and negative pins match.
1056	1056	)))
1057	1057
1058		-* Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
1059		-* Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
	1122	+
	1123	+
	1124	+== 5.3  Power Consumption Analyze ==
	1125	+
	1126	+(((
	1127	+Dragino Battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
1060	1060	)))
	1129	+
	1130	+(((
	1131	+Instruction to use as below:
1061	1061	)))
1062	1062
1063	1063
	1135	+**Step 1**: Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
1064	1064
	1137	+[[https:~~/~~/www.dragino.com/downloads/index.pHp?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
1065	1065
1066	1066
1067		-== 3.3  Set Interrupt Mode ==
	1140	+**Step 2**: Open it and choose
1068	1068
1069		-Feature, Set Interrupt mode for GPIO_EXIT.
	1142	+* Product Model
	1143	+* Uplink Interval
	1144	+* Working Mode
1070	1070
1071		-(% style="color:#037691" %)**Downlink Command: AT+INTMOD**
	1146	+And the Life expectation in difference case will be shown on the right.
1072	1072
1073		-[[image:image-20220610174917-9.png]]
	1148	+[[image:1654593605679-189.png]]
1074	1074
1075	1075
1076		-(% style="color:#037691" %)**Downlink Command: 0x06**
	1151	+The battery related documents as below:
1077	1077
1078		-Format: Command Code (0x06) followed by 3 bytes.
	1153	+* (((
	1154	+[[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
	1155	+)))
	1156	+* (((
	1157	+[[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
	1158	+)))
	1159	+* (((
	1160	+[[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC_1520_datasheet.jpg]], [[Tech Spec>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC1520%20Technical%20Specification20171123.pdf]]
	1161	+)))
1079	1079
	1163	+[[image:image-20220607172042-11.png]]
	1164	+
	1165	+
	1166	+
	1167	+=== 5.3.1  ​Battery Note ===
	1168	+
1080	1080	(((
1081		-This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
	1170	+The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
1082	1082	)))
1083	1083
1084		-* Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
1085		-* Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
1086	1086
1087	1087
	1175	+=== ​5.3.2  Replace the battery ===
1088	1088
1089		-= 4.  FAQ =
	1177	+(((
	1178	+You can change the battery in the LLDS12.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won’t be voltage drop between battery and main board.
	1179	+)))
1090	1090
1091		-== 4.1  What is the frequency plan for LDDS75? ==
	1181	+(((
	1182	+The default battery pack of LLDS12 includes a ER26500 plus super capacitor. If user can’t find this pack locally, they can find ER26500 or equivalence, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes)
	1183	+)))
1092	1092
1093		-LDDS75 use the same frequency as other Dragino products. User can see the detail from this link:  [[Introduction>>doc:Main.End Device Frequency Band.WebHome||anchor="H1.Introduction"]]
1094	1094
1095	1095
	1187	+= 6.  Use AT Command =
1096	1096
1097		-== 4.2  How to change the LoRa Frequency Bands/Region ==
	1189	+== 6.1  Access AT Commands ==
1098	1098
1099		-You can follow the instructions for [[how to upgrade image>>||anchor="H2.8A0200BFirmwareChangeLog"]].
1100		-When downloading the images, choose the required image file for download. ​
	1191	+LLDS12 supports AT Command set in the stock firmware. You can use a USB to TTL adapter to connect to LLDS12 for using AT command, as below.
1101	1101
	1193	+[[image:1654593668970-604.png]]
1102	1102
	1195	+**Connection:**
1103	1103
1104		-== 4.3  Can I use LDDS75 in condensation environment? ==
	1197	+(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
1105	1105
1106		-LDDS75 is not suitable to be used in condensation environment. Condensation on the LDDS75 probe will affect the reading and always got 0.
	1199	+(% style="background-color:yellow" %)** USB TTL TXD  <~-~-~-~-> UART_RXD**
1107	1107
	1201	+(% style="background-color:yellow" %)** USB TTL RXD  <~-~-~-~-> UART_TXD**
1108	1108
1109	1109
1110		-= 5.  Trouble Shooting =
	1204	+(((
	1205	+(((
	1206	+In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LLDS12.
	1207	+)))
1111	1111
1112		-== 5.1  Why I can’t join TTN V3 in US915 / AU915 bands? ==
	1209	+(((
	1210	+LLDS12 will output system info once power on as below:
	1211	+)))
	1212	+)))
1113	1113
1114		-It is due to channel mapping. Please see below link:  [[Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1115	1115
	1215	+ [[image:1654593712276-618.png]]
1116	1116
1117		-== 5.2  AT Command input doesn't work ==
	1217	+Valid AT Command please check [[Configure Device>>||anchor="H4.A0ConfigureLLDS12viaATCommandorLoRaWANDownlink"]].
1118	1118
	1219	+
	1220	+= 7.  FAQ =
	1221	+
	1222	+== 7.1  How to change the LoRa Frequency Bands/Region ==
	1223	+
	1224	+You can follow the instructions for [[how to upgrade image>>||anchor="H2.8A0200BFirmwareChangeLog"]].
	1225	+When downloading the images, choose the required image file for download. ​
	1226	+
	1227	+
	1228	+= 8.  Trouble Shooting =
	1229	+
	1230	+== 8.1  AT Commands input doesn’t work ==
	1231	+
	1232	+
	1233	+(((
1119	1119	In the case if user can see the console output but can’t type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn’t send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
	1235	+)))
1120	1120
	1237	+
	1238	+== 8.2  Significant error between the output distant value of LiDAR and actual distance ==
	1239	+
	1240	+
1121	1121	(((
1122		-
	1242	+(% style="color:blue" %)**Cause ①**(%%)**：**Due to the physical principles of The LiDAR probe, the above phenomenon is likely to occur if the detection object is the material with high reflectivity (such as mirror, smooth floor tile, etc.) or transparent substance (such as glass and water, etc.)
1123	1123	)))
1124	1124
	1245	+(((
	1246	+Troubleshooting: Please avoid use of this product under such circumstance in practice.
	1247	+)))
1125	1125
1126		-= 6.  Order Info =
	1249	+(((
	1250	+
	1251	+)))
1127	1127
	1253	+(((
	1254	+(% style="color:blue" %)**Cause ②**(%%)**: **The IR-pass filters are blocked.
	1255	+)))
1128	1128
1129		-Part Number **:** (% style="color:blue" %)**LDDS75-XX-YY**
	1257	+(((
	1258	+Troubleshooting: please use dry dust-free cloth to gently remove the foreign matter.
	1259	+)))
1130	1130
1131	1131
1132		-(% style="color:blue" %)**XX**(%%)**: **The default frequency band
1133	1133
1134		-* (% style="color:red" %)**AS923 **(%%)**:** LoRaWAN AS923 band
1135		-* (% style="color:red" %)**AU915 **(%%)**:** LoRaWAN AU915 band
1136		-* (% style="color:red" %)**EU433 **(%%)**:** LoRaWAN EU433 band
1137		-* (% style="color:red" %)**EU868 **(%%)**:** LoRaWAN EU868 band
1138		-* (% style="color:red" %)**KR920 **(%%)**:** LoRaWAN KR920 band
1139		-* (% style="color:red" %)**US915 **(%%)**:** LoRaWAN US915 band
1140		-* (% style="color:red" %)**IN865 **(%%)**:**  LoRaWAN IN865 band
1141		-* (% style="color:red" %)**CN470 **(%%)**:** LoRaWAN CN470 band
	1263	+= 9.  Order Info =
1142	1142
1143		-(% style="color:blue" %)**YY**(%%): Battery Option
1144	1144
1145		-* (% style="color:red" %)**4 **(%%)**: **4000mAh battery
1146		-* (% style="color:red" %)**8 **(%%)**:** 8500mAh battery
	1266	+Part Number: (% style="color:blue" %)**LLDS12-XX**
1147	1147
1148	1148
	1269	+(% style="color:blue" %)**XX**(%%): The default frequency band
1149	1149
1150		-= 7. ​ Packing Info =
	1271	+* (% style="color:red" %)**AS923**(%%):  LoRaWAN AS923 band
	1272	+* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
	1273	+* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
	1274	+* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
	1275	+* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
	1276	+* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
	1277	+* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
	1278	+* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1151	1151
	1280	+= 10. ​ Packing Info =
1152	1152
	1282	+
1153	1153	**Package Includes**:
1154	1154
1155		-* LDDS75 LoRaWAN Distance Detection Sensor x 1
	1285	+* LLDS12 LoRaWAN LiDAR Distance Sensor x 1
1156	1156
1157	1157	**Dimension and weight**:
1158	1158
...	...	@@ -1161,9 +1161,7 @@
1161	1161	* Package Size / pcs : cm
1162	1162	* Weight / pcs : g
1163	1163
	1294	+= 11.  ​Support =
1164	1164
1165		-
1166		-= 8.  ​Support =
1167		-
1168	1168	* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1169	1169	* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]].

1654850511545-399.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-88.3 KB

Content

1654850829385-439.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-59.2 KB

Content

1654851029373-510.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-92.0 KB

Content

1654852175653-550.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-106.2 KB

Content

1654852253176-749.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-106.6 KB

Content

1654912614655-664.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-169.3 KB

Content

1654912858581-740.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-84.0 KB

Content

image-20220610165129-11.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-50.5 KB

Content

image-20220610172003-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-5.9 KB

Content

image-20220610172003-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-18.6 KB

Content

image-20220610172400-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-370.3 KB

Content

image-20220610172924-4.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-1.5 MB

Content

image-20220610172924-5.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-901.4 KB

Content

image-20220610172924-6.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-68.6 KB

Content

image-20220610173409-7.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-11.8 KB

Content

image-20220610174836-8.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-34.3 KB

Content

image-20220610174917-9.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-34.3 KB

Content