Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 79.1 >
edited by Xiaoling
on 2022/12/07 17:40
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,236 +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 NMDS200 ==
128 +=== **2.2.1 Test Requirement** ===
144 144  
130 +To use CPN01 in your city, make sure meet below requirements:
145 145  
146 -To use NMDS200 in your city, make sure to meet below requirements:
147 -
148 -* Your local operator has already distributed an NB-IoT Network.
149 -* The local NB-IoT network used the band that NMDS200 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.
150 150  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
151 151  
152 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NMDS200 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
153 153  
154 -[[image:image-20221207173300-4.png]]
138 + ​
155 155  
140 +=== **2.2.2 Insert SIM card** ===
156 156  
157 -=== 2.2.1 Insert NB-IoT SIM card ===
158 -
159 -
160 160  Insert the NB-IoT Card get from your provider.
161 161  
162 -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:
163 163  
164 164  [[image:image-20221021110745-6.png]] ​
165 165  
148 +=== **2.2.3 Connect USB – TTL to CPN01 to configure it** ===
166 166  
167 -=== 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.
168 168  
152 +**Connection:**
169 169  
170 -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
171 171  
172 -(% style="color:blue" %)**Connection:**
156 + USB TTL TXD <~-~-~-~-> UART_RXD
173 173  
174 -(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
158 + USB TTL RXD <~-~-~-~-> UART_TXD
175 175  
176 -(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD**
177 -
178 -(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD**
179 -
180 -
181 181  In the PC, use below serial tool settings:
182 182  
183 -* Baud:  (% style="color:red" %)**9600**
162 +* Baud:  **9600**
163 +* Data bits:** 8**
164 +* Stop bits: **1**
165 +* Parity:  **None**
166 +* Flow Control: **None**
184 184  
185 -* 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.
186 186  
187 -* Stop bits: (% style="color:red" %)**1**
188 -
189 -* Parity:  (% style="color:red" %)**None**
190 -
191 -* Flow Control: (% style="color:red" %)**None**
192 -
193 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
194 -
195 195  ​[[image:image-20221021110817-7.png]]
196 196  
197 -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]]
198 198  
174 +=== **2.2.4 Use CoAP protocol to uplink data** ===
199 199  
200 -(% 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/]]
201 201  
178 +**Use below commands:**
202 202  
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
203 203  
204 -=== 2.2.4 Use CoAP protocol to uplink data ===
205 -
206 -
207 -(% 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/]]
208 -
209 -
210 -(% style="color:blue" %)**Use below commands in NDS03A:**
211 -
212 -* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
213 -
214 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/ Set CoAP server address and port
215 -
216 -* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/  Set CoAP resource path
217 -
218 218  For parameter description, please refer to AT command set
219 219  
220 220  [[image:image-20221021110948-8.png]]
221 221  
188 +After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server.
222 222  
223 -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]] ​
224 224  
225 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
192 +=== **2.2.5 Use UDP protocol to uplink data(Default protocol)** ===
226 226  
194 +This feature is supported since firmware version v1.0.1
227 227  
228 -=== 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
229 229  
230 -
231 -(% style="color:blue" %)**AT Commands:**
232 -
233 -* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
234 -
235 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  Set UDP server address and port
236 -
237 -* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
238 -
239 239  ​ [[image:image-20221021111025-10.png]]
240 240  
241 -
242 242  [[image:image-20221021111033-11.png||height="241" width="576"]]
243 243  
244 244  ​
245 245  
246 -=== 2.2.6 Use MQTT protocol to uplink data ===
206 +=== **2.2.6 Use MQTT protocol to uplink data** ===
247 247  
208 +This feature is supported since firmware version v110
248 248  
249 -(% 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
250 250  
251 -* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
218 +​ [[image:image-20221021111058-12.png]]
252 252  
253 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
220 +[[image:image-20221021111108-13.png]]
254 254  
255 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
256 -
257 -* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/  Set the username of MQTT
258 -
259 -* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/  Set the password of MQTT
260 -
261 -* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)** **~/~/  Set the sending topic of MQTT
262 -
263 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
264 -
265 -​ [[image:image-20221118103445-7.png]]
266 -
267 -
268 -[[image:image-20221118103453-8.png||height="608" width="841"]]
269 -
270 270  ​
271 271  
272 -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.
273 273  
226 +=== **2.2.7 Use TCP protocol to uplink data** ===
274 274  
275 -=== 2.2.7 Use TCP protocol to uplink data ===
228 +This feature is supported since firmware version v110
276 276  
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
277 277  
278 -(% style="color:blue" %)**AT Commands:**
279 -
280 -* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
281 -
282 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
283 -
284 284  ​ [[image:image-20221021111125-14.png]]
285 285  
286 286  [[image:image-20221021111131-15.png]]
... ... @@ -287,122 +287,93 @@
287 287  
288 288  ​
289 289  
290 -=== 2.2.8 Change Update Interval ===
239 +=== **2.2.8 Change Update Interval** ===
291 291  
241 +User can use below command to change the **uplink interval**.
292 292  
293 -User can use below command to change the (% style="color:blue" %)**uplink interval**.
243 +* **AT+TDC=600      ** ~/~/ Set Update Interval to 600s
294 294  
295 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
245 +**NOTE:**
296 296  
297 -(% style="color:red" %)**NOTE:**
247 +**~1. By default, the device will send an uplink message every 1 hour.**
298 298  
299 -1.  By default, the device will send an uplink message every 4 hour.
249 +== **2.3  Uplink Payload** ==
300 300  
251 +In this mode, uplink payload includes 87 bytes in total by default.
301 301  
302 -== 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.
303 303  
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
304 304  
305 -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|...
306 306  
307 -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.
308 308  
309 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
263 +[[image:image-20221021111201-16.png||height="572" width="792"]]
310 310  
311 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
312 -|=(% 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**
313 -|=(% 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)
314 -
315 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
316 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
317 -**1-32 group**
318 -)))
319 -|(% 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" %)...
320 -
321 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
322 -
323 -
324 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
325 -|=(% 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**
326 -|=(% 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)
327 -
328 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
329 -|(% 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**
330 -|(% 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)
331 -
332 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
333 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
334 -**1-32 group**
335 -)))
336 -|(% 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" %)......
337 -
338 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
339 -
340 -[[image:image-20221117145932-2.png]]
341 -
342 -
343 343  The payload is ASCII string, representative same HEX:
344 344  
345 -**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 //(%%)**
346 346  
347 -**where:**
269 +where:
270 +*(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317
348 348  
349 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
272 +*(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0
350 350  
351 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
274 +*(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
352 352  
353 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
276 +*(% style="color:#037691" %) **Singal: **(%%)0x17 = 23
354 354  
355 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
278 +*(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
356 356  
357 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
280 +*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00= 0
358 358  
359 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
282 +*(% style="color:#037691" %) **Contact Status:**(%%) 0x00= 0
360 360  
361 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
284 +*(% style="color:#037691" %) **Alarm:**(%%)0x00 =0
362 362  
363 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
286 +*(% style="color:#037691" %) **Total pulse:0x09 =0**
364 364  
365 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
288 +*(% style="color:#037691" %) **The last open duration:**(%%)0x02 =2
366 366  
367 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
290 +*(% style="color:#037691" %)**Time stamp :**(%%) 0x6315537b =1662342011
368 368  
369 -== 2.4  Payload Explanation and Sensor Interface ==
292 +*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000b0200002663510fed
370 370  
371 -=== 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,.......
372 372  
296 +== **2.4  Payload Explanation and Sensor Interface** ==
373 373  
374 -By default, the Device ID is equal to the last 15 bits of IMEI.
298 +=== **2.4.1  Device ID** ===
375 375  
376 -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.
377 377  
302 +User can use **AT+DEUI** to set Device ID
303 +
378 378  **Example:**
379 379  
380 380  AT+DEUI=868411056754138
381 381  
382 -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.
383 383  
310 +=== **2.4.2  Version Info** ===
384 384  
385 -=== 2.4.2  Version Info ===
312 +Specify the software version: 0x64=100, means firmware version 1.00.
386 386  
314 +For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0.
387 387  
388 -Specify the software version: 0x64=100, which means firmware version 1.00.
316 +=== **2.4.3  Battery Info** ===
389 389  
390 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
318 +Check the battery voltage for CPN01.
391 391  
392 -
393 -=== 2.4.3  Battery Info ===
394 -
395 -
396 -Check the battery voltage for NDS03A.
397 -
398 398  Ex1: 0x0B45 = 2885mV
399 399  
400 400  Ex2: 0x0B49 = 2889mV
401 401  
324 +=== **2.4.4  Signal Strength** ===
402 402  
403 -=== 2.4.4  Signal Strength ===
404 -
405 -
406 406  NB-IoT Network signal Strength.
407 407  
408 408  **Ex1: 0x1d = 29**
... ... @@ -417,46 +417,58 @@
417 417  
418 418  **99**    Not known or not detectable
419 419  
340 +=== **2.4.5 Calculate Flag** ===
420 420  
421 -=== 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.
422 422  
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.
423 423  
424 -(% 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. 
425 425  
426 -(% 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
427 427  
428 - (% 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** ===
429 429  
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]]
430 430  
431 -=== 2.4.6  Keep Status & Keep Time ===
354 +=== **2.4.7 Contact Status** ===
432 432  
356 +0: Open
433 433  
434 -Shows the configure value of Alarm Base on Timeout Feature
358 +1: Close
435 435  
360 +=== **2.4.8 Total pulse** ===
436 436  
437 -=== 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]]
438 438  
364 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
439 439  
440 -Timestamp : 0x6315537b =1662342011
366 +=== **2.4.9 The last open duration** ===
441 441  
368 +Dry Contact last open duration.
442 442  
443 -=== 2.4.8  Switch Dual Channel Mode ===
370 +Unit: min.
444 444  
372 +[[image:image-20221021111346-17.png||height="146" width="770"]]
445 445  
446 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
447 447  
375 +=== **2.4.10  Timestamp** ===
448 448  
449 -== 2.5  Downlink Payload ==
377 +Time stamp : 0x6315537b =1662342011
450 450  
379 +Convert Unix timestamp to time 2022-9-5 9:40:11.
451 451  
452 -By default, NDS03A prints the downlink payload to console port.
381 +**~ **
453 453  
454 -[[image:image-20221021111414-18.png]] ​
383 +== **2.5  Downlink Payload** ==
455 455  
385 +By default, CPN01 prints the downlink payload to console port.
456 456  
387 +[[image:image-20221021111414-18.png]] ​
388 +
457 457  **Examples:**
458 458  
459 -* (% style="color:#037691" %)**Set TDC**
391 +* **Set TDC**
460 460  
461 461  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
462 462  
... ... @@ -464,221 +464,171 @@
464 464  
465 465  Payload:    01 00 00 3C    TDC=60S
466 466  
467 -* (% style="color:#037691" %)**Reset**
399 +* **Reset**
468 468  
469 -If payload = 0x04FF, it will reset the NDS03A
401 +If payload = 0x04FF, it will reset the NSE01
470 470  
471 -* (% style="color:#037691" %)**INTMOD**
403 +* **INTMOD**
472 472  
473 473  Downlink Payload: 06000003, Set AT+INTMOD=3
474 474  
407 +== **2.6  ​LED Indicator** ==
475 475  
476 -== 2.6  ​LED Indicator ==
409 +The CPN01 has an internal LED which is to show the status of different state.
477 477  
478 -
479 -The NDS03A has an internal LED which is to show the status of different states.
480 -
481 -* When the device starts normally, the LED will light up for 1 second.
482 -* 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.
483 483  * For each uplink probe, LED will be on for 500ms.
484 484  
485 -== 2.7  Alarm Base on Timeout ==
416 +== **2.7  Alarm Base on Timeout** ==
486 486  
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:
487 487  
488 -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:
489 489  
421 +**~1. Keep Status: Status to be monitor**
490 490  
491 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
492 -
493 493  Keep Status = 1: Monitor Close to Open event
494 494  
495 495  Keep Status = 0: Monitor Open to Close event
496 496  
497 497  
498 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
428 +**2. Keep Time: Timeout to send an Alarm**
499 499  
500 500  Range 0 ~~ 65535(0xFFFF) seconds.
501 501  
502 502  If keep time = 0, Disable Alarm Base on Timeout feature.
503 503  
504 -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.
505 505  
506 506  
507 -(% style="color:blue" %)**AT Command to configure:**
437 +**AT Command** to configure:
508 508  
509 -(% 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.
510 510  
511 -(% 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.
512 512  
513 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
443 +== **2.8 Set debug mode** ==
514 514  
515 -
516 -(% style="color:blue" %)**PB15 PIN:**
517 -
518 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
519 -
520 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
521 -
522 -
523 -== 2.8  Set debug mode ==
524 -
525 -
526 526  Feature: Enable or Disable debug mode
527 527  
528 -(% style="color:blue" %)**AT Command: AT+DEBUG**
529 529  
448 +**AT Command: AT+DEBUG**
449 +
530 530  [[image:image-20221021111629-21.png]]
531 531  
452 +== **2.9 Clear Flash Record** ==
532 532  
533 -
534 -== 2.9  Clear Flash Record ==
535 -
536 -
537 537  Feature: Clear flash storage for data log feature.
538 538  
539 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
456 +**AT Command: AT+CLRDTA**
540 540  
541 541  [[image:image-20221021111527-19.png]]
542 542  
460 +== ** 2.10 Set trigger mode** ==
543 543  
544 -== 2.10  Count Mod ==
462 +➢ AT Command: **AT+TTRMOD**
545 545  
464 +Feature: Set the trigger interrupt mode.
546 546  
547 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
466 +[[image:image-20221021111552-20.png]]
548 548  
549 -[[image:image-20221118092935-1.png]]
468 +== **2.11 Set the calculate flag** ==
550 550  
470 +Feature: Set the calculate flag
551 551  
552 -== 2.11  Interrupt Pin Channel Mod ==
472 +**AT Command: AT+CALCFLAG**
553 553  
474 +[[image:image-20221021111711-22.png]]
554 554  
555 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
476 +== **2.12 Set count number** ==
556 556  
557 -[[image:image-20221118093144-2.png]]
478 +Feature: Manually set the count number
558 558  
480 +**AT Command: AT+SETCNT**
559 559  
560 -== 2.12 TTRIG1/2 timeout status alarm ==
482 +[[image:image-20221021111748-24.png]]
561 561  
484 +== **2.13 Set the number of data to be uploaded and the recording time** ==
562 562  
563 -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:
564 564  
565 -(% 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)
566 566  
567 -[[image:image-20221118093512-3.png]]
568 568  
491 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
569 569  
570 -== 2.13  Select counting mode ==
493 +== **2.14 Read or Clear cached data** ==
571 571  
495 +➢ AT Command:
572 572  
573 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
497 +AT+CDP    ~/~/ Read cached data
574 574  
575 -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"]]
576 576  
577 -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.
578 578  
579 -[[image:image-20221118093658-4.png]]
502 +AT+CDP=0    ~/~/ Clear cached data ​
580 580  
504 +== **2.15  ​Firmware Change Log** ==
581 581  
582 -== 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]]
583 583  
508 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
584 584  
585 -(% style="color:blue" %)**AT Command:**
510 +== **2.16  ​Battery Analysis** ==
586 586  
587 -(% 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** ===
588 588  
589 -(% 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.
590 590  
516 +The battery is designed to last for several years depends on the actually use environment and update interval. 
591 591  
592 -== 2.15  Read or Clear cached data ==
518 +The battery related documents as below:
593 593  
594 -
595 -(% style="color:blue" %)**AT Command:**
596 -
597 -(% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
598 -
599 -(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
600 -
601 -[[image:image-20221118094227-5.png]]
602 -
603 -
604 -== 2.16  ​Firmware Change Log ==
605 -
606 -
607 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
608 -
609 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
610 -
611 -
612 -== 2.17  ​Battery Analysis ==
613 -
614 -=== 2.17.1  ​Battery Type ===
615 -
616 -
617 -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.
618 -
619 -The battery is designed to last for several years depends on the actual use environment and update interval. 
620 -
621 -The battery-related documents as below:
622 -
623 623  * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
624 -
625 625  * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
626 -
627 627  * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
628 628  
629 629  [[image:image-20221021111911-26.png]] ​
630 630  
526 +=== **2.16.2  Power consumption Analyze** ===
631 631  
632 -=== 2.17.2  Power consumption Analyze ===
633 -
634 -
635 635  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.
636 636  
637 637  Instruction to use as below:
638 638  
639 -(% 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/]]
640 640  
641 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
534 +**Step 2: ** Open it and choose
642 642  
643 643  * Product Model
644 -
645 645  * Uplink Interval
646 -
647 647  * Working Mode
648 648  
649 649  And the Life expectation in difference case will be shown on the right.
650 650  
651 -[[image:1666596205057-567.png]] ​
542 +[[image:image-20221021111923-27.png||height="253" width="783"]] ​
652 652  
544 +=== **2.16.3  ​Battery Note** ===
653 653  
654 -=== 2.17.3  ​Battery Note ===
655 -
656 -
657 657  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.
658 658  
548 +=== **2.16.4  Replace the battery** ===
659 659  
660 -=== 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).
661 661  
552 += **3. ​ Access NB-IoT Module** =
662 662  
663 -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).
664 -
665 -
666 -= 3. ​ Access NB-IoT Module =
667 -
668 -
669 669  Users can directly access the AT command set of the NB-IoT module.
670 670  
671 671  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/]] 
672 672  
558 +[[image:image-20221021112006-28.png]] ​
673 673  
674 -[[image:image-20221118094449-6.png]] ​
560 += **4.  Using the AT Commands** =
675 675  
562 +== **4.1  Access AT Commands** ==
676 676  
677 -= 4.  Using the AT Commands =
678 -
679 -== 4.1  Access AT Commands ==
680 -
681 -
682 682  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]]
683 683  
684 684  AT+<CMD>?  : Help on <CMD>
... ... @@ -689,9 +689,8 @@
689 689  
690 690  AT+<CMD>=?  : Get the value
691 691  
574 +**General Commands**      
692 692  
693 -(% style="color:blue" %)**General Commands**      
694 -
695 695  AT  : Attention       
696 696  
697 697  AT?  : Short Help     
... ... @@ -714,41 +714,35 @@
714 714  
715 715  AT+SERVADDR  : Server Address
716 716  
717 -AT+TR      :  Get or Set record time
598 +AT+TR      : Get or Set record time"
718 718  
600 +
719 719  AT+NOUD      : Get or Set the number of data to be uploaded
720 720  
721 -AT+CDP     :  Read or Clear cached data
722 722  
723 -AT+ DEBUG   : Enable or Disable debug mode
604 +AT+CDP     : Read or Clear cached data
724 724  
725 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
726 726  
727 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
607 +AT+ DEBUG   : Enable or Disable debug mode
728 728  
729 -AT+COUNTMOD  :  Get or Set the count mode
609 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
730 730  
731 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
611 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
732 732  
733 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
613 +AT+ CALCFLAG   : Get or Set the calculate flag
734 734  
735 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
615 +AT+ CLRC   : Clear current door open count
736 736  
737 -AT+ CLRC   :  Clear current door open count
617 +**COAP Management**      
738 738  
739 -
740 -(% style="color:blue" %)**COAP Management**      
741 -
742 742  AT+URI            : Resource parameters
743 743  
621 +**UDP Management**
744 744  
745 -(% style="color:blue" %)**UDP Management**
746 -
747 747  AT+CFM          : Upload confirmation mode (only valid for UDP)
748 748  
625 +**MQTT Management**
749 749  
750 -(% style="color:blue" %)**MQTT Management**
751 -
752 752  AT+CLIENT               : Get or Set MQTT client
753 753  
754 754  AT+UNAME  : Get or Set MQTT Username
... ... @@ -759,58 +759,86 @@
759 759  
760 760  AT+SUBTOPIC  : Get or Set MQTT subscription topic
761 761  
637 +**Information**          
762 762  
763 -(% style="color:blue" %)**Information**          
764 -
765 765  AT+FDR  : Factory Data Reset
766 766  
767 767  AT+PWORD  : Serial Access Password
768 768  
643 += **​5.  FAQ** =
769 769  
770 -= ​5.  FAQ =
645 +== **5.1 ​ How to Upgrade Firmware** ==
771 771  
772 -== 5.1 ​ How to Upgrade Firmware ==
773 -
774 -
775 775  User can upgrade the firmware for 1) bug fix, 2) new feature release.
776 776  
777 777  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]]
778 778  
779 -(% 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.**
780 780  
653 +== **5.2  Can I calibrate CPN01 to different soil types?** ==
781 781  
782 -= 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]].
783 783  
784 -== 6.1  ​Connection problem when uploading firmware ==
657 += **6.  Trouble Shooting** =
785 785  
659 +== **6.1  ​Connection problem when uploading firmware** ==
786 786  
787 -(% 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]]
788 788  
663 +== **6.2  AT Command input doesn't work** ==
789 789  
790 -== 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.
791 791  
667 += **7. ​ Order Info** =
792 792  
793 -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
794 794  
671 += **8.  Packing Info** =
795 795  
796 -= 7. ​ Order Info =
673 +**Package Includes**:
797 797  
675 +* CPN01 NB-IoT Soil Moisture & EC Sensor x 1
676 +* External antenna x 1
798 798  
799 -Part Number**:** NDS03A
678 +**Dimension and weight**:
800 800  
680 +* Size: 195 x 125 x 55 mm
681 +* Weight:   420g
801 801  
802 -= 8.  Packing Info =
683 += **9.  Support** =
803 803  
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]]
804 804  
805 -(% style="color:blue" %)**Package Includes**:
688 +​
806 806  
807 -* NDS03A Open/Close Door Sensor x 1
808 808  
809 -= 9.  Support =
810 810  
811 811  
812 -* 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.
813 813  
814 -* 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]]
815 815  
816 -​
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
1670405841875-916.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.1 KB
Content
1670405928926-116.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.7 KB
Content
1670406036256-101.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.0 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
image-20221207173200-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.7 KB
Content
image-20221207173300-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.0 KB
Content

Applications

Navigation

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