Version 79.2 by Xiaoling on 2022/12/07 17:41
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
55
56 == 1.3 Radar probe specification ==
57
58
59 * Measuring Method: FMCW
60 * Frequency: 24.000 24.500 GHz
61 * Measurement output power: 6dBm
62 * Measure range: 0.5 20m
63 * Accuracy: ±0.1m
64 * Resolution: 0.01m
65 * Horizontal Angel: 78°
66 * Vertical Angel: 23°
67
68
69
70
71 == 1.4  Storage Temperature ==
72
73
74 -40°C to +85°C
75
76
77
78
79
80 == 1.5 ​ Applications ==
81
82
83
84 * Horizontal distance measurement
85 * Liquid level measurement
86 * Parking management system
87 * Object proximity and presence detection
88 * Intelligent trash can management system
89 * Robot obstacle avoidance
90 * Automatic control
91 * Sewer
92 * Bottom water level monitoring
93
94
95
96 == 1.6  Specification ==
97
98
99 (% style="color:blue" %)**Common DC Characteristics:**
100
101 * Supply Voltage: 2.1v ~~ 3.6v
102 * Operating Temperature: 0 ~~ 70°C
103
104 (% style="color:blue" %)**NB-IoT Spec:**
105
106 * B1 @H-FDD: 2100MHz
107 * B3 @H-FDD: 1800MHz
108 * B8 @H-FDD: 900MHz
109 * B5 @H-FDD: 850MHz
110 * B20 @H-FDD: 800MHz
111 * B28 @H-FDD: 700MHz
112
113
114
115 == 1.7  Installation ==
116
117
118 Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
119
120
121 [[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
122
123
124
125 == 1.8  Pin Definitions and Switch ==
126
127
128 [[image:1670404362039-351.png]]
129
130
131 = 2.  Use NMDS200 to communicate with IoT Server =
132
133 == 2.1  How it works ==
134
135
136 The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
137
138 The diagram below shows the working flow in the default firmware of NMDS200:
139
140 [[image:image-20221021110615-5.png]]
141
142
143 == 2.2 ​ Configure NMDS200 ==
144
145
146 To use NMDS200 in your city, make sure to meet below requirements:
147
148 * Your local operator has already distributed an NB-IoT Network.
149 * The local NB-IoT network used the band that NMDS200 supports.
150 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
151
152 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.
153
154 [[image:image-20221207173300-4.png]]
155
156
157 === 2.2.1 Insert NB-IoT SIM card ===
158
159
160 Insert the NB-IoT Card get from your provider.
161
162 User needs to take out the NB-IoT module and insert the SIM card like below:
163
164 [[image:image-20221021110745-6.png]] ​
165
166
167 === 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
168
169
170 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.
171
172 (% style="color:blue" %)**Connection:**
173
174 (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
175
176 (% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD**
177
178 (% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD**
179
180
181 In the PC, use below serial tool settings:
182
183 * Baud:  (% style="color:red" %)**9600**
184
185 * Data bits:** (% style="color:red" %)8(%%)**
186
187 * Stop bits: (% style="color:red" %)**1**
188
189 * Parity:  (% style="color:red" %)**None**
190
191 * Flow Control: (% style="color:red" %)**None**
192
193 Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
194
195 ​[[image:image-20221021110817-7.png]]
196
197 NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
198
199
200 (% 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]]
201
202
203
204 === 2.2.3 Use CoAP protocol to uplink data ===
205
206
207 (% 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/]]
208
209
210 (% style="color:blue" %)**Use below commands in NDS03A:**
211
212 * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
213
214 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/ Set CoAP server address and port
215
216 * (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/  Set CoAP resource path
217
218 For parameter description, please refer to AT command set
219
220 [[image:image-20221021110948-8.png]]
221
222
223 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.
224
225 [[image:1670405841875-916.png]] ​
226
227
228 === 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
229
230
231 (% style="color:blue" %)**AT Commands:**
232
233 * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
234
235 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  Set UDP server address and port
236
237 * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
238
239 ​ [[image:image-20221021111025-10.png]]
240
241
242 [[image:image-20221021111033-11.png||height="241" width="576"]]
243
244 ​
245
246 === 2.2.5 Use MQTT protocol to uplink data ===
247
248
249 (% style="color:blue" %)**AT Commands:**
250
251 * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
252
253 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
254
255 * (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
256
257 * (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/  Set the username of MQTT
258
259 * (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/  Set the password of MQTT
260
261 * (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)** **~/~/  Set the sending topic of MQTT
262
263 * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
264
265 ​ [[image:image-20221118103445-7.png]]
266
267
268 [[image:1670405928926-116.png]]
269
270 ​
271
272 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.
273
274
275 === 2.2.6 Use TCP protocol to uplink data ===
276
277
278 (% style="color:blue" %)**AT Commands:**
279
280 * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
281
282 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
283
284 ​ [[image:1670406036256-101.png||height="676" width="713"]]
285
286
287 [[image:image-20221021111131-15.png]]
288
289 ​
290
291 === 2.2.7 Change Update Interval ===
292
293
294 User can use below command to change the (% style="color:blue" %)**uplink interval**.
295
296 * (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
297
298 (% style="color:red" %)**NOTE:**
299
300 1.  By default, the device will send an uplink message every 4 hour.
301
302
303 == 2.3  Uplink Payload ==
304
305
306 The uplink payload includes 26 bytes in total by default.
307
308 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.
309
310 (% style="color:blue" %)**When AT+TTRCHANNEL=1:**
311
312 (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
313 |=(% 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:60px" %)**1**|(% style="width:90px" %)**3**|(% style="width:100px" %)**3**
314 |=(% 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" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
315
316 (% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
317 |(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
318 **1-32 group**
319 )))
320 |(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:115px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)|(% style="width:99px" %)last open time(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
321
322 (% style="color:blue" %)**When AT+TTRCHANNEL=2:**
323
324
325 (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
326 |=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:45px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:60px" %)**1**|(% style="width:60px" %)**1**|(% style="width:87px" %)**3**|(% style="width:80px" %)**3**
327 |=(% style="width: 96px;" %)**Value**|(% style="width:66px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:70px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:55px" %)Door Status(pb14)|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb14)|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
328
329 (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
330 |(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:75px" %)**1**|(% style="width:75px" %)**3**
331 |(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
332
333 (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
334 |(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
335 **1-32 group**
336 )))
337 |(% style="width:102px" %)last open time(pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:100px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......
338
339 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
340
341 [[image:image-20221117145932-2.png]]
342
343
344 The payload is ASCII string, representative same HEX:
345
346 **0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0ccf__(% style="color:#00b0f0" %) __19__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__(% style="color:#660066" %) (% style="color:#aaaa40" %)__000016__(% style="color:#663300" %) __000017__ (% style="color:#d60093" %)__637590df__(%%)**
347
348 **where:**
349
350 * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
351
352 * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
353
354 * (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
355
356 * (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
357
358 * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
359
360 * (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
361
362 * (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
363
364 * (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
365
366 * (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
367
368 * (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
369
370 == 2.4  Payload Explanation and Sensor Interface ==
371
372 === 2.4.1  Device ID ===
373
374
375 By default, the Device ID is equal to the last 15 bits of IMEI.
376
377 User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
378
379 **Example:**
380
381 AT+DEUI=868411056754138
382
383 The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
384
385
386 === 2.4.2  Version Info ===
387
388
389 Specify the software version: 0x64=100, which means firmware version 1.00.
390
391 For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
392
393
394 === 2.4.3  Battery Info ===
395
396
397 Check the battery voltage for NDS03A.
398
399 Ex1: 0x0B45 = 2885mV
400
401 Ex2: 0x0B49 = 2889mV
402
403
404 === 2.4.4  Signal Strength ===
405
406
407 NB-IoT Network signal Strength.
408
409 **Ex1: 0x1d = 29**
410
411 **0**  -113dBm or less
412
413 **1**  -111dBm
414
415 **2...30** -109dBm... -53dBm
416
417 **31**   -51dBm or greater
418
419 **99**    Not known or not detectable
420
421
422 === 2.4.5  Disalarm: (default: 0) ===
423
424
425 (% style="color:blue" %)**If Disalarm = 1**(%%), NDS03A will only send uplink at every TDC periodically. This is normally use for pulse meter application, in this application, there are many open/close event, and platform only care about the total number of pulse.
426
427 (% style="color:blue" %)**If Disalarm = 0**(%%), NDS03A will send uplink at every TDC periodically and send data on each open/close event. This is useful for the application user need to monitor the open/close event in real-time.
428
429 (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
430
431
432 === 2.4.6  Keep Status & Keep Time ===
433
434
435 Shows the configure value of Alarm Base on Timeout Feature
436
437
438 === 2.4.7  Timestamp ===
439
440
441 Timestamp : 0x6315537b =1662342011
442
443
444 === 2.4.8  Switch Dual Channel Mode ===
445
446
447 NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
448
449
450 == 2.5  Downlink Payload ==
451
452
453 By default, NDS03A prints the downlink payload to console port.
454
455 [[image:image-20221021111414-18.png]] ​
456
457
458 **Examples:**
459
460 * (% style="color:#037691" %)**Set TDC**
461
462 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
463
464 Payload:    01 00 00 1E    TDC=30S
465
466 Payload:    01 00 00 3C    TDC=60S
467
468 * (% style="color:#037691" %)**Reset**
469
470 If payload = 0x04FF, it will reset the NDS03A
471
472 * (% style="color:#037691" %)**INTMOD**
473
474 Downlink Payload: 06000003, Set AT+INTMOD=3
475
476
477 == 2.6  ​LED Indicator ==
478
479
480 The NDS03A has an internal LED which is to show the status of different states.
481
482 * When the device starts normally, the LED will light up for 1 second.
483 * After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
484 * For each uplink probe, LED will be on for 500ms.
485
486 == 2.7  Alarm Base on Timeout ==
487
488
489 NDS03A can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are:
490
491
492 (% style="color:blue" %)**1. Keep Status: Status to be monitor**
493
494 Keep Status = 1: Monitor Close to Open event
495
496 Keep Status = 0: Monitor Open to Close event
497
498
499 (% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
500
501 Range 0 ~~ 65535(0xFFFF) seconds.
502
503 If keep time = 0, Disable Alarm Base on Timeout feature.
504
505 If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
506
507
508 (% style="color:blue" %)**AT Command to configure:**
509
510 (% style="color:blue" %)**PB14 PIN:**
511
512 (% style="color:#037691" %)**AT+TTRIG=1,30** (%%) **~-~->**  When the **Keep Status** change from connected to disconnect, and device remains in disconnect status for more than 30 seconds. NDS03A will send an uplink packet, the [[Alarm bit>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.
513
514 (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
515
516
517 (% style="color:blue" %)**PB15 PIN:**
518
519 (% style="color:#037691" %)**AT+TTRIG2=1,30**
520
521 (% style="color:#037691" %)**AT+TTRIG2=0,0 **
522
523
524 == 2.8  Set debug mode ==
525
526
527 Feature: Enable or Disable debug mode
528
529 (% style="color:blue" %)**AT Command: AT+DEBUG**
530
531 [[image:image-20221021111629-21.png]]
532
533
534
535 == 2.9  Clear Flash Record ==
536
537
538 Feature: Clear flash storage for data log feature.
539
540 (% style="color:blue" %)**AT Command: AT+CLRDTA**
541
542 [[image:image-20221021111527-19.png]]
543
544
545 == 2.10  Count Mod ==
546
547
548 (% style="color:blue" %)**AT Command: AT+COUNTMOD**
549
550 [[image:image-20221118092935-1.png]]
551
552
553 == 2.11  Interrupt Pin Channel Mod ==
554
555
556 (% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
557
558 [[image:image-20221118093144-2.png]]
559
560
561 == 2.12 TTRIG1/2 timeout status alarm ==
562
563
564 It needs to be used with AT+TTRIG1 or AT+TTRIG2. When TTRIG1 or TTRIG2 times out and causes an alarm, and the status does not change subsequently, an alarm packet will be sent at the alarm interval.
565
566 (% style="color:blue" %)**AT Command: AT+TTRALARM**
567
568 [[image:image-20221118093512-3.png]]
569
570
571 == 2.13  Select counting mode ==
572
573
574 (% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
575
576 When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
577
578 When (% style="color:red" %)**b=0**(%%), it is the last door open duration, and when (% style="color:red" %)**b=1**(%%),the last door close duration.
579
580 [[image:image-20221118093658-4.png]]
581
582
583 == 2.14  Set the number of data to be uploaded and the recording time ==
584
585
586 (% style="color:blue" %)**AT Command:**
587
588 (% 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)
589
590 (% 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.
591
592
593 == 2.15  Read or Clear cached data ==
594
595
596 (% style="color:blue" %)**AT Command:**
597
598 (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
599
600 (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
601
602 [[image:image-20221118094227-5.png]]
603
604
605 == 2.16  ​Firmware Change Log ==
606
607
608 Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
609
610 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
611
612
613 == 2.17  ​Battery Analysis ==
614
615 === 2.17.1  ​Battery Type ===
616
617
618 The NDS03A 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.
619
620 The battery is designed to last for several years depends on the actual use environment and update interval. 
621
622 The battery-related documents as below:
623
624 * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
625
626 * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
627
628 * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
629
630 [[image:image-20221021111911-26.png]] ​
631
632
633 === 2.17.2  Power consumption Analyze ===
634
635
636 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.
637
638 Instruction to use as below:
639
640 (% 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/]]
641
642 (% style="color:blue" %)**Step 2: **(%%) Open it and choose
643
644 * Product Model
645
646 * Uplink Interval
647
648 * Working Mode
649
650 And the Life expectation in difference case will be shown on the right.
651
652 [[image:1666596205057-567.png]] ​
653
654
655 === 2.17.3  ​Battery Note ===
656
657
658 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.
659
660
661 === 2.17.4  Replace the battery ===
662
663
664 The default battery pack of NDS03A 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).
665
666
667 = 3. ​ Access NB-IoT Module =
668
669
670 Users can directly access the AT command set of the NB-IoT module.
671
672 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/]] 
673
674
675 [[image:image-20221118094449-6.png]] ​
676
677
678 = 4.  Using the AT Commands =
679
680 == 4.1  Access AT Commands ==
681
682
683 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]]
684
685 AT+<CMD>?  : Help on <CMD>
686
687 AT+<CMD>         : Run <CMD>
688
689 AT+<CMD>=<value> : Set the value
690
691 AT+<CMD>=?  : Get the value
692
693
694 (% style="color:blue" %)**General Commands**      
695
696 AT  : Attention       
697
698 AT?  : Short Help     
699
700 ATZ  : MCU Reset    
701
702 AT+TDC  : Application Data Transmission Interval
703
704 AT+CFG  : Print all configurations
705
706 AT+CFGMOD           : Working mode selection
707
708 AT+INTMOD            : Set the trigger interrupt mode
709
710 AT+5VT  : Set extend the time of 5V power  
711
712 AT+PRO  : Choose agreement
713
714 AT+RXDL  : Extend the sending and receiving time
715
716 AT+SERVADDR  : Server Address
717
718 AT+TR      :  Get or Set record time
719
720 AT+NOUD      : Get or Set the number of data to be uploaded
721
722 AT+CDP     :  Read or Clear cached data
723
724 AT+ DEBUG   : Enable or Disable debug mode
725
726 AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
727
728 AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
729
730 AT+COUNTMOD  :  Get or Set the count mode
731
732 AT+TTRCHANNEL  : Get or Set the number of interrupt channels
733
734 AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
735
736 AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
737
738 AT+ CLRC   :  Clear current door open count
739
740
741 (% style="color:blue" %)**COAP Management**      
742
743 AT+URI            : Resource parameters
744
745
746 (% style="color:blue" %)**UDP Management**
747
748 AT+CFM          : Upload confirmation mode (only valid for UDP)
749
750
751 (% style="color:blue" %)**MQTT Management**
752
753 AT+CLIENT               : Get or Set MQTT client
754
755 AT+UNAME  : Get or Set MQTT Username
756
757 AT+PWD                  : Get or Set MQTT password
758
759 AT+PUBTOPIC  : Get or Set MQTT publish topic
760
761 AT+SUBTOPIC  : Get or Set MQTT subscription topic
762
763
764 (% style="color:blue" %)**Information**          
765
766 AT+FDR  : Factory Data Reset
767
768 AT+PWORD  : Serial Access Password
769
770
771 = ​5.  FAQ =
772
773 == 5.1 ​ How to Upgrade Firmware ==
774
775
776 User can upgrade the firmware for 1) bug fix, 2) new feature release.
777
778 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]]
779
780 (% 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.**
781
782
783 = 6.  Trouble Shooting =
784
785 == 6.1  ​Connection problem when uploading firmware ==
786
787
788 (% 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]]
789
790
791 == 6.2  AT Command input doesn't work ==
792
793
794 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.
795
796
797 = 7. ​ Order Info =
798
799
800 Part Number**:** NDS03A
801
802
803 = 8.  Packing Info =
804
805
806 (% style="color:blue" %)**Package Includes**:
807
808 * NDS03A Open/Close Door Sensor x 1
809
810 = 9.  Support =
811
812
813 * 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.
814
815 * 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]]
816
817 ​

Applications

Navigation

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