Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 66.2 >
edited by Xiaoling
on 2022/11/18 09:43
To version < 48.2 >
edited by Xiaoling
on 2022/10/24 15:43
>
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
Content
... ... @@ -1,57 +1,38 @@
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 4  
5 5  
6 -
7 -
8 -
9 -
10 10  **Table of Contents：**
11 11  
8 +{{toc/}}
12 12  
13 13  
14 14  
15 15  
13 +
16 16  = 1.  Introduction =
17 17  
18 -== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
19 19  
17 +== 1.1 ​ What is CPN01 NB-IoT Pulse/Contact Sensor ==
20 20  
21 -(((
22 -The Dragino NDS03A is an (% style="color:blue" %)**Open/Close NB-IoT Door Sensor**(%%). It detects door (% style="color:blue" %)**open/close status**(%%) and (% style="color:blue" %)**uplinks**(%%) to IoT server via NB-IoT network. NDS03A can connect two door sensors. user can see the door status, open duration, open counts in the IoT Server.
23 -)))
24 24  
25 -(((
26 -The NDS03A will send periodically data (% style="color:blue" %)**every 4 hours** (%%)as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically.
27 -)))
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.
28 28  
29 -(((
30 -NDS03A has a (% style="color:blue" %)**Datalog feature**(%%), it will record the open/close event and the user can retrieve the history from NB-IoT.
31 -)))
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 32  
33 -(((
34 -NDS03A has the(% style="color:blue" %)**open alarm feature**(%%), user can set this feature so the device will send an alarm if the door has been open for a certain time.
35 -)))
24 +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.
36 36  
37 -(((
38 -NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
39 -)))
26 +CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures.
40 40  
41 -(((
42 -NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technologyTCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
43 -)))
28 +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.
29 +\\CPN01 supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
30 +\\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)
31 +\\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.
44 44  
45 -(((
46 -NDS03A is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
47 -)))
33 +​
48 48  
49 -(((
50 -To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into NDS03A to get NB-IoT network connection.
51 -)))
52 52  
53 -
54 -
55 55  == ​1.2  Features ==
56 56  
57 57  
... ... @@ -59,7 +59,7 @@
59 59  * Open/Close detect
60 60  * Open/Close statistics
61 61  * Monitor Battery Level
62 -* connect two door sensors
43 +* Uplink on periodically and open/close event
63 63  * Datalog feature
64 64  * Uplink periodically
65 65  * Downlink to change configure
... ... @@ -70,22 +70,31 @@
70 70  * Micro SIM card slot for NB-IoT SIM
71 71  * 8500mAh Battery for long-term use
72 72  
73 -== 1.3  Storage & Operation ==
54 +== 1.3  Specification ==
74 74  
75 75  
76 -Temperature -40°C to +85°C
57 +(% style="color:blue" %)**Common DC Characteristics:**
77 77  
59 +* Supply Voltage: 2.1v ~~ 3.6v
60 +* Operating Temperature: -40 ~~ 85°C
78 78  
79 -== 1.4  Mechanical ==
62 +(% style="color:blue" %)**NB-IoT Spec:**
80 80  
64 +* - B1 @H-FDD: 2100MHz
65 +* - B3 @H-FDD: 1800MHz
66 +* - B8 @H-FDD: 900MHz
67 +* - B5 @H-FDD: 850MHz
68 +* - B20 @H-FDD: 800MHz
69 +* - B28 @H-FDD: 700MHz
81 81  
82 -[[image:image-20221117114937-4.png]]
71 +== 1.4  Installation ==
83 83  
84 84  
85 -[[image:image-20221117114949-5.png]]
74 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
86 86  
76 +[[image:image-20221021110329-1.png]]
87 87  
88 -[[image:image-20221117115010-6.png]]
78 +[[image:image-20221022234602-2.png||height="288" width="922"]]
89 89  
90 90  
91 91  
... ... @@ -92,30 +92,19 @@
92 92  == 1.5 ​ Applications ==
93 93  
94 94  
95 -[[image:image-20221117114842-3.png]]
85 +* Open/Close Detection
86 +* Pulse meter application
87 +* Dry Contact Detection
96 96  
89 +== 1.6  Mechanical ==
97 97  
98 98  
99 -== 1.6  Specification ==
92 +​[[image:image-20221021110415-3.png]]
100 100  
101 101  
102 -(% style="color:blue" %)**Common DC Characteristics:**
103 103  
104 -* Supply Voltage: 2.1v ~~ 3.6v
105 -* Operating Temperature: -40 ~~ 85°C
106 -
107 -(% style="color:blue" %)**NB-IoT Spec:**
108 -
109 -* - B1 @H-FDD: 2100MHz
110 -* - B3 @H-FDD: 1800MHz
111 -* - B8 @H-FDD: 900MHz
112 -* - B5 @H-FDD: 850MHz
113 -* - B20 @H-FDD: 800MHz
114 -* - B28 @H-FDD: 700MHz
115 -
116 116  == 1.7  Pin Definitions and Switch ==
117 117  
118 -
119 119  [[image:image-20221021110429-4.png]]
120 120  
121 121  
... ... @@ -122,7 +122,7 @@
122 122  === 1.7.1  Pin Definition ===
123 123  
124 124  
125 -The device is pre-configured to connect to a door sensor. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at:  [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]
104 +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]]**.
126 126  
127 127  
128 128  
... ... @@ -136,9 +136,9 @@
136 136  === 1.7.3  BOOT MODE / SW1 ===
137 137  
138 138  
139 -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.
118 +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.
140 140  
141 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
120 +2) Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
142 142  
143 143  
144 144  
... ... @@ -160,42 +160,35 @@
160 160  
161 161  
162 162  
163 -== 1.8  Magnet Distance ==
164 -
165 -
166 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
167 -
168 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
169 -
170 -
171 -
172 172  = 2.  Use CPN01 to communicate with IoT Server =
173 173  
144 +
174 174  == 2.1  How it works ==
175 175  
176 176  
177 -In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A.
148 +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.
178 178  
179 -The diagram below shows the working flow in the default firmware of NDS03A:
150 +The diagram below shows the working flow in the default firmware of CPN01:
180 180  
181 181  [[image:image-20221021110615-5.png]]
182 182  
183 183  
184 184  
185 -== 2.2 ​ Configure NDS03A ==
156 +== 2.2 ​ Configure CPN01 ==
186 186  
158 +
187 187  === 2.2.1 Test Requirement ===
188 188  
189 189  
190 -To use NDS03A in your city, make sure to meet below requirements:
162 +To use CPN01 in your city, make sure to meet below requirements:
191 191  
192 192  * Your local operator has already distributed an NB-IoT Network.
193 -* The local NB-IoT network used the band that NDS03A supports.
165 +* The local NB-IoT network used the band that CPN01 supports.
194 194  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
195 195  
196 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDS03A will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
168 +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.
197 197  
198 -[[image:image-20221117142300-1.png]]
170 +[[image:image-20221023000439-3.png]]
199 199  
200 200   ​
201 201  
... ... @@ -211,10 +211,10 @@
211 211  
212 212  
213 213  
214 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
186 +=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
215 215  
216 216  
217 -User need to configure NDS03A via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USB to TTL adapter to connect to NDS03A and use AT Commands to configure it, as below.
189 +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.
218 218  
219 219  (% style="color:blue" %)**Connection:**
220 220  
... ... @@ -237,11 +237,11 @@
237 237  
238 238  * Flow Control: (% style="color:red" %)**None**
239 239  
240 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
212 +Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
241 241  
242 242  ​[[image:image-20221021110817-7.png]]
243 243  
244 -NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
216 +CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
245 245  
246 246  
247 247  (% 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]]
... ... @@ -256,18 +256,19 @@
256 256  
257 257  (% style="color:blue" %)**Use below commands in CPN01:**
258 258  
259 -* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
231 +(% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
260 260  
261 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/ Set CoAP server address and port
233 +(% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/ Set CoAP server address and port
262 262  
263 -* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/  Set CoAP resource path
235 +(% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/  Set CoAP resource path
264 264  
237 +
265 265  For parameter description, please refer to AT command set
266 266  
267 267  [[image:image-20221021110948-8.png]]
268 268  
269 269  
270 -After configuring the server address and (% style="color:green" %)**reset CPN01**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
243 +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.
271 271  
272 272  [[image:image-20221021110956-9.png]] ​
273 273  
... ... @@ -278,15 +278,14 @@
278 278  
279 279  (% style="color:blue" %)**AT Commands:**
280 280  
281 -* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
254 +* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
282 282  
283 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  Set UDP server address and port
256 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ Set UDP server address and port
284 284  
285 -* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
258 +* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
286 286  
287 287  ​ [[image:image-20221021111025-10.png]]
288 288  
289 -
290 290  [[image:image-20221021111033-11.png||height="241" width="576"]]
291 291  
292 292  ​
... ... @@ -297,23 +297,22 @@
297 297  
298 298  (% style="color:blue" %)**AT Commands:**
299 299  
300 -* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
272 +* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
301 301  
302 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
274 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
303 303  
304 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
276 +* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/Set up the CLIENT of MQTT
305 305  
306 -* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/  Set the username of MQTT
278 +* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/Set the username of MQTT
307 307  
308 -* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/  Set the password of MQTT
280 +* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/Set the password of MQTT
309 309  
310 -* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)** **~/~/  Set the sending topic of MQTT
282 +* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)** **~/~/Set the sending topic of MQTT
311 311  
312 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
284 +* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/Set the subscription topic of MQTT
313 313  
314 314  ​ [[image:image-20221021111058-12.png]]
315 315  
316 -
317 317  [[image:image-20221021111201-16.png||height="472" width="653"]]
318 318  
319 319  ​
... ... @@ -321,15 +321,14 @@
321 321  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.
322 322  
323 323  
324 -
325 325  === 2.2.7 Use TCP protocol to uplink data ===
326 326  
327 327  
328 -(% style="color:blue" %)**AT Commands:**
298 +(% style="color:blue" %)**AT Commands**
329 329  
330 -* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
300 +* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
331 331  
332 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
302 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/ Set TCP server address and port
333 333  
334 334  ​ [[image:image-20221021111125-14.png]]
335 335  
... ... @@ -337,87 +337,71 @@
337 337  
338 338  ​
339 339  
340 -
341 341  === 2.2.8 Change Update Interval ===
342 342  
343 343  
344 344  User can use below command to change the (% style="color:blue" %)**uplink interval**.
345 345  
346 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
315 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
347 347  
348 348  (% style="color:red" %)**NOTE:**
349 349  
350 -1.  By default, the device will send an uplink message every 4 hour.
319 +*
320 +**
321 +**1. By default, the device will send an uplink message every 1 hour.
351 351  
352 -
353 -
354 354  == 2.3  Uplink Payload ==
355 355  
356 356  
357 -The uplink payload includes 26 bytes in total by default.
326 +The uplink payload includes 123 bytes in total by default.
358 358  
359 -Each time the device uploads a data package. The user can use the AT+NOUD command to upload the recorded data.Up to 32 sets of recorded data can be uploaded.
328 +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.
360 360  
361 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
330 +|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**1**|**1**|**3**
331 +|**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
362 362  
363 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)
364 -|=(% scope="row" style="width: 93px;" %)**Size(bytes)**|(% style="width:67px" %)**8**|(% style="width:40px" %)**2**|(% style="width:45px" %)**2**|(% style="width:75px" %)**1**|(% style="width:54px" %)**1**|(% style="width:62px" %)**1**|(% style="width:60px" %)**1**|(% style="width:94px" %)**3**|(% style="width:93px" %)**3**
365 -|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.4.6A0Alarm"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
333 +(% style="width:1201px" %)
334 +|**3**|**4**|**1**|**3**|**1**|**3**|4|**8 group**|(% style="width:1px" %)
335 +|The last open duration|Time stamp|Contact Status|Total pulse|Calculate Flag|The last open duration|Time stamp|...|(% style="width:1px" %)
366 366  
367 -(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
368 -|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)(((
369 -**1-32 group**
370 -)))
371 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% style="width:115px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)|(% style="width:99px" %)last open time(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
337 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
372 372  
373 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
339 +[[image:image-20221021111201-16.png||height="572" width="792"]]
374 374  
341 +The payload is ASCII string, representative same HEX:
375 375  
376 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
377 -|=(% scope="row" style="width: 96px;" %)**Size(bytes)**|(% style="width:66px" %)**8**|(% style="width:40px" %)**2**|(% style="width:46px" %)**2**|(% style="width:70px" %)**1**|(% style="width:54px" %)**1**|(% style="width:55px" %)**1**|(% style="width:57px" %)**1**|(% style="width:86px" %)**3**|(% style="width:82px" %)**3**
378 -|=(% style="width: 96px;" %)**Value**|(% style="width:66px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:70px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:55px" %)Door Status|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.4.6A0Alarm"]]|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
343 +**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 __**
379 379  
380 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
381 -|(% style="width:59px" %)**1**|(% style="width:67px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:66px" %)**1**|(% style="width:92px" %)**3**
382 -|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPN01-%20NB-IoT%20Outdoor%20OpenClose%20Dry%20Contact%20Sensor%C2%A0User%20Manual/#H2.4.7A0ContactStatus]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)Time stamp|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
345 +**where:**
383 383  
384 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
385 -|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)(((
386 -**1-32 group**
387 -)))
388 -|(% style="width:102px" %)last open time (pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:88px" %)last open time(pb15)|(% style="width:63px" %)Time stamp|(% style="width:87px" %)...
347 +(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317
389 389  
390 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
349 +(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0
391 391  
392 -[[image:image-20221117145932-2.png]]
351 +(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
393 393  
353 +(% style="color:#037691" %) **Singal: **(%%)0x17 = 23
394 394  
395 -The payload is ASCII string, representative same HEX:
355 +(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
396 396  
397 -**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0ccf__(% style="color:#00b0f0" %) __19__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__(% style="color:#660066" %) (% style="color:#aaaa40" %)__000016__(% style="color:#663300" %) __000017__ (% style="color:#d60093" %)__637590df__(%%)**
357 +(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00=0
398 398  
399 -**where:**
359 +(% style="color:#037691" %) **Contact Status:**(%%) 0x00=0
400 400  
401 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
361 +(% style="color:#037691" %) **Alarm: **(%%)0x00 =0
402 402  
403 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
363 +(% style="color:#037691" %) **Total pulse: **(%%)0x09 =0
404 404  
405 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
365 +(% style="color:#037691" %) **The last open duration: **(%%)0x02 =2
406 406  
407 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
367 +(% style="color:#037691" %)** Time stamp :**(%%) 0x6315537b =1662342011 (Unix Time)
408 408  
409 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
369 +(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 01  00000b  02  000026  63510fed
410 410  
411 -* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0
371 +(% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
412 412  
413 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
414 414  
415 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
416 416  
417 -* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23
418 -
419 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
420 -
421 421  == 2.4  Payload Explanation and Sensor Interface ==
422 422  
423 423  
... ... @@ -435,18 +435,20 @@
435 435  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
436 436  
437 437  
392 +
438 438  === 2.4.2  Version Info ===
439 439  
440 440  
441 441  Specify the software version: 0x64=100, which means firmware version 1.00.
442 442  
443 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
398 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
444 444  
445 445  
401 +
446 446  === 2.4.3  Battery Info ===
447 447  
448 448  
449 -Check the battery voltage for NDS03A.
405 +Check the battery voltage for CPN01.
450 450  
451 451  Ex1: 0x0B45 = 2885mV
452 452  
... ... @@ -453,6 +453,7 @@
453 453  Ex2: 0x0B49 = 2889mV
454 454  
455 455  
412 +
456 456  === 2.4.4  Signal Strength ===
457 457  
458 458  
... ... @@ -471,39 +471,70 @@
471 471  **99**    Not known or not detectable
472 472  
473 473  
474 -=== 2.4.5  Disalarm: (default: 0) ===
475 475  
432 +=== 2.4.5  Calculate Flag ===
476 476  
477 -(% style="color:blue" %)**If Disalarm = 1**(%%), NDS03A will only send uplink at every TDC periodically. This is normally use for pulse meter application, in this application, there are many open/close event, and platform only care about the total number of pulse.
478 478  
479 -(% style="color:blue" %)**If Disalarm = 0**(%%), NDS03A will send uplink at every TDC periodically and send data on each open/close event. This is useful for the application user need to monitor the open/close event in real-time.
435 +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.
480 480  
481 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
437 +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.
482 482  
439 +Default value: 0. 
483 483  
484 -=== 2.4.6  Keep Status & Keep Time ===
441 +Range (6 bits): (b)000000 ~~ (b) 111111
485 485  
486 486  
487 -Shows the configure value of Alarm Base on Timeout Feature
488 488  
445 +=== 2.4.6  Alarm ===
489 489  
490 -=== 2.4.7  Timestamp ===
491 491  
448 +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]]
492 492  
493 -Timestamp : 0x6315537b =1662342011
494 494  
495 495  
452 +=== 2.4.7  Contact Status ===
496 496  
497 -=== 2.4.8  Switch Dual Channel Mode ===
498 498  
455 +0: Open
499 499  
500 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
457 +1: Close
501 501  
502 502  
460 +
461 +=== 2.4.8  Total pulse ===
462 +
463 +
464 +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]]
465 +
466 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
467 +
468 +
469 +
470 +=== 2.4.9  The last open duration ===
471 +
472 +
473 +Dry Contact last open duration.
474 +
475 +Unit: min.
476 +
477 +[[image:image-20221021111346-17.png||height="146" width="770"]]
478 +
479 +
480 +
481 +=== 2.4.10  Timestamp ===
482 +
483 +
484 +Timestamp : 0x6315537b =1662342011
485 +
486 +Convert Unix timestamp to time 2022-9-5 9:40:11.
487 +
488 +**~ **
489 +
490 +
503 503  == 2.5  Downlink Payload ==
504 504  
505 505  
506 -By default, NDS03A prints the downlink payload to console port.
494 +By default, CPN01 prints the downlink payload to console port.
507 507  
508 508  [[image:image-20221021111414-18.png]] ​
509 509  
... ... @@ -520,7 +520,7 @@
520 520  
521 521  * (% style="color:#037691" %)**Reset**
522 522  
523 -If payload = 0x04FF, it will reset the NDS03A
511 +If payload = 0x04FF, it will reset the NSE01
524 524  
525 525  * (% style="color:#037691" %)**INTMOD**
526 526  
... ... @@ -531,17 +531,16 @@
531 531  == 2.6  ​LED Indicator ==
532 532  
533 533  
534 -The NDS03A has an internal LED which is to show the status of different states.
522 +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 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 -
541 541  == 2.7  Alarm Base on Timeout ==
542 542  
543 543  
544 -NDS03A 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:
531 +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:
545 545  
546 546  
547 547  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -557,25 +557,17 @@
557 557  
558 558  If keep time = 0, Disable Alarm Base on Timeout feature.
559 559  
560 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
547 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
561 561  
562 562  
563 563  (% style="color:blue" %)**AT Command to configure:**
564 564  
565 -(% style="color:blue" %)**PB14 PIN:**
566 -
567 567  (% 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.
568 568  
569 569  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
570 570  
571 571  
572 -(% style="color:blue" %)**PB15 PIN:**
573 573  
574 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
575 -
576 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
577 -
578 -
579 579  == 2.8  Set debug mode ==
580 580  
581 581  
... ... @@ -598,78 +598,69 @@
598 598  
599 599  
600 600  
601 -== 2.10  Count Mod ==
580 +== 2.10  Set trigger mode ==
602 602  
603 603  
604 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
583 +(% style="color:blue" %)**AT Command: AT+TTRMOD**
605 605  
606 -[[image:image-20221118092935-1.png]]
585 +Feature: Set the trigger interrupt mode.
607 607  
587 +[[image:image-20221021111552-20.png]]
608 608  
609 609  
610 -== 2.11  Interrupt Pin Channel Mod ==
611 611  
591 +== 2.11  Set the calculate flag ==
612 612  
613 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
614 614  
615 -[[image:image-20221118093144-2.png]]
594 +Feature: Set the calculate flag
616 616  
596 +(% style="color:blue" %)**AT Command: AT+CALCFLAG**
617 617  
598 +[[image:image-20221021111711-22.png]]
618 618  
619 -== 2.12 TTRIG1/2 timeout status alarm ==
620 620  
621 621  
622 -It needs to be used with AT+TTRIG1 or AT+TTRIG2. When TTRIG1 or TTRIG2 times out and causes an alarm, and the status does not change subsequently, an alarm packet will be sent at the alarm interval.
602 +== 2.12 Set count number ==
623 623  
624 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
625 625  
626 -[[image:image-20221118093512-3.png]]
605 +Feature: Manually set the count number
627 627  
607 +(% style="color:blue" %)**AT Command: AT+SETCNT**
628 628  
609 +[[image:image-20221021111748-24.png]]
629 629  
630 -== 2.13  Select counting mode ==
631 631  
632 632  
633 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
613 +== 2.13  Set the number of data to be uploaded and the recording time ==
634 634  
635 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
636 636  
637 -When (% style="color:red" %)**b=0**(%%), it is the last door open duration, and when (% style="color:red" %)**b=1**(%%),the last door close duration.
616 +(% style="color:blue" %)**AT Command:**
638 638  
639 -[[image:image-20221118093658-4.png]]
618 +(% 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)
640 640  
620 +(% 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.
641 641  
642 642  
643 643  
644 -== 2.14  Set the number of data to be uploaded and the recording time ==
624 +== 2.14  Read or Clear cached data ==
645 645  
646 646  
647 647  (% style="color:blue" %)**AT Command:**
648 648  
649 -(% 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)
650 -
651 -(% style="color:#037691" %)**AT+NOUD=8**(%%)** ** ~/~/  The device uploads 0 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
652 -
653 -
654 -== 2.15  Read or Clear cached data ==
655 -
656 -
657 -(% style="color:blue" %)**AT Command:**
658 -
659 659  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
660 660  
661 661  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
662 662  
663 -[[image:image-20221118094227-5.png]]
633 +[[image:image-20221021111810-25.png||height="364" width="797"]]
664 664  
665 665  
666 666  
667 -== 2.16  ​Firmware Change Log ==
637 +== 2.15  ​Firmware Change Log ==
668 668  
669 669  
670 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
640 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
671 671  
672 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
642 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
673 673  
674 674  
675 675  
image-20221117105556-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -133.3 KB
Content
image-20221117114459-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
image-20221117114842-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -964.1 KB
Content
image-20221117114937-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.1 KB
Content
image-20221117114949-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -33.4 KB
Content
image-20221117115010-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -40.4 KB
Content
image-20221117142300-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -147.8 KB
Content
image-20221117145932-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -51.9 KB
Content
image-20221117150312-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.7 KB
Content
image-20221118092935-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -13.1 KB
Content
image-20221118093144-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.7 KB
Content
image-20221118093512-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -9.5 KB
Content
image-20221118093658-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -12.7 KB
Content
image-20221118094227-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.2 KB
Content

Applications

Navigation

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