Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 46.1 >
edited by David Huang
on 2022/10/24 10:18
To version < 64.1 >
edited by Xiaoling
on 2022/11/18 09:35
>
Change comment: Uploaded new attachment "image-20221118093512-3.png", version {1}

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -CPN01- NB-IoT Outdoor Open/Close Dry Contact Sensor User Manual
1 +NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.David
1 +XWiki.Xiaoling
Content
... ... @@ -1,34 +1,65 @@
1 1  (% style="text-align:center" %)
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"]]
2 +[[image:image-20221117105556-1.png]]
3 3  
4 -{{toc/}}
5 5  
6 -= **1. Introduction** =
7 7  
8 -== **1.1 ​**What is CPN01 **NB-IoT** Pulse/Contact Sensor ==
9 9  
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.
11 11  
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.
13 13  
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.
15 15  
16 -CPN01 is designed for outdoor use. It has a weatherproof enclosure and industrial-level battery to work in low to high temperatures.
10 +**Table of Contents：**
17 17  
18 -NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
19 -\\CPN01 supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
20 -\\CPN01 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
21 -\\To use CPN01, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that CPN01 supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into CPN01 to get NB-IoT network connection.
22 22  
23 -​
24 24  
25 -== **​1.2 Features** ==
26 26  
15 +
16 += 1.  Introduction =
17 +
18 +== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
19 +
20 +
21 +(((
22 +The Dragino NDS03A is an (% style="color:blue" %)**Open/Close NB-IoT Door Sensor**(%%). It detects door (% style="color:blue" %)**open/close status**(%%) and (% style="color:blue" %)**uplinks**(%%) to IoT server via NB-IoT network. NDS03A can connect two door sensors. user can see the door status, open duration, open counts in the IoT Server.
23 +)))
24 +
25 +(((
26 +The NDS03A will send periodically data (% style="color:blue" %)**every 4 hours** (%%)as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically.
27 +)))
28 +
29 +(((
30 +NDS03A has a (% style="color:blue" %)**Datalog feature**(%%), it will record the open/close event and the user can retrieve the history from NB-IoT.
31 +)))
32 +
33 +(((
34 +NDS03A has the(% style="color:blue" %)**open alarm feature**(%%), user can set this feature so the device will send an alarm if the door has been open for a certain time.
35 +)))
36 +
37 +(((
38 +NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
39 +)))
40 +
41 +(((
42 +NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technologyTCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
43 +)))
44 +
45 +(((
46 +NDS03A is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
47 +)))
48 +
49 +(((
50 +To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into NDS03A to get NB-IoT network connection.
51 +)))
52 +
53 +
54 +
55 +== ​1.2  Features ==
56 +
57 +
27 27  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
28 28  * Open/Close detect
29 29  * Open/Close statistics
30 30  * Monitor Battery Level
31 -* Uplink on periodically and open/close event
62 +* connect two door sensors
32 32  * Datalog feature
33 33  * Uplink periodically
34 34  * Downlink to change configure
... ... @@ -39,14 +39,41 @@
39 39  * Micro SIM card slot for NB-IoT SIM
40 40  * 8500mAh Battery for long-term use
41 41  
42 -== **1.3  Specification** ==
73 +== 1.3  Storage & Operation ==
43 43  
44 -**Common DC Characteristics:**
45 45  
76 +Temperature -40°C to +85°C
77 +
78 +
79 +== 1.4  Mechanical ==
80 +
81 +
82 +[[image:image-20221117114937-4.png]]
83 +
84 +
85 +[[image:image-20221117114949-5.png]]
86 +
87 +
88 +[[image:image-20221117115010-6.png]]
89 +
90 +
91 +
92 +== 1.5 ​ Applications ==
93 +
94 +
95 +[[image:image-20221117114842-3.png]]
96 +
97 +
98 +
99 +== 1.6  Specification ==
100 +
101 +
102 +(% style="color:blue" %)**Common DC Characteristics:**
103 +
46 46  * Supply Voltage: 2.1v ~~ 3.6v
47 47  * Operating Temperature: -40 ~~ 85°C
48 48  
49 -**NB-IoT Spec:**
107 +(% style="color:blue" %)**NB-IoT Spec:**
50 50  
51 51  * - B1 @H-FDD: 2100MHz
52 52  * - B3 @H-FDD: 1800MHz
... ... @@ -55,90 +55,96 @@
55 55  * - B20 @H-FDD: 800MHz
56 56  * - B28 @H-FDD: 700MHz
57 57  
58 -== **1.4 Installation** ==
116 +== 1.7  Pin Definitions and Switch ==
59 59  
60 -Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
61 61  
62 -[[image:image-20221021110329-1.png]]
119 +[[image:image-20221021110429-4.png]]
63 63  
64 -[[image:image-20221022234602-2.png||height="288" width="922"]]
65 65  
122 +=== 1.7.1  Pin Definition ===
66 66  
67 -== **1.5 ​Applications** ==
68 68  
69 -* Open/Close Detection
70 -* Pulse meter application
71 -* Dry Contact Detection
125 +The device is pre-configured to connect to a door sensor. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at:  [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]
72 72  
73 -== **1.6 Mechanical** ==
74 74  
75 -​[[image:image-20221021110415-3.png]]
76 76  
77 -== ** 1.7 Pin Definitions and Switch** ==
129 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
78 78  
79 -[[image:image-20221021110429-4.png]]
80 80  
81 -=== **1.7.1 Pin Definition** ===
132 +Power on Device when putting this jumper.
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]]**.
84 84  
85 85  
86 -=== **1.7.2 Jumper JP2(Power ON/OFF)** ===
136 +=== 1.7.3  BOOT MODE / SW1 ===
87 87  
88 -Power on Device when putting this jumper.
89 89  
139 +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.
90 90  
91 -=== **1.7.3 BOOT MODE / SW1** ===
141 +2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
92 92  
93 93  
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.
95 95  
96 -2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
145 +=== 1.7.4  Reset Button ===
97 97  
98 98  
99 -=== **1.7.4 Reset Button** ===
100 -
101 -
102 102  Press to reboot the device.
103 103  
104 104  
105 -=== **1.7.5 LED** ===
106 106  
152 +=== 1.7.5  LED ===
107 107  
154 +
108 108  The LED will blink when :
109 109  
110 -1. Boot the device in flash mode
111 -1. Send an uplink packet
157 +1.  Boot the device in flash mode
112 112  
113 -= **2.  Use CPN01 to communicate with IoT Server** =
159 +2.  Send an uplink packet
114 114  
115 -== **2.1  How it works** ==
116 116  
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.
118 118  
119 -The diagram below shows the working flow in the default firmware of CPN01:
163 +== 1.8  Magnet Distance ==
120 120  
165 +
166 +(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
167 +
168 +(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
169 +
170 +
171 +
172 += 2.  Use CPN01 to communicate with IoT Server =
173 +
174 +== 2.1  How it works ==
175 +
176 +
177 +In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A.
178 +
179 +The diagram below shows the working flow in the default firmware of NDS03A:
180 +
121 121  [[image:image-20221021110615-5.png]]
122 122  
123 123  
124 -== **2.2 ​ Configure CPN01** ==
125 125  
126 -=== **2.2.1 Test Requirement** ===
185 +== 2.2 ​ Configure NDS03A ==
127 127  
128 -To use CPN01 in your city, make sure to meet below requirements:
187 +=== 2.2.1 Test Requirement ===
129 129  
189 +
190 +To use NDS03A in your city, make sure to meet below requirements:
191 +
130 130  * Your local operator has already distributed an NB-IoT Network.
131 -* The local NB-IoT network used the band that CPN01 supports.
193 +* The local NB-IoT network used the band that NDS03A supports.
132 132  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
133 133  
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.
196 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDS03A will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
135 135  
136 -[[image:image-20221023000439-3.png]]
198 +[[image:image-20221117142300-1.png]]
137 137  
138 138   ​
139 139  
140 -=== **2.2.2 Insert NB-IoT SIM card** ===
141 141  
203 +=== 2.2.2 Insert NB-IoT SIM card ===
204 +
205 +
142 142  Insert the NB-IoT Card get from your provider.
143 143  
144 144  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -146,101 +146,127 @@
146 146  [[image:image-20221021110745-6.png]] ​
147 147  
148 148  
149 -=== **2.2.3 Connect USB – TTL to CPN01 and configure it** ===
150 150  
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.
214 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
152 152  
153 -**Connection:**
154 154  
155 - USB TTL GND <~-~-~-~-> GND
217 +User need to configure NDS03A via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USB to TTL adapter to connect to NDS03A and use AT Commands to configure it, as below.
156 156  
157 - USB TTL TXD <~-~-~-~-> UART_RXD
219 +(% style="color:blue" %)**Connection:**
158 158  
159 - USB TTL RXD <~-~-~-~-> UART_TXD
221 +(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
160 160  
223 +(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD**
224 +
225 +(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD**
226 +
227 +
161 161  In the PC, use below serial tool settings:
162 162  
163 -* Baud:  **9600**
164 -* Data bits:** 8**
165 -* Stop bits: **1**
166 -* Parity:  **None**
167 -* Flow Control: **None**
230 +* Baud:  (% style="color:red" %)**9600**
168 168  
169 -Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
232 +* Data bits:** (% style="color:red" %)8(%%)**
170 170  
234 +* Stop bits: (% style="color:red" %)**1**
235 +
236 +* Parity:  (% style="color:red" %)**None**
237 +
238 +* Flow Control: (% style="color:red" %)**None**
239 +
240 +Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
241 +
171 171  ​[[image:image-20221021110817-7.png]]
172 172  
173 -CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
244 +NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
174 174  
175 175  
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]]
247 +(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
177 177  
178 178  
179 -=== **2.2.4 Use CoAP protocol to uplink data** ===
180 180  
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/]]
251 +=== 2.2.4 Use CoAP protocol to uplink data ===
182 182  
183 183  
184 -**Use below commands in CPN01:**
254 +(% 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/]]
185 185  
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=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set CoAP resource path
189 189  
257 +(% style="color:blue" %)**Use below commands in CPN01:**
258 +
259 +* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
260 +
261 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/ Set CoAP server address and port
262 +
263 +* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/  Set CoAP resource path
264 +
190 190  For parameter description, please refer to AT command set
191 191  
192 192  [[image:image-20221021110948-8.png]]
193 193  
194 194  
195 -After configuring the server address and **reset CPN01** (via AT+ATZ ), CPN01 will start to uplink sensor values to the CoAP server.
270 +After configuring the server address and (% style="color:green" %)**reset CPN01**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
196 196  
197 197  [[image:image-20221021110956-9.png]] ​
198 198  
199 199  
200 -=== **2.2.5 Use UDP protocol to uplink data(Default protocol)** ===
201 201  
276 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
202 202  
203 -**AT Commands:**
204 204  
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
279 +(% style="color:blue" %)**AT Commands:**
208 208  
281 +* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
282 +
283 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  Set UDP server address and port
284 +
285 +* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
286 +
209 209  ​ [[image:image-20221021111025-10.png]]
210 210  
289 +
211 211  [[image:image-20221021111033-11.png||height="241" width="576"]]
212 212  
213 213  ​
214 214  
215 -=== **2.2.6 Use MQTT protocol to uplink data** ===
216 216  
295 +=== 2.2.6 Use MQTT protocol to uplink data ===
217 217  
218 -**AT Commands:**
219 219  
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
298 +(% style="color:blue" %)**AT Commands:**
227 227  
300 +* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
301 +
302 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
303 +
304 +* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
305 +
306 +* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/  Set the username of MQTT
307 +
308 +* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/  Set the password of MQTT
309 +
310 +* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)** **~/~/  Set the sending topic of MQTT
311 +
312 +* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
313 +
228 228  ​ [[image:image-20221021111058-12.png]]
229 229  
230 -[[image:image-20221021111108-13.png]]
231 231  
317 +[[image:image-20221021111201-16.png||height="472" width="653"]]
318 +
232 232  ​
233 233  
234 234  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.
235 235  
236 236  
237 -=== **2.2.7 Use TCP protocol to uplink data** ===
238 238  
239 -**AT Commands**
325 +=== 2.2.7 Use TCP protocol to uplink data ===
240 240  
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
243 243  
328 +(% style="color:blue" %)**AT Commands:**
329 +
330 +* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
331 +
332 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
333 +
244 244  ​ [[image:image-20221021111125-14.png]]
245 245  
246 246  [[image:image-20221021111131-15.png]]
... ... @@ -247,73 +247,96 @@
247 247  
248 248  ​
249 249  
250 -=== **2.2.8 Change Update Interval** ===
251 251  
252 -User can use below command to change the **uplink interval**.
341 +=== 2.2.8 Change Update Interval ===
253 253  
254 -* **AT+TDC=7200      ** ~/~/ Set Update Interval to 7200s (2 hours)
255 255  
256 -**NOTE:**
344 +User can use below command to change the (% style="color:blue" %)**uplink interval**.
257 257  
258 -**~1. By default, the device will send an uplink message every 1 hour.**
346 +* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
259 259  
348 +(% style="color:red" %)**NOTE:**
260 260  
261 -== **2.3  Uplink Payload** ==
350 +1.  By default, the device will send an uplink message every 4 hour.
262 262  
263 -The uplink payload includes 123 bytes in total by default.
264 264  
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.
266 266  
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
354 +== 2.3  Uplink Payload ==
269 269  
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" %)
273 273  
274 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
357 +The uplink payload includes 26 bytes in total by default.
275 275  
276 -[[image:image-20221021111201-16.png||height="572" width="792"]]
359 +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.
277 277  
278 -The payload is ASCII string, representative same HEX:
361 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
279 279  
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 //(%%)**
363 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)
364 +|=(% scope="row" style="width: 93px;" %)**Size(bytes)**|(% style="width:67px" %)**8**|(% style="width:40px" %)**2**|(% style="width:45px" %)**2**|(% style="width:75px" %)**1**|(% style="width:54px" %)**1**|(% style="width:62px" %)**1**|(% style="width:60px" %)**1**|(% style="width:94px" %)**3**|(% style="width:93px" %)**3**
365 +|=(% 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.4.6A0Alarm"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
281 281  
282 -where:
283 -*(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317
367 +(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
368 +|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)(((
369 +**1-32 group**
370 +)))
371 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% 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" %)...
284 284  
285 -*(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0
373 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
286 286  
287 -*(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
288 288  
289 -*(% style="color:#037691" %) **Singal: **(%%)0x17 = 23
376 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
377 +|=(% scope="row" style="width: 96px;" %)**Size(bytes)**|(% style="width:66px" %)**8**|(% style="width:40px" %)**2**|(% style="width:46px" %)**2**|(% style="width:70px" %)**1**|(% style="width:54px" %)**1**|(% style="width:55px" %)**1**|(% style="width:57px" %)**1**|(% style="width:86px" %)**3**|(% style="width:82px" %)**3**
378 +|=(% 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|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.4.6A0Alarm"]]|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
290 290  
291 -*(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
380 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
381 +|(% style="width:59px" %)**1**|(% style="width:67px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:66px" %)**1**|(% style="width:92px" %)**3**
382 +|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPN01-%20NB-IoT%20Outdoor%20OpenClose%20Dry%20Contact%20Sensor%C2%A0User%20Manual/#H2.4.7A0ContactStatus]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)Time stamp|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
292 292  
293 -*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00=0
384 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
385 +|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)(((
386 +**1-32 group**
387 +)))
388 +|(% style="width:102px" %)last open time (pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:88px" %)last open time(pb15)|(% style="width:63px" %)Time stamp|(% style="width:87px" %)...
294 294  
295 -*(% style="color:#037691" %) **Contact Status:**(%%) 0x00=0
390 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
296 296  
297 -*(% style="color:#037691" %) **Alarm:**(%%)0x00 =0
392 +[[image:image-20221117145932-2.png]]
298 298  
299 -*(% style="color:#037691" %) **Total pulse:0x09 =0**
300 300  
301 -*(% style="color:#037691" %) **The last open duration:**(%%)0x02 =2
395 +The payload is ASCII string, representative same HEX:
302 302  
303 -*(% style="color:#037691" %)** Time stamp :**(%%) 0x6315537b =1662342011 (Unix Time)
397 +**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__(%%)**
304 304  
305 -*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 01  00000b  02  000026  63510fed
399 +**where:**
306 306  
307 -*(% style="color:#037691" %) **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
401 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
308 308  
403 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
309 309  
310 -== **2.4  Payload Explanation and Sensor Interface** ==
405 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
311 311  
312 -=== **2.4.1  Device ID** ===
407 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
313 313  
409 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
410 +
411 +* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0
412 +
413 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
414 +
415 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
416 +
417 +* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23
418 +
419 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
420 +
421 +== 2.4  Payload Explanation and Sensor Interface ==
422 +
423 +
424 +=== 2.4.1  Device ID ===
425 +
426 +
314 314  By default, the Device ID is equal to the last 15 bits of IMEI.
315 315  
316 -User can use **AT+DEUI** to set Device ID
429 +User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
317 317  
318 318  **Example:**
319 319  
... ... @@ -322,24 +322,27 @@
322 322  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
323 323  
324 324  
325 -=== **2.4.2  Version Info** ===
438 +=== 2.4.2  Version Info ===
326 326  
440 +
327 327  Specify the software version: 0x64=100, which means firmware version 1.00.
328 328  
329 -For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
443 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
330 330  
331 331  
332 -=== **2.4.3  Battery Info** ===
446 +=== 2.4.3  Battery Info ===
333 333  
334 -Check the battery voltage for CPN01.
335 335  
449 +Check the battery voltage for NDS03A.
450 +
336 336  Ex1: 0x0B45 = 2885mV
337 337  
338 338  Ex2: 0x0B49 = 2889mV
339 339  
340 340  
341 -=== **2.4.4  Signal Strength** ===
456 +=== 2.4.4  Signal Strength ===
342 342  
458 +
343 343  NB-IoT Network signal Strength.
344 344  
345 345  **Ex1: 0x1d = 29**
... ... @@ -355,62 +355,46 @@
355 355  **99**    Not known or not detectable
356 356  
357 357  
358 -=== **2.4.5 Calculate Flag** ===
474 +=== 2.4.5  Disalarm: (default: 0) ===
359 359  
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.
361 361  
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.
477 +(% 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.
363 363  
364 -Default value: 0. 
479 +(% 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.
365 365  
366 -Range (6 bits): (b)000000 ~~ (b) 111111
481 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
367 367  
368 368  
369 -=== **2.4.6  Alarm** ===
484 +=== 2.4.6  Keep Status & Keep Time ===
370 370  
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]]
372 372  
487 +Shows the configure value of Alarm Base on Timeout Feature
373 373  
374 -=== **2.4.7 Contact Status** ===
375 375  
376 -0: Open
490 +=== 2.4.7  Timestamp ===
377 377  
378 -1: Close
379 379  
493 +Timestamp : 0x6315537b =1662342011
380 380  
381 -=== **2.4.8 Total pulse** ===
382 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 384  
385 -Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
497 +=== 2.4.8  Switch Dual Channel Mode ===
386 386  
387 387  
388 -=== **2.4.9 The last open duration** ===
500 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
389 389  
390 -Dry Contact last open duration.
391 391  
392 -Unit: min.
503 +== 2.5  Downlink Payload ==
393 393  
394 -[[image:image-20221021111346-17.png||height="146" width="770"]]
395 395  
506 +By default, NDS03A prints the downlink payload to console port.
396 396  
397 -=== **2.4.10  Timestamp** ===
398 -
399 -Timestamp : 0x6315537b =1662342011
400 -
401 -Convert Unix timestamp to time 2022-9-5 9:40:11.
402 -
403 -**~ **
404 -
405 -== **2.5  Downlink Payload** ==
406 -
407 -By default, CPN01 prints the downlink payload to console port.
408 -
409 409  [[image:image-20221021111414-18.png]] ​
410 410  
510 +
411 411  **Examples:**
412 412  
413 -* **Set TDC**
513 +* (% style="color:#037691" %)**Set TDC**
414 414  
415 415  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
416 416  
... ... @@ -418,16 +418,19 @@
418 418  
419 419  Payload:    01 00 00 3C    TDC=60S
420 420  
421 -* **Reset**
521 +* (% style="color:#037691" %)**Reset**
422 422  
423 423  If payload = 0x04FF, it will reset the NSE01
424 424  
425 -* **INTMOD**
525 +* (% style="color:#037691" %)**INTMOD**
426 426  
427 427  Downlink Payload: 06000003, Set AT+INTMOD=3
428 428  
429 -== **2.6  ​LED Indicator** ==
430 430  
530 +
531 +== 2.6  ​LED Indicator ==
532 +
533 +
431 431  The CPN01 has an internal LED which is to show the status of different states.
432 432  
433 433  * When the device starts normally, the LED will light up for 1 second.
... ... @@ -434,12 +434,13 @@
434 434  * After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
435 435  * For each uplink probe, LED will be on for 500ms.
436 436  
437 -== **2.7  Alarm Base on Timeout** ==
540 +== 2.7  Alarm Base on Timeout ==
438 438  
542 +
439 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:
440 440  
441 441  
442 -**~1. Keep Status: Status to be monitor**
546 +(% style="color:blue" %)**1. Keep Status: Status to be monitor**
443 443  
444 444  Keep Status = 1: Monitor Close to Open event
445 445  
... ... @@ -446,7 +446,7 @@
446 446  Keep Status = 0: Monitor Open to Close event
447 447  
448 448  
449 -**2. Keep Time: Timeout to send an Alarm**
553 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
450 450  
451 451  Range 0 ~~ 65535(0xFFFF) seconds.
452 452  
... ... @@ -455,84 +455,108 @@
455 455  If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
456 456  
457 457  
458 -**AT Command** to configure:
562 +(% style="color:blue" %)**AT Command to configure:**
459 459  
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.
564 +(% 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. 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.
461 461  
462 -**AT+TTRIG=0,0 ** ~-~-> Default Value, disable timeout Alarm.
566 +(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
463 463  
464 464  
465 -== **2.8 Set debug mode** ==
466 466  
467 -Feature: Enable or Disable debug mode
570 +== 2.8  Set debug mode ==
468 468  
469 469  
470 -**AT Command: AT+DEBUG**
573 +Feature: Enable or Disable debug mode
471 471  
575 +(% style="color:blue" %)**AT Command: AT+DEBUG**
576 +
472 472  [[image:image-20221021111629-21.png]]
473 473  
474 -== **2.9 Clear Flash Record** ==
475 475  
580 +
581 +== 2.9  Clear Flash Record ==
582 +
583 +
476 476  Feature: Clear flash storage for data log feature.
477 477  
478 -**AT Command: AT+CLRDTA**
586 +(% style="color:blue" %)**AT Command: AT+CLRDTA**
479 479  
480 480  [[image:image-20221021111527-19.png]]
481 481  
482 -== ** 2.10 Set trigger mode** ==
483 483  
484 -➢ AT Command: **AT+TTRMOD**
485 485  
592 +== 2.10  Set trigger mode ==
593 +
594 +
595 +(% style="color:blue" %)**AT Command: AT+TTRMOD**
596 +
486 486  Feature: Set the trigger interrupt mode.
487 487  
488 488  [[image:image-20221021111552-20.png]]
489 489  
490 -== **2.11 Set the calculate flag** ==
491 491  
602 +
603 +== 2.11  Set the calculate flag ==
604 +
605 +
492 492  Feature: Set the calculate flag
493 493  
494 -**AT Command: AT+CALCFLAG**
608 +(% style="color:blue" %)**AT Command: AT+CALCFLAG**
495 495  
496 496  [[image:image-20221021111711-22.png]]
497 497  
498 -== **2.12 Set count number** ==
499 499  
613 +
614 +== 2.12 Set count number ==
615 +
616 +
500 500  Feature: Manually set the count number
501 501  
502 -**AT Command: AT+SETCNT**
619 +(% style="color:blue" %)**AT Command: AT+SETCNT**
503 503  
504 504  [[image:image-20221021111748-24.png]]
505 505  
506 -== **2.13 Set the number of data to be uploaded and the recording time** ==
507 507  
508 -➢ AT Command:
509 509  
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)
625 +== 2.13  Set the number of data to be uploaded and the recording time ==
511 511  
512 512  
513 -AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
628 +(% style="color:blue" %)**AT Command:**
514 514  
515 -== **2.14 Read or Clear cached data** ==
630 +(% 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 516  
517 -➢ AT Command:
632 +(% style="color:#037691" %)**AT+NOUD=8 ** (%%)~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
518 518  
519 -AT+CDP    ~/~/ Read cached data
520 520  
635 +
636 +== 2.14  Read or Clear cached data ==
637 +
638 +
639 +(% style="color:blue" %)**AT Command:**
640 +
641 +(% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
642 +
643 +(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
644 +
521 521  [[image:image-20221021111810-25.png||height="364" width="797"]]
522 522  
523 523  
524 -AT+CDP=0    ~/~/ Clear cached data ​
525 525  
526 -== **2.15  ​Firmware Change Log** ==
649 +== 2.15  ​Firmware Change Log ==
527 527  
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]]
529 529  
530 -Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
652 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
531 531  
532 -== **2.16  ​Battery Analysis** ==
654 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
533 533  
534 -=== **2.16.1  ​Battery Type** ===
535 535  
657 +
658 +== 2.16  ​Battery Analysis ==
659 +
660 +
661 +=== 2.16.1  ​Battery Type ===
662 +
663 +
536 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.
537 537  
538 538  The battery is designed to last for several years depends on the actual use environment and update interval. 
... ... @@ -540,40 +540,55 @@
540 540  The battery-related documents as below:
541 541  
542 542  * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
671 +
543 543  * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
673 +
544 544  * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
545 545  
546 546  [[image:image-20221021111911-26.png]] ​
547 547  
548 -=== **2.16.2  Power consumption Analyze** ===
549 549  
679 +
680 +=== 2.16.2  Power consumption Analyze ===
681 +
682 +
550 550  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.
551 551  
552 552  Instruction to use as below:
553 553  
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/]]
687 +(% 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/]]
555 555  
556 -**Step 2: ** Open it and choose
689 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
557 557  
558 558  * Product Model
692 +
559 559  * Uplink Interval
694 +
560 560  * Working Mode
561 561  
562 562  And the Life expectation in difference case will be shown on the right.
563 563  
564 -[[image:image-20221021111923-27.png||height="253" width="783"]] ​
699 +[[image:1666596205057-567.png]] ​
565 565  
566 -=== **2.16.3  ​Battery Note** ===
567 567  
702 +
703 +=== 2.16.3  ​Battery Note ===
704 +
705 +
568 568  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.
569 569  
570 -=== **2.16.4  Replace the battery** ===
571 571  
709 +
710 +=== 2.16.4  Replace the battery ===
711 +
712 +
572 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).
573 573  
574 574  
575 -= **3. ​ Access NB-IoT Module** =
576 576  
717 += 3. ​ Access NB-IoT Module =
718 +
719 +
577 577  Users can directly access the AT command set of the NB-IoT module.
578 578  
579 579  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/]] 
... ... @@ -580,10 +580,14 @@
580 580  
581 581  [[image:image-20221021112006-28.png]] ​
582 582  
583 -= **4.  Using the AT Commands** =
584 584  
585 -== **4.1  Access AT Commands** ==
586 586  
728 += 4.  Using the AT Commands =
729 +
730 +
731 +== 4.1  Access AT Commands ==
732 +
733 +
587 587  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]]
588 588  
589 589  AT+<CMD>?  : Help on <CMD>
... ... @@ -594,8 +594,9 @@
594 594  
595 595  AT+<CMD>=?  : Get the value
596 596  
597 -**General Commands**      
598 598  
745 +(% style="color:blue" %)**General Commands**      
746 +
599 599  AT  : Attention       
600 600  
601 601  AT?  : Short Help     
... ... @@ -618,15 +618,12 @@
618 618  
619 619  AT+SERVADDR  : Server Address
620 620  
621 -AT+TR      : Get or Set record time"
769 +AT+TR      :  Get or Set record time
622 622  
623 -
624 624  AT+NOUD      : Get or Set the number of data to be uploaded
625 625  
773 +AT+CDP     :  Read or Clear cached data
626 626  
627 -AT+CDP     : Read or Clear cached data
628 -
629 -
630 630  AT+ DEBUG   : Enable or Disable debug mode
631 631  
632 632  AT+ TTRIG   : Get or Set Alarm Base on Timeout
... ... @@ -637,16 +637,19 @@
637 637  
638 638  AT+ CLRC   : Clear current door open count
639 639  
640 -**COAP Management**      
641 641  
786 +(% style="color:blue" %)**COAP Management**      
787 +
642 642  AT+URI            : Resource parameters
643 643  
644 -**UDP Management**
645 645  
791 +(% style="color:blue" %)**UDP Management**
792 +
646 646  AT+CFM          : Upload confirmation mode (only valid for UDP)
647 647  
648 -**MQTT Management**
649 649  
796 +(% style="color:blue" %)**MQTT Management**
797 +
650 650  AT+CLIENT               : Get or Set MQTT client
651 651  
652 652  AT+UNAME  : Get or Set MQTT Username
... ... @@ -657,86 +657,71 @@
657 657  
658 658  AT+SUBTOPIC  : Get or Set MQTT subscription topic
659 659  
660 -**Information**          
661 661  
809 +(% style="color:blue" %)**Information**          
810 +
662 662  AT+FDR  : Factory Data Reset
663 663  
664 664  AT+PWORD  : Serial Access Password
665 665  
666 -= **​5.  FAQ** =
667 667  
668 -== **5.1 ​ How to Upgrade Firmware** ==
669 669  
670 -User can upgrade the firmware for 1) bug fix, 2) new feature release.
817 += ​5.  FAQ =
671 671  
672 -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]]
673 673  
674 -**Notice, **CPN01 **and **CPL01 **share the same mother board. They use the same connection and method to update.**
820 +== 5.1 ​ How to Upgrade Firmware ==
675 675  
676 676  
677 -= **6.  Trouble Shooting** =
823 +User can upgrade the firmware for 1) bug fix, 2) new feature release.
678 678  
679 -== **6.1  ​Connection problem when uploading firmware** ==
825 +Please see this link for how to upgrade:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
680 680  
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]]
827 +(% style="color:red" %)**Notice: **(% style="color:blue" %)**CPN01** (%%)**and (% style="color:blue" %)CPL01(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
682 682  
683 683  
684 -== **6.2  AT Command input doesn't work** ==
685 685  
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.
831 += 6.  Trouble Shooting =
687 687  
688 688  
689 -= **7. ​ Order Info** =
834 +== 6.1  ​Connection problem when uploading firmware ==
690 690  
691 -Part Number**:** CPN01
692 692  
837 +(% 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]]
693 693  
694 -= **8.  Packing Info** =
695 695  
696 -**Package Includes**:
697 697  
698 -* CPN01 Open/Close Sensor x 1
699 -* External antenna x 1
841 +== 6.2  AT Command input doesn't work ==
700 700  
701 -**Dimension and weight**:
702 702  
703 -* Size: 195 x 125 x 55 mm
704 -* Weight:   420g
844 +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.
705 705  
706 -= **9.  Support** =
707 707  
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]]
710 710  
711 -​
848 += 7. ​ Order Info =
712 712  
713 713  
851 +Part Number**:** CPN01
714 714  
715 715  
716 716  
855 += 8.  Packing Info =
717 717  
718 718  
858 +(% style="color:blue" %)**Package Includes**:
719 719  
860 +* CPN01 Open/Close Sensor x 1
861 +* External antenna x 1
720 720  
863 +(% style="color:blue" %)**Dimension and weight**:
721 721  
865 +* Size: 195 x 125 x 55 mm
866 +* Weight:   420g
722 722  
868 += 9.  Support =
723 723  
724 724  
871 +* 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.
725 725  
873 +* 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]]
726 726  
727 -
728 -
729 -
730 -
731 -
732 -
733 -
734 -
735 -
736 -
737 -
738 -
739 -
740 -
741 -
742 -
875 +​
1666596205057-567.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +179.8 KB
Content
image-20221117105556-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +133.3 KB
Content
image-20221117114459-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +14.9 KB
Content
image-20221117114842-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +964.1 KB
Content
image-20221117114937-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +79.1 KB
Content
image-20221117114949-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +33.4 KB
Content
image-20221117115010-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +40.4 KB
Content
image-20221117142300-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +147.8 KB
Content
image-20221117145932-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +51.9 KB
Content
image-20221117150312-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +8.7 KB
Content
image-20221118092935-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +13.1 KB
Content
image-20221118093144-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +11.7 KB
Content
image-20221118093512-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +9.5 KB
Content

Applications

Navigation

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