Skip to Content
Version 83.9 by Xiaoling on 2022/12/08 11:31
Show last authors
1 (% style="text-align:center" %)
2 [[image:LMDS200_10.jpg]]
3
4
5 **Table of Contents：**
6
7 {{toc/}}
8
9
10
11
12 = 1.  Introduction =
13
14 == 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
15
16
17 (((
18 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.
19 )))
20
21 (((
22 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.
23 )))
24
25 (((
26 NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
27 )))
28
29 (((
30 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.
31 )))
32
33 (((
34 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.
35 )))
36
37 (((
38 NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
39 )))
40
41 (((
42 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)
43 )))
44
45 (((
46 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.
47 )))
48
49
50 == ​1.2  Features ==
51
52
53 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
54 * Short uplink interval for Distance Alarm
55 * Monitor Battery Level
56 * Microwave Radar for distance detection
57 * Datalog feature
58 * Uplink periodically
59 * Downlink to change configure
60 * Wall Mountable
61 * Outdoor Use
62 * Ultra-Low Power consumption
63 * AT Commands to change parameters
64 * Micro SIM card slot for NB-IoT SIM
65 * 8500mAh Battery for long-term use
66
67 == 1.3 Radar probe specification ==
68
69
70 * Measuring Method: FMCW
71 * Frequency: 24.000 24.500 GHz
72 * Measurement output power: 6dBm
73 * Measure range: 0.5 20m
74 * Accuracy: ±0.1m
75 * Resolution: 0.01m
76 * Horizontal Angel: 78°
77 * Vertical Angel: 23°
78
79 == 1.4  Storage Temperature ==
80
81
82 -40°C to +85°C
83
84
85 == 1.5 ​ Applications ==
86
87
88 * Horizontal distance measurement
89 * Liquid level measurement
90 * Parking management system
91 * Object proximity and presence detection
92 * Intelligent trash can management system
93 * Robot obstacle avoidance
94 * Automatic control
95 * Sewer
96 * Bottom water level monitoring
97
98 == 1.6  Specification ==
99
100
101 (% style="color:blue" %)**Common DC Characteristics:**
102
103 * Supply Voltage: 2.1v ~~ 3.6v
104 * Operating Temperature: 0 ~~ 70°C
105
106 (% style="color:blue" %)**NB-IoT Spec:**
107
108 * B1 @H-FDD: 2100MHz
109 * B3 @H-FDD: 1800MHz
110 * B8 @H-FDD: 900MHz
111 * B5 @H-FDD: 850MHz
112 * B20 @H-FDD: 800MHz
113 * B28 @H-FDD: 700MHz
114
115 == 1.7  Installation ==
116
117
118 Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
119
120
121 [[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
122
123
124
125 == 1.8  Pin Definitions and Switch ==
126
127
128 [[image:1670404362039-351.png]]
129
130
131 = 2.  Use NMDS200 to communicate with IoT Server =
132
133 == 2.1  How it works ==
134
135
136 The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
137
138 The diagram below shows the working flow in the default firmware of NMDS200:
139
140 [[image:image-20221021110615-5.png]]
141
142
143 == 2.2 ​ Configure NMDS200 ==
144
145
146 To use NMDS200 in your city, make sure to meet below requirements:
147
148 * Your local operator has already distributed an NB-IoT Network.
149 * The local NB-IoT network used the band that NMDS200 supports.
150 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
151
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
154 [[image:image-20221208090742-1.png]]
155
156
157 === 2.2.1 Insert NB-IoT SIM card ===
158
159
160 Insert the NB-IoT Card get from your provider.
161
162 User needs to take out the NB-IoT module and insert the SIM card like below:
163
164 [[image:image-20221021110745-6.png]] ​
165
166
167 === 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
168
169
170 User need to configure NMDS200 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NMDS200 support AT Commands, user can use a USB to TTL adapter to connect to NMDS200 and use AT Commands to configure it, as below.
171
172 (% style="color:blue" %)**Connection:**
173
174 (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
175
176 (% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD**
177
178 (% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD**
179
180
181 In the PC, use below serial tool settings:
182
183 * Baud:  (% style="color:red" %)**9600**
184
185 * Data bits:** (% style="color:red" %)8(%%)**
186
187 * Stop bits: (% style="color:red" %)**1**
188
189 * Parity:  (% style="color:red" %)**None**
190
191 * Flow Control: (% style="color:red" %)**None**
192
193 Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
194
195 ​[[image:image-20221021110817-7.png]]
196
197 NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
198
199
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
202
203
204 === 2.2.3 Use CoAP protocol to uplink data ===
205
206
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
209
210 (% style="color:blue" %)**Use below commands in NMDS200:**
211
212 * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
213
214 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/ Set CoAP server address and port
215
216 * (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/  Set CoAP resource path
217
218 For parameter description, please refer to AT command set
219
220 [[image:image-20221021110948-8.png]]
221
222
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.
224
225 [[image:1670405841875-916.png]] ​
226
227
228 === 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
229
230
231 (% style="color:blue" %)**AT Commands:**
232
233 * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
234
235 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  Set UDP server address and port
236
237 * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
238
239 ​ [[image:image-20221021111025-10.png]]
240
241
242 [[image:image-20221021111033-11.png||height="241" width="576"]]
243
244 ​
245
246 === 2.2.5 Use MQTT protocol to uplink data ===
247
248
249 (% style="color:blue" %)**AT Commands:**
250
251 * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
252
253 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
254
255 * (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
256
257 * (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/  Set the username of MQTT
258
259 * (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/  Set the password of MQTT
260
261 * (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)** **~/~/  Set the sending topic of MQTT
262
263 * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
264
265 ​ [[image:image-20221118103445-7.png]]
266
267
268 [[image:1670405928926-116.png]]
269
270 ​
271
272 MQTT protocol has a much higher power consumption compare with UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
273
274
275 === 2.2.6 Use TCP protocol to uplink data ===
276
277
278 (% style="color:blue" %)**AT Commands:**
279
280 * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
281
282 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
283
284 ​ [[image:1670406036256-101.png||height="676" width="713"]]
285
286
287 [[image:image-20221021111131-15.png]]
288
289 ​
290
291 === 2.2.7 Change Update Interval ===
292
293
294 User can use below command to change the (% style="color:blue" %)**uplink interval**.
295
296 * (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
297
298 (% style="color:red" %)**NOTE:**
299
300 1.  By default, the device will send an uplink message every 4 hour.
301
302
303 == 2.3  Uplink Payload ==
304
305
306 The uplink payload includes 23 bytes in total by default.
307
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
310
311 (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:450px" %)
312 |=(% 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**
313 |=(% 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"]]
314
315 (% border="1" style="background-color:#ffffcc; color:green; width:350px" %)
316 |(% style="width:60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)(((
317 **1-32 group**
318 )))
319 |(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:98px" %)...
320
321 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
322
323 [[image:1670406261143-723.png]]
324
325
326 The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
327
328 **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__(%%)**
329
330 **where:**
331
332 * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
333
334 * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
335
336 * (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
337
338 * (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
339
340 * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
341
342 * (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
343
344 * (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
345
346 * (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
347
348 * (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
349
350
351 == 2.4  Payload Explanation and Sensor Interface ==
352
353 === 2.4.1  Device ID ===
354
355
356 By default, the Device ID is equal to the last 15 bits of IMEI.
357
358 User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
359
360 **Example:**
361
362 AT+DEUI=868411056754138
363
364 The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
365
366
367 === 2.4.2  Version Info ===
368
369
370 Specify the software version: 0x64=100, which means firmware version 1.00.
371
372 For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
373
374
375 === 2.4.3  Battery Info ===
376
377
378 Check the battery voltage for NMDS200.
379
380 Ex1: 0x0B45 = 2885mV
381
382 Ex2: 0x0B49 = 2889mV
383
384
385 === 2.4.4  Signal Strength ===
386
387
388 NB-IoT Network signal Strength.
389
390 (% style="color:blue" %)**Ex1: 0x1d = 29**
391
392 (% style="color:#037691" %)**0** (%%) -113dBm or less
393
394 (% style="color:#037691" %)**1**  (%%) -111dBm
395
396 (% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
397
398 (% style="color:#037691" %)**31** (%%) -51dBm or greater
399
400 (% style="color:#037691" %)**99** (%%) Not known or not detectable
401
402
403 === 2.4.5  Distance ===
404
405
406 [[image:1670407401682-959.png]]
407
408
409 (% style="color:blue" %)**Object1 Distance:**
410
411 Distance between sensor probe to the first object. (unit: cm)
412
413 For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
414
415 (% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
416
417
418 (% style="color:blue" %)**Object2 Distance:**
419
420 Distance between sensor probe to the second object. (unit: cm)
421
422
423 === 2.4.6  Timestamp ===
424
425
426 Timestamp : 0x6315537b =1662342011
427
428
429 == 2.5  Downlink Payload ==
430
431
432 By default, NMDS200 prints the downlink payload to console port.
433
434 [[image:image-20221021111414-18.png]] ​
435
436
437 **Examples:**
438
439 * (% style="color:#037691" %)**Set TDC**
440
441 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
442
443 Payload:    01 00 00 1E    TDC=30S
444
445 Payload:    01 00 00 3C    TDC=60S
446
447 * (% style="color:#037691" %)**Reset**
448
449 If payload = 0x04FF, it will reset the NMDS200
450
451 * (% style="color:#037691" %)**INTMOD**
452
453 Downlink Payload: 06000003, Set AT+INTMOD=3
454
455
456 == 2.6  ​LED Indicator ==
457
458
459 The NMDS200 has an internal LED which is to show the status of different states.
460
461 * When the device starts normally, the LED will light up for 1 second.
462 * After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
463 * For each uplink probe, LED will be on for 500ms.
464
465
466 == 2.7  Distance alarm function ==
467
468
469 (% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
470
471 (% style="color:#037691" %)**Example 1:**
472
473 AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
474
475 AT+ ALARM2 =min,max
476
477
478 (% style="color:#037691" %)**Example 2:**
479
480 AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
481
482
483 == 2.8  Set the number of data to be uploaded and the recording time ==
484
485
486 (% style="color:blue" %)**AT Command:**
487
488 (% 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)
489
490 (% 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.
491
492
493 == 2.9  Read or Clear cached data ==
494
495
496 (% style="color:blue" %)**AT Command:**
497
498 (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
499
500 (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
501
502 [[image:1670408172929-569.png]]
503
504
505 == 2.10  ​Firmware Change Log ==
506
507
508 Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
509
510 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
511
512
513 == 2.11  ​Battery Analysis ==
514
515 === 2.11.1  ​Battery Type ===
516
517
518 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.
519
520 The battery is designed to last for several years depends on the actual use environment and update interval. 
521
522 The battery-related documents as below:
523
524 * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
525
526 * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
527
528 * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
529
530 [[image:image-20221021111911-26.png]] ​
531
532
533 === 2.11.2  Power consumption Analyze ===
534
535
536 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.
537
538 Instruction to use as below:
539
540 (% 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/]]
541
542 (% style="color:blue" %)**Step 2: **(%%) Open it and choose
543
544 * Product Model
545
546 * Uplink Interval
547
548 * Working Mode
549
550 And the Life expectation in difference case will be shown on the right.
551
552 [[image:1666596205057-567.png]] ​
553
554
555 === 2.11.3  ​Battery Note ===
556
557
558 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.
559
560
561 === 2.11.4  Replace the battery ===
562
563
564 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).
565
566
567 = 3. ​ Access NB-IoT Module =
568
569
570 Users can directly access the AT command set of the NB-IoT module.
571
572 The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 
573
574
575 [[image:image-20221118094449-6.png]] ​
576
577
578 = 4.  Using the AT Commands =
579
580 == 4.1  Access AT Commands ==
581
582
583 See this link for detail:  [[https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
584
585 AT+<CMD>?  : Help on <CMD>
586
587 AT+<CMD>         : Run <CMD>
588
589 AT+<CMD>=<value> : Set the value
590
591 AT+<CMD>=?  : Get the value
592
593
594 (% style="color:blue" %)**General Commands**      
595
596 AT  : Attention       
597
598 AT?  : Short Help     
599
600 ATZ  : MCU Reset    
601
602 AT+TDC  : Application Data Transmission Interval
603
604 AT+CFG  : Print all configurations
605
606 AT+CFGMOD           : Working mode selection
607
608 AT+INTMOD            : Set the trigger interrupt mode
609
610 AT+5VT  : Set extend the time of 5V power  
611
612 AT+PRO  : Choose agreement
613
614 AT+RXDL  : Extend the sending and receiving time
615
616 AT+SERVADDR  : Server Address
617
618 AT+TR      :  Get or Set record time
619
620 AT+NOUD :  Get or Set the number of data to be uploaded
621
622 AT+CDP     :  Read or Clear cached data
623
624 AT+DEBUG:  Enable or Disable debug mode
625
626 AT+ALARM1:  Get or Set alarm of distance1
627
628 AT+ALARM2:  Get or Set alarm of distance2
629
630 AT+GETSENSORVALUE :  Returns the current sensor measurement
631
632 AT+POWERIC :  Get or set the Power IC flag
633
634
635 (% style="color:blue" %)**COAP Management**      
636
637 AT+URI :  Resource parameters
638
639
640 (% style="color:blue" %)**UDP Management**
641
642 AT+CFM :  Upload confirmation mode (only valid for UDP)
643
644
645 (% style="color:blue" %)**MQTT Management**
646
647 AT+CLIENT  : Get or Set MQTT client
648
649 AT+UNAME : Get or Set MQTT Username
650
651 AT+PWD  :  Get or Set MQTT password
652
653 AT+PUBTOPIC :  Get or Set MQTT publish topic
654
655 AT+SUBTOPIC :  Get or Set MQTT subscription topic
656
657
658 (% style="color:blue" %)**Information**          
659
660 AT+FDR :  Factory Data Reset
661
662 AT+PWORD :  Serial Access Password
663
664
665 = ​5.  FAQ =
666
667 == 5.1 ​ How to Upgrade Firmware ==
668
669
670 User can upgrade the firmware for 1) bug fix, 2) new feature release.
671
672 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]]
673
674 (% 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.**
675
676
677 = 6.  Trouble Shooting =
678
679 == 6.1  ​Connection problem when uploading firmware ==
680
681
682 (% style="color:blue" %)**Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
683
684
685 == 6.2  AT Command input doesn't work ==
686
687
688 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.
689
690
691 = 7. ​ Order Info =
692
693
694 Part Number:(% style="color:blue" %)** NMDS200**
695
696
697 = 8.  Packing Info =
698
699
700 (% style="color:blue" %)**Package Includes**:
701
702 * NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
703
704
705 = 9.  Support =
706
707
708 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
709
710 * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
711
712 ​