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

Applications

Navigation

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