Skip to Content
Version 113.4 by Xiaoling on 2023/11/10 09:32
Show last authors
1 (% style="text-align:center" %)
2 [[image:image-20231110085342-2.png||height="481" width="481"]]
3
4
5
6
7
8
9
10
11 **Table of Contents：**
12
13 {{toc/}}
14
15
16
17
18
19
20 = 1. Introduction =
21
22 == 1.1 What is LoRaWAN Smart Distance Detector ==
23
24
25 The Dragino (% style="color:blue" %)**DS20L is a smart distance detector**(%%) base on long-range wireless LoRaWAN technology. It uses (% style="color:blue" %)**LiDAR sensor**(%%) to detect the distance between DS20L and object, then DS20L will send the distance data to the IoT Platform via LoRaWAN.
26
27 DS20L allows users to send data and reach extremely long ranges via LoRaWAN. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current 
28 consumption. It targets professional wireless sensor network applications such smart cities, building automation, and so on.
29
30 DS20L has a (% style="color:blue" %)**built-in 2400mAh non-chargeable battery**(%%) for long-term use up to several years*. Users can also power DS20L with an external power source for (% style="color:blue" %)**continuous measuring and distance alarm / counting purposes.**
31
32 DS20L is fully compatible with (% style="color:blue" %)**LoRaWAN v1.0.3 Class A protocol**(%%), it can work with a standard LoRaWAN gateway.
33
34 DS20L supports (% style="color:blue" %)**Datalog feature**(%%). It will record the data when there is no network coverage and users can retrieve the sensor value later to ensure no miss for every sensor reading.
35
36 [[image:image-20231110091506-4.png||height="391" width="768"]]
37
38
39 == 1.2 ​Features ==
40
41
42 * LoRaWAN Class A protocol
43 * LiDAR distance detector, range 3 ~~ 200cm
44 * Periodically detect or continuously detect mode
45 * AT Commands to change parameters
46 * Remotely configure parameters via LoRaWAN Downlink
47 * Alarm & Counting mode
48 * Datalog Feature
49 * Firmware upgradable via program port or LoRa protocol
50 * Built-in 2400mAh battery or power by external power source
51
52 == 1.3 Specification ==
53
54
55 (% style="color:#037691" %)**Common DC Characteristics:**
56
57 * Supply Voltage: built in 8500mAh Li-SOCI2 battery , 2.5v ~~ 3.6v
58 * Operating Temperature: -40 ~~ 85°C
59
60 (% style="color:#037691" %)**Probe Specification:**
61
62 * Measure Range: 3cm~~200cm @ 90% reflectivity
63 * Accuracy: ±2cm @ (3cm~~100cm); ±5% @ (100~~200cm)
64 * ToF FoV: ±9°, Total 18°
65 * Light source: VCSEL
66
67 (% style="color:#037691" %)**LoRa Spec:**
68
69 * Frequency Range,  Band 1 (HF): 862 ~~ 1020 Mhz
70 * Max +22 dBm constant RF output vs.
71 * RX sensitivity: down to -139 dBm.
72 * Excellent blocking immunity
73
74 (% style="color:#037691" %)**Battery:**
75
76 * Li/SOCI2 un-chargeable battery
77 * Capacity: 8500mAh
78 * Self-Discharge: <1% / Year @ 25°C
79 * Max continuously current: 130mA
80 * Max boost current: 2A, 1 second
81
82 (% style="color:#037691" %)**Power Consumption**
83
84 * Sleep Mode: 5uA @ 3.3v
85 * LoRa Transmit Mode: 125mA @ 20dBm, 82mA @ 14dBm
86
87 == 1.4 Applications ==
88
89
90 * Horizontal distance measurement
91 * Parking management system
92 * Object proximity and presence detection
93 * Intelligent trash can management system
94 * Robot obstacle avoidance
95 * Automatic control
96 * Sewer
97
98 (% style="display:none" %)
99
100 == 1.5 Sleep mode and working mode ==
101
102
103 (% style="color:blue" %)**Deep Sleep Mode: **(%%)Sensor doesn't have any LoRaWAN activate. This mode is used for storage and shipping to save battery life.
104
105 (% style="color:blue" %)**Working Mode:** (%%)In this mode, Sensor will work as LoRaWAN Sensor to Join LoRaWAN network and send out sensor data to server. Between each sampling/tx/rx periodically, sensor will be in IDLE mode), in IDLE mode, sensor has the same power consumption as Deep Sleep mode.
106
107
108 == 1.6 Button & LEDs ==
109
110
111 [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png]]
112
113
114 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
115 |=(% style="width: 167px;background-color:#4F81BD;color:white" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 225px;background-color:#4F81BD;color:white" %)**Action**
116 |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)(((
117 If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once.
118 Meanwhile, BLE module will be active and user can connect via BLE to configure device.
119 )))
120 |(% style="width:167px" %)Pressing ACT for more than 3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)(((
121 (% style="color:green" %)**Green led**(%%) will fast blink 5 times, device will enter (% style="color:#037691" %)**OTA mode**(%%) for 3 seconds. And then start to JOIN LoRaWAN network.
122 (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network.
123 Once sensor is active, BLE module will be active and user can connect via BLE to configure device, no matter if device join or not join LoRaWAN network.
124 )))
125 |(% style="width:167px" %)Fast press ACT 5 times.|(% style="width:117px" %)Deactivate Device|(% style="width:225px" %)(% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means device is in Deep Sleep Mode.
126
127 == 1.7 BLE connection ==
128
129
130 LDS12-LB support BLE remote configure.
131
132 BLE can be used to configure the parameter of sensor or see the console output from sensor. BLE will be only activate on below case:
133
134 * Press button to send an uplink
135 * Press button to active device.
136 * Device Power on or reset.
137
138 If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode.
139
140
141 == 1.8 Pin Definitions ==
142
143
144 [[image:image-20230805144259-1.png||height="413" width="741"]]
145
146 == 1.9 Mechanical ==
147
148
149 [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675143884058-338.png]]
150
151
152 [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675143899218-599.png]]
153
154
155 [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675143909447-639.png]]
156
157
158 (% style="color:blue" %)**Probe Mechanical:**
159
160
161 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654827224480-952.png?rev=1.1||alt="1654827224480-952.png"]]
162
163
164 = 2. Configure LDS12-LB to connect to LoRaWAN network =
165
166 == 2.1 How it works ==
167
168
169 The LDS12-LB is configured as (% style="color:#037691" %)**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 press the button to activate the LDS12-LB. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes.
170
171 (% style="display:none" %) (%%)
172
173 == 2.2 ​Quick guide to connect to LoRaWAN server (OTAA) ==
174
175
176 Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LPS8v2>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/228-lps8v2.html]] as a LoRaWAN gateway in this example.
177
178 The LPS8v2 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server.
179
180 [[image:image-20231110091447-3.png||height="383" width="752"]](% style="display:none" %)
181
182
183 (% style="color:blue" %)**Step 1:**(%%) Create a device in TTN with the OTAA keys from LDS12-LB.
184
185 Each LDS12-LB is shipped with a sticker with the default device EUI as below:
186
187 [[image:image-20230426084152-1.png||alt="图片-20230426084152-1.png" height="233" width="502"]]
188
189
190 You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
191
192
193 (% style="color:blue" %)**Register the device**
194
195 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50v2-S31-S31B%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20User%20Manual/WebHome/1654935135620-998.png?rev=1.1||alt="1654935135620-998.png"]]
196
197
198 (% style="color:blue" %)**Add APP EUI and DEV EUI**
199
200 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50v2-S31-S31B%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20User%20Manual/WebHome/image-20220611161308-4.png?width=753&height=551&rev=1.1||alt="图片-20220611161308-4.png"]]
201
202
203 (% style="color:blue" %)**Add APP EUI in the application**
204
205
206 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50v2-S31-S31B%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20User%20Manual/WebHome/image-20220611161308-5.png?width=742&height=601&rev=1.1||alt="图片-20220611161308-5.png"]]
207
208
209 (% style="color:blue" %)**Add APP KEY**
210
211 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50v2-S31-S31B%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20User%20Manual/WebHome/image-20220611161308-6.png?width=744&height=485&rev=1.1||alt="图片-20220611161308-6.png"]]
212
213
214 (% style="color:blue" %)**Step 2:**(%%) Activate on LDS12-LB
215
216
217 Press the button for 5 seconds to activate the LDS12-LB.
218
219 (% style="color:green" %)**Green led**(%%) will fast blink 5 times, device will enter (% style="color:blue" %)**OTA mode**(%%) for 3 seconds. And then start to JOIN LoRaWAN network. (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network.
220
221 After join success, it will start to upload messages to TTN and you can see the messages in the panel.
222
223
224 == 2.3 ​Uplink Payload ==
225
226 === 2.3.1 Device Status, FPORT~=5 ===
227
228
229 Users can use the downlink command(**0x26 01**) to ask LDS12-LB to send device configure detail, include device configure status. LDS12-LB will uplink a payload via FPort=5 to server.
230
231 The Payload format is as below.
232
233 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
234 |=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
235 **Size(bytes)**
236 )))|=(% style="width: 100px; background-color: #4F81BD;color:white;" %)**1**|=(% style="width: 100px; background-color: #4F81BD;color:white;" %)**2**|=(% style="background-color: #4F81BD;color:white; width: 100px;" %)**1**|=(% style="background-color: #4F81BD;color:white; width: 100px;" %)**1**|=(% style="background-color: #4F81BD;color:white; width: 50px;" %)**2**
237 |(% style="width:62.5px" %)Value|(% style="width:110px" %)Sensor Model|(% style="width:48px" %)Firmware Version|(% style="width:94px" %)Frequency Band|(% style="width:91px" %)Sub-band|(% style="width:60px" %)BAT
238
239 Example parse in TTNv3
240
241 [[image:image-20230805103904-1.png||height="131" width="711"]]
242
243 (% style="color:blue" %)**Sensor Model**(%%): For LDS12-LB, this value is 0x24
244
245 (% style="color:blue" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version
246
247 (% style="color:blue" %)**Frequency Band**:
248
249 0x01: EU868
250
251 0x02: US915
252
253 0x03: IN865
254
255 0x04: AU915
256
257 0x05: KZ865
258
259 0x06: RU864
260
261 0x07: AS923
262
263 0x08: AS923-1
264
265 0x09: AS923-2
266
267 0x0a: AS923-3
268
269 0x0b: CN470
270
271 0x0c: EU433
272
273 0x0d: KR920
274
275 0x0e: MA869
276
277 (% style="color:blue" %)**Sub-Band**:
278
279 AU915 and US915:value 0x00 ~~ 0x08
280
281 CN470: value 0x0B ~~ 0x0C
282
283 Other Bands: Always 0x00
284
285 (% style="color:blue" %)**Battery Info**:
286
287 Check the battery voltage.
288
289 Ex1: 0x0B45 = 2885mV
290
291 Ex2: 0x0B49 = 2889mV
292
293
294 === 2.3.2 Uplink Payload, FPORT~=2 ===
295
296
297 (((
298 LDS12-LB will send this uplink **after** Device Status once join the LoRaWAN network successfully. And LDS12-LB will:
299
300 periodically send this uplink every 20 minutes, this interval [[can be changed>>||anchor="H3.3.1SetTransmitIntervalTime"]].
301
302 Uplink Payload totals 11 bytes.
303 )))
304
305 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
306 |=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
307 **Size(bytes)**
308 )))|=(% style="width: 30px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 50px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 70px;background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD;color:white; width: 80px;" %)**1**|=(% style="background-color: #4F81BD;color:white; width: 70px;" %)**1**|=(% style="background-color: #4F81BD;color:white; width: 70px;" %)**1**
309 |(% style="width:62.5px" %)Value|(% style="width:62.5px" %)[[BAT>>||anchor="HBatteryInfo"]]|(% style="width:62.5px" %)(((
310 [[Temperature DS18B20>>||anchor="HDS18B20Temperaturesensor"]]
311 )))|[[Distance>>||anchor="HDistance"]]|[[Distance signal strength>>||anchor="HDistancesignalstrength"]]|(% style="width:122px" %)(((
312 [[Interrupt flag & Interrupt_level>>||anchor="HInterruptPin26A0InterruptLevel"]]
313 )))|(% style="width:54px" %)[[LiDAR temp>>||anchor="HLiDARtemp"]]|(% style="width:96px" %)(((
314 [[Message Type>>||anchor="HMessageType"]]
315 )))
316
317 [[image:image-20230805104104-2.png||height="136" width="754"]]
318
319
320 ==== (% style="color:blue" %)**Battery Info**(%%) ====
321
322
323 Check the battery voltage for LDS12-LB.
324
325 Ex1: 0x0B45 = 2885mV
326
327 Ex2: 0x0B49 = 2889mV
328
329
330 ==== (% style="color:blue" %)**DS18B20 Temperature sensor**(%%) ====
331
332
333 This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
334
335
336 **Example**:
337
338 If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
339
340 If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
341
342
343 ==== (% style="color:blue" %)**Distance**(%%) ====
344
345
346 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.
347
348
349 **Example**:
350
351 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.
352
353
354 ==== (% style="color:blue" %)**Distance signal strength**(%%) ====
355
356
357 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.
358
359
360 **Example**:
361
362 If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
363
364 Customers can judge whether they need to adjust the environment based on the signal strength.
365
366
367 **1) When the sensor detects valid data:**
368
369 [[image:image-20230805155335-1.png||height="145" width="724"]]
370
371
372 **2) When the sensor detects invalid data:**
373
374 [[image:image-20230805155428-2.png||height="139" width="726"]]
375
376
377 **3) When the sensor is not connected:**
378
379 [[image:image-20230805155515-3.png||height="143" width="725"]]
380
381
382 ==== (% style="color:blue" %)**Interrupt Pin & Interrupt Level**(%%) ====
383
384
385 This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H3.3.2SetInterruptMode"]] for the hardware and software set up.
386
387 Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.8PinDefinitions"]] of GPIO_EXTI .
388
389 **Example:**
390
391 If byte[0]&0x01=0x00 : Normal uplink packet.
392
393 If byte[0]&0x01=0x01 : Interrupt Uplink Packet.
394
395
396 ==== (% style="color:blue" %)**LiDAR temp**(%%) ====
397
398
399 Characterize the internal temperature value of the sensor.
400
401 **Example: **
402 If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
403 If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
404
405
406 ==== (% style="color:blue" %)**Message Type**(%%) ====
407
408
409 (((
410 For a normal uplink payload, the message type is always 0x01.
411 )))
412
413 (((
414 Valid Message Type:
415 )))
416
417 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:499px" %)
418 |=(% style="width: 161px;background-color:#4F81BD;color:white" %)**Message Type Code**|=(% style="width: 164px;background-color:#4F81BD;color:white" %)**Description**|=(% style="width: 174px;background-color:#4F81BD;color:white" %)**Payload**
419 |(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)Normal Uplink Payload
420 |(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)Configure Info Payload
421
422 [[image:image-20230805150315-4.png||height="233" width="723"]]
423
424
425 === 2.3.3 Historical measuring distance, FPORT~=3 ===
426
427
428 LDS12-LB stores sensor values and users can retrieve these history values via the [[downlink command>>||anchor="H2.5.4Pollsensorvalue"]].
429
430 The historical payload includes one or multiplies entries and every entry has the same payload as Real-Time measuring distance.
431
432 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
433 |=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
434 **Size(bytes)**
435 )))|=(% style="width: 80px;background-color:#4F81BD;color:white" %)1|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 50px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 70px;background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD; color: white; width: 85px;" %)**1**|=(% style="background-color: #4F81BD; color: white; width: 85px;" %)4
436 |(% style="width:62.5px" %)Value|(% style="width:62.5px" %)Interrupt flag & Interrupt_level|(% style="width:62.5px" %)(((
437 Reserve(0xFF)
438 )))|Distance|Distance signal strength|(% style="width:88px" %)(((
439 LiDAR temp
440 )))|(% style="width:85px" %)Unix TimeStamp
441
442 **Interrupt flag & Interrupt level:**
443
444 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:480px" %)
445 |=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
446 **Size(bit)**
447 )))|=(% style="width: 90px;background-color:#4F81BD;color:white" %)**bit7**|=(% style="width: 90px;background-color:#4F81BD;color:white" %)**bit6**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**[bit5:bit2]**|=(% style="width: 90px; background-color: #4F81BD; color: white;" %)**bit1**|=(% style="background-color: #4F81BD; color: white; width: 90px;" %)**bit0**
448 |(% style="width:62.5px" %)Value|(% style="width:62.5px" %)No ACK message|(% style="width:62.5px" %)Poll Message Flag|Reserve|(% style="width:91px" %)Interrupt level|(% style="width:88px" %)(((
449 Interrupt flag
450 )))
451
452 * (((
453 Each data entry is 11 bytes and has the same structure as [[Uplink Payload>>||anchor="H2.3.2UplinkPayload2CFPORT3D2"]], to save airtime and battery, LDS12-LB will send max bytes according to the current DR and Frequency bands.
454 )))
455
456 For example, in the US915 band, the max payload for different DR is:
457
458 **a) DR0:** max is 11 bytes so one entry of data
459
460 **b) DR1:** max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
461
462 **c) DR2:** total payload includes 11 entries of data
463
464 **d) DR3:** total payload includes 22 entries of data.
465
466 If LDS12-LB doesn't have any data in the polling time. It will uplink 11 bytes of 0
467
468
469 **Downlink:**
470
471 0x31 64 CC 68 0C 64 CC 69 74 05
472
473 [[image:image-20230805144936-2.png||height="113" width="746"]]
474
475 **Uplink:**
476
477 43 FF 0E 10 00 B0 1E 64 CC 68 0C 40 FF 0D DE 00 A8 1E 64 CC 68 29 40 FF 09 92 00 D3 1E 64 CC 68 65 40 FF 02 3A 02 BC 1E 64 CC 68 A1 41 FF 0E 1A 00 A4 1E 64 CC 68 C0 40 FF 0D 2A 00 B8 1E 64 CC 68 E8 40 FF 00 C8 11 6A 1E 64 CC 69 24 40 FF 0E 24 00 AD 1E 64 CC 69 6D
478
479
480 **Parsed Value:**
481
482 [DISTANCE , DISTANCE_SIGNAL_STRENGTH，LIDAR_TEMP，EXTI_STATUS , EXTI_FLAG , TIME]
483
484
485 [360,176,30,High,True,2023-08-04 02:53:00],
486
487 [355,168,30,Low,False,2023-08-04 02:53:29],
488
489 [245,211,30,Low,False,2023-08-04 02:54:29],
490
491 [57,700,30,Low,False,2023-08-04 02:55:29],
492
493 [361,164,30,Low,True,2023-08-04 02:56:00],
494
495 [337,184,30,Low,False,2023-08-04 02:56:40],
496
497 [20,4458,30,Low,False,2023-08-04 02:57:40],
498
499 [362,173,30,Low,False,2023-08-04 02:58:53],
500
501
502 **History read from serial port：**
503
504 [[image:image-20230805145056-3.png]]
505
506
507 === 2.3.4 Decode payload in The Things Network ===
508
509
510 While using TTN network, you can add the payload format to decode the payload.
511
512 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654592762713-715.png?rev=1.1||alt="1654592762713-715.png"]]
513
514
515 (((
516 The payload decoder function for TTN is here:
517 )))
518
519 (((
520 LDS12-LB TTN Payload Decoder:  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]
521 )))
522
523
524 == 2.4 ​Show Data in DataCake IoT Server ==
525
526
527 (((
528 [[DATACAKE>>url:https://datacake.co/]] provides a human friendly interface to show the sensor data, once we have data in TTN, we can use [[DATACAKE>>url:https://datacake.co/]] to connect to TTN and see the data in DATACAKE. Below are the steps:
529 )))
530
531
532 (((
533 (% style="color:blue" %)**Step 1**(%%)**: Be sure that your device is programmed and properly connected to the network at this time.**
534 )))
535
536 (((
537 (% style="color:blue" %)**Step 2**(%%)**: To configure the Application to forward data to DATACAKE you will need to add integration. To add the DATACAKE integration, perform the following steps:**
538 )))
539
540
541 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDDS75%20-%20LoRaWAN%20Distance%20Detection%20Sensor%20User%20Manual/WebHome/1654592790040-760.png?rev=1.1||alt="1654592790040-760.png"]]
542
543
544 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDDS75%20-%20LoRaWAN%20Distance%20Detection%20Sensor%20User%20Manual/WebHome/1654592800389-571.png?rev=1.1||alt="1654592800389-571.png"]]
545
546
547 (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
548
549 (% style="color:blue" %)**Step 4**(%%)**: Search the LDS12-LB and add DevEUI.**
550
551 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDDS75%20-%20LoRaWAN%20Distance%20Detection%20Sensor%20User%20Manual/WebHome/1654851029373-510.png?rev=1.1||alt="1654851029373-510.png"]]
552
553
554 After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
555
556 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDDS75%20-%20LoRaWAN%20Distance%20Detection%20Sensor%20User%20Manual/WebHome/image-20220610165129-11.png?width=1088&height=595&rev=1.1||alt="image-20220610165129-11.png"]]
557
558
559 == 2.5 Datalog Feature ==
560
561
562 Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, LDS12-LB will store the reading for future retrieving purposes.
563
564
565 === 2.5.1 Ways to get datalog via LoRaWAN ===
566
567
568 Set PNACKMD=1, LDS12-LB will wait for ACK for every uplink, when there is no LoRaWAN network,LDS12-LB will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
569
570 * (((
571 a) LDS12-LB will do an ACK check for data records sending to make sure every data arrive server.
572 )))
573 * (((
574 b) LDS12-LB will send data in **CONFIRMED Mode** when PNACKMD=1, but LDS12-LB won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink if LDS12-LB gets a ACK, LDS12-LB will consider there is a network connection and resend all NONE-ACK messages.
575 )))
576
577 Below is the typical case for the auto-update datalog feature (Set PNACKMD=1)
578
579 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/WebHome/image-20220703111700-2.png?width=1119&height=381&rev=1.1||alt="图片-20220703111700-2.png" height="381" width="1119"]]
580
581
582 === 2.5.2 Unix TimeStamp ===
583
584
585 LDS12-LB uses Unix TimeStamp format based on
586
587 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/WebHome/image-20220523001219-11.png?width=627&height=97&rev=1.1||alt="图片-20220523001219-11.png" height="97" width="627"]]
588
589 User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
590
591 Below is the converter example
592
593 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/WebHome/image-20220523001219-12.png?width=720&height=298&rev=1.1||alt="图片-20220523001219-12.png" height="298" width="720"]]
594
595
596 So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
597
598
599 === 2.5.3 Set Device Time ===
600
601
602 User need to set (% style="color:blue" %)**SYNCMOD=1**(%%) to enable sync time via MAC command.
603
604 Once LDS12-LB Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to LDS12-LB. If LDS12-LB fails to get the time from the server, LDS12-LB will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
605
606 (% style="color:red" %)**Note: LoRaWAN Server need to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature, Chirpstack,TTN V3 v3 and loriot support but TTN V3 v2 doesn't support. If server doesn't support this command, it will through away uplink packet with this command, so user will lose the packet with time request for TTN V3 v2 if SYNCMOD=1.**
607
608
609 === 2.5.4 Poll sensor value ===
610
611
612 Users can poll sensor values based on timestamps. Below is the downlink command.
613
614 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:425.818px" %)
615 |(% colspan="4" style="background-color:#4f81bd; color:white; width:423px" %)**Downlink Command to poll Open/Close status (0x31)**
616 |(% style="width:58px" %)**1byte**|(% style="width:127px" %)**4bytes**|(% style="width:124px" %)**4bytes**|(% style="width:114px" %)**1byte**
617 |(% style="width:58px" %)31|(% style="width:127px" %)Timestamp start|(% style="width:124px" %)Timestamp end|(% style="width:114px" %)Uplink Interval
618
619 (((
620 Timestamp start and Timestamp end-use Unix TimeStamp format as mentioned above. Devices will reply with all data logs during this period, using the uplink interval.
621 )))
622
623 (((
624 For example, downlink command [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/WebHome/image-20220518162852-1.png?rev=1.1||alt="image-20220518162852-1.png"]]
625 )))
626
627 (((
628 Is to check 2021/11/12 12:00:00 to 2021/11/12 15:00:00's data
629 )))
630
631 (((
632 Uplink Internal =5s，means LDS12-LB will send one packet every 5s. range 5~~255s.
633 )))
634
635
636 == 2.6 Frequency Plans ==
637
638
639 The LDS12-LB 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.
640
641 [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/]]
642
643
644 == 2.7 LiDAR ToF Measurement ==
645
646 === 2.7.1 Principle of Distance Measurement ===
647
648
649 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.
650
651 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654831757579-263.png?rev=1.1||alt="1654831757579-263.png"]]
652
653
654 === 2.7.2 Distance Measurement Characteristics ===
655
656
657 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:
658
659 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654831774373-275.png?rev=1.1||alt="1654831774373-275.png"]]
660
661
662 (((
663 (% style="color:blue" %)**① **(%%)Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable.
664 )))
665
666 (((
667 (% style="color:blue" %)**② **(%%)Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m.
668 )))
669
670 (((
671 (% style="color:blue" %)**③ **(%%)Represents the operating range of The LiDAR probe detecting white target with 90% reflectivity, 0.1-12m.
672 )))
673
674
675 (((
676 Vertical Coordinates: Represents the radius of light spot for The LiDAR probe at 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:
677 )))
678
679 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654831797521-720.png?rev=1.1||alt="1654831797521-720.png"]]
680
681 (((
682 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.
683 )))
684
685 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LLDS12-LoRaWAN%20LiDAR%20ToF%20Distance%20Sensor%20User%20Manual/WebHome/1654831810009-716.png?rev=1.1||alt="1654831810009-716.png"]]
686
687 (((
688 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.
689 )))
690
691
692 === 2.7.3 Notice of usage ===
693
694
695 Possible invalid /wrong reading for LiDAR ToF tech:
696
697 * Measure high reflectivity object such as: Mirror, Smooth ceramic tile, static milk surface, will have possible wrong readings.
698 * While there is transparent object such as glass, water drop between the measured object and the LiDAR sensor, the reading might be wrong.
699 * The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
700 * The sensor window is made by Acrylic. Don't touch it with alcohol material. This will destroy the sensor window.
701
702 === 2.7.4  Reflectivity of different objects ===
703
704
705 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:379px" %)
706 |=(% style="width: 54px;background-color:#4F81BD;color:white" %)Item|=(% style="width: 231px;background-color:#4F81BD;color:white" %)Material|=(% style="width: 94px;background-color:#4F81BD;color:white" %)Relectivity
707 |(% style="width:53px" %)1|(% style="width:229px" %)Black foam rubber|(% style="width:93px" %)2.4%
708 |(% style="width:53px" %)2|(% style="width:229px" %)Black fabric|(% style="width:93px" %)3%
709 |(% style="width:53px" %)3|(% style="width:229px" %)Black rubber|(% style="width:93px" %)4%
710 |(% style="width:53px" %)4|(% style="width:229px" %)Coal (different types of coal)|(% style="width:93px" %)4~~8%
711 |(% style="width:53px" %)5|(% style="width:229px" %)Black car paint|(% style="width:93px" %)5%
712 |(% style="width:53px" %)6|(% style="width:229px" %)Black Jam|(% style="width:93px" %)10%
713 |(% style="width:53px" %)7|(% style="width:229px" %)Opaque black plastic|(% style="width:93px" %)14%
714 |(% style="width:53px" %)8|(% style="width:229px" %)Clean rough board|(% style="width:93px" %)20%
715 |(% style="width:53px" %)9|(% style="width:229px" %)Translucent plastic bottle|(% style="width:93px" %)62%
716 |(% style="width:53px" %)10|(% style="width:229px" %)Carton cardboard|(% style="width:93px" %)68%
717 |(% style="width:53px" %)11|(% style="width:229px" %)Clean pine|(% style="width:93px" %)70%
718 |(% style="width:53px" %)12|(% style="width:229px" %)Opaque white plastic|(% style="width:93px" %)87%
719 |(% style="width:53px" %)13|(% style="width:229px" %)White Jam|(% style="width:93px" %)90%
720 |(% style="width:53px" %)14|(% style="width:229px" %)Kodak Standard Whiteboard|(% style="width:93px" %)100%
721 |(% style="width:53px" %)15|(% style="width:229px" %)(((
722 Unpolished white metal surface
723 )))|(% style="width:93px" %)130%
724 |(% style="width:53px" %)16|(% style="width:229px" %)Glossy light metal surface|(% style="width:93px" %)150%
725 |(% style="width:53px" %)17|(% style="width:229px" %)stainless steel|(% style="width:93px" %)200%
726 |(% style="width:53px" %)18|(% style="width:229px" %)Reflector plate, reflective tape|(% style="width:93px" %)>300%
727
728 = 3. Configure LDS12-LB =
729
730 == 3.1 Configure Methods ==
731
732
733 LDS12-LB supports below configure method:
734
735 * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]].
736
737 * AT Command via UART Connection : See [[UART Connection>>http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]].
738
739 * LoRaWAN Downlink.  Instruction for different platforms: See [[IoT LoRaWAN Server>>http://wiki.dragino.com/xwiki/bin/view/Main/]] section.
740
741 == 3.2 General Commands ==
742
743
744 These commands are to configure:
745
746 * General system settings like: uplink interval.
747
748 * LoRaWAN protocol & radio related command.
749
750 They are same for all Dragino Devices which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki:
751
752 [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
753
754
755 == 3.3 Commands special design for LDS12-LB ==
756
757
758 These commands only valid for LDS12-LB, as below:
759
760
761 === 3.3.1 Set Transmit Interval Time ===
762
763
764 (((
765 Feature: Change LoRaWAN End Node Transmit Interval.
766 )))
767
768 (((
769 (% style="color:blue" %)**AT Command: AT+TDC**
770 )))
771
772 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
773 |=(% style="width: 156px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 137px;background-color:#4F81BD;color:white" %)**Function**|=(% style="background-color:#4F81BD;color:white" %)**Response**
774 |(% style="width:156px" %)AT+TDC=?|(% style="width:137px" %)Show current transmit Interval|(((
775 30000
776 OK
777 the interval is 30000ms = 30s
778 )))
779 |(% style="width:156px" %)AT+TDC=60000|(% style="width:137px" %)Set Transmit Interval|(((
780 OK
781 Set transmit interval to 60000ms = 60 seconds
782 )))
783
784 (((
785 (% style="color:blue" %)**Downlink Command: 0x01**
786 )))
787
788 (((
789 Format: Command Code (0x01) followed by 3 bytes time value.
790 )))
791
792 (((
793 If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01.
794 )))
795
796 * (((
797 Example 1: Downlink Payload: 0100001E  ~/~/ Set Transmit Interval (TDC) = 30 seconds
798 )))
799 * (((
800 Example 2: Downlink Payload: 0100003C  ~/~/ Set Transmit Interval (TDC) = 60 seconds 
801
802
803
804 )))
805
806 === 3.3.2 Set Interrupt Mode ===
807
808
809 Feature, Set Interrupt mode for pin of GPIO_EXTI.
810
811 When AT+INTMOD=0 is set, GPIO_EXTI is used as a digital input port.
812
813 (% style="color:blue" %)**AT Command: AT+INTMOD**
814
815 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
816 |=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 197px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 158px;background-color:#4F81BD;color:white" %)**Response**
817 |(% style="width:154px" %)AT+INTMOD=?|(% style="width:196px" %)Show current interrupt mode|(% style="width:157px" %)(((
818 0
819 OK
820 the mode is 0 =Disable Interrupt
821 )))
822 |(% style="width:154px" %)(((
823 AT+INTMOD=2
824
825 (default)
826 )))|(% style="width:196px" %)(((
827 Set Transmit Interval
828 0. (Disable Interrupt),
829 ~1. (Trigger by rising and falling edge)
830 2. (Trigger by falling edge)
831 3. (Trigger by rising edge)
832 )))|(% style="width:157px" %)OK
833
834 (% style="color:blue" %)**Downlink Command: 0x06**
835
836 Format: Command Code (0x06) followed by 3 bytes.
837
838 This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
839
840 * Example 1: Downlink Payload: 06000000  ~/~/  Turn off interrupt mode
841
842 * Example 2: Downlink Payload: 06000003  ~/~/  Set the interrupt mode to rising edge trigger
843
844 === 3.3.3  Set Power Output Duration ===
845
846 Control the output duration 3V3(pin of VBAT_OUT) . Before each sampling, device will
847
848 ~1. first enable the power output to external sensor,
849
850 2. keep it on as per duration, read sensor value and construct uplink payload
851
852 3. final, close the power output.
853
854 (% style="color:blue" %)**AT Command: AT+3V3T**
855
856 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
857 |=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 197px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 158px;background-color:#4F81BD;color:white" %)**Response**
858 |(% style="width:154px" %)AT+3V3T=?|(% style="width:196px" %)Show 3V3 open time.|(% style="width:157px" %)0 (default)
859 OK
860 |(% style="width:154px" %)AT+3V3T=1000|(% style="width:196px" %)Close after a delay of 1000 milliseconds.|(% style="width:157px" %)OK
861 |(% style="width:154px" %)AT+3V3T=0|(% style="width:196px" %)Always turn on the power supply of 3V3 pin.|(% style="width:157px" %)OK
862 |(% style="width:154px" %)AT+3V3T=65535|(% style="width:196px" %)Always turn off the power supply of 3V3 pin.|(% style="width:157px" %)OK
863
864 (% style="color:blue" %)**Downlink Command: 0x07**(%%)
865 Format: Command Code (0x07) followed by 3 bytes.
866
867 The first byte is 01,the second and third bytes are the time to turn on.
868
869 * Example 1: Downlink Payload: 07 01 00 00  **~-~-->**  AT+3V3T=0
870 * Example 2: Downlink Payload: 07 01 01 F4  **~-~-->**  AT+3V3T=500
871 * Example 3: Downlink Payload: 07 01 FF FF  **~-~-->**  AT+3V3T=65535
872
873 = 4. Battery & Power Consumption =
874
875
876 LDS12-LB use ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
877
878 [[**Battery Info & Power Consumption Analyze**>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
879
880
881 = 5. OTA Firmware update =
882
883
884 (% class="wikigeneratedid" %)
885 User can change firmware LDS12-LB to:
886
887 * Change Frequency band/ region.
888
889 * Update with new features.
890
891 * Fix bugs.
892
893 Firmware and changelog can be downloaded from : **[[Firmware download link>>url:https://www.dropbox.com/sh/w1p7ukjrx49e62r/AAB3uCNCt-koYUvMkZUPBRSca?dl=0]]**
894
895 Methods to Update Firmware:
896
897 * (Recommanded way) OTA firmware update via wireless:  **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/]]**
898
899 * Update through UART TTL interface: **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]]**.
900
901 = 6. FAQ =
902
903 == 6.1 What is the frequency plan for LDS12-LB? ==
904
905
906 LDS12-LB 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"]]
907
908
909 = 7. Trouble Shooting =
910
911 == 7.1 AT Command input doesn't work ==
912
913
914 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:blue" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:blue" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
915
916
917 == 7.2 Significant error between the output distant value of LiDAR and actual distance ==
918
919
920 (((
921 (% 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.)
922 )))
923
924 (((
925 (% style="color:red" %)**Troubleshooting**(%%): Please avoid use of this product under such circumstance in practice.
926 )))
927
928
929 (((
930 (% style="color:blue" %)**Cause ②**(%%)**: **The IR-pass filters are blocked.
931 )))
932
933 (((
934 (% style="color:red" %)**Troubleshooting**(%%): please use dry dust-free cloth to gently remove the foreign matter.
935 )))
936
937
938 = 8. Order Info =
939
940
941 Part Number: (% style="color:blue" %)**LDS12-LB-XXX**
942
943 (% style="color:red" %)**XXX**(%%): **The default frequency band**
944
945 * (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band
946
947 * (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
948
949 * (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
950
951 * (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
952
953 * (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
954
955 * (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
956
957 * (% style="color:red" %)**IN865**(%%): LoRaWAN IN865 band
958
959 * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
960
961 = 9. ​Packing Info =
962
963
964 (% style="color:#037691" %)**Package Includes**:
965
966 * LDS12-LB LoRaWAN LiDAR ToF Distance Sensor x 1
967
968 (% style="color:#037691" %)**Dimension and weight**:
969
970 * Device Size: cm
971
972 * Device Weight: g
973
974 * Package Size / pcs : cm
975
976 * Weight / pcs : g
977
978 = 10. Support =
979
980
981 * 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.
982
983 * 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.cc>>mailto:Support@dragino.cc]].