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

Applications

Navigation

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