Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 74.3 >
edited by Xiaoling
on 2022/12/07 17:16
To version < 39.1 >
edited by Edwin Chen
on 2022/10/23 00:04
>
Change comment: Uploaded new attachment "image-20221023000439-3.png", version {1}

Summary

Details

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

Applications

Navigation

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