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