Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 80.1 >
edited by Xiaoling
on 2022/12/07 17:44
To version < 90.3 >
edited by Xiaoling
on 2022/12/13 11: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,25 +15,37 @@
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  
19 -
35 +(((
20 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.
37 +)))
21 21  
39 +(((
22 22  NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
41 +)))
23 23  
43 +(((
24 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.
45 +)))
25 25  
47 +(((
26 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.
49 +)))
27 27  
51 +(((
28 28  NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
53 +)))
29 29  
55 +(((
30 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)
57 +)))
31 31  
59 +(((
32 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.
33 33  )))
34 34  
35 35  
36 -
37 37  == ​1.2  Features ==
38 38  
39 39  
... ... @@ -57,9 +57,9 @@
57 57  
58 58  
59 59  * Measuring Method: FMCW
60 -* Frequency: 24.000 24.500 GHz
87 +* Frequency: 24.000 ~~ 24.500 GHz
61 61  * Measurement output power: 6dBm
62 -* Measure range: 0.5 20m
89 +* Measure range: 0.5 ~~ 20m
63 63  * Accuracy: ±0.1m
64 64  * Resolution: 0.01m
65 65  * Horizontal Angel: 78°
... ... @@ -67,7 +67,6 @@
67 67  
68 68  
69 69  
70 -
71 71  == 1.4  Storage Temperature ==
72 72  
73 73  
... ... @@ -74,13 +74,9 @@
74 74   -40°C to +85°C
75 75  
76 76  
77 -
78 -
79 -
80 80  == 1.5 ​ Applications ==
81 81  
82 82  
83 -
84 84  * Horizontal distance measurement
85 85  * Liquid level measurement
86 86  * Parking management system
... ... @@ -118,10 +118,12 @@
118 118  Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
119 119  
120 120  
121 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
143 +[[image:image-20221207170748-1.png]]
122 122  
123 123  
146 + [[image:image-20221207170748-2.png||height="345" width="634"]]
124 124  
148 +
125 125  == 1.8  Pin Definitions and Switch ==
126 126  
127 127  
... ... @@ -137,7 +137,7 @@
137 137  
138 138  The diagram below shows the working flow in the default firmware of NMDS200:
139 139  
140 -[[image:image-20221021110615-5.png]]
164 +[[image:image-20221021110615-5.png||height="996" width="492"]]
141 141  
142 142  
143 143  == 2.2 ​ Configure NMDS200 ==
... ... @@ -151,7 +151,7 @@
151 151  
152 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.
153 153  
154 -[[image:image-20221207173300-4.png]]
178 +[[image:image-20221209090938-1.png]]
155 155  
156 156  
157 157  === 2.2.1 Insert NB-IoT SIM card ===
... ... @@ -200,7 +200,6 @@
200 200  (% 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]]
201 201  
202 202  
203 -
204 204  === 2.2.3 Use CoAP protocol to uplink data ===
205 205  
206 206  
... ... @@ -207,7 +207,7 @@
207 207  (% 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/]]
208 208  
209 209  
210 -(% style="color:blue" %)**Use below commands in NDS03A:**
233 +(% style="color:blue" %)**Use below commands in NMDS200:**
211 211  
212 212  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
213 213  
... ... @@ -217,7 +217,7 @@
217 217  
218 218  For parameter description, please refer to AT command set
219 219  
220 -[[image:image-20221021110948-8.png]]
243 +[[image:1670471530120-960.png||height="647" width="674"]]
221 221  
222 222  
223 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.
... ... @@ -236,7 +236,7 @@
236 236  
237 237  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
238 238  
239 -​ [[image:image-20221021111025-10.png]]
262 +​ [[image:1670471559211-638.png]]
240 240  
241 241  
242 242  [[image:image-20221021111033-11.png||height="241" width="576"]]
... ... @@ -262,7 +262,7 @@
262 262  
263 263  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
264 264  
265 -​ [[image:image-20221118103445-7.png]]
288 +​ [[image:1670471584490-640.png]]
266 266  
267 267  
268 268  [[image:1670405928926-116.png]]
... ... @@ -281,7 +281,7 @@
281 281  
282 282  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
283 283  
284 -​ [[image:1670406036256-101.png||height="676" width="713"]]
307 +​ [[image:1670471613823-833.png]]
285 285  
286 286  
287 287  [[image:image-20221021111131-15.png]]
... ... @@ -303,70 +303,52 @@
303 303  == 2.3  Uplink Payload ==
304 304  
305 305  
306 -The uplink payload includes 26 bytes in total by default.
329 +The uplink payload includes 23 bytes in total by default.
307 307  
308 308  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.
309 309  
310 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
311 311  
312 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
313 -|=(% 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:60px" %)**1**|(% style="width:90px" %)**3**|(% style="width:100px" %)**3**
314 -|=(% 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" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
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**
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"]]
315 315  
316 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
317 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
338 +(% border="1" style="background-color:#ffffcc; color:green; width:429px" %)
339 +|(% style="width:60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)(((
318 318  **1-32 group**
319 319  )))
320 -|(% 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" %)...
342 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)...
321 321  
322 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
344 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
323 323  
346 +[[image:1670406261143-723.png]]
324 324  
325 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
326 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:45px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:60px" %)**1**|(% style="width:60px" %)**1**|(% style="width:87px" %)**3**|(% style="width:80px" %)**3**
327 -|=(% style="width: 96px;" %)**Value**|(% style="width:66px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:70px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:55px" %)Door Status(pb14)|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb14)|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
328 328  
329 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
330 -|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:75px" %)**1**|(% style="width:75px" %)**3**
331 -|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
349 +The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
332 332  
333 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
334 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
335 -**1-32 group**
336 -)))
337 -|(% 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" %)......
351 +**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__(%%)**
338 338  
339 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
340 -
341 -[[image:image-20221117145932-2.png]]
342 -
343 -
344 -The payload is ASCII string, representative same HEX:
345 -
346 -**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0ccf__(% style="color:#00b0f0" %) __19__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__(% style="color:#660066" %) (% style="color:#aaaa40" %)__000016__(% style="color:#663300" %) __000017__ (% style="color:#d60093" %)__637590df__(%%)**
347 -
348 348  **where:**
349 349  
350 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
355 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
351 351  
352 352  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
353 353  
354 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
359 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
355 355  
356 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
361 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
357 357  
358 358  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
359 359  
360 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
365 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
361 361  
362 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
367 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
363 363  
364 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
369 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
365 365  
366 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
371 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
367 367  
368 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
369 369  
374 +
370 370  == 2.4  Payload Explanation and Sensor Interface ==
371 371  
372 372  === 2.4.1  Device ID ===
... ... @@ -388,13 +388,13 @@
388 388  
389 389  Specify the software version: 0x64=100, which means firmware version 1.00.
390 390  
391 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
396 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
392 392  
393 393  
394 394  === 2.4.3  Battery Info ===
395 395  
396 396  
397 -Check the battery voltage for NDS03A.
402 +Check the battery voltage for NMDS200.
398 398  
399 399  Ex1: 0x0B45 = 2885mV
400 400  
... ... @@ -406,51 +406,49 @@
406 406  
407 407  NB-IoT Network signal Strength.
408 408  
409 -**Ex1: 0x1d = 29**
414 +(% style="color:blue" %)**Ex1: 0x1d = 29**
410 410  
411 -**0**  -113dBm or less
416 +(% style="color:#037691" %)**0** (%%) -113dBm or less
412 412  
413 -**1**  -111dBm
418 +(% style="color:#037691" %)**1**  (%%) -111dBm
414 414  
415 -**2...30** -109dBm... -53dBm
420 +(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
416 416  
417 -**31**   -51dBm or greater
422 +(% style="color:#037691" %)**31** (%%) -51dBm or greater
418 418  
419 -**99**    Not known or not detectable
424 +(% style="color:#037691" %)**99** (%%) Not known or not detectable
420 420  
421 421  
422 -=== 2.4.5  Disalarm: (default: 0) ===
427 +=== 2.4.5  Distance ===
423 423  
424 424  
425 -(% style="color:blue" %)**If Disalarm = 1**(%%), NDS03A will only send uplink at every TDC periodically. This is normally use for pulse meter application, in this application, there are many open/close event, and platform only care about the total number of pulse.
430 +[[image:1670407401682-959.png]]
426 426  
427 -(% style="color:blue" %)**If Disalarm = 0**(%%), NDS03A will send uplink at every TDC periodically and send data on each open/close event. This is useful for the application user need to monitor the open/close event in real-time.
428 428  
429 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
433 +(% style="color:blue" %)**Object1 Distance:**
430 430  
435 +Distance between sensor probe to the first object. (unit: cm)
431 431  
432 -=== 2.4.6  Keep Status & Keep Time ===
437 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
433 433  
439 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
434 434  
435 -Shows the configure value of Alarm Base on Timeout Feature
436 436  
442 +(% style="color:blue" %)**Object2 Distance:**
437 437  
438 -=== 2.4.7  Timestamp ===
444 +Distance between sensor probe to the second object. (unit: cm)
439 439  
440 440  
441 -Timestamp : 0x6315537b =1662342011
447 +=== 2.4.6  Timestamp ===
442 442  
443 443  
444 -=== 2.4.8  Switch Dual Channel Mode ===
450 +Timestamp : 0x6315537b =1662342011
445 445  
446 446  
447 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
448 -
449 -
450 450  == 2.5  Downlink Payload ==
451 451  
452 452  
453 -By default, NDS03A prints the downlink payload to console port.
456 +By default, NMDS200 prints the downlink payload to console port.
454 454  
455 455  [[image:image-20221021111414-18.png]] ​
456 456  
... ... @@ -467,7 +467,7 @@
467 467  
468 468  * (% style="color:#037691" %)**Reset**
469 469  
470 -If payload = 0x04FF, it will reset the NDS03A
473 +If payload = 0x04FF, it will reset the NMDS200
471 471  
472 472  * (% style="color:#037691" %)**INTMOD**
473 473  
... ... @@ -477,112 +477,34 @@
477 477  == 2.6  ​LED Indicator ==
478 478  
479 479  
480 -The NDS03A has an internal LED which is to show the status of different states.
483 +The NMDS200 has an internal LED which is to show the status of different states.
481 481  
482 482  * When the device starts normally, the LED will light up for 1 second.
483 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
486 +* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
484 484  * For each uplink probe, LED will be on for 500ms.
485 485  
486 -== 2.7  Alarm Base on Timeout ==
487 487  
488 488  
489 -NDS03A can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are:
491 +== 2.7  Distance alarm function ==
490 490  
491 491  
492 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
494 +(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
493 493  
494 -Keep Status = 1: Monitor Close to Open event
496 +(% style="color:#037691" %)**Example 1:**
495 495  
496 -Keep Status = 0: Monitor Open to Close event
498 +AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
497 497  
500 +AT+ ALARM2 =min,max
498 498  
499 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
500 500  
501 -Range 0 ~~ 65535(0xFFFF) seconds.
503 +(% style="color:#037691" %)**Example 2:**
502 502  
503 -If keep time = 0, Disable Alarm Base on Timeout feature.
505 +AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
504 504  
505 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
506 506  
508 +== 2.8  Set the number of data to be uploaded and the recording time ==
507 507  
508 -(% style="color:blue" %)**AT Command to configure:**
509 509  
510 -(% style="color:blue" %)**PB14 PIN:**
511 -
512 -(% style="color:#037691" %)**AT+TTRIG=1,30** (%%) **~-~->**  When the **Keep Status** change from connected to disconnect, and device remains in disconnect status for more than 30 seconds. NDS03A will send an uplink packet, the [[Alarm bit>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.
513 -
514 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
515 -
516 -
517 -(% style="color:blue" %)**PB15 PIN:**
518 -
519 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
520 -
521 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
522 -
523 -
524 -== 2.8  Set debug mode ==
525 -
526 -
527 -Feature: Enable or Disable debug mode
528 -
529 -(% style="color:blue" %)**AT Command: AT+DEBUG**
530 -
531 -[[image:image-20221021111629-21.png]]
532 -
533 -
534 -
535 -== 2.9  Clear Flash Record ==
536 -
537 -
538 -Feature: Clear flash storage for data log feature.
539 -
540 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
541 -
542 -[[image:image-20221021111527-19.png]]
543 -
544 -
545 -== 2.10  Count Mod ==
546 -
547 -
548 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
549 -
550 -[[image:image-20221118092935-1.png]]
551 -
552 -
553 -== 2.11  Interrupt Pin Channel Mod ==
554 -
555 -
556 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
557 -
558 -[[image:image-20221118093144-2.png]]
559 -
560 -
561 -== 2.12 TTRIG1/2 timeout status alarm ==
562 -
563 -
564 -It needs to be used with AT+TTRIG1 or AT+TTRIG2. When TTRIG1 or TTRIG2 times out and causes an alarm, and the status does not change subsequently, an alarm packet will be sent at the alarm interval.
565 -
566 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
567 -
568 -[[image:image-20221118093512-3.png]]
569 -
570 -
571 -== 2.13  Select counting mode ==
572 -
573 -
574 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
575 -
576 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
577 -
578 -When (% style="color:red" %)**b=0**(%%), it is the last door open duration, and when (% style="color:red" %)**b=1**(%%),the last door close duration.
579 -
580 -[[image:image-20221118093658-4.png]]
581 -
582 -
583 -== 2.14  Set the number of data to be uploaded and the recording time ==
584 -
585 -
586 586  (% style="color:blue" %)**AT Command:**
587 587  
588 588  (% 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)
... ... @@ -590,7 +590,7 @@
590 590  (% 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.
591 591  
592 592  
593 -== 2.15  Read or Clear cached data ==
518 +== 2.9  Read or Clear cached data ==
594 594  
595 595  
596 596  (% style="color:blue" %)**AT Command:**
... ... @@ -599,23 +599,23 @@
599 599  
600 600  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
601 601  
602 -[[image:image-20221118094227-5.png]]
527 +[[image:1670408172929-569.png]]
603 603  
604 604  
605 -== 2.16  ​Firmware Change Log ==
530 +== 2.10  ​Firmware Change Log ==
606 606  
607 607  
608 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
533 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0>>https://www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0]]
609 609  
610 610  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
611 611  
612 612  
613 -== 2.17  ​Battery Analysis ==
538 +== 2.11  ​Battery Analysis ==
614 614  
615 -=== 2.17.1  ​Battery Type ===
540 +=== 2.11.1  ​Battery Type ===
616 616  
617 617  
618 -The NDS03A 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.
543 +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.
619 619  
620 620  The battery is designed to last for several years depends on the actual use environment and update interval. 
621 621  
... ... @@ -630,7 +630,7 @@
630 630  [[image:image-20221021111911-26.png]] ​
631 631  
632 632  
633 -=== 2.17.2  Power consumption Analyze ===
558 +=== 2.11.2  Power consumption Analyze ===
634 634  
635 635  
636 636  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.
... ... @@ -652,16 +652,16 @@
652 652  [[image:1666596205057-567.png]] ​
653 653  
654 654  
655 -=== 2.17.3  ​Battery Note ===
580 +=== 2.11.3  ​Battery Note ===
656 656  
657 657  
658 658  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.
659 659  
660 660  
661 -=== 2.17.4  Replace the battery ===
586 +=== 2.11.4  Replace the battery ===
662 662  
663 663  
664 -The default battery pack of NDS03A 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).
589 +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).
665 665  
666 666  
667 667  = 3. ​ Access NB-IoT Module =
... ... @@ -707,65 +707,59 @@
707 707  
708 708  AT+INTMOD            : Set the trigger interrupt mode
709 709  
710 -AT+5VT  : Set extend the time of 5V power  
635 +AT+5VT  : Set extend the time of 5V power  
711 711  
712 -AT+PRO  : Choose agreement
637 +AT+PRO  : Choose agreement
713 713  
714 -AT+RXDL  : Extend the sending and receiving time
639 +AT+RXDL  : Extend the sending and receiving time
715 715  
716 -AT+SERVADDR  : Server Address
641 +AT+SERVADDR  : Server Address
717 717  
718 -AT+TR      :  Get or Set record time
643 +AT+TR      :  Get or Set record time
719 719  
720 -AT+NOUD      : Get or Set the number of data to be uploaded
645 +AT+NOUD :  Get or Set the number of data to be uploaded
721 721  
722 722  AT+CDP     :  Read or Clear cached data
723 723  
724 -AT+ DEBUG   : Enable or Disable debug mode
649 +AT+DEBUG:  Enable or Disable debug mode
725 725  
726 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
651 +AT+ALARM1:  Get or Set alarm of distance1
727 727  
728 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
653 +AT+ALARM2:  Get or Set alarm of distance2
729 729  
730 -AT+COUNTMOD  :  Get or Set the count mode
655 +AT+GETSENSORVALUE :  Returns the current sensor measurement
731 731  
732 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
657 +AT+POWERIC :  Get or set the Power IC flag
733 733  
734 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
735 735  
736 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
737 -
738 -AT+ CLRC   :  Clear current door open count
739 -
740 -
741 741  (% style="color:blue" %)**COAP Management**      
742 742  
743 -AT+URI            : Resource parameters
662 +AT+URI :  Resource parameters
744 744  
745 745  
746 746  (% style="color:blue" %)**UDP Management**
747 747  
748 -AT+CFM          : Upload confirmation mode (only valid for UDP)
667 +AT+CFM :  Upload confirmation mode (only valid for UDP)
749 749  
750 750  
751 751  (% style="color:blue" %)**MQTT Management**
752 752  
753 -AT+CLIENT               : Get or Set MQTT client
672 +AT+CLIENT  : Get or Set MQTT client
754 754  
755 -AT+UNAME  : Get or Set MQTT Username
674 +AT+UNAME : Get or Set MQTT Username
756 756  
757 -AT+PWD                  : Get or Set MQTT password
676 +AT+PWD  :  Get or Set MQTT password
758 758  
759 -AT+PUBTOPIC  : Get or Set MQTT publish topic
678 +AT+PUBTOPIC :  Get or Set MQTT publish topic
760 760  
761 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
680 +AT+SUBTOPIC :  Get or Set MQTT subscription topic
762 762  
763 763  
764 764  (% style="color:blue" %)**Information**          
765 765  
766 -AT+FDR  : Factory Data Reset
685 +AT+FDR :  Factory Data Reset
767 767  
768 -AT+PWORD  : Serial Access Password
687 +AT+PWORD :  Serial Access Password
769 769  
770 770  
771 771  = ​5.  FAQ =
... ... @@ -777,7 +777,7 @@
777 777  
778 778  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]]
779 779  
780 -(% 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.**
699 +(% 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.**
781 781  
782 782  
783 783  = 6.  Trouble Shooting =
... ... @@ -797,7 +797,7 @@
797 797  = 7. ​ Order Info =
798 798  
799 799  
800 -Part Number**:** NDS03A
719 +Part Number:(% style="color:blue" %)** NMDS200**
801 801  
802 802  
803 803  = 8.  Packing Info =
... ... @@ -805,8 +805,10 @@
805 805  
806 806  (% style="color:blue" %)**Package Includes**:
807 807  
808 -* NDS03A Open/Close Door Sensor x 1
727 +* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
809 809  
729 +
730 +
810 810  = 9.  Support =
811 811  
812 812  
1670407401682-959.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +23.7 KB
Content
1670408172929-569.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +211.8 KB
Content
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-20221208090742-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +79.7 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

Applications

Navigation

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