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

Applications

Navigation

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