Last modified by Xiaoling on 2025/04/27 11:48
Show last authors
1
2
3 (% style="text-align:center" %)
4 [[image:image-20220610095606-1.png]]
5
6
7
8
9
10
11 **Table of Contents:**
12
13 {{toc/}}
14
15
16
17 = 1.  Introduction =
18
19 == 1.1 ​ What is LoRaWAN LiDAR ToF Distance Sensor ==
20
21
22 (((
23 The Dragino LLDS12 is a (% style="color:blue" %)**LoRaWAN LiDAR ToF (Time of Flight) Distance Sensor**(%%) for Internet of Things solution. It is capable to measure the distance to an object as close as 10 centimeters (+/- 5cm up to 6m) and as far as 12 meters (+/-1% starting at 6m)!. The LiDAR probe uses laser induction technology for distance measurement.
24 )))
25
26 (((
27 The LLDS12 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
28 )))
29
30 (((
31 It detects the distance between the measured object and the sensor, and uploads the value via wireless to LoRaWAN IoT Server.
32 )))
33
34 (((
35 The LoRa wireless technology used in LLDS12 allows device to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption.
36 )))
37
38 (((
39 LLDS12 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use up to 5 years.
40 )))
41
42 (((
43 Each LLDS12 is pre-load with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect after power on.
44 )))
45
46
47 == ​1.2  Features ==
48
49
50 * LoRaWAN 1.0.3 Class A
51 * Ultra-low power consumption
52 * Laser technology for distance detection
53 * Measure Distance: 0.1m~~12m
54 * Accuracy :  ±5cm@(0.1-5m), ±1%@(5m-12m)
55 * Monitor Battery Level
56 * Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
57 * AT Commands to change parameters
58 * Uplink on periodically
59 * Downlink to change configure
60 * 8500mAh Battery for long-term use
61
62 == 1.3  Probe Specification ==
63
64
65 * Storage temperature: -20℃~~75℃
66 * Operating temperature : -20℃~~60℃
67 * Measure Distance:
68 ** 0.1m ~~ 12m @ 90% Reflectivity
69 ** 0.1m ~~ 4m @ 10% Reflectivity
70 * Accuracy : ±5cm@(0.1-5m), ±1%@(5m-12m)
71 * Distance resolution : 1cm
72 * Ambient light immunity : 70klux
73 * Enclosure rating : IP65
74 * Light source : LED
75 * Central wavelength : 850nm
76 * FOV : 3.6°
77 * Material of enclosure : ABS+PC
78 * Wire length : 25cm
79
80 == 1.4  Probe Dimension ==
81
82
83 [[image:1654827224480-952.png]]
84
85
86 == 1.5 ​ Applications ==
87
88
89 * Horizontal distance measurement
90 * Parking management system
91 * Object proximity and presence detection
92 * Intelligent trash can management system
93 * Robot obstacle avoidance
94 * Automatic control
95 * Sewer
96
97 == 1.6  Pin mapping and power on ==
98
99
100 [[image:1654827332142-133.png]]
101
102
103 = 2.  Configure LLDS12 to connect to LoRaWAN network =
104
105 == 2.1  How it works ==
106
107
108 (((
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.
110 )))
111
112 (((
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.
114 )))
115
116
117 == 2.2  ​Quick guide to connect to LoRaWAN server (OTAA) ==
118
119
120 (((
121 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 [[LG308>>url:http://www.dragino.com/products/lora/item/140-lg308.html]] as a LoRaWAN gateway in this example.
122 )))
123
124 (((
125 [[image:image-20250427113730-1.png]]
126 )))
127
128 (((
129 The LG308 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.
130 )))
131
132 (((
133
134
135 (% style="color:blue" %)**Step 1:**(%%) Create a device in TTN with the OTAA keys from LLDS12.
136 )))
137
138 (((
139 Each LLDS12 is shipped with a sticker with the default device EUI as below:
140 )))
141
142 [[image:image-20230426085359-1.png||height="250" width="538"]]
143
144
145 You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
146
147 **Create the application.**
148
149 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SAC01L_LoRaWAN_Temperature%26Humidity_Sensor_User_Manual/WebHome/image-20250423093843-1.png?width=756&height=264&rev=1.1||alt="image-20250423093843-1.png"]]
150
151 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111305-2.png?width=1000&height=572&rev=1.1||alt="image-20240907111305-2.png"]]
152
153
154 **Add devices to the created Application.**
155
156 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111659-3.png?width=977&height=185&rev=1.1||alt="image-20240907111659-3.png"]]
157
158 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111820-5.png?width=975&height=377&rev=1.1||alt="image-20240907111820-5.png"]]
159
160
161 **Enter end device specifics manually.**
162
163 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907112136-6.png?width=697&height=687&rev=1.1||alt="image-20240907112136-6.png"]]
164
165
166 **Add DevEUI and AppKey. Customize a platform ID for the device.**
167
168 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907112427-7.png?rev=1.1||alt="image-20240907112427-7.png"]]
169
170
171 (% style="color:blue" %)**Step 2:**(%%) Add decoder.
172
173 In TTN, user can add a custom payload so it shows friendly reading.
174
175 Click this link to get the decoder: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/]]
176
177 Below is TTN screen shot:
178
179 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS25-LBLDS25-LS--LoRaWAN_LiDAR_Distance_Auto-Clean_Sensor_User_Manual/WebHome/image-20241009140556-1.png?width=1184&height=488&rev=1.1||alt="image-20241009140556-1.png" height="488" width="1184"]]
180
181 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS25-LBLDS25-LS--LoRaWAN_LiDAR_Distance_Auto-Clean_Sensor_User_Manual/WebHome/image-20241009140603-2.png?width=1168&height=562&rev=1.1||alt="image-20241009140603-2.png" height="562" width="1168"]]
182
183
184 (% style="color:blue" %)**Step 3:**(%%) Power on LLDS12
185
186 Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
187
188 [[image:image-20220607170442-2.png]]
189
190 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.
191
192 [[image:1654833501679-968.png]]
193
194
195 == 2.3  ​Uplink Payload ==
196
197
198 (((
199 LLDS12 will uplink payload via LoRaWAN with below payload format: 
200 )))
201
202 (((
203 Uplink payload includes in total 11 bytes.
204 )))
205
206 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
207 |=(% style="width: 62.5px;background-color:#4F81BD;color:white" %)(((
208 **Size(bytes)**
209 )))|=(% style="width: 62.5px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 62.5px;background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**1**
210 |(% style="width:62.5px" %)Value|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)(((
211 [[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]]
212 )))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
213 [[Interrupt flag>>||anchor="H2.3.5A0InterruptPin"]]
214 )))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|(((
215 [[Message Type>>||anchor="H2.3.7A0MessageType"]]
216 )))
217
218 [[image:1654833689380-972.png]]
219
220
221 === 2.3.1  Battery Info ===
222
223
224 Check the battery voltage for LLDS12.
225
226 Ex1: 0x0B45 = 2885mV
227
228 Ex2: 0x0B49 = 2889mV
229
230
231 === 2.3.2  DS18B20 Temperature sensor ===
232
233
234 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
236
237 **Example**:
238
239 If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
240
241 If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
242
243
244 === 2.3.3  Distance ===
245
246
247 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.
248
249
250 **Example**:
251
252 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.
253
254
255 === 2.3.4  Distance signal strength ===
256
257
258 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.
259
260
261 **Example**:
262
263 If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
264
265 Customers can judge whether they need to adjust the environment based on the signal strength.
266
267
268 === 2.3.5  Interrupt Pin ===
269
270
271 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.
272
273 Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
274
275 **Example:**
276
277 0x00: Normal uplink packet.
278
279 0x01: Interrupt Uplink Packet.
280
281
282 === 2.3.6  LiDAR temp ===
283
284
285 Characterize the internal temperature value of the sensor.
286
287 **Example: **
288 If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
289 If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
290
291
292 === 2.3.7  Message Type ===
293
294
295 (((
296 For a normal uplink payload, the message type is always 0x01.
297 )))
298
299 (((
300 Valid Message Type:
301 )))
302
303 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:499px" %)
304 |=(% 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**
305 |(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]]
306 |(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]]
307
308 === 2.3.8  Decode payload in The Things Network ===
309
310
311 While using TTN network, you can add the payload format to decode the payload.
312
313
314 [[image:1654592762713-715.png]]
315
316
317 (((
318 The payload decoder function for TTN is here:
319 )))
320
321 (((
322 LLDS12 TTN Payload Decoder:  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]
323 )))
324
325
326 == 2.4  Uplink Interval ==
327
328
329 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"]]
330
331
332 == 2.5  ​Show Data in DataCake IoT Server ==
333
334
335 (((
336 [[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:
337 )))
338
339 (((
340
341 )))
342
343 (((
344 (% style="color:blue" %)**Step 1**(%%)**: Be sure that your device is programmed and properly connected to the network at this time.**
345 )))
346
347 (((
348 (% 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:**
349 )))
350
351
352 [[image:1654592790040-760.png]]
353
354
355 [[image:1654592800389-571.png]]
356
357
358 (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
359
360 (% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
361
362 [[image:1654832691989-514.png]]
363
364
365 [[image:1654592833877-762.png]]
366
367
368 [[image:1654832740634-933.png]]
369
370
371
372 (((
373 (% style="color:blue" %)**Step 5**(%%)**: add payload decode**
374 )))
375
376 (((
377
378 )))
379
380 [[image:1654833065139-942.png]]
381
382
383
384 [[image:1654833092678-390.png]]
385
386
387
388 After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
389
390 [[image:1654833163048-332.png]]
391
392
393 == 2.6  Frequency Plans ==
394
395
396 (((
397 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.
398 )))
399
400
401 === 2.6.1  EU863-870 (EU868) ===
402
403
404 (((
405 (% style="color:blue" %)**Uplink:**
406 )))
407
408 (((
409 868.1 - SF7BW125 to SF12BW125
410 )))
411
412 (((
413 868.3 - SF7BW125 to SF12BW125 and SF7BW250
414 )))
415
416 (((
417 868.5 - SF7BW125 to SF12BW125
418 )))
419
420 (((
421 867.1 - SF7BW125 to SF12BW125
422 )))
423
424 (((
425 867.3 - SF7BW125 to SF12BW125
426 )))
427
428 (((
429 867.5 - SF7BW125 to SF12BW125
430 )))
431
432 (((
433 867.7 - SF7BW125 to SF12BW125
434 )))
435
436 (((
437 867.9 - SF7BW125 to SF12BW125
438 )))
439
440 (((
441 868.8 - FSK
442 )))
443
444 (((
445
446 )))
447
448 (((
449 (% style="color:blue" %)**Downlink:**
450 )))
451
452 (((
453 Uplink channels 1-9 (RX1)
454 )))
455
456 (((
457 869.525 - SF9BW125 (RX2 downlink only)
458 )))
459
460
461 === 2.6.2  US902-928(US915) ===
462
463
464 (((
465 Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
466 )))
467
468 (((
469 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.
470 )))
471
472 (((
473 After Join success, the end node will switch to the correct sub band by:
474 )))
475
476 * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
477 * 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)
478
479 === 2.6.3  CN470-510 (CN470) ===
480
481
482 (((
483 Used in China, Default use CHE=1
484 )))
485
486 (((
487 (% style="color:blue" %)**Uplink:**
488 )))
489
490 (((
491 486.3 - SF7BW125 to SF12BW125
492 )))
493
494 (((
495 486.5 - SF7BW125 to SF12BW125
496 )))
497
498 (((
499 486.7 - SF7BW125 to SF12BW125
500 )))
501
502 (((
503 486.9 - SF7BW125 to SF12BW125
504 )))
505
506 (((
507 487.1 - SF7BW125 to SF12BW125
508 )))
509
510 (((
511 487.3 - SF7BW125 to SF12BW125
512 )))
513
514 (((
515 487.5 - SF7BW125 to SF12BW125
516 )))
517
518 (((
519 487.7 - SF7BW125 to SF12BW125
520 )))
521
522 (((
523
524 )))
525
526 (((
527 (% style="color:blue" %)**Downlink:**
528 )))
529
530 (((
531 506.7 - SF7BW125 to SF12BW125
532 )))
533
534 (((
535 506.9 - SF7BW125 to SF12BW125
536 )))
537
538 (((
539 507.1 - SF7BW125 to SF12BW125
540 )))
541
542 (((
543 507.3 - SF7BW125 to SF12BW125
544 )))
545
546 (((
547 507.5 - SF7BW125 to SF12BW125
548 )))
549
550 (((
551 507.7 - SF7BW125 to SF12BW125
552 )))
553
554 (((
555 507.9 - SF7BW125 to SF12BW125
556 )))
557
558 (((
559 508.1 - SF7BW125 to SF12BW125
560 )))
561
562 (((
563 505.3 - SF12BW125 (RX2 downlink only)
564 )))
565
566
567 === 2.6.4  AU915-928(AU915) ===
568
569
570 (((
571 Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
572 )))
573
574 (((
575 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.
576 )))
577
578 (((
579
580 )))
581
582 (((
583 After Join success, the end node will switch to the correct sub band by:
584 )))
585
586 * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
587 * 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)
588
589 === 2.6.5  AS920-923 & AS923-925 (AS923) ===
590
591
592 (((
593 (% style="color:blue" %)**Default Uplink channel:**
594 )))
595
596 (((
597 923.2 - SF7BW125 to SF10BW125
598 )))
599
600 (((
601 923.4 - SF7BW125 to SF10BW125
602 )))
603
604 (((
605
606 )))
607
608 (((
609 (% style="color:blue" %)**Additional Uplink Channel**:
610 )))
611
612 (((
613 (OTAA mode, channel added by JoinAccept message)
614 )))
615
616 (((
617
618 )))
619
620 (((
621 (% style="color:blue" %)**AS920~~AS923 for Japan, Malaysia, Singapore**:
622 )))
623
624 (((
625 922.2 - SF7BW125 to SF10BW125
626 )))
627
628 (((
629 922.4 - SF7BW125 to SF10BW125
630 )))
631
632 (((
633 922.6 - SF7BW125 to SF10BW125
634 )))
635
636 (((
637 922.8 - SF7BW125 to SF10BW125
638 )))
639
640 (((
641 923.0 - SF7BW125 to SF10BW125
642 )))
643
644 (((
645 922.0 - SF7BW125 to SF10BW125
646 )))
647
648 (((
649
650 )))
651
652 (((
653 (% style="color:blue" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**:
654 )))
655
656 (((
657 923.6 - SF7BW125 to SF10BW125
658 )))
659
660 (((
661 923.8 - SF7BW125 to SF10BW125
662 )))
663
664 (((
665 924.0 - SF7BW125 to SF10BW125
666 )))
667
668 (((
669 924.2 - SF7BW125 to SF10BW125
670 )))
671
672 (((
673 924.4 - SF7BW125 to SF10BW125
674 )))
675
676 (((
677 924.6 - SF7BW125 to SF10BW125
678 )))
679
680 (((
681
682 )))
683
684 (((
685 (% style="color:blue" %)**Downlink:**
686 )))
687
688 (((
689 Uplink channels 1-8 (RX1)
690 )))
691
692 (((
693 923.2 - SF10BW125 (RX2)
694 )))
695
696
697 === 2.6.6  KR920-923 (KR920) ===
698
699
700 (((
701 (% style="color:blue" %)**Default channel:**
702 )))
703
704 (((
705 922.1 - SF7BW125 to SF12BW125
706 )))
707
708 (((
709 922.3 - SF7BW125 to SF12BW125
710 )))
711
712 (((
713 922.5 - SF7BW125 to SF12BW125
714 )))
715
716 (((
717
718 )))
719
720 (((
721 (% style="color:blue" %)**Uplink: (OTAA mode, channel added by JoinAccept message)**
722 )))
723
724 (((
725 922.1 - SF7BW125 to SF12BW125
726 )))
727
728 (((
729 922.3 - SF7BW125 to SF12BW125
730 )))
731
732 (((
733 922.5 - SF7BW125 to SF12BW125
734 )))
735
736 (((
737 922.7 - SF7BW125 to SF12BW125
738 )))
739
740 (((
741 922.9 - SF7BW125 to SF12BW125
742 )))
743
744 (((
745 923.1 - SF7BW125 to SF12BW125
746 )))
747
748 (((
749 923.3 - SF7BW125 to SF12BW125
750 )))
751
752 (((
753
754 )))
755
756 (((
757 (% style="color:blue" %)**Downlink:**
758 )))
759
760 (((
761 Uplink channels 1-7(RX1)
762 )))
763
764 (((
765 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
766 )))
767
768
769 === 2.6.7  IN865-867 (IN865) ===
770
771
772 (((
773 (% style="color:blue" %)**Uplink:**
774 )))
775
776 (((
777 865.0625 - SF7BW125 to SF12BW125
778 )))
779
780 (((
781 865.4025 - SF7BW125 to SF12BW125
782 )))
783
784 (((
785 865.9850 - SF7BW125 to SF12BW125
786 )))
787
788 (((
789
790 )))
791
792 (((
793 (% style="color:blue" %)**Downlink:**
794 )))
795
796 (((
797 Uplink channels 1-3 (RX1)
798 )))
799
800 (((
801 866.550 - SF10BW125 (RX2)
802 )))
803
804
805 == 2.7  LED Indicator ==
806
807
808 The LLDS12 has an internal LED which is to show the status of different state.
809
810 * The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
811 * Blink once when device transmit a packet.
812
813 == 2.8  ​Firmware Change Log ==
814
815
816 **Firmware download link:  **[[https:~~/~~/www.dropbox.com/sh/zjrobt4eb6tju89/AADPX7jC7mLN2dlvV-Miz3nFa?dl=0>>https://www.dropbox.com/sh/zjrobt4eb6tju89/AADPX7jC7mLN2dlvV-Miz3nFa?dl=0]]
817
818 **Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
819
820
821 = 3.  LiDAR ToF Measurement =
822
823 == 3.1 Principle of Distance Measurement ==
824
825
826 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.
827
828 [[image:1654831757579-263.png]]
829
830
831 == 3.2 Distance Measurement Characteristics ==
832
833
834 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:
835
836 [[image:1654831774373-275.png]]
837
838
839 (((
840 (% style="color:blue" %)**① **(%%)Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable.
841 )))
842
843 (((
844 (% style="color:blue" %)**② **(%%)Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m.
845 )))
846
847 (((
848 (% style="color:blue" %)**③ **(%%)Represents the operating range of The LiDAR probe detecting white target with 90% reflectivity, 0.1-12m.
849 )))
850
851
852 (((
853 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:
854 )))
855
856 [[image:1654831797521-720.png]]
857
858 (((
859 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.
860 )))
861
862 [[image:1654831810009-716.png]]
863
864 (((
865 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.
866 )))
867
868
869 == 3.3 Notice of usage: ==
870
871
872 Possible invalid /wrong reading for LiDAR ToF tech:
873
874 * Measure high reflectivity object such as: Mirror, Smooth ceramic tile, static milk surface, will have possible wrong readings.
875 * While there is transparent object such as glass, water drop between the measured object and the LiDAR sensor, the reading might be wrong.
876 * The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
877 * The sensor window is made by Acrylic. Don't touch it with alcohol material. This will destroy the sensor window.
878
879 == 3.4  Reflectivity of different objects: ==
880
881
882 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:379px" %)
883 |=(% 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
884 |(% style="width:53px" %)1|(% style="width:229px" %)Black foam rubber|(% style="width:93px" %)2.4%
885 |(% style="width:53px" %)2|(% style="width:229px" %)Black fabric|(% style="width:93px" %)3%
886 |(% style="width:53px" %)3|(% style="width:229px" %)Black rubber|(% style="width:93px" %)4%
887 |(% style="width:53px" %)4|(% style="width:229px" %)Coal (different types of coal)|(% style="width:93px" %)4~~8%
888 |(% style="width:53px" %)5|(% style="width:229px" %)Black car paint|(% style="width:93px" %)5%
889 |(% style="width:53px" %)6|(% style="width:229px" %)Black Jam|(% style="width:93px" %)10%
890 |(% style="width:53px" %)7|(% style="width:229px" %)Opaque black plastic|(% style="width:93px" %)14%
891 |(% style="width:53px" %)8|(% style="width:229px" %)Clean rough board|(% style="width:93px" %)20%
892 |(% style="width:53px" %)9|(% style="width:229px" %)Translucent plastic bottle|(% style="width:93px" %)62%
893 |(% style="width:53px" %)10|(% style="width:229px" %)Carton cardboard|(% style="width:93px" %)68%
894 |(% style="width:53px" %)11|(% style="width:229px" %)Clean pine|(% style="width:93px" %)70%
895 |(% style="width:53px" %)12|(% style="width:229px" %)Opaque white plastic|(% style="width:93px" %)87%
896 |(% style="width:53px" %)13|(% style="width:229px" %)White Jam|(% style="width:93px" %)90%
897 |(% style="width:53px" %)14|(% style="width:229px" %)Kodak Standard Whiteboard|(% style="width:93px" %)100%
898 |(% style="width:53px" %)15|(% style="width:229px" %)(((
899 Unpolished white metal surface
900 )))|(% style="width:93px" %)130%
901 |(% style="width:53px" %)16|(% style="width:229px" %)Glossy light metal surface|(% style="width:93px" %)150%
902 |(% style="width:53px" %)17|(% style="width:229px" %)stainless steel|(% style="width:93px" %)200%
903 |(% style="width:53px" %)18|(% style="width:229px" %)Reflector plate, reflective tape|(% style="width:93px" %)>300%
904
905 = 4.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
906
907
908 Use can configure LLDS12 via AT Command or LoRaWAN Downlink.
909
910 * (((
911 (((
912 AT Command Connection: See [[FAQ>>||anchor="H7.A0FAQ"]].
913 )))
914 )))
915 * (((
916 (((
917 LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
918 )))
919 )))
920
921 (((
922 (((
923
924 )))
925
926 (((
927 There are two kinds of commands to configure LLDS12, they are:
928 )))
929 )))
930
931 * (((
932 (((
933 (% style="color:#4f81bd" %)** General Commands**.
934 )))
935 )))
936
937 (((
938 (((
939 These commands are to configure:
940 )))
941 )))
942
943 * (((
944 (((
945 General system settings like: uplink interval.
946 )))
947 )))
948 * (((
949 (((
950 LoRaWAN protocol & radio related command.
951 )))
952 )))
953
954 (((
955 (((
956 They are same for all Dragino Device which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
957 )))
958 )))
959
960 (((
961 (((
962
963 )))
964 )))
965
966 * (((
967 (((
968 (% style="color:#4f81bd" %)** Commands special design for LLDS12**
969 )))
970 )))
971
972 (((
973 (((
974 These commands only valid for LLDS12, as below:
975 )))
976 )))
977
978
979 == 4.1  Set Transmit Interval Time ==
980
981
982 Feature: Change LoRaWAN End Node Transmit Interval.
983
984 (% style="color:#037691" %)**AT Command: AT+TDC**
985
986 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
987 |=(% style="width: 160px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 140px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 210px;background-color:#4F81BD;color:white" %)**Response**
988 |(% style="width:156px" %)AT+TDC=?|(% style="width:137px" %)Show current transmit Interval|(((
989 30000
990 OK
991 the interval is 30000ms = 30s
992 )))
993 |(% style="width:156px" %)AT+TDC=60000|(% style="width:137px" %)Set Transmit Interval|(((
994 OK
995 Set transmit interval to 60000ms = 60 seconds
996 )))
997
998 (((
999 (% style="color:#037691" %)**Downlink Command: 0x01**
1000 )))
1001
1002 (((
1003 Format: Command Code (0x01) followed by 3 bytes time value.
1004 )))
1005
1006 (((
1007 If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01.
1008 )))
1009
1010 * (((
1011 Example 1: Downlink Payload: 0100001E  ~/~/ Set Transmit Interval (TDC) = 30 seconds
1012 )))
1013 * (((
1014 Example 2: Downlink Payload: 0100003C  ~/~/ Set Transmit Interval (TDC) = 60 seconds
1015
1016
1017
1018 )))
1019
1020 == 4.2  Set Interrupt Mode ==
1021
1022
1023 Feature, Set Interrupt mode for GPIO_EXIT.
1024
1025 (% style="color:#037691" %)**AT Command: AT+INTMOD**
1026
1027 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1028 |=(% style="width: 154px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 196px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 160px;background-color:#4F81BD;color:white" %)**Response**
1029 |(% style="width:154px" %)AT+INTMOD=?|(% style="width:196px" %)Show current interrupt mode|(% style="width:157px" %)(((
1030 0
1031 OK
1032 the mode is 0 =No Interruption
1033 )))
1034 |(% style="width:154px" %)AT+INTMOD=2|(% style="width:196px" %)(((
1035 Set Transmit Interval
1036 0. (Disable Interrupt),
1037 ~1. (Trigger by rising and falling edge)
1038 2. (Trigger by falling edge)
1039 3. (Trigger by rising edge)
1040 )))|(% style="width:157px" %)OK
1041
1042 (((
1043 (% style="color:#037691" %)**Downlink Command: 0x06**
1044 )))
1045
1046 (((
1047 Format: Command Code (0x06) followed by 3 bytes.
1048 )))
1049
1050 (((
1051 This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
1052 )))
1053
1054 * (((
1055 Example 1: Downlink Payload: 06000000  ~/~/ Turn off interrupt mode
1056 )))
1057 * (((
1058 Example 2: Downlink Payload: 06000003  ~/~/ Set the interrupt mode to rising edge trigger
1059
1060
1061
1062 )))
1063
1064 == 4.3  Get Firmware Version Info ==
1065
1066
1067 Feature: use downlink to get firmware version.
1068
1069 (% style="color:#037691" %)**Downlink Command: 0x26**
1070
1071 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:492px" %)
1072 |(% style="background-color:#4f81bd; color:white; width:191px" %)**Downlink Control Type**|(% style="background-color:#4f81bd; color:white; width:57px" %)**FPort**|(% style="background-color:#4f81bd; color:white; width:91px" %)**Type Code**|(% style="background-color:#4f81bd; color:white; width:153px" %)**Downlink payload size(bytes)**
1073 |(% style="width:191px" %)Get Firmware Version Info|(% style="width:57px" %)Any|(% style="width:91px" %)26|(% style="width:151px" %)2
1074
1075 * Reply to the confirmation package: 26 01
1076 * Reply to non-confirmed packet: 26 00
1077
1078 Device will send an uplink after got this downlink command. With below payload:
1079
1080 Configures info payload:
1081
1082 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
1083 |=(% style="background-color:#4F81BD;color:white" %)(((
1084 **Size(bytes)**
1085 )))|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**5**|=(% style="background-color:#4F81BD;color:white" %)**1**
1086 |Value|Software Type|(((
1087 Frequency
1088 Band
1089 )))|Sub-band|(((
1090 Firmware
1091 Version
1092 )))|Sensor Type|Reserve|(((
1093 [[Message Type>>||anchor="H2.3.7A0MessageType"]]
1094 Always 0x02
1095 )))
1096
1097 (% style="color:#037691" %)**Software Type**(%%): Always 0x03 for LLDS12
1098
1099 (% style="color:#037691" %)**Frequency Band**:
1100
1101 *0x01: EU868
1102
1103 *0x02: US915
1104
1105 *0x03: IN865
1106
1107 *0x04: AU915
1108
1109 *0x05: KZ865
1110
1111 *0x06: RU864
1112
1113 *0x07: AS923
1114
1115 *0x08: AS923-1
1116
1117 *0x09: AS923-2
1118
1119 *0xa0: AS923-3
1120
1121
1122 (% style="color:#037691" %)**Sub-Band**(%%): value 0x00 ~~ 0x08
1123
1124 (% style="color:#037691" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version
1125
1126 (% style="color:#037691" %)**Sensor Type**:
1127
1128 0x01: LSE01
1129
1130 0x02: LDDS75
1131
1132 0x03: LDDS20
1133
1134 0x04: LLMS01
1135
1136 0x05: LSPH01
1137
1138 0x06: LSNPK01
1139
1140 0x07: LLDS12
1141
1142
1143 = 5. Battery & Power Consumption =
1144
1145
1146 LLDS12 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
1147
1148 [[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
1149
1150
1151 = 6.  Use AT Command =
1152
1153 == 6.1  Access AT Commands ==
1154
1155
1156 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.
1157
1158
1159 [[image:1654593668970-604.png]]
1160
1161
1162 **Connection:**
1163
1164 (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
1165
1166 (% style="background-color:yellow" %)** USB TTL TXD  <~-~-~-~-> UART_RXD**
1167
1168 (% style="background-color:yellow" %)** USB TTL RXD  <~-~-~-~-> UART_TXD**
1169
1170
1171 (((
1172 (((
1173 In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LLDS12.
1174 )))
1175
1176 (((
1177 LLDS12 will output system info once power on as below:
1178 )))
1179 )))
1180
1181
1182 [[image:1654593712276-618.png]]
1183
1184 Valid AT Command please check [[Configure Device>>||anchor="H4.A0ConfigureLLDS12viaATCommandorLoRaWANDownlink"]].
1185
1186
1187 = 7.  FAQ =
1188
1189 == 7.1  How to change the LoRa Frequency Bands/Region ==
1190
1191
1192 You can follow the instructions for [[how to upgrade image>>||anchor="H2.8A0200BFirmwareChangeLog"]].
1193 When downloading the images, choose the required image file for download. ​
1194
1195
1196 = 8.  Trouble Shooting =
1197
1198 == 8.1  AT Commands input doesn't work ==
1199
1200
1201 (((
1202 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.
1203 )))
1204
1205
1206 == 8.2  Significant error between the output distant value of LiDAR and actual distance ==
1207
1208
1209 (((
1210 (% 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.)
1211 )))
1212
1213 (((
1214 Troubleshooting: Please avoid use of this product under such circumstance in practice.
1215 )))
1216
1217 (((
1218
1219 )))
1220
1221 (((
1222 (% style="color:blue" %)**Cause ②**(%%)**: **The IR-pass filters are blocked.
1223 )))
1224
1225 (((
1226 Troubleshooting: please use dry dust-free cloth to gently remove the foreign matter.
1227 )))
1228
1229
1230 == 8.3 Possible reasons why the device is unresponsive： ==
1231
1232
1233 ​1. Check whether the battery voltage is lower than 2.8V
1234 2. Check whether the jumper of the device is correctly connected
1235
1236 [[image:image-20240330175858-1.png]]
1237 3. Check whether the switch here of the device is at the ISP（The switch can operate normally only when it is in RUN）
1238
1239 [[image:image-20240330175905-2.png]]
1240 ​
1241
1242 = 9.  Order Info =
1243
1244
1245 Part Number: (% style="color:blue" %)**LLDS12-XX**
1246
1247 (% style="color:blue" %)**XX**(%%): The default frequency band
1248
1249 * (% style="color:red" %)**AS923**(%%):  LoRaWAN AS923 band
1250 * (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
1251 * (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
1252 * (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
1253 * (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
1254 * (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
1255 * (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1256 * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1257
1258 = 10. ​ Packing Info =
1259
1260
1261 **Package Includes**:
1262
1263 * LLDS12 LoRaWAN LiDAR Distance Sensor x 1
1264
1265 **Dimension and weight**:
1266
1267 * Device Size: cm
1268 * Device Weight: g
1269 * Package Size / pcs : cm
1270 * Weight / pcs : g
1271
1272 = 11.  ​Support =
1273
1274
1275 * 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.
1276 * 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]].
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0