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, 6 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,23 +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.** 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 -[[image:image-20220610155021-2.png||height="377" width="1021"]] 79 79 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 - 82 -**(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.** 83 - 84 84 (% style="display:none" %) (%%) 85 85 86 -(% style="display:none" %)** **[[image:image-20220610155021-3.png||height="374" width="1020"]] 87 87 88 -(% style="display:none" %) (%%) 89 - 90 - 91 - 92 92 == 1.5 Applications == 93 93 94 94 * Horizontal distance measurement ... ... @@ -108,7 +108,6 @@ 108 108 [[image:1654847583902-256.png]] 109 109 110 110 111 - 112 112 = 2. Configure LDDS75 to connect to LoRaWAN network = 113 113 114 114 == 2.1 How it works == ... ... @@ -122,7 +122,6 @@ 122 122 ))) 123 123 124 124 125 - 126 126 == 2.2 Quick guide to connect to LoRaWAN server (OTAA) == 127 127 128 128 ((( ... ... @@ -152,43 +152,44 @@ 152 152 153 153 Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot: 154 154 155 -**Add APP EUI in the application** 156 156 157 - [[image:image-20220610161353-4.png]]145 +**Register the device** 158 158 159 -[[image:image-20220610161353-5.png]] 160 160 161 -[[image: image-20220610161353-6.png]]148 +[[image:1654592600093-601.png]] 162 162 163 163 164 -[[image:image-20220610161353-7.png]] 165 165 152 +**Add APP EUI and DEV EUI** 166 166 167 - You can also choose to create the devicemanually.154 +[[image:1654592619856-881.png]] 168 168 169 - [[image:image-20220610161538-8.png]] 170 170 171 171 158 +**Add APP EUI in the application** 172 172 173 - **Add APP KEYand DEV EUI**160 +[[image:1654592632656-512.png]] 174 174 175 -[[image:image-20220610161538-9.png]] 176 176 177 177 164 +**Add APP KEY** 178 178 179 - (% style="color:blue" %)**Step2**(%%): Power on LDDS75166 +[[image:1654592653453-934.png]] 180 180 181 181 169 +(% style="color:blue" %)**Step 2**(%%): Power on LLDS12 170 + 171 + 182 182 Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position). 183 183 184 -[[image:image-202206 10161724-10.png]]174 +[[image:image-20220607170442-2.png]] 185 185 186 186 187 187 ((( 188 -(% style="color:blue" %)**Step 3**(%%)**:** The LD DS75will 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.178 +(% style="color:blue" %)**Step 3**(%%)**:** The LLDS12 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. 189 189 ))) 190 190 191 -[[image:16548 49068701-275.png]]181 +[[image:1654833501679-968.png]] 192 192 193 193 194 194 ... ... @@ -195,10 +195,11 @@ 195 195 == 2.3 Uplink Payload == 196 196 197 197 ((( 198 -LDDS75 will uplink payload via LoRaWAN with below payload format: 188 +LLDS12 will uplink payload via LoRaWAN with below payload format: 189 +))) 199 199 200 - Uplink payload includes in total 4 bytes.201 - Payloadfor firmware versionv1.1.4. . Before v1.1.3, there ison twofields:BATand Distance191 +((( 192 +Uplink payload includes in total 11 bytes. 202 202 ))) 203 203 204 204 ((( ... ... @@ -208,23 +208,23 @@ 208 208 (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %) 209 209 |=(% style="width: 62.5px;" %)((( 210 210 **Size (bytes)** 211 -)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1** 212 -|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|((( 213 -[[Distance>>||anchor="H2.3.3A0Distance"]] 202 +)))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1** 203 +|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)((( 204 +[[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]] 205 +)))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|((( 206 +[[Interrupt flag>>||anchor="H2.3.5A0InterruptPin"]] 207 +)))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|((( 208 +[[Message Type>>||anchor="H2.3.7A0MessageType"]] 209 +))) 214 214 215 -(unit: mm) 216 -)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.4A0Distancesignalstrength"]]|((( 217 -[[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]] 218 -)))|[[Sensor Flag>>path:#Sensor_Flag]] 211 +[[image:1654833689380-972.png]] 219 219 220 -[[image:1654850511545-399.png]] 221 221 222 222 223 - 224 224 === 2.3.1 Battery Info === 225 225 226 226 227 -Check the battery voltage for LD DS75.218 +Check the battery voltage for LLDS12. 228 228 229 229 Ex1: 0x0B45 = 2885mV 230 230 ... ... @@ -232,22 +232,49 @@ 232 232 233 233 234 234 235 -=== 2.3.2 D istance ===226 +=== 2.3.2 DS18B20 Temperature sensor === 236 236 237 - Get thedistance.Flatobject range280mm-7500mm.228 +This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature. 238 238 239 -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.** 240 240 231 +**Example**: 241 241 242 -* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor. 243 -* 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 +If payload is: 0105H: (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree 244 244 235 +If payload is: FF3FH : (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. 245 245 246 246 247 -=== 2.3.3 Interrupt Pin === 248 248 239 +=== 2.3.3 Distance === 240 + 241 +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. 242 + 243 + 244 +**Example**: 245 + 246 +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. 247 + 248 + 249 + 250 +=== 2.3.4 Distance signal strength === 251 + 252 +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. 253 + 254 + 255 +**Example**: 256 + 257 +If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible. 258 + 259 +Customers can judge whether they need to adjust the environment based on the signal strength. 260 + 261 + 262 + 263 +=== 2.3.5 Interrupt Pin === 264 + 249 249 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. 250 250 267 +Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]]. 268 + 251 251 **Example:** 252 252 253 253 0x00: Normal uplink packet. ... ... @@ -256,44 +256,52 @@ 256 256 257 257 258 258 259 -=== 2.3. 4DS18B20Temperaturesensor===277 +=== 2.3.6 LiDAR temp === 260 260 261 - This is optional, usercanconnectxternal DS18B20 sensorto the+3.3v, 1-wire and GND pin . andthis fieldwill reporttemperature.279 +Characterize the internal temperature value of the sensor. 262 262 263 -**Example**: 281 +**Example: ** 282 +If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃. 283 +If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃. 264 264 265 -If payload is: 0105H: (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree 266 266 267 -If payload is: FF3FH : (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. 268 268 269 - (% style="color:red"%)Note: DS18B20feature isupported in the hardwareversion> v1.3 which made since early of 2021.287 +=== 2.3.7 Message Type === 270 270 289 +((( 290 +For a normal uplink payload, the message type is always 0x01. 291 +))) 271 271 293 +((( 294 +Valid Message Type: 295 +))) 272 272 273 -=== 2.3.5 Sensor Flag === 274 274 275 -0x01: Detect Ultrasonic Sensor 298 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %) 299 +|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload** 300 +|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]] 301 +|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]] 276 276 277 - 0x00:NoUltrasonicSensor303 +=== 2.3.8 Decode payload in The Things Network === 278 278 279 - 280 -=== 281 -(% style="color:inherit; font-family:inherit" %)2.3.6 Decode payload in The Things Network(%%) === 282 - 283 283 While using TTN network, you can add the payload format to decode the payload. 284 284 285 285 286 -[[image:1654 850829385-439.png]]308 +[[image:1654592762713-715.png]] 287 287 288 -The payload decoder function for TTN V3 is here: 310 +((( 311 +The payload decoder function for TTN is here: 312 +))) 289 289 290 -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/]] 314 +((( 315 +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/]] 316 +))) 291 291 292 292 293 293 294 294 == 2.4 Uplink Interval == 295 295 296 -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"]]322 +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"]] 297 297 298 298 299 299 ... ... @@ -324,25 +324,47 @@ 324 324 325 325 (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.** 326 326 327 -(% style="color:blue" %)**Step 4**(%%)**: Searchthe LDDS75andadd DevEUI.**353 +(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.** 328 328 329 -[[image:16548 51029373-510.png]]355 +[[image:1654832691989-514.png]] 330 330 331 331 332 - After added, the sensor data arrive TTN V3, it willalso arriveand show in Datacake.358 +[[image:1654592833877-762.png]] 333 333 334 -[[image:image-20220610165129-11.png||height="595" width="1088"]] 335 335 361 +[[image:1654832740634-933.png]] 336 336 337 337 338 -== 2.6 Frequency Plans == 339 339 340 340 ((( 341 - TheLDDS75 uses OTAA mode and below frequency plansby default. Ifuserwantto useitwithdifferentfrequencyplan, pleaserefer the ATcommandsets.366 +(% style="color:blue" %)**Step 5**(%%)**: add payload decode** 342 342 ))) 343 343 369 +((( 370 + 371 +))) 344 344 373 +[[image:1654833065139-942.png]] 345 345 375 + 376 + 377 +[[image:1654833092678-390.png]] 378 + 379 + 380 + 381 +After added, the sensor data arrive TTN, it will also arrive and show in Datacake. 382 + 383 +[[image:1654833163048-332.png]] 384 + 385 + 386 + 387 +== 2.6 Frequency Plans == 388 + 389 +((( 390 +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. 391 +))) 392 + 393 + 346 346 === 2.6.1 EU863-870 (EU868) === 347 347 348 348 ((( ... ... @@ -406,51 +406,20 @@ 406 406 === 2.6.2 US902-928(US915) === 407 407 408 408 ((( 409 -Used in USA, Canada and South America. Default use CHE=2 457 +Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document. 458 +))) 410 410 411 -(% style="color:blue" %)**Uplink:** 460 +((( 461 +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. 462 +))) 412 412 413 -903.9 - SF7BW125 to SF10BW125 414 - 415 -904.1 - SF7BW125 to SF10BW125 416 - 417 -904.3 - SF7BW125 to SF10BW125 418 - 419 -904.5 - SF7BW125 to SF10BW125 420 - 421 -904.7 - SF7BW125 to SF10BW125 422 - 423 -904.9 - SF7BW125 to SF10BW125 424 - 425 -905.1 - SF7BW125 to SF10BW125 426 - 427 -905.3 - SF7BW125 to SF10BW125 428 - 429 - 430 -(% style="color:blue" %)**Downlink:** 431 - 432 -923.3 - SF7BW500 to SF12BW500 433 - 434 -923.9 - SF7BW500 to SF12BW500 435 - 436 -924.5 - SF7BW500 to SF12BW500 437 - 438 -925.1 - SF7BW500 to SF12BW500 439 - 440 -925.7 - SF7BW500 to SF12BW500 441 - 442 -926.3 - SF7BW500 to SF12BW500 443 - 444 -926.9 - SF7BW500 to SF12BW500 445 - 446 -927.5 - SF7BW500 to SF12BW500 447 - 448 -923.3 - SF12BW500(RX2 downlink only) 449 - 450 - 451 - 464 +((( 465 +After Join success, the end node will switch to the correct sub band by: 452 452 ))) 453 453 468 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 469 +* 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) 470 + 454 454 === 2.6.3 CN470-510 (CN470) === 455 455 456 456 ((( ... ... @@ -543,51 +543,24 @@ 543 543 === 2.6.4 AU915-928(AU915) === 544 544 545 545 ((( 546 -Default use CHE=2 563 +Frequency band as per definition in LoRaWAN 1.0.3 Regional document. 564 +))) 547 547 548 -(% style="color:blue" %)**Uplink:** 566 +((( 567 +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. 568 +))) 549 549 550 -916.8 - SF7BW125 to SF12BW125 551 - 552 -917.0 - SF7BW125 to SF12BW125 553 - 554 -917.2 - SF7BW125 to SF12BW125 555 - 556 -917.4 - SF7BW125 to SF12BW125 557 - 558 -917.6 - SF7BW125 to SF12BW125 559 - 560 -917.8 - SF7BW125 to SF12BW125 561 - 562 -918.0 - SF7BW125 to SF12BW125 563 - 564 -918.2 - SF7BW125 to SF12BW125 565 - 566 - 567 -(% style="color:blue" %)**Downlink:** 568 - 569 -923.3 - SF7BW500 to SF12BW500 570 - 571 -923.9 - SF7BW500 to SF12BW500 572 - 573 -924.5 - SF7BW500 to SF12BW500 574 - 575 -925.1 - SF7BW500 to SF12BW500 576 - 577 -925.7 - SF7BW500 to SF12BW500 578 - 579 -926.3 - SF7BW500 to SF12BW500 580 - 581 -926.9 - SF7BW500 to SF12BW500 582 - 583 -927.5 - SF7BW500 to SF12BW500 584 - 585 -923.3 - SF12BW500(RX2 downlink only) 586 - 587 - 570 +((( 588 588 589 589 ))) 590 590 574 +((( 575 +After Join success, the end node will switch to the correct sub band by: 576 +))) 577 + 578 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 579 +* 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) 580 + 591 591 === 2.6.5 AS920-923 & AS923-925 (AS923) === 592 592 593 593 (((
- 1654849068701-275.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -88.3 KB - Content
- 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-20220610161724-10.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -180.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