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