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.
...	...	@@ -481,8 +481,6 @@
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	483
484		-
485		-
486	486	=== 2.6.3  CN470-510 (CN470) ===
487	487
488	488	(((
...	...	@@ -594,8 +594,6 @@
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	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		-)))
	836	+①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		-)))
	838	+②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		-)))
	840	+③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,81 +895,56 @@
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
	867	+
898	898	= 4.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
899	899
900	900	(((
901		-(((
902	902	Use can configure LLDS12 via AT Command or LoRaWAN Downlink.
903	903	)))
904		-)))
905	905
906	906	* (((
907		-(((
908	908	AT Command Connection: See [[FAQ>>||anchor="H7.A0FAQ"]].
909	909	)))
910		-)))
911	911	* (((
912		-(((
913	913	LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
914	914	)))
915		-)))
916	916
917	917	(((
918		-(((
919	919
920		-)))
921	921
922		-(((
923	923	There are two kinds of commands to configure LLDS12, they are:
924	924	)))
925		-)))
926	926
927	927	* (((
928		-(((
929	929	(% style="color:#4f81bd" %)** General Commands**.
930	930	)))
931		-)))
932	932
933	933	(((
934		-(((
935	935	These commands are to configure:
936	936	)))
937		-)))
938	938
939	939	* (((
940		-(((
941	941	General system settings like: uplink interval.
942	942	)))
943		-)))
944	944	* (((
945		-(((
946	946	LoRaWAN protocol & radio related command.
947	947	)))
948		-)))
949	949
950	950	(((
951		-(((
952	952	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]]
953	953	)))
954		-)))
955	955
956	956	(((
957		-(((
958	958
959	959	)))
960		-)))
961	961
962	962	* (((
963		-(((
964	964	(% style="color:#4f81bd" %)** Commands special design for LLDS12**
965	965	)))
966		-)))
967	967
968	968	(((
969		-(((
970	970	These commands only valid for LLDS12, as below:
971	971	)))
972		-)))
973	973
974	974
975	975
...	...	@@ -982,6 +982,7 @@
982	982	[[image:image-20220607171554-8.png]]
983	983
984	984
	929	+
985	985	(((
986	986	(% style="color:#037691" %)**Downlink Command: 0x01**
987	987	)))
...	...	@@ -1004,7 +1004,6 @@
1004	1004
1005	1005	)))
1006	1006
1007		-
1008	1008	== 4.2  Set Interrupt Mode ==
1009	1009
1010	1010	Feature, Set Interrupt mode for GPIO_EXIT.
...	...	@@ -1034,6 +1034,7 @@
1034	1034	)))
1035	1035
1036	1036
	981	+
1037	1037	== 4.3  Get Firmware Version Info ==
1038	1038
1039	1039	Feature: use downlink to get firmware version.
...	...	@@ -1230,14 +1230,10 @@
1230	1230
1231	1231
1232	1232	(((
1233		-(((
1234	1234	In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LLDS12.
1235		-)))
1236	1236
1237		-(((
1238	1238	LLDS12 will output system info once power on as below:
1239	1239	)))
1240		-)))
1241	1241
1242	1242
1243	1243	[[image:1654593712276-618.png]]
...	...	@@ -1258,9 +1258,7 @@
1258	1258	== 8.1  AT Commands input doesn’t work ==
1259	1259
1260	1260
1261		-(((
1262	1262	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.
1263		-)))
1264	1264
1265	1265
1266	1266	== 8.2  Significant error between the output distant value of LiDAR and actual distance ==