Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 91.1 >
edited by Ellie Zhang
on 2023/08/14 16:31
To version < 82.2 >
edited by Xiaoling
on 2022/12/07 18:18
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Ellie
1 +XWiki.Xiaoling
Content
... ... @@ -1,28 +1,13 @@
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 -{{toc/}}
17 17  
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,37 +30,25 @@
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 -(((
19 +
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  
63 63  
36 +
64 64  == ​1.2  Features ==
65 65  
66 66  
... ... @@ -78,14 +78,13 @@
78 78  * Micro SIM card slot for NB-IoT SIM
79 79  * 8500mAh Battery for long-term use
80 80  
81 -
82 82  == 1.3 Radar probe specification ==
83 83  
84 84  
85 85  * Measuring Method: FMCW
86 -* Frequency: 24.000 ~~ 24.500 GHz
58 +* Frequency: 24.000 24.500 GHz
87 87  * Measurement output power: 6dBm
88 -* Measure range: 0.5 ~~ 20m
60 +* Measure range: 0.5 20m
89 89  * Accuracy: ±0.1m
90 90  * Resolution: 0.01m
91 91  * Horizontal Angel: 78°
... ... @@ -98,9 +98,13 @@
98 98   -40°C to +85°C
99 99  
100 100  
73 +
74 +
75 +
101 101  == 1.5 ​ Applications ==
102 102  
103 103  
79 +
104 104  * Horizontal distance measurement
105 105  * Liquid level measurement
106 106  * Parking management system
... ... @@ -111,7 +111,6 @@
111 111  * Sewer
112 112  * Bottom water level monitoring
113 113  
114 -
115 115  == 1.6  Specification ==
116 116  
117 117  
... ... @@ -129,7 +129,6 @@
129 129  * B20 @H-FDD: 800MHz
130 130  * B28 @H-FDD: 700MHz
131 131  
132 -
133 133  == 1.7  Installation ==
134 134  
135 135  
... ... @@ -136,12 +136,10 @@
136 136  Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
137 137  
138 138  
139 -[[image:image-20221207170748-1.png]]
113 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
140 140  
141 141  
142 - [[image:image-20221207170748-2.png||height="345" width="634"]]
143 143  
144 -
145 145  == 1.8  Pin Definitions and Switch ==
146 146  
147 147  
... ... @@ -157,7 +157,7 @@
157 157  
158 158  The diagram below shows the working flow in the default firmware of NMDS200:
159 159  
160 -[[image:image-20221021110615-5.png||height="996" width="492"]]
132 +[[image:image-20221021110615-5.png]]
161 161  
162 162  
163 163  == 2.2 ​ Configure NMDS200 ==
... ... @@ -171,7 +171,7 @@
171 171  
172 172  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.
173 173  
174 -[[image:image-20221209090938-1.png]]
146 +[[image:image-20221207173300-4.png]]
175 175  
176 176  
177 177  === 2.2.1 Insert NB-IoT SIM card ===
... ... @@ -220,6 +220,7 @@
220 220  (% 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]]
221 221  
222 222  
195 +
223 223  === 2.2.3 Use CoAP protocol to uplink data ===
224 224  
225 225  
... ... @@ -226,7 +226,7 @@
226 226  (% 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/]]
227 227  
228 228  
229 -(% style="color:blue" %)**Use below commands in NMDS200:**
202 +(% style="color:blue" %)**Use below commands in NDS03A:**
230 230  
231 231  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
232 232  
... ... @@ -236,7 +236,7 @@
236 236  
237 237  For parameter description, please refer to AT command set
238 238  
239 -[[image:1670471530120-960.png||height="647" width="674"]]
212 +[[image:image-20221021110948-8.png]]
240 240  
241 241  
242 242  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.
... ... @@ -255,7 +255,7 @@
255 255  
256 256  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
257 257  
258 -​ [[image:1670471559211-638.png]]
231 +​ [[image:image-20221021111025-10.png]]
259 259  
260 260  
261 261  [[image:image-20221021111033-11.png||height="241" width="576"]]
... ... @@ -281,7 +281,7 @@
281 281  
282 282  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
283 283  
284 -​ [[image:1670471584490-640.png]]
257 +​ [[image:image-20221118103445-7.png]]
285 285  
286 286  
287 287  [[image:1670405928926-116.png]]
... ... @@ -300,7 +300,7 @@
300 300  
301 301  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
302 302  
303 -​ [[image:1670471613823-833.png]]
276 +​ [[image:1670406036256-101.png||height="676" width="713"]]
304 304  
305 305  
306 306  [[image:image-20221021111131-15.png]]
... ... @@ -327,15 +327,15 @@
327 327  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.
328 328  
329 329  
330 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %)
331 -|(% 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:31px" %)**2**|(% style="background-color:#4f81bd; color:white; width:31px" %)**2**|(% style="background-color:#4f81bd; color:white; width:75px" %)**1**|(% style="background-color:#4f81bd; color:white; width:31px" %)**1**|(% style="background-color:#4f81bd; color:white; width:51px" %)**1**|(% style="background-color:#4f81bd; color:white; width:61px" %)**2**|(% style="background-color:#4f81bd; color:white; width:60px" %)**2**
332 -|(% 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"]]
303 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
304 +|=(% 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**
305 +|=(% 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
333 333  
334 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:430px" %)
335 -|(% 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" %)(((
307 +(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
308 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
336 336  **1-32 group**
337 337  )))
338 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)...
311 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
339 339  
340 340  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
341 341  
... ... @@ -342,8 +342,10 @@
342 342  [[image:1670406261143-723.png]]
343 343  
344 344  
345 -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__(%%)**
318 +The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
346 346  
320 +**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__(%%)**
321 +
347 347  **where:**
348 348  
349 349  * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
... ... @@ -386,7 +386,7 @@
386 386  
387 387  Specify the software version: 0x64=100, which means firmware version 1.00.
388 388  
389 -For example 0x00 64 : This device is NMDS200 with firmware version 1.0.0.
364 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
390 390  
391 391  
392 392  === 2.4.3  Battery Info ===
... ... @@ -404,17 +404,17 @@
404 404  
405 405  NB-IoT Network signal Strength.
406 406  
407 -(% style="color:blue" %)**Ex1: 0x1d = 29**
382 +**Ex1: 0x1d = 29**
408 408  
409 -(% style="color:#037691" %)**0** (%%) -113dBm or less
384 +**0**  -113dBm or less
410 410  
411 -(% style="color:#037691" %)**1**  (%%) -111dBm
386 +**1**  -111dBm
412 412  
413 -(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
388 +**2...30** -109dBm... -53dBm
414 414  
415 -(% style="color:#037691" %)**31** (%%) -51dBm or greater
390 +**31**   -51dBm or greater
416 416  
417 -(% style="color:#037691" %)**99** (%%) Not known or not detectable
392 +**99**    Not known or not detectable
418 418  
419 419  
420 420  === 2.4.5  Distance ===
... ... @@ -422,7 +422,6 @@
422 422  
423 423  [[image:1670407401682-959.png]]
424 424  
425 -
426 426  (% style="color:blue" %)**Object1 Distance:**
427 427  
428 428  Distance between sensor probe to the first object. (unit: cm)
... ... @@ -448,12 +448,9 @@
448 448  
449 449  By default, NMDS200 prints the downlink payload to console port.
450 450  
451 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %)
452 -|(% style="background-color:#4f81bd; color:white" %)**Downlink Control Type**|(% style="background-color:#4f81bd; color:white" %)**FPort**|(% style="background-color:#4f81bd; color:white; width:97px" %)**Type Code**|(% style="background-color:#4f81bd; color:white; width:183px" %)**Downlink payload size(bytes)**
453 -|TDC (Transmit Time Interval)|Any|(% style="width:97px" %)01|(% style="width:183px" %)4
454 -|RESET|Any|(% style="width:97px" %)04|(% style="width:183px" %)2
455 -|INTMOD|Any|(% style="width:97px" %)06|(% style="width:183px" %)4
425 +[[image:image-20221021111414-18.png]] ​
456 456  
427 +
457 457  **Examples:**
458 458  
459 459  * (% style="color:#037691" %)**Set TDC**
... ... @@ -479,25 +479,26 @@
479 479  The NMDS200 has an internal LED which is to show the status of different states.
480 480  
481 481  * When the device starts normally, the LED will light up for 1 second.
482 -* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
453 +* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
483 483  * For each uplink probe, LED will be on for 500ms.
484 484  
485 485  
457 +
486 486  == 2.7  Distance alarm function ==
487 487  
488 488  
489 489  (% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
490 490  
491 -(% style="color:#037691" %)**Example 1:**
463 +**Example 1:**
492 492  
493 -AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
465 +AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
494 494  
495 495  AT+ ALARM2 =min,max
496 496  
497 497  
498 -(% style="color:#037691" %)**Example 2:**
470 +**Example 2:**
499 499  
500 -AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
472 +AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
501 501  
502 502  
503 503  == 2.8  Set the number of data to be uploaded and the recording time ==
... ... @@ -505,7 +505,7 @@
505 505  
506 506  (% style="color:blue" %)**AT Command:**
507 507  
508 -(% style="color:#037691" %)**AT+TR=900**(%%)  ~/~/  The unit is seconds, and the default is to record data once every 900 seconds. **(**The minimum can be set to 180 seconds, **also the time when the alarm function sends an uplink when it detects an alarm)**
480 +(% style="color:#037691" %)**AT+TR=900**(%%)  ~/~/  The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
509 509  
510 510  (% style="color:#037691" %)**AT+NOUD=8**(%%)** ** ~/~/  The device uploads 0 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
511 511  
... ... @@ -525,19 +525,65 @@
525 525  == 2.10  ​Firmware Change Log ==
526 526  
527 527  
528 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0>>https://www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0]]
500 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
529 529  
530 530  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
531 531  
532 532  
533 -== 2.11 Battery & Power Consumption ==
505 +== 2.11  ​Battery Analysis ==
534 534  
507 +=== 2.11.1  ​Battery Type ===
535 535  
536 -NMDS200 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
537 537  
538 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
510 +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.
539 539  
512 +The battery is designed to last for several years depends on the actual use environment and update interval. 
540 540  
514 +The battery-related documents as below:
515 +
516 +* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
517 +
518 +* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
519 +
520 +* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
521 +
522 +[[image:image-20221021111911-26.png]] ​
523 +
524 +
525 +=== 2.11.2  Power consumption Analyze ===
526 +
527 +
528 +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.
529 +
530 +Instruction to use as below:
531 +
532 +(% 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/]]
533 +
534 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
535 +
536 +* Product Model
537 +
538 +* Uplink Interval
539 +
540 +* Working Mode
541 +
542 +And the Life expectation in difference case will be shown on the right.
543 +
544 +[[image:1666596205057-567.png]] ​
545 +
546 +
547 +=== 2.11.3  ​Battery Note ===
548 +
549 +
550 +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.
551 +
552 +
553 +=== 2.11.4  Replace the battery ===
554 +
555 +
556 +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).
557 +
558 +
541 541  = 3. ​ Access NB-IoT Module =
542 542  
543 543  
... ... @@ -581,59 +581,65 @@
581 581  
582 582  AT+INTMOD            : Set the trigger interrupt mode
583 583  
584 -AT+5VT  : Set extend the time of 5V power  
602 +AT+5VT  : Set extend the time of 5V power  
585 585  
586 -AT+PRO  : Choose agreement
604 +AT+PRO  : Choose agreement
587 587  
588 -AT+RXDL  : Extend the sending and receiving time
606 +AT+RXDL  : Extend the sending and receiving time
589 589  
590 -AT+SERVADDR  : Server Address
608 +AT+SERVADDR  : Server Address
591 591  
592 -AT+TR      :  Get or Set record time
610 +AT+TR      :  Get or Set record time
593 593  
594 -AT+NOUD :  Get or Set the number of data to be uploaded
612 +AT+NOUD      : Get or Set the number of data to be uploaded
595 595  
596 596  AT+CDP     :  Read or Clear cached data
597 597  
598 -AT+DEBUG:  Enable or Disable debug mode
616 +AT+ DEBUG   : Enable or Disable debug mode
599 599  
600 -AT+ALARM1:  Get or Set alarm of distance1
618 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
601 601  
602 -AT+ALARM2:  Get or Set alarm of distance2
620 +AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
603 603  
604 -AT+GETSENSORVALUE :  Returns the current sensor measurement
622 +AT+COUNTMOD  :  Get or Set the count mode
605 605  
606 -AT+POWERIC :  Get or set the Power IC flag
624 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
607 607  
626 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
608 608  
628 +AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
629 +
630 +AT+ CLRC   :  Clear current door open count
631 +
632 +
609 609  (% style="color:blue" %)**COAP Management**      
610 610  
611 -AT+URI :  Resource parameters
635 +AT+URI            : Resource parameters
612 612  
613 613  
614 614  (% style="color:blue" %)**UDP Management**
615 615  
616 -AT+CFM :  Upload confirmation mode (only valid for UDP)
640 +AT+CFM          : Upload confirmation mode (only valid for UDP)
617 617  
618 618  
619 619  (% style="color:blue" %)**MQTT Management**
620 620  
621 -AT+CLIENT  : Get or Set MQTT client
645 +AT+CLIENT               : Get or Set MQTT client
622 622  
623 -AT+UNAME : Get or Set MQTT Username
647 +AT+UNAME  : Get or Set MQTT Username
624 624  
625 -AT+PWD  :  Get or Set MQTT password
649 +AT+PWD                  : Get or Set MQTT password
626 626  
627 -AT+PUBTOPIC :  Get or Set MQTT publish topic
651 +AT+PUBTOPIC  : Get or Set MQTT publish topic
628 628  
629 -AT+SUBTOPIC :  Get or Set MQTT subscription topic
653 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
630 630  
631 631  
632 632  (% style="color:blue" %)**Information**          
633 633  
634 -AT+FDR :  Factory Data Reset
658 +AT+FDR  : Factory Data Reset
635 635  
636 -AT+PWORD :  Serial Access Password
660 +AT+PWORD  : Serial Access Password
637 637  
638 638  
639 639  = ​5.  FAQ =
... ... @@ -645,7 +645,7 @@
645 645  
646 646  Please see this link for how to upgrade:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
647 647  
648 -(% style="color:red" %)**Notice: **(% style="color:blue" %)**NMDS200** (%%)**and (% style="color:blue" %)LMDS200(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
672 +(% style="color:red" %)**Notice: **(% style="color:blue" %)**NDS03A** (%%)**and (% style="color:blue" %)LDS03A(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
649 649  
650 650  
651 651  = 6.  Trouble Shooting =
... ... @@ -662,16 +662,10 @@
662 662  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.
663 663  
664 664  
665 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
666 -
667 -
668 -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]]//**.
669 -
670 -
671 671  = 7. ​ Order Info =
672 672  
673 673  
674 -Part Number:(% style="color:blue" %)** NMDS200**
692 +Part Number**:** NDS03A
675 675  
676 676  
677 677  = 8.  Packing Info =
... ... @@ -679,9 +679,8 @@
679 679  
680 680  (% style="color:blue" %)**Package Includes**:
681 681  
682 -* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
700 +* NDS03A Open/Close Door Sensor x 1
683 683  
684 -
685 685  = 9.  Support =
686 686  
687 687  
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-20221208090742-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.7 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

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0