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

Applications

Navigation

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