Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 24 removed)
  • 1654848616367-242.png
  • 1654849068701-275.png
  • 1654850511545-399.png
  • 1654850829385-439.png
  • 1654851029373-510.png
  • 1654852175653-550.png
  • 1654852253176-749.png
  • image-20220610161353-4.png
  • image-20220610161353-5.png
  • image-20220610161353-6.png
  • image-20220610161353-7.png
  • image-20220610161538-8.png
  • image-20220610161538-9.png
  • image-20220610161724-10.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

Content

...	...	@@ -3,7 +3,6 @@
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 ==
...	...	@@ -35,7 +35,7 @@
35	35	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.
36	36
37	37
38		-(% style="color:#4472c4" %) * (%%)Actually lifetime depends on network coverage and uplink interval and other factors
	36	+(% style="color:#4472c4" %) ***** (%%)Actually lifetime depends on network coverage and uplink interval and other factors
39	39	)))
40	40	)))
41	41
...	...	@@ -59,6 +59,7 @@
59	59	* IP66 Waterproof Enclosure
60	60	* 4000mAh or 8500mAh Battery for long term use
61	61
	60	+
62	62	== 1.3  Specification ==
63	63
64	64	=== 1.3.1  Rated environmental conditions ===
...	...	@@ -73,20 +73,15 @@
73	73
74	74	=== 1.3.2  Effective measurement range Reference beam pattern ===
75	75
76		-**(1) The tested object is a white cylindrical tube made of PVC, with a height of 100cm and a diameter of 7.5cm.**
	75	+**(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"]]
77	77
78	78
79	79
80		-[[image:1654852253176-749.png]]
	79	+**(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"]]
81	81
	81	+(% style="display:none" %) (%%)
82	82
83		-**(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.**
84	84
85		-
86		-[[image:1654852175653-550.png]](% style="display:none" %) ** **
87		-
88		-
89		-
90	90	== 1.5 ​ Applications ==
91	91
92	92	* Horizontal distance measurement
...	...	@@ -99,6 +99,8 @@
99	99	* Sewer
100	100	* Bottom water level monitoring
101	101
	96	+
	97	+
102	102	== 1.6  Pin mapping and power on ==
103	103
104	104
...	...	@@ -105,21 +105,19 @@
105	105	[[image:1654847583902-256.png]]
106	106
107	107
108		-
109	109	= 2.  Configure LDDS75 to connect to LoRaWAN network =
110	110
111	111	== 2.1  How it works ==
112	112
113	113	(((
114		-The LDDS75 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LDDS75. If there is coverage of the LoRaWAN network, it will automatically join the network via OTAA and start to send the sensor value
	109	+The LLDS12 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LLDS12. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes.
115	115	)))
116	116
117	117	(((
118		-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="H3.A0ConfigureLDDS75viaATCommandorLoRaWANDownlink"]]to set the keys in the LDDS75.
	113	+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.
119	119	)))
120	120
121	121
122		-
123	123	== 2.2  ​Quick guide to connect to LoRaWAN server (OTAA) ==
124	124
125	125	(((
...	...	@@ -127,7 +127,7 @@
127	127	)))
128	128
129	129	(((
130		-[[image:1654848616367-242.png]]
	124	+[[image:1654827857527-556.png]]
131	131	)))
132	132
133	133	(((
...	...	@@ -135,57 +135,57 @@
135	135	)))
136	136
137	137	(((
138		-(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LDDS75.
	132	+(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LSPH01.
139	139	)))
140	140
141	141	(((
142		-Each LDDS75 is shipped with a sticker with the default device keys, user can find this sticker in the box. it looks like below.
	136	+Each LSPH01 is shipped with a sticker with the default device EUI as below:
143	143	)))
144	144
145	145	[[image:image-20220607170145-1.jpeg]]
146	146
147	147
148		-For OTAA registration, we need to set **APP EUI/ APP KEY/ DEV EUI**. Some server might no need to set APP EUI.
149	149
150		-Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
	143	+You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
151	151
152		-**Add APP EUI in the application**
153	153
154		-[[image:image-20220610161353-4.png]]
	146	+**Register the device**
155	155
156		-[[image:image-20220610161353-5.png]]
157	157
158		-[[image:image-20220610161353-6.png]]
	149	+[[image:1654592600093-601.png]]
159	159
160	160
161		-[[image:image-20220610161353-7.png]]
162	162
	153	+**Add APP EUI and DEV EUI**
163	163
164		-You can also choose to create the device manually.
	155	+[[image:1654592619856-881.png]]
165	165
166		- [[image:image-20220610161538-8.png]]
167	167
168	168
	159	+**Add APP EUI in the application**
169	169
170		-**Add APP KEY and DEV EUI**
	161	+[[image:1654592632656-512.png]]
171	171
172		-[[image:image-20220610161538-9.png]]
173	173
174	174
	165	+**Add APP KEY**
175	175
176		-(% style="color:blue" %)**Step 2**(%%): Power on LDDS75
	167	+[[image:1654592653453-934.png]]
177	177
178	178
	170	+(% style="color:blue" %)**Step 2**(%%): Power on LLDS12
	171	+
	172	+
179	179	Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
180	180
181		-[[image:image-20220610161724-10.png]]
	175	+[[image:image-20220607170442-2.png]]
182	182
183	183
184	184	(((
185		-(% style="color:blue" %)**Step 3**(%%)**:** The LDDS75 will auto join to the TTN network. After join success, it will start to upload messages to TTN and you can see the messages in the panel.
	179	+(% style="color:blue" %)**Step 3**(%%)**:** The LLDS12 will auto join to the TTN network. After join success, it will start to upload messages to TTN and you can see the messages in the panel.
186	186	)))
187	187
188		-[[image:1654849068701-275.png]]
	182	+[[image:1654833501679-968.png]]
189	189
190	190
191	191
...	...	@@ -192,10 +192,11 @@
192	192	== 2.3  ​Uplink Payload ==
193	193
194	194	(((
195		-LDDS75 will uplink payload via LoRaWAN with below payload format:
	189	+LLDS12 will uplink payload via LoRaWAN with below payload format:
	190	+)))
196	196
197		-Uplink payload includes in total 4 bytes.
198		-Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance
	192	+(((
	193	+Uplink payload includes in total 11 bytes.
199	199	)))
200	200
201	201	(((
...	...	@@ -205,23 +205,23 @@
205	205	(% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
206	206	|=(% style="width: 62.5px;" %)(((
207	207	**Size (bytes)**
208		-)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1**
209		-|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(((
210		-[[Distance>>||anchor="H2.3.3A0Distance"]]
	203	+)))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1**
	204	+|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)(((
	205	+[[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]]
	206	+)))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
	207	+[[Interrupt flag>>||anchor="H2.3.5A0InterruptPin"]]
	208	+)))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|(((
	209	+[[Message Type>>||anchor="H2.3.7A0MessageType"]]
	210	+)))
211	211
212		-(unit: mm)
213		-)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
214		-[[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]]
215		-)))|[[Sensor Flag>>path:#Sensor_Flag]]
	212	+[[image:1654833689380-972.png]]
216	216
217		-[[image:1654850511545-399.png]]
218	218
219	219
220		-
221	221	=== 2.3.1  Battery Info ===
222	222
223	223
224		-Check the battery voltage for LDDS75.
	219	+Check the battery voltage for LLDS12.
225	225
226	226	Ex1: 0x0B45 = 2885mV
227	227
...	...	@@ -229,70 +229,103 @@
229	229
230	230
231	231
232		-=== 2.3.2  Distance ===
	227	+=== 2.3.2  DS18B20 Temperature sensor ===
233	233
234		-Get the distance. Flat object range 280mm - 7500mm.
	229	+This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
235	235
236		-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.**
237	237
	232	+**Example**:
238	238
239		-* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
240		-* 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.
	234	+If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
241	241
242		-=== 2.3.3  Interrupt Pin ===
	236	+If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
243	243
244		-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.
245	245
246		-**Example:**
247	247
248		-0x00: Normal uplink packet.
	240	+=== 2.3.3  Distance ===
249	249
250		-0x01: Interrupt Uplink Packet.
	242	+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.
251	251
252	252
	245	+**Example**:
253	253
254		-=== 2.3.4  DS18B20 Temperature sensor ===
	247	+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.
255	255
256		-This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
257	257
	250	+
	251	+=== 2.3.4  Distance signal strength ===
	252	+
	253	+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.
	254	+
	255	+
258	258	**Example**:
259	259
260		-If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
	258	+If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
261	261
262		-If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
	260	+Customers can judge whether they need to adjust the environment based on the signal strength.
263	263
264		-(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
265	265
266	266
	264	+=== 2.3.5  Interrupt Pin ===
267	267
268		-=== 2.3.5  Sensor Flag ===
	266	+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.
269	269
270		-0x01: Detect Ultrasonic Sensor
	268	+Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
271	271
272		-0x00: No Ultrasonic Sensor
	270	+**Example:**
273	273
	272	+0x00: Normal uplink packet.
274	274
275		-(% class="wikigeneratedid" %)
	274	+0x01: Interrupt Uplink Packet.
276	276
277	277
278		-(% class="wikigeneratedid" id="H2.3.6A0DecodepayloadinTheThingsNetwork" %)
279	279
280		-(% style="color:inherit; font-family:inherit" %)2.3.6  Decode payload in The Things Network
	278	+=== 2.3.6  LiDAR temp ===
281	281
	280	+Characterize the internal temperature value of the sensor.
	281	+
	282	+**Example: **
	283	+If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
	284	+If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
	285	+
	286	+
	287	+
	288	+=== 2.3.7  Message Type ===
	289	+
	290	+(((
	291	+For a normal uplink payload, the message type is always 0x01.
	292	+)))
	293	+
	294	+(((
	295	+Valid Message Type:
	296	+)))
	297	+
	298	+
	299	+(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %)
	300	+|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
	301	+|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]]
	302	+|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]]
	303	+
	304	+=== 2.3.8  Decode payload in The Things Network ===
	305	+
282	282	While using TTN network, you can add the payload format to decode the payload.
283	283
284	284
285		-[[image:1654850829385-439.png]]
	309	+[[image:1654592762713-715.png]]
286	286
287		-The payload decoder function for TTN V3 is here:
	311	+(((
	312	+The payload decoder function for TTN is here:
	313	+)))
288	288
289		-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/]]
	315	+(((
	316	+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/]]
	317	+)))
290	290
291	291
292	292
293	293	== 2.4  Uplink Interval ==
294	294
295		-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"]]
	323	+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"]]
296	296
297	297
298	298
...	...	@@ -323,25 +323,47 @@
323	323
324	324	(% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
325	325
326		-(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
	354	+(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
327	327
328		-[[image:1654851029373-510.png]]
	356	+[[image:1654832691989-514.png]]
329	329
330	330
331		-After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
	359	+[[image:1654592833877-762.png]]
332	332
333		-[[image:image-20220610165129-11.png||height="595" width="1088"]]
334	334
	362	+[[image:1654832740634-933.png]]
335	335
336	336
337		-== 2.6  Frequency Plans ==
338	338
339	339	(((
340		-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.
	367	+(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
341	341	)))
342	342
	370	+(((
	371	+
	372	+)))
343	343
	374	+[[image:1654833065139-942.png]]
344	344
	376	+
	377	+
	378	+[[image:1654833092678-390.png]]
	379	+
	380	+
	381	+
	382	+After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
	383	+
	384	+[[image:1654833163048-332.png]]
	385	+
	386	+
	387	+
	388	+== 2.6  Frequency Plans ==
	389	+
	390	+(((
	391	+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.
	392	+)))
	393	+
	394	+
345	345	=== 2.6.1  EU863-870 (EU868) ===
346	346
347	347	(((
...	...	@@ -405,51 +405,20 @@
405	405	=== 2.6.2  US902-928(US915) ===
406	406
407	407	(((
408		-Used in USA, Canada and South America. Default use CHE=2
	458	+Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
	459	+)))
409	409
410		-(% style="color:blue" %)**Uplink:**
	461	+(((
	462	+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.
	463	+)))
411	411
412		-903.9 - SF7BW125 to SF10BW125
413		-
414		-904.1 - SF7BW125 to SF10BW125
415		-
416		-904.3 - SF7BW125 to SF10BW125
417		-
418		-904.5 - SF7BW125 to SF10BW125
419		-
420		-904.7 - SF7BW125 to SF10BW125
421		-
422		-904.9 - SF7BW125 to SF10BW125
423		-
424		-905.1 - SF7BW125 to SF10BW125
425		-
426		-905.3 - SF7BW125 to SF10BW125
427		-
428		-
429		-(% style="color:blue" %)**Downlink:**
430		-
431		-923.3 - SF7BW500 to SF12BW500
432		-
433		-923.9 - SF7BW500 to SF12BW500
434		-
435		-924.5 - SF7BW500 to SF12BW500
436		-
437		-925.1 - SF7BW500 to SF12BW500
438		-
439		-925.7 - SF7BW500 to SF12BW500
440		-
441		-926.3 - SF7BW500 to SF12BW500
442		-
443		-926.9 - SF7BW500 to SF12BW500
444		-
445		-927.5 - SF7BW500 to SF12BW500
446		-
447		-923.3 - SF12BW500(RX2 downlink only)
448		-
449		-
450		-
	465	+(((
	466	+After Join success, the end node will switch to the correct sub band by:
451	451	)))
452	452
	469	+* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
	470	+* 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)
	471	+
453	453	=== 2.6.3  CN470-510 (CN470) ===
454	454
455	455	(((
...	...	@@ -538,54 +538,28 @@
538	538
539	539
540	540
	560	+
541	541	=== 2.6.4  AU915-928(AU915) ===
542	542
543	543	(((
544		-Default use CHE=2
	564	+Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
	565	+)))
545	545
546		-(% style="color:blue" %)**Uplink:**
	567	+(((
	568	+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.
	569	+)))
547	547
548		-916.8 - SF7BW125 to SF12BW125
549		-
550		-917.0 - SF7BW125 to SF12BW125
551		-
552		-917.2 - SF7BW125 to SF12BW125
553		-
554		-917.4 - SF7BW125 to SF12BW125
555		-
556		-917.6 - SF7BW125 to SF12BW125
557		-
558		-917.8 - SF7BW125 to SF12BW125
559		-
560		-918.0 - SF7BW125 to SF12BW125
561		-
562		-918.2 - SF7BW125 to SF12BW125
563		-
564		-
565		-(% style="color:blue" %)**Downlink:**
566		-
567		-923.3 - SF7BW500 to SF12BW500
568		-
569		-923.9 - SF7BW500 to SF12BW500
570		-
571		-924.5 - SF7BW500 to SF12BW500
572		-
573		-925.1 - SF7BW500 to SF12BW500
574		-
575		-925.7 - SF7BW500 to SF12BW500
576		-
577		-926.3 - SF7BW500 to SF12BW500
578		-
579		-926.9 - SF7BW500 to SF12BW500
580		-
581		-927.5 - SF7BW500 to SF12BW500
582		-
583		-923.3 - SF12BW500(RX2 downlink only)
584		-
585		-
	571	+(((
586	586
587	587	)))
588	588
	575	+(((
	576	+After Join success, the end node will switch to the correct sub band by:
	577	+)))
	578	+
	579	+* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
	580	+* 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)
	581	+
589	589	=== 2.6.5  AS920-923 & AS923-925 (AS923) ===
590	590
591	591	(((
...	...	@@ -694,6 +694,7 @@
694	694
695	695
696	696
	690	+
697	697	=== 2.6.6  KR920-923 (KR920) ===
698	698
699	699	(((
...	...	@@ -766,6 +766,7 @@
766	766
767	767
768	768
	763	+
769	769	=== 2.6.7  IN865-867 (IN865) ===
770	770
771	771	(((
...	...	@@ -802,20 +802,18 @@
802	802
803	803
804	804
	800	+
805	805	== 2.7  LED Indicator ==
806	806
807		-The LDDS75 has an internal LED which is to show the status of different state.
	803	+The LLDS12 has an internal LED which is to show the status of different state.
808	808
809		-
810		-* Blink once when device power on.
811		-* The device detects the sensor and flashes 5 times.
812		-* Solid ON for 5 seconds once device successful Join the network.
	805	+* The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
813	813	* Blink once when device transmit a packet.
814	814
815	815	== 2.8  ​Firmware Change Log ==
816	816
817	817
818		-**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/]]
	811	+**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/]]
819	819
820	820
821	821	**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
...	...	@@ -822,58 +822,71 @@
822	822
823	823
824	824
825		-== 2.9  Mechanical ==
	818	+= 3.  LiDAR ToF Measurement =
826	826
	820	+== 3.1 Principle of Distance Measurement ==
827	827
828		-[[image:image-20220610172003-1.png]]
	822	+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.
829	829
830		-[[image:image-20220610172003-2.png]]
	824	+[[image:1654831757579-263.png]]
831	831
832	832
833		-== 2.10  Battery Analysis ==
834	834
835		-=== 2.10.1  Battery Type ===
	828	+== 3.2 Distance Measurement Characteristics ==
836	836
837		-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.
	830	+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:
838	838
	832	+[[image:1654831774373-275.png]]
839	839
840		-The battery related documents as below:
841	841
842		-* (((
843		-[[ Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
	835	+(((
	836	+(% style="color:blue" %)**① **(%%)Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable.
844	844	)))
845		-* (((
846		-[[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
	838	+
	839	+(((
	840	+(% style="color:blue" %)**② **(%%)Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m.
847	847	)))
848		-* (((
849		-[[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]]
	842	+
	843	+(((
	844	+(% style="color:blue" %)**③ **(%%)Represents the operating range of The LiDAR probe detecting white target with 90% reflectivity, 0.1-12m.
850	850	)))
851	851
852		- [[image:image-20220610172400-3.png]]
853	853
	848	+(((
	849	+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:
	850	+)))
854	854
855	855
856		-=== 2.10.2  Replace the battery ===
	853	+[[image:1654831797521-720.png]]
857	857
858		-(((
859		-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.
860		-)))
861	861
862	862	(((
863		-
	857	+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.
864	864	)))
865	865
	860	+[[image:1654831810009-716.png]]
	861	+
	862	+
866	866	(((
867		-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)
	864	+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.
868	868	)))
869	869
870	870
871	871
872		-= 3.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
	869	+== 3.3 Notice of usage: ==
873	873
	871	+Possible invalid /wrong reading for LiDAR ToF tech:
	872	+
	873	+* Measure high reflectivity object such as: Mirror, Smooth ceramic tile, static milk surface, will have possible wrong readings.
	874	+* While there is transparent object such as glass, water drop between the measured object and the LiDAR sensor, the reading might wrong.
	875	+* The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
	876	+* The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window.
	877	+
	878	+= 4.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
	879	+
874	874	(((
875	875	(((
876		-Use can configure LDDS75 via AT Command or LoRaWAN Downlink.
	882	+Use can configure LLDS12 via AT Command or LoRaWAN Downlink.
877	877	)))
878	878	)))
879	879
...	...	@@ -894,7 +894,7 @@
894	894	)))
895	895
896	896	(((
897		-There are two kinds of commands to configure LDDS75, they are:
	903	+There are two kinds of commands to configure LLDS12, they are:
898	898	)))
899	899	)))
900	900
...	...	@@ -935,152 +935,352 @@
935	935
936	936	* (((
937	937	(((
938		-(% style="color:#4f81bd" %)** Commands special design for LDDS75**
	944	+(% style="color:#4f81bd" %)** Commands special design for LLDS12**
939	939	)))
940	940	)))
941	941
942	942	(((
943	943	(((
944		-These commands only valid for LDDS75, as below:
	950	+These commands only valid for LLDS12, as below:
945	945	)))
946	946	)))
947	947
948	948
949	949
950		-== 3.1  Access AT Commands ==
	956	+== 4.1  Set Transmit Interval Time ==
951	951
952		-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.
	958	+Feature: Change LoRaWAN End Node Transmit Interval.
953	953
954		-[[image:image-20220610172924-4.png||height="483" width="988"]]
	960	+(% style="color:#037691" %)**AT Command: AT+TDC**
955	955
	962	+[[image:image-20220607171554-8.png]]
956	956
957		-Or if you have below board, use below connection:
958	958
	965	+(((
	966	+(% style="color:#037691" %)**Downlink Command: 0x01**
	967	+)))
959	959
960		-[[image:image-20220610172924-5.png]]
	969	+(((
	970	+Format: Command Code (0x01) followed by 3 bytes time value.
	971	+)))
961	961
	973	+(((
	974	+If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
	975	+)))
962	962
963		-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:
	977	+* (((
	978	+Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
	979	+)))
	980	+* (((
	981	+Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
	982	+)))
964	964
	984	+== 4.2  Set Interrupt Mode ==
965	965
966		- [[image:image-20220610172924-6.png||height="601" width="860"]]
	986	+Feature, Set Interrupt mode for GPIO_EXIT.
967	967
	988	+(% style="color:#037691" %)**AT Command: AT+INTMOD**
968	968
	990	+[[image:image-20220610105806-2.png]]
969	969
970		-== 3.2  Set Transmit Interval Time ==
971	971
972		-Feature: Change LoRaWAN End Node Transmit Interval.
	993	+(((
	994	+(% style="color:#037691" %)**Downlink Command: 0x06**
	995	+)))
973	973
974		-(% style="color:#037691" %)**AT Command: AT+TDC**
	997	+(((
	998	+Format: Command Code (0x06) followed by 3 bytes.
	999	+)))
975	975
976		-[[image:image-20220610173409-7.png]]
	1001	+(((
	1002	+This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
	1003	+)))
977	977
	1005	+* (((
	1006	+Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
	1007	+)))
	1008	+* (((
	1009	+Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
	1010	+)))
978	978
	1012	+== 4.3  Get Firmware Version Info ==
	1013	+
	1014	+Feature: use downlink to get firmware version.
	1015	+
	1016	+(% style="color:#037691" %)**Downlink Command: 0x26**
	1017	+
	1018	+[[image:image-20220607171917-10.png]]
	1019	+
	1020	+* Reply to the confirmation package: 26 01
	1021	+* Reply to non-confirmed packet: 26 00
	1022	+
	1023	+Device will send an uplink after got this downlink command. With below payload:
	1024	+
	1025	+Configures info payload:
	1026	+
	1027	+(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
	1028	+|=(((
	1029	+**Size(bytes)**
	1030	+)))|=**1**|=**1**|=**1**|=**1**|=**1**|=**5**|=**1**
	1031	+|**Value**|Software Type|(((
	1032	+Frequency
	1033	+
	1034	+Band
	1035	+)))|Sub-band|(((
	1036	+Firmware
	1037	+
	1038	+Version
	1039	+)))|Sensor Type|Reserve|(((
	1040	+[[Message Type>>||anchor="H2.3.7A0MessageType"]]
	1041	+Always 0x02
	1042	+)))
	1043	+
	1044	+**Software Type**: Always 0x03 for LLDS12
	1045	+
	1046	+
	1047	+**Frequency Band**:
	1048	+
	1049	+*0x01: EU868
	1050	+
	1051	+*0x02: US915
	1052	+
	1053	+*0x03: IN865
	1054	+
	1055	+*0x04: AU915
	1056	+
	1057	+*0x05: KZ865
	1058	+
	1059	+*0x06: RU864
	1060	+
	1061	+*0x07: AS923
	1062	+
	1063	+*0x08: AS923-1
	1064	+
	1065	+*0x09: AS923-2
	1066	+
	1067	+*0xa0: AS923-3
	1068	+
	1069	+
	1070	+**Sub-Band**: value 0x00 ~~ 0x08
	1071	+
	1072	+
	1073	+**Firmware Version**: 0x0100, Means: v1.0.0 version
	1074	+
	1075	+
	1076	+**Sensor Type**:
	1077	+
	1078	+0x01: LSE01
	1079	+
	1080	+0x02: LDDS75
	1081	+
	1082	+0x03: LDDS20
	1083	+
	1084	+0x04: LLMS01
	1085	+
	1086	+0x05: LSPH01
	1087	+
	1088	+0x06: LSNPK01
	1089	+
	1090	+0x07: LLDS12
	1091	+
	1092	+
	1093	+
	1094	+= 5.  Battery & How to replace =
	1095	+
	1096	+== 5.1  Battery Type ==
	1097	+
979	979	(((
980		-(% style="color:#037691" %)**Downlink Command: 0x01**
	1099	+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.
981	981	)))
982	982
983	983	(((
	1103	+The discharge curve is not linear so can’t simply use percentage to show the battery level. Below is the battery performance.
	1104	+)))
	1105	+
	1106	+[[image:1654593587246-335.png]]
	1107	+
	1108	+
	1109	+Minimum Working Voltage for the LLDS12:
	1110	+
	1111	+LLDS12:  2.45v ~~ 3.6v
	1112	+
	1113	+
	1114	+
	1115	+== 5.2  Replace Battery ==
	1116	+
984	984	(((
985		-Format: Command Code (0x01) followed by 3 bytes time value.
	1118	+Any battery with range 2.45 ~~ 3.6v can be a replacement. We recommend to use Li-SOCl2 Battery.
	1119	+)))
986	986
987		-If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
	1121	+(((
	1122	+And make sure the positive and negative pins match.
	1123	+)))
988	988
989		-* Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
990		-* Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
	1125	+
	1126	+
	1127	+== 5.3  Power Consumption Analyze ==
	1128	+
	1129	+(((
	1130	+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.
991	991	)))
992	992
	1133	+(((
	1134	+Instruction to use as below:
	1135	+)))
993	993
994		-
	1137	+
	1138	+**Step 1**: Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
	1139	+
	1140	+[[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/]]
	1141	+
	1142	+
	1143	+**Step 2**: Open it and choose
	1144	+
	1145	+* Product Model
	1146	+* Uplink Interval
	1147	+* Working Mode
	1148	+
	1149	+And the Life expectation in difference case will be shown on the right.
	1150	+
	1151	+[[image:1654593605679-189.png]]
	1152	+
	1153	+
	1154	+The battery related documents as below:
	1155	+
	1156	+* (((
	1157	+[[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
995	995	)))
	1159	+* (((
	1160	+[[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
	1161	+)))
	1162	+* (((
	1163	+[[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]]
	1164	+)))
996	996
997		-== 3.3  Set Interrupt Mode ==
	1166	+[[image:image-20220607172042-11.png]]
998	998
999		-Feature, Set Interrupt mode for GPIO_EXIT.
1000	1000
1001		-(% style="color:#037691" %)**Downlink Command: AT+INTMOD**
1002	1002
1003		-[[image:image-20220610174917-9.png]]
	1170	+=== 5.3.1  ​Battery Note ===
1004	1004
	1172	+(((
	1173	+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.
	1174	+)))
1005	1005
1006		-(% style="color:#037691" %)**Downlink Command: 0x06**
1007	1007
1008		-Format: Command Code (0x06) followed by 3 bytes.
1009	1009
1010		-This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
	1178	+=== ​5.3.2  Replace the battery ===
1011	1011
1012		-* Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
1013		-* Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
	1180	+(((
	1181	+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.
	1182	+)))
1014	1014
	1184	+(((
	1185	+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)
	1186	+)))
1015	1015
1016	1016
1017		-= 4.  FAQ =
1018	1018
1019		-== 4.1  What is the frequency plan for LDDS75? ==
	1190	+= 6.  Use AT Command =
1020	1020
1021		-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"]]
	1192	+== 6.1  Access AT Commands ==
1022	1022
	1194	+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.
1023	1023
	1196	+[[image:1654593668970-604.png]]
1024	1024
1025		-== 4.2  How to change the LoRa Frequency Bands/Region ==
	1198	+**Connection:**
1026	1026
1027		-You can follow the instructions for [[how to upgrade image>>||anchor="H2.8A0200BFirmwareChangeLog"]].
1028		-When downloading the images, choose the required image file for download. ​
	1200	+(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
1029	1029
	1202	+(% style="background-color:yellow" %)** USB TTL TXD  <~-~-~-~-> UART_RXD**
1030	1030
	1204	+(% style="background-color:yellow" %)** USB TTL RXD  <~-~-~-~-> UART_TXD**
1031	1031
1032		-== 4.3  Can I use LDDS75 in condensation environment? ==
1033	1033
1034		-LDDS75 is not suitable to be used in condensation environment. Condensation on the LDDS75 probe will affect the reading and always got 0.
	1207	+(((
	1208	+(((
	1209	+In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LLDS12.
	1210	+)))
1035	1035
	1212	+(((
	1213	+LLDS12 will output system info once power on as below:
	1214	+)))
	1215	+)))
1036	1036
1037	1037
1038		-= 5.  Trouble Shooting =
	1218	+ [[image:1654593712276-618.png]]
1039	1039
1040		-== 5.1  Why I can’t join TTN V3 in US915 / AU915 bands? ==
	1220	+Valid AT Command please check [[Configure Device>>||anchor="H4.A0ConfigureLLDS12viaATCommandorLoRaWANDownlink"]].
1041	1041
1042		-It is due to channel mapping. Please see below link:  [[Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1043	1043
	1223	+= 7.  FAQ =
1044	1044
1045		-== 5.2  AT Command input doesn't work ==
	1225	+== 7.1  How to change the LoRa Frequency Bands/Region ==
1046	1046
	1227	+You can follow the instructions for [[how to upgrade image>>||anchor="H2.8A0200BFirmwareChangeLog"]].
	1228	+When downloading the images, choose the required image file for download. ​
	1229	+
	1230	+
	1231	+= 8.  Trouble Shooting =
	1232	+
	1233	+== 8.1  AT Commands input doesn’t work ==
	1234	+
	1235	+
	1236	+(((
1047	1047	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.
	1238	+)))
1048	1048
	1240	+
	1241	+== 8.2  Significant error between the output distant value of LiDAR and actual distance ==
	1242	+
	1243	+
1049	1049	(((
	1245	+(% 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.)
	1246	+)))
	1247	+
	1248	+(((
	1249	+Troubleshooting: Please avoid use of this product under such circumstance in practice.
	1250	+)))
	1251	+
	1252	+(((
1050	1050
1051	1051	)))
1052	1052
	1256	+(((
	1257	+(% style="color:blue" %)**Cause ②**(%%)**: **The IR-pass filters are blocked.
	1258	+)))
1053	1053
1054		-= 6.  Order Info =
	1260	+(((
	1261	+Troubleshooting: please use dry dust-free cloth to gently remove the foreign matter.
	1262	+)))
1055	1055
1056	1056
1057		-Part Number **:** (% style="color:blue" %)**LDDS75-XX-YY**
1058	1058
	1266	+= 9.  Order Info =
1059	1059
1060		-(% style="color:blue" %)**XX**(%%)**: **The default frequency band
1061	1061
1062		-* (% style="color:red" %)**AS923 **(%%)**:** LoRaWAN AS923 band
1063		-* (% style="color:red" %)**AU915 **(%%)**:** LoRaWAN AU915 band
1064		-* (% style="color:red" %)**EU433 **(%%)**:** LoRaWAN EU433 band
1065		-* (% style="color:red" %)**EU868 **(%%)**:** LoRaWAN EU868 band
1066		-* (% style="color:red" %)**KR920 **(%%)**:** LoRaWAN KR920 band
1067		-* (% style="color:red" %)**US915 **(%%)**:** LoRaWAN US915 band
1068		-* (% style="color:red" %)**IN865 **(%%)**:**  LoRaWAN IN865 band
1069		-* (% style="color:red" %)**CN470 **(%%)**:** LoRaWAN CN470 band
	1269	+Part Number: (% style="color:blue" %)**LLDS12-XX**
1070	1070
1071		-(% style="color:blue" %)**YY**(%%): Battery Option
1072	1072
1073		-* (% style="color:red" %)**4 **(%%)**: **4000mAh battery
1074		-* (% style="color:red" %)**8 **(%%)**:** 8500mAh battery
	1272	+(% style="color:blue" %)**XX**(%%): The default frequency band
1075	1075
	1274	+* (% style="color:red" %)**AS923**(%%):  LoRaWAN AS923 band
	1275	+* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
	1276	+* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
	1277	+* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
	1278	+* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
	1279	+* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
	1280	+* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
	1281	+* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1076	1076
1077	1077
1078		-= 7. ​ Packing Info =
	1284	+= 10. ​ Packing Info =
1079	1079
1080	1080
1081	1081	**Package Includes**:
1082	1082
1083		-* LDDS75 LoRaWAN Distance Detection Sensor x 1
	1289	+* LLDS12 LoRaWAN LiDAR Distance Sensor x 1
1084	1084
1085	1085	**Dimension and weight**:
1086	1086
...	...	@@ -1090,8 +1090,7 @@
1090	1090	* Weight / pcs : g
1091	1091
1092	1092
	1299	+= 11.  ​Support =
1093	1093
1094		-= 8.  ​Support =
1095		-
1096	1096	* 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.
1097	1097	* 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]].

1654848616367-242.png

Author

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

Size

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

Content

1654849068701-275.png

Author

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

Size

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

Content

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

image-20220610161353-4.png

Author

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

Size

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

Content

image-20220610161353-5.png

Author

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

Size

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

Content

image-20220610161353-6.png

Author

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

Size

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

Content

image-20220610161353-7.png

Author

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

Size

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

Content

image-20220610161538-8.png

Author

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

Size

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

Content

image-20220610161538-9.png

Author

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

Size

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

Content

image-20220610161724-10.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-180.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