Changes for page LDDS45 - LoRaWAN Distance Detection Sensor User Manual
Last modified by Mengting Qiu on 2025/02/26 15:04
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -63,9 +63,6 @@ 63 63 * Downlink to change configure 64 64 * 8500mAh Battery for long term use 65 65 66 - 67 - 68 - 69 69 == 1.3 Probe Specification == 70 70 71 71 * Storage temperature :-20℃~~75℃ ... ... @@ -81,9 +81,6 @@ 81 81 * Material of enclosure - ABS+PC 82 82 * Wire length - 25cm 83 83 84 - 85 - 86 - 87 87 == 1.4 Probe Dimension == 88 88 89 89 ... ... @@ -100,9 +100,6 @@ 100 100 * Automatic control 101 101 * Sewer 102 102 103 - 104 - 105 - 106 106 == 1.6 Pin mapping and power on == 107 107 108 108 ... ... @@ -309,9 +309,6 @@ 309 309 |(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]] 310 310 |(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]] 311 311 312 - 313 - 314 - 315 315 === 2.3.8 Decode payload in The Things Network === 316 316 317 317 While using TTN network, you can add the payload format to decode the payload. ... ... @@ -480,9 +480,6 @@ 480 480 * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 481 481 * 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) 482 482 483 - 484 - 485 - 486 486 === 2.6.3 CN470-510 (CN470) === 487 487 488 488 ((( ... ... @@ -593,9 +593,6 @@ 593 593 * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 594 594 * 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) 595 595 596 - 597 - 598 - 599 599 === 2.6.5 AS920-923 & AS923-925 (AS923) === 600 600 601 601 ((( ... ... @@ -822,9 +822,6 @@ 822 822 * The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected. 823 823 * Blink once when device transmit a packet. 824 824 825 - 826 - 827 - 828 828 == 2.8 Firmware Change Log == 829 829 830 830 ... ... @@ -852,37 +852,25 @@ 852 852 [[image:1654831774373-275.png]] 853 853 854 854 855 -((( 856 -(% style="color:blue" %)**① **(%%)Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable. 857 -))) 834 +**(% style="color:blue" %)① **(%%)Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable. 858 858 859 -((( 860 -(% style="color:blue" %)**② **(%%)Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m. 861 -))) 836 +**(% style="color:blue" %)② **(%%)Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m. 862 862 863 -((( 864 -(% style="color:blue" %)**③ **(%%)Represents the operating range of The LiDAR probe detecting white target with 90% reflectivity, 0.1-12m. 865 -))) 838 +**(% style="color:blue" %)③ **(%%)Represents the operating range of The LiDAR probe detecting white target with 90% reflectivity, 0.1-12m. 866 866 867 867 868 -((( 869 869 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: 870 -))) 871 871 872 872 873 873 [[image:1654831797521-720.png]] 874 874 875 875 876 -((( 877 877 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. 878 -))) 879 879 880 880 [[image:1654831810009-716.png]] 881 881 882 882 883 -((( 884 884 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. 885 -))) 886 886 887 887 888 888 ... ... @@ -895,84 +895,55 @@ 895 895 * The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe. 896 896 * The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window. 897 897 898 - 899 - 900 - 901 901 = 4. Configure LLDS12 via AT Command or LoRaWAN Downlink = 902 902 903 903 ((( 904 -((( 905 905 Use can configure LLDS12 via AT Command or LoRaWAN Downlink. 906 906 ))) 907 -))) 908 908 909 909 * ((( 910 -((( 911 911 AT Command Connection: See [[FAQ>>||anchor="H7.A0FAQ"]]. 912 912 ))) 913 -))) 914 914 * ((( 915 -((( 916 916 LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] 917 917 ))) 918 -))) 919 919 920 920 ((( 921 -((( 922 922 923 -))) 924 924 925 -((( 926 926 There are two kinds of commands to configure LLDS12, they are: 927 927 ))) 928 -))) 929 929 930 930 * ((( 931 -((( 932 932 (% style="color:#4f81bd" %)** General Commands**. 933 933 ))) 934 -))) 935 935 936 936 ((( 937 -((( 938 938 These commands are to configure: 939 939 ))) 940 -))) 941 941 942 942 * ((( 943 -((( 944 944 General system settings like: uplink interval. 945 945 ))) 946 -))) 947 947 * ((( 948 -((( 949 949 LoRaWAN protocol & radio related command. 950 950 ))) 951 -))) 952 952 953 953 ((( 954 -((( 955 955 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]] 956 956 ))) 957 -))) 958 958 959 959 ((( 960 -((( 961 961 962 962 ))) 963 -))) 964 964 965 965 * ((( 966 -((( 967 967 (% style="color:#4f81bd" %)** Commands special design for LLDS12** 968 968 ))) 969 -))) 970 970 971 971 ((( 972 -((( 973 973 These commands only valid for LLDS12, as below: 974 974 ))) 975 -))) 976 976 977 977 978 978 ... ... @@ -985,6 +985,7 @@ 985 985 [[image:image-20220607171554-8.png]] 986 986 987 987 926 + 988 988 ((( 989 989 (% style="color:#037691" %)**Downlink Command: 0x01** 990 990 ))) ... ... @@ -1007,9 +1007,6 @@ 1007 1007 1008 1008 ))) 1009 1009 1010 - 1011 - 1012 - 1013 1013 == 4.2 Set Interrupt Mode == 1014 1014 1015 1015 Feature, Set Interrupt mode for GPIO_EXIT. ... ... @@ -1235,14 +1235,10 @@ 1235 1235 1236 1236 1237 1237 ((( 1238 -((( 1239 1239 In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LLDS12. 1240 -))) 1241 1241 1242 -((( 1243 1243 LLDS12 will output system info once power on as below: 1244 1244 ))) 1245 -))) 1246 1246 1247 1247 1248 1248 [[image:1654593712276-618.png]] ... ... @@ -1263,9 +1263,7 @@ 1263 1263 == 8.1 AT Commands input doesn’t work == 1264 1264 1265 1265 1266 -((( 1267 1267 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. 1268 -))) 1269 1269 1270 1270 1271 1271 == 8.2 Significant error between the output distant value of LiDAR and actual distance == ... ... @@ -1310,6 +1310,7 @@ 1310 1310 * (% style="color:red" %)**IN865**(%%): LoRaWAN IN865 band 1311 1311 * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band 1312 1312 1243 + 1313 1313 = 10. Packing Info = 1314 1314 1315 1315 ... ... @@ -1324,6 +1324,7 @@ 1324 1324 * Package Size / pcs : cm 1325 1325 * Weight / pcs : g 1326 1326 1258 + 1327 1327 = 11. Support = 1328 1328 1329 1329 * 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.