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

Applications

Navigation

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