Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 7 added, 0 removed)
  • image-20220610172003-1.png
  • image-20220610172003-2.png
  • image-20220610172400-3.png
  • image-20220610172924-4.png
  • image-20220610172924-5.png
  • image-20220610172924-6.png
  • image-20220610173409-7.png

Details

Page properties

Content

...	...	@@ -58,7 +58,6 @@
58	58	* 4000mAh or 8500mAh Battery for long term use
59	59
60	60
61		-
62	62	== 1.3  Specification ==
63	63
64	64	=== 1.3.1  Rated environmental conditions ===
...	...	@@ -100,7 +100,6 @@
100	100	* Bottom water level monitoring
101	101
102	102
103		-
104	104	== 1.6  Pin mapping and power on ==
105	105
106	106
...	...	@@ -242,7 +242,6 @@
242	242	* 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.
243	243
244	244
245		-
246	246	=== 2.3.3  Interrupt Pin ===
247	247
248	248	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.
...	...	@@ -694,7 +694,6 @@
694	694
695	695
696	696
697		-
698	698	=== 2.6.6  KR920-923 (KR920) ===
699	699
700	700	(((
...	...	@@ -767,7 +767,6 @@
767	767
768	768
769	769
770		-
771	771	=== 2.6.7  IN865-867 (IN865) ===
772	772
773	773	(((
...	...	@@ -804,18 +804,21 @@
804	804
805	805
806	806
807		-
808	808	== 2.7  LED Indicator ==
809	809
810		-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.
811	811
812		-* 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.
813	813	* Blink once when device transmit a packet.
814	814
	812	+
815	815	== 2.8  ​Firmware Change Log ==
816	816
817	817
818		-**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/]]
819	819
820	820
821	821	**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
...	...	@@ -822,71 +822,58 @@
822	822
823	823
824	824
825		-= 3.  LiDAR ToF Measurement =
	823	+== 2.9  Mechanical ==
826	826
827		-== 3.1 Principle of Distance Measurement ==
828	828
829		-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]]
830	830
831		-[[image:1654831757579-263.png]]
	828	+[[image:image-20220610172003-2.png]]
832	832
833	833
	831	+== 2.10  Battery Analysis ==
834	834
835		-== 3.2 Distance Measurement Characteristics ==
	833	+=== 2.10.1  Battery Type ===
836	836
837		-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.
838	838
839		-[[image:1654831774373-275.png]]
840	840
	838	+The battery related documents as below:
841	841
842		-(((
843		-(% 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]],
844	844	)))
845		-
846		-(((
847		-(% 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]],
848	848	)))
849		-
850		-(((
851		-(% 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]]
852	852	)))
853	853
	850	+ [[image:image-20220610172400-3.png]]
854	854
855		-(((
856		-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:
857		-)))
858	858
859	859
860		-[[image:1654831797521-720.png]]
	854	+=== 2.10.2  Replace the battery ===
861	861
	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	+)))
862	862
863	863	(((
864		-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	+
865	865	)))
866	866
867		-[[image:1654831810009-716.png]]
868		-
869		-
870	870	(((
871		-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)
872	872	)))
873	873
874	874
875	875
876		-== 3.3 Notice of usage: ==
	870	+= 3.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
877	877
878		-Possible invalid /wrong reading for LiDAR ToF tech:
879		-
880		-* Measure high reflectivity object such as: Mirror, Smooth ceramic tile, static milk surface, will have possible wrong readings.
881		-* While there is transparent object such as glass, water drop between the measured object and the LiDAR sensor, the reading might wrong.
882		-* The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
883		-* The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window.
884		-
885		-= 4.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
886		-
887	887	(((
888	888	(((
889		-Use can configure LLDS12 via AT Command or LoRaWAN Downlink.
	874	+Use can configure LDDS75 via AT Command or LoRaWAN Downlink.
890	890	)))
891	891	)))
892	892
...	...	@@ -907,7 +907,7 @@
907	907	)))
908	908
909	909	(((
910		-There are two kinds of commands to configure LLDS12, they are:
	895	+There are two kinds of commands to configure LDDS75, they are:
911	911	)))
912	912	)))
913	913
...	...	@@ -948,156 +948,88 @@
948	948
949	949	* (((
950	950	(((
951		-(% style="color:#4f81bd" %)** Commands special design for LLDS12**
	936	+(% style="color:#4f81bd" %)** Commands special design for LDDS75**
952	952	)))
953	953	)))
954	954
955	955	(((
956	956	(((
957		-These commands only valid for LLDS12, as below:
	942	+These commands only valid for LDDS75, as below:
958	958	)))
959	959	)))
960	960
961	961
962	962
963		-== 4.1  Set Transmit Interval Time ==
	948	+== 3.1  Access AT Commands ==
964	964
965		-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.
966	966
967		-(% style="color:#037691" %)**AT Command: AT+TDC**
	952	+[[image:image-20220610172924-4.png||height="483" width="988"]]
968	968
969		-[[image:image-20220607171554-8.png]]
970	970
	955	+Or if you have below board, use below connection:
971	971
972		-(((
973		-(% style="color:#037691" %)**Downlink Command: 0x01**
974		-)))
975	975
976		-(((
977		-Format: Command Code (0x01) followed by 3 bytes time value.
978		-)))
	958	+[[image:image-20220610172924-5.png]]
979	979
980		-(((
981		-If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
982		-)))
983	983
984		-* (((
985		-Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
986		-)))
987		-* (((
988		-Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
989		-)))
	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:
990	990
991		-== 4.2  Set Interrupt Mode ==
992	992
993		-Feature, Set Interrupt mode for GPIO_EXIT.
	964	+ [[image:image-20220610172924-6.png||height="601" width="860"]]
994	994
995		-(% style="color:#037691" %)**AT Command: AT+INTMOD**
996	996
997		-[[image:image-20220610105806-2.png]]
998	998
	968	+== 3.2  Set Transmit Interval Time ==
999	999
1000		-(((
1001		-(% style="color:#037691" %)**Downlink Command: 0x06**
1002		-)))
	970	+Feature: Change LoRaWAN End Node Transmit Interval.
1003	1003
1004		-(((
1005		-Format: Command Code (0x06) followed by 3 bytes.
1006		-)))
	972	+(% style="color:#037691" %)**AT Command: AT+TDC**
1007	1007
1008		-(((
1009		-This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
1010		-)))
	974	+[[image:image-20220610173409-7.png]]
1011	1011
1012		-* (((
1013		-Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
1014		-)))
1015		-* (((
1016		-Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
1017		-)))
1018	1018
1019		-== 4.3  Get Firmware Version Info ==
1020	1020
1021		-Feature: use downlink to get firmware version.
1022	1022
1023		-(% style="color:#037691" %)**Downlink Command: 0x26**
	979	+(((
	980	+(% style="color:#037691" %)**Downlink Command: 0x01**
	981	+)))
1024	1024
1025		-[[image:image-20220607171917-10.png]]
	983	+(((
	984	+(((
	985	+Format: Command Code (0x01) followed by 3 bytes time value.
1026	1026
1027		-* Reply to the confirmation package: 26 01
1028		-* Reply to non-confirmed packet: 26 00
	987	+If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
1029	1029
1030		-Device will send an uplink after got this downlink command. With below payload:
	989	+* Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
	990	+* Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
	991	+)))
1031	1031
1032		-Configures info payload:
1033	1033
1034		-(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
1035		-|=(((
1036		-**Size(bytes)**
1037		-)))|=**1**|=**1**|=**1**|=**1**|=**1**|=**5**|=**1**
1038		-|**Value**|Software Type|(((
1039		-Frequency
1040		-
1041		-Band
1042		-)))|Sub-band|(((
1043		-Firmware
1044		-
1045		-Version
1046		-)))|Sensor Type|Reserve|(((
1047		-[[Message Type>>||anchor="H2.3.7A0MessageType"]]
1048		-Always 0x02
	994	+
1049	1049	)))
1050	1050
1051		-**Software Type**: Always 0x03 for LLDS12
	997	+== 3.3  Set Interrupt Mode ==
1052	1052
	999	+Feature, Set Interrupt mode for GPIO_EXIT.
1053	1053
1054		-**Frequency Band**:
1055	1055
1056		-*0x01: EU868
	1002	+(% style="color:#037691" %)**Downlink Command: AT+INTMOD**
1057	1057
1058		-*0x02: US915
	1004	+[[image:image-20220610105907-1.png]]
1059	1059
1060		-*0x03: IN865
1061	1061
1062		-*0x04: AU915
	1007	+**Downlink Command: 0x06**
1063	1063
1064		-*0x05: KZ865
	1009	+Format: Command Code (0x06) followed by 3 bytes.
1065	1065
1066		-*0x06: RU864
	1011	+This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
1067	1067
1068		-*0x07: AS923
	1013	+* Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
	1014	+* Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
1069	1069
1070		-*0x08: AS923-1
1071	1071
1072		-*0x09: AS923-2
1073	1073
1074		-*0xa0: AS923-3
1075		-
1076		-
1077		-**Sub-Band**: value 0x00 ~~ 0x08
1078		-
1079		-
1080		-**Firmware Version**: 0x0100, Means: v1.0.0 version
1081		-
1082		-
1083		-**Sensor Type**:
1084		-
1085		-0x01: LSE01
1086		-
1087		-0x02: LDDS75
1088		-
1089		-0x03: LDDS20
1090		-
1091		-0x04: LLMS01
1092		-
1093		-0x05: LSPH01
1094		-
1095		-0x06: LSNPK01
1096		-
1097		-0x07: LLDS12
1098		-
1099		-
1100		-
1101	1101	= 5.  Battery & How to replace =
1102	1102
1103	1103	== 5.1  Battery Type ==

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