Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 1.5 >
edited by Xiaoling
on 2022/10/19 16:31
To version < 58.1 >
edited by Xiaoling
on 2022/11/17 11:50
>
Change comment: Uploaded new attachment "image-20221117115010-6.png", version {1}

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -CPN01- NB-IoT Outdoor Open/Close Dry Contact Sensor User Manual
1 +NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/WebHome/1652856952171-363.png?rev=1.1||alt="1652856952171-363.png"]]
2 +[[image:image-20221117105556-1.png]]
3 3  
4 4  
5 5  
... ... @@ -7,28 +7,885 @@
7 7  
8 8  
9 9  
10 +**Table of Contents：**
10 10  
11 11  
12 12  
13 13  
14 14  
16 += 1.  Introduction =
15 15  
16 16  
19 +== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
17 17  
18 18  
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 +)))
19 19  
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 +)))
20 20  
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 +)))
21 21  
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 +)))
22 22  
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 +)))
23 23  
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 +)))
24 24  
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 +)))
25 25  
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 +)))
26 26  
27 27  
55 +​
28 28  
29 29  
58 +== ​1.2  Features ==
30 30  
31 31  
61 +* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
62 +* Open/Close detect
63 +* Open/Close statistics
64 +* Monitor Battery Level
65 +* Uplink on periodically and open/close event
66 +* Datalog feature
67 +* Uplink periodically
68 +* Downlink to change configure
69 +* Wall Mountable
70 +* Outdoor Use
71 +* Ultra-Low Power consumption
72 +* AT Commands to change parameters
73 +* Micro SIM card slot for NB-IoT SIM
74 +* 8500mAh Battery for long-term use
32 32  
76 +== 1.3  Specification ==
33 33  
34 -
78 +
79 +(% style="color:blue" %)**Common DC Characteristics:**
80 +
81 +* Supply Voltage: 2.1v ~~ 3.6v
82 +* Operating Temperature: -40 ~~ 85°C
83 +
84 +(% style="color:blue" %)**NB-IoT Spec:**
85 +
86 +* - B1 @H-FDD: 2100MHz
87 +* - B3 @H-FDD: 1800MHz
88 +* - B8 @H-FDD: 900MHz
89 +* - B5 @H-FDD: 850MHz
90 +* - B20 @H-FDD: 800MHz
91 +* - B28 @H-FDD: 700MHz
92 +
93 +== 1.4  Installation ==
94 +
95 +
96 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
97 +
98 +[[image:image-20221021110329-1.png]]
99 +
100 +
101 +[[image:image-20221022234602-2.png||height="288" width="922"]]
102 +
103 +
104 +
105 +== 1.5 ​ Applications ==
106 +
107 +
108 +* Open/Close Detection
109 +* Pulse meter application
110 +* Dry Contact Detection
111 +
112 +== 1.6  Mechanical ==
113 +
114 +
115 +​[[image:image-20221021110415-3.png]]
116 +
117 +
118 +
119 +== 1.7  Pin Definitions and Switch ==
120 +
121 +
122 +[[image:image-20221021110429-4.png]]
123 +
124 +
125 +=== 1.7.1  Pin Definition ===
126 +
127 +
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 +
130 +
131 +
132 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
133 +
134 +
135 +Power on Device when putting this jumper.
136 +
137 +
138 +
139 +=== 1.7.3  BOOT MODE / SW1 ===
140 +
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.
143 +
144 +2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
145 +
146 +
147 +
148 +=== 1.7.4  Reset Button ===
149 +
150 +
151 +Press to reboot the device.
152 +
153 +
154 +
155 +=== 1.7.5  LED ===
156 +
157 +
158 +The LED will blink when :
159 +
160 +1.  Boot the device in flash mode
161 +
162 +2.  Send an uplink packet
163 +
164 +
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 +The diagram below shows the working flow in the default firmware of CPN01:
175 +
176 +[[image:image-20221021110615-5.png]]
177 +
178 +
179 +
180 +== 2.2 ​ Configure CPN01 ==
181 +
182 +
183 +=== 2.2.1 Test Requirement ===
184 +
185 +
186 +To use CPN01 in your city, make sure to meet below requirements:
187 +
188 +* Your local operator has already distributed an NB-IoT Network.
189 +* The local NB-IoT network used the band that CPN01 supports.
190 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
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.
193 +
194 +[[image:image-20221023000439-3.png]]
195 +
196 + ​
197 +
198 +
199 +=== 2.2.2 Insert NB-IoT SIM card ===
200 +
201 +
202 +Insert the NB-IoT Card get from your provider.
203 +
204 +User needs to take out the NB-IoT module and insert the SIM card like below:
205 +
206 +[[image:image-20221021110745-6.png]] ​
207 +
208 +
209 +
210 +=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
211 +
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.
214 +
215 +(% style="color:blue" %)**Connection:**
216 +
217 +(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
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 +In the PC, use below serial tool settings:
225 +
226 +* Baud:  (% style="color:red" %)**9600**
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 +Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
237 +
238 +​[[image:image-20221021110817-7.png]]
239 +
240 +CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
241 +
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]]
244 +
245 +
246 +
247 +=== 2.2.4 Use CoAP protocol to uplink data ===
248 +
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/]]
251 +
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 +For parameter description, please refer to AT command set
262 +
263 +[[image:image-20221021110948-8.png]]
264 +
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.
267 +
268 +[[image:image-20221021110956-9.png]] ​
269 +
270 +
271 +
272 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
273 +
274 +
275 +(% style="color:blue" %)**AT Commands:**
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 +​ [[image:image-20221021111025-10.png]]
284 +
285 +
286 +[[image:image-20221021111033-11.png||height="241" width="576"]]
287 +
288 +​
289 +
290 +
291 +=== 2.2.6 Use MQTT protocol to uplink data ===
292 +
293 +
294 +(% style="color:blue" %)**AT Commands:**
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 +​ [[image:image-20221021111058-12.png]]
311 +
312 +
313 +[[image:image-20221021111201-16.png||height="472" width="653"]]
314 +
315 +​
316 +
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 +
319 +
320 +
321 +=== 2.2.7 Use TCP protocol to uplink data ===
322 +
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 +​ [[image:image-20221021111125-14.png]]
331 +
332 +[[image:image-20221021111131-15.png]]
333 +
334 +​
335 +
336 +
337 +=== 2.2.8 Change Update Interval ===
338 +
339 +
340 +User can use below command to change the (% style="color:blue" %)**uplink interval**.
341 +
342 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
343 +
344 +(% style="color:red" %)**NOTE:**
345 +
346 +1.  By default, the device will send an uplink message every 1 hour.
347 +
348 +
349 +
350 +== 2.3  Uplink Payload ==
351 +
352 +
353 +The uplink payload includes 123 bytes in total by default.
354 +
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 +
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"]]
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 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
367 +
368 +[[image:image-20221021111201-16.png||height="572" width="792"]]
369 +
370 +
371 +The payload is ASCII string, representative same HEX:
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 __**
374 +
375 +**where:**
376 +
377 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
378 +
379 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
380 +
381 +* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
382 +
383 +* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
384 +
385 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
386 +
387 +* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
388 +
389 +* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
390 +
391 +* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
392 +
393 +* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
394 +
395 +* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
396 +
397 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
398 +
399 +* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
400 +
401 +* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
402 +
403 +== 2.4  Payload Explanation and Sensor Interface ==
404 +
405 +
406 +=== 2.4.1  Device ID ===
407 +
408 +
409 +By default, the Device ID is equal to the last 15 bits of IMEI.
410 +
411 +User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
412 +
413 +**Example:**
414 +
415 +AT+DEUI=868411056754138
416 +
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 +
419 +
420 +
421 +=== 2.4.2  Version Info ===
422 +
423 +
424 +Specify the software version: 0x64=100, which means firmware version 1.00.
425 +
426 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
427 +
428 +
429 +
430 +=== 2.4.3  Battery Info ===
431 +
432 +
433 +Check the battery voltage for CPN01.
434 +
435 +Ex1: 0x0B45 = 2885mV
436 +
437 +Ex2: 0x0B49 = 2889mV
438 +
439 +
440 +
441 +=== 2.4.4  Signal Strength ===
442 +
443 +
444 +NB-IoT Network signal Strength.
445 +
446 +**Ex1: 0x1d = 29**
447 +
448 +**0**  -113dBm or less
449 +
450 +**1**  -111dBm
451 +
452 +**2...30** -109dBm... -53dBm
453 +
454 +**31**   -51dBm or greater
455 +
456 +**99**    Not known or not detectable
457 +
458 +
459 +
460 +=== 2.4.5  Calculate Flag ===
461 +
462 +
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 +
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.
466 +
467 +Default value: 0. 
468 +
469 +Range (6 bits): (b)000000 ~~ (b) 111111
470 +
471 +
472 +
473 +=== 2.4.6  Alarm ===
474 +
475 +
476 +See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
477 +
478 +
479 +
480 +=== 2.4.7  Contact Status ===
481 +
482 +
483 +0: Open
484 +
485 +1: Close
486 +
487 +
488 +
489 +=== 2.4.8  Total pulse ===
490 +
491 +
492 +Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
493 +
494 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
495 +
496 +
497 +
498 +=== 2.4.9  The last open duration ===
499 +
500 +
501 +Dry Contact last open duration.
502 +
503 +Unit: min.
504 +
505 +[[image:image-20221021111346-17.png||height="146" width="770"]]
506 +
507 +
508 +
509 +=== 2.4.10  Timestamp ===
510 +
511 +
512 +Timestamp : 0x6315537b =1662342011
513 +
514 +Convert Unix timestamp to time 2022-9-5 9:40:11.
515 +
516 +**~ **
517 +
518 +
519 +== 2.5  Downlink Payload ==
520 +
521 +
522 +By default, CPN01 prints the downlink payload to console port.
523 +
524 +[[image:image-20221021111414-18.png]] ​
525 +
526 +
527 +**Examples:**
528 +
529 +* (% style="color:#037691" %)**Set TDC**
530 +
531 +If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
532 +
533 +Payload:    01 00 00 1E    TDC=30S
534 +
535 +Payload:    01 00 00 3C    TDC=60S
536 +
537 +* (% style="color:#037691" %)**Reset**
538 +
539 +If payload = 0x04FF, it will reset the NSE01
540 +
541 +* (% style="color:#037691" %)**INTMOD**
542 +
543 +Downlink Payload: 06000003, Set AT+INTMOD=3
544 +
545 +
546 +
547 +== 2.6  ​LED Indicator ==
548 +
549 +
550 +The CPN01 has an internal LED which is to show the status of different states.
551 +
552 +* When the device starts normally, the LED will light up for 1 second.
553 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
554 +* For each uplink probe, LED will be on for 500ms.
555 +
556 +== 2.7  Alarm Base on Timeout ==
557 +
558 +
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 +
561 +
562 +(% style="color:blue" %)**1. Keep Status: Status to be monitor**
563 +
564 +Keep Status = 1: Monitor Close to Open event
565 +
566 +Keep Status = 0: Monitor Open to Close event
567 +
568 +
569 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
570 +
571 +Range 0 ~~ 65535(0xFFFF) seconds.
572 +
573 +If keep time = 0, Disable Alarm Base on Timeout feature.
574 +
575 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
576 +
577 +
578 +(% style="color:blue" %)**AT Command to configure:**
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.
581 +
582 +(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
583 +
584 +
585 +
586 +== 2.8  Set debug mode ==
587 +
588 +
589 +Feature: Enable or Disable debug mode
590 +
591 +(% style="color:blue" %)**AT Command: AT+DEBUG**
592 +
593 +[[image:image-20221021111629-21.png]]
594 +
595 +
596 +
597 +== 2.9  Clear Flash Record ==
598 +
599 +
600 +Feature: Clear flash storage for data log feature.
601 +
602 +(% style="color:blue" %)**AT Command: AT+CLRDTA**
603 +
604 +[[image:image-20221021111527-19.png]]
605 +
606 +
607 +
608 +== 2.10  Set trigger mode ==
609 +
610 +
611 +(% style="color:blue" %)**AT Command: AT+TTRMOD**
612 +
613 +Feature: Set the trigger interrupt mode.
614 +
615 +[[image:image-20221021111552-20.png]]
616 +
617 +
618 +
619 +== 2.11  Set the calculate flag ==
620 +
621 +
622 +Feature: Set the calculate flag
623 +
624 +(% style="color:blue" %)**AT Command: AT+CALCFLAG**
625 +
626 +[[image:image-20221021111711-22.png]]
627 +
628 +
629 +
630 +== 2.12 Set count number ==
631 +
632 +
633 +Feature: Manually set the count number
634 +
635 +(% style="color:blue" %)**AT Command: AT+SETCNT**
636 +
637 +[[image:image-20221021111748-24.png]]
638 +
639 +
640 +
641 +== 2.13  Set the number of data to be uploaded and the recording time ==
642 +
643 +
644 +(% style="color:blue" %)**AT Command:**
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)
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.
649 +
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 +[[image:image-20221021111810-25.png||height="364" width="797"]]
662 +
663 +
664 +
665 +== 2.15  ​Firmware Change Log ==
666 +
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]]
669 +
670 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
671 +
672 +
673 +
674 +== 2.16  ​Battery Analysis ==
675 +
676 +
677 +=== 2.16.1  ​Battery Type ===
678 +
679 +
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 +
682 +The battery is designed to last for several years depends on the actual use environment and update interval. 
683 +
684 +The battery-related documents as below:
685 +
686 +* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
687 +
688 +* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
689 +
690 +* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
691 +
692 +[[image:image-20221021111911-26.png]] ​
693 +
694 +
695 +
696 +=== 2.16.2  Power consumption Analyze ===
697 +
698 +
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 +
701 +Instruction to use as below:
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/]]
704 +
705 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
706 +
707 +* Product Model
708 +
709 +* Uplink Interval
710 +
711 +* Working Mode
712 +
713 +And the Life expectation in difference case will be shown on the right.
714 +
715 +[[image:1666596205057-567.png]] ​
716 +
717 +
718 +
719 +=== 2.16.3  ​Battery Note ===
720 +
721 +
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 +
724 +
725 +
726 +=== 2.16.4  Replace the battery ===
727 +
728 +
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 +
731 +
732 +
733 += 3. ​ Access NB-IoT Module =
734 +
735 +
736 +Users can directly access the AT command set of the NB-IoT module.
737 +
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 +
740 +[[image:image-20221021112006-28.png]] ​
741 +
742 +
743 +
744 += 4.  Using the AT Commands =
745 +
746 +
747 +== 4.1  Access AT Commands ==
748 +
749 +
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 +
752 +AT+<CMD>?  : Help on <CMD>
753 +
754 +AT+<CMD>         : Run <CMD>
755 +
756 +AT+<CMD>=<value> : Set the value
757 +
758 +AT+<CMD>=?  : Get the value
759 +
760 +
761 +(% style="color:blue" %)**General Commands**      
762 +
763 +AT  : Attention       
764 +
765 +AT?  : Short Help     
766 +
767 +ATZ  : MCU Reset    
768 +
769 +AT+TDC  : Application Data Transmission Interval
770 +
771 +AT+CFG  : Print all configurations
772 +
773 +AT+CFGMOD           : Working mode selection
774 +
775 +AT+INTMOD            : Set the trigger interrupt mode
776 +
777 +AT+5VT  : Set extend the time of 5V power  
778 +
779 +AT+PRO  : Choose agreement
780 +
781 +AT+RXDL  : Extend the sending and receiving time
782 +
783 +AT+SERVADDR  : Server Address
784 +
785 +AT+TR      :  Get or Set record time
786 +
787 +AT+NOUD      : Get or Set the number of data to be uploaded
788 +
789 +AT+CDP     :  Read or Clear cached data
790 +
791 +AT+ DEBUG   : Enable or Disable debug mode
792 +
793 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
794 +
795 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
796 +
797 +AT+ CALCFLAG   : Get or Set the calculate flag
798 +
799 +AT+ CLRC   : Clear current door open count
800 +
801 +
802 +(% style="color:blue" %)**COAP Management**      
803 +
804 +AT+URI            : Resource parameters
805 +
806 +
807 +(% style="color:blue" %)**UDP Management**
808 +
809 +AT+CFM          : Upload confirmation mode (only valid for UDP)
810 +
811 +
812 +(% style="color:blue" %)**MQTT Management**
813 +
814 +AT+CLIENT               : Get or Set MQTT client
815 +
816 +AT+UNAME  : Get or Set MQTT Username
817 +
818 +AT+PWD                  : Get or Set MQTT password
819 +
820 +AT+PUBTOPIC  : Get or Set MQTT publish topic
821 +
822 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
823 +
824 +
825 +(% style="color:blue" %)**Information**          
826 +
827 +AT+FDR  : Factory Data Reset
828 +
829 +AT+PWORD  : Serial Access Password
830 +
831 +
832 +
833 += ​5.  FAQ =
834 +
835 +
836 +== 5.1 ​ How to Upgrade Firmware ==
837 +
838 +
839 +User can upgrade the firmware for 1) bug fix, 2) new feature release.
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]]
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.**
844 +
845 +
846 +
847 += 6.  Trouble Shooting =
848 +
849 +
850 +== 6.1  ​Connection problem when uploading firmware ==
851 +
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 +
855 +
856 +
857 +== 6.2  AT Command input doesn't work ==
858 +
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.
861 +
862 +
863 +
864 += 7. ​ Order Info =
865 +
866 +
867 +Part Number**:** CPN01
868 +
869 +
870 +
871 += 8.  Packing Info =
872 +
873 +
874 +(% style="color:blue" %)**Package Includes**:
875 +
876 +* CPN01 Open/Close Sensor x 1
877 +* External antenna x 1
878 +
879 +(% style="color:blue" %)**Dimension and weight**:
880 +
881 +* Size: 195 x 125 x 55 mm
882 +* Weight:   420g
883 +
884 += 9.  Support =
885 +
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 +
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 +
891 +​
1666596205057-567.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +179.8 KB
Content
image-20221021110329-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +127.0 KB
Content
image-20221021110340-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +37.2 KB
Content
image-20221021110415-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +48.6 KB
Content
image-20221021110429-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +176.7 KB
Content
image-20221021110615-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +112.8 KB
Content
image-20221021110745-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +419.3 KB
Content
image-20221021110817-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +296.3 KB
Content
image-20221021110948-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +66.8 KB
Content
image-20221021110956-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +59.8 KB
Content
image-20221021111025-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +21.6 KB
Content
image-20221021111033-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +45.3 KB
Content
image-20221021111058-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +70.7 KB
Content
image-20221021111108-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +58.1 KB
Content
image-20221021111125-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +60.1 KB
Content
image-20221021111131-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +55.5 KB
Content
image-20221021111201-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +63.8 KB
Content
image-20221021111346-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +14.6 KB
Content
image-20221021111414-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +32.1 KB
Content
image-20221021111527-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +7.3 KB
Content
image-20221021111552-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +10.6 KB
Content
image-20221021111629-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +9.6 KB
Content
image-20221021111711-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +10.1 KB
Content
image-20221021111730-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +6.6 KB
Content
image-20221021111748-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +10.1 KB
Content
image-20221021111810-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +75.7 KB
Content
image-20221021111911-26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +179.7 KB
Content
image-20221021111923-27.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +130.6 KB
Content
image-20221021112006-28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.5 KB
Content
image-20221022234529-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +43.3 KB
Content
image-20221022234602-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +135.7 KB
Content
image-20221023000439-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +82.1 KB
Content
image-20221117105556-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +133.3 KB
Content
image-20221117114459-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +14.9 KB
Content
image-20221117114842-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +964.1 KB
Content
image-20221117114937-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +79.1 KB
Content
image-20221117114949-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +33.4 KB
Content
image-20221117115010-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +40.4 KB
Content

Applications

Navigation

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