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