<
From version < 83.2 >
edited by Xiaoling
on 2022/12/08 09:28
To version < 90.16 >
edited by Xiaoling
on 2023/05/26 10:28
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,13 +1,28 @@
1 1  (% style="text-align:center" %)
2 -[[image:LMDS200_10.jpg]]
2 +[[image:LMDS200_10.jpg||height="572" width="572"]]
3 3  
4 4  
5 +
6 +
7 +
8 +(% style="display:none" %) (%%)
9 +
10 +
11 +
12 +
13 +
5 5  **Table of Contents:**
6 6  
16 +{{toc/}}
7 7  
8 8  
9 9  
10 10  
21 +
22 +
23 +
24 +
25 +
11 11  = 1.  Introduction =
12 12  
13 13  == 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
... ... @@ -15,19 +15,33 @@
15 15  
16 16  (((
17 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.
33 +)))
18 18  
35 +(((
19 19  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 +)))
20 20  
39 +(((
21 21  NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
41 +)))
22 22  
43 +(((
23 23  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 +)))
24 24  
47 +(((
25 25  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 +)))
26 26  
51 +(((
27 27  NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
53 +)))
28 28  
55 +(((
29 29  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 +)))
30 30  
59 +(((
31 31  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.
32 32  )))
33 33  
... ... @@ -53,9 +53,9 @@
53 53  
54 54  
55 55  * Measuring Method: FMCW
56 -* Frequency: 24.000 24.500 GHz
85 +* Frequency: 24.000 ~~ 24.500 GHz
57 57  * Measurement output power: 6dBm
58 -* Measure range: 0.5 20m
87 +* Measure range: 0.5 ~~ 20m
59 59  * Accuracy: ±0.1m
60 60  * Resolution: 0.01m
61 61  * Horizontal Angel: 78°
... ... @@ -103,10 +103,12 @@
103 103  Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
104 104  
105 105  
106 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
135 +[[image:image-20221207170748-1.png]]
107 107  
108 108  
138 + [[image:image-20221207170748-2.png||height="345" width="634"]]
109 109  
140 +
110 110  == 1.8  Pin Definitions and Switch ==
111 111  
112 112  
... ... @@ -122,7 +122,7 @@
122 122  
123 123  The diagram below shows the working flow in the default firmware of NMDS200:
124 124  
125 -[[image:image-20221021110615-5.png]]
156 +[[image:image-20221021110615-5.png||height="996" width="492"]]
126 126  
127 127  
128 128  == 2.2 ​ Configure NMDS200 ==
... ... @@ -136,7 +136,7 @@
136 136  
137 137  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.
138 138  
139 -[[image:image-20221208090742-1.png]]
170 +[[image:image-20221209090938-1.png]]
140 140  
141 141  
142 142  === 2.2.1 Insert NB-IoT SIM card ===
... ... @@ -185,7 +185,6 @@
185 185  (% 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]]
186 186  
187 187  
188 -
189 189  === 2.2.3 Use CoAP protocol to uplink data ===
190 190  
191 191  
... ... @@ -202,7 +202,7 @@
202 202  
203 203  For parameter description, please refer to AT command set
204 204  
205 -[[image:image-20221021110948-8.png]]
235 +[[image:1670471530120-960.png||height="647" width="674"]]
206 206  
207 207  
208 208  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.
... ... @@ -221,7 +221,7 @@
221 221  
222 222  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
223 223  
224 -​ [[image:image-20221021111025-10.png]]
254 +​ [[image:1670471559211-638.png]]
225 225  
226 226  
227 227  [[image:image-20221021111033-11.png||height="241" width="576"]]
... ... @@ -247,7 +247,7 @@
247 247  
248 248  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
249 249  
250 -​ [[image:image-20221118103445-7.png]]
280 +​ [[image:1670471584490-640.png]]
251 251  
252 252  
253 253  [[image:1670405928926-116.png]]
... ... @@ -266,7 +266,7 @@
266 266  
267 267  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
268 268  
269 -​ [[image:1670406036256-101.png||height="676" width="713"]]
299 +​ [[image:1670471613823-833.png]]
270 270  
271 271  
272 272  [[image:image-20221021111131-15.png]]
... ... @@ -293,15 +293,15 @@
293 293  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.
294 294  
295 295  
296 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
297 -|=(% 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**
298 -|=(% 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 |(% style="width:93px" %) Distance  2
326 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %)
327 +|(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:50px" %)**8**|(% style="background-color:#4f81bd; color:white; width:30px" %)**2**|(% style="background-color:#4f81bd; color:white; width:30px" %)**2**|(% style="background-color:#4f81bd; color:white; width:75px" %)**1**|(% style="background-color:#4f81bd; color:white; width:30px" %)**1**|(% style="background-color:#4f81bd; color:white; width:50px" %)**1**|(% style="background-color:#4f81bd; color:white; width:60px" %)**2**|(% style="background-color:#4f81bd; color:white; width:60px" %)**2**
328 +|(% 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"]]
299 299  
300 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
301 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
330 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:430px" %)
331 +|(% style="background-color:#4f81bd; color:white; width:80px" %)**4**|(% style="background-color:#4f81bd; color:white; width:80px" %)**2**|(% style="background-color:#4f81bd; color:white; width:80px" %)**2**|(% style="background-color:#4f81bd; color:white; width:80px" %)**4**|(% style="background-color:#4f81bd; color:white; width:110px" %)(((
302 302  **1-32 group**
303 303  )))
304 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
334 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)...
305 305  
306 306  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
307 307  
... ... @@ -308,10 +308,8 @@
308 308  [[image:1670406261143-723.png]]
309 309  
310 310  
311 -The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
341 +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 312  
313 -**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__(%%)**
314 -
315 315  **where:**
316 316  
317 317  * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
... ... @@ -353,7 +353,7 @@
353 353  
354 354  Specify the software version: 0x64=100, which means firmware version 1.00.
355 355  
356 -For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
384 +For example 0x00 64 : This device is NMDS200 with firmware version 1.0.0.
357 357  
358 358  
359 359  === 2.4.3  Battery Info ===
... ... @@ -371,17 +371,17 @@
371 371  
372 372  NB-IoT Network signal Strength.
373 373  
374 -**Ex1: 0x1d = 29**
402 +(% style="color:blue" %)**Ex1: 0x1d = 29**
375 375  
376 -**0**  -113dBm or less
404 +(% style="color:#037691" %)**0** (%%) -113dBm or less
377 377  
378 -**1**  -111dBm
406 +(% style="color:#037691" %)**1**  (%%) -111dBm
379 379  
380 -**2...30** -109dBm... -53dBm
408 +(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
381 381  
382 -**31**   -51dBm or greater
410 +(% style="color:#037691" %)**31** (%%) -51dBm or greater
383 383  
384 -**99**    Not known or not detectable
412 +(% style="color:#037691" %)**99** (%%) Not known or not detectable
385 385  
386 386  
387 387  === 2.4.5  Distance ===
... ... @@ -415,9 +415,12 @@
415 415  
416 416  By default, NMDS200 prints the downlink payload to console port.
417 417  
418 -[[image:image-20221021111414-18.png]] ​
446 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %)
447 +|(% style="background-color:#d9e2f3; color:#0070c0" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:97px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; width:183px" %)**Downlink payload size(bytes)**
448 +|TDC (Transmit Time Interval)|Any|(% style="width:97px" %)01|(% style="width:183px" %)4
449 +|RESET|Any|(% style="width:97px" %)04|(% style="width:183px" %)2
450 +|INTMOD|Any|(% style="width:97px" %)06|(% style="width:183px" %)4
419 419  
420 -
421 421  **Examples:**
422 422  
423 423  * (% style="color:#037691" %)**Set TDC**
... ... @@ -446,28 +446,23 @@
446 446  * After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
447 447  * For each uplink probe, LED will be on for 500ms.
448 448  
449 -
450 -
451 -
452 452  == 2.7  Distance alarm function ==
453 453  
454 454  
455 455  (% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
456 456  
457 -**(% style="color:blue" %)Example 1:**
485 +(% style="color:#037691" %)**Example 1:**
458 458  
459 -AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
487 +AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
460 460  
461 461  AT+ ALARM2 =min,max
462 462  
463 463  
464 -**(% style="color:blue" %)Example 2:**
492 +(% style="color:#037691" %)**Example 2:**
465 465  
466 -AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
494 +AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
467 467  
468 468  
469 -
470 -
471 471  == 2.8  Set the number of data to be uploaded and the recording time ==
472 472  
473 473  
... ... @@ -493,65 +493,19 @@
493 493  == 2.10  ​Firmware Change Log ==
494 494  
495 495  
496 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
522 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0>>https://www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0]]
497 497  
498 498  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
499 499  
500 500  
501 -== 2.11  Battery Analysis ==
527 +== 2.11 Battery & Power Consumption ==
502 502  
503 -=== 2.11.1  ​Battery Type ===
504 504  
530 +NMDS200 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
505 505  
506 -The NMDS200 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
532 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
507 507  
508 -The battery is designed to last for several years depends on the actual use environment and update interval. 
509 509  
510 -The battery-related documents as below:
511 -
512 -* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
513 -
514 -* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
515 -
516 -* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
517 -
518 -[[image:image-20221021111911-26.png]] ​
519 -
520 -
521 -=== 2.11.2  Power consumption Analyze ===
522 -
523 -
524 -Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
525 -
526 -Instruction to use as below:
527 -
528 -(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
529 -
530 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
531 -
532 -* Product Model
533 -
534 -* Uplink Interval
535 -
536 -* Working Mode
537 -
538 -And the Life expectation in difference case will be shown on the right.
539 -
540 -[[image:1666596205057-567.png]] ​
541 -
542 -
543 -=== 2.11.3  ​Battery Note ===
544 -
545 -
546 -The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
547 -
548 -
549 -=== 2.11.4  Replace the battery ===
550 -
551 -
552 -The default battery pack of NMDS200 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
553 -
554 -
555 555  = 3. ​ Access NB-IoT Module =
556 556  
557 557  
... ... @@ -595,13 +595,13 @@
595 595  
596 596  AT+INTMOD            : Set the trigger interrupt mode
597 597  
598 -AT+5VT  : Set extend the time of 5V power  
578 +AT+5VT  : Set extend the time of 5V power  
599 599  
600 -AT+PRO  : Choose agreement
580 +AT+PRO  : Choose agreement
601 601  
602 -AT+RXDL  : Extend the sending and receiving time
582 +AT+RXDL  : Extend the sending and receiving time
603 603  
604 -AT+SERVADDR  : Server Address
584 +AT+SERVADDR  : Server Address
605 605  
606 606  AT+TR      :  Get or Set record time
607 607  
... ... @@ -609,7 +609,7 @@
609 609  
610 610  AT+CDP     :  Read or Clear cached data
611 611  
612 -AT+DEBUG:  Enable or Disable debug mode
592 +AT+DEBUG:  Enable or Disable debug mode
613 613  
614 614  AT+ALARM1:  Get or Set alarm of distance1
615 615  
... ... @@ -676,10 +676,16 @@
676 676  In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER** (%%)while press the send key, user need to add ENTER in their string.
677 677  
678 678  
659 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
660 +
661 +
662 +This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**.
663 +
664 +
679 679  = 7. ​ Order Info =
680 680  
681 681  
682 -Part Number:**(% style="color:blue" %) NMDS200**
668 +Part Number:(% style="color:blue" %)** NMDS200**
683 683  
684 684  
685 685  = 8.  Packing Info =
1670471530120-960.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +67.6 KB
Content
1670471559211-638.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +170.6 KB
Content
1670471584490-640.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +91.1 KB
Content
1670471613823-833.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +181.0 KB
Content
image-20221209090938-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +121.9 KB
Content
image-20221212171610-1.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +756.0 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0