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
-
... ... @@ -87,9 +87,6 @@ 87 87 * 4000mAh or 8500mAh Battery for long term use 88 88 89 89 90 - 91 - 92 - 93 93 == 1.3 Specification == 94 94 95 95 === 1.3.1 Rated environmental conditions === ... ... @@ -133,6 +133,8 @@ 133 133 * Sewer 134 134 * Bottom water level monitoring 135 135 133 + 134 + 136 136 == 1.6 Pin mapping and power on == 137 137 138 138 ... ... @@ -287,6 +287,9 @@ 287 287 * If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor. 288 288 * 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. 289 289 289 + 290 + 291 + 290 290 === 2.3.3 Interrupt Pin === 291 291 292 292 This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H3.3A0SetInterruptMode"]] for the hardware and software set up. ... ... @@ -315,13 +315,9 @@ 315 315 316 316 === 2.3.5 Sensor Flag === 317 317 318 -((( 319 319 0x01: Detect Ultrasonic Sensor 320 -))) 321 321 322 -((( 323 323 0x00: No Ultrasonic Sensor 324 -))) 325 325 326 326 327 327 ... ... @@ -334,9 +334,7 @@ 334 334 335 335 The payload decoder function for TTN V3 is here: 336 336 337 -((( 338 338 LDDS75 TTN V3 Payload Decoder: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LDDS75/Payload_Decoder/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Payload_Decoder/]] 339 -))) 340 340 341 341 342 342 ... ... @@ -865,17 +865,10 @@ 865 865 == 2.8 Firmware Change Log == 866 866 867 867 868 -((( 869 869 **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/]] 870 -))) 871 871 872 -((( 873 - 874 -))) 875 875 876 -((( 877 877 **Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]] 878 -))) 879 879 880 880 881 881 ... ... @@ -1019,9 +1019,7 @@ 1019 1019 [[image:image-20220610172924-5.png]] 1020 1020 1021 1021 1022 -((( 1023 1023 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: 1024 -))) 1025 1025 1026 1026 1027 1027 [[image:image-20220610172924-6.png||height="601" width="860"]] ... ... @@ -1045,9 +1045,7 @@ 1045 1045 ((( 1046 1046 Format: Command Code (0x01) followed by 3 bytes time value. 1047 1047 1048 -((( 1049 1049 If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01. 1050 -))) 1051 1051 1052 1052 * Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds 1053 1053 * Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds ... ... @@ -1070,14 +1070,11 @@ 1070 1070 1071 1071 Format: Command Code (0x06) followed by 3 bytes. 1072 1072 1073 -((( 1074 1074 This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06. 1075 -))) 1076 1076 1077 1077 * Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode 1078 1078 * Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger 1079 1079 1080 - 1081 1081 = 4. FAQ = 1082 1082 1083 1083 == 4.1 What is the frequency plan for LDDS75? == ... ... @@ -1137,7 +1137,6 @@ 1137 1137 * (% style="color:red" %)**4 **(%%)**: **4000mAh battery 1138 1138 * (% style="color:red" %)**8 **(%%)**:** 8500mAh battery 1139 1139 1140 - 1141 1141 = 7. Packing Info = 1142 1142 1143 1143 ... ... @@ -1152,7 +1152,6 @@ 1152 1152 * Package Size / pcs : cm 1153 1153 * Weight / pcs : g 1154 1154 1155 - 1156 1156 = 8. Support = 1157 1157 1158 1158 * 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.