Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 32.1 >
edited by David Huang
on 2022/10/21 11:24
To version < 42.1 >
edited by Edwin Chen
on 2022/10/23 00:32
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.David
1 +XWiki.Edwin
Content
... ... @@ -5,24 +5,23 @@
5 5  
6 6  = **1. Introduction** =
7 7  
8 -== **1.1 ​**What is CPN01 **NB-IOT** Pulse/Contact Sensor ==
8 +== **1.1 ​**What is CPN01 **NB-IoT** Pulse/Contact Sensor ==
9 9  
10 -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.
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 11  
12 -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.
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 13  
14 -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.
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 15  
16 -CPL01 is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
16 +CPN01 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 include **TCP,MQTT,UDP and CoAP  **for different application requirement.
20 -\\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)
21 -\\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
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 22  
23 23  ​
24 24  
25 -
26 26  == **​1.2 Features** ==
27 27  
28 28  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
... ... @@ -31,7 +31,7 @@
31 31  * Monitor Battery Level
32 32  * Uplink on periodically and open/close event
33 33  * Datalog feature
34 -* Uplink on periodically
33 +* Uplink periodically
35 35  * Downlink to change configure
36 36  * Wall Mountable
37 37  * Outdoor Use
... ... @@ -38,7 +38,7 @@
38 38  * Ultra-Low Power consumption
39 39  * AT Commands to change parameters
40 40  * Micro SIM card slot for NB-IoT SIM
41 -* 8500mAh Battery for long term use
40 +* 8500mAh Battery for long-term use
42 42  
43 43  == **1.3  Specification** ==
44 44  
... ... @@ -58,12 +58,13 @@
58 58  
59 59  == **1.4 Installation** ==
60 60  
61 -Connect CPL01 to an Open Close sensor like below. So it can detect the open/close event.
60 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
62 62  
63 63  [[image:image-20221021110329-1.png]]
64 64  
65 -[[image:image-20221021110340-2.png]]
64 +[[image:image-20221022234602-2.png||height="288" width="922"]]
66 66  
66 +
67 67  == **1.5 ​Applications** ==
68 68  
69 69  * Open/Close Detection
... ... @@ -80,35 +80,32 @@
80 80  
81 81  === **1.7.1 Pin Definition** ===
82 82  
83 -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 +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 84  
85 +
85 85  === **1.7.2 Jumper JP2(Power ON/OFF)** ===
86 86  
87 -
88 88  Power on Device when putting this jumper.
89 89  
90 90  
91 -
92 92  === **1.7.3 BOOT MODE / SW1** ===
93 93  
94 94  
95 -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.
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.
96 96  
97 -2) Flash: work mode, the device starts to work and send out console output for further debug
96 +2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
98 98  
99 99  
100 -
101 101  === **1.7.4 Reset Button** ===
102 102  
103 103  
104 104  Press to reboot the device.
105 105  
106 -== ==
107 107  
108 108  === **1.7.5 LED** ===
109 109  
110 110  
111 -It will flash:
108 +The LED will blink when :
112 112  
113 113  1. Boot the device in flash mode
114 114  1. Send an uplink packet
... ... @@ -117,36 +117,40 @@
117 117  
118 118  == **2.1  How it works** ==
119 119  
120 -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.
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.
121 121  
122 -The diagram below shows the working flow in default firmware of CPN01:
119 +The diagram below shows the working flow in the default firmware of CPN01:
123 123  
124 124  [[image:image-20221021110615-5.png]]
125 125  
126 -== **2.2 ​ Configure the CPN01** ==
127 127  
124 +== **2.2 ​ Configure CPN01** ==
125 +
128 128  === **2.2.1 Test Requirement** ===
129 129  
130 -To use CPN01 in your city, make sure meet below requirements:
128 +To use CPN01 in your city, make sure to meet below requirements:
131 131  
132 -* Your local operator has already distributed a NB-IoT Network there.
130 +* Your local operator has already distributed an NB-IoT Network.
133 133  * The local NB-IoT network used the band that CPN01 supports.
134 134  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
135 135  
136 -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
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.
137 137  
136 +[[image:image-20221023000439-3.png]]
137 +
138 138   ​
139 139  
140 -=== **2.2.2 Insert SIM card** ===
140 +=== **2.2.2 Insert NB-IoT SIM card** ===
141 141  
142 142  Insert the NB-IoT Card get from your provider.
143 143  
144 -User need to take out the NB-IoT module and insert the SIM card like below:
144 +User needs to take out the NB-IoT module and insert the SIM card like below:
145 145  
146 146  [[image:image-20221021110745-6.png]] ​
147 147  
148 -=== **2.2.3 Connect USB – TTL to CPN01 to configure it** ===
149 149  
149 +=== **2.2.3 Connect USB – TTL to CPN01 and configure it** ===
150 +
150 150  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.
151 151  
152 152  **Connection:**
... ... @@ -165,36 +165,44 @@
165 165  * Parity:  **None**
166 166  * Flow Control: **None**
167 167  
168 -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.
169 +Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
169 169  
170 170  ​[[image:image-20221021110817-7.png]]
171 171  
173 +CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
174 +
175 +
172 172  **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]]
173 173  
178 +
174 174  === **2.2.4 Use CoAP protocol to uplink data** ===
175 175  
176 -**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/]]
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/]]
177 177  
178 -**Use below commands:**
179 179  
184 +**Use below commands in CPN01:**
185 +
180 180  * **AT+PRO=1**   ~/~/ Set to use CoAP protocol to uplink
181 -* **AT+SERVADDR=120.24.4.116,5683   ** ~/~/ to set CoAP server address and port
182 -* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path
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
183 183  
184 184  For parameter description, please refer to AT command set
185 185  
186 186  [[image:image-20221021110948-8.png]]
187 187  
188 -After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server.
189 189  
195 +After configuring the server address and **reset CPN01** (via AT+ATZ ), CPN01 will start to uplink sensor values to the CoAP server.
196 +
190 190  [[image:image-20221021110956-9.png]] ​
191 191  
199 +
192 192  === **2.2.5 Use UDP protocol to uplink data(Default protocol)** ===
193 193  
194 -This feature is supported since firmware version v1.0.1
195 195  
203 +**AT Commands:**
204 +
196 196  * **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
197 -* **AT+SERVADDR=120.24.4.116,5601   ** ~/~/ to set UDP server address and port
206 +* **AT+SERVADDR=120.24.4.116,5601   ** ~/~/ Set UDP server address and port
198 198  * **AT+CFM=1       ** ~/~/If the server does not respond, this command is unnecessary
199 199  
200 200  ​ [[image:image-20221021111025-10.png]]
... ... @@ -205,8 +205,9 @@
205 205  
206 206  === **2.2.6 Use MQTT protocol to uplink data** ===
207 207  
208 -This feature is supported since firmware version v110
209 209  
218 +**AT Commands:**
219 +
210 210  * **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
211 211  * **AT+SERVADDR=120.24.4.116,1883   ** ~/~/Set MQTT server address and port
212 212  * **AT+CLIENT=CLIENT       ** ~/~/Set up the CLIENT of MQTT
... ... @@ -221,14 +221,15 @@
221 221  
222 222  ​
223 223  
224 -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.
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.
225 225  
236 +
226 226  === **2.2.7 Use TCP protocol to uplink data** ===
227 227  
228 -This feature is supported since firmware version v110
239 +**AT Commands**
229 229  
230 230  * **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
231 -* **AT+SERVADDR=120.24.4.116,5600   ** ~/~/ to set TCP server address and port
242 +* **AT+SERVADDR=120.24.4.116,5600   ** ~/~/ Set TCP server address and port
232 232  
233 233  ​ [[image:image-20221021111125-14.png]]
234 234  
... ... @@ -240,15 +240,16 @@
240 240  
241 241  User can use below command to change the **uplink interval**.
242 242  
243 -* **AT+TDC=600      ** ~/~/ Set Update Interval to 600s
254 +* **AT+TDC=7200      ** ~/~/ Set Update Interval to 7200s (2 hours)
244 244  
245 245  **NOTE:**
246 246  
247 247  **~1. By default, the device will send an uplink message every 1 hour.**
248 248  
260 +
249 249  == **2.3  Uplink Payload** ==
250 250  
251 -In this mode, uplink payload includes 87 bytes in total by default.
263 +The uplink payload includes 87 bytes in total by default.
252 252  
253 253  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.
254 254  
... ... @@ -264,28 +264,41 @@
264 264  
265 265  The payload is ASCII string, representative same HEX:
266 266  
267 -0xf86778705021331700640c7817010001000000090000026315537b 0100000b02000002663510fed0100000e0200000263510f39010000000000000063510e85010000000000000063510d2e010000000000000063510c7a010000000000000063510bc6010000000000000063510954010000000000000063510882 where:
279 +**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 //(%%)**
268 268  
269 -* **Device ID: 0x f867787050213317 = f867787050213317**
270 -* **Version: 0x0064=100=1.0.0**
281 +where:
282 +*(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317
271 271  
272 -* **BAT: 0x0c78 = 3192 mV = 3.192V**
273 -* **Singal: 0x17 = 23**
274 -* **Mod: 0x01 = 1**
275 -* **Calculate Flag: 0x00= 0**
276 -* **Contact Status: 0x00= 0**
277 -* **Alarm:0x00 =0**
278 -* **Total pulse:0x09 =0**
279 -* **The last open duration:0x02 =2**
280 -* **Time stamp : 0x6315537b =1662342011**
281 -* **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp : 0100000b0200002663510fed**
282 -* **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp : 0100000e0200002663510f39,.......**
284 +*(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0
283 283  
286 +*(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
287 +
288 +*(% style="color:#037691" %) **Singal: **(%%)0x17 = 23
289 +
290 +*(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
291 +
292 +*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00=0
293 +
294 +*(% style="color:#037691" %) **Contact Status:**(%%) 0x00=0
295 +
296 +*(% style="color:#037691" %) **Alarm:**(%%)0x00 =0
297 +
298 +*(% style="color:#037691" %) **Total pulse:0x09 =0**
299 +
300 +*(% style="color:#037691" %) **The last open duration:**(%%)0x02 =2
301 +
302 +*(% style="color:#037691" %)** Time stamp :**(%%) 0x6315537b =1662342011 (Unix Time)
303 +
304 +*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000b0200002663510fed
305 +
306 +*(% style="color:#037691" %) **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
307 +
308 +
284 284  == **2.4  Payload Explanation and Sensor Interface** ==
285 285  
286 286  === **2.4.1  Device ID** ===
287 287  
288 -By default, the Device ID equal to the last 15 bits of IMEI.
313 +By default, the Device ID is equal to the last 15 bits of IMEI.
289 289  
290 290  User can use **AT+DEUI** to set Device ID
291 291  
... ... @@ -293,14 +293,16 @@
293 293  
294 294  AT+DEUI=868411056754138
295 295  
296 -The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
321 +The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
297 297  
323 +
298 298  === **2.4.2  Version Info** ===
299 299  
300 -Specify the software version: 0x64=100, means firmware version 1.00.
326 +Specify the software version: 0x64=100, which means firmware version 1.00.
301 301  
302 -For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0.
328 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
303 303  
330 +
304 304  === **2.4.3  Battery Info** ===
305 305  
306 306  Check the battery voltage for CPN01.
... ... @@ -309,6 +309,7 @@
309 309  
310 310  Ex2: 0x0B49 = 2889mV
311 311  
339 +
312 312  === **2.4.4  Signal Strength** ===
313 313  
314 314  NB-IoT Network signal Strength.
... ... @@ -325,9 +325,10 @@
325 325  
326 326  **99**    Not known or not detectable
327 327  
356 +
328 328  === **2.4.5 Calculate Flag** ===
329 329  
330 -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.
359 +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.
331 331  
332 332  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.
333 333  
... ... @@ -335,10 +335,12 @@
335 335  
336 336  Range (6 bits): (b)000000 ~~ (b) 111111
337 337  
367 +
338 338  === **2.4.6  Alarm** ===
339 339  
340 340  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]]
341 341  
372 +
342 342  === **2.4.7 Contact Status** ===
343 343  
344 344  0: Open
... ... @@ -345,12 +345,14 @@
345 345  
346 346  1: Close
347 347  
379 +
348 348  === **2.4.8 Total pulse** ===
349 349  
350 -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]]
382 +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]]
351 351  
352 352  Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
353 353  
386 +
354 354  === **2.4.9 The last open duration** ===
355 355  
356 356  Dry Contact last open duration.
... ... @@ -362,7 +362,7 @@
362 362  
363 363  === **2.4.10  Timestamp** ===
364 364  
365 -Time stamp : 0x6315537b =1662342011
398 +Timestamp : 0x6315537b =1662342011
366 366  
367 367  Convert Unix timestamp to time 2022-9-5 9:40:11.
368 368  
... ... @@ -394,7 +394,7 @@
394 394  
395 395  == **2.6  ​LED Indicator** ==
396 396  
397 -The CPN01 has an internal LED which is to show the status of different state.
430 +The CPN01 has an internal LED which is to show the status of different states.
398 398  
399 399  * When power on, CPN01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
400 400  * Then the LED will be on for 1 second means device is boot normally.
... ... @@ -401,9 +401,10 @@
401 401  * After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
402 402  * For each uplink probe, LED will be on for 500ms.
403 403  
437 +
404 404  == **2.7  Alarm Base on Timeout** ==
405 405  
406 -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:
440 +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:
407 407  
408 408  
409 409  **~1. Keep Status: Status to be monitor**
... ... @@ -424,10 +424,11 @@
424 424  
425 425  **AT Command** to configure:
426 426  
427 -**AT+TTRIG=1,30**  ~-~-> When the **Keep Status** change from connect to disconnect, and device remains in disconnect status for more than 30 seconds. CPL01 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 +**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.
428 428  
429 429  **AT+TTIG=0,0 ** ~-~-> Default Value, disable timeout Alarm.
430 430  
465 +
431 431  == **2.8 Set debug mode** ==
432 432  
433 433  Feature: Enable or Disable debug mode
... ... @@ -499,11 +499,11 @@
499 499  
500 500  === **2.16.1  ​Battery Type** ===
501 501  
502 -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.
537 +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.
503 503  
504 -The battery is designed to last for several years depends on the actually use environment and update interval. 
539 +The battery is designed to last for several years depends on the actual use environment and update interval. 
505 505  
506 -The battery related documents as below:
541 +The battery-related documents as below:
507 507  
508 508  * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
509 509  * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
... ... @@ -537,6 +537,7 @@
537 537  
538 538  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).
539 539  
575 +
540 540  = **3. ​ Access NB-IoT Module** =
541 541  
542 542  Users can directly access the AT command set of the NB-IoT module.
... ... @@ -636,12 +636,10 @@
636 636  
637 637  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]]
638 638  
639 -**Notice, **CPN01 **and **CPN01 **share the same mother board. They use the same connection and method to update.**
675 +**Notice, **CPN01 **and **CPL01 **share the same mother board. They use the same connection and method to update.**
640 640  
641 -== **5.2  Can I calibrate CPN01 to different soil types?** ==
677 +
642 642  
643 -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]].
644 -
645 645  = **6.  Trouble Shooting** =
646 646  
647 647  == **6.1  ​Connection problem when uploading firmware** ==
... ... @@ -648,19 +648,22 @@
648 648  
649 649  **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]]
650 650  
685 +
651 651  == **6.2  AT Command input doesn't work** ==
652 652  
653 653  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.
654 654  
690 +
655 655  = **7. ​ Order Info** =
656 656  
657 657  Part Number**:** CPN01
658 658  
695 +
659 659  = **8.  Packing Info** =
660 660  
661 661  **Package Includes**:
662 662  
663 -* CPN01 NB-IoT Soil Moisture & EC Sensor x 1
700 +* CPN01 Open/Close Sensor x 1
664 664  * External antenna x 1
665 665  
666 666  **Dimension and weight**:
image-20221022234529-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +43.3 KB
Content
image-20221022234602-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +135.7 KB
Content
image-20221023000439-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +82.1 KB
Content

Applications

Navigation

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