<
From version < 101.2 >
edited by Xiaoling
on 2022/06/10 11:38
To version < 99.1 >
edited by Xiaoling
on 2022/06/10 11:30
>
Change comment: Uploaded new attachment "1654831810009-716.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -485,14 +485,14 @@
485 485  * Reply to the confirmation package: 14 01
486 486  * Reply to non-confirmed packet: 14 00
487 487  
488 -== 2. Frequency Plans ==
488 +== 2.8 Frequency Plans ==
489 489  
490 490  (((
491 -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.
491 +The LSPH01 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.
492 492  )))
493 493  
494 494  
495 -=== 2.6.1  EU863-870 (EU868) ===
495 +=== 2.8.1 EU863-870 (EU868) ===
496 496  
497 497  (((
498 498  (% style="color:blue" %)**Uplink:**
... ... @@ -552,7 +552,7 @@
552 552  
553 553  
554 554  
555 -=== 2.6.2  US902-928(US915) ===
555 +=== 2.8.2 US902-928(US915) ===
556 556  
557 557  (((
558 558  Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
... ... @@ -569,10 +569,8 @@
569 569  * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
570 570  * 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)
571 571  
572 +=== 2.8.3 CN470-510 (CN470) ===
572 572  
573 -
574 -=== 2.6.3 CN470-510 (CN470) ===
575 -
576 576  (((
577 577  Used in China, Default use CHE=1
578 578  )))
... ... @@ -659,9 +659,8 @@
659 659  
660 660  
661 661  
660 +=== 2.8.4 AU915-928(AU915) ===
662 662  
663 -=== 2.6.4 AU915-928(AU915) ===
664 -
665 665  (((
666 666  Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
667 667  )))
... ... @@ -681,9 +681,8 @@
681 681  * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
682 682  * 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)
683 683  
681 +=== 2.8.5 AS920-923 & AS923-925 (AS923) ===
684 684  
685 -=== 2.6.5 AS920-923 & AS923-925 (AS923) ===
686 -
687 687  (((
688 688  (% style="color:blue" %)**Default Uplink channel:**
689 689  )))
... ... @@ -790,9 +790,8 @@
790 790  
791 791  
792 792  
789 +=== 2.8.6 KR920-923 (KR920) ===
793 793  
794 -=== 2.6.6 KR920-923 (KR920) ===
795 -
796 796  (((
797 797  (% style="color:blue" %)**Default channel:**
798 798  )))
... ... @@ -863,9 +863,8 @@
863 863  
864 864  
865 865  
861 +=== 2.8.7 IN865-867 (IN865) ===
866 866  
867 -=== 2.6.7 IN865-867 (IN865) ===
868 -
869 869  (((
870 870  (% style="color:blue" %)**Uplink:**
871 871  )))
... ... @@ -900,27 +900,24 @@
900 900  
901 901  
902 902  
897 +== 2.9 LED Indicator ==
903 903  
904 -== 2.7  LED Indicator ==
899 +The LSPH01 has an internal LED which is to show the status of different state.
905 905  
906 -The LLDS12 has an internal LED which is to show the status of different state.
907 -
908 908  * The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
909 909  * Blink once when device transmit a packet.
910 910  
904 +== 2.10 ​Firmware Change Log ==
911 911  
912 912  
907 +**Firmware download link:**
913 913  
914 -== 2.8  ​Firmware Change Log ==
909 +[[http:~~/~~/www.dragino.com/downloads/index.pHp?dir=LoRa_End_Node/LSPH01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/]]
915 915  
916 916  
917 -**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/]]
918 -
919 -
920 920  **Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>path:/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/]]
921 921  
922 922  
923 -
924 924  = 3.  LiDAR ToF Measurement =
925 925  
926 926  == 3.1 Principle of Distance Measurement ==
... ... @@ -927,7 +927,7 @@
927 927  
928 928  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.
929 929  
930 -[[image:1654831757579-263.png]]
921 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]
931 931  
932 932  
933 933  
... ... @@ -935,7 +935,7 @@
935 935  
936 936  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:
937 937  
938 -[[image:1654831774373-275.png]]
929 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.png]]
939 939  
940 940  
941 941  ①Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable.
... ... @@ -948,12 +948,12 @@
948 948  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:
949 949  
950 950  
951 -[[image:1654831797521-720.png]]
942 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image003.png]]
952 952  
953 953  
954 954  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.
955 955  
956 -[[image:1654831810009-716.png]]
947 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.png]]
957 957  
958 958  
959 959  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.
... ... @@ -969,6 +969,8 @@
969 969  * The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
970 970  * The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window.
971 971  
963 +
964 +
972 972  = 4.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
973 973  
974 974  (((
... ... @@ -1083,6 +1083,8 @@
1083 1083  Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
1084 1084  )))
1085 1085  
1079 +
1080 +
1086 1086  == 4.3  Get Firmware Version Info ==
1087 1087  
1088 1088  Feature: use downlink to get firmware version.
... ... @@ -1094,6 +1094,7 @@
1094 1094  * Reply to the confirmation package: 26 01
1095 1095  * Reply to non-confirmed packet: 26 00
1096 1096  
1092 +
1097 1097  Device will send an uplink after got this downlink command. With below payload:
1098 1098  
1099 1099  Configures info payload:
... ... @@ -1346,6 +1346,7 @@
1346 1346  * (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1347 1347  * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1348 1348  
1345 +
1349 1349  = 10. ​ Packing Info =
1350 1350  
1351 1351  
... ... @@ -1360,6 +1360,7 @@
1360 1360  * Package Size / pcs : cm
1361 1361  * Weight / pcs : g
1362 1362  
1360 +
1363 1363  = 11.  ​Support =
1364 1364  
1365 1365  * 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.
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0