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

Applications

Navigation

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