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

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,332 +51,290 @@
51 51  * Micro SIM card slot for NB-IoT SIM
52 52  * 8500mAh Battery for long-term use
53 53  
54 -== 1.3 Radar probe specification ==
42 +== **1.3  Specification** ==
55 55  
44 +**Common DC Characteristics:**
56 56  
57 -* Measuring Method: FMCW
58 -* Frequency: 24.000 24.500 GHz
59 -* Measurement output power: 6dBm
60 -* Measure range: 0.5 20m
61 -* Accuracy: ±0.1m
62 -* Resolution: 0.01m
63 -* Horizontal Angel: 78°
64 -* Vertical Angel: 23°
46 +* Supply Voltage: 2.1v ~~ 3.6v
47 +* Operating Temperature: -40 ~~ 85°C
65 65  
49 +**NB-IoT Spec:**
66 66  
67 -== 1.4  Storage Temperature ==
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
68 68  
58 +== **1.4 Installation** ==
69 69  
70 - -40°C to +85°C
60 +Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
71 71  
62 +[[image:image-20221021110329-1.png]]
72 72  
64 +[[image:image-20221022234602-2.png||height="288" width="922"]]
73 73  
74 74  
67 +== **1.5 ​Applications** ==
75 75  
76 -== 1.5 ​ Applications ==
69 +* Open/Close Detection
70 +* Pulse meter application
71 +* Dry Contact Detection
77 77  
78 78  
74 +== **1.6 Mechanical** ==
79 79  
80 -* Horizontal distance measurement
81 -* Liquid level measurement
82 -* Parking management system
83 -* Object proximity and presence detection
84 -* Intelligent trash can management system
85 -* Robot obstacle avoidance
86 -* Automatic control
87 -* Sewer
88 -* Bottom water level monitoring
76 +​[[image:image-20221021110415-3.png]]
89 89  
90 -== 1.6  Specification ==
78 +== ** 1.7 Pin Definitions and Switch** ==
91 91  
80 +[[image:image-20221021110429-4.png]]
92 92  
93 -(% style="color:blue" %)**Common DC Characteristics:**
82 +=== **1.7.1 Pin Definition** ===
94 94  
95 -* Supply Voltage: 2.1v ~~ 3.6v
96 -* Operating Temperature: 0 ~~ 70°C
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]]**.
97 97  
98 -(% style="color:blue" %)**NB-IoT Spec:**
99 99  
100 -* B1 @H-FDD: 2100MHz
101 -* B3 @H-FDD: 1800MHz
102 -* B8 @H-FDD: 900MHz
103 -* B5 @H-FDD: 850MHz
104 -* B20 @H-FDD: 800MHz
105 -* B28 @H-FDD: 700MHz
87 +=== **1.7.2 Jumper JP2(Power ON/OFF)** ===
106 106  
107 -== 1.7  Installation ==
89 +Power on Device when putting this jumper.
108 108  
109 109  
110 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
92 +=== **1.7.3 BOOT MODE / SW1** ===
111 111  
112 112  
113 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
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.
114 114  
97 +2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
115 115  
116 116  
117 -== 1.8  Pin Definitions and Switch ==
100 +=== **1.7.4 Reset Button** ===
118 118  
119 119  
120 -[[image:1670404362039-351.png]]
103 +Press to reboot the device.
121 121  
105 +== ==
122 122  
123 -= 2.  Use NMDS200 to communicate with IoT Server =
107 +=== **1.7.5 LED** ===
124 124  
125 -== 2.1  How it works ==
126 126  
110 +The LED will blink when :
127 127  
128 -The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
112 +1. Boot the device in flash mode
113 +1. Send an uplink packet
129 129  
130 -The diagram below shows the working flow in the default firmware of NMDS200:
131 131  
132 -[[image:image-20221021110615-5.png]]
116 += **2.  Use CPN01 to communicate with IoT Server** =
133 133  
118 +== **2.1  How it works** ==
134 134  
135 -== 2.2 ​ Configure NMDS200 ==
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.
136 136  
122 +The diagram below shows the working flow in default firmware of CPN01:
137 137  
138 -To use NMDS200 in your city, make sure to meet below requirements:
124 +[[image:image-20221021110615-5.png]]
139 139  
140 -* Your local operator has already distributed an NB-IoT Network.
141 -* The local NB-IoT network used the band that NMDS200 supports.
142 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
126 +== **2.2 ​ Configure the CPN01** ==
143 143  
144 -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.
128 +=== **2.2.1 Test Requirement** ===
145 145  
146 -[[image:image-20221207173300-4.png]]
130 +To use CPN01 in your city, make sure meet below requirements:
147 147  
132 +* Your local operator has already distributed a NB-IoT Network there.
133 +* The local NB-IoT network used the band that CPN01 supports.
134 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
148 148  
149 -=== 2.2.1 Insert NB-IoT SIM card ===
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
150 150  
138 + ​
151 151  
140 +=== **2.2.2 Insert SIM card** ===
141 +
152 152  Insert the NB-IoT Card get from your provider.
153 153  
154 -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:
155 155  
156 156  [[image:image-20221021110745-6.png]] ​
157 157  
148 +=== **2.2.3 Connect USB – TTL to CPN01 to configure it** ===
158 158  
159 -=== 2.2.2 Connect USB – TTL to NMDS200 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.
160 160  
152 +**Connection:**
161 161  
162 -User need to configure NMDS200 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NMDS200 support AT Commands, user can use a USB to TTL adapter to connect to NMDS200 and use AT Commands to configure it, as below.
154 + USB TTL GND <~-~-~-~-> GND
163 163  
164 -(% style="color:blue" %)**Connection:**
156 + USB TTL TXD <~-~-~-~-> UART_RXD
165 165  
166 -(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
158 + USB TTL RXD <~-~-~-~-> UART_TXD
167 167  
168 -(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD**
169 -
170 -(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD**
171 -
172 -
173 173  In the PC, use below serial tool settings:
174 174  
175 -* Baud:  (% style="color:red" %)**9600**
162 +* Baud:  **9600**
163 +* Data bits:** 8**
164 +* Stop bits: **1**
165 +* Parity:  **None**
166 +* Flow Control: **None**
176 176  
177 -* 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.
178 178  
179 -* Stop bits: (% style="color:red" %)**1**
180 -
181 -* Parity:  (% style="color:red" %)**None**
182 -
183 -* Flow Control: (% style="color:red" %)**None**
184 -
185 -Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
186 -
187 187  ​[[image:image-20221021110817-7.png]]
188 188  
189 -NMDS200 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]]
190 190  
174 +=== **2.2.4 Use CoAP protocol to uplink data** ===
191 191  
192 -(% 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/]]
193 193  
178 +**Use below commands:**
194 194  
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
195 195  
196 -=== 2.2.3 Use CoAP protocol to uplink data ===
197 -
198 -
199 -(% 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/]]
200 -
201 -
202 -(% style="color:blue" %)**Use below commands in NDS03A:**
203 -
204 -* (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
205 -
206 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/ Set CoAP server address and port
207 -
208 -* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/  Set CoAP resource path
209 -
210 210  For parameter description, please refer to AT command set
211 211  
212 212  [[image:image-20221021110948-8.png]]
213 213  
188 +After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server.
214 214  
215 -After configuring the server address and (% style="color:green" %)**reset NMDS200**(%%) (via AT+ATZ ), NMDS200 will start to uplink sensor values to the CoAP server.
190 +[[image:image-20221021110956-9.png]] ​
216 216  
217 -[[image:1670405841875-916.png]] ​
192 +=== **2.2.5 Use UDP protocol to uplink data(Default protocol)** ===
218 218  
194 +This feature is supported since firmware version v1.0.1
219 219  
220 -=== 2.2.4 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
221 221  
222 -
223 -(% style="color:blue" %)**AT Commands:**
224 -
225 -* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
226 -
227 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  Set UDP server address and port
228 -
229 -* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
230 -
231 231  ​ [[image:image-20221021111025-10.png]]
232 232  
233 -
234 234  [[image:image-20221021111033-11.png||height="241" width="576"]]
235 235  
236 236  ​
237 237  
238 -=== 2.2.5 Use MQTT protocol to uplink data ===
206 +=== **2.2.6 Use MQTT protocol to uplink data** ===
239 239  
208 +This feature is supported since firmware version v110
240 240  
241 -(% 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
242 242  
243 -* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
218 +​ [[image:image-20221021111058-12.png]]
244 244  
245 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
220 +[[image:image-20221021111108-13.png]]
246 246  
247 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
248 -
249 -* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/  Set the username of MQTT
250 -
251 -* (% style="color:#037691" %)**AT+PWD=PWD                         **(%%)** **~/~/  Set the password of MQTT
252 -
253 -* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB              **(%%)** **~/~/  Set the sending topic of MQTT
254 -
255 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
256 -
257 -​ [[image:image-20221118103445-7.png]]
258 -
259 -
260 -[[image:1670405928926-116.png]]
261 -
262 262  ​
263 263  
264 -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.
265 265  
226 +=== **2.2.7 Use TCP protocol to uplink data** ===
266 266  
267 -=== 2.2.6 Use TCP protocol to uplink data ===
228 +This feature is supported since firmware version v110
268 268  
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
269 269  
270 -(% style="color:blue" %)**AT Commands:**
233 +​ [[image:image-20221021111125-14.png]]
271 271  
272 -* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
273 -
274 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
275 -
276 -​ [[image:1670406036256-101.png||height="676" width="713"]]
277 -
278 -
279 279  [[image:image-20221021111131-15.png]]
280 280  
281 281  ​
282 282  
283 -=== 2.2.7 Change Update Interval ===
239 +=== **2.2.8 Change Update Interval** ===
284 284  
241 +User can use below command to change the **uplink interval**.
285 285  
286 -User can use below command to change the (% style="color:blue" %)**uplink interval**.
243 +* **AT+TDC=600      ** ~/~/ Set Update Interval to 600s
287 287  
288 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
245 +**NOTE:**
289 289  
290 -(% style="color:red" %)**NOTE:**
247 +**~1. By default, the device will send an uplink message every 1 hour.**
291 291  
292 -1.  By default, the device will send an uplink message every 4 hour.
249 +== **2.3  Uplink Payload** ==
293 293  
251 +In this mode, uplink payload includes 87 bytes in total by default.
294 294  
295 -== 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.
296 296  
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
297 297  
298 -The uplink payload includes 23 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|...
299 299  
300 -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.
301 301  
263 +[[image:image-20221021111201-16.png||height="572" width="792"]]
302 302  
303 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
304 -|=(% 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:90px" %)**2**|(% style="width:100px" %)**2**
305 -|=(% 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" %)Exit flag|(% style="width:94px" %) Distance 1 |(% style="width:93px" %) Distance  2
265 +The payload is ASCII string, representative same HEX:
306 306  
307 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
308 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
309 -**1-32 group**
310 -)))
311 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
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 //(%%)**
312 312  
313 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
269 +where:
270 +*(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317
314 314  
315 -[[image:1670406261143-723.png]]
272 +*(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0
316 316  
274 +*(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
317 317  
318 -The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
276 +*(% style="color:#037691" %) **Singal: **(%%)0x17 = 23
319 319  
320 -**0x (% style="color:red" %)__f867787050471071__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)**
278 +*(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
321 321  
322 -**where:**
280 +*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00= 0
323 323  
324 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
282 +*(% style="color:#037691" %) **Contact Status:**(%%) 0x00= 0
325 325  
326 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
284 +*(% style="color:#037691" %) **Alarm:**(%%)0x00 =0
327 327  
328 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
286 +*(% style="color:#037691" %) **Total pulse:0x09 =0**
329 329  
330 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
288 +*(% style="color:#037691" %) **The last open duration:**(%%)0x02 =2
331 331  
332 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
290 +*(% style="color:#037691" %)**Time stamp :**(%%) 0x6315537b =1662342011
333 333  
334 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
292 +*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000b0200002663510fed
335 335  
336 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
294 +*(% style="color:#037691" %) **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
337 337  
338 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
296 +== **2.4  Payload Explanation and Sensor Interface** ==
339 339  
340 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
298 +=== **2.4.1  Device ID** ===
341 341  
300 +By default, the Device ID equal to the last 15 bits of IMEI.
342 342  
343 -== 2.4  Payload Explanation and Sensor Interface ==
302 +User can use **AT+DEUI** to set Device ID
344 344  
345 -=== 2.4.1  Device ID ===
346 -
347 -
348 -By default, the Device ID is equal to the last 15 bits of IMEI.
349 -
350 -User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
351 -
352 352  **Example:**
353 353  
354 354  AT+DEUI=868411056754138
355 355  
356 -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.
357 357  
310 +=== **2.4.2  Version Info** ===
358 358  
359 -=== 2.4.2  Version Info ===
312 +Specify the software version: 0x64=100, means firmware version 1.00.
360 360  
314 +For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0.
361 361  
362 -Specify the software version: 0x64=100, which means firmware version 1.00.
316 +=== **2.4.3  Battery Info** ===
363 363  
364 -For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
318 +Check the battery voltage for CPN01.
365 365  
366 -
367 -=== 2.4.3  Battery Info ===
368 -
369 -
370 -Check the battery voltage for NMDS200.
371 -
372 372  Ex1: 0x0B45 = 2885mV
373 373  
374 374  Ex2: 0x0B49 = 2889mV
375 375  
324 +=== **2.4.4  Signal Strength** ===
376 376  
377 -=== 2.4.4  Signal Strength ===
378 -
379 -
380 380  NB-IoT Network signal Strength.
381 381  
382 382  **Ex1: 0x1d = 29**
... ... @@ -391,43 +391,58 @@
391 391  
392 392  **99**    Not known or not detectable
393 393  
340 +=== **2.4.5 Calculate Flag** ===
394 394  
395 -=== 2.4.5  Distance ===
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.
396 396  
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.
397 397  
398 -[[image:1670407401682-959.png]]
346 +Default value: 0. 
399 399  
400 -(% style="color:blue" %)**Object1 Distance:**
348 +Range (6 bits): (b)000000 ~~ (b) 111111
401 401  
402 -Distance between sensor probe to the first object. (unit: cm)
350 +=== **2.4.6  Alarm** ===
403 403  
404 -For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
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]]
405 405  
406 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
354 +=== **2.4.7 Contact Status** ===
407 407  
356 +0: Open
408 408  
409 -(% style="color:blue" %)**Object2 Distance:**
358 +1: Close
410 410  
411 -Distance between sensor probe to the second object. (unit: cm)
360 +=== **2.4.8 Total pulse** ===
412 412  
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]]
413 413  
414 -=== 2.4.6  Timestamp ===
364 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
415 415  
366 +=== **2.4.9 The last open duration** ===
416 416  
417 -Timestamp : 0x6315537b =1662342011
368 +Dry Contact last open duration.
418 418  
370 +Unit: min.
419 419  
420 -== 2.5  Downlink Payload ==
372 +[[image:image-20221021111346-17.png||height="146" width="770"]]
421 421  
422 422  
423 -By default, NMDS200 prints the downlink payload to console port.
375 +=== **2.4.10  Timestamp** ===
424 424  
425 -[[image:image-20221021111414-18.png]] ​
377 +Time stamp : 0x6315537b =1662342011
426 426  
379 +Convert Unix timestamp to time 2022-9-5 9:40:11.
427 427  
381 +**~ **
382 +
383 +== **2.5  Downlink Payload** ==
384 +
385 +By default, CPN01 prints the downlink payload to console port.
386 +
387 +[[image:image-20221021111414-18.png]] ​
388 +
428 428  **Examples:**
429 429  
430 -* (% style="color:#037691" %)**Set TDC**
391 +* **Set TDC**
431 431  
432 432  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
433 433  
... ... @@ -435,223 +435,171 @@
435 435  
436 436  Payload:    01 00 00 3C    TDC=60S
437 437  
438 -* (% style="color:#037691" %)**Reset**
399 +* **Reset**
439 439  
440 -If payload = 0x04FF, it will reset the NMDS200
401 +If payload = 0x04FF, it will reset the NSE01
441 441  
442 -* (% style="color:#037691" %)**INTMOD**
403 +* **INTMOD**
443 443  
444 444  Downlink Payload: 06000003, Set AT+INTMOD=3
445 445  
407 +== **2.6  ​LED Indicator** ==
446 446  
447 -== 2.6  ​LED Indicator ==
409 +The CPN01 has an internal LED which is to show the status of different state.
448 448  
449 -
450 -The NMDS200 has an internal LED which is to show the status of different states.
451 -
452 -* When the device starts normally, the LED will light up for 1 second.
453 -* 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.
454 454  * For each uplink probe, LED will be on for 500ms.
455 455  
416 +== **2.7  Alarm Base on Timeout** ==
456 456  
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:
457 457  
458 -== 2.7  Distance alarm function ==
459 459  
421 +**~1. Keep Status: Status to be monitor**
460 460  
461 -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:
462 -
463 -
464 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
465 -
466 466  Keep Status = 1: Monitor Close to Open event
467 467  
468 468  Keep Status = 0: Monitor Open to Close event
469 469  
470 470  
471 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
428 +**2. Keep Time: Timeout to send an Alarm**
472 472  
473 473  Range 0 ~~ 65535(0xFFFF) seconds.
474 474  
475 475  If keep time = 0, Disable Alarm Base on Timeout feature.
476 476  
477 -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.
478 478  
479 479  
480 -(% style="color:blue" %)**AT Command to configure:**
437 +**AT Command** to configure:
481 481  
482 -(% 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.
483 483  
484 -(% 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.
485 485  
486 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
443 +== **2.8 Set debug mode** ==
487 487  
488 -
489 -(% style="color:blue" %)**PB15 PIN:**
490 -
491 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
492 -
493 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
494 -
495 -
496 -== 2.8  Set debug mode ==
497 -
498 -
499 499  Feature: Enable or Disable debug mode
500 500  
501 -(% style="color:blue" %)**AT Command: AT+DEBUG**
502 502  
448 +**AT Command: AT+DEBUG**
449 +
503 503  [[image:image-20221021111629-21.png]]
504 504  
452 +== **2.9 Clear Flash Record** ==
505 505  
506 -
507 -== 2.9  Clear Flash Record ==
508 -
509 -
510 510  Feature: Clear flash storage for data log feature.
511 511  
512 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
456 +**AT Command: AT+CLRDTA**
513 513  
514 514  [[image:image-20221021111527-19.png]]
515 515  
460 +== ** 2.10 Set trigger mode** ==
516 516  
517 -== 2.10  Count Mod ==
462 +➢ AT Command: **AT+TTRMOD**
518 518  
464 +Feature: Set the trigger interrupt mode.
519 519  
520 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
466 +[[image:image-20221021111552-20.png]]
521 521  
522 -[[image:image-20221118092935-1.png]]
468 +== **2.11 Set the calculate flag** ==
523 523  
470 +Feature: Set the calculate flag
524 524  
525 -== 2.11  Interrupt Pin Channel Mod ==
472 +**AT Command: AT+CALCFLAG**
526 526  
474 +[[image:image-20221021111711-22.png]]
527 527  
528 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
476 +== **2.12 Set count number** ==
529 529  
530 -[[image:image-20221118093144-2.png]]
478 +Feature: Manually set the count number
531 531  
480 +**AT Command: AT+SETCNT**
532 532  
533 -== 2.12 TTRIG1/2 timeout status alarm ==
482 +[[image:image-20221021111748-24.png]]
534 534  
484 +== **2.13 Set the number of data to be uploaded and the recording time** ==
535 535  
536 -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:
537 537  
538 -(% 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)
539 539  
540 -[[image:image-20221118093512-3.png]]
541 541  
491 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
542 542  
543 -== 2.13  Select counting mode ==
493 +== **2.14 Read or Clear cached data** ==
544 544  
495 +➢ AT Command:
545 545  
546 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
497 +AT+CDP    ~/~/ Read cached data
547 547  
548 -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"]]
549 549  
550 -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.
551 551  
552 -[[image:image-20221118093658-4.png]]
502 +AT+CDP=0    ~/~/ Clear cached data ​
553 553  
504 +== **2.15  ​Firmware Change Log** ==
554 554  
555 -== 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]]
556 556  
508 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
557 557  
558 -(% style="color:blue" %)**AT Command:**
510 +== **2.16  ​Battery Analysis** ==
559 559  
560 -(% 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** ===
561 561  
562 -(% 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.
563 563  
516 +The battery is designed to last for several years depends on the actually use environment and update interval. 
564 564  
565 -== 2.15  Read or Clear cached data ==
518 +The battery related documents as below:
566 566  
567 -
568 -(% style="color:blue" %)**AT Command:**
569 -
570 -(% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
571 -
572 -(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
573 -
574 -[[image:image-20221118094227-5.png]]
575 -
576 -
577 -== 2.16  ​Firmware Change Log ==
578 -
579 -
580 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
581 -
582 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
583 -
584 -
585 -== 2.17  ​Battery Analysis ==
586 -
587 -=== 2.17.1  ​Battery Type ===
588 -
589 -
590 -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.
591 -
592 -The battery is designed to last for several years depends on the actual use environment and update interval. 
593 -
594 -The battery-related documents as below:
595 -
596 596  * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
597 -
598 598  * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
599 -
600 600  * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
601 601  
602 602  [[image:image-20221021111911-26.png]] ​
603 603  
526 +=== **2.16.2  Power consumption Analyze** ===
604 604  
605 -=== 2.17.2  Power consumption Analyze ===
606 -
607 -
608 608  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.
609 609  
610 610  Instruction to use as below:
611 611  
612 -(% 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/]]
613 613  
614 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
534 +**Step 2: ** Open it and choose
615 615  
616 616  * Product Model
617 -
618 618  * Uplink Interval
619 -
620 620  * Working Mode
621 621  
622 622  And the Life expectation in difference case will be shown on the right.
623 623  
624 -[[image:1666596205057-567.png]] ​
542 +[[image:image-20221021111923-27.png||height="253" width="783"]] ​
625 625  
544 +=== **2.16.3  ​Battery Note** ===
626 626  
627 -=== 2.17.3  ​Battery Note ===
628 -
629 -
630 630  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.
631 631  
548 +=== **2.16.4  Replace the battery** ===
632 632  
633 -=== 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).
634 634  
552 += **3. ​ Access NB-IoT Module** =
635 635  
636 -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).
637 -
638 -
639 -= 3. ​ Access NB-IoT Module =
640 -
641 -
642 642  Users can directly access the AT command set of the NB-IoT module.
643 643  
644 644  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/]] 
645 645  
558 +[[image:image-20221021112006-28.png]] ​
646 646  
647 -[[image:image-20221118094449-6.png]] ​
560 += **4.  Using the AT Commands** =
648 648  
562 +== **4.1  Access AT Commands** ==
649 649  
650 -= 4.  Using the AT Commands =
651 -
652 -== 4.1  Access AT Commands ==
653 -
654 -
655 655  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]]
656 656  
657 657  AT+<CMD>?  : Help on <CMD>
... ... @@ -662,9 +662,8 @@
662 662  
663 663  AT+<CMD>=?  : Get the value
664 664  
574 +**General Commands**      
665 665  
666 -(% style="color:blue" %)**General Commands**      
667 -
668 668  AT  : Attention       
669 669  
670 670  AT?  : Short Help     
... ... @@ -687,41 +687,35 @@
687 687  
688 688  AT+SERVADDR  : Server Address
689 689  
690 -AT+TR      :  Get or Set record time
598 +AT+TR      : Get or Set record time"
691 691  
600 +
692 692  AT+NOUD      : Get or Set the number of data to be uploaded
693 693  
694 -AT+CDP     :  Read or Clear cached data
695 695  
696 -AT+ DEBUG   : Enable or Disable debug mode
604 +AT+CDP     : Read or Clear cached data
697 697  
698 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
699 699  
700 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
607 +AT+ DEBUG   : Enable or Disable debug mode
701 701  
702 -AT+COUNTMOD  :  Get or Set the count mode
609 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
703 703  
704 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
611 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
705 705  
706 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
613 +AT+ CALCFLAG   : Get or Set the calculate flag
707 707  
708 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
615 +AT+ CLRC   : Clear current door open count
709 709  
710 -AT+ CLRC   :  Clear current door open count
617 +**COAP Management**      
711 711  
712 -
713 -(% style="color:blue" %)**COAP Management**      
714 -
715 715  AT+URI            : Resource parameters
716 716  
621 +**UDP Management**
717 717  
718 -(% style="color:blue" %)**UDP Management**
719 -
720 720  AT+CFM          : Upload confirmation mode (only valid for UDP)
721 721  
625 +**MQTT Management**
722 722  
723 -(% style="color:blue" %)**MQTT Management**
724 -
725 725  AT+CLIENT               : Get or Set MQTT client
726 726  
727 727  AT+UNAME  : Get or Set MQTT Username
... ... @@ -732,58 +732,86 @@
732 732  
733 733  AT+SUBTOPIC  : Get or Set MQTT subscription topic
734 734  
637 +**Information**          
735 735  
736 -(% style="color:blue" %)**Information**          
737 -
738 738  AT+FDR  : Factory Data Reset
739 739  
740 740  AT+PWORD  : Serial Access Password
741 741  
643 += **​5.  FAQ** =
742 742  
743 -= ​5.  FAQ =
645 +== **5.1 ​ How to Upgrade Firmware** ==
744 744  
745 -== 5.1 ​ How to Upgrade Firmware ==
746 -
747 -
748 748  User can upgrade the firmware for 1) bug fix, 2) new feature release.
749 749  
750 750  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]]
751 751  
752 -(% 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.**
753 753  
653 +== **5.2  Can I calibrate CPN01 to different soil types?** ==
754 754  
755 -= 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]].
756 756  
757 -== 6.1  ​Connection problem when uploading firmware ==
657 += **6.  Trouble Shooting** =
758 758  
659 +== **6.1  ​Connection problem when uploading firmware** ==
759 759  
760 -(% 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]]
761 761  
663 +== **6.2  AT Command input doesn't work** ==
762 762  
763 -== 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.
764 764  
667 += **7. ​ Order Info** =
765 765  
766 -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
767 767  
671 += **8.  Packing Info** =
768 768  
769 -= 7. ​ Order Info =
673 +**Package Includes**:
770 770  
675 +* CPN01 NB-IoT Soil Moisture & EC Sensor x 1
676 +* External antenna x 1
771 771  
772 -Part Number**:** NDS03A
678 +**Dimension and weight**:
773 773  
680 +* Size: 195 x 125 x 55 mm
681 +* Weight:   420g
774 774  
775 -= 8.  Packing Info =
683 += **9.  Support** =
776 776  
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]]
777 777  
778 -(% style="color:blue" %)**Package Includes**:
688 +​
779 779  
780 -* NDS03A Open/Close Door Sensor x 1
781 781  
782 -= 9.  Support =
783 783  
784 784  
785 -* 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.
786 786  
787 -* 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]]
788 788  
789 -​
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
1670406261143-723.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.9 KB
Content
1670407401682-959.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -23.7 KB
Content
LMDS200_10.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 KB
Content
image-20221023000439-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -82.1 KB
Content
image-20221117105556-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -133.3 KB
Content
image-20221117114459-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
image-20221117114842-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -964.1 KB
Content
image-20221117114937-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.1 KB
Content
image-20221117114949-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -33.4 KB
Content
image-20221117115010-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -40.4 KB
Content
image-20221117142300-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -147.8 KB
Content
image-20221117145932-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -51.9 KB
Content
image-20221117150312-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.7 KB
Content
image-20221118092935-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -13.1 KB
Content
image-20221118093144-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.7 KB
Content
image-20221118093512-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -9.5 KB
Content
image-20221118093658-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -12.7 KB
Content
image-20221118094227-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.2 KB
Content
image-20221118094449-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.5 KB
Content
image-20221118103445-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -20.4 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.5 KB
Content
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