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

Applications

Navigation

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