Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 38.1 >
edited by Edwin Chen
on 2022/10/22 23:49
To version < 58.2 >
edited by Xiaoling
on 2022/11/17 11:54
>
Change comment: There is no comment for this version

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.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -1,34 +1,66 @@
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 +
19 +== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
20 +
21 +
22 +(((
23 +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.
24 +)))
25 +
26 +(((
27 +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.
28 +)))
29 +
30 +(((
31 +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.
32 +)))
33 +
34 +(((
35 +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.
36 +)))
37 +
38 +(((
39 +NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
40 +)))
41 +
42 +(((
43 +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.
44 +)))
45 +
46 +(((
47 +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)
48 +)))
49 +
50 +(((
51 +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.
52 +)))
53 +
54 +
55 +
56 +== ​1.2  Features ==
57 +
58 +
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
63 +* connect two door sensors
32 32  * Datalog feature
33 33  * Uplink periodically
34 34  * Downlink to change configure
... ... @@ -39,14 +39,47 @@
39 39  * Micro SIM card slot for NB-IoT SIM
40 40  * 8500mAh Battery for long-term use
41 41  
42 -== **1.3  Specification** ==
43 43  
44 -**Common DC Characteristics:**
45 45  
76 +
77 +== 1.3  Storage & Operation ==
78 +
79 +
80 +Temperature -40°C to +85°C
81 +
82 +
83 +== 1.4  Mechanical ==
84 +
85 +
86 +[[image:image-20221117114937-4.png]]
87 +
88 +
89 +[[image:image-20221117114949-5.png]]
90 +
91 +
92 +[[image:image-20221117115010-6.png]]
93 +
94 +
95 +
96 +
97 +
98 +
99 +== 1.5 ​ Applications ==
100 +
101 +
102 +[[image:image-20221117114842-3.png]]
103 +
104 +
105 +
106 +== 1.6  Specification ==
107 +
108 +
109 +(% style="color:blue" %)**Common DC Characteristics:**
110 +
46 46  * Supply Voltage: 2.1v ~~ 3.6v
47 47  * Operating Temperature: -40 ~~ 85°C
48 48  
49 -**NB-IoT Spec:**
114 +(% style="color:blue" %)**NB-IoT Spec:**
50 50  
51 51  * - B1 @H-FDD: 2100MHz
52 52  * - B3 @H-FDD: 1800MHz
... ... @@ -55,181 +55,228 @@
55 55  * - B20 @H-FDD: 800MHz
56 56  * - B28 @H-FDD: 700MHz
57 57  
58 -== **1.4 Installation** ==
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]]
125 +== 1.7  Pin Definitions and Switch ==
63 63  
64 -[[image:image-20221022234602-2.png||height="288" width="922"]]
65 65  
128 +[[image:image-20221021110429-4.png]]
66 66  
67 -== **1.5 ​Applications** ==
68 68  
69 -* Open/Close Detection
70 -* Pulse meter application
71 -* Dry Contact Detection
131 +=== 1.7.1  Pin Definition ===
72 72  
73 73  
74 -== **1.6 Mechanical** ==
134 +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]]**.
75 75  
76 -​[[image:image-20221021110415-3.png]]
77 77  
78 -== ** 1.7 Pin Definitions and Switch** ==
79 79  
80 -[[image:image-20221021110429-4.png]]
138 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
81 81  
82 -=== **1.7.1 Pin Definition** ===
83 83  
84 -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]]**.
141 +Power on Device when putting this jumper.
85 85  
86 86  
87 -=== **1.7.2 Jumper JP2(Power ON/OFF)** ===
88 88  
89 -Power on Device when putting this jumper.
145 +=== 1.7.3  BOOT MODE / SW1 ===
90 90  
91 91  
92 -=== **1.7.3 BOOT MODE / SW1** ===
148 +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.
93 93  
150 +2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
94 94  
95 -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.
96 96  
97 -2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
98 98  
154 +=== 1.7.4  Reset Button ===
99 99  
100 -=== **1.7.4 Reset Button** ===
101 101  
102 -
103 103  Press to reboot the device.
104 104  
105 -== ==
106 106  
107 -=== **1.7.5 LED** ===
108 108  
161 +=== 1.7.5  LED ===
109 109  
163 +
110 110  The LED will blink when :
111 111  
112 -1. Boot the device in flash mode
113 -1. Send an uplink packet
166 +1.  Boot the device in flash mode
114 114  
168 +2.  Send an uplink packet
115 115  
116 -= **2.  Use CPN01 to communicate with IoT Server** =
117 117  
118 -== **2.1  How it works** ==
119 119  
120 -The CPN01 is equipped with a NB-IoT module, the pre-loaded firmware in CPN01 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01.
172 +== 1.8  Magnet Distance ==
121 121  
122 -The diagram below shows the working flow in default firmware of CPN01:
123 123  
175 +**Wood Door:** 10 ~~ 30mm
176 +
177 +**Iron Door:  **30 ~~ 45mm
178 +
179 +
180 +
181 += 2.  Use CPN01 to communicate with IoT Server =
182 +
183 +
184 +== 2.1  How it works ==
185 +
186 +
187 +The CPN01 is equipped with an NB-IoT module, the pre-loaded firmware in CPN01 will get (% style="color:blue" %)**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.
188 +
189 +The diagram below shows the working flow in the default firmware of CPN01:
190 +
124 124  [[image:image-20221021110615-5.png]]
125 125  
126 -== **2.2 ​ Configure the CPN01** ==
127 127  
128 -=== **2.2.1 Test Requirement** ===
129 129  
130 -To use CPN01 in your city, make sure meet below requirements:
195 +== 2.2 ​ Configure CPN01 ==
131 131  
132 -* Your local operator has already distributed a NB-IoT Network there.
197 +
198 +=== 2.2.1 Test Requirement ===
199 +
200 +
201 +To use CPN01 in your city, make sure to meet below requirements:
202 +
203 +* Your local operator has already distributed an NB-IoT Network.
133 133  * The local NB-IoT network used the band that CPN01 supports.
134 134  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
135 135  
136 -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
207 +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** (% 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.
137 137  
209 +[[image:image-20221023000439-3.png]]
210 +
138 138   ​
139 139  
140 -=== **2.2.2 Insert SIM card** ===
141 141  
214 +=== 2.2.2 Insert NB-IoT SIM card ===
215 +
216 +
142 142  Insert the NB-IoT Card get from your provider.
143 143  
144 -User need to take out the NB-IoT module and insert the SIM card like below:
219 +User needs to take out the NB-IoT module and insert the SIM card like below:
145 145  
146 146  [[image:image-20221021110745-6.png]] ​
147 147  
148 -=== **2.2.3 Connect USB – TTL to CPN01 to configure it** ===
149 149  
150 -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.
151 151  
152 -**Connection:**
225 +=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
153 153  
154 - USB TTL GND <~-~-~-~-> GND
155 155  
156 - USB TTL TXD <~-~-~-~-> UART_RXD
228 +User need to configure CPN01 via serial port to set the (% style="color:red" %)**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.
157 157  
158 - USB TTL RXD <~-~-~-~-> UART_TXD
230 +(% style="color:blue" %)**Connection:**
159 159  
232 +(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
233 +
234 +(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD**
235 +
236 +(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD**
237 +
238 +
160 160  In the PC, use below serial tool settings:
161 161  
162 -* Baud:  **9600**
163 -* Data bits:** 8**
164 -* Stop bits: **1**
165 -* Parity:  **None**
166 -* Flow Control: **None**
241 +* Baud:  (% style="color:red" %)**9600**
167 167  
168 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on CPN01. CPN01 will output system info once power on as below, we can enter the **password: 12345678** to access AT Command input.
243 +* Data bits:** (% style="color:red" %)8(%%)**
169 169  
245 +* Stop bits: (% style="color:red" %)**1**
246 +
247 +* Parity:  (% style="color:red" %)**None**
248 +
249 +* Flow Control: (% style="color:red" %)**None**
250 +
251 +Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
252 +
170 170  ​[[image:image-20221021110817-7.png]]
171 171  
172 -**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]]
255 +CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
173 173  
174 -=== **2.2.4 Use CoAP protocol to uplink data** ===
175 175  
176 -**Note: if you don't have CoAP server, you can refer this link to set up one: **[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
258 +(% 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 -**Use below commands:**
179 179  
180 -* **AT+PRO=1**   ~/~/ Set to use CoAP protocol to uplink
181 -* **AT+SERVADDR=120.24.4.116,5683   ** ~/~/ to set CoAP server address and port
182 -* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path
183 183  
262 +=== 2.2.4 Use CoAP protocol to uplink data ===
263 +
264 +
265 +(% 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/]]
266 +
267 +
268 +(% style="color:blue" %)**Use below commands in CPN01:**
269 +
270 +* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
271 +
272 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/ Set CoAP server address and port
273 +
274 +* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/  Set CoAP resource path
275 +
184 184  For parameter description, please refer to AT command set
185 185  
186 186  [[image:image-20221021110948-8.png]]
187 187  
188 -After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server.
189 189  
281 +After configuring the server address and (% style="color:green" %)**reset CPN01**(%%) (via AT+ATZ ), CPN01 will start to uplink sensor values to the CoAP server.
282 +
190 190  [[image:image-20221021110956-9.png]] ​
191 191  
192 -=== **2.2.5 Use UDP protocol to uplink data(Default protocol)** ===
193 193  
194 -This feature is supported since firmware version v1.0.1
195 195  
196 -* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
197 -* **AT+SERVADDR=120.24.4.116,5601   ** ~/~/ to set UDP server address and port
198 -* **AT+CFM=1       ** ~/~/If the server does not respond, this command is unnecessary
287 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
199 199  
289 +
290 +(% style="color:blue" %)**AT Commands:**
291 +
292 +* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
293 +
294 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  Set UDP server address and port
295 +
296 +* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
297 +
200 200  ​ [[image:image-20221021111025-10.png]]
201 201  
300 +
202 202  [[image:image-20221021111033-11.png||height="241" width="576"]]
203 203  
204 204  ​
205 205  
206 -=== **2.2.6 Use MQTT protocol to uplink data** ===
207 207  
208 -This feature is supported since firmware version v110
306 +=== 2.2.6 Use MQTT protocol to uplink data ===
209 209  
210 -* **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
211 -* **AT+SERVADDR=120.24.4.116,1883   ** ~/~/Set MQTT server address and port
212 -* **AT+CLIENT=CLIENT       ** ~/~/Set up the CLIENT of MQTT
213 -* **AT+UNAME=UNAME                               **~/~/Set the username of MQTT
214 -* **AT+PWD=PWD                                        **~/~/Set the password of MQTT
215 -* **AT+PUBTOPIC=NSE01_PUB                    **~/~/Set the sending topic of MQTT
216 -* **AT+SUBTOPIC=NSE01_SUB          ** ~/~/Set the subscription topic of MQTT
217 217  
309 +(% style="color:blue" %)**AT Commands:**
310 +
311 +* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
312 +
313 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
314 +
315 +* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
316 +
317 +* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/  Set the username of MQTT
318 +
319 +* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/  Set the password of MQTT
320 +
321 +* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)** **~/~/  Set the sending topic of MQTT
322 +
323 +* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
324 +
218 218  ​ [[image:image-20221021111058-12.png]]
219 219  
220 -[[image:image-20221021111108-13.png]]
221 221  
328 +[[image:image-20221021111201-16.png||height="472" width="653"]]
329 +
222 222  ​
223 223  
224 -MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
332 +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.
225 225  
226 -=== **2.2.7 Use TCP protocol to uplink data** ===
227 227  
228 -This feature is supported since firmware version v110
229 229  
230 -* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
231 -* **AT+SERVADDR=120.24.4.116,5600   ** ~/~/ to set TCP server address and port
336 +=== 2.2.7 Use TCP protocol to uplink data ===
232 232  
338 +
339 +(% style="color:blue" %)**AT Commands:**
340 +
341 +* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
342 +
343 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
344 +
233 233  ​ [[image:image-20221021111125-14.png]]
234 234  
235 235  [[image:image-20221021111131-15.png]]
... ... @@ -236,85 +236,103 @@
236 236  
237 237  ​
238 238  
239 -=== **2.2.8 Change Update Interval** ===
240 240  
241 -User can use below command to change the **uplink interval**.
352 +=== 2.2.8 Change Update Interval ===
242 242  
243 -* **AT+TDC=600      ** ~/~/ Set Update Interval to 600s
244 244  
245 -**NOTE:**
355 +User can use below command to change the (% style="color:blue" %)**uplink interval**.
246 246  
247 -**~1. By default, the device will send an uplink message every 1 hour.**
357 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
248 248  
249 -== **2.3  Uplink Payload** ==
359 +(% style="color:red" %)**NOTE:**
250 250  
251 -In this mode, uplink payload includes 87 bytes in total by default.
361 +1.  By default, the device will send an uplink message every 1 hour.
252 252  
363 +
364 +
365 +== 2.3  Uplink Payload ==
366 +
367 +
368 +The uplink payload includes 123 bytes in total by default.
369 +
253 253  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.
254 254  
255 -|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**2**|**2**|4
256 -|**Value**|[[Device ID>>path:#H2.4.1A0A0DeviceID]]|[[Ver>>path:#H2.4.2A0VersionInfo]]|[[BAT>>path:#H2.4.3A0BatteryInfo]]|[[Signal Strength>>path:#H2.4.4A0SignalStrength]]|MOD|[[Interrupt>>path:#H2.4.8A0DigitalInterrupt]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|Time stamp
257 257  
258 -|2|2|4|8 group
259 -|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|Time stamp|...
373 +(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
374 +|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:60px" %)**3**
375 +|=(% style="width: 96px;" %)**Value**|(% style="width:84px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:44px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:121px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:52px" %)MOD|(% style="width:84px" %)[[ Calculate Flag>>||anchor="H2.4.5A0CalculateFlag"]]|(% style="width:116px" %)[[Contact Status>>||anchor="H2.4.7A0ContactStatus"]]|(% style="width:57px" %)[[Alarm>>||anchor="H2.4.6A0Alarm"]]|(% style="width:91px" %)[[Total pulse>>||anchor="H2.4.8A0Totalpulse"]]
260 260  
377 +(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
378 +|(% style="width:100px" %)**3**|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:100px" %)**3**|(% style="width:80px" %)4|(% style="width:50px" %)**8 group**
379 +|(% style="width:176px" %)[[The last open duration>>||anchor="H2.4.9A0Thelastopenduration"]]|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% style="width:115px" %)Contact Status|(% style="width:92px" %)Total pulse|(% style="width:169px" %)The last open duration|(% style="width:97px" %)Time stamp|(% style="width:74px" %)...
380 +
261 261  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
262 262  
263 263  [[image:image-20221021111201-16.png||height="572" width="792"]]
264 264  
385 +
265 265  The payload is ASCII string, representative same HEX:
266 266  
267 -**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 //(%%)**
388 +**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0c78__(% style="color:#00b0f0" %) __17__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__ (% style="color:#660066" %)__00__ (% style="color:#aaaa40" %)__000009__(% style="color:#663300" %) __000002__ (% style="color:#d60093" %)__6315537b__ (% style="color:#660066" %)__01 00000b 02 0000026 63510fed__ (%%)__0100000e0200000263510f39__ __010000000000000063510e85__ __010000000000000063510d2e__ __010000000000000063510c7a__ __010000000000000063510bc6__ __010000000000000063510954__ __010000000000000063510882 __**
268 268  
269 -where:
270 -*(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317
390 +**where:**
271 271  
272 -*(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0
392 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
273 273  
274 -*(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
394 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
275 275  
276 -*(% style="color:#037691" %) **Singal: **(%%)0x17 = 23
396 +* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
277 277  
278 -*(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
398 +* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
279 279  
280 -*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00= 0
400 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
281 281  
282 -*(% style="color:#037691" %) **Contact Status:**(%%) 0x00= 0
402 +* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
283 283  
284 -*(% style="color:#037691" %) **Alarm:**(%%)0x00 =0
404 +* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
285 285  
286 -*(% style="color:#037691" %) **Total pulse:0x09 =0**
406 +* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
287 287  
288 -*(% style="color:#037691" %) **The last open duration:**(%%)0x02 =2
408 +* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
289 289  
290 -*(% style="color:#037691" %)**Time stamp :**(%%) 0x6315537b =1662342011
410 +* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
291 291  
292 -*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000b0200002663510fed
412 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
293 293  
294 -*(% style="color:#037691" %) **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
414 +* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
295 295  
296 -== **2.4  Payload Explanation and Sensor Interface** ==
416 +* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
297 297  
298 -=== **2.4.1  Device ID** ===
418 +== 2.4  Payload Explanation and Sensor Interface ==
299 299  
300 -By default, the Device ID equal to the last 15 bits of IMEI.
301 301  
302 -User can use **AT+DEUI** to set Device ID
421 +=== 2.4.1  Device ID ===
303 303  
423 +
424 +By default, the Device ID is equal to the last 15 bits of IMEI.
425 +
426 +User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
427 +
304 304  **Example:**
305 305  
306 306  AT+DEUI=868411056754138
307 307  
308 -The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
432 +The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
309 309  
310 -=== **2.4.2  Version Info** ===
311 311  
312 -Specify the software version: 0x64=100, means firmware version 1.00.
313 313  
314 -For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0.
436 +=== 2.4.2  Version Info ===
315 315  
316 -=== **2.4.3  Battery Info** ===
317 317  
439 +Specify the software version: 0x64=100, which means firmware version 1.00.
440 +
441 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
442 +
443 +
444 +
445 +=== 2.4.3  Battery Info ===
446 +
447 +
318 318  Check the battery voltage for CPN01.
319 319  
320 320  Ex1: 0x0B45 = 2885mV
... ... @@ -321,8 +321,11 @@
321 321  
322 322  Ex2: 0x0B49 = 2889mV
323 323  
324 -=== **2.4.4  Signal Strength** ===
325 325  
455 +
456 +=== 2.4.4  Signal Strength ===
457 +
458 +
326 326  NB-IoT Network signal Strength.
327 327  
328 328  **Ex1: 0x1d = 29**
... ... @@ -337,10 +337,13 @@
337 337  
338 338  **99**    Not known or not detectable
339 339  
340 -=== **2.4.5 Calculate Flag** ===
341 341  
342 -The calculate flag is a user define field, IoT server can use this filed to handle different meter with different pulse factor. For example, if there are 100 water meters, meter 1 ~~50 are 1 liter/pulse and meter 51 ~~ 100 has 1.5 liter/pulse.
343 343  
475 +=== 2.4.5  Calculate Flag ===
476 +
477 +
478 +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.
479 +
344 344  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.
345 345  
346 346  Default value: 0. 
... ... @@ -347,24 +347,36 @@
347 347  
348 348  Range (6 bits): (b)000000 ~~ (b) 111111
349 349  
350 -=== **2.4.6  Alarm** ===
351 351  
352 -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]]
353 353  
354 -=== **2.4.7 Contact Status** ===
488 +=== 2.4.6  Alarm ===
355 355  
490 +
491 +See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
492 +
493 +
494 +
495 +=== 2.4.7  Contact Status ===
496 +
497 +
356 356  0: Open
357 357  
358 358  1: Close
359 359  
360 -=== **2.4.8 Total pulse** ===
361 361  
362 -Total pulse/counting base on dry [[contact trigger event>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.2SensorConfiguration2CFPORT3D4]]
363 363  
504 +=== 2.4.8  Total pulse ===
505 +
506 +
507 +Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
508 +
364 364  Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
365 365  
366 -=== **2.4.9 The last open duration** ===
367 367  
512 +
513 +=== 2.4.9  The last open duration ===
514 +
515 +
368 368  Dry Contact last open duration.
369 369  
370 370  Unit: min.
... ... @@ -372,23 +372,28 @@
372 372  [[image:image-20221021111346-17.png||height="146" width="770"]]
373 373  
374 374  
375 -=== **2.4.10  Timestamp** ===
376 376  
377 -Time stamp : 0x6315537b =1662342011
524 +=== 2.4.10  Timestamp ===
378 378  
526 +
527 +Timestamp : 0x6315537b =1662342011
528 +
379 379  Convert Unix timestamp to time 2022-9-5 9:40:11.
380 380  
381 381  **~ **
382 382  
383 -== **2.5  Downlink Payload** ==
384 384  
534 +== 2.5  Downlink Payload ==
535 +
536 +
385 385  By default, CPN01 prints the downlink payload to console port.
386 386  
387 387  [[image:image-20221021111414-18.png]] ​
388 388  
541 +
389 389  **Examples:**
390 390  
391 -* **Set TDC**
544 +* (% style="color:#037691" %)**Set TDC**
392 392  
393 393  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
394 394  
... ... @@ -396,36 +396,39 @@
396 396  
397 397  Payload:    01 00 00 3C    TDC=60S
398 398  
399 -* **Reset**
552 +* (% style="color:#037691" %)**Reset**
400 400  
401 401  If payload = 0x04FF, it will reset the NSE01
402 402  
403 -* **INTMOD**
556 +* (% style="color:#037691" %)**INTMOD**
404 404  
405 405  Downlink Payload: 06000003, Set AT+INTMOD=3
406 406  
407 -== **2.6  ​LED Indicator** ==
408 408  
409 -The CPN01 has an internal LED which is to show the status of different state.
410 410  
411 -* When power on, CPN01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
412 -* Then the LED will be on for 1 second means device is boot normally.
562 +== 2.6  ​LED Indicator ==
563 +
564 +
565 +The CPN01 has an internal LED which is to show the status of different states.
566 +
567 +* When the device starts normally, the LED will light up for 1 second.
413 413  * After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
414 414  * For each uplink probe, LED will be on for 500ms.
415 415  
416 -== **2.7  Alarm Base on Timeout** ==
571 +== 2.7  Alarm Base on Timeout ==
417 417  
418 -CPL01 can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are:
419 419  
574 +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:
420 420  
421 -**~1. Keep Status: Status to be monitor**
422 422  
577 +(% style="color:blue" %)**1. Keep Status: Status to be monitor**
578 +
423 423  Keep Status = 1: Monitor Close to Open event
424 424  
425 425  Keep Status = 0: Monitor Open to Close event
426 426  
427 427  
428 -**2. Keep Time: Timeout to send an Alarm**
584 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
429 429  
430 430  Range 0 ~~ 65535(0xFFFF) seconds.
431 431  
... ... @@ -434,123 +434,164 @@
434 434  If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
435 435  
436 436  
437 -**AT Command** to configure:
593 +(% style="color:blue" %)**AT Command to configure:**
438 438  
439 -**AT+TTRIG=1,30**  ~-~-> When the **Keep Status** change from connect to disconnect, and device remains in disconnect status for more than 30 seconds. CPL01 will send an uplink packet, the [[Alarm bit>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.
595 +(% 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.
440 440  
441 -**AT+TTIG=0,0 ** ~-~-> Default Value, disable timeout Alarm.
597 +(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
442 442  
443 -== **2.8 Set debug mode** ==
444 444  
445 -Feature: Enable or Disable debug mode
446 446  
601 +== 2.8  Set debug mode ==
447 447  
448 -**AT Command: AT+DEBUG**
449 449  
604 +Feature: Enable or Disable debug mode
605 +
606 +(% style="color:blue" %)**AT Command: AT+DEBUG**
607 +
450 450  [[image:image-20221021111629-21.png]]
451 451  
452 -== **2.9 Clear Flash Record** ==
453 453  
611 +
612 +== 2.9  Clear Flash Record ==
613 +
614 +
454 454  Feature: Clear flash storage for data log feature.
455 455  
456 -**AT Command: AT+CLRDTA**
617 +(% style="color:blue" %)**AT Command: AT+CLRDTA**
457 457  
458 458  [[image:image-20221021111527-19.png]]
459 459  
460 -== ** 2.10 Set trigger mode** ==
461 461  
462 -➢ AT Command: **AT+TTRMOD**
463 463  
623 +== 2.10  Set trigger mode ==
624 +
625 +
626 +(% style="color:blue" %)**AT Command: AT+TTRMOD**
627 +
464 464  Feature: Set the trigger interrupt mode.
465 465  
466 466  [[image:image-20221021111552-20.png]]
467 467  
468 -== **2.11 Set the calculate flag** ==
469 469  
633 +
634 +== 2.11  Set the calculate flag ==
635 +
636 +
470 470  Feature: Set the calculate flag
471 471  
472 -**AT Command: AT+CALCFLAG**
639 +(% style="color:blue" %)**AT Command: AT+CALCFLAG**
473 473  
474 474  [[image:image-20221021111711-22.png]]
475 475  
476 -== **2.12 Set count number** ==
477 477  
644 +
645 +== 2.12 Set count number ==
646 +
647 +
478 478  Feature: Manually set the count number
479 479  
480 -**AT Command: AT+SETCNT**
650 +(% style="color:blue" %)**AT Command: AT+SETCNT**
481 481  
482 482  [[image:image-20221021111748-24.png]]
483 483  
484 -== **2.13 Set the number of data to be uploaded and the recording time** ==
485 485  
486 -➢ AT Command:
487 487  
488 -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)
656 +== 2.13  Set the number of data to be uploaded and the recording time ==
489 489  
490 490  
491 -AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
659 +(% style="color:blue" %)**AT Command:**
492 492  
493 -== **2.14 Read or Clear cached data** ==
661 +(% 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)
494 494  
495 -➢ AT Command:
663 +(% 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.
496 496  
497 -AT+CDP    ~/~/ Read cached data
498 498  
666 +
667 +== 2.14  Read or Clear cached data ==
668 +
669 +
670 +(% style="color:blue" %)**AT Command:**
671 +
672 +(% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
673 +
674 +(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
675 +
499 499  [[image:image-20221021111810-25.png||height="364" width="797"]]
500 500  
501 501  
502 -AT+CDP=0    ~/~/ Clear cached data ​
503 503  
504 -== **2.15  ​Firmware Change Log** ==
680 +== 2.15  ​Firmware Change Log ==
505 505  
506 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
507 507  
508 -Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
683 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
509 509  
510 -== **2.16  ​Battery Analysis** ==
685 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
511 511  
512 -=== **2.16.1  ​Battery Type** ===
513 513  
514 -The CPN01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
515 515  
516 -The battery is designed to last for several years depends on the actually use environment and update interval. 
689 +== 2.16  ​Battery Analysis ==
517 517  
518 -The battery related documents as below:
519 519  
692 +=== 2.16.1  ​Battery Type ===
693 +
694 +
695 +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.
696 +
697 +The battery is designed to last for several years depends on the actual use environment and update interval. 
698 +
699 +The battery-related documents as below:
700 +
520 520  * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
702 +
521 521  * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
704 +
522 522  * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
523 523  
524 524  [[image:image-20221021111911-26.png]] ​
525 525  
526 -=== **2.16.2  Power consumption Analyze** ===
527 527  
710 +
711 +=== 2.16.2  Power consumption Analyze ===
712 +
713 +
528 528  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.
529 529  
530 530  Instruction to use as below:
531 531  
532 -**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/]]
718 +(% 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/]]
533 533  
534 -**Step 2: ** Open it and choose
720 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
535 535  
536 536  * Product Model
723 +
537 537  * Uplink Interval
725 +
538 538  * Working Mode
539 539  
540 540  And the Life expectation in difference case will be shown on the right.
541 541  
542 -[[image:image-20221021111923-27.png||height="253" width="783"]] ​
730 +[[image:1666596205057-567.png]] ​
543 543  
544 -=== **2.16.3  ​Battery Note** ===
545 545  
733 +
734 +=== 2.16.3  ​Battery Note ===
735 +
736 +
546 546  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.
547 547  
548 -=== **2.16.4  Replace the battery** ===
549 549  
740 +
741 +=== 2.16.4  Replace the battery ===
742 +
743 +
550 550  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).
551 551  
552 -= **3. ​ Access NB-IoT Module** =
553 553  
747 +
748 += 3. ​ Access NB-IoT Module =
749 +
750 +
554 554  Users can directly access the AT command set of the NB-IoT module.
555 555  
556 556  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/]] 
... ... @@ -557,10 +557,14 @@
557 557  
558 558  [[image:image-20221021112006-28.png]] ​
559 559  
560 -= **4.  Using the AT Commands** =
561 561  
562 -== **4.1  Access AT Commands** ==
563 563  
759 += 4.  Using the AT Commands =
760 +
761 +
762 +== 4.1  Access AT Commands ==
763 +
764 +
564 564  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]]
565 565  
566 566  AT+<CMD>?  : Help on <CMD>
... ... @@ -571,8 +571,9 @@
571 571  
572 572  AT+<CMD>=?  : Get the value
573 573  
574 -**General Commands**      
575 575  
776 +(% style="color:blue" %)**General Commands**      
777 +
576 576  AT  : Attention       
577 577  
578 578  AT?  : Short Help     
... ... @@ -595,15 +595,12 @@
595 595  
596 596  AT+SERVADDR  : Server Address
597 597  
598 -AT+TR      : Get or Set record time"
800 +AT+TR      :  Get or Set record time
599 599  
600 -
601 601  AT+NOUD      : Get or Set the number of data to be uploaded
602 602  
804 +AT+CDP     :  Read or Clear cached data
603 603  
604 -AT+CDP     : Read or Clear cached data
605 -
606 -
607 607  AT+ DEBUG   : Enable or Disable debug mode
608 608  
609 609  AT+ TTRIG   : Get or Set Alarm Base on Timeout
... ... @@ -614,16 +614,19 @@
614 614  
615 615  AT+ CLRC   : Clear current door open count
616 616  
617 -**COAP Management**      
618 618  
817 +(% style="color:blue" %)**COAP Management**      
818 +
619 619  AT+URI            : Resource parameters
620 620  
621 -**UDP Management**
622 622  
822 +(% style="color:blue" %)**UDP Management**
823 +
623 623  AT+CFM          : Upload confirmation mode (only valid for UDP)
624 624  
625 -**MQTT Management**
626 626  
827 +(% style="color:blue" %)**MQTT Management**
828 +
627 627  AT+CLIENT               : Get or Set MQTT client
628 628  
629 629  AT+UNAME  : Get or Set MQTT Username
... ... @@ -634,86 +634,71 @@
634 634  
635 635  AT+SUBTOPIC  : Get or Set MQTT subscription topic
636 636  
637 -**Information**          
638 638  
840 +(% style="color:blue" %)**Information**          
841 +
639 639  AT+FDR  : Factory Data Reset
640 640  
641 641  AT+PWORD  : Serial Access Password
642 642  
643 -= **​5.  FAQ** =
644 644  
645 -== **5.1 ​ How to Upgrade Firmware** ==
646 646  
647 -User can upgrade the firmware for 1) bug fix, 2) new feature release.
848 += ​5.  FAQ =
648 648  
649 -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]]
650 650  
651 -**Notice, **CPN01 **and **CPN01 **share the same mother board. They use the same connection and method to update.**
851 +== 5.1 ​ How to Upgrade Firmware ==
652 652  
653 -== **5.2  Can I calibrate CPN01 to different soil types?** ==
654 654  
655 -CPN01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]].
854 +User can upgrade the firmware for 1) bug fix, 2) new feature release.
656 656  
657 -= **6.  Trouble Shooting** =
856 +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]]
658 658  
659 -== **6.1  ​Connection problem when uploading firmware** ==
858 +(% 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.**
660 660  
661 -**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]]
662 662  
663 -== **6.2  AT Command input doesn't work** ==
664 664  
665 -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.
862 += 6.  Trouble Shooting =
666 666  
667 -= **7. ​ Order Info** =
668 668  
669 -Part Number**:** CPN01
865 +== 6.1  ​Connection problem when uploading firmware ==
670 670  
671 -= **8.  Packing Info** =
672 672  
673 -**Package Includes**:
868 +(% 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]]
674 674  
675 -* CPN01 NB-IoT Soil Moisture & EC Sensor x 1
676 -* External antenna x 1
677 677  
678 -**Dimension and weight**:
679 679  
680 -* Size: 195 x 125 x 55 mm
681 -* Weight:   420g
872 +== 6.2  AT Command input doesn't work ==
682 682  
683 -= **9.  Support** =
684 684  
685 -* 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.
686 -* 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]]
875 +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.
687 687  
688 -​
689 689  
690 690  
879 += 7. ​ Order Info =
691 691  
692 692  
882 +Part Number**:** CPN01
693 693  
694 694  
695 695  
886 += 8.  Packing Info =
696 696  
697 697  
889 +(% style="color:blue" %)**Package Includes**:
698 698  
891 +* CPN01 Open/Close Sensor x 1
892 +* External antenna x 1
699 699  
894 +(% style="color:blue" %)**Dimension and weight**:
700 700  
896 +* Size: 195 x 125 x 55 mm
897 +* Weight:   420g
701 701  
899 += 9.  Support =
702 702  
703 703  
902 +* 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.
704 704  
904 +* 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]]
705 705  
706 -
707 -
708 -
709 -
710 -
711 -
712 -
713 -
714 -
715 -
716 -
717 -
718 -
719 -
906 +​
1666596205057-567.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +179.8 KB
Content
image-20221023000439-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +82.1 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

Applications

Navigation

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