Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 90.4 >
edited by Xiaoling
on 2022/12/23 09:19
To version < 35.1 >
edited by Edwin Chen
on 2022/10/22 23:43
>
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,531 +78,527 @@
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 CPL01 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-20221021110340-2.png]]
99 99  
100 - -40°C to +85°C
66 +== **1.5 ​Applications** ==
101 101  
68 +* Open/Close Detection
69 +* Pulse meter application
70 +* Dry Contact Detection
102 102  
103 -== 1.5 ​ Applications ==
72 +== **1.6 Mechanical** ==
104 104  
74 +​[[image:image-20221021110415-3.png]]
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
76 +== ** 1.7 Pin Definitions and Switch** ==
115 115  
78 +[[image:image-20221021110429-4.png]]
116 116  
80 +=== **1.7.1 Pin Definition** ===
117 117  
118 -== 1.6  Specification ==
82 +CPL01 is pre-configured to connect to two external wires. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at: [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>url:https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]
119 119  
84 +=== **1.7.2 Jumper JP2(Power ON/OFF)** ===
120 120  
121 -(% style="color:blue" %)**Common DC Characteristics:**
122 122  
123 -* Supply Voltage: 2.1v ~~ 3.6v
124 -* Operating Temperature: 0 ~~ 70°C
87 +Power on Device when putting this jumper.
125 125  
126 -(% style="color:blue" %)**NB-IoT Spec:**
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. Firmware won't run.
138 138  
96 +2) Flash: work mode, the device starts to work and send out console output for further debug
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  
142 142  
143 -[[image:image-20221207170748-1.png]]
100 +=== **1.7.4 Reset Button** ===
144 144  
145 145  
146 - [[image:image-20221207170748-2.png||height="345" width="634"]]
103 +Press to reboot the device.
147 147  
105 +== ==
148 148  
149 -== 1.8  Pin Definitions and Switch ==
107 +=== **1.7.5 LED** ===
150 150  
151 151  
152 -[[image:1670404362039-351.png]]
110 +It will flash:
153 153  
112 +1. Boot the device in flash mode
113 +1. Send an uplink packet
154 154  
155 -= 2.  Use NMDS200 to communicate with IoT Server =
115 += **2.  Use CPN01 to communicate with IoT Server** =
156 156  
157 -== 2.1  How it works ==
117 +== **2.1  How it works** ==
158 158  
119 +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.
159 159  
160 -The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
121 +The diagram below shows the working flow in default firmware of CPN01:
161 161  
162 -The diagram below shows the working flow in the default firmware of NMDS200:
123 +[[image:image-20221021110615-5.png]]
163 163  
164 -[[image:image-20221021110615-5.png||height="996" width="492"]]
125 +== **2.2 ​ Configure the CPN01** ==
165 165  
127 +=== **2.2.1 Test Requirement** ===
166 166  
167 -== 2.2 ​ Configure NMDS200 ==
129 +To use CPN01 in your city, make sure meet below requirements:
168 168  
169 -
170 -To use NMDS200 in your city, make sure to meet below requirements:
171 -
172 -* Your local operator has already distributed an NB-IoT Network.
173 -* The local NB-IoT network used the band that NMDS200 supports.
131 +* Your local operator has already distributed a NB-IoT Network there.
132 +* 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.
135 +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]]
137 + ​
179 179  
139 +=== **2.2.2 Insert SIM card** ===
180 180  
181 -=== 2.2.1 Insert NB-IoT SIM card ===
182 -
183 -
184 184  Insert the NB-IoT Card get from your provider.
185 185  
186 -User needs to take out the NB-IoT module and insert the SIM card like below:
143 +User need to take out the NB-IoT module and insert the SIM card like below:
187 187  
188 188  [[image:image-20221021110745-6.png]] ​
189 189  
147 +=== **2.2.3 Connect USB – TTL to CPN01 to configure it** ===
190 190  
191 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
149 +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.
192 192  
151 +**Connection:**
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 + USB TTL GND <~-~-~-~-> GND
195 195  
196 -(% style="color:blue" %)**Connection:**
155 + USB TTL TXD <~-~-~-~-> UART_RXD
197 197  
198 -(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
157 + USB TTL RXD <~-~-~-~-> UART_TXD
199 199  
200 -(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD**
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**
161 +* Baud:  **9600**
162 +* Data bits:** 8**
163 +* Stop bits: **1**
164 +* Parity:  **None**
165 +* Flow Control: **None**
208 208  
209 -* Data bits:** (% style="color:red" %)8(%%)**
167 +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.
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.
171 +**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]]
222 222  
173 +=== **2.2.4 Use CoAP protocol to uplink data** ===
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]]
175 +**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/]]
225 225  
177 +**Use below commands:**
226 226  
227 -=== 2.2.3 Use CoAP protocol to uplink data ===
179 +* **AT+PRO=1**   ~/~/ Set to use CoAP protocol to uplink
180 +* **AT+SERVADDR=120.24.4.116,5683   ** ~/~/ to set CoAP server address and port
181 +* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path
228 228  
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/]]
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"]]
185 +[[image:image-20221021110948-8.png]]
244 244  
187 +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.
189 +[[image:image-20221021110956-9.png]] ​
247 247  
248 -[[image:1670405841875-916.png]] ​
191 +=== **2.2.5 Use UDP protocol to uplink data(Default protocol)** ===
249 249  
193 +This feature is supported since firmware version v1.0.1
250 250  
251 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
195 +* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
196 +* **AT+SERVADDR=120.24.4.116,5601   ** ~/~/ to set UDP server address and port
197 +* **AT+CFM=1       ** ~/~/If the server does not respond, this command is unnecessary
252 252  
199 +​ [[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 ===
205 +=== **2.2.6 Use MQTT protocol to uplink data** ===
270 270  
207 +This feature is supported since firmware version v110
271 271  
272 -(% style="color:blue" %)**AT Commands:**
209 +* **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
210 +* **AT+SERVADDR=120.24.4.116,1883   ** ~/~/Set MQTT server address and port
211 +* **AT+CLIENT=CLIENT       ** ~/~/Set up the CLIENT of MQTT
212 +* **AT+UNAME=UNAME                               **~/~/Set the username of MQTT
213 +* **AT+PWD=PWD                                        **~/~/Set the password of MQTT
214 +* **AT+PUBTOPIC=NSE01_PUB                    **~/~/Set the sending topic of MQTT
215 +* **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
217 +​ [[image:image-20221021111058-12.png]]
275 275  
276 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
219 +[[image:image-20221021111108-13.png]]
277 277  
278 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
221 +​
279 279  
280 -* (% style="color:#037691" %)**AT+UNAME=UNAME                     **(%%)** **~/~/  Set the username of MQTT
223 +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
225 +=== **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
227 +This feature is supported since firmware version v110
285 285  
286 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
229 +* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
230 +* **AT+SERVADDR=120.24.4.116,5600   ** ~/~/ to set TCP server address and port
287 287  
288 -​ [[image:1670471584490-640.png]]
232 +​ [[image:image-20221021111125-14.png]]
289 289  
234 +[[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.
238 +=== **2.2.8 Change Update Interval** ===
296 296  
240 +User can use below command to change the **uplink interval**.
297 297  
298 -=== 2.2.6 Use TCP protocol to uplink data ===
242 +* **AT+TDC=600      ** ~/~/ Set Update Interval to 600s
299 299  
244 +**NOTE:**
300 300  
301 -(% style="color:blue" %)**AT Commands:**
246 +**~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
248 +== **2.3  Uplink Payload** ==
304 304  
305 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
250 +In this mode, uplink payload includes 87 bytes in total by default.
306 306  
307 -​ [[image:1670471613823-833.png]]
252 +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  
254 +|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**2**|**2**|4
255 +|**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]]
257 +|2|2|4|8 group
258 +|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|Time stamp|...
311 311  
312 -​
260 +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 ===
262 +[[image:image-20221021111201-16.png||height="572" width="792"]]
315 315  
264 +The payload is ASCII string, representative same HEX:
316 316  
317 -User can use below command to change the (% style="color:blue" %)**uplink interval**.
266 +**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)
268 +where:
269 +*(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317
320 320  
321 -(% style="color:red" %)**NOTE:**
271 +*(% 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.
273 +*(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V
324 324  
275 +*(% style="color:#037691" %) **Singal: **(%%)0x17 = 23
325 325  
326 -== 2.3  Uplink Payload ==
277 +*(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1
327 327  
279 +*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00= 0
328 328  
329 -The uplink payload includes 23 bytes in total by default.
281 +*(% 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.
283 +*(% style="color:#037691" %) **Alarm:**(%%)0x00 =0
332 332  
285 +*(% 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"]]
287 +*(% 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" %)...
289 +*(% 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.
291 +*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000b0200002663510fed
345 345  
346 -[[image:1670406261143-723.png]]
293 +*(% style="color:#037691" %) **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......
347 347  
295 +== **2.4  Payload Explanation and Sensor Interface** ==
348 348  
349 -The payload is ASCII string, representative same HEX: **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__(%%)**
297 +=== **2.4.1  Device ID** ===
350 350  
351 -**where:**
299 +By default, the Device ID equal to the last 15 bits of IMEI.
352 352  
353 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
301 +User can use **AT+DEUI** to set Device ID
354 354  
355 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
303 +**Example:**
356 356  
357 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
305 +AT+DEUI=868411056754138
358 358  
359 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
307 +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" %)**Mod:**(%%)  0x01 = 1
309 +=== **2.4.2  Version Info** ===
362 362  
363 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
311 +Specify the software version: 0x64=100, means firmware version 1.00.
364 364  
365 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
313 +For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0.
366 366  
367 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
315 +=== **2.4.3  Battery Info** ===
368 368  
369 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
317 +Check the battery voltage for CPN01.
370 370  
319 +Ex1: 0x0B45 = 2885mV
371 371  
321 +Ex2: 0x0B49 = 2889mV
372 372  
373 -== 2.4  Payload Explanation and Sensor Interface ==
323 +=== **2.4.4  Signal Strength** ===
374 374  
375 -=== 2.4.1  Device ID ===
325 +NB-IoT Network signal Strength.
376 376  
327 +**Ex1: 0x1d = 29**
377 377  
378 -By default, the Device ID is equal to the last 15 bits of IMEI.
329 +**0**  -113dBm or less
379 379  
380 -User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID
331 +**1**  -111dBm
381 381  
382 -**Example:**
333 +**2...30** -109dBm... -53dBm
383 383  
384 -AT+DEUI=868411056754138
335 +**31**   -51dBm or greater
385 385  
386 -The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
337 +**99**    Not known or not detectable
387 387  
339 +=== **2.4.5 Calculate Flag** ===
388 388  
389 -=== 2.4.2  Version Info ===
341 +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  
343 +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.
391 391  
392 -Specify the software version: 0x64=100, which means firmware version 1.00.
345 +Default value: 0. 
393 393  
394 -For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
347 +Range (6 bits): (b)000000 ~~ (b) 111111
395 395  
349 +=== **2.4.6  Alarm** ===
396 396  
397 -=== 2.4.3  Battery Info ===
351 +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  
353 +=== **2.4.7 Contact Status** ===
399 399  
400 -Check the battery voltage for NMDS200.
355 +0: Open
401 401  
402 -Ex1: 0x0B45 = 2885mV
357 +1: Close
403 403  
404 -Ex2: 0x0B49 = 2889mV
359 +=== **2.4.8 Total pulse** ===
405 405  
361 +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]]
406 406  
407 -=== 2.4.4  Signal Strength ===
363 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
408 408  
365 +=== **2.4.9 The last open duration** ===
409 409  
410 -NB-IoT Network signal Strength.
367 +Dry Contact last open duration.
411 411  
412 -(% style="color:blue" %)**Ex1: 0x1d = 29**
369 +Unit: min.
413 413  
414 -(% style="color:#037691" %)**0** (%%) -113dBm or less
371 +[[image:image-20221021111346-17.png||height="146" width="770"]]
415 415  
416 -(% style="color:#037691" %)**1**  (%%) -111dBm
417 417  
418 -(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
374 +=== **2.4.10  Timestamp** ===
419 419  
420 -(% style="color:#037691" %)**31** (%%) -51dBm or greater
376 +Time stamp : 0x6315537b =1662342011
421 421  
422 -(% style="color:#037691" %)**99** (%%) Not known or not detectable
378 +Convert Unix timestamp to time 2022-9-5 9:40:11.
423 423  
380 +**~ **
424 424  
425 -=== 2.4.5  Distance ===
382 +== **2.5  Downlink Payload** ==
426 426  
384 +By default, CPN01 prints the downlink payload to console port.
427 427  
428 -[[image:1670407401682-959.png]]
386 +[[image:image-20221021111414-18.png]] ​
429 429  
388 +**Examples:**
430 430  
431 -(% style="color:blue" %)**Object1 Distance:**
390 +* **Set TDC**
432 432  
433 -Distance between sensor probe to the first object. (unit: cm)
392 +If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
434 434  
435 -For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
394 +Payload:    01 00 00 1E    TDC=30S
436 436  
437 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
396 +Payload:    01 00 00 3C    TDC=60S
438 438  
398 +* **Reset**
439 439  
440 -(% style="color:blue" %)**Object2 Distance:**
400 +If payload = 0x04FF, it will reset the NSE01
441 441  
442 -Distance between sensor probe to the second object. (unit: cm)
402 +* **INTMOD**
443 443  
404 +Downlink Payload: 06000003, Set AT+INTMOD=3
444 444  
445 -=== 2.4.6  Timestamp ===
406 +== **2.6  ​LED Indicator** ==
446 446  
408 +The CPN01 has an internal LED which is to show the status of different state.
447 447  
448 -Timestamp : 0x6315537b =1662342011
410 +* 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)
411 +* Then the LED will be on for 1 second means device is boot normally.
412 +* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
413 +* For each uplink probe, LED will be on for 500ms.
449 449  
415 +== **2.7  Alarm Base on Timeout** ==
450 450  
451 -== 2.5  Downlink Payload ==
417 +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 453  
454 -By default, NMDS200 prints the downlink payload to console port.
420 +**~1. Keep Status: Status to be monitor**
455 455  
456 -[[image:image-20221021111414-18.png]] ​
422 +Keep Status = 1: Monitor Close to Open event
457 457  
424 +Keep Status = 0: Monitor Open to Close event
458 458  
459 -**Examples:**
460 460  
461 -* (% style="color:#037691" %)**Set TDC**
427 +**2. Keep Time: Timeout to send an Alarm**
462 462  
463 -If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
429 +Range 0 ~~ 65535(0xFFFF) seconds.
464 464  
465 -Payload:    01 00 00 1E    TDC=30S
431 +If keep time = 0, Disable Alarm Base on Timeout feature.
466 466  
467 -Payload:    01 00 00 3C    TDC=60S
433 +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 -* (% style="color:#037691" %)**Reset**
470 470  
471 -If payload = 0x04FF, it will reset the NMDS200
436 +**AT Command** to configure:
472 472  
473 -* (% style="color:#037691" %)**INTMOD**
438 +**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 -Downlink Payload: 06000003, Set AT+INTMOD=3
440 +**AT+TTIG=0,0 ** ~-~-> Default Value, disable timeout Alarm.
476 476  
442 +== **2.8 Set debug mode** ==
477 477  
478 -== 2.6  ​LED Indicator ==
444 +Feature: Enable or Disable debug mode
479 479  
480 480  
481 -The NMDS200 has an internal LED which is to show the status of different states.
447 +**AT Command: AT+DEBUG**
482 482  
483 -* When the device starts normally, the LED will light up for 1 second.
484 -* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
485 -* For each uplink probe, LED will be on for 500ms.
449 +[[image:image-20221021111629-21.png]]
486 486  
451 +== **2.9 Clear Flash Record** ==
487 487  
453 +Feature: Clear flash storage for data log feature.
488 488  
489 -== 2.7  Distance alarm function ==
455 +**AT Command: AT+CLRDTA**
490 490  
457 +[[image:image-20221021111527-19.png]]
491 491  
492 -(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
459 +== ** 2.10 Set trigger mode** ==
493 493  
494 -(% style="color:#037691" %)**Example 1:**
461 +➢ AT Command: **AT+TTRMOD**
495 495  
496 -AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
463 +Feature: Set the trigger interrupt mode.
497 497  
498 -AT+ ALARM2 =min,max
465 +[[image:image-20221021111552-20.png]]
499 499  
467 +== **2.11 Set the calculate flag** ==
500 500  
501 -(% style="color:#037691" %)**Example 2:**
469 +Feature: Set the calculate flag
502 502  
503 -AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
471 +**AT Command: AT+CALCFLAG**
504 504  
473 +[[image:image-20221021111711-22.png]]
505 505  
506 -== 2.8  Set the number of data to be uploaded and the recording time ==
475 +== **2.12 Set count number** ==
507 507  
477 +Feature: Manually set the count number
508 508  
509 -(% style="color:blue" %)**AT Command:**
479 +**AT Command: AT+SETCNT**
510 510  
511 -(% 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)
481 +[[image:image-20221021111748-24.png]]
512 512  
513 -(% 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.
483 +== **2.13 Set the number of data to be uploaded and the recording time** ==
514 514  
485 +➢ AT Command:
515 515  
516 -== 2.9  Read or Clear cached data ==
487 +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 518  
519 -(% style="color:blue" %)**AT Command:**
490 +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:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
492 +== **2.14 Read or Clear cached data** ==
522 522  
523 -(% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
494 +➢ AT Command:
524 524  
525 -[[image:1670408172929-569.png]]
496 +AT+CDP    ~/~/ Read cached data
526 526  
498 +[[image:image-20221021111810-25.png||height="364" width="797"]]
527 527  
528 -== 2.10  ​Firmware Change Log ==
529 529  
501 +AT+CDP=0    ~/~/ Clear cached data ​
530 530  
531 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0>>https://www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0]]
503 +== **2.15  ​Firmware Change Log** ==
532 532  
533 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
505 +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  
507 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
535 535  
536 -== 2.11  ​Battery Analysis ==
509 +== **2.16  ​Battery Analysis** ==
537 537  
538 -=== 2.11.1  ​Battery Type ===
511 +=== **2.16.1  ​Battery Type** ===
539 539  
513 +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.
540 540  
541 -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.
515 +The battery is designed to last for several years depends on the actually use environment and update interval. 
542 542  
543 -The battery is designed to last for several years depends on the actual use environment and update interval. 
517 +The battery related documents as below:
544 544  
545 -The battery-related documents as below:
546 -
547 547  * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
548 -
549 549  * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
550 -
551 551  * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
552 552  
553 553  [[image:image-20221021111911-26.png]] ​
554 554  
525 +=== **2.16.2  Power consumption Analyze** ===
555 555  
556 -=== 2.11.2  Power consumption Analyze ===
557 -
558 -
559 559  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.
560 560  
561 561  Instruction to use as below:
562 562  
563 -(% 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/]]
531 +**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/]]
564 564  
565 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
533 +**Step 2: ** Open it and choose
566 566  
567 567  * Product Model
568 -
569 569  * Uplink Interval
570 -
571 571  * Working Mode
572 572  
573 573  And the Life expectation in difference case will be shown on the right.
574 574  
575 -[[image:1666596205057-567.png]] ​
541 +[[image:image-20221021111923-27.png||height="253" width="783"]] ​
576 576  
543 +=== **2.16.3  ​Battery Note** ===
577 577  
578 -=== 2.11.3  ​Battery Note ===
579 -
580 -
581 581  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.
582 582  
547 +=== **2.16.4  Replace the battery** ===
583 583  
584 -=== 2.11.4  Replace the battery ===
549 +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).
585 585  
551 += **3. ​ Access NB-IoT Module** =
586 586  
587 -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).
588 -
589 -
590 -= 3. ​ Access NB-IoT Module =
591 -
592 -
593 593  Users can directly access the AT command set of the NB-IoT module.
594 594  
595 595  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/]] 
596 596  
557 +[[image:image-20221021112006-28.png]] ​
597 597  
598 -[[image:image-20221118094449-6.png]] ​
559 += **4.  Using the AT Commands** =
599 599  
561 +== **4.1  Access AT Commands** ==
600 600  
601 -= 4.  Using the AT Commands =
602 -
603 -== 4.1  Access AT Commands ==
604 -
605 -
606 606  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]]
607 607  
608 608  AT+<CMD>?  : Help on <CMD>
... ... @@ -613,9 +613,8 @@
613 613  
614 614  AT+<CMD>=?  : Get the value
615 615  
573 +**General Commands**      
616 616  
617 -(% style="color:blue" %)**General Commands**      
618 -
619 619  AT  : Attention       
620 620  
621 621  AT?  : Short Help     
... ... @@ -630,107 +630,133 @@
630 630  
631 631  AT+INTMOD            : Set the trigger interrupt mode
632 632  
633 -AT+5VT  : Set extend the time of 5V power  
589 +AT+5VT  : Set extend the time of 5V power  
634 634  
635 -AT+PRO  : Choose agreement
591 +AT+PRO  : Choose agreement
636 636  
637 -AT+RXDL  : Extend the sending and receiving time
593 +AT+RXDL  : Extend the sending and receiving time
638 638  
639 -AT+SERVADDR  : Server Address
595 +AT+SERVADDR  : Server Address
640 640  
641 -AT+TR      :  Get or Set record time
597 +AT+TR      : Get or Set record time"
642 642  
643 -AT+NOUD :  Get or Set the number of data to be uploaded
644 644  
645 -AT+CDP     :  Read or Clear cached data
600 +AT+NOUD      : Get or Set the number of data to be uploaded
646 646  
647 -AT+DEBUG:  Enable or Disable debug mode
648 648  
649 -AT+ALARM1:  Get or Set alarm of distance1
603 +AT+CDP     : Read or Clear cached data
650 650  
651 -AT+ALARM2:  Get or Set alarm of distance2
652 652  
653 -AT+GETSENSORVALUE :  Returns the current sensor measurement
606 +AT+ DEBUG   : Enable or Disable debug mode
654 654  
655 -AT+POWERIC :  Get or set the Power IC flag
608 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
656 656  
610 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
657 657  
658 -(% style="color:blue" %)**COAP Management**      
612 +AT+ CALCFLAG   : Get or Set the calculate flag
659 659  
660 -AT+URI :  Resource parameters
614 +AT+ CLRC   : Clear current door open count
661 661  
616 +**COAP Management**      
662 662  
663 -(% style="color:blue" %)**UDP Management**
618 +AT+URI            : Resource parameters
664 664  
665 -AT+CFM :  Upload confirmation mode (only valid for UDP)
620 +**UDP Management**
666 666  
622 +AT+CFM          : Upload confirmation mode (only valid for UDP)
667 667  
668 -(% style="color:blue" %)**MQTT Management**
624 +**MQTT Management**
669 669  
670 -AT+CLIENT  : Get or Set MQTT client
626 +AT+CLIENT               : Get or Set MQTT client
671 671  
672 -AT+UNAME : Get or Set MQTT Username
628 +AT+UNAME  : Get or Set MQTT Username
673 673  
674 -AT+PWD  :  Get or Set MQTT password
630 +AT+PWD                  : Get or Set MQTT password
675 675  
676 -AT+PUBTOPIC :  Get or Set MQTT publish topic
632 +AT+PUBTOPIC  : Get or Set MQTT publish topic
677 677  
678 -AT+SUBTOPIC :  Get or Set MQTT subscription topic
634 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
679 679  
636 +**Information**          
680 680  
681 -(% style="color:blue" %)**Information**          
638 +AT+FDR  : Factory Data Reset
682 682  
683 -AT+FDR :  Factory Data Reset
640 +AT+PWORD  : Serial Access Password
684 684  
685 -AT+PWORD :  Serial Access Password
642 += **​5.  FAQ** =
686 686  
644 +== **5.1 ​ How to Upgrade Firmware** ==
687 687  
688 -= ​5.  FAQ =
646 +User can upgrade the firmware for 1) bug fix, 2) new feature release.
689 689  
690 -== 5.1 ​ How to Upgrade Firmware ==
648 +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]]
691 691  
650 +**Notice, **CPN01 **and **CPN01 **share the same mother board. They use the same connection and method to update.**
692 692  
693 -User can upgrade the firmware for 1) bug fix, 2) new feature release.
652 +== **5.2  Can I calibrate CPN01 to different soil types?** ==
694 694  
695 -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]]
654 +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]].
696 696  
697 -(% 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.**
656 += **6.  Trouble Shooting** =
698 698  
658 +== **6.1  ​Connection problem when uploading firmware** ==
699 699  
700 -= 6.  Trouble Shooting =
660 +**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]]
701 701  
702 -== 6.1  ​Connection problem when uploading firmware ==
662 +== **6.2  AT Command input doesn't work** ==
703 703  
664 +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.
704 704  
705 -(% 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]]
666 += **7. ​ Order Info** =
706 706  
668 +Part Number**:** CPN01
707 707  
708 -== 6.2  AT Command input doesn't work ==
670 += **8.  Packing Info** =
709 709  
672 +**Package Includes**:
710 710  
711 -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.
674 +* CPN01 NB-IoT Soil Moisture & EC Sensor x 1
675 +* External antenna x 1
712 712  
677 +**Dimension and weight**:
713 713  
714 -= 7. ​ Order Info =
679 +* Size: 195 x 125 x 55 mm
680 +* Weight:   420g
715 715  
682 += **9.  Support** =
716 716  
717 -Part Number:(% style="color:blue" %)** NMDS200**
684 +* 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.
685 +* 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]]
718 718  
687 +​
719 719  
720 -= 8.  Packing Info =
721 721  
722 722  
723 -(% style="color:blue" %)**Package Includes**:
724 724  
725 -* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
726 726  
727 727  
728 728  
729 -= 9.  Support =
730 730  
731 731  
732 -* 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.
733 733  
734 -* 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]]
735 735  
736 -​
699 +
700 +
701 +
702 +
703 +
704 +
705 +
706 +
707 +
708 +
709 +
710 +
711 +
712 +
713 +
714 +
715 +
716 +
717 +
718 +
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-20221022234529-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.3 KB
Content
image-20221022234602-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -135.7 KB
Content
image-20221023000439-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -82.1 KB
Content
image-20221117105556-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -133.3 KB
Content
image-20221117114459-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content
image-20221117114842-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -964.1 KB
Content
image-20221117114937-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.1 KB
Content
image-20221117114949-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -33.4 KB
Content
image-20221117115010-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -40.4 KB
Content
image-20221117142300-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -147.8 KB
Content
image-20221117145932-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -51.9 KB
Content
image-20221117150312-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.7 KB
Content
image-20221118092935-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -13.1 KB
Content
image-20221118093144-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -11.7 KB
Content
image-20221118093512-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -9.5 KB
Content
image-20221118093658-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -12.7 KB
Content
image-20221118094227-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.2 KB
Content
image-20221118094449-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.5 KB
Content
image-20221118103445-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -20.4 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.5 KB
Content
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