Changes for page LMDS200 -- LoRaWAN Microwave Radar Distance Sensor User Manual
Last modified by Mengting Qiu on 2024/03/07 08:41
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 6 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -57,6 +57,8 @@ 57 57 * IP66 Waterproof Enclosure 58 58 * 4000mAh or 8500mAh Battery for long term use 59 59 60 + 61 + 60 60 == 1.3 Specification == 61 61 62 62 === 1.3.1 Rated environmental conditions === ... ... @@ -71,15 +71,20 @@ 71 71 72 72 === 1.3.2 Effective measurement range Reference beam pattern === 73 73 74 -**(1) The tested object is a white cylindrical tube made of PVC, with a height of 100cm and a diameter of 7.5cm.** [[image:image-20220610155021-2.png||height="440" width="1189"]]76 +**(1) The tested object is a white cylindrical tube made of PVC, with a height of 100cm and a diameter of 7.5cm.** 75 75 76 76 77 77 78 - **(2)** The object to be tested is a "corrugated cardboard box" perpendicular to the central axis of 0 °, and the length * width is 60cm * 50cm.[[image:image-20220610155021-3.png||height="437" width="1192"]]80 +[[image:1654852253176-749.png]] 79 79 80 -(% style="display:none" %) (%%) 81 81 83 +**(2)** **The object to be tested is a "corrugated cardboard box" perpendicular to the central axis of 0 °, and the length * width is 60cm * 50cm.** 82 82 85 + 86 +[[image:1654852175653-550.png]](% style="display:none" %) ** ** 87 + 88 + 89 + 83 83 == 1.5 Applications == 84 84 85 85 * Horizontal distance measurement ... ... @@ -93,6 +93,7 @@ 93 93 * Bottom water level monitoring 94 94 95 95 103 + 96 96 == 1.6 Pin mapping and power on == 97 97 98 98 ... ... @@ -99,6 +99,7 @@ 99 99 [[image:1654847583902-256.png]] 100 100 101 101 110 + 102 102 = 2. Configure LDDS75 to connect to LoRaWAN network = 103 103 104 104 == 2.1 How it works == ... ... @@ -112,6 +112,7 @@ 112 112 ))) 113 113 114 114 124 + 115 115 == 2.2 Quick guide to connect to LoRaWAN server (OTAA) == 116 116 117 117 ((( ... ... @@ -184,11 +184,10 @@ 184 184 == 2.3 Uplink Payload == 185 185 186 186 ((( 187 -LLDS12 will uplink payload via LoRaWAN with below payload format: 188 -))) 197 +LDDS75 will uplink payload via LoRaWAN with below payload format: 189 189 190 - (((191 - Uplink payload includesintotal11bytes.199 +Uplink payload includes in total 4 bytes. 200 +Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance 192 192 ))) 193 193 194 194 ((( ... ... @@ -198,23 +198,23 @@ 198 198 (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %) 199 199 |=(% style="width: 62.5px;" %)((( 200 200 **Size (bytes)** 201 -)))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1** 202 -|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)((( 203 -[[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]] 204 -)))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|((( 205 -[[Interrupt flag>>||anchor="H2.3.5A0InterruptPin"]] 206 -)))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|((( 207 -[[Message Type>>||anchor="H2.3.7A0MessageType"]] 208 -))) 210 +)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1** 211 +|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|((( 212 +[[Distance>>||anchor="H2.3.3A0Distance"]] 209 209 210 -[[image:1654833689380-972.png]] 214 +(unit: mm) 215 +)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.4A0Distancesignalstrength"]]|((( 216 +[[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]] 217 +)))|[[Sensor Flag>>path:#Sensor_Flag]] 211 211 219 +[[image:1654850511545-399.png]] 212 212 213 213 222 + 214 214 === 2.3.1 Battery Info === 215 215 216 216 217 -Check the battery voltage for L LDS12.226 +Check the battery voltage for LDDS75. 218 218 219 219 Ex1: 0x0B45 = 2885mV 220 220 ... ... @@ -222,49 +222,22 @@ 222 222 223 223 224 224 225 -=== 2.3.2 D S18B20 Temperaturesensor===234 +=== 2.3.2 Distance === 226 226 227 - Thisisoptional, usercanconnectexternalDS18B20sensor to the +3.3v, 1-wireand GND pin . and this field will report temperature.236 +Get the distance. Flat object range 280mm - 7500mm. 228 228 238 +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.** 229 229 230 -**Example**: 231 231 232 -If payload is: 0105H: (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree 241 +* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor. 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. 233 233 234 -If payload is: FF3FH : (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. 235 235 236 236 246 +=== 2.3.3 Interrupt Pin === 237 237 238 -=== 2.3.3 Distance === 239 - 240 -Represents the distance value of the measurement output, the default unit is cm, and the value range parsed as a decimal number is 0-1200. In actual use, when the signal strength value Strength. 241 - 242 - 243 -**Example**: 244 - 245 -If the data you get from the register is 0x0B 0xEA, the distance between the sensor and the measured object is 0BEA(H) = 3050 (D)/10 = 305cm. 246 - 247 - 248 - 249 -=== 2.3.4 Distance signal strength === 250 - 251 -Refers to the signal strength, the default output value will be between 0-65535. When the distance measurement gear is fixed, the farther the distance measurement is, the lower the signal strength; the lower the target reflectivity, the lower the signal strength. When Strength is greater than 100 and not equal to 65535, the measured value of Dist is considered credible. 252 - 253 - 254 -**Example**: 255 - 256 -If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible. 257 - 258 -Customers can judge whether they need to adjust the environment based on the signal strength. 259 - 260 - 261 - 262 -=== 2.3.5 Interrupt Pin === 263 - 264 264 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. 265 265 266 -Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]]. 267 - 268 268 **Example:** 269 269 270 270 0x00: Normal uplink packet. ... ... @@ -273,52 +273,44 @@ 273 273 274 274 275 275 276 -=== 2.3. 6LiDARtemp ===258 +=== 2.3.4 DS18B20 Temperature sensor === 277 277 278 - Characterizetheinternaltemperature valueofthesensor.260 +This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature. 279 279 280 -**Example: ** 281 -If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃. 282 -If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃. 262 +**Example**: 283 283 264 +If payload is: 0105H: (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree 284 284 266 +If payload is: FF3FH : (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. 285 285 286 -= ==2.3.7MessageType===268 +(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021. 287 287 288 -((( 289 -For a normal uplink payload, the message type is always 0x01. 290 -))) 291 291 292 -((( 293 -Valid Message Type: 294 -))) 295 295 272 +=== 2.3.5 Sensor Flag === 296 296 297 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %) 298 -|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload** 299 -|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]] 300 -|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]] 274 +0x01: Detect Ultrasonic Sensor 301 301 302 - ===2.3.8 Decodepayload inTheThingsNetwork ===276 +0x00: No Ultrasonic Sensor 303 303 278 + 279 +=== 280 +(% style="color:inherit; font-family:inherit" %)2.3.6 Decode payload in The Things Network(%%) === 281 + 304 304 While using TTN network, you can add the payload format to decode the payload. 305 305 306 306 307 -[[image:16545 92762713-715.png]]285 +[[image:1654850829385-439.png]] 308 308 309 -((( 310 -The payload decoder function for TTN is here: 311 -))) 287 +The payload decoder function for TTN V3 is here: 312 312 313 -((( 314 -LLDS12 TTN Payload Decoder: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LLDS12/Decoder/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LLDS12/Decoder/]] 315 -))) 289 +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/]] 316 316 317 317 318 318 319 319 == 2.4 Uplink Interval == 320 320 321 -The L LDS12by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[Change Uplink Interval>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H4.1ChangeUplinkInterval"]]295 +The LDDS75 by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[Change Uplink Interval>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H4.1ChangeUplinkInterval"]] 322 322 323 323 324 324 ... ... @@ -349,47 +349,25 @@ 349 349 350 350 (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.** 351 351 352 -(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12product.**326 +(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.** 353 353 354 -[[image:16548 32691989-514.png]]328 +[[image:1654851029373-510.png]] 355 355 356 356 357 - [[image:1654592833877-762.png]]331 +After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake. 358 358 333 +[[image:image-20220610165129-11.png||height="595" width="1088"]] 359 359 360 -[[image:1654832740634-933.png]] 361 361 362 362 363 - 364 -((( 365 -(% style="color:blue" %)**Step 5**(%%)**: add payload decode** 366 -))) 367 - 368 -((( 369 - 370 -))) 371 - 372 -[[image:1654833065139-942.png]] 373 - 374 - 375 - 376 -[[image:1654833092678-390.png]] 377 - 378 - 379 - 380 -After added, the sensor data arrive TTN, it will also arrive and show in Datacake. 381 - 382 -[[image:1654833163048-332.png]] 383 - 384 - 385 - 386 386 == 2.6 Frequency Plans == 387 387 388 388 ((( 389 -The L LDS12uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets.340 +The LDDS75 uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets. 390 390 ))) 391 391 392 392 344 + 393 393 === 2.6.1 EU863-870 (EU868) === 394 394 395 395 ((( ... ... @@ -453,20 +453,51 @@ 453 453 === 2.6.2 US902-928(US915) === 454 454 455 455 ((( 456 -Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document. 457 -))) 408 +Used in USA, Canada and South America. Default use CHE=2 458 458 459 -((( 460 -To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join. 461 -))) 410 +(% style="color:blue" %)**Uplink:** 462 462 463 -((( 464 -After Join success, the end node will switch to the correct sub band by: 465 -))) 412 +903.9 - SF7BW125 to SF10BW125 466 466 467 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 468 -* 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) 414 +904.1 - SF7BW125 to SF10BW125 469 469 416 +904.3 - SF7BW125 to SF10BW125 417 + 418 +904.5 - SF7BW125 to SF10BW125 419 + 420 +904.7 - SF7BW125 to SF10BW125 421 + 422 +904.9 - SF7BW125 to SF10BW125 423 + 424 +905.1 - SF7BW125 to SF10BW125 425 + 426 +905.3 - SF7BW125 to SF10BW125 427 + 428 + 429 +(% style="color:blue" %)**Downlink:** 430 + 431 +923.3 - SF7BW500 to SF12BW500 432 + 433 +923.9 - SF7BW500 to SF12BW500 434 + 435 +924.5 - SF7BW500 to SF12BW500 436 + 437 +925.1 - SF7BW500 to SF12BW500 438 + 439 +925.7 - SF7BW500 to SF12BW500 440 + 441 +926.3 - SF7BW500 to SF12BW500 442 + 443 +926.9 - SF7BW500 to SF12BW500 444 + 445 +927.5 - SF7BW500 to SF12BW500 446 + 447 +923.3 - SF12BW500(RX2 downlink only) 448 + 449 + 450 + 451 +))) 452 + 470 470 === 2.6.3 CN470-510 (CN470) === 471 471 472 472 ((( ... ... @@ -559,24 +559,51 @@ 559 559 === 2.6.4 AU915-928(AU915) === 560 560 561 561 ((( 562 -Frequency band as per definition in LoRaWAN 1.0.3 Regional document. 563 -))) 545 +Default use CHE=2 564 564 565 -((( 566 -To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join. 567 -))) 547 +(% style="color:blue" %)**Uplink:** 568 568 569 -((( 570 - 571 -))) 549 +916.8 - SF7BW125 to SF12BW125 572 572 573 -((( 574 -After Join success, the end node will switch to the correct sub band by: 575 -))) 551 +917.0 - SF7BW125 to SF12BW125 576 576 577 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 578 -* 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) 553 +917.2 - SF7BW125 to SF12BW125 579 579 555 +917.4 - SF7BW125 to SF12BW125 556 + 557 +917.6 - SF7BW125 to SF12BW125 558 + 559 +917.8 - SF7BW125 to SF12BW125 560 + 561 +918.0 - SF7BW125 to SF12BW125 562 + 563 +918.2 - SF7BW125 to SF12BW125 564 + 565 + 566 +(% style="color:blue" %)**Downlink:** 567 + 568 +923.3 - SF7BW500 to SF12BW500 569 + 570 +923.9 - SF7BW500 to SF12BW500 571 + 572 +924.5 - SF7BW500 to SF12BW500 573 + 574 +925.1 - SF7BW500 to SF12BW500 575 + 576 +925.7 - SF7BW500 to SF12BW500 577 + 578 +926.3 - SF7BW500 to SF12BW500 579 + 580 +926.9 - SF7BW500 to SF12BW500 581 + 582 +927.5 - SF7BW500 to SF12BW500 583 + 584 +923.3 - SF12BW500(RX2 downlink only) 585 + 586 + 587 + 588 +))) 589 + 580 580 === 2.6.5 AS920-923 & AS923-925 (AS923) === 581 581 582 582 (((
- 1654850511545-399.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +88.3 KB - Content
- 1654850829385-439.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +59.2 KB - Content
- 1654851029373-510.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +92.0 KB - Content
- 1654852175653-550.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +106.2 KB - Content
- 1654852253176-749.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +106.6 KB - Content
- image-20220610165129-11.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +50.5 KB - Content