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, 0 added, 4 removed)
Details
- Page properties
-
- Content
-
... ... @@ -57,7 +57,6 @@ 57 57 * IP66 Waterproof Enclosure 58 58 * 4000mAh or 8500mAh Battery for long term use 59 59 60 - 61 61 == 1.3 Specification == 62 62 63 63 === 1.3.1 Rated environmental conditions === ... ... @@ -72,20 +72,15 @@ 72 72 73 73 === 1.3.2 Effective measurement range Reference beam pattern === 74 74 75 -**(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=" 377" width="1021"]]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 76 77 77 78 78 79 -**(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.**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 80 81 81 (% style="display:none" %) (%%) 82 82 83 -(% style="display:none" %)** **[[image:image-20220610155021-3.png||height="374" width="1020"]] 84 84 85 -(% style="display:none" %) (%%) 86 - 87 - 88 - 89 89 == 1.5 Applications == 90 90 91 91 * Horizontal distance measurement ... ... @@ -105,7 +105,6 @@ 105 105 [[image:1654847583902-256.png]] 106 106 107 107 108 - 109 109 = 2. Configure LDDS75 to connect to LoRaWAN network = 110 110 111 111 == 2.1 How it works == ... ... @@ -119,7 +119,6 @@ 119 119 ))) 120 120 121 121 122 - 123 123 == 2.2 Quick guide to connect to LoRaWAN server (OTAA) == 124 124 125 125 ((( ... ... @@ -192,7 +192,7 @@ 192 192 == 2.3 Uplink Payload == 193 193 194 194 ((( 195 -LDDS75 will uplink payload via LoRaWAN with below payload format: 187 +LDDS75 will uplink payload via LoRaWAN with below payload format: 196 196 197 197 Uplink payload includes in total 4 bytes. 198 198 Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance ... ... @@ -214,7 +214,7 @@ 214 214 [[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]] 215 215 )))|[[Sensor Flag>>path:#Sensor_Flag]] 216 216 217 -[[image:16548 50511545-399.png]]209 +[[image:1654833689380-972.png]] 218 218 219 219 220 220 ... ... @@ -221,7 +221,7 @@ 221 221 === 2.3.1 Battery Info === 222 222 223 223 224 -Check the battery voltage for LD DS75.216 +Check the battery voltage for LLDS12. 225 225 226 226 Ex1: 0x0B45 = 2885mV 227 227 ... ... @@ -229,22 +229,49 @@ 229 229 230 230 231 231 232 -=== 2.3.2 D istance ===224 +=== 2.3.2 DS18B20 Temperature sensor === 233 233 234 - Get thedistance.Flatobject range280mm-7500mm.226 +This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature. 235 235 236 -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.** 237 237 229 +**Example**: 238 238 239 -* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor. 240 -* 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. 231 +If payload is: 0105H: (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree 241 241 233 +If payload is: FF3FH : (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. 242 242 243 243 244 -=== 2.3.3 Interrupt Pin === 245 245 237 +=== 2.3.3 Distance === 238 + 239 +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. 240 + 241 + 242 +**Example**: 243 + 244 +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. 245 + 246 + 247 + 248 +=== 2.3.4 Distance signal strength === 249 + 250 +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. 251 + 252 + 253 +**Example**: 254 + 255 +If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible. 256 + 257 +Customers can judge whether they need to adjust the environment based on the signal strength. 258 + 259 + 260 + 261 +=== 2.3.5 Interrupt Pin === 262 + 246 246 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. 247 247 265 +Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]]. 266 + 248 248 **Example:** 249 249 250 250 0x00: Normal uplink packet. ... ... @@ -253,44 +253,52 @@ 253 253 254 254 255 255 256 -=== 2.3. 4DS18B20Temperaturesensor===275 +=== 2.3.6 LiDAR temp === 257 257 258 - This is optional, usercanconnectxternal DS18B20 sensorto the+3.3v, 1-wire and GND pin . andthis fieldwill reporttemperature.277 +Characterize the internal temperature value of the sensor. 259 259 260 -**Example**: 279 +**Example: ** 280 +If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃. 281 +If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃. 261 261 262 -If payload is: 0105H: (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree 263 263 264 -If payload is: FF3FH : (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. 265 265 266 - (% style="color:red"%)Note: DS18B20feature isupported in the hardwareversion> v1.3 which made since early of 2021.285 +=== 2.3.7 Message Type === 267 267 287 +((( 288 +For a normal uplink payload, the message type is always 0x01. 289 +))) 268 268 291 +((( 292 +Valid Message Type: 293 +))) 269 269 270 -=== 2.3.5 Sensor Flag === 271 271 272 -0x01: Detect Ultrasonic Sensor 296 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %) 297 +|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload** 298 +|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]] 299 +|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]] 273 273 274 - 0x00:NoUltrasonicSensor301 +=== 2.3.8 Decode payload in The Things Network === 275 275 276 - 277 -=== 278 -(% style="color:inherit; font-family:inherit" %)2.3.6 Decode payload in The Things Network(%%) === 279 - 280 280 While using TTN network, you can add the payload format to decode the payload. 281 281 282 282 283 -[[image:1654 850829385-439.png]]306 +[[image:1654592762713-715.png]] 284 284 285 -The payload decoder function for TTN V3 is here: 308 +((( 309 +The payload decoder function for TTN is here: 310 +))) 286 286 287 -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/]] 312 +((( 313 +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/]] 314 +))) 288 288 289 289 290 290 291 291 == 2.4 Uplink Interval == 292 292 293 -The LD DS75by 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"]]320 +The LLDS12 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"]] 294 294 295 295 296 296 ... ... @@ -321,25 +321,47 @@ 321 321 322 322 (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.** 323 323 324 -(% style="color:blue" %)**Step 4**(%%)**: Searchthe LDDS75andadd DevEUI.**351 +(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.** 325 325 326 -[[image:16548 51029373-510.png]]353 +[[image:1654832691989-514.png]] 327 327 328 328 329 - After added, the sensor data arrive TTN V3, it willalso arriveand show in Datacake.356 +[[image:1654592833877-762.png]] 330 330 331 -[[image:image-20220610165129-11.png||height="595" width="1088"]] 332 332 359 +[[image:1654832740634-933.png]] 333 333 334 334 335 -== 2.6 Frequency Plans == 336 336 337 337 ((( 338 - TheLDDS75 uses OTAA mode and below frequency plansby default. Ifuserwantto useitwithdifferentfrequencyplan, pleaserefer the ATcommandsets.364 +(% style="color:blue" %)**Step 5**(%%)**: add payload decode** 339 339 ))) 340 340 367 +((( 368 + 369 +))) 341 341 371 +[[image:1654833065139-942.png]] 342 342 373 + 374 + 375 +[[image:1654833092678-390.png]] 376 + 377 + 378 + 379 +After added, the sensor data arrive TTN, it will also arrive and show in Datacake. 380 + 381 +[[image:1654833163048-332.png]] 382 + 383 + 384 + 385 +== 2.6 Frequency Plans == 386 + 387 +((( 388 +The LLDS12 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. 389 +))) 390 + 391 + 343 343 === 2.6.1 EU863-870 (EU868) === 344 344 345 345 ((( ... ... @@ -403,51 +403,20 @@ 403 403 === 2.6.2 US902-928(US915) === 404 404 405 405 ((( 406 -Used in USA, Canada and South America. Default use CHE=2 455 +Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document. 456 +))) 407 407 408 -(% style="color:blue" %)**Uplink:** 458 +((( 459 +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. 460 +))) 409 409 410 -903.9 - SF7BW125 to SF10BW125 411 - 412 -904.1 - SF7BW125 to SF10BW125 413 - 414 -904.3 - SF7BW125 to SF10BW125 415 - 416 -904.5 - SF7BW125 to SF10BW125 417 - 418 -904.7 - SF7BW125 to SF10BW125 419 - 420 -904.9 - SF7BW125 to SF10BW125 421 - 422 -905.1 - SF7BW125 to SF10BW125 423 - 424 -905.3 - SF7BW125 to SF10BW125 425 - 426 - 427 -(% style="color:blue" %)**Downlink:** 428 - 429 -923.3 - SF7BW500 to SF12BW500 430 - 431 -923.9 - SF7BW500 to SF12BW500 432 - 433 -924.5 - SF7BW500 to SF12BW500 434 - 435 -925.1 - SF7BW500 to SF12BW500 436 - 437 -925.7 - SF7BW500 to SF12BW500 438 - 439 -926.3 - SF7BW500 to SF12BW500 440 - 441 -926.9 - SF7BW500 to SF12BW500 442 - 443 -927.5 - SF7BW500 to SF12BW500 444 - 445 -923.3 - SF12BW500(RX2 downlink only) 446 - 447 - 448 - 462 +((( 463 +After Join success, the end node will switch to the correct sub band by: 449 449 ))) 450 450 466 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 467 +* 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) 468 + 451 451 === 2.6.3 CN470-510 (CN470) === 452 452 453 453 ((( ... ... @@ -540,51 +540,24 @@ 540 540 === 2.6.4 AU915-928(AU915) === 541 541 542 542 ((( 543 -Default use CHE=2 561 +Frequency band as per definition in LoRaWAN 1.0.3 Regional document. 562 +))) 544 544 545 -(% style="color:blue" %)**Uplink:** 564 +((( 565 +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. 566 +))) 546 546 547 -916.8 - SF7BW125 to SF12BW125 548 - 549 -917.0 - SF7BW125 to SF12BW125 550 - 551 -917.2 - SF7BW125 to SF12BW125 552 - 553 -917.4 - SF7BW125 to SF12BW125 554 - 555 -917.6 - SF7BW125 to SF12BW125 556 - 557 -917.8 - SF7BW125 to SF12BW125 558 - 559 -918.0 - SF7BW125 to SF12BW125 560 - 561 -918.2 - SF7BW125 to SF12BW125 562 - 563 - 564 -(% style="color:blue" %)**Downlink:** 565 - 566 -923.3 - SF7BW500 to SF12BW500 567 - 568 -923.9 - SF7BW500 to SF12BW500 569 - 570 -924.5 - SF7BW500 to SF12BW500 571 - 572 -925.1 - SF7BW500 to SF12BW500 573 - 574 -925.7 - SF7BW500 to SF12BW500 575 - 576 -926.3 - SF7BW500 to SF12BW500 577 - 578 -926.9 - SF7BW500 to SF12BW500 579 - 580 -927.5 - SF7BW500 to SF12BW500 581 - 582 -923.3 - SF12BW500(RX2 downlink only) 583 - 584 - 568 +((( 585 585 586 586 ))) 587 587 572 +((( 573 +After Join success, the end node will switch to the correct sub band by: 574 +))) 575 + 576 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 577 +* 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) 578 + 588 588 === 2.6.5 AS920-923 & AS923-925 (AS923) === 589 589 590 590 (((
- 1654850511545-399.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -88.3 KB - Content
- 1654850829385-439.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -59.2 KB - Content
- 1654851029373-510.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -92.0 KB - Content
- image-20220610165129-11.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -50.5 KB - Content