Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 70.21 >
edited by Xiaoling
on 2022/11/18 11:23
To version < 48.1 >
edited by Xiaoling
on 2022/10/24 15:23
>
Change comment: Uploaded new attachment "1666596205057-567.png", version {1}

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,67 +1,34 @@
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 -
5 -
6 -
7 -
8 -
9 -
10 -**Table of Contents：**
11 -
12 12  {{toc/}}
13 13  
6 += **1. Introduction** =
14 14  
8 +== **1.1 ​**What is CPN01 **NB-IoT** Pulse/Contact Sensor ==
15 15  
10 +The Dragino CPN01 is an (% style="color:blue" %)**NB-IoT Dry Contact Sensor**(%%). It detects open/close status and uplinks the info to IoT server via NB-IoT network. User can see the (% style="color:blue" %)**dry contact status, open time, and open counts**(%%) in the IoT Server.
16 16  
12 +The CPN01 will send periodically data every day as well as for each dry contact action. It also counts the contact open times and calculates the last open duration. Users can also disable the uplink for each Open/Close event, instead, device can count each open event and uplink periodically.
17 17  
18 -= 1.  Introduction =
14 +CPN01 has** (% style="color:blue" %)Open-Alarm feature(%%)**, user can set this feature so CPN01 will send an alarm if the contact has been open exceeds a certain time.
19 19  
20 -== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
16 +CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures.
21 21  
18 +NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
19 +\\CPN01 supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
20 +\\CPN01 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
21 +\\To use CPN01, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that CPN01 supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into CPN01 to get NB-IoT network connection.
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 -)))
23 +​
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 -)))
25 +== **​1.2 Features** ==
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 -)))
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 -)))
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 -)))
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 -)))
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 -)))
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 -
55 -
56 -
57 -== ​1.2  Features ==
58 -
59 -
60 60  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
61 61  * Open/Close detect
62 62  * Open/Close statistics
63 63  * Monitor Battery Level
64 -* connect two door sensors
31 +* Uplink on periodically and open/close event
65 65  * Datalog feature
66 66  * Uplink periodically
67 67  * Downlink to change configure
... ... @@ -72,42 +72,14 @@
72 72  * Micro SIM card slot for NB-IoT SIM
73 73  * 8500mAh Battery for long-term use
74 74  
42 +== **1.3  Specification** ==
75 75  
76 -== 1.3  Storage & Operation ==
44 +**Common DC Characteristics:**
77 77  
78 -
79 -Temperature -40°C to +85°C
80 -
81 -
82 -== 1.4  Mechanical ==
83 -
84 -
85 -[[image:image-20221117114937-4.png]]
86 -
87 -
88 -[[image:image-20221117114949-5.png]]
89 -
90 -
91 -[[image:image-20221117115010-6.png]]
92 -
93 -
94 -
95 -== 1.5 ​ Applications ==
96 -
97 -
98 -[[image:image-20221117114842-3.png]]
99 -
100 -
101 -
102 -== 1.6  Specification ==
103 -
104 -
105 -(% style="color:blue" %)**Common DC Characteristics:**
106 -
107 107  * Supply Voltage: 2.1v ~~ 3.6v
108 108  * Operating Temperature: -40 ~~ 85°C
109 109  
110 -(% style="color:blue" %)**NB-IoT Spec:**
49 +**NB-IoT Spec:**
111 111  
112 112  * - B1 @H-FDD: 2100MHz
113 113  * - B3 @H-FDD: 1800MHz
... ... @@ -116,88 +116,90 @@
116 116  * - B20 @H-FDD: 800MHz
117 117  * - B28 @H-FDD: 700MHz
118 118  
58 +== **1.4 Installation** ==
119 119  
120 -== 1.7  Pin Definitions and Switch ==
60 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
121 121  
62 +[[image:image-20221021110329-1.png]]
122 122  
123 -[[image:image-20221021110429-4.png]]
64 +[[image:image-20221022234602-2.png||height="288" width="922"]]
124 124  
125 125  
126 -=== 1.7.1  Pin Definition ===
67 +== **1.5 ​Applications** ==
127 127  
69 +* Open/Close Detection
70 +* Pulse meter application
71 +* Dry Contact Detection
128 128  
129 -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]]
73 +== **1.6 Mechanical** ==
130 130  
75 +​[[image:image-20221021110415-3.png]]
131 131  
132 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
77 +== ** 1.7 Pin Definitions and Switch** ==
133 133  
79 +[[image:image-20221021110429-4.png]]
134 134  
135 -Power on Device when putting this jumper.
81 +=== **1.7.1 Pin Definition** ===
136 136  
83 +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]]**.
137 137  
138 -=== 1.7.3  BOOT MODE / SW1 ===
139 139  
86 +=== **1.7.2 Jumper JP2(Power ON/OFF)** ===
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.
88 +Power on Device when putting this jumper.
142 142  
143 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
144 144  
91 +=== **1.7.3 BOOT MODE / SW1** ===
145 145  
146 -=== 1.7.4  Reset Button ===
147 147  
94 +1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run.
148 148  
149 -Press to reboot the device.
96 +2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
150 150  
151 151  
152 -=== 1.7.5  LED ===
99 +=== **1.7.4 Reset Button** ===
153 153  
154 154  
155 -The LED will blink when :
102 +Press to reboot the device.
156 156  
157 -1.  Boot the device in flash mode
158 158  
159 -2.  Send an uplink packet
105 +=== **1.7.5 LED** ===
160 160  
161 161  
162 -== 1.8  Magnet Distance ==
108 +The LED will blink when :
163 163  
110 +1. Boot the device in flash mode
111 +1. Send an uplink packet
164 164  
165 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
113 += **2.  Use CPN01 to communicate with IoT Server** =
166 166  
167 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
115 +== **2.1  How it works** ==
168 168  
117 +The CPN01 is equipped with an NB-IoT module, the pre-loaded firmware in CPN01 will get **Open/Close Event or Count** from sensor and send the value to the NB-IoT network. The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01.
169 169  
170 -= 2.  Use NDS03A to communicate with IoT Server =
119 +The diagram below shows the working flow in the default firmware of CPN01:
171 171  
172 -== 2.1  How it works ==
173 -
174 -
175 -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.
176 -
177 -The diagram below shows the working flow in the default firmware of NDS03A:
178 -
179 179  [[image:image-20221021110615-5.png]]
180 180  
181 181  
182 -== 2.2 ​ Configure NDS03A ==
124 +== **2.2 ​ Configure CPN01** ==
183 183  
184 -=== 2.2.1 Test Requirement ===
126 +=== **2.2.1 Test Requirement** ===
185 185  
128 +To use CPN01 in your city, make sure to meet below requirements:
186 186  
187 -To use NDS03A in your city, make sure to meet below requirements:
188 -
189 189  * Your local operator has already distributed an NB-IoT Network.
190 -* The local NB-IoT network used the band that NDS03A supports.
131 +* The local NB-IoT network used the band that CPN01 supports.
191 191  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
192 192  
193 -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.
134 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The CPN01 will use CoAP(120.24.4.116:5683) or raw UDP(120.24.4.116:5601) or MQTT(120.24.4.116:1883)or TCP(120.24.4.116:5600)protocol to send data to the test server.
194 194  
195 -[[image:image-20221117142300-1.png]]
136 +[[image:image-20221023000439-3.png]]
196 196  
138 + ​
197 197  
198 -=== 2.2.2 Insert NB-IoT SIM card ===
140 +=== **2.2.2 Insert NB-IoT SIM card** ===
199 199  
200 -
201 201  Insert the NB-IoT Card get from your provider.
202 202  
203 203  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -205,123 +205,101 @@
205 205  [[image:image-20221021110745-6.png]] ​
206 206  
207 207  
208 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
149 +=== **2.2.3 Connect USB – TTL to CPN01 and configure it** ===
209 209  
151 +User need to configure CPN01 via serial port to set the **Server Address** / **Uplink Topic** to define where and how-to uplink packets. CPN01 support AT Commands, user can use a USB to TTL adapter to connect to CPN01 and use AT Commands to configure it, as below.
210 210  
211 -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.
153 +**Connection:**
212 212  
213 -(% style="color:blue" %)**Connection:**
155 + USB TTL GND <~-~-~-~-> GND
214 214  
215 -(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
157 + USB TTL TXD <~-~-~-~-> UART_RXD
216 216  
217 -(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD**
159 + USB TTL RXD <~-~-~-~-> UART_TXD
218 218  
219 -(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD**
220 -
221 -
222 222  In the PC, use below serial tool settings:
223 223  
224 -* Baud:  (% style="color:red" %)**9600**
163 +* Baud:  **9600**
164 +* Data bits:** 8**
165 +* Stop bits: **1**
166 +* Parity:  **None**
167 +* Flow Control: **None**
225 225  
226 -* Data bits:** (% style="color:red" %)8(%%)**
169 +Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
227 227  
228 -* Stop bits: (% style="color:red" %)**1**
229 -
230 -* Parity:  (% style="color:red" %)**None**
231 -
232 -* Flow Control: (% style="color:red" %)**None**
233 -
234 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
235 -
236 236  ​[[image:image-20221021110817-7.png]]
237 237  
238 -NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
173 +CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
239 239  
240 240  
241 -(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
176 +**Note: the valid AT Commands can be found at:  **[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
242 242  
243 243  
179 +=== **2.2.4 Use CoAP protocol to uplink data** ===
244 244  
245 -=== 2.2.4 Use CoAP protocol to uplink data ===
181 +**Note: if you don't have a CoAP server, you can refer this link to set up a CoAP server: **[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
246 246  
247 247  
248 -(% style="color:red" %)**Note: if you don't have a CoAP server, you can refer this link to set up a CoAP server: **(%%)[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
184 +**Use below commands in CPN01:**
249 249  
186 +* **AT+PRO=1**   ~/~/ Set to use CoAP protocol to uplink
187 +* **AT+SERVADDR=120.24.4.116,5683   ** ~/~/ Set CoAP server address and port
188 +* **AT+URI=0,0,11,2,"mqtt" ** ~/~/Set CoAP resource path
250 250  
251 -(% style="color:blue" %)**Use below commands in NDS03A:**
252 -
253 -* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
254 -
255 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/ Set CoAP server address and port
256 -
257 -* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/  Set CoAP resource path
258 -
259 259  For parameter description, please refer to AT command set
260 260  
261 261  [[image:image-20221021110948-8.png]]
262 262  
263 263  
264 -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.
195 +After configuring the server address and **reset CPN01** (via AT+ATZ ), CPN01 will start to uplink sensor values to the CoAP server.
265 265  
266 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
197 +[[image:image-20221021110956-9.png]] ​
267 267  
268 268  
269 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
200 +=== **2.2.5 Use UDP protocol to uplink data(Default protocol)** ===
270 270  
271 271  
272 -(% style="color:blue" %)**AT Commands:**
203 +**AT Commands:**
273 273  
274 -* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
205 +* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
206 +* **AT+SERVADDR=120.24.4.116,5601   ** ~/~/ Set UDP server address and port
207 +* **AT+CFM=1       ** ~/~/If the server does not respond, this command is unnecessary
275 275  
276 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  Set UDP server address and port
277 -
278 -* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
279 -
280 280  ​ [[image:image-20221021111025-10.png]]
281 281  
282 -
283 283  [[image:image-20221021111033-11.png||height="241" width="576"]]
284 284  
285 285  ​
286 286  
287 -=== 2.2.6 Use MQTT protocol to uplink data ===
215 +=== **2.2.6 Use MQTT protocol to uplink data** ===
288 288  
289 289  
290 -(% style="color:blue" %)**AT Commands:**
218 +**AT Commands:**
291 291  
292 -* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
220 +* **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
221 +* **AT+SERVADDR=120.24.4.116,1883   ** ~/~/Set MQTT server address and port
222 +* **AT+CLIENT=CLIENT       ** ~/~/Set up the CLIENT of MQTT
223 +* **AT+UNAME=UNAME                               **~/~/Set the username of MQTT
224 +* **AT+PWD=PWD                                        **~/~/Set the password of MQTT
225 +* **AT+PUBTOPIC=NSE01_PUB                    **~/~/Set the sending topic of MQTT
226 +* **AT+SUBTOPIC=NSE01_SUB          ** ~/~/Set the subscription topic of MQTT
293 293  
294 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
228 +​ [[image:image-20221021111058-12.png]]
295 295  
296 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
230 +[[image:image-20221021111201-16.png||height="472" width="653"]]
297 297  
298 -* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/  Set the username of MQTT
299 -
300 -* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/  Set the password of MQTT
301 -
302 -* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)** **~/~/  Set the sending topic of MQTT
303 -
304 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
305 -
306 -​ [[image:image-20221118103445-7.png]]
307 -
308 -
309 -[[image:image-20221118103453-8.png||height="608" width="841"]]
310 -
311 311  ​
312 312  
313 313  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.
314 314  
315 315  
316 -=== 2.2.7 Use TCP protocol to uplink data ===
237 +=== **2.2.7 Use TCP protocol to uplink data** ===
317 317  
239 +**AT Commands**
318 318  
319 -(% style="color:blue" %)**AT Commands:**
241 +* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
242 +* **AT+SERVADDR=120.24.4.116,5600   ** ~/~/ Set TCP server address and port
320 320  
321 -* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
322 -
323 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
324 -
325 325  ​ [[image:image-20221021111125-14.png]]
326 326  
327 327  [[image:image-20221021111131-15.png]]
... ... @@ -328,95 +328,73 @@
328 328  
329 329  ​
330 330  
331 -=== 2.2.8 Change Update Interval ===
250 +=== **2.2.8 Change Update Interval** ===
332 332  
252 +User can use below command to change the **uplink interval**.
333 333  
334 -User can use below command to change the (% style="color:blue" %)**uplink interval**.
254 +* **AT+TDC=7200      ** ~/~/ Set Update Interval to 7200s (2 hours)
335 335  
336 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
256 +**NOTE:**
337 337  
338 -(% style="color:red" %)**NOTE:**
258 +**~1. By default, the device will send an uplink message every 1 hour.**
339 339  
340 -1.  By default, the device will send an uplink message every 4 hour.
341 341  
261 +== **2.3  Uplink Payload** ==
342 342  
343 -== 2.3  Uplink Payload ==
263 +The uplink payload includes 123 bytes in total by default.
344 344  
265 +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.
345 345  
346 -The uplink payload includes 26 bytes in total by default.
267 +|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**1**|**1**|**3**
268 +|**Value**|[[Device ID>>path:#H2.4.1A0A0DeviceID]]|[[Ver>>path:#H2.4.2A0VersionInfo]]|[[BAT>>path:#H2.4.3A0BatteryInfo]]|[[Signal Strength>>path:#H2.4.4A0SignalStrength]]|MOD|[[ Calculate Flag>>path:#H2.4.8A0DigitalInterrupt]]|Contact Status|Alarm|Total pulse
347 347  
348 -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.
270 +(% style="width:1201px" %)
271 +|**3**|**4**|**1**|**3**|**1**|**3**|4|**8 group**|(% style="width:1px" %)
272 +|The last open duration|Time stamp|Contact Status|Total pulse|Calculate Flag|The last open duration|Time stamp|...|(% style="width:1px" %)
349 349  
350 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
274 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
351 351  
352 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
353 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:60px" %)**1**|(% style="width:90px" %)**3**|(% style="width:100px" %)**3**
354 -|=(% 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.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
276 +[[image:image-20221021111201-16.png||height="572" width="792"]]
355 355  
356 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
357 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
358 -**1-32 group**
359 -)))
360 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% 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" %)...
361 -
362 -
363 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
364 -
365 -
366 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
367 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:45px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:60px" %)**1**|(% style="width:60px" %)**1**|(% style="width:87px" %)**3**|(% style="width:80px" %)**3**
368 -|=(% 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.7A0AlarmBaseonTimeout"]](pb14)|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
369 -
370 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
371 -|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:75px" %)**1**|(% style="width:75px" %)**3**
372 -|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
373 -
374 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
375 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
376 -**1-32 group**
377 -)))
378 -|(% style="width:102px" %)last open time(pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:100px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......
379 -
380 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
381 -
382 -[[image:image-20221117145932-2.png]]
383 -
384 -
385 385  The payload is ASCII string, representative same HEX:
386 386  
387 -**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__(%%)**
280 +**0x (% style="color:red" %)__0xf867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %)_0c78__  __(% style="color:#00b0f0" %)17__  __(% style="color:#7030a0" %)01__  __(% style="color:#d60093" %)00__  __(% style="color:#a14d07" %)01 __ __(% style="color:#0020b0" %)__ __00__  __(% style="color:#420042" %)000009__  __(% style="color:#663300" %) 000002__  __(% style="color:#d60093" %)6315537bb__  __(% style="color:#663300" %)// 0100000b02000002663510fed__  __0100000e0200000263510f39 010000000000000063510e85 010000000000000063510d2e 010000000000000063510c7a 010000000000000063510bc6 010000000000000063510954 010000000000000063510882 //(%%)**
388 388  
389 -**where:**
282 +where:
283 +*(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317
390 390  
391 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
285 +*(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0
392 392  
393 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
287 +*(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
394 394  
395 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
289 +*(% style="color:#037691" %) **Singal: **(%%)0x17 = 23
396 396  
397 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
291 +*(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
398 398  
399 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
293 +*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00=0
400 400  
401 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
295 +*(% style="color:#037691" %) **Contact Status:**(%%) 0x00=0
402 402  
403 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
297 +*(% style="color:#037691" %) **Alarm:**(%%)0x00 =0
404 404  
405 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
299 +*(% style="color:#037691" %) **Total pulse:0x09 =0**
406 406  
407 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
301 +*(% style="color:#037691" %) **The last open duration:**(%%)0x02 =2
408 408  
409 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
303 +*(% style="color:#037691" %)** Time stamp :**(%%) 0x6315537b =1662342011 (Unix Time)
410 410  
305 +*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 01  00000b  02  000026  63510fed
411 411  
412 -== 2.4  Payload Explanation and Sensor Interface ==
307 +*(% style="color:#037691" %) **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
413 413  
414 -=== 2.4.1  Device ID ===
415 415  
310 +== **2.4  Payload Explanation and Sensor Interface** ==
416 416  
312 +=== **2.4.1  Device ID** ===
313 +
417 417  By default, the Device ID is equal to the last 15 bits of IMEI.
418 418  
419 -User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
316 +User can use **AT+DEUI** to set Device ID
420 420  
421 421  **Example:**
422 422  
... ... @@ -425,27 +425,24 @@
425 425  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
426 426  
427 427  
428 -=== 2.4.2  Version Info ===
325 +=== **2.4.2  Version Info** ===
429 429  
430 -
431 431  Specify the software version: 0x64=100, which means firmware version 1.00.
432 432  
433 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
329 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
434 434  
435 435  
436 -=== 2.4.3  Battery Info ===
332 +=== **2.4.3  Battery Info** ===
437 437  
334 +Check the battery voltage for CPN01.
438 438  
439 -Check the battery voltage for NDS03A.
440 -
441 441  Ex1: 0x0B45 = 2885mV
442 442  
443 443  Ex2: 0x0B49 = 2889mV
444 444  
445 445  
446 -=== 2.4.4  Signal Strength ===
341 +=== **2.4.4  Signal Strength** ===
447 447  
448 -
449 449  NB-IoT Network signal Strength.
450 450  
451 451  **Ex1: 0x1d = 29**
... ... @@ -461,45 +461,62 @@
461 461  **99**    Not known or not detectable
462 462  
463 463  
464 -=== 2.4.5  Disalarm: (default: 0) ===
358 +=== **2.4.5 Calculate Flag** ===
465 465  
360 +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.
466 466  
467 -(% 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.
362 +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.
468 468  
469 -(% 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.
364 +Default value: 0. 
470 470  
471 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
366 +Range (6 bits): (b)000000 ~~ (b) 111111
472 472  
473 473  
474 -=== 2.4.6  Keep Status & Keep Time ===
369 +=== **2.4.6  Alarm** ===
475 475  
371 +See [[Alarm Base on Timeout>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H3.5AlarmBaseonTimeout]]
476 476  
477 -Shows the configure value of Alarm Base on Timeout Feature
478 478  
374 +=== **2.4.7 Contact Status** ===
479 479  
480 -=== 2.4.7  Timestamp ===
376 +0: Open
481 481  
378 +1: Close
482 482  
483 -Timestamp : 0x6315537b =1662342011
484 484  
381 +=== **2.4.8 Total pulse** ===
485 485  
486 -=== 2.4.8  Switch Dual Channel Mode ===
383 +Total pulse/counting based on dry [[contact trigger event>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.2SensorConfiguration2CFPORT3D4]]
487 487  
385 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
488 488  
489 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
490 490  
388 +=== **2.4.9 The last open duration** ===
491 491  
492 -== 2.5  Downlink Payload ==
390 +Dry Contact last open duration.
493 493  
392 +Unit: min.
494 494  
495 -By default, NDS03A prints the downlink payload to console port.
394 +[[image:image-20221021111346-17.png||height="146" width="770"]]
496 496  
497 -[[image:image-20221021111414-18.png]] ​
498 498  
397 +=== **2.4.10  Timestamp** ===
499 499  
399 +Timestamp : 0x6315537b =1662342011
400 +
401 +Convert Unix timestamp to time 2022-9-5 9:40:11.
402 +
403 +**~ **
404 +
405 +== **2.5  Downlink Payload** ==
406 +
407 +By default, CPN01 prints the downlink payload to console port.
408 +
409 +[[image:image-20221021111414-18.png]] ​
410 +
500 500  **Examples:**
501 501  
502 -* (% style="color:#037691" %)**Set TDC**
413 +* **Set TDC**
503 503  
504 504  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
505 505  
... ... @@ -507,221 +507,172 @@
507 507  
508 508  Payload:    01 00 00 3C    TDC=60S
509 509  
510 -* (% style="color:#037691" %)**Reset**
421 +* **Reset**
511 511  
512 -If payload = 0x04FF, it will reset the NDS03A
423 +If payload = 0x04FF, it will reset the NSE01
513 513  
514 -* (% style="color:#037691" %)**INTMOD**
425 +* **INTMOD**
515 515  
516 516  Downlink Payload: 06000003, Set AT+INTMOD=3
517 517  
429 +== **2.6  ​LED Indicator** ==
518 518  
519 -== 2.6  ​LED Indicator ==
431 +The CPN01 has an internal LED which is to show the status of different states.
520 520  
521 -
522 -The NDS03A has an internal LED which is to show the status of different states.
523 -
524 524  * When the device starts normally, the LED will light up for 1 second.
525 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
434 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
526 526  * For each uplink probe, LED will be on for 500ms.
527 527  
437 +== **2.7  Alarm Base on Timeout** ==
528 528  
529 -== 2.7  Alarm Base on Timeout ==
439 +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:
530 530  
531 531  
532 -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:
442 +**~1. Keep Status: Status to be monitor**
533 533  
534 -
535 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
536 -
537 537  Keep Status = 1: Monitor Close to Open event
538 538  
539 539  Keep Status = 0: Monitor Open to Close event
540 540  
541 541  
542 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
449 +**2. Keep Time: Timeout to send an Alarm**
543 543  
544 544  Range 0 ~~ 65535(0xFFFF) seconds.
545 545  
546 546  If keep time = 0, Disable Alarm Base on Timeout feature.
547 547  
548 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
455 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
549 549  
550 550  
551 -(% style="color:blue" %)**AT Command to configure:**
458 +**AT Command** to configure:
552 552  
553 -(% style="color:blue" %)**PB14 PIN:**
460 +**AT+TTRIG=1,30**  ~-~-> When the **Keep Status** change from connected to disconnect, and device remains in disconnect status for more than 30 seconds. CPN01 will send an uplink packet, the [[Alarm bit>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.
554 554  
555 -(% 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.
462 +**AT+TTRIG=0,0 ** ~-~-> Default Value, disable timeout Alarm.
556 556  
557 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
558 558  
465 +== **2.8 Set debug mode** ==
559 559  
560 -(% style="color:blue" %)**PB15 PIN:**
561 -
562 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
563 -
564 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
565 -
566 -
567 -== 2.8  Set debug mode ==
568 -
569 -
570 570  Feature: Enable or Disable debug mode
571 571  
572 -(% style="color:blue" %)**AT Command: AT+DEBUG**
573 573  
470 +**AT Command: AT+DEBUG**
471 +
574 574  [[image:image-20221021111629-21.png]]
575 575  
474 +== **2.9 Clear Flash Record** ==
576 576  
577 -
578 -== 2.9  Clear Flash Record ==
579 -
580 -
581 581  Feature: Clear flash storage for data log feature.
582 582  
583 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
478 +**AT Command: AT+CLRDTA**
584 584  
585 585  [[image:image-20221021111527-19.png]]
586 586  
482 +== ** 2.10 Set trigger mode** ==
587 587  
588 -== 2.10  Count Mod ==
484 +➢ AT Command: **AT+TTRMOD**
589 589  
486 +Feature: Set the trigger interrupt mode.
590 590  
591 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
488 +[[image:image-20221021111552-20.png]]
592 592  
593 -[[image:image-20221118092935-1.png]]
490 +== **2.11 Set the calculate flag** ==
594 594  
492 +Feature: Set the calculate flag
595 595  
596 -== 2.11  Interrupt Pin Channel Mod ==
494 +**AT Command: AT+CALCFLAG**
597 597  
496 +[[image:image-20221021111711-22.png]]
598 598  
599 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
498 +== **2.12 Set count number** ==
600 600  
601 -[[image:image-20221118093144-2.png]]
500 +Feature: Manually set the count number
602 602  
502 +**AT Command: AT+SETCNT**
603 603  
604 -== 2.12 TTRIG1/2 timeout status alarm ==
504 +[[image:image-20221021111748-24.png]]
605 605  
506 +== **2.13 Set the number of data to be uploaded and the recording time** ==
606 606  
607 -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.
508 +➢ AT Command:
608 608  
609 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
510 +AT+TR=900  ~/~/The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
610 610  
611 -[[image:image-20221118093512-3.png]]
612 612  
513 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
613 613  
614 -== 2.13  Select counting mode ==
515 +== **2.14 Read or Clear cached data** ==
615 615  
517 +➢ AT Command:
616 616  
617 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
519 +AT+CDP    ~/~/ Read cached data
618 618  
619 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
521 +[[image:image-20221021111810-25.png||height="364" width="797"]]
620 620  
621 -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.
622 622  
623 -[[image:image-20221118093658-4.png]]
524 +AT+CDP=0    ~/~/ Clear cached data ​
624 624  
526 +== **2.15  ​Firmware Change Log** ==
625 625  
626 -== 2.14  Set the number of data to be uploaded and the recording time ==
528 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
627 627  
530 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
628 628  
629 -(% style="color:blue" %)**AT Command:**
532 +== **2.16  ​Battery Analysis** ==
630 630  
631 -(% 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)
534 +=== **2.16.1  ​Battery Type** ===
632 632  
633 -(% 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.
536 +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.
634 634  
635 -
636 -== 2.15  Read or Clear cached data ==
637 -
638 -
639 -(% style="color:blue" %)**AT Command:**
640 -
641 -(% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
642 -
643 -(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
644 -
645 -[[image:image-20221118094227-5.png]]
646 -
647 -
648 -== 2.16  ​Firmware Change Log ==
649 -
650 -
651 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
652 -
653 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
654 -
655 -
656 -== 2.17  ​Battery Analysis ==
657 -
658 -=== 2.17.1  ​Battery Type ===
659 -
660 -
661 -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.
662 -
663 663  The battery is designed to last for several years depends on the actual use environment and update interval. 
664 664  
665 665  The battery-related documents as below:
666 666  
667 667  * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
668 -
669 669  * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
670 -
671 671  * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
672 672  
673 673  [[image:image-20221021111911-26.png]] ​
674 674  
548 +=== **2.16.2  Power consumption Analyze** ===
675 675  
676 -=== 2.17.2  Power consumption Analyze ===
677 -
678 -
679 679  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.
680 680  
681 681  Instruction to use as below:
682 682  
683 -(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
554 +**Step 1:  **Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
684 684  
685 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
556 +**Step 2: ** Open it and choose
686 686  
687 687  * Product Model
688 -
689 689  * Uplink Interval
690 -
691 691  * Working Mode
692 692  
693 693  And the Life expectation in difference case will be shown on the right.
694 694  
695 -[[image:1666596205057-567.png]] ​
564 +[[image:image-20221021111923-27.png||height="253" width="783"]] ​
696 696  
566 +=== **2.16.3  ​Battery Note** ===
697 697  
698 -=== 2.17.3  ​Battery Note ===
699 -
700 -
701 701  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.
702 702  
570 +=== **2.16.4  Replace the battery** ===
703 703  
704 -=== 2.17.4  Replace the battery ===
572 +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).
705 705  
706 706  
707 -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).
575 += **3. ​ Access NB-IoT Module** =
708 708  
709 -
710 -= 3. ​ Access NB-IoT Module =
711 -
712 -
713 713  Users can directly access the AT command set of the NB-IoT module.
714 714  
715 715  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/]] 
716 716  
717 -[[image:image-20221118094449-6.png]] ​
581 +[[image:image-20221021112006-28.png]] ​
718 718  
583 += **4.  Using the AT Commands** =
719 719  
720 -= 4.  Using the AT Commands =
585 +== **4.1  Access AT Commands** ==
721 721  
722 -== 4.1  Access AT Commands ==
723 -
724 -
725 725  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]]
726 726  
727 727  AT+<CMD>?  : Help on <CMD>
... ... @@ -732,9 +732,8 @@
732 732  
733 733  AT+<CMD>=?  : Get the value
734 734  
597 +**General Commands**      
735 735  
736 -(% style="color:blue" %)**General Commands**      
737 -
738 738  AT  : Attention       
739 739  
740 740  AT?  : Short Help     
... ... @@ -757,41 +757,35 @@
757 757  
758 758  AT+SERVADDR  : Server Address
759 759  
760 -AT+TR      :  Get or Set record time
621 +AT+TR      : Get or Set record time"
761 761  
623 +
762 762  AT+NOUD      : Get or Set the number of data to be uploaded
763 763  
764 -AT+CDP     :  Read or Clear cached data
765 765  
766 -AT+ DEBUG   : Enable or Disable debug mode
627 +AT+CDP     : Read or Clear cached data
767 767  
768 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
769 769  
770 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
630 +AT+ DEBUG   : Enable or Disable debug mode
771 771  
772 -AT+COUNTMOD  :  Get or Set the count mode
632 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
773 773  
774 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
634 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
775 775  
776 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
636 +AT+ CALCFLAG   : Get or Set the calculate flag
777 777  
778 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
638 +AT+ CLRC   : Clear current door open count
779 779  
780 -AT+ CLRC   :  Clear current door open count
640 +**COAP Management**      
781 781  
782 -
783 -(% style="color:blue" %)**COAP Management**      
784 -
785 785  AT+URI            : Resource parameters
786 786  
644 +**UDP Management**
787 787  
788 -(% style="color:blue" %)**UDP Management**
789 -
790 790  AT+CFM          : Upload confirmation mode (only valid for UDP)
791 791  
648 +**MQTT Management**
792 792  
793 -(% style="color:blue" %)**MQTT Management**
794 -
795 795  AT+CLIENT               : Get or Set MQTT client
796 796  
797 797  AT+UNAME  : Get or Set MQTT Username
... ... @@ -802,59 +802,86 @@
802 802  
803 803  AT+SUBTOPIC  : Get or Set MQTT subscription topic
804 804  
660 +**Information**          
805 805  
806 -(% style="color:blue" %)**Information**          
807 -
808 808  AT+FDR  : Factory Data Reset
809 809  
810 810  AT+PWORD  : Serial Access Password
811 811  
666 += **​5.  FAQ** =
812 812  
813 -= ​5.  FAQ =
668 +== **5.1 ​ How to Upgrade Firmware** ==
814 814  
815 -== 5.1 ​ How to Upgrade Firmware ==
816 -
817 -
818 818  User can upgrade the firmware for 1) bug fix, 2) new feature release.
819 819  
820 820  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]]
821 821  
822 -(% 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.**
674 +**Notice, **CPN01 **and **CPL01 **share the same mother board. They use the same connection and method to update.**
823 823  
824 824  
825 -= 6.  Trouble Shooting =
677 += **6.  Trouble Shooting** =
826 826  
827 -== 6.1  ​Connection problem when uploading firmware ==
679 +== **6.1  ​Connection problem when uploading firmware** ==
828 828  
681 +**Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
829 829  
830 -(% 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]]
831 831  
684 +== **6.2  AT Command input doesn't work** ==
832 832  
833 -== 6.2  AT Command input doesn't work ==
686 +In the case if user can see the console output but can't type input to the device. Please check if you already include the **ENTER** while sending out the command. Some serial tool doesn't send **ENTER** while press the send key, user need to add ENTER in their string.
834 834  
835 835  
836 -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.
689 += **7. ​ Order Info** =
837 837  
691 +Part Number**:** CPN01
838 838  
839 -= 7. ​ Order Info =
840 840  
694 += **8.  Packing Info** =
841 841  
842 -Part Number**:** NDS03A
696 +**Package Includes**:
843 843  
698 +* CPN01 Open/Close Sensor x 1
699 +* External antenna x 1
844 844  
845 -= 8.  Packing Info =
701 +**Dimension and weight**:
846 846  
703 +* Size: 195 x 125 x 55 mm
704 +* Weight:   420g
847 847  
848 -(% style="color:blue" %)**Package Includes**:
706 += **9.  Support** =
849 849  
850 -* NDS03A Open/Close Door Sensor x 1
708 +* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
709 +* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
851 851  
711 +​
852 852  
853 -= 9.  Support =
854 854  
855 855  
856 -* 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.
857 857  
858 -* 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]]
859 859  
860 -​
717 +
718 +
719 +
720 +
721 +
722 +
723 +
724 +
725 +
726 +
727 +
728 +
729 +
730 +
731 +
732 +
733 +
734 +
735 +
736 +
737 +
738 +
739 +
740 +
741 +
742 +
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
image-20221118103445-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -20.4 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.5 KB
Content

Applications

Navigation

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