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

Applications

Navigation

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