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)
-
Attachments (0 modified, 4 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -3,7 +3,6 @@ 3 3 4 4 **Contents:** 5 5 6 -{{toc/}} 7 7 8 8 9 9 ... ... @@ -90,7 +90,6 @@ 90 90 * 8500mAh Battery for long term use 91 91 92 92 93 - 94 94 == 1.3 Specification == 95 95 96 96 === 1.3.1 Rated environmental conditions === ... ... @@ -97,8 +97,11 @@ 97 97 98 98 [[image:image-20220610154839-1.png]] 99 99 98 + 100 100 ((( 101 -**Remarks: (1) a. When the ambient temperature is 0-39 ℃, the maximum humidity is 90% (non-condensing); b. When the ambient temperature is 40-50 ℃, the highest humidity is the highest humidity in the natural world at the current temperature (no condensation)** 100 +**Remarks: (1) a. When the ambient temperature is 0-39 ℃, the maximum humidity is 90% (non-condensing); ** 101 + 102 +**~ b. When the ambient temperature is 40-50 ℃, the highest humidity is the highest humidity in the natural world at the current temperature (no condensation)** 102 102 ))) 103 103 104 104 ... ... @@ -135,7 +135,6 @@ 135 135 * Bottom water level monitoring 136 136 137 137 138 - 139 139 == 1.6 Pin mapping and power on == 140 140 141 141 ... ... @@ -143,16 +143,16 @@ 143 143 144 144 145 145 146 -= 2. Configure LDDS 75 to connect to LoRaWAN network =146 += 2. Configure LDDS45 to connect to LoRaWAN network = 147 147 148 148 == 2.1 How it works == 149 149 150 150 ((( 151 -The LDDS 75 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LDDS75. If there is coverage of the LoRaWAN network, it will automatically join the network via OTAA and start to send the sensor value151 +The LDDS45 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LDDS45. If there is coverage of the LoRaWAN network, it will automatically join the network via OTAA and start to send the sensor value 152 152 ))) 153 153 154 154 ((( 155 -In case you can't set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>||anchor="H3.A0ConfigureLDDS75viaATCommandorLoRaWANDownlink"]]to set the keys in the LDDS 75.155 +In case you can't set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>||anchor="H3.A0ConfigureLDDS75viaATCommandorLoRaWANDownlink"]]to set the keys in the LDDS45. 156 156 ))) 157 157 158 158 ... ... @@ -161,10 +161,15 @@ 161 161 162 162 ((( 163 163 Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LG308>>url:http://www.dragino.com/products/lora/item/140-lg308.html]] as a LoRaWAN gateway in this example. 164 + 165 + 164 164 ))) 165 165 168 +[[image:1654913911773-521.png]] 169 + 170 + 166 166 ((( 167 - [[image:1654848616367-242.png]]172 + 168 168 ))) 169 169 170 170 ((( ... ... @@ -172,11 +172,11 @@ 172 172 ))) 173 173 174 174 ((( 175 -(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LDDS 75.180 +(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LDDS45. 176 176 ))) 177 177 178 178 ((( 179 -Each LDDS 75 is shipped with a sticker with the default device keys, user can find this sticker in the box. it looks like below.184 +Each LDDS45 is shipped with a sticker with the default device keys, user can find this sticker in the box. it looks like below. 180 180 ))) 181 181 182 182 [[image:image-20220607170145-1.jpeg]] ... ... @@ -203,7 +203,10 @@ 203 203 204 204 [[image:image-20220610161353-7.png]] 205 205 211 +**Choose LDDS75 instead of LDDS45 is ok. They are of the same payload** 206 206 213 + 214 + 207 207 You can also choose to create the device manually. 208 208 209 209 [[image:image-20220610161538-8.png]] ... ... @@ -216,16 +216,16 @@ 216 216 217 217 218 218 219 -(% style="color:blue" %)**Step 2**(%%): Power on LDDS 75227 +(% style="color:blue" %)**Step 2**(%%): Power on LDDS45 220 220 221 221 222 222 Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position). 223 223 224 -[[image:image-2022061 0161724-10.png]]232 +[[image:image-20220611102908-2.png]] 225 225 226 226 227 227 ((( 228 -(% style="color:blue" %)**Step 3**(%%)**:** The LDDS 75 will auto join to the TTN network. After join success, it will start to upload messages to TTN and you can see the messages in the panel.236 +(% style="color:blue" %)**Step 3**(%%)**:** The LDDS45 will auto join to the TTN network. After join success, it will start to upload messages to TTN and you can see the messages in the panel. 229 229 ))) 230 230 231 231 [[image:1654849068701-275.png]] ... ... @@ -236,12 +236,9 @@ 236 236 237 237 ((( 238 238 ((( 239 -LDDS75 will uplink payload via LoRaWAN with below payload format: 240 -))) 247 +LDDS45 will uplink payload via LoRaWAN with below payload format: 241 241 242 -((( 243 -Uplink payload includes in total 4 bytes. 244 -Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance 249 +Uplink payload includes in total 8 bytes. 245 245 ))) 246 246 ))) 247 247 ... ... @@ -268,7 +268,7 @@ 268 268 === 2.3.1 Battery Info === 269 269 270 270 271 -Check the battery voltage for LDDS 75.276 +Check the battery voltage for LDDS45. 272 272 273 273 Ex1: 0x0B45 = 2885mV 274 274 ... ... @@ -279,22 +279,21 @@ 279 279 === 2.3.2 Distance === 280 280 281 281 ((( 282 -Get the distance. Flat object range 280mm -7500mm.287 +Get the distance. Flat object range 30mm - 4500mm. 283 283 ))) 284 284 285 285 ((( 286 -For example, if the data you get from the register is 0x0B 0x05, the distance between the sensor and the measured object is(% style="color:#4472c4" %)** 0B05(H) = 2821 (D) = 2821 mm.** 291 +For example, if the data you get from the register is __0x0B 0x05__, the distance between the sensor and the measured object is(% style="color:#4472c4" %)** 0B05(H) = 2821 (D) = 2821 mm.** 287 287 ))) 288 288 289 289 290 290 * If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor. 291 -* If the sensor value lower than 0x01 18(280mm), the sensor value will beinvalid. Since v1.1.4, all value lower than 280mm will be set to 0x0014(20mm) which means the value is invalid.296 +* If the sensor value lower than 0x001E (30mm), the sensor value will be 0x00. 292 292 293 293 294 - 295 295 === 2.3.3 Interrupt Pin === 296 296 297 -This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H 3.3A0SetInterruptMode"]] for the hardware and software set up.301 +This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H4.3A0SetInterruptMode"]] for the hardware and software set up. 298 298 299 299 **Example:** 300 300 ... ... @@ -314,10 +314,8 @@ 314 314 315 315 If payload is: FF3FH : (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. 316 316 317 -(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021. 318 318 319 319 320 - 321 321 === 2.3.5 Sensor Flag === 322 322 323 323 ((( ... ... @@ -868,7 +868,6 @@ 868 868 * Blink once when device transmit a packet. 869 869 870 870 871 - 872 872 == 2.8 Firmware Change Log == 873 873 874 874 ... ... @@ -1086,7 +1086,6 @@ 1086 1086 * Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger 1087 1087 1088 1088 1089 - 1090 1090 = 4. FAQ = 1091 1091 1092 1092 == 4.1 What is the frequency plan for LDDS75? == ... ... @@ -1147,7 +1147,6 @@ 1147 1147 * (% style="color:red" %)**8 **(%%)**:** 8500mAh battery 1148 1148 1149 1149 1150 - 1151 1151 = 7. Packing Info = 1152 1152 1153 1153 ... ... @@ -1163,7 +1163,6 @@ 1163 1163 * Weight / pcs : g 1164 1164 1165 1165 1166 - 1167 1167 = 8. Support = 1168 1168 1169 1169 * 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.
- 1654913911773-521.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +84.0 KB - Content
- 1654914413351-871.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +492.6 KB - Content
- image-20220611102837-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +233.7 KB - Content
- image-20220611102908-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +341.6 KB - Content