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

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0