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