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 (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 10 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -NDS0 3A-OutdoorNB-IoTOpen/CloseDoor Sensor User Manual1 +NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual - Content
-
... ... @@ -1,55 +1,35 @@ 1 1 (% style="text-align:center" %) 2 -[[image: image-20221117105556-1.png]]2 +[[image:LMDS200_10.jpg]] 3 3 4 4 5 - 6 - 7 - 8 - 9 - 10 10 **Table of Contents:** 11 11 12 -{{toc/}} 13 13 14 14 15 15 16 16 17 - 18 18 = 1. Introduction = 19 19 20 -== 1.1 What is NDS0 3ANB-IoTOpen/CloseDoor Sensor ==13 +== 1.1 What is NMDS200 NB-IoT Microwave Radar Distance Sensor == 21 21 22 22 23 23 ((( 24 -The Dragino NDS03A is an (% style="color:blue" %)**Open/Close NB-IoT Door Sensor**(%%). It detects door (% style="color:blue" %)**open/close status**(%%) and (% style="color:blue" %)**uplinks**(%%) to IoT server via NB-IoT network. NDS03A can connect two door sensors. user can see the door status, open duration, open counts in the IoT Server. 25 -))) 17 +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. 26 26 27 -((( 28 -The NDS03A will send periodically data (% style="color:blue" %)**every 4 hours** (%%)as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically. 29 -))) 30 30 31 -((( 32 -NDS03A has a (% style="color:blue" %)**Datalog feature**(%%), it will record the open/close event and the user can retrieve the history from NB-IoT. 33 -))) 20 +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. 34 34 35 -((( 36 -NDS03A has the(% style="color:blue" %)**open alarm feature**(%%), user can set this feature so the device will send an alarm if the door has been open for a certain time. 37 -))) 22 +NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one. 38 38 39 -((( 40 -NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures. 41 -))) 24 +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. 42 42 43 -((( 44 -NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technologyTCP, MQTT, UDP, and CoAP**(%%) for different application requirements. 45 -))) 26 +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. 46 46 47 -((( 48 -NDS03A 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) 49 -))) 28 +NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements. 50 50 51 -((( 52 -To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into NDS03A to get NB-IoT network connection. 30 +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) 31 + 32 +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. 53 53 ))) 54 54 55 55 ... ... @@ -58,10 +58,9 @@ 58 58 59 59 60 60 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 61 -* Open/Close detect 62 -* Open/Close statistics 41 +* Short uplink interval for Distance Alarm 63 63 * Monitor Battery Level 64 -* co nnecttwodoor sensors43 +* Microwave Radar for distance detection 65 65 * Datalog feature 66 66 * Uplink periodically 67 67 * Downlink to change configure ... ... @@ -74,22 +74,27 @@ 74 74 75 75 76 76 77 -== 1.3 Storage& Operation ==56 +== 1.3 Radar probe specification == 78 78 79 79 80 -Temperature -40°C to +85°C 59 +* Measuring Method: FMCW 60 +* Frequency: 24.000 24.500 GHz 61 +* Measurement output power: 6dBm 62 +* Measure range: 0.5 20m 63 +* Accuracy: ±0.1m 64 +* Resolution: 0.01m 65 +* Horizontal Angel: 78° 66 +* Vertical Angel: 23° 81 81 82 82 83 -== 1.4 Mechanical == 84 84 85 85 86 - [[image:image-20221117114937-4.png]]71 +== 1.4 Storage Temperature == 87 87 88 88 89 - [[image:image-20221117114949-5.png]]74 + -40°C to +85°C 90 90 91 91 92 -[[image:image-20221117115010-6.png]] 93 93 94 94 95 95 ... ... @@ -96,10 +96,19 @@ 96 96 == 1.5 Applications == 97 97 98 98 99 -[[image:image-20221117114842-3.png]] 100 100 84 +* Horizontal distance measurement 85 +* Liquid level measurement 86 +* Parking management system 87 +* Object proximity and presence detection 88 +* Intelligent trash can management system 89 +* Robot obstacle avoidance 90 +* Automatic control 91 +* Sewer 92 +* Bottom water level monitoring 101 101 102 102 95 + 103 103 == 1.6 Specification == 104 104 105 105 ... ... @@ -106,98 +106,62 @@ 106 106 (% style="color:blue" %)**Common DC Characteristics:** 107 107 108 108 * Supply Voltage: 2.1v ~~ 3.6v 109 -* Operating Temperature: -40 ~~85°C102 +* Operating Temperature: 0 ~~ 70°C 110 110 111 111 (% style="color:blue" %)**NB-IoT Spec:** 112 112 113 -* -B1 @H-FDD: 2100MHz114 -* -B3 @H-FDD: 1800MHz115 -* -B8 @H-FDD: 900MHz116 -* -B5 @H-FDD: 850MHz117 -* -B20 @H-FDD: 800MHz118 -* -B28 @H-FDD: 700MHz106 +* B1 @H-FDD: 2100MHz 107 +* B3 @H-FDD: 1800MHz 108 +* B8 @H-FDD: 900MHz 109 +* B5 @H-FDD: 850MHz 110 +* B20 @H-FDD: 800MHz 111 +* B28 @H-FDD: 700MHz 119 119 120 120 121 121 122 -== 1.7 PinDefinitionsand Switch==115 +== 1.7 Installation == 123 123 124 124 125 - [[image:image-20221021110429-4.png]]118 +Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object. 126 126 127 127 128 - ===1.7.1PinDefinition===121 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]] 129 129 130 130 131 -The device is pre-configured to connect to a door sensor. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at: [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]] 132 132 125 +== 1.8 Pin Definitions and Switch == 133 133 134 -=== 1.7.2 Jumper JP2(Power ON/OFF) === 135 135 128 +[[image:1670404362039-351.png]] 136 136 137 -Power on Device when putting this jumper. 138 138 131 += 2. Use NMDS200 to communicate with IoT Server = 139 139 140 -=== 1.7.3 BOOT MODE / SW1 === 141 - 142 - 143 -1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run. 144 - 145 -2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging. 146 - 147 - 148 -=== 1.7.4 Reset Button === 149 - 150 - 151 -Press to reboot the device. 152 - 153 - 154 -=== 1.7.5 LED === 155 - 156 - 157 -The LED will blink when : 158 - 159 -1. Boot the device in flash mode 160 - 161 -2. Send an uplink packet 162 - 163 - 164 -== 1.8 Magnet Distance == 165 - 166 - 167 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm 168 - 169 -(% style="color:blue" %)**Iron Door:**(%%)** **30 ~~ 45mm 170 - 171 - 172 -= 2. Use NDS03A to communicate with IoT Server = 173 - 174 174 == 2.1 How it works == 175 175 176 176 177 - In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoTserver. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A.136 +The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200. 178 178 179 -The diagram below shows the working flow in the default firmware of NDS0 3A:138 +The diagram below shows the working flow in the default firmware of NMDS200: 180 180 181 181 [[image:image-20221021110615-5.png]] 182 182 183 183 184 -== 2.2 Configure NDS0 3A==143 +== 2.2 Configure NMDS200 == 185 185 186 -=== 2.2.1 Test Requirement === 187 187 146 +To use NMDS200 in your city, make sure to meet below requirements: 188 188 189 -To use NDS03A in your city, make sure to meet below requirements: 190 - 191 191 * Your local operator has already distributed an NB-IoT Network. 192 -* The local NB-IoT network used the band that NDS0 3Asupports.149 +* The local NB-IoT network used the band that NMDS200 supports. 193 193 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 194 194 195 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NDS0 3Awill 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.152 +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. 196 196 197 -[[image:image-20221 117142300-1.png]]154 +[[image:image-20221207173300-4.png]] 198 198 199 199 200 -=== 2.2. 2Insert NB-IoT SIM card ===157 +=== 2.2.1 Insert NB-IoT SIM card === 201 201 202 202 203 203 Insert the NB-IoT Card get from your provider. ... ... @@ -207,10 +207,10 @@ 207 207 [[image:image-20221021110745-6.png]] 208 208 209 209 210 -=== 2.2. 3Connect USB – TTL to NDS03Aand configure it ===167 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it === 211 211 212 212 213 -User need to configure NDS0 3Avia serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03Asupport AT Commands, user can use a USB to TTL adapter to connect to NDS03Aand use AT Commands to configure it, as below.170 +User need to configure NMDS200 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NMDS200 support AT Commands, user can use a USB to TTL adapter to connect to NMDS200 and use AT Commands to configure it, as below. 214 214 215 215 (% style="color:blue" %)**Connection:** 216 216 ... ... @@ -233,11 +233,11 @@ 233 233 234 234 * Flow Control: (% style="color:red" %)**None** 235 235 236 -Make sure the switch is in FLASH position, then power on NDS0 3Aby connecting the (% style="color:orange" %)**Yellow Jumper**(%%).193 +Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%). 237 237 238 238 [[image:image-20221021110817-7.png]] 239 239 240 -NDS0 3Awill output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.197 +NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input. 241 241 242 242 243 243 (% 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]] ... ... @@ -244,7 +244,7 @@ 244 244 245 245 246 246 247 -=== 2.2. 4Use CoAP protocol to uplink data ===204 +=== 2.2.3 Use CoAP protocol to uplink data === 248 248 249 249 250 250 (% style="color:red" %)**Note: if you don't have a CoAP server, you can refer this link to set up a CoAP server: **(%%)[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] ... ... @@ -263,12 +263,12 @@ 263 263 [[image:image-20221021110948-8.png]] 264 264 265 265 266 -After configuring the server address and (% style="color:green" %)**reset NDS0 3A**(%%)3Awill start to uplink sensor values to the CoAP server.223 +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. 267 267 268 -[[image: image-20221118103547-9.png||height="605" width="837"]] 225 +[[image:1670405841875-916.png]] 269 269 270 270 271 -=== 2.2. 5Use UDP protocol to uplink data(Default protocol) ===228 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) === 272 272 273 273 274 274 (% style="color:blue" %)**AT Commands:** ... ... @@ -286,7 +286,7 @@ 286 286 287 287 288 288 289 -=== 2.2. 6Use MQTT protocol to uplink data ===246 +=== 2.2.5 Use MQTT protocol to uplink data === 290 290 291 291 292 292 (% style="color:blue" %)**AT Commands:** ... ... @@ -308,7 +308,7 @@ 308 308 [[image:image-20221118103445-7.png]] 309 309 310 310 311 -[[image: image-20221118103453-8.png||height="608" width="841"]]268 +[[image:1670405928926-116.png]] 312 312 313 313 314 314 ... ... @@ -315,7 +315,7 @@ 315 315 MQTT protocol has a much higher power consumption compare with UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 316 316 317 317 318 -=== 2.2. 7Use TCP protocol to uplink data ===275 +=== 2.2.6 Use TCP protocol to uplink data === 319 319 320 320 321 321 (% style="color:blue" %)**AT Commands:** ... ... @@ -324,18 +324,19 @@ 324 324 325 325 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ Set TCP server address and port 326 326 327 - [[image: image-20221021111125-14.png]]284 + [[image:1670406036256-101.png||height="676" width="713"]] 328 328 286 + 329 329 [[image:image-20221021111131-15.png]] 330 330 331 331 332 332 333 -=== 2.2. 8Change Update Interval ===291 +=== 2.2.7 Change Update Interval === 334 334 335 335 336 336 User can use below command to change the (% style="color:blue" %)**uplink interval**. 337 337 338 -* (% style="color:#037691" %)**AT+TDC= 14400 ** (%%) ~/~/ Set Update Interval to14400s (4 hours)296 +* (% style="color:#037691" %)**AT+TDC=7200 ** (%%) ~/~/ Set Update Interval to 7200s (4 hours) 339 339 340 340 (% style="color:red" %)**NOTE:** 341 341 ... ... @@ -361,7 +361,6 @@ 361 361 ))) 362 362 |(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:115px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)|(% style="width:99px" %)last open time(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)... 363 363 364 - 365 365 (% style="color:blue" %)**When AT+TTRCHANNEL=2:** 366 366 367 367 ... ... @@ -379,7 +379,6 @@ 379 379 ))) 380 380 |(% style="width:102px" %)last open time(pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:100px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)...... 381 381 382 - 383 383 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data. 384 384 385 385 [[image:image-20221117145932-2.png]] ... ... @@ -411,7 +411,6 @@ 411 411 412 412 * (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time) 413 413 414 - 415 415 == 2.4 Payload Explanation and Sensor Interface == 416 416 417 417 === 2.4.1 Device ID === ... ... @@ -528,7 +528,6 @@ 528 528 * After NDS03A join NB-IoT network. The LED will be ON for 3 seconds. 529 529 * For each uplink probe, LED will be on for 500ms. 530 530 531 - 532 532 == 2.7 Alarm Base on Timeout == 533 533 534 534 ... ... @@ -853,8 +853,6 @@ 853 853 854 854 * NDS03A Open/Close Door Sensor x 1 855 855 856 - 857 - 858 858 = 9. Support = 859 859 860 860
- 1670404362039-351.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +492.6 KB - Content
- 1670405841875-916.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +76.1 KB - Content
- 1670405928926-116.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +76.7 KB - Content
- 1670406036256-101.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +181.0 KB - Content
- 1670406261143-723.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +77.9 KB - Content
- LMDS200_10.jpg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +39.9 KB - Content
- image-20221207170748-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +26.1 KB - Content
- image-20221207170748-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +29.9 KB - Content
- image-20221207173200-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +76.7 KB - Content
- image-20221207173300-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +77.0 KB - Content