Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 70.4 >
edited by Xiaoling
on 2022/11/18 10:41
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,69 +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  
12 -{{toc/}}
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
13 13  
22 +​
14 14  
15 15  
25 +**​1.2 Features**
16 16  
17 -
18 -= 1.  Introduction =
19 -
20 -== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
21 -
22 -
23 -(((
24 -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.
25 -)))
26 -
27 -(((
28 -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.
29 -)))
30 -
31 -(((
32 -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.
33 -)))
34 -
35 -(((
36 -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.
37 -)))
38 -
39 -(((
40 -NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
41 -)))
42 -
43 -(((
44 -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.
45 -)))
46 -
47 -(((
48 -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)
49 -)))
50 -
51 -(((
52 -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.
53 -)))
54 -
55 -
56 -
57 -== ​1.2  Features ==
58 -
59 -
60 60  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
61 61  * Open/Close detect
62 62  * Open/Close statistics
63 63  * Monitor Battery Level
64 -* connect two door sensors
31 +* Uplink on periodically and open/close event
65 65  * Datalog feature
66 -* Uplink periodically
33 +* Uplink on periodically
67 67  * Downlink to change configure
68 68  * Wall Mountable
69 69  * Outdoor Use
... ... @@ -70,45 +70,16 @@
70 70  * Ultra-Low Power consumption
71 71  * AT Commands to change parameters
72 72  * Micro SIM card slot for NB-IoT SIM
73 -* 8500mAh Battery for long-term use
40 +* 8500mAh Battery for long term use
74 74  
42 +**1.3  Specification**
75 75  
44 +**Common DC Characteristics:**
76 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 -== 1.5 ​ Applications ==
97 -
98 -
99 -[[image:image-20221117114842-3.png]]
100 -
101 -
102 -
103 -== 1.6  Specification ==
104 -
105 -
106 -(% style="color:blue" %)**Common DC Characteristics:**
107 -
108 108  * Supply Voltage: 2.1v ~~ 3.6v
109 109  * Operating Temperature: -40 ~~ 85°C
110 110  
111 -(% style="color:blue" %)**NB-IoT Spec:**
49 +**NB-IoT Spec:**
112 112  
113 113  * - B1 @H-FDD: 2100MHz
114 114  * - B3 @H-FDD: 1800MHz
... ... @@ -117,339 +117,261 @@
117 117  * - B20 @H-FDD: 800MHz
118 118  * - B28 @H-FDD: 700MHz
119 119  
58 +**1.4 Installation**
120 120  
60 +Connect CPL01 to an Open Close sensor like below. So it can detect the open/close event.
121 121  
122 -== 1.7  Pin Definitions and Switch ==
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]] ​
123 123  
64 +**1.5 ​Applications**
124 124  
125 -[[image:image-20221021110429-4.png]]
66 +* Open/Close Detection
67 +* Pulse meter application
68 +* Dry Contact Detection
126 126  
70 +**1.6 Mechanical**
127 127  
128 -=== 1.7.1  Pin Definition ===
72 +​[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image003.png]]
129 129  
74 +**~ 1.7 Pin Definitions and Switch**
130 130  
131 -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]]
76 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image004.png]]
132 132  
78 +**1.7.1 Pin Definition**
133 133  
134 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
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]]
135 135  
82 +**1.7.2 Jumper JP2(Power ON/OFF)**
136 136  
84 +
137 137  Power on Device when putting this jumper.
138 138  
139 139  
140 -=== 1.7.3  BOOT MODE / SW1 ===
141 141  
89 +**1.7.3 BOOT MODE / SW1**
142 142  
143 -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.
144 144  
145 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
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.
146 146  
94 +2) Flash: work mode, the device starts to work and send out console output for further debug
147 147  
148 -=== 1.7.4  Reset Button ===
149 149  
150 150  
151 -Press to reboot the device.
98 +**1.7.4 Reset Button**
152 152  
153 153  
154 -=== 1.7.5  LED ===
101 +Press to reboot the device.
155 155  
156 156  
157 -The LED will blink when :
158 158  
159 -1.  Boot the device in flash mode
105 +**1.7.5 LED**
160 160  
161 -2.  Send an uplink packet
162 162  
108 +It will flash:
163 163  
164 -== 1.8  Magnet Distance ==
110 +1. Boot the device in flash mode
111 +1. Send an uplink packet
165 165  
166 166  
167 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
114 +**2.  Use CPN01 to communicate with IoT Server**
168 168  
169 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
116 +**2.1  How it works**
170 170  
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.
171 171  
172 -= 2.  Use NDS03A to communicate with IoT Server =
120 +The diagram below shows the working flow in default firmware of CPN01:
173 173  
174 -== 2.1  How it works ==
122 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image005.png||alt="说明: image-20220708101605-2.png"]]
175 175  
124 +**2.2 ​ Configure the CPN01**
176 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.
126 +**2.2.1 Test Requirement**
178 178  
179 -The diagram below shows the working flow in the default firmware of NDS03A:
128 +To use CPN01 in your city, make sure meet below requirements:
180 180  
181 -[[image:image-20221021110615-5.png]]
182 -
183 -
184 -== 2.2 ​ Configure NDS03A ==
185 -
186 -=== 2.2.1 Test Requirement ===
187 -
188 -
189 -To use NDS03A in your city, make sure to meet below requirements:
190 -
191 -* Your local operator has already distributed an NB-IoT Network.
192 -* 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.
193 193  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
194 194  
195 -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
196 196  
197 -[[image:image-20221117142300-1.png]]
136 + ​
198 198  
138 +**2.2.2 Insert SIM card**
199 199  
200 -=== 2.2.2 Insert NB-IoT SIM card ===
201 -
202 -
203 203  Insert the NB-IoT Card get from your provider.
204 204  
205 -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:
206 206  
207 -[[image:image-20221021110745-6.png]] ​
144 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image006.png||alt="说明: 1657249468462-536.png"]] ​
208 208  
146 +**2.2.3 Connect USB – TTL to CPN01 to configure it**
209 209  
210 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
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.
211 211  
150 +**Connection:**
212 212  
213 -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.
152 + USB TTL GND <~-~-~-~-> GND
214 214  
215 -(% style="color:blue" %)**Connection:**
154 + USB TTL TXD <~-~-~-~-> UART_RXD
216 216  
217 -(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
156 + USB TTL RXD <~-~-~-~-> UART_TXD
218 218  
219 -(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD**
220 -
221 -(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD**
222 -
223 -
224 224  In the PC, use below serial tool settings:
225 225  
226 -* Baud:  (% style="color:red" %)**9600**
160 +* Baud:  **9600**
161 +* Data bits:** 8**
162 +* Stop bits: **1**
163 +* Parity:  **None**
164 +* Flow Control: **None**
227 227  
228 -* 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.
229 229  
230 -* Stop bits: (% style="color:red" %)**1**
168 +​[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image007.png]]
231 231  
232 -* 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]]
233 233  
234 -* Flow Control: (% style="color:red" %)**None**
172 +**2.2.4 Use CoAP protocol to uplink data**
235 235  
236 -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/]]
237 237  
238 -​[[image:image-20221021110817-7.png]]
176 +**Use below commands:**
239 239  
240 -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
241 241  
242 -
243 -(% 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]]
244 -
245 -
246 -
247 -=== 2.2.4 Use CoAP protocol to uplink data ===
248 -
249 -
250 -(% 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/]]
251 -
252 -
253 -(% style="color:blue" %)**Use below commands in NDS03A:**
254 -
255 -* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
256 -
257 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/ Set CoAP server address and port
258 -
259 -* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/  Set CoAP resource path
260 -
261 261  For parameter description, please refer to AT command set
262 262  
263 -[[image:image-20221021110948-8.png]]
184 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image008.png]]
264 264  
186 +After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server.
265 265  
266 -After configuring the server address and (% style="color:green" %)**reset NDS03A**(%%) (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]] ​
267 267  
268 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
190 +**2.2.5 Use UDP protocol to uplink data(Default protocol)**
269 269  
192 +This feature is supported since firmware version v1.0.1
270 270  
271 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
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
272 272  
198 +​ [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image010.png]]
273 273  
274 -(% style="color:blue" %)**AT Commands:**
200 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image011.png||alt="说明: 1657249930215-289.png"]]
275 275  
276 -* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
277 -
278 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  Set UDP server address and port
279 -
280 -* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
281 -
282 -​ [[image:image-20221021111025-10.png]]
283 -
284 -
285 -[[image:image-20221021111033-11.png||height="241" width="576"]]
286 -
287 287  ​
288 288  
289 -=== 2.2.6 Use MQTT protocol to uplink data ===
204 +**2.2.6 Use MQTT protocol to uplink data**
290 290  
206 +This feature is supported since firmware version v110
291 291  
292 -(% style="color:blue" %)**AT Commands:**
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
293 293  
294 -* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
216 +​ [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image012.png]]
295 295  
296 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
218 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image013.png]]
297 297  
298 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
299 -
300 -* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/  Set the username of MQTT
301 -
302 -* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/  Set the password of MQTT
303 -
304 -* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)** **~/~/  Set the sending topic of MQTT
305 -
306 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
307 -
308 -​ [[image:image-20221118103445-7.png]]
309 -
310 -
311 -[[image:image-20221118103453-8.png||height="608" width="841"]]
312 -
313 313  ​
314 314  
315 -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.
316 316  
224 +**2.2.7 Use TCP protocol to uplink data**
317 317  
318 -=== 2.2.7 Use TCP protocol to uplink data ===
226 +This feature is supported since firmware version v110
319 319  
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
320 320  
321 -(% style="color:blue" %)**AT Commands:**
231 +​ [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image014.png]]
322 322  
323 -* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
233 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image015.png||alt="说明: 1657250255956-604.png"]]
324 324  
325 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
326 -
327 -​ [[image:image-20221021111125-14.png]]
328 -
329 -[[image:image-20221021111131-15.png]]
330 -
331 331  ​
332 332  
333 -=== 2.2.8 Change Update Interval ===
237 +**2.2.8 Change Update Interval**
334 334  
239 +User can use below command to change the **uplink interval**.
335 335  
336 -User can use below command to change the (% style="color:blue" %)**uplink interval**.
241 +* **AT+TDC=600      ** ~/~/ Set Update Interval to 600s
337 337  
338 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
243 +**NOTE:**
339 339  
340 -(% style="color:red" %)**NOTE:**
245 +**~1. By default, the device will send an uplink message every 1 hour.**
341 341  
342 -1.  By default, the device will send an uplink message every 4 hour.
247 +**2.3  Uplink Payload**
343 343  
249 +In this mode, uplink payload includes 87 bytes in total by default.
344 344  
345 -== 2.3  Uplink Payload ==
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.
346 346  
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
347 347  
348 -The uplink payload includes 26 bytes in total by default.
349 349  
350 -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.
257 +|2|2|4|8 group
258 +|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|Time stamp|...
351 351  
352 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
260 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
353 353  
354 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)
355 -|=(% 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**
356 -|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
262 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image016.png]]
357 357  
358 -(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
359 -|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)(((
360 -**1-32 group**
361 -)))
362 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:115px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)|(% style="width:99px" %)last open time(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
363 -
364 -
365 -
366 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
367 -
368 -
369 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
370 -|=(% 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**
371 -|=(% style="width: 96px;" %)**Value**|(% style="width:66px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:70px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:55px" %)Door Status(pb14)|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb14)|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
372 -
373 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
374 -|(% 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**
375 -|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
376 -
377 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
378 -|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)(((
379 -**1-32 group**
380 -)))
381 -|(% 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>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......
382 -
383 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
384 -
385 -[[image:image-20221117145932-2.png]]
386 -
387 -
388 388  The payload is ASCII string, representative same HEX:
389 389  
390 -**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:
391 391  
392 -**where:**
268 +* **Device ID: 0x f867787050213317 = f867787050213317**
269 +* **Version: 0x0064=100=1.0.0**
393 393  
394 -* (% 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,.......**
395 395  
396 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
283 +**2.4  Payload Explanation and Sensor Interface**
397 397  
398 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
285 +**2.4.1  Device ID**
399 399  
400 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
287 +By default, the Device ID equal to the last 15 bits of IMEI.
401 401  
402 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
289 +User can use **AT+DEUI** to set Device ID
403 403  
404 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
405 -
406 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
407 -
408 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
409 -
410 -* (% style="color:#037691" %)**last open time:  **(%%)0x000017 =23
411 -
412 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
413 -
414 -
415 -
416 -== 2.4  Payload Explanation and Sensor Interface ==
417 -
418 -=== 2.4.1  Device ID ===
419 -
420 -
421 -By default, the Device ID is equal to the last 15 bits of IMEI.
422 -
423 -User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
424 -
425 425  **Example:**
426 426  
427 427  AT+DEUI=868411056754138
428 428  
429 -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.
430 430  
297 +**2.4.2  Version Info**
431 431  
432 -=== 2.4.2  Version Info ===
299 +Specify the software version: 0x64=100, means firmware version 1.00.
433 433  
301 +For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0.
434 434  
435 -Specify the software version: 0x64=100, which means firmware version 1.00.
303 +**2.4.3  Battery Info**
436 436  
437 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
305 +Check the battery voltage for CPN01.
438 438  
439 -
440 -=== 2.4.3  Battery Info ===
441 -
442 -
443 -Check the battery voltage for NDS03A.
444 -
445 445  Ex1: 0x0B45 = 2885mV
446 446  
447 447  Ex2: 0x0B49 = 2889mV
448 448  
311 +**2.4.4  Signal Strength**
449 449  
450 -=== 2.4.4  Signal Strength ===
451 -
452 -
453 453  NB-IoT Network signal Strength.
454 454  
455 455  **Ex1: 0x1d = 29**
... ... @@ -464,46 +464,58 @@
464 464  
465 465  **99**    Not known or not detectable
466 466  
327 +**2.4.5 Calculate Flag**
467 467  
468 -=== 2.4.5  Disalarm: (default: 0) ===
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.
469 469  
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.
470 470  
471 -(% 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.
333 +Default value: 0. 
472 472  
473 -(% 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.
335 +Range (6 bits): (b)000000 ~~ (b) 111111
474 474  
475 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
337 +**2.4.6  Alarm**
476 476  
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]]
477 477  
478 -=== 2.4.6  Keep Status & Keep Time ===
341 +**2.4.7 Contact Status**
479 479  
343 +0: Open
480 480  
481 -Shows the configure value of Alarm Base on Timeout Feature
345 +1: Close
482 482  
347 +**2.4.8 Total pulse**
483 483  
484 -=== 2.4.7  Timestamp ===
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]]
485 485  
351 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
486 486  
487 -Timestamp : 0x6315537b =1662342011
353 +**2.4.9 The last open duration**
488 488  
355 +Dry Contact last open duration.
489 489  
490 -=== 2.4.8  Switch Dual Channel Mode ===
357 +Unit: min.
491 491  
359 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image017.png]]
492 492  
493 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
494 494  
362 +**2.4.10  Timestamp**
495 495  
496 -== 2.5  Downlink Payload ==
364 +Time stamp : 0x6315537b =1662342011
497 497  
366 +Convert Unix timestamp to time 2022-9-5 9:40:11.
498 498  
499 -By default, NDS03A prints the downlink payload to console port.
368 +**~ **
500 500  
501 -[[image:image-20221021111414-18.png]] ​
370 +**2.5  Downlink Payload**
502 502  
372 +By default, CPN01 prints the downlink payload to console port.
503 503  
374 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image018.png||alt="说明: image-20220708133731-5.png"]] ​
375 +
504 504  **Examples:**
505 505  
506 -* (% style="color:#037691" %)**Set TDC**
378 +* **Set TDC**
507 507  
508 508  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
509 509  
... ... @@ -511,222 +511,178 @@
511 511  
512 512  Payload:    01 00 00 3C    TDC=60S
513 513  
514 -* (% style="color:#037691" %)**Reset**
386 +* **Reset**
515 515  
516 -If payload = 0x04FF, it will reset the NDS03A
388 +If payload = 0x04FF, it will reset the NSE01
517 517  
518 -* (% style="color:#037691" %)**INTMOD**
390 +* **INTMOD**
519 519  
520 520  Downlink Payload: 06000003, Set AT+INTMOD=3
521 521  
394 +**2.6  ​LED Indicator**
522 522  
523 -== 2.6  ​LED Indicator ==
396 +The CPN01 has an internal LED which is to show the status of different state.
524 524  
525 -
526 -The NDS03A has an internal LED which is to show the status of different states.
527 -
528 -* When the device starts normally, the LED will light up for 1 second.
529 -* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
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.
400 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
530 530  * For each uplink probe, LED will be on for 500ms.
531 531  
403 +**2.7 ** Alarm Base on Timeout
532 532  
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:
533 533  
534 -== 2.7  Alarm Base on Timeout ==
535 535  
408 +**~1. Keep Status: Status to be monitor**
536 536  
537 -NDS03A can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are:
538 -
539 -
540 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
541 -
542 542  Keep Status = 1: Monitor Close to Open event
543 543  
544 544  Keep Status = 0: Monitor Open to Close event
545 545  
546 546  
547 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
415 +**2. Keep Time: Timeout to send an Alarm**
548 548  
549 549  Range 0 ~~ 65535(0xFFFF) seconds.
550 550  
551 551  If keep time = 0, Disable Alarm Base on Timeout feature.
552 552  
553 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
421 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
554 554  
555 555  
556 -(% style="color:blue" %)**AT Command to configure:**
424 +**AT Command** to configure:
557 557  
558 -(% style="color:blue" %)**PB14 PIN:**
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.
559 559  
560 -(% style="color:#037691" %)**AT+TTRIG=1,30** (%%) **~-~->**  When the **Keep Status** change from connected to disconnect, and device remains in disconnect status for more than 30 seconds. NDS03A will send an uplink packet, the [[Alarm bit>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.
428 +**AT+TTIG=0,0 ** ~-~-> Default Value, disable timeout Alarm.
561 561  
562 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
430 +**2.8** Set debug mode
563 563  
564 -
565 -(% style="color:blue" %)**PB15 PIN:**
566 -
567 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
568 -
569 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
570 -
571 -
572 -== 2.8  Set debug mode ==
573 -
574 -
575 575  Feature: Enable or Disable debug mode
576 576  
577 -(% style="color:blue" %)**AT Command: AT+DEBUG**
578 578  
579 -[[image:image-20221021111629-21.png]]
435 +**AT Command: AT+DEBUG**
580 580  
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
581 581  
441 +== 2.9 Clear Flash Record ==
582 582  
583 -== 2.9  Clear Flash Record ==
584 -
585 -
586 586  Feature: Clear flash storage for data log feature.
587 587  
588 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
445 +**AT Command: AT+CLRDTA**
589 589  
590 -[[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"]]
591 591  
449 +**~ 2.10 **Set trigger mode
592 592  
593 -== 2.10  Count Mod ==
451 +➢ AT Command: **AT+TTRMOD**
594 594  
453 +Feature: Set the trigger interrupt mode.
595 595  
596 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
455 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image020.png||alt="说明: image-20220609151344-9.png"]]
597 597  
598 -[[image:image-20221118092935-1.png]]
457 +**2.11** Set the calculate flag
599 599  
459 +Feature: Set the calculate flag
600 600  
601 -== 2.11  Interrupt Pin Channel Mod ==
461 +**AT Command: AT+CALCFLAG**
602 602  
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
603 603  
604 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
467 +**2.12** Set count number
605 605  
606 -[[image:image-20221118093144-2.png]]
469 +Feature: Manually set the count number
607 607  
471 +**AT Command: AT+SETCNT**
608 608  
609 -== 2.12 TTRIG1/2 timeout status alarm ==
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
610 610  
611 611  
612 -It needs to be used with AT+TTRIG1 or AT+TTRIG2. When TTRIG1 or TTRIG2 times out and causes an alarm, and the status does not change subsequently, an alarm packet will be sent at the alarm interval.
478 +**2.13 Set the number of data to be uploaded and the recording time**
613 613  
614 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
480 +➢ AT Command:
615 615  
616 -[[image:image-20221118093512-3.png]]
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)
617 617  
618 618  
619 -== 2.13  Select counting mode ==
485 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
620 620  
487 +**2.14 Read or Clear cached data**
621 621  
622 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
489 +➢ AT Command:
623 623  
624 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
491 +AT+CDP    ~/~/ Read cached data
625 625  
626 -When (% style="color:red" %)**b=0**(%%), it is the last door open duration, and when (% style="color:red" %)**b=1**(%%),the last door close duration.
493 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image021.png]]
627 627  
628 -[[image:image-20221118093658-4.png]]
629 629  
496 +AT+CDP=0    ~/~/ Clear cached data ​
630 630  
631 -== 2.14  Set the number of data to be uploaded and the recording time ==
498 +**2.15  ​Firmware Change Log**
632 632  
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]]
633 633  
634 -(% style="color:blue" %)**AT Command:**
502 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
635 635  
636 -(% 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)
504 +**2.16  ​Battery Analysis**
637 637  
638 -(% style="color:#037691" %)**AT+NOUD=8**(%%)** ** ~/~/  The device uploads 0 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
506 +**2.16.1  ​Battery Type**
639 639  
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.
640 640  
641 -== 2.15  Read or Clear cached data ==
510 +The battery is designed to last for several years depends on the actually use environment and update interval. 
642 642  
512 +The battery related documents as below:
643 643  
644 -(% style="color:blue" %)**AT Command:**
645 -
646 -(% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
647 -
648 -(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
649 -
650 -[[image:image-20221118094227-5.png]]
651 -
652 -
653 -== 2.16  ​Firmware Change Log ==
654 -
655 -
656 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
657 -
658 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
659 -
660 -
661 -== 2.17  ​Battery Analysis ==
662 -
663 -=== 2.17.1  ​Battery Type ===
664 -
665 -
666 -The NDS03A battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
667 -
668 -The battery is designed to last for several years depends on the actual use environment and update interval. 
669 -
670 -The battery-related documents as below:
671 -
672 672  * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
673 -
674 674  * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
675 -
676 676  * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
677 677  
678 -[[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"]] ​
679 679  
520 +**2.16.2  Power consumption Analyze**
680 680  
681 -=== 2.17.2  Power consumption Analyze ===
682 -
683 -
684 684  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.
685 685  
686 686  Instruction to use as below:
687 687  
688 -(% 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/]]
689 689  
690 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
528 +**Step 2: ** Open it and choose
691 691  
692 692  * Product Model
693 -
694 694  * Uplink Interval
695 -
696 696  * Working Mode
697 697  
698 698  And the Life expectation in difference case will be shown on the right.
699 699  
700 -[[image:1666596205057-567.png]] ​
536 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image023.jpg||alt="说明: image-20220708141352-7.jpeg"]] ​
701 701  
538 +**2.16.3  ​Battery Note**
702 702  
703 -=== 2.17.3  ​Battery Note ===
704 -
705 -
706 706  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.
707 707  
542 +**2.16.4  Replace the battery**
708 708  
709 -=== 2.17.4  Replace the battery ===
544 +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).
710 710  
546 +**3. ​ Access NB-IoT Module**
711 711  
712 -The default battery pack of NDS03A includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
713 -
714 -
715 -= 3. ​ Access NB-IoT Module =
716 -
717 -
718 718  Users can directly access the AT command set of the NB-IoT module.
719 719  
720 720  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/]] 
721 721  
722 -[[image:image-20221118094449-6.png]] ​
552 +[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image024.png||alt="说明: 1657261278785-153.png"]] ​
723 723  
554 +**4.  Using the AT Commands**
724 724  
725 -= 4.  Using the AT Commands =
556 +**4.1  Access AT Commands**
726 726  
727 -== 4.1  Access AT Commands ==
728 -
729 -
730 730  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]]
731 731  
732 732  AT+<CMD>?  : Help on <CMD>
... ... @@ -737,9 +737,8 @@
737 737  
738 738  AT+<CMD>=?  : Get the value
739 739  
568 +**General Commands**      
740 740  
741 -(% style="color:blue" %)**General Commands**      
742 -
743 743  AT  : Attention       
744 744  
745 745  AT?  : Short Help     
... ... @@ -762,41 +762,35 @@
762 762  
763 763  AT+SERVADDR  : Server Address
764 764  
765 -AT+TR      :  Get or Set record time
592 +AT+TR      : Get or Set record time"
766 766  
594 +
767 767  AT+NOUD      : Get or Set the number of data to be uploaded
768 768  
769 -AT+CDP     :  Read or Clear cached data
770 770  
771 -AT+ DEBUG   : Enable or Disable debug mode
598 +AT+CDP     : Read or Clear cached data
772 772  
773 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
774 774  
775 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
601 +AT+ DEBUG   : Enable or Disable debug mode
776 776  
777 -AT+COUNTMOD  :  Get or Set the count mode
603 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
778 778  
779 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
605 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
780 780  
781 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
607 +AT+ CALCFLAG   : Get or Set the calculate flag
782 782  
783 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
609 +AT+ CLRC   : Clear current door open count
784 784  
785 -AT+ CLRC   :  Clear current door open count
611 +**COAP Management**      
786 786  
787 -
788 -(% style="color:blue" %)**COAP Management**      
789 -
790 790  AT+URI            : Resource parameters
791 791  
615 +**UDP Management**
792 792  
793 -(% style="color:blue" %)**UDP Management**
794 -
795 795  AT+CFM          : Upload confirmation mode (only valid for UDP)
796 796  
619 +**MQTT Management**
797 797  
798 -(% style="color:blue" %)**MQTT Management**
799 -
800 800  AT+CLIENT               : Get or Set MQTT client
801 801  
802 802  AT+UNAME  : Get or Set MQTT Username
... ... @@ -807,60 +807,86 @@
807 807  
808 808  AT+SUBTOPIC  : Get or Set MQTT subscription topic
809 809  
631 +**Information**          
810 810  
811 -(% style="color:blue" %)**Information**          
812 -
813 813  AT+FDR  : Factory Data Reset
814 814  
815 815  AT+PWORD  : Serial Access Password
816 816  
637 +**​5.  FAQ**
817 817  
818 -= ​5.  FAQ =
639 +**5.1 ​ How to Upgrade Firmware**
819 819  
820 -== 5.1 ​ How to Upgrade Firmware ==
821 -
822 -
823 823  User can upgrade the firmware for 1) bug fix, 2) new feature release.
824 824  
825 825  Please see this link for how to upgrade:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
826 826  
827 -(% style="color:red" %)**Notice: **(% style="color:blue" %)**NDS03A** (%%)**and (% style="color:blue" %)LDS03A(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
645 +**Notice, **CPN01 **and **CPN01 **share the same mother board. They use the same connection and method to update.**
828 828  
647 +**5.2  Can I calibrate CPN01 to different soil types?**
829 829  
830 -= 6.  Trouble Shooting =
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]].
831 831  
832 -== 6.1  ​Connection problem when uploading firmware ==
651 +**6.  Trouble Shooting**
833 833  
653 +**6.1  ​Connection problem when uploading firmware**
834 834  
835 -(% 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]]
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]]
836 836  
657 +**6.2  AT Command input doesn't work**
837 837  
838 -== 6.2  AT Command input doesn't work ==
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.
839 839  
661 +**7. ​ Order Info**
840 840  
841 -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.
663 +Part Number**:** CPN01
842 842  
665 +**8.  Packing Info**
843 843  
844 -= 7. ​ Order Info =
667 +**Package Includes**:
845 845  
669 +* CPN01 NB-IoT Soil Moisture & EC Sensor x 1
670 +* External antenna x 1
846 846  
847 -Part Number**:** NDS03A
672 +**Dimension and weight**:
848 848  
674 +* Size: 195 x 125 x 55 mm
675 +* Weight:   420g
849 849  
850 -= 8.  Packing Info =
677 +**9.  Support**
851 851  
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]]
852 852  
853 -(% style="color:blue" %)**Package Includes**:
682 +​
854 854  
855 -* NDS03A Open/Close Door Sensor x 1
856 856  
857 857  
858 858  
859 -= 9.  Support =
860 860  
861 861  
862 -* 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.
863 863  
864 -* 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]]
865 865  
866 -​
691 +
692 +
693 +
694 +
695 +
696 +
697 +
698 +
699 +
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
image-20221118092935-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -13.1 KB
Content
image-20221118093144-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.7 KB
Content
image-20221118093512-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -9.5 KB
Content
image-20221118093658-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -12.7 KB
Content
image-20221118094227-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.2 KB
Content
image-20221118094449-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.5 KB
Content
image-20221118103445-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -20.4 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.5 KB
Content

Applications

Navigation

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