Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 67.4 >
edited by Xiaoling
on 2022/11/18 10:16
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,12 +1,8 @@
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  
12 12  {{toc/}}
... ... @@ -17,43 +17,26 @@
17 17  
18 18  = 1.  Introduction =
19 19  
20 -== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
21 21  
17 +== 1.1 ​ What is CPN01 NB-IoT Pulse/Contact Sensor ==
22 22  
23 -(((
24 -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.
25 -)))
26 26  
27 -(((
28 -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.
29 -)))
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.
30 30  
31 -(((
32 -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.
33 -)))
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.
34 34  
35 -(((
36 -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.
37 -)))
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.
38 38  
39 -(((
40 -NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
41 -)))
26 +CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures.
42 42  
43 -(((
44 -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.
45 -)))
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.
46 46  
47 -(((
48 -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)
49 -)))
33 +​
50 50  
51 -(((
52 -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.
53 -)))
54 54  
55 -
56 -
57 57  == ​1.2  Features ==
58 58  
59 59  
... ... @@ -61,7 +61,7 @@
61 61  * Open/Close detect
62 62  * Open/Close statistics
63 63  * Monitor Battery Level
64 -* connect two door sensors
43 +* Uplink on periodically and open/close event
65 65  * Datalog feature
66 66  * Uplink periodically
67 67  * Downlink to change configure
... ... @@ -72,22 +72,31 @@
72 72  * Micro SIM card slot for NB-IoT SIM
73 73  * 8500mAh Battery for long-term use
74 74  
75 -== 1.3  Storage & Operation ==
54 +== 1.3  Specification ==
76 76  
77 77  
78 -Temperature -40°C to +85°C
57 +(% style="color:blue" %)**Common DC Characteristics:**
79 79  
59 +* Supply Voltage: 2.1v ~~ 3.6v
60 +* Operating Temperature: -40 ~~ 85°C
80 80  
81 -== 1.4  Mechanical ==
62 +(% style="color:blue" %)**NB-IoT Spec:**
82 82  
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
83 83  
84 -[[image:image-20221117114937-4.png]]
71 +== 1.4  Installation ==
85 85  
86 86  
87 -[[image:image-20221117114949-5.png]]
74 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
88 88  
76 +[[image:image-20221021110329-1.png]]
89 89  
90 -[[image:image-20221117115010-6.png]]
78 +[[image:image-20221022234602-2.png||height="288" width="922"]]
91 91  
92 92  
93 93  
... ... @@ -94,30 +94,19 @@
94 94  == 1.5 ​ Applications ==
95 95  
96 96  
97 -[[image:image-20221117114842-3.png]]
85 +* Open/Close Detection
86 +* Pulse meter application
87 +* Dry Contact Detection
98 98  
89 +== 1.6  Mechanical ==
99 99  
100 100  
101 -== 1.6  Specification ==
92 +​[[image:image-20221021110415-3.png]]
102 102  
103 103  
104 -(% style="color:blue" %)**Common DC Characteristics:**
105 105  
106 -* Supply Voltage: 2.1v ~~ 3.6v
107 -* Operating Temperature: -40 ~~ 85°C
108 -
109 -(% style="color:blue" %)**NB-IoT Spec:**
110 -
111 -* - B1 @H-FDD: 2100MHz
112 -* - B3 @H-FDD: 1800MHz
113 -* - B8 @H-FDD: 900MHz
114 -* - B5 @H-FDD: 850MHz
115 -* - B20 @H-FDD: 800MHz
116 -* - B28 @H-FDD: 700MHz
117 -
118 118  == 1.7  Pin Definitions and Switch ==
119 119  
120 -
121 121  [[image:image-20221021110429-4.png]]
122 122  
123 123  
... ... @@ -124,7 +124,7 @@
124 124  === 1.7.1  Pin Definition ===
125 125  
126 126  
127 -The device is pre-configured to connect to a door sensor. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at:  [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]
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]]**.
128 128  
129 129  
130 130  
... ... @@ -138,9 +138,9 @@
138 138  === 1.7.3  BOOT MODE / SW1 ===
139 139  
140 140  
141 -1)  ISP:  upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run.
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.
142 142  
143 -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.
144 144  
145 145  
146 146  
... ... @@ -162,42 +162,35 @@
162 162  
163 163  
164 164  
165 -== 1.8  Magnet Distance ==
142 += 2.  Use CPN01 to communicate with IoT Server =
166 166  
167 167  
168 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
169 -
170 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
171 -
172 -
173 -
174 -= 2.  Use NDS03A to communicate with IoT Server =
175 -
176 176  == 2.1  How it works ==
177 177  
178 178  
179 -In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A.
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.
180 180  
181 -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:
182 182  
183 183  [[image:image-20221021110615-5.png]]
184 184  
185 185  
186 186  
187 -== 2.2 ​ Configure NDS03A ==
156 +== 2.2 ​ Configure CPN01 ==
188 188  
158 +
189 189  === 2.2.1 Test Requirement ===
190 190  
191 191  
192 -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:
193 193  
194 194  * Your local operator has already distributed an NB-IoT Network.
195 -* The local NB-IoT network used the band that NDS03A supports.
165 +* The local NB-IoT network used the band that CPN01 supports.
196 196  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
197 197  
198 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDS03A will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
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.
199 199  
200 -[[image:image-20221117142300-1.png]]
170 +[[image:image-20221023000439-3.png]]
201 201  
202 202   ​
203 203  
... ... @@ -213,10 +213,10 @@
213 213  
214 214  
215 215  
216 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
186 +=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
217 217  
218 218  
219 -User need to configure NDS03A via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USB to TTL adapter to connect to NDS03A and use AT Commands to configure it, as below.
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.
220 220  
221 221  (% style="color:blue" %)**Connection:**
222 222  
... ... @@ -239,11 +239,11 @@
239 239  
240 240  * Flow Control: (% style="color:red" %)**None**
241 241  
242 -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**(%%).
243 243  
244 244  ​[[image:image-20221021110817-7.png]]
245 245  
246 -NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
216 +CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
247 247  
248 248  
249 249  (% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
... ... @@ -256,20 +256,21 @@
256 256  (% style="color:red" %)**Note: if you don't have a CoAP server, you can refer this link to set up a CoAP server: **(%%)[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
257 257  
258 258  
259 -(% style="color:blue" %)**Use below commands in NDS03A:**
229 +(% style="color:blue" %)**Use below commands in CPN01:**
260 260  
261 -* (% 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
262 262  
263 -* (% 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
264 264  
265 -* (% 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
266 266  
237 +
267 267  For parameter description, please refer to AT command set
268 268  
269 269  [[image:image-20221021110948-8.png]]
270 270  
271 271  
272 -After configuring the server address and (% style="color:green" %)**reset NDS03A**(%%) (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.
273 273  
274 274  [[image:image-20221021110956-9.png]] ​
275 275  
... ... @@ -280,15 +280,14 @@
280 280  
281 281  (% style="color:blue" %)**AT Commands:**
282 282  
283 -* (% 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
284 284  
285 -* (% 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
286 286  
287 -* (% 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
288 288  
289 289  ​ [[image:image-20221021111025-10.png]]
290 290  
291 -
292 292  [[image:image-20221021111033-11.png||height="241" width="576"]]
293 293  
294 294  ​
... ... @@ -299,23 +299,22 @@
299 299  
300 300  (% style="color:blue" %)**AT Commands:**
301 301  
302 -* (% 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
303 303  
304 -* (% 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
305 305  
306 -* (% 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
307 307  
308 -* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/  Set the username of MQTT
278 +* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/Set the username of MQTT
309 309  
310 -* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/  Set the password of MQTT
280 +* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/Set the password of MQTT
311 311  
312 -* (% 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
313 313  
314 -* (% 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
315 315  
316 316  ​ [[image:image-20221021111058-12.png]]
317 317  
318 -
319 319  [[image:image-20221021111201-16.png||height="472" width="653"]]
320 320  
321 321  ​
... ... @@ -323,15 +323,14 @@
323 323  MQTT protocol has a much higher power consumption compare with UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
324 324  
325 325  
326 -
327 327  === 2.2.7 Use TCP protocol to uplink data ===
328 328  
329 329  
330 -(% style="color:blue" %)**AT Commands:**
298 +(% style="color:blue" %)**AT Commands**
331 331  
332 -* (% 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
333 333  
334 -* (% 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
335 335  
336 336  ​ [[image:image-20221021111125-14.png]]
337 337  
... ... @@ -339,87 +339,71 @@
339 339  
340 340  ​
341 341  
342 -
343 343  === 2.2.8 Change Update Interval ===
344 344  
345 345  
346 346  User can use below command to change the (% style="color:blue" %)**uplink interval**.
347 347  
348 -* (% 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)
349 349  
350 350  (% style="color:red" %)**NOTE:**
351 351  
352 -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.
353 353  
354 -
355 -
356 356  == 2.3  Uplink Payload ==
357 357  
358 358  
359 -The uplink payload includes 26 bytes in total by default.
326 +The uplink payload includes 123 bytes in total by default.
360 360  
361 -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.
362 362  
363 -(% 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
364 364  
365 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)
366 -|=(% 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**
367 -|=(% 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" %)
368 368  
369 -(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
370 -|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)(((
371 -**1-32 group**
372 -)))
373 -|(% 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.
374 374  
375 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
339 +[[image:image-20221021111201-16.png||height="572" width="792"]]
376 376  
341 +The payload is ASCII string, representative same HEX:
377 377  
378 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
379 -|=(% 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**
380 -|=(% 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(pb14)|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.4.6A0Alarm"]](pb14)|(% 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 __**
381 381  
382 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
383 -|(% 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**
384 -|(% 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:**
385 385  
386 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
387 -|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)(((
388 -**1-32 group**
389 -)))
390 -|(% 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
391 391  
392 -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
393 393  
394 -[[image:image-20221117145932-2.png]]
351 +(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
395 395  
353 +(% style="color:#037691" %) **Singal: **(%%)0x17 = 23
396 396  
397 -The payload is ASCII string, representative same HEX:
355 +(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
398 398  
399 -**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
400 400  
401 -**where:**
359 +(% style="color:#037691" %) **Contact Status:**(%%) 0x00=0
402 402  
403 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
361 +(% style="color:#037691" %) **Alarm: **(%%)0x00 =0
404 404  
405 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
363 +(% style="color:#037691" %) **Total pulse: **(%%)0x09 =0
406 406  
407 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
365 +(% style="color:#037691" %) **The last open duration: **(%%)0x02 =2
408 408  
409 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
367 +(% style="color:#037691" %)** Time stamp :**(%%) 0x6315537b =1662342011 (Unix Time)
410 410  
411 -* (% 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
412 412  
413 -* (% 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,.......
414 414  
415 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
416 416  
417 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
418 418  
419 -* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23
420 -
421 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
422 -
423 423  == 2.4  Payload Explanation and Sensor Interface ==
424 424  
425 425  
... ... @@ -437,18 +437,20 @@
437 437  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
438 438  
439 439  
392 +
440 440  === 2.4.2  Version Info ===
441 441  
442 442  
443 443  Specify the software version: 0x64=100, which means firmware version 1.00.
444 444  
445 -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.
446 446  
447 447  
401 +
448 448  === 2.4.3  Battery Info ===
449 449  
450 450  
451 -Check the battery voltage for NDS03A.
405 +Check the battery voltage for CPN01.
452 452  
453 453  Ex1: 0x0B45 = 2885mV
454 454  
... ... @@ -455,6 +455,7 @@
455 455  Ex2: 0x0B49 = 2889mV
456 456  
457 457  
412 +
458 458  === 2.4.4  Signal Strength ===
459 459  
460 460  
... ... @@ -473,39 +473,70 @@
473 473  **99**    Not known or not detectable
474 474  
475 475  
476 -=== 2.4.5  Disalarm: (default: 0) ===
477 477  
432 +=== 2.4.5  Calculate Flag ===
478 478  
479 -(% 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.
480 480  
481 -(% 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.
482 482  
483 - (% 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.
484 484  
439 +Default value: 0. 
485 485  
486 -=== 2.4.6  Keep Status & Keep Time ===
441 +Range (6 bits): (b)000000 ~~ (b) 111111
487 487  
488 488  
489 -Shows the configure value of Alarm Base on Timeout Feature
490 490  
445 +=== 2.4.6  Alarm ===
491 491  
492 -=== 2.4.7  Timestamp ===
493 493  
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]]
494 494  
495 -Timestamp : 0x6315537b =1662342011
496 496  
497 497  
452 +=== 2.4.7  Contact Status ===
498 498  
499 -=== 2.4.8  Switch Dual Channel Mode ===
500 500  
455 +0: Open
501 501  
502 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
457 +1: Close
503 503  
504 504  
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 +
505 505  == 2.5  Downlink Payload ==
506 506  
507 507  
508 -By default, NDS03A prints the downlink payload to console port.
494 +By default, CPN01 prints the downlink payload to console port.
509 509  
510 510  [[image:image-20221021111414-18.png]] ​
511 511  
... ... @@ -522,7 +522,7 @@
522 522  
523 523  * (% style="color:#037691" %)**Reset**
524 524  
525 -If payload = 0x04FF, it will reset the NDS03A
511 +If payload = 0x04FF, it will reset the NSE01
526 526  
527 527  * (% style="color:#037691" %)**INTMOD**
528 528  
... ... @@ -533,16 +533,16 @@
533 533  == 2.6  ​LED Indicator ==
534 534  
535 535  
536 -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.
537 537  
538 538  * When the device starts normally, the LED will light up for 1 second.
539 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
525 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
540 540  * For each uplink probe, LED will be on for 500ms.
541 541  
542 542  == 2.7  Alarm Base on Timeout ==
543 543  
544 544  
545 -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:
546 546  
547 547  
548 548  (% style="color:blue" %)**1. Keep Status: Status to be monitor**
... ... @@ -558,25 +558,17 @@
558 558  
559 559  If keep time = 0, Disable Alarm Base on Timeout feature.
560 560  
561 -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.
562 562  
563 563  
564 564  (% style="color:blue" %)**AT Command to configure:**
565 565  
566 -(% style="color:blue" %)**PB14 PIN:**
552 +(% 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.
567 567  
568 -(% 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. NDS03A 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.
569 -
570 570  (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
571 571  
572 572  
573 -(% style="color:blue" %)**PB15 PIN:**
574 574  
575 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
576 -
577 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
578 -
579 -
580 580  == 2.8  Set debug mode ==
581 581  
582 582  
... ... @@ -599,88 +599,79 @@
599 599  
600 600  
601 601  
602 -== 2.10  Count Mod ==
580 +== 2.10  Set trigger mode ==
603 603  
604 604  
605 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
583 +(% style="color:blue" %)**AT Command: AT+TTRMOD**
606 606  
607 -[[image:image-20221118092935-1.png]]
585 +Feature: Set the trigger interrupt mode.
608 608  
587 +[[image:image-20221021111552-20.png]]
609 609  
610 610  
611 -== 2.11  Interrupt Pin Channel Mod ==
612 612  
591 +== 2.11  Set the calculate flag ==
613 613  
614 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
615 615  
616 -[[image:image-20221118093144-2.png]]
594 +Feature: Set the calculate flag
617 617  
596 +(% style="color:blue" %)**AT Command: AT+CALCFLAG**
618 618  
598 +[[image:image-20221021111711-22.png]]
619 619  
620 -== 2.12 TTRIG1/2 timeout status alarm ==
621 621  
622 622  
623 -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 ==
624 624  
625 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
626 626  
627 -[[image:image-20221118093512-3.png]]
605 +Feature: Manually set the count number
628 628  
607 +(% style="color:blue" %)**AT Command: AT+SETCNT**
629 629  
609 +[[image:image-20221021111748-24.png]]
630 630  
631 -== 2.13  Select counting mode ==
632 632  
633 633  
634 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
613 +== 2.13  Set the number of data to be uploaded and the recording time ==
635 635  
636 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
637 637  
638 -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:**
639 639  
640 -[[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)
641 641  
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.
642 642  
643 643  
644 644  
645 -== 2.14  Set the number of data to be uploaded and the recording time ==
624 +== 2.14  Read or Clear cached data ==
646 646  
647 647  
648 648  (% style="color:blue" %)**AT Command:**
649 649  
650 -(% style="color:#037691" %)**AT+TR=900**(%%)  ~/~/  The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
651 -
652 -(% 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.
653 -
654 -
655 -== 2.15  Read or Clear cached data ==
656 -
657 -
658 -(% style="color:blue" %)**AT Command:**
659 -
660 660  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
661 661  
662 662  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
663 663  
664 -[[image:image-20221118094227-5.png]]
633 +[[image:image-20221021111810-25.png||height="364" width="797"]]
665 665  
666 666  
667 667  
668 -== 2.16  ​Firmware Change Log ==
637 +== 2.15  ​Firmware Change Log ==
669 669  
670 670  
671 -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]]
672 672  
673 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
642 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
674 674  
675 675  
676 676  
677 -== 2.17  ​Battery Analysis ==
646 +== 2.16  ​Battery Analysis ==
678 678  
679 679  
680 -=== 2.17.1  ​Battery Type ===
649 +=== 2.16.1  ​Battery Type ===
681 681  
682 682  
683 -The NDS03A 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.
652 +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.
684 684  
685 685  The battery is designed to last for several years depends on the actual use environment and update interval. 
686 686  
... ... @@ -696,7 +696,7 @@
696 696  
697 697  
698 698  
699 -=== 2.17.2  Power consumption Analyze ===
668 +=== 2.16.2  Power consumption Analyze ===
700 700  
701 701  
702 702  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.
... ... @@ -719,7 +719,7 @@
719 719  
720 720  
721 721  
722 -=== 2.17.3  ​Battery Note ===
691 +=== 2.16.3  ​Battery Note ===
723 723  
724 724  
725 725  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.
... ... @@ -726,10 +726,10 @@
726 726  
727 727  
728 728  
729 -=== 2.17.4  Replace the battery ===
698 +=== 2.16.4  Replace the battery ===
730 730  
731 731  
732 -The default battery pack of NDS03A 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).
701 +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).
733 733  
734 734  
735 735  
... ... @@ -740,7 +740,7 @@
740 740  
741 741  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/]] 
742 742  
743 -[[image:image-20221118094449-6.png]] ​
712 +[[image:image-20221021112006-28.png]] ​
744 744  
745 745  
746 746  
... ... @@ -793,21 +793,15 @@
793 793  
794 794  AT+ DEBUG   : Enable or Disable debug mode
795 795  
796 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
765 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
797 797  
798 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
767 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
799 799  
800 -AT+COUNTMOD  :  Get or Set the count mode
769 +AT+ CALCFLAG   : Get or Set the calculate flag
801 801  
802 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
771 +AT+ CLRC   : Clear current door open count
803 803  
804 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
805 805  
806 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
807 -
808 -AT+ CLRC   :  Clear current door open count
809 -
810 -
811 811  (% style="color:blue" %)**COAP Management**      
812 812  
813 813  AT+URI            : Resource parameters
... ... @@ -849,7 +849,7 @@
849 849  
850 850  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]]
851 851  
852 -(% style="color:red" %)**Notice: **(% style="color:blue" %)**NDS03A** (%%)**and (% style="color:blue" %)LDS03A(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
815 +(% 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.**
853 853  
854 854  
855 855  
... ... @@ -873,7 +873,7 @@
873 873  = 7. ​ Order Info =
874 874  
875 875  
876 -Part Number**:** NDS03A
839 +Part Number**:** CPN01
877 877  
878 878  
879 879  
... ... @@ -882,8 +882,14 @@
882 882  
883 883  (% style="color:blue" %)**Package Includes**:
884 884  
885 -* NDS03A Open/Close Door Sensor x 1
848 +* CPN01 Open/Close Sensor x 1
849 +* External antenna x 1
886 886  
851 +(% style="color:blue" %)**Dimension and weight**:
852 +
853 +* Size: 195 x 125 x 55 mm
854 +* Weight:   420g
855 +
887 887  = 9.  Support =
888 888  
889 889  
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
image-20221118094449-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.5 KB
Content

Applications

Navigation

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