Changes for page NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 17:03
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 6 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,16 +1,7 @@ 1 1 (% style="text-align:center" %) 2 -[[image:LMDS200_10.jpg ||height="572" width="572"]]2 +[[image:LMDS200_10.jpg]] 3 3 4 4 5 - 6 - 7 - 8 -(% style="display:none" %) (%%) 9 - 10 - 11 - 12 - 13 - 14 14 **Table of Contents:** 15 15 16 16 {{toc/}} ... ... @@ -18,11 +18,6 @@ 18 18 19 19 20 20 21 - 22 - 23 - 24 - 25 - 26 26 = 1. Introduction = 27 27 28 28 == 1.1 What is NMDS200 NB-IoT Microwave Radar Distance Sensor == ... ... @@ -30,33 +30,19 @@ 30 30 31 31 ((( 32 32 The Dragino NMDS200 is a(% style="color:blue" %)** NB-IoT Microwave Radar distance sensor**(%%). It uses (% style="color:blue" %)**24Ghz Microwave**(%%) to detect the distance between sensor and different objects. Compare vs ultrasonic or Lidar measurement method, Microwave Radar is (% style="color:blue" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or thick dust on top of the sensor. 33 -))) 34 34 35 -((( 36 36 The NMDS200 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc. 37 -))) 38 38 39 -((( 40 40 NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one. 41 -))) 42 42 43 -((( 44 44 NMDS200 (% style="color:blue" %)**supports Alarm Feature**(%%), user can set the NMDS200 to uplink data in a short interval when the distance is out of configured range. 45 -))) 46 46 47 -((( 48 48 NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technology**(%%) developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage. 49 -))) 50 50 51 -((( 52 52 NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements. 53 -))) 54 54 55 -((( 56 56 NMDS200 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**,(%%) It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 57 -))) 58 58 59 -((( 60 60 To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection. 61 61 ))) 62 62 ... ... @@ -78,22 +78,18 @@ 78 78 * Micro SIM card slot for NB-IoT SIM 79 79 * 8500mAh Battery for long-term use 80 80 81 - 82 - 83 83 == 1.3 Radar probe specification == 84 84 85 85 86 86 * Measuring Method: FMCW 87 -* Frequency: 24.000 ~~24.500 GHz57 +* Frequency: 24.000 24.500 GHz 88 88 * Measurement output power: 6dBm 89 -* Measure range: 0.5 ~~20m59 +* Measure range: 0.5 20m 90 90 * Accuracy: ±0.1m 91 91 * Resolution: 0.01m 92 92 * Horizontal Angel: 78° 93 93 * Vertical Angel: 23° 94 94 95 - 96 - 97 97 == 1.4 Storage Temperature == 98 98 99 99 ... ... @@ -113,8 +113,6 @@ 113 113 * Sewer 114 114 * Bottom water level monitoring 115 115 116 - 117 - 118 118 == 1.6 Specification == 119 119 120 120 ... ... @@ -132,8 +132,6 @@ 132 132 * B20 @H-FDD: 800MHz 133 133 * B28 @H-FDD: 700MHz 134 134 135 - 136 - 137 137 == 1.7 Installation == 138 138 139 139 ... ... @@ -140,12 +140,10 @@ 140 140 Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object. 141 141 142 142 143 -[[image:image-20221207170748-1.png]] 107 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]] 144 144 145 145 146 - [[image:image-20221207170748-2.png||height="345" width="634"]] 147 147 148 - 149 149 == 1.8 Pin Definitions and Switch == 150 150 151 151 ... ... @@ -161,7 +161,7 @@ 161 161 162 162 The diagram below shows the working flow in the default firmware of NMDS200: 163 163 164 -[[image:image-20221021110615-5.png ||height="996" width="492"]]126 +[[image:image-20221021110615-5.png]] 165 165 166 166 167 167 == 2.2 Configure NMDS200 == ... ... @@ -175,7 +175,7 @@ 175 175 176 176 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NMDS200 will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server. 177 177 178 -[[image:image-2022120 9090938-1.png]]140 +[[image:image-20221208090742-1.png]] 179 179 180 180 181 181 === 2.2.1 Insert NB-IoT SIM card === ... ... @@ -224,6 +224,7 @@ 224 224 (% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]] 225 225 226 226 189 + 227 227 === 2.2.3 Use CoAP protocol to uplink data === 228 228 229 229 ... ... @@ -240,7 +240,7 @@ 240 240 241 241 For parameter description, please refer to AT command set 242 242 243 -[[image: 1670471530120-960.png||height="647" width="674"]]206 +[[image:image-20221021110948-8.png]] 244 244 245 245 246 246 After configuring the server address and (% style="color:green" %)**reset NMDS200**(%%) (via AT+ATZ ), NMDS200 will start to uplink sensor values to the CoAP server. ... ... @@ -259,7 +259,7 @@ 259 259 260 260 * (% style="color:#037691" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 261 261 262 - [[image: 1670471559211-638.png]]225 + [[image:image-20221021111025-10.png]] 263 263 264 264 265 265 [[image:image-20221021111033-11.png||height="241" width="576"]] ... ... @@ -285,7 +285,7 @@ 285 285 286 286 * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB ** (%%) ~/~/ Set the subscription topic of MQTT 287 287 288 - [[image: 1670471584490-640.png]]251 + [[image:image-20221118103445-7.png]] 289 289 290 290 291 291 [[image:1670405928926-116.png]] ... ... @@ -304,7 +304,7 @@ 304 304 305 305 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ Set TCP server address and port 306 306 307 - [[image:16704 71613823-833.png]]270 + [[image:1670406036256-101.png||height="676" width="713"]] 308 308 309 309 310 310 [[image:image-20221021111131-15.png]] ... ... @@ -331,15 +331,15 @@ 331 331 Each time the device uploads a data package. The user can use the AT+NOUD command to upload the recorded data.Up to 32 sets of recorded data can be uploaded. 332 332 333 333 334 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width: 450px" %)335 -|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:30px" %)**2**|(% style="width:30px" %)**2**|(% style="width:75px" %)**1**|(% style="width:30px" %)**1**|(% style="width:50px" %)**1**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**297 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 298 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:90px" %)**2**|(% style="width:100px" %)**2** 336 336 |=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Exit flag|(% style="width:94px" %) [[Distance 1>>||anchor="H2.4.5A0Distance"]] |(% style="width:93px" %) [[Distance 2>>||anchor="H2.4.5A0Distance"]] 337 337 338 -(% border="1" style="background-color:#ffffcc; color:green; width:4 29px" %)339 -|(% style="width: 60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)(((301 +(% border="1" style="background-color:#ffffcc; color:green; width:471px" %) 302 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:98px" %)((( 340 340 **1-32 group** 341 341 ))) 342 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance 2|(% style="width:67px" %)Time stamp|(% style="width: 100px" %)...305 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance 2|(% style="width:67px" %)Time stamp|(% style="width:98px" %)... 343 343 344 344 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data. 345 345 ... ... @@ -346,8 +346,10 @@ 346 346 [[image:1670406261143-723.png]] 347 347 348 348 349 -The payload is ASCII string, representative same HEX: **0x (% style="color:red" %)__f867787050471071__(% style="color:blue" %)__0064__(% style="color:green" %) __0cc3__(%style="color:#00b0f0" %) 0__9__(%style="color:#7030a0" %) __01__(%style="color:#0020b0"%) __00__(% style="color:#420042" %)__00ef__(%style="color:#660066" %) (% style="color:#663300" %)__013d__(% style="color:#d60093" %)__6390453d__(%%)**312 +The payload is ASCII string, representative same HEX: f867787050471071 0064 0cc3 09 01 00 00ef 013d 6390453d 350 350 314 +**0x (% style="color:red" %)__f867787050471071__ (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)** 315 + 351 351 **where:** 352 352 353 353 * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071 ... ... @@ -368,8 +368,6 @@ 368 368 369 369 * (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time) 370 370 371 - 372 - 373 373 == 2.4 Payload Explanation and Sensor Interface == 374 374 375 375 === 2.4.1 Device ID === ... ... @@ -485,7 +485,6 @@ 485 485 * For each uplink probe, LED will be on for 500ms. 486 486 487 487 488 - 489 489 == 2.7 Distance alarm function == 490 490 491 491 ... ... @@ -493,7 +493,7 @@ 493 493 494 494 (% style="color:#037691" %)**Example 1:** 495 495 496 -AT+ ALARM1 =60,200 ~/~/ Alarm when distance1lower than 60.458 +AT+ ALARM1 =60,200 ~/~/ Alarm when moisture lower than 60. 497 497 498 498 AT+ ALARM2 =min,max 499 499 ... ... @@ -500,7 +500,7 @@ 500 500 501 501 (% style="color:#037691" %)**Example 2:** 502 502 503 -AT+ ALARM2 =200,1500 ~/~/ Alarm when distance2lower than 1500.465 +AT+ ALARM2 =200,1500 ~/~/ Alarm when temperature lower than 1500 504 504 505 505 506 506 == 2.8 Set the number of data to be uploaded and the recording time == ... ... @@ -528,7 +528,7 @@ 528 528 == 2.10 Firmware Change Log == 529 529 530 530 531 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8 elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0>>https://www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0]]493 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]] 532 532 533 533 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 534 534 ... ... @@ -630,13 +630,13 @@ 630 630 631 631 AT+INTMOD : Set the trigger interrupt mode 632 632 633 -AT+5VT : Set extend the time of 5V power 595 +AT+5VT : Set extend the time of 5V power 634 634 635 -AT+PRO : Choose agreement 597 +AT+PRO : Choose agreement 636 636 637 -AT+RXDL : Extend the sending and receiving time 599 +AT+RXDL : Extend the sending and receiving time 638 638 639 -AT+SERVADDR : Server Address 601 +AT+SERVADDR : Server Address 640 640 641 641 AT+TR : Get or Set record time 642 642 ... ... @@ -644,7 +644,7 @@ 644 644 645 645 AT+CDP : Read or Clear cached data 646 646 647 -AT+DEBUG: 609 +AT+DEBUG: Enable or Disable debug mode 648 648 649 649 AT+ALARM1: Get or Set alarm of distance1 650 650 ... ... @@ -724,8 +724,6 @@ 724 724 725 725 * NMDS200 NB-IoT Microwave Radar Distance Sensor x 1 726 726 727 - 728 - 729 729 = 9. Support = 730 730 731 731
- 1670471530120-960.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -67.6 KB - Content
- 1670471559211-638.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -170.6 KB - Content
- 1670471584490-640.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -91.1 KB - Content
- 1670471613823-833.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -181.0 KB - Content
- image-20221209090938-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -121.9 KB - Content
- image-20221212171610-1.jpeg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -756.0 KB - Content