Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 61.5 >
edited by Xiaoling
on 2022/11/17 16:45
To version < 25.1 >
edited by David Huang
on 2022/10/21 11:17
>
Change comment: Uploaded new attachment "image-20221021111730-23.png", version {1}

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
1 +CPN01- NB-IoT Outdoor Open/Close Dry Contact Sensor User Manual
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.David
Content
... ... @@ -1,67 +1,36 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20221117105556-1.png]]
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"]]
3 3  
4 4  
5 +**~1. Introduction**
5 5  
7 +**1.1 ​**What is CPN01 **NB-IOT** Pulse/Contact Sensor
6 6  
9 +The Dragino CPL01 is a **NB-IOT Contact Sensor**. It detects open/close status and uplink to IoT server via LoRaWAN network. user can see the dry contact status, open time, open counts in the IoT Server.
7 7  
11 +The CPL01 will send periodically data every day as well as for each dry contact action. It also counts the contact open times and calculate last open duration. User can also disable the uplink for each open/close event, instead, device can count each open event and uplink periodically.
8 8  
13 +CPL01 has the open alarm feature, user can set this feature so device will send Alarm if the contact has been open for a certain time.
9 9  
10 -**Table of Contents：**
15 +CPL01 is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
11 11  
17 +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.
18 +\\CPN01 supports different uplink methods include **TCP,MQTT,UDP and CoAP  **for different application requirement.
19 +\\CPN01 is powered by  **8500mAh Li-SOCI2 battery**, It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
20 +\\To use CPN01, user needs to check if there is NB-IoT coverage in local area and with the bands CPN01 supports. If the local operate support it, user needs to get a **NB-IoT SIM card** from local operator and install CPN01 to get NB-IoT network connection
12 12  
22 +​
13 13  
14 14  
25 +**​1.2 Features**
15 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 -
58 58  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
59 59  * Open/Close detect
60 60  * Open/Close statistics
61 61  * Monitor Battery Level
62 -* connect two door sensors
31 +* Uplink on periodically and open/close event
63 63  * Datalog feature
64 -* Uplink periodically
33 +* Uplink on periodically
65 65  * Downlink to change configure
66 66  * Wall Mountable
67 67  * Outdoor Use
... ... @@ -68,43 +68,16 @@
68 68  * Ultra-Low Power consumption
69 69  * AT Commands to change parameters
70 70  * Micro SIM card slot for NB-IoT SIM
71 -* 8500mAh Battery for long-term use
40 +* 8500mAh Battery for long term use
72 72  
73 -== 1.3  Storage & Operation ==
42 +**1.3  Specification**
74 74  
44 +**Common DC Characteristics:**
75 75  
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 -
104 104  * Supply Voltage: 2.1v ~~ 3.6v
105 105  * Operating Temperature: -40 ~~ 85°C
106 106  
107 -(% style="color:blue" %)**NB-IoT Spec:**
49 +**NB-IoT Spec:**
108 108  
109 109  * - B1 @H-FDD: 2100MHz
110 110  * - B3 @H-FDD: 1800MHz
... ... @@ -113,36 +113,47 @@
113 113  * - B20 @H-FDD: 800MHz
114 114  * - B28 @H-FDD: 700MHz
115 115  
116 -== 1.7  Pin Definitions and Switch ==
58 +**1.4 Installation**
117 117  
60 +Connect CPL01 to an Open Close sensor like below. So it can detect the open/close event.
118 118  
119 -[[image:image-20221021110429-4.png]]
62 +​[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image001.png]] [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image002.png]] ​
120 120  
64 +**1.5 ​Applications**
121 121  
122 -=== 1.7.1  Pin Definition ===
66 +* Open/Close Detection
67 +* Pulse meter application
68 +* Dry Contact Detection
123 123  
70 +**1.6 Mechanical**
124 124  
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 +​[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image003.png]]
126 126  
74 +**~ 1.7 Pin Definitions and Switch**
127 127  
76 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image004.png]]
128 128  
129 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
78 +**1.7.1 Pin Definition**
130 130  
80 +CPL01 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 user manual of LSN50v2 at: [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>url:https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]
131 131  
82 +**1.7.2 Jumper JP2(Power ON/OFF)**
83 +
84 +
132 132  Power on Device when putting this jumper.
133 133  
134 134  
135 135  
136 -=== 1.7.3  BOOT MODE / SW1 ===
89 +**1.7.3 BOOT MODE / SW1**
137 137  
138 138  
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.
92 +1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
140 140  
141 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
94 +2) Flash: work mode, the device starts to work and send out console output for further debug
142 142  
143 143  
144 144  
145 -=== 1.7.4  Reset Button ===
98 +**1.7.4 Reset Button**
146 146  
147 147  
148 148  Press to reboot the device.
... ... @@ -149,316 +149,214 @@
149 149  
150 150  
151 151  
152 -=== 1.7.5  LED ===
105 +**1.7.5 LED**
153 153  
154 154  
155 -The LED will blink when :
108 +It will flash:
156 156  
157 -1.  Boot the device in flash mode
110 +1. Boot the device in flash mode
111 +1. Send an uplink packet
158 158  
159 -2.  Send an uplink packet
160 160  
114 +**2.  Use CPN01 to communicate with IoT Server**
161 161  
116 +**2.1  How it works**
162 162  
163 -== 1.8  Magnet Distance ==
118 +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.
164 164  
120 +The diagram below shows the working flow in default firmware of CPN01:
165 165  
166 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
122 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image005.png||alt="说明: image-20220708101605-2.png"]]
167 167  
168 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
124 +**2.2 ​ Configure the CPN01**
169 169  
126 +**2.2.1 Test Requirement**
170 170  
128 +To use CPN01 in your city, make sure meet below requirements:
171 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 -
181 -[[image:image-20221021110615-5.png]]
182 -
183 -
184 -
185 -== 2.2 ​ Configure NDS03A ==
186 -
187 -=== 2.2.1 Test Requirement ===
188 -
189 -
190 -To use NDS03A in your city, make sure to meet below requirements:
191 -
192 -* Your local operator has already distributed an NB-IoT Network.
193 -* The local NB-IoT network used the band that NDS03A supports.
130 +* Your local operator has already distributed a NB-IoT Network there.
131 +* The local NB-IoT network used the band that CPN01 supports.
194 194  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
195 195  
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.
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
197 197  
198 -[[image:image-20221117142300-1.png]]
199 -
200 200   ​
201 201  
138 +**2.2.2 Insert SIM card**
202 202  
203 -=== 2.2.2 Insert NB-IoT SIM card ===
204 -
205 -
206 206  Insert the NB-IoT Card get from your provider.
207 207  
208 -User needs to take out the NB-IoT module and insert the SIM card like below:
142 +User need to take out the NB-IoT module and insert the SIM card like below:
209 209  
210 -[[image:image-20221021110745-6.png]] ​
144 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image006.png||alt="说明: 1657249468462-536.png"]] ​
211 211  
146 +**2.2.3 Connect USB – TTL to CPN01 to configure it**
212 212  
148 +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.
213 213  
214 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
150 +**Connection:**
215 215  
152 + USB TTL GND <~-~-~-~-> GND
216 216  
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.
154 + USB TTL TXD <~-~-~-~-> UART_RXD
218 218  
219 -(% style="color:blue" %)**Connection:**
156 + USB TTL RXD <~-~-~-~-> UART_TXD
220 220  
221 -(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
222 -
223 -(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD**
224 -
225 -(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD**
226 -
227 -
228 228  In the PC, use below serial tool settings:
229 229  
230 -* Baud:  (% style="color:red" %)**9600**
160 +* Baud:  **9600**
161 +* Data bits:** 8**
162 +* Stop bits: **1**
163 +* Parity:  **None**
164 +* Flow Control: **None**
231 231  
232 -* Data bits:** (% style="color:red" %)8(%%)**
166 +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.
233 233  
234 -* Stop bits: (% style="color:red" %)**1**
168 +​[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image007.png]]
235 235  
236 -* Parity:  (% style="color:red" %)**None**
170 +**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]]
237 237  
238 -* Flow Control: (% style="color:red" %)**None**
172 +**2.2.4 Use CoAP protocol to uplink data**
239 239  
240 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
174 +**Note: if you don't have CoAP server, you can refer this link to set up one: **[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
241 241  
242 -​[[image:image-20221021110817-7.png]]
176 +**Use below commands:**
243 243  
244 -NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
178 +* **AT+PRO=1**   ~/~/ Set to use CoAP protocol to uplink
179 +* **AT+SERVADDR=120.24.4.116,5683   ** ~/~/ to set CoAP server address and port
180 +* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path
245 245  
246 -
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]]
248 -
249 -
250 -
251 -=== 2.2.4 Use CoAP protocol to uplink data ===
252 -
253 -
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/]]
255 -
256 -
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 -
265 265  For parameter description, please refer to AT command set
266 266  
267 -[[image:image-20221021110948-8.png]]
184 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image008.png]]
268 268  
186 +After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server.
269 269  
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.
188 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image009.png]] ​
271 271  
272 -[[image:image-20221021110956-9.png]] ​
190 +**2.2.5 Use UDP protocol to uplink data(Default protocol)**
273 273  
192 +This feature is supported since firmware version v1.0.1
274 274  
194 +* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
195 +* **AT+SERVADDR=120.24.4.116,5601   ** ~/~/ to set UDP server address and port
196 +* **AT+CFM=1       ** ~/~/If the server does not respond, this command is unnecessary
275 275  
276 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
198 +​ [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image010.png]]
277 277  
200 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image011.png||alt="说明: 1657249930215-289.png"]]
278 278  
279 -(% style="color:blue" %)**AT Commands:**
280 -
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 -
287 -​ [[image:image-20221021111025-10.png]]
288 -
289 -
290 -[[image:image-20221021111033-11.png||height="241" width="576"]]
291 -
292 292  ​
293 293  
204 +**2.2.6 Use MQTT protocol to uplink data**
294 294  
295 -=== 2.2.6 Use MQTT protocol to uplink data ===
206 +This feature is supported since firmware version v110
296 296  
208 +* **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
209 +* **AT+SERVADDR=120.24.4.116,1883   ** ~/~/Set MQTT server address and port
210 +* **AT+CLIENT=CLIENT       ** ~/~/Set up the CLIENT of MQTT
211 +* **AT+UNAME=UNAME                               **~/~/Set the username of MQTT
212 +* **AT+PWD=PWD                                        **~/~/Set the password of MQTT
213 +* **AT+PUBTOPIC=NSE01_PUB                    **~/~/Set the sending topic of MQTT
214 +* **AT+SUBTOPIC=NSE01_SUB          ** ~/~/Set the subscription topic of MQTT
297 297  
298 -(% style="color:blue" %)**AT Commands:**
216 +​ [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image012.png]]
299 299  
300 -* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
218 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image013.png]]
301 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 -
314 -​ [[image:image-20221021111058-12.png]]
315 -
316 -
317 -[[image:image-20221021111201-16.png||height="472" width="653"]]
318 -
319 319  ​
320 320  
321 -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.
222 +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.
322 322  
224 +**2.2.7 Use TCP protocol to uplink data**
323 323  
226 +This feature is supported since firmware version v110
324 324  
325 -=== 2.2.7 Use TCP protocol to uplink data ===
228 +* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
229 +* **AT+SERVADDR=120.24.4.116,5600   ** ~/~/ to set TCP server address and port
326 326  
231 +​ [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image014.png]]
327 327  
328 -(% style="color:blue" %)**AT Commands:**
233 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image015.png||alt="说明: 1657250255956-604.png"]]
329 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 -
334 -​ [[image:image-20221021111125-14.png]]
335 -
336 -[[image:image-20221021111131-15.png]]
337 -
338 338  ​
339 339  
237 +**2.2.8 Change Update Interval**
340 340  
341 -=== 2.2.8 Change Update Interval ===
239 +User can use below command to change the **uplink interval**.
342 342  
241 +* **AT+TDC=600      ** ~/~/ Set Update Interval to 600s
343 343  
344 -User can use below command to change the (% style="color:blue" %)**uplink interval**.
243 +**NOTE:**
345 345  
346 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
245 +**~1. By default, the device will send an uplink message every 1 hour.**
347 347  
348 -(% style="color:red" %)**NOTE:**
247 +**2.3  Uplink Payload**
349 349  
350 -1.  By default, the device will send an uplink message every 4 hour.
249 +In this mode, uplink payload includes 87 bytes in total by default.
351 351  
251 +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.
352 352  
253 +|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**2**|**2**|4
254 +|**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
353 353  
354 -== 2.3  Uplink Payload ==
355 355  
257 +|2|2|4|8 group
258 +|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|Time stamp|...
356 356  
357 -The uplink payload includes 26 bytes in total by default.
260 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
358 358  
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.
262 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image016.png]]
360 360  
361 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
362 -
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)
366 -
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" %)...
372 -
373 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
374 -
375 -
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)
379 -
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)
383 -
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" %)...
389 -
390 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
391 -
392 -[[image:image-20221117145932-2.png]]
393 -
394 -
395 395  The payload is ASCII string, representative same HEX:
396 396  
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__(%%)**
266 +0xf86778705021331700640c7817010001000000090000026315537b 0100000b02000002663510fed0100000e0200000263510f39010000000000000063510e85010000000000000063510d2e010000000000000063510c7a010000000000000063510bc6010000000000000063510954010000000000000063510882 where:
398 398  
399 -**where:**
268 +* **Device ID: 0x f867787050213317 = f867787050213317**
269 +* **Version: 0x0064=100=1.0.0**
400 400  
401 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
271 +* **BAT: 0x0c78 = 3192 mV = 3.192V**
272 +* **Singal: 0x17 = 23**
273 +* **Mod: 0x01 = 1**
274 +* **Calculate Flag: 0x00= 0**
275 +* **Contact Status: 0x00= 0**
276 +* **Alarm:0x00 =0**
277 +* **Total pulse:0x09 =0**
278 +* **The last open duration:0x02 =2**
279 +* **Time stamp : 0x6315537b =1662342011**
280 +* **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp : 0100000b0200002663510fed**
281 +* **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp : 0100000e0200002663510f39,.......**
402 402  
403 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
283 +**2.4  Payload Explanation and Sensor Interface**
404 404  
405 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
285 +**2.4.1  Device ID**
406 406  
407 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
287 +By default, the Device ID equal to the last 15 bits of IMEI.
408 408  
409 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
289 +User can use **AT+DEUI** to set Device ID
410 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 -
427 -By default, the Device ID is equal to the last 15 bits of IMEI.
428 -
429 -User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
430 -
431 431  **Example:**
432 432  
433 433  AT+DEUI=868411056754138
434 434  
435 -The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
295 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
436 436  
297 +**2.4.2  Version Info**
437 437  
299 +Specify the software version: 0x64=100, means firmware version 1.00.
438 438  
439 -=== 2.4.2  Version Info ===
301 +For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0.
440 440  
303 +**2.4.3  Battery Info**
441 441  
442 -Specify the software version: 0x64=100, which means firmware version 1.00.
305 +Check the battery voltage for CPN01.
443 443  
444 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
445 -
446 -
447 -
448 -=== 2.4.3  Battery Info ===
449 -
450 -
451 -Check the battery voltage for NDS03A.
452 -
453 453  Ex1: 0x0B45 = 2885mV
454 454  
455 455  Ex2: 0x0B49 = 2889mV
456 456  
311 +**2.4.4  Signal Strength**
457 457  
458 -
459 -=== 2.4.4  Signal Strength ===
460 -
461 -
462 462  NB-IoT Network signal Strength.
463 463  
464 464  **Ex1: 0x1d = 29**
... ... @@ -473,76 +473,58 @@
473 473  
474 474  **99**    Not known or not detectable
475 475  
327 +**2.4.5 Calculate Flag**
476 476  
329 +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.
477 477  
478 -=== 2.4.5  Disalarm: (default: 0) ===
331 +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.
479 479  
333 +Default value: 0. 
480 480  
481 -(% 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.
335 +Range (6 bits): (b)000000 ~~ (b) 111111
482 482  
483 -(% 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.
337 +**2.4.6  Alarm**
484 484  
485 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
339 +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]]
486 486  
341 +**2.4.7 Contact Status**
487 487  
488 -
489 -=== 2.4.6  Alarm ===
490 -
491 -
492 -See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
493 -
494 -
495 -
496 -=== 2.4.7  Contact Status ===
497 -
498 -
499 499  0: Open
500 500  
501 501  1: Close
502 502  
347 +**2.4.8 Total pulse**
503 503  
349 +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]]
504 504  
505 -=== 2.4.8  Total pulse ===
506 -
507 -
508 -Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
509 -
510 510  Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
511 511  
353 +**2.4.9 The last open duration**
512 512  
513 -
514 -=== 2.4.9  The last open duration ===
515 -
516 -
517 517  Dry Contact last open duration.
518 518  
519 519  Unit: min.
520 520  
521 -[[image:image-20221021111346-17.png||height="146" width="770"]]
359 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image017.png]]
522 522  
523 523  
362 +**2.4.10  Timestamp**
524 524  
525 -=== 2.4.10  Timestamp ===
364 +Time stamp : 0x6315537b =1662342011
526 526  
527 -
528 -Timestamp : 0x6315537b =1662342011
529 -
530 530  Convert Unix timestamp to time 2022-9-5 9:40:11.
531 531  
532 532  **~ **
533 533  
370 +**2.5  Downlink Payload**
534 534  
535 -== 2.5  Downlink Payload ==
536 -
537 -
538 538  By default, CPN01 prints the downlink payload to console port.
539 539  
540 -[[image:image-20221021111414-18.png]] ​
374 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image018.png||alt="说明: image-20220708133731-5.png"]] ​
541 541  
542 -
543 543  **Examples:**
544 544  
545 -* (% style="color:#037691" %)**Set TDC**
378 +* **Set TDC**
546 546  
547 547  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
548 548  
... ... @@ -550,39 +550,36 @@
550 550  
551 551  Payload:    01 00 00 3C    TDC=60S
552 552  
553 -* (% style="color:#037691" %)**Reset**
386 +* **Reset**
554 554  
555 555  If payload = 0x04FF, it will reset the NSE01
556 556  
557 -* (% style="color:#037691" %)**INTMOD**
390 +* **INTMOD**
558 558  
559 559  Downlink Payload: 06000003, Set AT+INTMOD=3
560 560  
394 +**2.6  ​LED Indicator**
561 561  
396 +The CPN01 has an internal LED which is to show the status of different state.
562 562  
563 -== 2.6  ​LED Indicator ==
564 -
565 -
566 -The CPN01 has an internal LED which is to show the status of different states.
567 -
568 -* When the device starts normally, the LED will light up for 1 second.
398 +* 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)
399 +* Then the LED will be on for 1 second means device is boot normally.
569 569  * After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
570 570  * For each uplink probe, LED will be on for 500ms.
571 571  
572 -== 2.7  Alarm Base on Timeout ==
403 +**2.7 ** Alarm Base on Timeout
573 573  
405 +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:
574 574  
575 -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:
576 576  
408 +**~1. Keep Status: Status to be monitor**
577 577  
578 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
579 -
580 580  Keep Status = 1: Monitor Close to Open event
581 581  
582 582  Keep Status = 0: Monitor Open to Close event
583 583  
584 584  
585 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
415 +**2. Keep Time: Timeout to send an Alarm**
586 586  
587 587  Range 0 ~~ 65535(0xFFFF) seconds.
588 588  
... ... @@ -591,178 +591,140 @@
591 591  If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
592 592  
593 593  
594 -(% style="color:blue" %)**AT Command to configure:**
424 +**AT Command** to configure:
595 595  
596 -(% 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.
426 +**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.
597 597  
598 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
428 +**AT+TTIG=0,0 ** ~-~-> Default Value, disable timeout Alarm.
599 599  
430 +**2.8** Set debug mode
600 600  
601 -
602 -== 2.8  Set debug mode ==
603 -
604 -
605 605  Feature: Enable or Disable debug mode
606 606  
607 -(% style="color:blue" %)**AT Command: AT+DEBUG**
608 608  
609 -[[image:image-20221021111629-21.png]]
435 +**AT Command: AT+DEBUG**
610 610  
437 +|**Command Example**|**Function**|**Response**
438 +|AT+DEBUG =0|Disable debug mode to 0|OK
439 +|AT+ DEBUG =1|Enable debug mode to 1|OK
611 611  
441 +== 2.9 Clear Flash Record ==
612 612  
613 -== 2.9  Clear Flash Record ==
614 -
615 -
616 616  Feature: Clear flash storage for data log feature.
617 617  
618 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
445 +**AT Command: AT+CLRDTA**
619 619  
620 -[[image:image-20221021111527-19.png]]
447 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image019.png||alt="说明: image-20220609151132-7.png"]]
621 621  
449 +**~ 2.10 **Set trigger mode
622 622  
451 +➢ AT Command: **AT+TTRMOD**
623 623  
624 -== 2.10  Set trigger mode ==
625 -
626 -
627 -(% style="color:blue" %)**AT Command: AT+TTRMOD**
628 -
629 629  Feature: Set the trigger interrupt mode.
630 630  
631 -[[image:image-20221021111552-20.png]]
455 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image020.png||alt="说明: image-20220609151344-9.png"]]
632 632  
457 +**2.11** Set the calculate flag
633 633  
634 -
635 -== 2.11  Set the calculate flag ==
636 -
637 -
638 638  Feature: Set the calculate flag
639 639  
640 -(% style="color:blue" %)**AT Command: AT+CALCFLAG**
461 +**AT Command: AT+CALCFLAG**
641 641  
642 -[[image:image-20221021111711-22.png]]
463 +|**Command Example**|**Function**|**Response**
464 +|AT+CALCFLAG =1|Set the calculate flag to 1.|OK
465 +|AT+CALCFLAG =2|Set the calculate flag to 2.|OK
643 643  
467 +**2.12** Set count number
644 644  
645 -
646 -== 2.12 Set count number ==
647 -
648 -
649 649  Feature: Manually set the count number
650 650  
651 -(% style="color:blue" %)**AT Command: AT+SETCNT**
471 +**AT Command: AT+SETCNT**
652 652  
653 -[[image:image-20221021111748-24.png]]
473 +|**Command Example**|**Function**|**Response**
474 +|AT+ SETCNT =0|Set the count number to 0.|OK
475 +|AT+ SETCNT =100|Set the count number to 100.|OK
654 654  
655 655  
478 +**2.13 Set the number of data to be uploaded and the recording time**
656 656  
657 -== 2.13  Set the number of data to be uploaded and the recording time ==
480 +➢ AT Command:
658 658  
482 +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)
659 659  
660 -(% style="color:blue" %)**AT Command:**
661 661  
662 -(% 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)
485 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
663 663  
664 -(% 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.
487 +**2.14 Read or Clear cached data**
665 665  
489 +➢ AT Command:
666 666  
491 +AT+CDP    ~/~/ Read cached data
667 667  
668 -== 2.14  Read or Clear cached data ==
493 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image021.png]]
669 669  
670 670  
671 -(% style="color:blue" %)**AT Command:**
496 +AT+CDP=0    ~/~/ Clear cached data ​
672 672  
673 -(% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
498 +**2.15  ​Firmware Change Log**
674 674  
675 -(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
500 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
676 676  
677 -[[image:image-20221021111810-25.png||height="364" width="797"]]
502 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
678 678  
504 +**2.16  ​Battery Analysis**
679 679  
506 +**2.16.1  ​Battery Type**
680 680  
681 -== 2.15  ​Firmware Change Log ==
508 +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.
682 682  
510 +The battery is designed to last for several years depends on the actually use environment and update interval. 
683 683  
684 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
512 +The battery related documents as below:
685 685  
686 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
687 -
688 -
689 -
690 -== 2.16  ​Battery Analysis ==
691 -
692 -
693 -=== 2.16.1  ​Battery Type ===
694 -
695 -
696 -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.
697 -
698 -The battery is designed to last for several years depends on the actual use environment and update interval. 
699 -
700 -The battery-related documents as below:
701 -
702 702  * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
703 -
704 704  * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
705 -
706 706  * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
707 707  
708 -[[image:image-20221021111911-26.png]] ​
518 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image022.png||alt="说明: image-20220708140453-6.png"]] ​
709 709  
520 +**2.16.2  Power consumption Analyze**
710 710  
711 -
712 -=== 2.16.2  Power consumption Analyze ===
713 -
714 -
715 715  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.
716 716  
717 717  Instruction to use as below:
718 718  
719 -(% 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/]]
526 +**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/]]
720 720  
721 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
528 +**Step 2: ** Open it and choose
722 722  
723 723  * Product Model
724 -
725 725  * Uplink Interval
726 -
727 727  * Working Mode
728 728  
729 729  And the Life expectation in difference case will be shown on the right.
730 730  
731 -[[image:1666596205057-567.png]] ​
536 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image023.jpg||alt="说明: image-20220708141352-7.jpeg"]] ​
732 732  
538 +**2.16.3  ​Battery Note**
733 733  
734 -
735 -=== 2.16.3  ​Battery Note ===
736 -
737 -
738 738  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.
739 739  
542 +**2.16.4  Replace the battery**
740 740  
741 -
742 -=== 2.16.4  Replace the battery ===
743 -
744 -
745 745  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).
746 746  
546 +**3. ​ Access NB-IoT Module**
747 747  
748 -
749 -= 3. ​ Access NB-IoT Module =
750 -
751 -
752 752  Users can directly access the AT command set of the NB-IoT module.
753 753  
754 754  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/]] 
755 755  
756 -[[image:image-20221021112006-28.png]] ​
552 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image024.png||alt="说明: 1657261278785-153.png"]] ​
757 757  
554 +**4.  Using the AT Commands**
758 758  
556 +**4.1  Access AT Commands**
759 759  
760 -= 4.  Using the AT Commands =
761 -
762 -
763 -== 4.1  Access AT Commands ==
764 -
765 -
766 766  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]]
767 767  
768 768  AT+<CMD>?  : Help on <CMD>
... ... @@ -773,9 +773,8 @@
773 773  
774 774  AT+<CMD>=?  : Get the value
775 775  
568 +**General Commands**      
776 776  
777 -(% style="color:blue" %)**General Commands**      
778 -
779 779  AT  : Attention       
780 780  
781 781  AT?  : Short Help     
... ... @@ -798,12 +798,15 @@
798 798  
799 799  AT+SERVADDR  : Server Address
800 800  
801 -AT+TR      :  Get or Set record time
592 +AT+TR      : Get or Set record time"
802 802  
594 +
803 803  AT+NOUD      : Get or Set the number of data to be uploaded
804 804  
805 -AT+CDP     :  Read or Clear cached data
806 806  
598 +AT+CDP     : Read or Clear cached data
599 +
600 +
807 807  AT+ DEBUG   : Enable or Disable debug mode
808 808  
809 809  AT+ TTRIG   : Get or Set Alarm Base on Timeout
... ... @@ -814,19 +814,16 @@
814 814  
815 815  AT+ CLRC   : Clear current door open count
816 816  
611 +**COAP Management**      
817 817  
818 -(% style="color:blue" %)**COAP Management**      
819 -
820 820  AT+URI            : Resource parameters
821 821  
615 +**UDP Management**
822 822  
823 -(% style="color:blue" %)**UDP Management**
824 -
825 825  AT+CFM          : Upload confirmation mode (only valid for UDP)
826 826  
619 +**MQTT Management**
827 827  
828 -(% style="color:blue" %)**MQTT Management**
829 -
830 830  AT+CLIENT               : Get or Set MQTT client
831 831  
832 832  AT+UNAME  : Get or Set MQTT Username
... ... @@ -837,71 +837,86 @@
837 837  
838 838  AT+SUBTOPIC  : Get or Set MQTT subscription topic
839 839  
631 +**Information**          
840 840  
841 -(% style="color:blue" %)**Information**          
842 -
843 843  AT+FDR  : Factory Data Reset
844 844  
845 845  AT+PWORD  : Serial Access Password
846 846  
637 +**​5.  FAQ**
847 847  
639 +**5.1 ​ How to Upgrade Firmware**
848 848  
849 -= ​5.  FAQ =
641 +User can upgrade the firmware for 1) bug fix, 2) new feature release.
850 850  
643 +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]]
851 851  
852 -== 5.1 ​ How to Upgrade Firmware ==
645 +**Notice, **CPN01 **and **CPN01 **share the same mother board. They use the same connection and method to update.**
853 853  
647 +**5.2  Can I calibrate CPN01 to different soil types?**
854 854  
855 -User can upgrade the firmware for 1) bug fix, 2) new feature release.
649 +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]].
856 856  
857 -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]]
651 +**6.  Trouble Shooting**
858 858  
859 -(% 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.**
653 +**6.1  ​Connection problem when uploading firmware**
860 860  
655 +**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]]
861 861  
657 +**6.2  AT Command input doesn't work**
862 862  
863 -= 6.  Trouble Shooting =
659 +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.
864 864  
661 +**7. ​ Order Info**
865 865  
866 -== 6.1  ​Connection problem when uploading firmware ==
663 +Part Number**:** CPN01
867 867  
665 +**8.  Packing Info**
868 868  
869 -(% 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]]
667 +**Package Includes**:
870 870  
669 +* CPN01 NB-IoT Soil Moisture & EC Sensor x 1
670 +* External antenna x 1
871 871  
672 +**Dimension and weight**:
872 872  
873 -== 6.2  AT Command input doesn't work ==
674 +* Size: 195 x 125 x 55 mm
675 +* Weight:   420g
874 874  
677 +**9.  Support**
875 875  
876 -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.
679 +* 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.
680 +* 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]]
877 877  
682 +​
878 878  
879 879  
880 -= 7. ​ Order Info =
881 881  
882 882  
883 -Part Number**:** CPN01
884 884  
885 885  
886 886  
887 -= 8.  Packing Info =
888 888  
889 889  
890 -(% style="color:blue" %)**Package Includes**:
891 891  
892 -* CPN01 Open/Close Sensor x 1
893 -* External antenna x 1
894 894  
895 -(% style="color:blue" %)**Dimension and weight**:
896 896  
897 -* Size: 195 x 125 x 55 mm
898 -* Weight:   420g
899 899  
900 -= 9.  Support =
901 901  
902 902  
903 -* 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.
904 904  
905 -* 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]]
906 906  
907 -​
700 +
701 +
702 +
703 +
704 +
705 +
706 +
707 +
708 +
709 +
710 +
711 +
712 +
713 +
1666596205057-567.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -179.8 KB
Content
image-20221021111748-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -10.1 KB
Content
image-20221021111810-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -75.7 KB
Content
image-20221021111911-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -179.7 KB
Content
image-20221021111923-27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -130.6 KB
Content
image-20221021112006-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.5 KB
Content
image-20221022234529-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.3 KB
Content
image-20221022234602-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -135.7 KB
Content
image-20221023000439-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -82.1 KB
Content
image-20221117105556-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -133.3 KB
Content
image-20221117114459-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
image-20221117114842-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -964.1 KB
Content
image-20221117114937-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.1 KB
Content
image-20221117114949-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -33.4 KB
Content
image-20221117115010-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -40.4 KB
Content
image-20221117142300-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -147.8 KB
Content
image-20221117145932-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -51.9 KB
Content
image-20221117150312-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.7 KB
Content

Applications

Navigation

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