Last modified by Mengting Qiu on 2024/03/07 08:41
<
From version < 137.1 >
edited by Xiaoling
on 2022/06/10 16:51
To version < 147.2 >
edited by Xiaoling
on 2022/06/10 17:34
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -57,6 +57,7 @@
57 57  * IP66 Waterproof Enclosure
58 58  * 4000mAh or 8500mAh Battery for long term use
59 59  
60 +
60 60  == 1.3  Specification ==
61 61  
62 62  === 1.3.1  Rated environmental conditions ===
... ... @@ -71,15 +71,20 @@
71 71  
72 72  === 1.3.2  Effective measurement range Reference beam pattern ===
73 73  
74 -**(1) The tested object is a white cylindrical tube made of PVC, with a height of 100cm and a diameter of 7.5cm.**[[image:image-20220610155021-2.png||height="440" width="1189"]]
75 +**(1) The tested object is a white cylindrical tube made of PVC, with a height of 100cm and a diameter of 7.5cm.**
75 75  
76 76  
77 77  
78 -**(2)** The object to be tested is a "corrugated cardboard box" perpendicular to the central axis of 0 °, and the length * width is 60cm * 50cm.[[image:image-20220610155021-3.png||height="437" width="1192"]]
79 +[[image:1654852253176-749.png]]
79 79  
80 -(% style="display:none" %) (%%)
81 81  
82 +**(2)** **The object to be tested is a "corrugated cardboard box" perpendicular to the central axis of 0 °, and the length * width is 60cm * 50cm.**
82 82  
84 +
85 +[[image:1654852175653-550.png]](% style="display:none" %) ** **
86 +
87 +
88 +
83 83  == 1.5 ​ Applications ==
84 84  
85 85  * Horizontal distance measurement
... ... @@ -92,6 +92,7 @@
92 92  * Sewer
93 93  * Bottom water level monitoring
94 94  
101 +
95 95  == 1.6  Pin mapping and power on ==
96 96  
97 97  
... ... @@ -98,6 +98,7 @@
98 98  [[image:1654847583902-256.png]]
99 99  
100 100  
108 +
101 101  = 2.  Configure LDDS75 to connect to LoRaWAN network =
102 102  
103 103  == 2.1  How it works ==
... ... @@ -111,6 +111,7 @@
111 111  )))
112 112  
113 113  
122 +
114 114  == 2.2  ​Quick guide to connect to LoRaWAN server (OTAA) ==
115 115  
116 116  (((
... ... @@ -231,7 +231,6 @@
231 231  * If the sensor value lower than 0x0118 (280mm), the sensor value will be invalid. Since v1.1.4, all value lower than 280mm will be set to 0x0014(20mm) which means the value is invalid.
232 232  
233 233  
234 -
235 235  === 2.3.3  Interrupt Pin ===
236 236  
237 237  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.
... ... @@ -243,6 +243,7 @@
243 243  0x01: Interrupt Uplink Packet.
244 244  
245 245  
254 +
246 246  === 2.3.4  DS18B20 Temperature sensor ===
247 247  
248 248  This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
... ... @@ -280,7 +280,7 @@
280 280  
281 281  == 2.4  Uplink Interval ==
282 282  
283 -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"]]
292 +The LDDS75 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"]]
284 284  
285 285  
286 286  
... ... @@ -311,47 +311,25 @@
311 311  
312 312  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
313 313  
314 -(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
323 +(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
315 315  
316 -[[image:1654832691989-514.png]]
325 +[[image:1654851029373-510.png]]
317 317  
318 318  
319 -[[image:1654592833877-762.png]]
328 +After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
320 320  
330 +[[image:image-20220610165129-11.png||height="595" width="1088"]]
321 321  
322 -[[image:1654832740634-933.png]]
323 323  
324 324  
325 -
326 -(((
327 -(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
328 -)))
329 -
330 -(((
331 -
332 -)))
333 -
334 -[[image:1654833065139-942.png]]
335 -
336 -
337 -
338 -[[image:1654833092678-390.png]]
339 -
340 -
341 -
342 -After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
343 -
344 -[[image:1654833163048-332.png]]
345 -
346 -
347 -
348 348  == 2.6  Frequency Plans ==
349 349  
350 350  (((
351 -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.
337 +The LDDS75 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.
352 352  )))
353 353  
354 354  
341 +
355 355  === 2.6.1  EU863-870 (EU868) ===
356 356  
357 357  (((
... ... @@ -415,20 +415,51 @@
415 415  === 2.6.2  US902-928(US915) ===
416 416  
417 417  (((
418 -Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
419 -)))
405 +Used in USA, Canada and South America. Default use CHE=2
420 420  
421 -(((
422 -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.
423 -)))
407 +(% style="color:blue" %)**Uplink:**
424 424  
425 -(((
426 -After Join success, the end node will switch to the correct sub band by:
427 -)))
409 +903.9 - SF7BW125 to SF10BW125
428 428  
429 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
430 -* 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)
411 +904.1 - SF7BW125 to SF10BW125
431 431  
413 +904.3 - SF7BW125 to SF10BW125
414 +
415 +904.5 - SF7BW125 to SF10BW125
416 +
417 +904.7 - SF7BW125 to SF10BW125
418 +
419 +904.9 - SF7BW125 to SF10BW125
420 +
421 +905.1 - SF7BW125 to SF10BW125
422 +
423 +905.3 - SF7BW125 to SF10BW125
424 +
425 +
426 +(% style="color:blue" %)**Downlink:**
427 +
428 +923.3 - SF7BW500 to SF12BW500
429 +
430 +923.9 - SF7BW500 to SF12BW500
431 +
432 +924.5 - SF7BW500 to SF12BW500
433 +
434 +925.1 - SF7BW500 to SF12BW500
435 +
436 +925.7 - SF7BW500 to SF12BW500
437 +
438 +926.3 - SF7BW500 to SF12BW500
439 +
440 +926.9 - SF7BW500 to SF12BW500
441 +
442 +927.5 - SF7BW500 to SF12BW500
443 +
444 +923.3 - SF12BW500(RX2 downlink only)
445 +
446 +
447 +
448 +)))
449 +
432 432  === 2.6.3  CN470-510 (CN470) ===
433 433  
434 434  (((
... ... @@ -517,28 +517,54 @@
517 517  
518 518  
519 519  
520 -
521 521  === 2.6.4  AU915-928(AU915) ===
522 522  
523 523  (((
524 -Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
525 -)))
541 +Default use CHE=2
526 526  
527 -(((
528 -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.
529 -)))
543 +(% style="color:blue" %)**Uplink:**
530 530  
531 -(((
532 -
533 -)))
545 +916.8 - SF7BW125 to SF12BW125
534 534  
535 -(((
536 -After Join success, the end node will switch to the correct sub band by:
537 -)))
547 +917.0 - SF7BW125 to SF12BW125
538 538  
539 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
540 -* 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)
549 +917.2 - SF7BW125 to SF12BW125
541 541  
551 +917.4 - SF7BW125 to SF12BW125
552 +
553 +917.6 - SF7BW125 to SF12BW125
554 +
555 +917.8 - SF7BW125 to SF12BW125
556 +
557 +918.0 - SF7BW125 to SF12BW125
558 +
559 +918.2 - SF7BW125 to SF12BW125
560 +
561 +
562 +(% style="color:blue" %)**Downlink:**
563 +
564 +923.3 - SF7BW500 to SF12BW500
565 +
566 +923.9 - SF7BW500 to SF12BW500
567 +
568 +924.5 - SF7BW500 to SF12BW500
569 +
570 +925.1 - SF7BW500 to SF12BW500
571 +
572 +925.7 - SF7BW500 to SF12BW500
573 +
574 +926.3 - SF7BW500 to SF12BW500
575 +
576 +926.9 - SF7BW500 to SF12BW500
577 +
578 +927.5 - SF7BW500 to SF12BW500
579 +
580 +923.3 - SF12BW500(RX2 downlink only)
581 +
582 +
583 +
584 +)))
585 +
542 542  === 2.6.5  AS920-923 & AS923-925 (AS923) ===
543 543  
544 544  (((
... ... @@ -647,7 +647,6 @@
647 647  
648 648  
649 649  
650 -
651 651  === 2.6.6  KR920-923 (KR920) ===
652 652  
653 653  (((
... ... @@ -720,7 +720,6 @@
720 720  
721 721  
722 722  
723 -
724 724  === 2.6.7  IN865-867 (IN865) ===
725 725  
726 726  (((
... ... @@ -757,18 +757,21 @@
757 757  
758 758  
759 759  
760 -
761 761  == 2.7  LED Indicator ==
762 762  
763 -The LLDS12 has an internal LED which is to show the status of different state.
804 +The LDDS75 has an internal LED which is to show the status of different state.
764 764  
765 -* The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
806 +
807 +* Blink once when device power on.
808 +* The device detects the sensor and flashes 5 times.
809 +* Solid ON for 5 seconds once device successful Join the network.
766 766  * Blink once when device transmit a packet.
767 767  
812 +
768 768  == 2.8  ​Firmware Change Log ==
769 769  
770 770  
771 -**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/]]
816 +**Firmware download link: **[[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/]]
772 772  
773 773  
774 774  **Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
... ... @@ -775,71 +775,58 @@
775 775  
776 776  
777 777  
778 -= 3.  LiDAR ToF Measurement =
823 +== 2.9  Mechanical ==
779 779  
780 -== 3.1 Principle of Distance Measurement ==
781 781  
782 -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.
826 +[[image:image-20220610172003-1.png]]
783 783  
784 -[[image:1654831757579-263.png]]
828 +[[image:image-20220610172003-2.png]]
785 785  
786 786  
831 +== 2.10  Battery Analysis ==
787 787  
788 -== 3.2 Distance Measurement Characteristics ==
833 +=== 2.10.1  Battery Type ===
789 789  
790 -With optimization of light path and algorithm, The LiDAR probe has minimized influence from external environment on distance measurement performance. Despite that, the range of distance measurement may still be affected by the environment illumination intensity and the reflectivity of detection object. As shown in below:
835 +The LDDS75 battery is a combination of a 4000mAh or 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
791 791  
792 -[[image:1654831774373-275.png]]
793 793  
838 +The battery related documents as below:
794 794  
795 -(((
796 -(% style="color:blue" %)**① **(%%)Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable.
840 +* (((
841 +[[ Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
797 797  )))
798 -
799 -(((
800 -(% style="color:blue" %)**② **(%%)Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m.
843 +* (((
844 +[[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
801 801  )))
802 -
803 -(((
804 -(% style="color:blue" %)**③ **(%%)Represents the operating range of The LiDAR probe detecting white target with 90% reflectivity, 0.1-12m.
846 +* (((
847 +[[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]]
805 805  )))
806 806  
850 + [[image:image-20220610172400-3.png]]
807 807  
808 -(((
809 -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:
810 -)))
811 811  
812 812  
813 -[[image:1654831797521-720.png]]
854 +=== 2.10.2  Replace the battery ===
814 814  
856 +(((
857 +You can change the battery in the LDDS75.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.
858 +)))
815 815  
816 816  (((
817 -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.
861 +
818 818  )))
819 819  
820 -[[image:1654831810009-716.png]]
821 -
822 -
823 823  (((
824 -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.
865 +The default battery pack of LDDS75 includes a ER18505 plus super capacitor. If user can’t find this pack locally, they can find ER18505 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)
825 825  )))
826 826  
827 827  
828 828  
829 -== 3.3 Notice of usage: ==
870 += 3.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
830 830  
831 -Possible invalid /wrong reading for LiDAR ToF tech:
832 -
833 -* Measure high reflectivity object such as: Mirror, Smooth ceramic tile, static milk surface, will have possible wrong readings.
834 -* While there is transparent object such as glass, water drop between the measured object and the LiDAR sensor, the reading might wrong.
835 -* The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
836 -* The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window.
837 -
838 -= 4.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
839 -
840 840  (((
841 841  (((
842 -Use can configure LLDS12 via AT Command or LoRaWAN Downlink.
874 +Use can configure LDDS75 via AT Command or LoRaWAN Downlink.
843 843  )))
844 844  )))
845 845  
... ... @@ -860,7 +860,7 @@
860 860  )))
861 861  
862 862  (((
863 -There are two kinds of commands to configure LLDS12, they are:
895 +There are two kinds of commands to configure LDDS75, they are:
864 864  )))
865 865  )))
866 866  
... ... @@ -901,55 +901,49 @@
901 901  
902 902  * (((
903 903  (((
904 -(% style="color:#4f81bd" %)** Commands special design for LLDS12**
936 +(% style="color:#4f81bd" %)** Commands special design for LDDS75**
905 905  )))
906 906  )))
907 907  
908 908  (((
909 909  (((
910 -These commands only valid for LLDS12, as below:
942 +These commands only valid for LDDS75, as below:
911 911  )))
912 912  )))
913 913  
914 914  
915 915  
916 -== 4.1  Set Transmit Interval Time ==
948 +== 3.1  Access AT Commands ==
917 917  
918 -Feature: Change LoRaWAN End Node Transmit Interval.
950 +LDDS75 supports AT Command set in the stock firmware. You can use a USB to TTL adapter to connect to LDDS75 for using AT command, as below.
919 919  
920 -(% style="color:#037691" %)**AT Command: AT+TDC**
952 +[[image:image-20220610172924-4.png||height="483" width="988"]]
921 921  
922 -[[image:image-20220607171554-8.png]]
923 923  
955 +Or if you have below board, use below connection:
924 924  
925 -(((
926 -(% style="color:#037691" %)**Downlink Command: 0x01**
927 -)))
928 928  
929 -(((
930 -Format: Command Code (0x01) followed by 3 bytes time value.
931 -)))
958 +[[image:image-20220610172924-5.png]]
932 932  
933 -(((
934 -If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
935 -)))
936 936  
937 -* (((
938 -Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
939 -)))
940 -* (((
941 -Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
942 -)))
961 +In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LDDS75. LDDS75 will output system info once power on as below:
943 943  
944 -== 4.2  Set Interrupt Mode ==
945 945  
946 -Feature, Set Interrupt mode for GPIO_EXIT.
964 + [[image:image-20220610172924-6.png||height="601" width="860"]]
947 947  
948 -(% style="color:#037691" %)**AT Command: AT+INTMOD**
949 949  
950 -[[image:image-20220610105806-2.png]]
951 951  
968 +== 3.2  Set Transmit Interval Time ==
952 952  
970 +Feature: Change LoRaWAN End Node Transmit Interval.
971 +
972 +(% style="color:#037691" %)**AT Command: AT+TDC**
973 +
974 +[[image:image-20220610173409-7.png]]
975 +
976 +
977 +
978 +
953 953  (((
954 954  (% style="color:#037691" %)**Downlink Command: 0x06**
955 955  )))
... ... @@ -969,7 +969,7 @@
969 969  Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
970 970  )))
971 971  
972 -== 4.3  Get Firmware Version Info ==
998 +== 3.3  Get Firmware Version Info ==
973 973  
974 974  Feature: use downlink to get firmware version.
975 975  
1654852175653-550.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +106.2 KB
Content
1654852253176-749.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +106.6 KB
Content
image-20220610172003-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +5.9 KB
Content
image-20220610172003-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +18.6 KB
Content
image-20220610172400-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +370.3 KB
Content
image-20220610172924-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +1.5 MB
Content
image-20220610172924-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +901.4 KB
Content
image-20220610172924-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +68.6 KB
Content
image-20220610173409-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +11.8 KB
Content

Applications

Navigation

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