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

Applications

Navigation

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