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