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

Applications

Navigation

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