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