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

Summary

Details

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