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