Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 82.1 >
edited by Xiaoling
on 2022/12/07 18:16
To version < 90.15 >
edited by Xiaoling
on 2023/05/26 10:25
>
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  
... ... @@ -55,15 +55,14 @@
55 55  
56 56  
57 57  * Measuring Method: FMCW
58 -* Frequency: 24.000 24.500 GHz
85 +* Frequency: 24.000 ~~ 24.500 GHz
59 59  * Measurement output power: 6dBm
60 -* Measure range: 0.5 20m
87 +* Measure range: 0.5 ~~ 20m
61 61  * Accuracy: ±0.1m
62 62  * Resolution: 0.01m
63 63  * Horizontal Angel: 78°
64 64  * Vertical Angel: 23°
65 65  
66 -
67 67  == 1.4  Storage Temperature ==
68 68  
69 69  
... ... @@ -70,13 +70,9 @@
70 70   -40°C to +85°C
71 71  
72 72  
73 -
74 -
75 -
76 76  == 1.5 ​ Applications ==
77 77  
78 78  
79 -
80 80  * Horizontal distance measurement
81 81  * Liquid level measurement
82 82  * Parking management system
... ... @@ -110,10 +110,12 @@
110 110  Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
111 111  
112 112  
113 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
135 +[[image:image-20221207170748-1.png]]
114 114  
115 115  
138 + [[image:image-20221207170748-2.png||height="345" width="634"]]
116 116  
140 +
117 117  == 1.8  Pin Definitions and Switch ==
118 118  
119 119  
... ... @@ -129,7 +129,7 @@
129 129  
130 130  The diagram below shows the working flow in the default firmware of NMDS200:
131 131  
132 -[[image:image-20221021110615-5.png]]
156 +[[image:image-20221021110615-5.png||height="996" width="492"]]
133 133  
134 134  
135 135  == 2.2 ​ Configure NMDS200 ==
... ... @@ -143,7 +143,7 @@
143 143  
144 144  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.
145 145  
146 -[[image:image-20221207173300-4.png]]
170 +[[image:image-20221209090938-1.png]]
147 147  
148 148  
149 149  === 2.2.1 Insert NB-IoT SIM card ===
... ... @@ -192,7 +192,6 @@
192 192  (% 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]]
193 193  
194 194  
195 -
196 196  === 2.2.3 Use CoAP protocol to uplink data ===
197 197  
198 198  
... ... @@ -199,7 +199,7 @@
199 199  (% 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/]]
200 200  
201 201  
202 -(% style="color:blue" %)**Use below commands in NDS03A:**
225 +(% style="color:blue" %)**Use below commands in NMDS200:**
203 203  
204 204  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
205 205  
... ... @@ -209,7 +209,7 @@
209 209  
210 210  For parameter description, please refer to AT command set
211 211  
212 -[[image:image-20221021110948-8.png]]
235 +[[image:1670471530120-960.png||height="647" width="674"]]
213 213  
214 214  
215 215  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.
... ... @@ -228,7 +228,7 @@
228 228  
229 229  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
230 230  
231 -​ [[image:image-20221021111025-10.png]]
254 +​ [[image:1670471559211-638.png]]
232 232  
233 233  
234 234  [[image:image-20221021111033-11.png||height="241" width="576"]]
... ... @@ -254,7 +254,7 @@
254 254  
255 255  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
256 256  
257 -​ [[image:image-20221118103445-7.png]]
280 +​ [[image:1670471584490-640.png]]
258 258  
259 259  
260 260  [[image:1670405928926-116.png]]
... ... @@ -273,7 +273,7 @@
273 273  
274 274  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
275 275  
276 -​ [[image:1670406036256-101.png||height="676" width="713"]]
299 +​ [[image:1670471613823-833.png]]
277 277  
278 278  
279 279  [[image:image-20221021111131-15.png]]
... ... @@ -300,15 +300,15 @@
300 300  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.
301 301  
302 302  
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
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"]]
306 306  
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" %)(((
330 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:429px" %)
331 +|(% style="background-color:#4f81bd; color:white; width:60px" %)**4**|(% style="background-color:#4f81bd; color:white; width:60px" %)**2**|(% style="background-color:#4f81bd; color:white; width:60px" %)**2**|(% style="background-color:#4f81bd; color:white; width:60px" %)**4**|(% style="background-color:#4f81bd; color:white; width:100px" %)(((
309 309  **1-32 group**
310 310  )))
311 -|(% 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" %)...
312 312  
313 313  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
314 314  
... ... @@ -315,10 +315,8 @@
315 315  [[image:1670406261143-723.png]]
316 316  
317 317  
318 -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__(%%)**
319 319  
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 -
322 322  **where:**
323 323  
324 324  * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
... ... @@ -339,7 +339,6 @@
339 339  
340 340  * (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
341 341  
342 -
343 343  == 2.4  Payload Explanation and Sensor Interface ==
344 344  
345 345  === 2.4.1  Device ID ===
... ... @@ -361,7 +361,7 @@
361 361  
362 362  Specify the software version: 0x64=100, which means firmware version 1.00.
363 363  
364 -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.
365 365  
366 366  
367 367  === 2.4.3  Battery Info ===
... ... @@ -379,17 +379,17 @@
379 379  
380 380  NB-IoT Network signal Strength.
381 381  
382 -**Ex1: 0x1d = 29**
402 +(% style="color:blue" %)**Ex1: 0x1d = 29**
383 383  
384 -**0**  -113dBm or less
404 +(% style="color:#037691" %)**0** (%%) -113dBm or less
385 385  
386 -**1**  -111dBm
406 +(% style="color:#037691" %)**1**  (%%) -111dBm
387 387  
388 -**2...30** -109dBm... -53dBm
408 +(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
389 389  
390 -**31**   -51dBm or greater
410 +(% style="color:#037691" %)**31** (%%) -51dBm or greater
391 391  
392 -**99**    Not known or not detectable
412 +(% style="color:#037691" %)**99** (%%) Not known or not detectable
393 393  
394 394  
395 395  === 2.4.5  Distance ===
... ... @@ -397,6 +397,7 @@
397 397  
398 398  [[image:1670407401682-959.png]]
399 399  
420 +
400 400  (% style="color:blue" %)**Object1 Distance:**
401 401  
402 402  Distance between sensor probe to the first object. (unit: cm)
... ... @@ -422,9 +422,12 @@
422 422  
423 423  By default, NMDS200 prints the downlink payload to console port.
424 424  
425 -[[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
426 426  
427 -
428 428  **Examples:**
429 429  
430 430  * (% style="color:#037691" %)**Set TDC**
... ... @@ -450,90 +450,29 @@
450 450  The NMDS200 has an internal LED which is to show the status of different states.
451 451  
452 452  * When the device starts normally, the LED will light up for 1 second.
453 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
477 +* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
454 454  * For each uplink probe, LED will be on for 500ms.
455 455  
456 -
457 -
458 458  == 2.7  Distance alarm function ==
459 459  
460 460  
461 461  (% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
462 462  
463 -**Example 1:**
485 +(% style="color:#037691" %)**Example 1:**
464 464  
465 -AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
487 +AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
466 466  
467 467  AT+ ALARM2 =min,max
468 468  
469 469  
470 -**Example 2:**
492 +(% style="color:#037691" %)**Example 2:**
471 471  
472 -AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
494 +AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
473 473  
474 474  
475 -== 2.8  Set debug mode ==
497 +== 2.8  Set the number of data to be uploaded and the recording time ==
476 476  
477 477  
478 -Feature: Enable or Disable debug mode
479 -
480 -(% style="color:blue" %)**AT Command: AT+DEBUG**
481 -
482 -[[image:image-20221021111629-21.png]]
483 -
484 -
485 -
486 -== 2.9  Clear Flash Record ==
487 -
488 -
489 -Feature: Clear flash storage for data log feature.
490 -
491 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
492 -
493 -[[image:image-20221021111527-19.png]]
494 -
495 -
496 -== 2.10  Count Mod ==
497 -
498 -
499 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
500 -
501 -[[image:image-20221118092935-1.png]]
502 -
503 -
504 -== 2.11  Interrupt Pin Channel Mod ==
505 -
506 -
507 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
508 -
509 -[[image:image-20221118093144-2.png]]
510 -
511 -
512 -== 2.12 TTRIG1/2 timeout status alarm ==
513 -
514 -
515 -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.
516 -
517 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
518 -
519 -[[image:image-20221118093512-3.png]]
520 -
521 -
522 -== 2.13  Select counting mode ==
523 -
524 -
525 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
526 -
527 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
528 -
529 -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.
530 -
531 -[[image:image-20221118093658-4.png]]
532 -
533 -
534 -== 2.14  Set the number of data to be uploaded and the recording time ==
535 -
536 -
537 537  (% style="color:blue" %)**AT Command:**
538 538  
539 539  (% 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)
... ... @@ -541,7 +541,7 @@
541 541  (% 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.
542 542  
543 543  
544 -== 2.15  Read or Clear cached data ==
507 +== 2.9  Read or Clear cached data ==
545 545  
546 546  
547 547  (% style="color:blue" %)**AT Command:**
... ... @@ -550,71 +550,25 @@
550 550  
551 551  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
552 552  
553 -[[image:image-20221118094227-5.png]]
516 +[[image:1670408172929-569.png]]
554 554  
555 555  
556 -== 2.16  ​Firmware Change Log ==
519 +== 2.10  ​Firmware Change Log ==
557 557  
558 558  
559 -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]]
560 560  
561 561  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
562 562  
563 563  
564 -== 2.17  ​Battery Analysis ==
527 +== 2.11 Battery & Power Consumption ==
565 565  
566 -=== 2.17.1  ​Battery Type ===
567 567  
530 +NMDS200 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
568 568  
569 -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.
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/]] .
570 570  
571 -The battery is designed to last for several years depends on the actual use environment and update interval. 
572 572  
573 -The battery-related documents as below:
574 -
575 -* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
576 -
577 -* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
578 -
579 -* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
580 -
581 -[[image:image-20221021111911-26.png]] ​
582 -
583 -
584 -=== 2.17.2  Power consumption Analyze ===
585 -
586 -
587 -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.
588 -
589 -Instruction to use as below:
590 -
591 -(% 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/]]
592 -
593 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
594 -
595 -* Product Model
596 -
597 -* Uplink Interval
598 -
599 -* Working Mode
600 -
601 -And the Life expectation in difference case will be shown on the right.
602 -
603 -[[image:1666596205057-567.png]] ​
604 -
605 -
606 -=== 2.17.3  ​Battery Note ===
607 -
608 -
609 -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.
610 -
611 -
612 -=== 2.17.4  Replace the battery ===
613 -
614 -
615 -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).
616 -
617 -
618 618  = 3. ​ Access NB-IoT Module =
619 619  
620 620  
... ... @@ -658,65 +658,59 @@
658 658  
659 659  AT+INTMOD            : Set the trigger interrupt mode
660 660  
661 -AT+5VT  : Set extend the time of 5V power  
578 +AT+5VT  : Set extend the time of 5V power  
662 662  
663 -AT+PRO  : Choose agreement
580 +AT+PRO  : Choose agreement
664 664  
665 -AT+RXDL  : Extend the sending and receiving time
582 +AT+RXDL  : Extend the sending and receiving time
666 666  
667 -AT+SERVADDR  : Server Address
584 +AT+SERVADDR  : Server Address
668 668  
669 -AT+TR      :  Get or Set record time
586 +AT+TR      :  Get or Set record time
670 670  
671 -AT+NOUD      : Get or Set the number of data to be uploaded
588 +AT+NOUD :  Get or Set the number of data to be uploaded
672 672  
673 673  AT+CDP     :  Read or Clear cached data
674 674  
675 -AT+ DEBUG   : Enable or Disable debug mode
592 +AT+DEBUG:  Enable or Disable debug mode
676 676  
677 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
594 +AT+ALARM1:  Get or Set alarm of distance1
678 678  
679 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
596 +AT+ALARM2:  Get or Set alarm of distance2
680 680  
681 -AT+COUNTMOD  :  Get or Set the count mode
598 +AT+GETSENSORVALUE :  Returns the current sensor measurement
682 682  
683 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
600 +AT+POWERIC :  Get or set the Power IC flag
684 684  
685 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
686 686  
687 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
688 -
689 -AT+ CLRC   :  Clear current door open count
690 -
691 -
692 692  (% style="color:blue" %)**COAP Management**      
693 693  
694 -AT+URI            : Resource parameters
605 +AT+URI :  Resource parameters
695 695  
696 696  
697 697  (% style="color:blue" %)**UDP Management**
698 698  
699 -AT+CFM          : Upload confirmation mode (only valid for UDP)
610 +AT+CFM :  Upload confirmation mode (only valid for UDP)
700 700  
701 701  
702 702  (% style="color:blue" %)**MQTT Management**
703 703  
704 -AT+CLIENT               : Get or Set MQTT client
615 +AT+CLIENT  : Get or Set MQTT client
705 705  
706 -AT+UNAME  : Get or Set MQTT Username
617 +AT+UNAME : Get or Set MQTT Username
707 707  
708 -AT+PWD                  : Get or Set MQTT password
619 +AT+PWD  :  Get or Set MQTT password
709 709  
710 -AT+PUBTOPIC  : Get or Set MQTT publish topic
621 +AT+PUBTOPIC :  Get or Set MQTT publish topic
711 711  
712 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
623 +AT+SUBTOPIC :  Get or Set MQTT subscription topic
713 713  
714 714  
715 715  (% style="color:blue" %)**Information**          
716 716  
717 -AT+FDR  : Factory Data Reset
628 +AT+FDR :  Factory Data Reset
718 718  
719 -AT+PWORD  : Serial Access Password
630 +AT+PWORD :  Serial Access Password
720 720  
721 721  
722 722  = ​5.  FAQ =
... ... @@ -728,7 +728,7 @@
728 728  
729 729  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]]
730 730  
731 -(% 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.**
642 +(% 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.**
732 732  
733 733  
734 734  = 6.  Trouble Shooting =
... ... @@ -745,10 +745,16 @@
745 745  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.
746 746  
747 747  
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 +
748 748  = 7. ​ Order Info =
749 749  
750 750  
751 -Part Number**:** NDS03A
668 +Part Number:(% style="color:blue" %)** NMDS200**
752 752  
753 753  
754 754  = 8.  Packing Info =
... ... @@ -756,7 +756,7 @@
756 756  
757 757  (% style="color:blue" %)**Package Includes**:
758 758  
759 -* NDS03A Open/Close Door Sensor x 1
676 +* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
760 760  
761 761  = 9.  Support =
762 762  
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