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

Applications

Navigation

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