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