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