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

Applications

Navigation

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