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

Applications

Navigation

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