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