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℃
...	...	@@ -834,37 +834,25 @@
834	834	[[image:1654831774373-275.png]]
835	835
836	836
837		-(((
838		-(% style="color:blue" %)**① **(%%)Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable.
839		-)))
	834	+**(% style="color:blue" %)① **(%%)Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable.
840	840
841		-(((
842		-(% style="color:blue" %)**② **(%%)Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m.
843		-)))
	836	+**(% style="color:blue" %)② **(%%)Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m.
844	844
845		-(((
846		-(% style="color:blue" %)**③ **(%%)Represents the operating range of The LiDAR probe detecting white target with 90% reflectivity, 0.1-12m.
847		-)))
	838	+**(% style="color:blue" %)③ **(%%)Represents the operating range of The LiDAR probe detecting white target with 90% reflectivity, 0.1-12m.
848	848
849	849
850		-(((
851	851	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:
852		-)))
853	853
854	854
855	855	[[image:1654831797521-720.png]]
856	856
857	857
858		-(((
859	859	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.
860		-)))
861	861
862	862	[[image:1654831810009-716.png]]
863	863
864	864
865		-(((
866	866	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.
867		-)))
868	868
869	869
870	870
...	...	@@ -877,81 +877,58 @@
877	877	* The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
878	878	* The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window.
879	879
	865	+
	866	+
	867	+
880	880	= 4.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
881	881
882	882	(((
883		-(((
884	884	Use can configure LLDS12 via AT Command or LoRaWAN Downlink.
885	885	)))
886		-)))
887	887
888	888	* (((
889		-(((
890	890	AT Command Connection: See [[FAQ>>||anchor="H7.A0FAQ"]].
891	891	)))
892		-)))
893	893	* (((
894		-(((
895	895	LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
896	896	)))
897		-)))
898	898
899	899	(((
900		-(((
901	901
902		-)))
903	903
904		-(((
905	905	There are two kinds of commands to configure LLDS12, they are:
906	906	)))
907		-)))
908	908
909	909	* (((
910		-(((
911	911	(% style="color:#4f81bd" %)** General Commands**.
912	912	)))
913		-)))
914	914
915	915	(((
916		-(((
917	917	These commands are to configure:
918	918	)))
919		-)))
920	920
921	921	* (((
922		-(((
923	923	General system settings like: uplink interval.
924	924	)))
925		-)))
926	926	* (((
927		-(((
928	928	LoRaWAN protocol & radio related command.
929	929	)))
930		-)))
931	931
932	932	(((
933		-(((
934	934	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]]
935	935	)))
936		-)))
937	937
938	938	(((
939		-(((
940	940
941	941	)))
942		-)))
943	943
944	944	* (((
945		-(((
946	946	(% style="color:#4f81bd" %)** Commands special design for LLDS12**
947	947	)))
948		-)))
949	949
950	950	(((
951		-(((
952	952	These commands only valid for LLDS12, as below:
953	953	)))
954		-)))
955	955
956	956
957	957
...	...	@@ -964,6 +964,7 @@
964	964	[[image:image-20220607171554-8.png]]
965	965
966	966
	929	+
967	967	(((
968	968	(% style="color:#037691" %)**Downlink Command: 0x01**
969	969	)))
...	...	@@ -986,7 +986,6 @@
986	986
987	987	)))
988	988
989		-
990	990	== 4.2  Set Interrupt Mode ==
991	991
992	992	Feature, Set Interrupt mode for GPIO_EXIT.
...	...	@@ -1212,14 +1212,10 @@
1212	1212
1213	1213
1214	1214	(((
1215		-(((
1216	1216	In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LLDS12.
1217		-)))
1218	1218
1219		-(((
1220	1220	LLDS12 will output system info once power on as below:
1221	1221	)))
1222		-)))
1223	1223
1224	1224
1225	1225	[[image:1654593712276-618.png]]
...	...	@@ -1240,9 +1240,7 @@
1240	1240	== 8.1  AT Commands input doesn’t work ==
1241	1241
1242	1242
1243		-(((
1244	1244	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.
1245		-)))
1246	1246
1247	1247
1248	1248	== 8.2  Significant error between the output distant value of LiDAR and actual distance ==
...	...	@@ -1287,6 +1287,7 @@
1287	1287	* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1288	1288	* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1289	1289
	1246	+
1290	1290	= 10. ​ Packing Info =
1291	1291
1292	1292
...	...	@@ -1301,6 +1301,7 @@
1301	1301	* Package Size / pcs : cm
1302	1302	* Weight / pcs : g
1303	1303
	1261	+
1304	1304	= 11.  ​Support =
1305	1305
1306	1306	* 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.