<
From version < 35.1 >
edited by Edwin Chen
on 2022/10/22 23:43
To version < 30.1 >
edited by David Huang
on 2022/10/21 11:20
>
Change comment: Uploaded new attachment "image-20221021112006-28.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.David
Content
... ... @@ -1,29 +1,29 @@
1 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"]]
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"]]
3 3  
4 -{{toc/}}
5 5  
6 -= **1. Introduction** =
5 +**~1. Introduction**
7 7  
8 -== **1.1 ​**What is CPN01 **NB-IoT** Pulse/Contact Sensor ==
7 +**1.1 ​**What is CPN01 **NB-IOT** Pulse/Contact Sensor
9 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.
9 +The Dragino CPL01 is a **NB-IOT Contact Sensor**. It detects open/close status and uplink to IoT server via LoRaWAN network. user can see the dry contact status, open time, open counts in the IoT Server.
11 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.
11 +The CPL01 will send periodically data every day as well as for each dry contact action. It also counts the contact open times and calculate last open duration. User can also disable the uplink for each open/close event, instead, device can count each open event and uplink periodically.
13 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.
13 +CPL01 has the open alarm feature, user can set this feature so device will send Alarm if the contact has been open for a certain time.
15 15  
16 -CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures.
15 +CPL01 is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
17 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.
17 +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.
18 +\\CPN01 supports different uplink methods include **TCP,MQTT,UDP and CoAP  **for different application requirement.
19 +\\CPN01 is powered by  **8500mAh Li-SOCI2 battery**, It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
20 +\\To use CPN01, user needs to check if there is NB-IoT coverage in local area and with the bands CPN01 supports. If the local operate support it, user needs to get a **NB-IoT SIM card** from local operator and install CPN01 to get NB-IoT network connection
22 22  
23 23  ​
24 24  
25 -== **​1.2 Features** ==
26 26  
25 +**​1.2 Features**
26 +
27 27  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
28 28  * Open/Close detect
29 29  * Open/Close statistics
... ... @@ -30,7 +30,7 @@
30 30  * Monitor Battery Level
31 31  * Uplink on periodically and open/close event
32 32  * Datalog feature
33 -* Uplink periodically
33 +* Uplink on periodically
34 34  * Downlink to change configure
35 35  * Wall Mountable
36 36  * Outdoor Use
... ... @@ -37,9 +37,9 @@
37 37  * Ultra-Low Power consumption
38 38  * AT Commands to change parameters
39 39  * Micro SIM card slot for NB-IoT SIM
40 -* 8500mAh Battery for long-term use
40 +* 8500mAh Battery for long term use
41 41  
42 -== **1.3  Specification** ==
42 +**1.3  Specification**
43 43  
44 44  **Common DC Characteristics:**
45 45  
... ... @@ -55,33 +55,31 @@
55 55  * - B20 @H-FDD: 800MHz
56 56  * - B28 @H-FDD: 700MHz
57 57  
58 -== **1.4 Installation** ==
58 +**1.4 Installation**
59 59  
60 60  Connect CPL01 to an Open Close sensor like below. So it can detect the open/close event.
61 61  
62 -[[image:image-20221021110329-1.png]]
62 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image001.png]] [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image002.png]]
63 63  
64 -[[image:image-20221021110340-2.png]]
64 +**1.5 ​Applications**
65 65  
66 -== **1.5 ​Applications** ==
67 -
68 68  * Open/Close Detection
69 69  * Pulse meter application
70 70  * Dry Contact Detection
71 71  
72 -== **1.6 Mechanical** ==
70 +**1.6 Mechanical**
73 73  
74 -​[[image:image-20221021110415-3.png]]
72 +​[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image003.png]]
75 75  
76 -== ** 1.7 Pin Definitions and Switch** ==
74 +**~ 1.7 Pin Definitions and Switch**
77 77  
78 -[[image:image-20221021110429-4.png]]
76 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image004.png]]
79 79  
80 -=== **1.7.1 Pin Definition** ===
78 +**1.7.1 Pin Definition**
81 81  
82 82  CPL01 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 user manual of LSN50v2 at: [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>url:https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]
83 83  
84 -=== **1.7.2 Jumper JP2(Power ON/OFF)** ===
82 +**1.7.2 Jumper JP2(Power ON/OFF)**
85 85  
86 86  
87 87  Power on Device when putting this jumper.
... ... @@ -88,7 +88,7 @@
88 88  
89 89  
90 90  
91 -=== **1.7.3 BOOT MODE / SW1** ===
89 +**1.7.3 BOOT MODE / SW1**
92 92  
93 93  
94 94  1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
... ... @@ -97,34 +97,35 @@
97 97  
98 98  
99 99  
100 -=== **1.7.4 Reset Button** ===
98 +**1.7.4 Reset Button**
101 101  
102 102  
103 103  Press to reboot the device.
104 104  
105 -== ==
106 106  
107 -=== **1.7.5 LED** ===
108 108  
105 +**1.7.5 LED**
109 109  
107 +
110 110  It will flash:
111 111  
112 112  1. Boot the device in flash mode
113 113  1. Send an uplink packet
114 114  
115 -= **2.  Use CPN01 to communicate with IoT Server** =
116 116  
117 -== **2.1  How it works** ==
114 +**2.  Use CPN01 to communicate with IoT Server**
118 118  
116 +**2.1  How it works**
117 +
119 119  The CPN01 is equipped with a NB-IoT module, the pre-loaded firmware in CPN01 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01.
120 120  
121 121  The diagram below shows the working flow in default firmware of CPN01:
122 122  
123 -[[image:image-20221021110615-5.png]]
122 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image005.png||alt="说明: image-20220708101605-2.png"]]
124 124  
125 -== **2.2 ​ Configure the CPN01** ==
124 +**2.2 ​ Configure the CPN01**
126 126  
127 -=== **2.2.1 Test Requirement** ===
126 +**2.2.1 Test Requirement**
128 128  
129 129  To use CPN01 in your city, make sure meet below requirements:
130 130  
... ... @@ -136,15 +136,15 @@
136 136  
137 137   ​
138 138  
139 -=== **2.2.2 Insert SIM card** ===
138 +**2.2.2 Insert SIM card**
140 140  
141 141  Insert the NB-IoT Card get from your provider.
142 142  
143 143  User need to take out the NB-IoT module and insert the SIM card like below:
144 144  
145 -[[image:image-20221021110745-6.png]] ​
144 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image006.png||alt="说明: 1657249468462-536.png"]] ​
146 146  
147 -=== **2.2.3 Connect USB – TTL to CPN01 to configure it** ===
146 +**2.2.3 Connect USB – TTL to CPN01 to configure it**
148 148  
149 149  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.
150 150  
... ... @@ -166,11 +166,11 @@
166 166  
167 167  Make sure the switch is in FLASH position, then power on device by connecting the jumper on CPN01. CPN01 will output system info once power on as below, we can enter the **password: 12345678** to access AT Command input.
168 168  
169 -​[[image:image-20221021110817-7.png]]
168 +​[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image007.png]]
170 170  
171 171  **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]]
172 172  
173 -=== **2.2.4 Use CoAP protocol to uplink data** ===
172 +**2.2.4 Use CoAP protocol to uplink data**
174 174  
175 175  **Note: if you don't have CoAP server, you can refer this link to set up one: **[[**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/]]
176 176  
... ... @@ -182,13 +182,13 @@
182 182  
183 183  For parameter description, please refer to AT command set
184 184  
185 -[[image:image-20221021110948-8.png]]
184 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image008.png]]
186 186  
187 187  After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server.
188 188  
189 -[[image:image-20221021110956-9.png]] ​
188 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image009.png]] ​
190 190  
191 -=== **2.2.5 Use UDP protocol to uplink data(Default protocol)** ===
190 +**2.2.5 Use UDP protocol to uplink data(Default protocol)**
192 192  
193 193  This feature is supported since firmware version v1.0.1
194 194  
... ... @@ -196,13 +196,13 @@
196 196  * **AT+SERVADDR=120.24.4.116,5601   ** ~/~/ to set UDP server address and port
197 197  * **AT+CFM=1       ** ~/~/If the server does not respond, this command is unnecessary
198 198  
199 -​ [[image:image-20221021111025-10.png]]
198 +​ [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image010.png]]
200 200  
201 -[[image:image-20221021111033-11.png||height="241" width="576"]]
200 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image011.png||alt="说明: 1657249930215-289.png"]]
202 202  
203 203  ​
204 204  
205 -=== **2.2.6 Use MQTT protocol to uplink data** ===
204 +**2.2.6 Use MQTT protocol to uplink data**
206 206  
207 207  This feature is supported since firmware version v110
208 208  
... ... @@ -214,15 +214,15 @@
214 214  * **AT+PUBTOPIC=NSE01_PUB                    **~/~/Set the sending topic of MQTT
215 215  * **AT+SUBTOPIC=NSE01_SUB          ** ~/~/Set the subscription topic of MQTT
216 216  
217 -​ [[image:image-20221021111058-12.png]]
216 +​ [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image012.png]]
218 218  
219 -[[image:image-20221021111108-13.png]]
218 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image013.png]]
220 220  
221 221  ​
222 222  
223 223  MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
224 224  
225 -=== **2.2.7 Use TCP protocol to uplink data** ===
224 +**2.2.7 Use TCP protocol to uplink data**
226 226  
227 227  This feature is supported since firmware version v110
228 228  
... ... @@ -229,13 +229,13 @@
229 229  * **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
230 230  * **AT+SERVADDR=120.24.4.116,5600   ** ~/~/ to set TCP server address and port
231 231  
232 -​ [[image:image-20221021111125-14.png]]
231 +​ [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image014.png]]
233 233  
234 -[[image:image-20221021111131-15.png]]
233 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image015.png||alt="说明: 1657250255956-604.png"]]
235 235  
236 236  ​
237 237  
238 -=== **2.2.8 Change Update Interval** ===
237 +**2.2.8 Change Update Interval**
239 239  
240 240  User can use below command to change the **uplink interval**.
241 241  
... ... @@ -245,7 +245,7 @@
245 245  
246 246  **~1. By default, the device will send an uplink message every 1 hour.**
247 247  
248 -== **2.3  Uplink Payload** ==
247 +**2.3  Uplink Payload**
249 249  
250 250  In this mode, uplink payload includes 87 bytes in total by default.
251 251  
... ... @@ -254,48 +254,37 @@
254 254  |**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**2**|**2**|4
255 255  |**Value**|[[Device ID>>path:#H2.4.1A0A0DeviceID]]|[[Ver>>path:#H2.4.2A0VersionInfo]]|[[BAT>>path:#H2.4.3A0BatteryInfo]]|[[Signal Strength>>path:#H2.4.4A0SignalStrength]]|MOD|[[Interrupt>>path:#H2.4.8A0DigitalInterrupt]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|Time stamp
256 256  
256 +
257 257  |2|2|4|8 group
258 258  |[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|Time stamp|...
259 259  
260 260  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
261 261  
262 -[[image:image-20221021111201-16.png||height="572" width="792"]]
262 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image016.png]]
263 263  
264 264  The payload is ASCII string, representative same HEX:
265 265  
266 -**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 //(%%)**
266 +0xf86778705021331700640c7817010001000000090000026315537b 0100000b02000002663510fed0100000e0200000263510f39010000000000000063510e85010000000000000063510d2e010000000000000063510c7a010000000000000063510bc6010000000000000063510954010000000000000063510882 where:
267 267  
268 -where:
269 -*(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317
268 +* **Device ID: 0x f867787050213317 = f867787050213317**
269 +* **Version: 0x0064=100=1.0.0**
270 270  
271 -*(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0
271 +* **BAT: 0x0c78 = 3192 mV = 3.192V**
272 +* **Singal: 0x17 = 23**
273 +* **Mod: 0x01 = 1**
274 +* **Calculate Flag: 0x00= 0**
275 +* **Contact Status: 0x00= 0**
276 +* **Alarm:0x00 =0**
277 +* **Total pulse:0x09 =0**
278 +* **The last open duration:0x02 =2**
279 +* **Time stamp : 0x6315537b =1662342011**
280 +* **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp : 0100000b0200002663510fed**
281 +* **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp : 0100000e0200002663510f39,.......**
272 272  
273 -*(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
283 +**2.4  Payload Explanation and Sensor Interface**
274 274  
275 -*(% style="color:#037691" %) **Singal: **(%%)0x17 = 23
285 +**2.4.1  Device ID**
276 276  
277 -*(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
278 -
279 -*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00= 0
280 -
281 -*(% style="color:#037691" %) **Contact Status:**(%%) 0x00= 0
282 -
283 -*(% style="color:#037691" %) **Alarm:**(%%)0x00 =0
284 -
285 -*(% style="color:#037691" %) **Total pulse:0x09 =0**
286 -
287 -*(% style="color:#037691" %) **The last open duration:**(%%)0x02 =2
288 -
289 -*(% style="color:#037691" %)**Time stamp :**(%%) 0x6315537b =1662342011
290 -
291 -*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000b0200002663510fed
292 -
293 -*(% style="color:#037691" %) **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
294 -
295 -== **2.4  Payload Explanation and Sensor Interface** ==
296 -
297 -=== **2.4.1  Device ID** ===
298 -
299 299  By default, the Device ID equal to the last 15 bits of IMEI.
300 300  
301 301  User can use **AT+DEUI** to set Device ID
... ... @@ -306,13 +306,13 @@
306 306  
307 307  The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
308 308  
309 -=== **2.4.2  Version Info** ===
297 +**2.4.2  Version Info**
310 310  
311 311  Specify the software version: 0x64=100, means firmware version 1.00.
312 312  
313 313  For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0.
314 314  
315 -=== **2.4.3  Battery Info** ===
303 +**2.4.3  Battery Info**
316 316  
317 317  Check the battery voltage for CPN01.
318 318  
... ... @@ -320,7 +320,7 @@
320 320  
321 321  Ex2: 0x0B49 = 2889mV
322 322  
323 -=== **2.4.4  Signal Strength** ===
311 +**2.4.4  Signal Strength**
324 324  
325 325  NB-IoT Network signal Strength.
326 326  
... ... @@ -336,7 +336,7 @@
336 336  
337 337  **99**    Not known or not detectable
338 338  
339 -=== **2.4.5 Calculate Flag** ===
327 +**2.4.5 Calculate Flag**
340 340  
341 341  The calculate flag is a user define field, IoT server can use this filed to handle different meter with different pulse factor. For example, if there are 100 water meters, meter 1 ~~50 are 1 liter/pulse and meter 51 ~~ 100 has 1.5 liter/pulse.
342 342  
... ... @@ -346,32 +346,32 @@
346 346  
347 347  Range (6 bits): (b)000000 ~~ (b) 111111
348 348  
349 -=== **2.4.6  Alarm** ===
337 +**2.4.6  Alarm**
350 350  
351 351  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]]
352 352  
353 -=== **2.4.7 Contact Status** ===
341 +**2.4.7 Contact Status**
354 354  
355 355  0: Open
356 356  
357 357  1: Close
358 358  
359 -=== **2.4.8 Total pulse** ===
347 +**2.4.8 Total pulse**
360 360  
361 361  Total pulse/counting base 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]]
362 362  
363 363  Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
364 364  
365 -=== **2.4.9 The last open duration** ===
353 +**2.4.9 The last open duration**
366 366  
367 367  Dry Contact last open duration.
368 368  
369 369  Unit: min.
370 370  
371 -[[image:image-20221021111346-17.png||height="146" width="770"]]
359 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image017.png]]
372 372  
373 373  
374 -=== **2.4.10  Timestamp** ===
362 +**2.4.10  Timestamp**
375 375  
376 376  Time stamp : 0x6315537b =1662342011
377 377  
... ... @@ -379,11 +379,11 @@
379 379  
380 380  **~ **
381 381  
382 -== **2.5  Downlink Payload** ==
370 +**2.5  Downlink Payload**
383 383  
384 384  By default, CPN01 prints the downlink payload to console port.
385 385  
386 -[[image:image-20221021111414-18.png]] ​
374 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image018.png||alt="说明: image-20220708133731-5.png"]] ​
387 387  
388 388  **Examples:**
389 389  
... ... @@ -403,7 +403,7 @@
403 403  
404 404  Downlink Payload: 06000003, Set AT+INTMOD=3
405 405  
406 -== **2.6  ​LED Indicator** ==
394 +**2.6  ​LED Indicator**
407 407  
408 408  The CPN01 has an internal LED which is to show the status of different state.
409 409  
... ... @@ -412,7 +412,7 @@
412 412  * After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
413 413  * For each uplink probe, LED will be on for 500ms.
414 414  
415 -== **2.7  Alarm Base on Timeout** ==
403 +**2.7 ** Alarm Base on Timeout
416 416  
417 417  CPL01 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:
418 418  
... ... @@ -439,7 +439,7 @@
439 439  
440 440  **AT+TTIG=0,0 ** ~-~-> Default Value, disable timeout Alarm.
441 441  
442 -== **2.8 Set debug mode** ==
430 +**2.8** Set debug mode
443 443  
444 444  Feature: Enable or Disable debug mode
445 445  
... ... @@ -446,42 +446,49 @@
446 446  
447 447  **AT Command: AT+DEBUG**
448 448  
449 -[[image:image-20221021111629-21.png]]
437 +|**Command Example**|**Function**|**Response**
438 +|AT+DEBUG =0|Disable debug mode to 0|OK
439 +|AT+ DEBUG =1|Enable debug mode to 1|OK
450 450  
451 -== **2.9 Clear Flash Record** ==
441 +== 2.9 Clear Flash Record ==
452 452  
453 453  Feature: Clear flash storage for data log feature.
454 454  
455 455  **AT Command: AT+CLRDTA**
456 456  
457 -[[image:image-20221021111527-19.png]]
447 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image019.png||alt="说明: image-20220609151132-7.png"]]
458 458  
459 -== ** 2.10 Set trigger mode** ==
449 +**~ 2.10 **Set trigger mode
460 460  
461 461  ➢ AT Command: **AT+TTRMOD**
462 462  
463 463  Feature: Set the trigger interrupt mode.
464 464  
465 -[[image:image-20221021111552-20.png]]
455 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image020.png||alt="说明: image-20220609151344-9.png"]]
466 466  
467 -== **2.11 Set the calculate flag** ==
457 +**2.11** Set the calculate flag
468 468  
469 469  Feature: Set the calculate flag
470 470  
471 471  **AT Command: AT+CALCFLAG**
472 472  
473 -[[image:image-20221021111711-22.png]]
463 +|**Command Example**|**Function**|**Response**
464 +|AT+CALCFLAG =1|Set the calculate flag to 1.|OK
465 +|AT+CALCFLAG =2|Set the calculate flag to 2.|OK
474 474  
475 -== **2.12 Set count number** ==
467 +**2.12** Set count number
476 476  
477 477  Feature: Manually set the count number
478 478  
479 479  **AT Command: AT+SETCNT**
480 480  
481 -[[image:image-20221021111748-24.png]]
473 +|**Command Example**|**Function**|**Response**
474 +|AT+ SETCNT =0|Set the count number to 0.|OK
475 +|AT+ SETCNT =100|Set the count number to 100.|OK
482 482  
483 -== **2.13 Set the number of data to be uploaded and the recording time** ==
484 484  
478 +**2.13 Set the number of data to be uploaded and the recording time**
479 +
485 485  ➢ AT Command:
486 486  
487 487  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)
... ... @@ -489,26 +489,26 @@
489 489  
490 490  AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
491 491  
492 -== **2.14 Read or Clear cached data** ==
487 +**2.14 Read or Clear cached data**
493 493  
494 494  ➢ AT Command:
495 495  
496 496  AT+CDP    ~/~/ Read cached data
497 497  
498 -[[image:image-20221021111810-25.png||height="364" width="797"]]
493 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image021.png]]
499 499  
500 500  
501 501  AT+CDP=0    ~/~/ Clear cached data ​
502 502  
503 -== **2.15  ​Firmware Change Log** ==
498 +**2.15  ​Firmware Change Log**
504 504  
505 505  Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
506 506  
507 507  Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
508 508  
509 -== **2.16  ​Battery Analysis** ==
504 +**2.16  ​Battery Analysis**
510 510  
511 -=== **2.16.1  ​Battery Type** ===
506 +**2.16.1  ​Battery Type**
512 512  
513 513  The CPN01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-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.
514 514  
... ... @@ -520,9 +520,9 @@
520 520  * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
521 521  * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
522 522  
523 -[[image:image-20221021111911-26.png]] ​
518 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image022.png||alt="说明: image-20220708140453-6.png"]] ​
524 524  
525 -=== **2.16.2  Power consumption Analyze** ===
520 +**2.16.2  Power consumption Analyze**
526 526  
527 527  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.
528 528  
... ... @@ -538,27 +538,27 @@
538 538  
539 539  And the Life expectation in difference case will be shown on the right.
540 540  
541 -[[image:image-20221021111923-27.png||height="253" width="783"]] ​
536 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image023.jpg||alt="说明: image-20220708141352-7.jpeg"]] ​
542 542  
543 -=== **2.16.3  ​Battery Note** ===
538 +**2.16.3  ​Battery Note**
544 544  
545 545  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.
546 546  
547 -=== **2.16.4  Replace the battery** ===
542 +**2.16.4  Replace the battery**
548 548  
549 549  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).
550 550  
551 -= **3. ​ Access NB-IoT Module** =
546 +**3. ​ Access NB-IoT Module**
552 552  
553 553  Users can directly access the AT command set of the NB-IoT module.
554 554  
555 555  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/]] 
556 556  
557 -[[image:image-20221021112006-28.png]] ​
552 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image024.png||alt="说明: 1657261278785-153.png"]] ​
558 558  
559 -= **4.  Using the AT Commands** =
554 +**4.  Using the AT Commands**
560 560  
561 -== **4.1  Access AT Commands** ==
556 +**4.1  Access AT Commands**
562 562  
563 563  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]]
564 564  
... ... @@ -639,9 +639,9 @@
639 639  
640 640  AT+PWORD  : Serial Access Password
641 641  
642 -= **​5.  FAQ** =
637 +**​5.  FAQ**
643 643  
644 -== **5.1 ​ How to Upgrade Firmware** ==
639 +**5.1 ​ How to Upgrade Firmware**
645 645  
646 646  User can upgrade the firmware for 1) bug fix, 2) new feature release.
647 647  
... ... @@ -649,25 +649,25 @@
649 649  
650 650  **Notice, **CPN01 **and **CPN01 **share the same mother board. They use the same connection and method to update.**
651 651  
652 -== **5.2  Can I calibrate CPN01 to different soil types?** ==
647 +**5.2  Can I calibrate CPN01 to different soil types?**
653 653  
654 654  CPN01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]].
655 655  
656 -= **6.  Trouble Shooting** =
651 +**6.  Trouble Shooting**
657 657  
658 -== **6.1  ​Connection problem when uploading firmware** ==
653 +**6.1  ​Connection problem when uploading firmware**
659 659  
660 660  **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]]
661 661  
662 -== **6.2  AT Command input doesn't work** ==
657 +**6.2  AT Command input doesn't work**
663 663  
664 664  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.
665 665  
666 -= **7. ​ Order Info** =
661 +**7. ​ Order Info**
667 667  
668 668  Part Number**:** CPN01
669 669  
670 -= **8.  Packing Info** =
665 +**8.  Packing Info**
671 671  
672 672  **Package Includes**:
673 673  
... ... @@ -679,7 +679,7 @@
679 679  * Size: 195 x 125 x 55 mm
680 680  * Weight:   420g
681 681  
682 -= **9.  Support** =
677 +**9.  Support**
683 683  
684 684  * 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.
685 685  * 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]]
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0