Version 78.1 by Xiaoling on 2022/12/07 17:38
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.3 Connect USB – TTL to NDS03A and configure it ===
168
169
170 User need to configure NDS03A via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USB to TTL adapter to connect to NDS03A 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 NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
194
195 ​[[image:image-20221021110817-7.png]]
196
197 NDS03A 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.4 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 NDS03A**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
224
225 [[image:image-20221118103547-9.png||height="605" width="837"]] ​
226
227
228 === 2.2.5 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.6 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:image-20221118103453-8.png||height="608" width="841"]]
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.7 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:image-20221021111125-14.png]]
285
286 [[image:image-20221021111131-15.png]]
287
288 ​
289
290 === 2.2.8 Change Update Interval ===
291
292
293 User can use below command to change the (% style="color:blue" %)**uplink interval**.
294
295 * (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
296
297 (% style="color:red" %)**NOTE:**
298
299 1.  By default, the device will send an uplink message every 4 hour.
300
301
302 == 2.3  Uplink Payload ==
303
304
305 The uplink payload includes 26 bytes in total by default.
306
307 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.
308
309 (% style="color:blue" %)**When AT+TTRCHANNEL=1:**
310
311 (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
312 |=(% 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**
313 |=(% 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)
314
315 (% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
316 |(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
317 **1-32 group**
318 )))
319 |(% 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" %)...
320
321 (% style="color:blue" %)**When AT+TTRCHANNEL=2:**
322
323
324 (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
325 |=(% 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**
326 |=(% 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)
327
328 (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
329 |(% 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**
330 |(% 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)
331
332 (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
333 |(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
334 **1-32 group**
335 )))
336 |(% 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" %)......
337
338 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
339
340 [[image:image-20221117145932-2.png]]
341
342
343 The payload is ASCII string, representative same HEX:
344
345 **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__(%%)**
346
347 **where:**
348
349 * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
350
351 * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
352
353 * (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
354
355 * (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
356
357 * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
358
359 * (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
360
361 * (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
362
363 * (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
364
365 * (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
366
367 * (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
368
369 == 2.4  Payload Explanation and Sensor Interface ==
370
371 === 2.4.1  Device ID ===
372
373
374 By default, the Device ID is equal to the last 15 bits of IMEI.
375
376 User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
377
378 **Example:**
379
380 AT+DEUI=868411056754138
381
382 The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
383
384
385 === 2.4.2  Version Info ===
386
387
388 Specify the software version: 0x64=100, which means firmware version 1.00.
389
390 For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
391
392
393 === 2.4.3  Battery Info ===
394
395
396 Check the battery voltage for NDS03A.
397
398 Ex1: 0x0B45 = 2885mV
399
400 Ex2: 0x0B49 = 2889mV
401
402
403 === 2.4.4  Signal Strength ===
404
405
406 NB-IoT Network signal Strength.
407
408 **Ex1: 0x1d = 29**
409
410 **0**  -113dBm or less
411
412 **1**  -111dBm
413
414 **2...30** -109dBm... -53dBm
415
416 **31**   -51dBm or greater
417
418 **99**    Not known or not detectable
419
420
421 === 2.4.5  Disalarm: (default: 0) ===
422
423
424 (% 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.
425
426 (% 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.
427
428 (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
429
430
431 === 2.4.6  Keep Status & Keep Time ===
432
433
434 Shows the configure value of Alarm Base on Timeout Feature
435
436
437 === 2.4.7  Timestamp ===
438
439
440 Timestamp : 0x6315537b =1662342011
441
442
443 === 2.4.8  Switch Dual Channel Mode ===
444
445
446 NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
447
448
449 == 2.5  Downlink Payload ==
450
451
452 By default, NDS03A prints the downlink payload to console port.
453
454 [[image:image-20221021111414-18.png]] ​
455
456
457 **Examples:**
458
459 * (% style="color:#037691" %)**Set TDC**
460
461 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
462
463 Payload:    01 00 00 1E    TDC=30S
464
465 Payload:    01 00 00 3C    TDC=60S
466
467 * (% style="color:#037691" %)**Reset**
468
469 If payload = 0x04FF, it will reset the NDS03A
470
471 * (% style="color:#037691" %)**INTMOD**
472
473 Downlink Payload: 06000003, Set AT+INTMOD=3
474
475
476 == 2.6  ​LED Indicator ==
477
478
479 The NDS03A has an internal LED which is to show the status of different states.
480
481 * When the device starts normally, the LED will light up for 1 second.
482 * After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
483 * For each uplink probe, LED will be on for 500ms.
484
485 == 2.7  Alarm Base on Timeout ==
486
487
488 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:
489
490
491 (% style="color:blue" %)**1. Keep Status: Status to be monitor**
492
493 Keep Status = 1: Monitor Close to Open event
494
495 Keep Status = 0: Monitor Open to Close event
496
497
498 (% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
499
500 Range 0 ~~ 65535(0xFFFF) seconds.
501
502 If keep time = 0, Disable Alarm Base on Timeout feature.
503
504 If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
505
506
507 (% style="color:blue" %)**AT Command to configure:**
508
509 (% style="color:blue" %)**PB14 PIN:**
510
511 (% 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.
512
513 (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
514
515
516 (% style="color:blue" %)**PB15 PIN:**
517
518 (% style="color:#037691" %)**AT+TTRIG2=1,30**
519
520 (% style="color:#037691" %)**AT+TTRIG2=0,0 **
521
522
523 == 2.8  Set debug mode ==
524
525
526 Feature: Enable or Disable debug mode
527
528 (% style="color:blue" %)**AT Command: AT+DEBUG**
529
530 [[image:image-20221021111629-21.png]]
531
532
533
534 == 2.9  Clear Flash Record ==
535
536
537 Feature: Clear flash storage for data log feature.
538
539 (% style="color:blue" %)**AT Command: AT+CLRDTA**
540
541 [[image:image-20221021111527-19.png]]
542
543
544 == 2.10  Count Mod ==
545
546
547 (% style="color:blue" %)**AT Command: AT+COUNTMOD**
548
549 [[image:image-20221118092935-1.png]]
550
551
552 == 2.11  Interrupt Pin Channel Mod ==
553
554
555 (% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
556
557 [[image:image-20221118093144-2.png]]
558
559
560 == 2.12 TTRIG1/2 timeout status alarm ==
561
562
563 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.
564
565 (% style="color:blue" %)**AT Command: AT+TTRALARM**
566
567 [[image:image-20221118093512-3.png]]
568
569
570 == 2.13  Select counting mode ==
571
572
573 (% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
574
575 When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
576
577 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.
578
579 [[image:image-20221118093658-4.png]]
580
581
582 == 2.14  Set the number of data to be uploaded and the recording time ==
583
584
585 (% style="color:blue" %)**AT Command:**
586
587 (% 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)
588
589 (% 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.
590
591
592 == 2.15  Read or Clear cached data ==
593
594
595 (% style="color:blue" %)**AT Command:**
596
597 (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
598
599 (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
600
601 [[image:image-20221118094227-5.png]]
602
603
604 == 2.16  ​Firmware Change Log ==
605
606
607 Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
608
609 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
610
611
612 == 2.17  ​Battery Analysis ==
613
614 === 2.17.1  ​Battery Type ===
615
616
617 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.
618
619 The battery is designed to last for several years depends on the actual use environment and update interval. 
620
621 The battery-related documents as below:
622
623 * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
624
625 * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
626
627 * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
628
629 [[image:image-20221021111911-26.png]] ​
630
631
632 === 2.17.2  Power consumption Analyze ===
633
634
635 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.
636
637 Instruction to use as below:
638
639 (% 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/]]
640
641 (% style="color:blue" %)**Step 2: **(%%) Open it and choose
642
643 * Product Model
644
645 * Uplink Interval
646
647 * Working Mode
648
649 And the Life expectation in difference case will be shown on the right.
650
651 [[image:1666596205057-567.png]] ​
652
653
654 === 2.17.3  ​Battery Note ===
655
656
657 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.
658
659
660 === 2.17.4  Replace the battery ===
661
662
663 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).
664
665
666 = 3. ​ Access NB-IoT Module =
667
668
669 Users can directly access the AT command set of the NB-IoT module.
670
671 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/]] 
672
673
674 [[image:image-20221118094449-6.png]] ​
675
676
677 = 4.  Using the AT Commands =
678
679 == 4.1  Access AT Commands ==
680
681
682 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]]
683
684 AT+<CMD>?  : Help on <CMD>
685
686 AT+<CMD>         : Run <CMD>
687
688 AT+<CMD>=<value> : Set the value
689
690 AT+<CMD>=?  : Get the value
691
692
693 (% style="color:blue" %)**General Commands**      
694
695 AT  : Attention       
696
697 AT?  : Short Help     
698
699 ATZ  : MCU Reset    
700
701 AT+TDC  : Application Data Transmission Interval
702
703 AT+CFG  : Print all configurations
704
705 AT+CFGMOD           : Working mode selection
706
707 AT+INTMOD            : Set the trigger interrupt mode
708
709 AT+5VT  : Set extend the time of 5V power  
710
711 AT+PRO  : Choose agreement
712
713 AT+RXDL  : Extend the sending and receiving time
714
715 AT+SERVADDR  : Server Address
716
717 AT+TR      :  Get or Set record time
718
719 AT+NOUD      : Get or Set the number of data to be uploaded
720
721 AT+CDP     :  Read or Clear cached data
722
723 AT+ DEBUG   : Enable or Disable debug mode
724
725 AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
726
727 AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
728
729 AT+COUNTMOD  :  Get or Set the count mode
730
731 AT+TTRCHANNEL  : Get or Set the number of interrupt channels
732
733 AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
734
735 AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
736
737 AT+ CLRC   :  Clear current door open count
738
739
740 (% style="color:blue" %)**COAP Management**      
741
742 AT+URI            : Resource parameters
743
744
745 (% style="color:blue" %)**UDP Management**
746
747 AT+CFM          : Upload confirmation mode (only valid for UDP)
748
749
750 (% style="color:blue" %)**MQTT Management**
751
752 AT+CLIENT               : Get or Set MQTT client
753
754 AT+UNAME  : Get or Set MQTT Username
755
756 AT+PWD                  : Get or Set MQTT password
757
758 AT+PUBTOPIC  : Get or Set MQTT publish topic
759
760 AT+SUBTOPIC  : Get or Set MQTT subscription topic
761
762
763 (% style="color:blue" %)**Information**          
764
765 AT+FDR  : Factory Data Reset
766
767 AT+PWORD  : Serial Access Password
768
769
770 = ​5.  FAQ =
771
772 == 5.1 ​ How to Upgrade Firmware ==
773
774
775 User can upgrade the firmware for 1) bug fix, 2) new feature release.
776
777 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]]
778
779 (% 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.**
780
781
782 = 6.  Trouble Shooting =
783
784 == 6.1  ​Connection problem when uploading firmware ==
785
786
787 (% 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]]
788
789
790 == 6.2  AT Command input doesn't work ==
791
792
793 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.
794
795
796 = 7. ​ Order Info =
797
798
799 Part Number**:** NDS03A
800
801
802 = 8.  Packing Info =
803
804
805 (% style="color:blue" %)**Package Includes**:
806
807 * NDS03A Open/Close Door Sensor x 1
808
809 = 9.  Support =
810
811
812 * 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.
813
814 * 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]]
815
816 ​

Applications

Navigation

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