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

Applications

Navigation

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