Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 61.2 >
edited by Xiaoling
on 2022/11/17 15:08
To version < 45.1 >
edited by David Huang
on 2022/10/24 09:16
>
Change comment: There is no comment for this version

Summary

Details

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

Applications

Navigation

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