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 === ... ... @@ -135,8 +135,6 @@ 135 135 136 136 137 137 138 - 139 - 140 140 == 1.6 Pin mapping and power on == 141 141 142 142 ... ... @@ -291,6 +291,9 @@ 291 291 * If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor. 292 292 * 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. 293 293 289 + 290 + 291 + 294 294 === 2.3.3 Interrupt Pin === 295 295 296 296 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. ... ... @@ -319,13 +319,9 @@ 319 319 320 320 === 2.3.5 Sensor Flag === 321 321 322 -((( 323 323 0x01: Detect Ultrasonic Sensor 324 -))) 325 325 326 -((( 327 327 0x00: No Ultrasonic Sensor 328 -))) 329 329 330 330 331 331 ... ... @@ -338,9 +338,7 @@ 338 338 339 339 The payload decoder function for TTN V3 is here: 340 340 341 -((( 342 342 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/]] 343 -))) 344 344 345 345 346 346 ... ... @@ -869,17 +869,10 @@ 869 869 == 2.8 Firmware Change Log == 870 870 871 871 872 -((( 873 873 **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/]] 874 -))) 875 875 876 -((( 877 - 878 -))) 879 879 880 -((( 881 881 **Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]] 882 -))) 883 883 884 884 885 885 ... ... @@ -1023,9 +1023,7 @@ 1023 1023 [[image:image-20220610172924-5.png]] 1024 1024 1025 1025 1026 -((( 1027 1027 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: 1028 -))) 1029 1029 1030 1030 1031 1031 [[image:image-20220610172924-6.png||height="601" width="860"]] ... ... @@ -1049,9 +1049,7 @@ 1049 1049 ((( 1050 1050 Format: Command Code (0x01) followed by 3 bytes time value. 1051 1051 1052 -((( 1053 1053 If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01. 1054 -))) 1055 1055 1056 1056 * Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds 1057 1057 * Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds ... ... @@ -1074,14 +1074,11 @@ 1074 1074 1075 1075 Format: Command Code (0x06) followed by 3 bytes. 1076 1076 1077 -((( 1078 1078 This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06. 1079 -))) 1080 1080 1081 1081 * Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode 1082 1082 * Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger 1083 1083 1084 - 1085 1085 = 4. FAQ = 1086 1086 1087 1087 == 4.1 What is the frequency plan for LDDS75? == ... ... @@ -1141,7 +1141,6 @@ 1141 1141 * (% style="color:red" %)**4 **(%%)**: **4000mAh battery 1142 1142 * (% style="color:red" %)**8 **(%%)**:** 8500mAh battery 1143 1143 1144 - 1145 1145 = 7. Packing Info = 1146 1146 1147 1147 ... ... @@ -1156,7 +1156,6 @@ 1156 1156 * Package Size / pcs : cm 1157 1157 * Weight / pcs : g 1158 1158 1159 - 1160 1160 = 8. Support = 1161 1161 1162 1162 * 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.