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