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