<
From version < 90.11 >
edited by Xiaoling
on 2023/05/26 10:12
To version < 83.7 >
edited by Xiaoling
on 2022/12/08 11:20
>
Change comment: There is no comment for this version

Summary

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  
... ... @@ -82,9 +82,9 @@
82 82  
83 83  
84 84  * Measuring Method: FMCW
85 -* Frequency: 24.000 ~~ 24.500 GHz
57 +* Frequency: 24.000 24.500 GHz
86 86  * Measurement output power: 6dBm
87 -* Measure range: 0.5 ~~ 20m
59 +* Measure range: 0.5 20m
88 88  * Accuracy: ±0.1m
89 89  * Resolution: 0.01m
90 90  * Horizontal Angel: 78°
... ... @@ -132,12 +132,10 @@
132 132  Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
133 133  
134 134  
135 -[[image:image-20221207170748-1.png]]
107 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
136 136  
137 137  
138 - [[image:image-20221207170748-2.png||height="345" width="634"]]
139 139  
140 -
141 141  == 1.8  Pin Definitions and Switch ==
142 142  
143 143  
... ... @@ -153,7 +153,7 @@
153 153  
154 154  The diagram below shows the working flow in the default firmware of NMDS200:
155 155  
156 -[[image:image-20221021110615-5.png||height="996" width="492"]]
126 +[[image:image-20221021110615-5.png]]
157 157  
158 158  
159 159  == 2.2 ​ Configure NMDS200 ==
... ... @@ -167,7 +167,7 @@
167 167  
168 168  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.
169 169  
170 -[[image:image-20221209090938-1.png]]
140 +[[image:image-20221208090742-1.png]]
171 171  
172 172  
173 173  === 2.2.1 Insert NB-IoT SIM card ===
... ... @@ -216,6 +216,7 @@
216 216  (% 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]]
217 217  
218 218  
189 +
219 219  === 2.2.3 Use CoAP protocol to uplink data ===
220 220  
221 221  
... ... @@ -232,7 +232,7 @@
232 232  
233 233  For parameter description, please refer to AT command set
234 234  
235 -[[image:1670471530120-960.png||height="647" width="674"]]
206 +[[image:image-20221021110948-8.png]]
236 236  
237 237  
238 238  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.
... ... @@ -251,7 +251,7 @@
251 251  
252 252  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
253 253  
254 -​ [[image:1670471559211-638.png]]
225 +​ [[image:image-20221021111025-10.png]]
255 255  
256 256  
257 257  [[image:image-20221021111033-11.png||height="241" width="576"]]
... ... @@ -277,7 +277,7 @@
277 277  
278 278  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
279 279  
280 -​ [[image:1670471584490-640.png]]
251 +​ [[image:image-20221118103445-7.png]]
281 281  
282 282  
283 283  [[image:1670405928926-116.png]]
... ... @@ -296,7 +296,7 @@
296 296  
297 297  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
298 298  
299 -​ [[image:1670471613823-833.png]]
270 +​ [[image:1670406036256-101.png||height="676" width="713"]]
300 300  
301 301  
302 302  [[image:image-20221021111131-15.png]]
... ... @@ -323,15 +323,15 @@
323 323  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.
324 324  
325 325  
326 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:450px" %)
327 -|=(% 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**
328 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"]]
329 329  
330 -(% border="1" style="background-color:#ffffcc; color:green; width:429px" %)
331 -|(% 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" %)(((
332 332  **1-32 group**
333 333  )))
334 -|(% 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" %)...
335 335  
336 336  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
337 337  
... ... @@ -338,8 +338,10 @@
338 338  [[image:1670406261143-723.png]]
339 339  
340 340  
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 +The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
342 342  
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 +
343 343  **where:**
344 344  
345 345  * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
... ... @@ -381,7 +381,7 @@
381 381  
382 382  Specify the software version: 0x64=100, which means firmware version 1.00.
383 383  
384 -For example 0x00 64 : This device is NMDS200 with firmware version 1.0.0.
357 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
385 385  
386 386  
387 387  === 2.4.3  Battery Info ===
... ... @@ -443,12 +443,6 @@
443 443  
444 444  By default, NMDS200 prints the downlink payload to console port.
445 445  
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
451 -
452 452  [[image:image-20221021111414-18.png]] ​
453 453  
454 454  
... ... @@ -480,6 +480,7 @@
480 480  * After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
481 481  * For each uplink probe, LED will be on for 500ms.
482 482  
450 +
483 483  == 2.7  Distance alarm function ==
484 484  
485 485  
... ... @@ -487,7 +487,7 @@
487 487  
488 488  (% style="color:#037691" %)**Example 1:**
489 489  
490 -AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
458 +AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
491 491  
492 492  AT+ ALARM2 =min,max
493 493  
... ... @@ -494,7 +494,7 @@
494 494  
495 495  (% style="color:#037691" %)**Example 2:**
496 496  
497 -AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
465 +AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
498 498  
499 499  
500 500  == 2.8  Set the number of data to be uploaded and the recording time ==
... ... @@ -522,19 +522,65 @@
522 522  == 2.10  ​Firmware Change Log ==
523 523  
524 524  
525 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8elvp2qi9bcv47a/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]]
526 526  
527 527  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
528 528  
529 529  
530 -== 2.11 Battery & Power Consumption ==
498 +== 2.11  Battery Analysis ==
531 531  
500 +=== 2.11.1  ​Battery Type ===
532 532  
533 -NMDS200 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
534 534  
535 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
503 +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.
536 536  
505 +The battery is designed to last for several years depends on the actual use environment and update interval. 
537 537  
507 +The battery-related documents as below:
508 +
509 +* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
510 +
511 +* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
512 +
513 +* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
514 +
515 +[[image:image-20221021111911-26.png]] ​
516 +
517 +
518 +=== 2.11.2  Power consumption Analyze ===
519 +
520 +
521 +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.
522 +
523 +Instruction to use as below:
524 +
525 +(% 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/]]
526 +
527 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
528 +
529 +* Product Model
530 +
531 +* Uplink Interval
532 +
533 +* Working Mode
534 +
535 +And the Life expectation in difference case will be shown on the right.
536 +
537 +[[image:1666596205057-567.png]] ​
538 +
539 +
540 +=== 2.11.3  ​Battery Note ===
541 +
542 +
543 +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.
544 +
545 +
546 +=== 2.11.4  Replace the battery ===
547 +
548 +
549 +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).
550 +
551 +
538 538  = 3. ​ Access NB-IoT Module =
539 539  
540 540  
... ... @@ -578,13 +578,13 @@
578 578  
579 579  AT+INTMOD            : Set the trigger interrupt mode
580 580  
581 -AT+5VT  : Set extend the time of 5V power  
595 +AT+5VT  : Set extend the time of 5V power  
582 582  
583 -AT+PRO  : Choose agreement
597 +AT+PRO  : Choose agreement
584 584  
585 -AT+RXDL  : Extend the sending and receiving time
599 +AT+RXDL  : Extend the sending and receiving time
586 586  
587 -AT+SERVADDR  : Server Address
601 +AT+SERVADDR  : Server Address
588 588  
589 589  AT+TR      :  Get or Set record time
590 590  
... ... @@ -592,7 +592,7 @@
592 592  
593 593  AT+CDP     :  Read or Clear cached data
594 594  
595 -AT+DEBUG:  Enable or Disable debug mode
609 +AT+DEBUG:  Enable or Disable debug mode
596 596  
597 597  AT+ALARM1:  Get or Set alarm of distance1
598 598  
... ... @@ -659,12 +659,6 @@
659 659  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.
660 660  
661 661  
662 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
663 -
664 -
665 -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]]//**.
666 -
667 -
668 668  = 7. ​ Order Info =
669 669  
670 670  
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
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0