Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 88.1 >
edited by Xiaoling
on 2022/12/09 09:09
To version < 53.1 >
edited by Xiaoling
on 2022/11/17 10:55
>
Change comment: Uploaded new attachment "image-20221117105556-1.png", version {1}

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
1 +NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
Content
... ... @@ -1,7 +1,8 @@
1 1  (% style="text-align:center" %)
2 -[[image:LMDS200_10.jpg]]
2 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/WebHome/1652856952171-363.png?rev=1.1||alt="1652856952171-363.png" height="578" width="588"]]
3 3  
4 4  
5 +
5 5  **Table of Contents：**
6 6  
7 7  {{toc/}}
... ... @@ -9,51 +9,47 @@
9 9  
10 10  
11 11  
13 +
12 12  = 1.  Introduction =
13 13  
14 -== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
15 15  
17 +== 1.1 ​ What is CPN01 NB-IoT Pulse/Contact Sensor ==
16 16  
17 -(((
18 -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.
19 -)))
20 20  
21 21  (((
22 -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.
23 23  )))
24 24  
25 25  (((
26 -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.
27 27  )))
28 28  
29 29  (((
30 -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.
31 31  )))
32 32  
33 33  (((
34 -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.
35 35  )))
36 36  
37 37  (((
38 -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.
39 39  )))
40 40  
41 -(((
42 -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)
43 -)))
43 +​
44 44  
45 -(((
46 -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.
47 -)))
48 48  
49 -
50 50  == ​1.2  Features ==
51 51  
52 52  
53 53  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
54 -* Short uplink interval for Distance Alarm
50 +* Open/Close detect
51 +* Open/Close statistics
55 55  * Monitor Battery Level
56 -* Microwave Radar for distance detection
53 +* Uplink on periodically and open/close event
57 57  * Datalog feature
58 58  * Uplink periodically
59 59  * Downlink to change configure
... ... @@ -66,108 +66,136 @@
66 66  
67 67  
68 68  
69 -== 1.3 Radar probe specification ==
66 +== 1.3  Specification ==
70 70  
71 71  
72 -* Measuring Method: FMCW
73 -* Frequency: 24.000 ~~ 24.500 GHz
74 -* Measurement output power: 6dBm
75 -* Measure range: 0.5 ~~ 20m
76 -* Accuracy: ±0.1m
77 -* Resolution: 0.01m
78 -* Horizontal Angel: 78°
79 -* Vertical Angel: 23°
69 +(% style="color:blue" %)**Common DC Characteristics:**
80 80  
71 +* Supply Voltage: 2.1v ~~ 3.6v
72 +* Operating Temperature: -40 ~~ 85°C
81 81  
74 +(% style="color:blue" %)**NB-IoT Spec:**
82 82  
83 -== 1.4  Storage Temperature ==
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
84 84  
85 85  
86 - -40°C to +85°C
87 87  
85 +== 1.4  Installation ==
88 88  
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 +
89 89  == 1.5 ​ Applications ==
90 90  
91 91  
92 -* Horizontal distance measurement
93 -* Liquid level measurement
94 -* Parking management system
95 -* Object proximity and presence detection
96 -* Intelligent trash can management system
97 -* Robot obstacle avoidance
98 -* Automatic control
99 -* Sewer
100 -* Bottom water level monitoring
100 +* Open/Close Detection
101 +* Pulse meter application
102 +* Dry Contact Detection
101 101  
102 102  
103 103  
104 -== 1.6  Specification ==
106 +== 1.6  Mechanical ==
105 105  
106 106  
107 -(% style="color:blue" %)**Common DC Characteristics:**
109 +​[[image:image-20221021110415-3.png]]
108 108  
109 -* Supply Voltage: 2.1v ~~ 3.6v
110 -* Operating Temperature: 0 ~~ 70°C
111 111  
112 -(% style="color:blue" %)**NB-IoT Spec:**
113 113  
114 -* B1 @H-FDD: 2100MHz
115 -* B3 @H-FDD: 1800MHz
116 -* B8 @H-FDD: 900MHz
117 -* B5 @H-FDD: 850MHz
118 -* B20 @H-FDD: 800MHz
119 -* B28 @H-FDD: 700MHz
113 +== 1.7  Pin Definitions and Switch ==
120 120  
121 121  
116 +[[image:image-20221021110429-4.png]]
122 122  
123 -== 1.7  Installation ==
124 124  
119 +=== 1.7.1  Pin Definition ===
125 125  
126 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
127 127  
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]]**.
128 128  
129 -[[image:image-20221207170748-1.png]]
130 130  
131 131  
132 - [[image:image-20221207170748-2.png||height="345" width="634"]]
126 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
133 133  
134 134  
129 +Power on Device when putting this jumper.
135 135  
136 -== 1.8  Pin Definitions and Switch ==
137 137  
138 138  
139 -[[image:1670404362039-351.png]]
133 +=== 1.7.3  BOOT MODE / SW1 ===
140 140  
141 141  
142 -= 2.  Use NMDS200 to communicate with IoT Server =
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.
143 143  
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 +
144 144  == 2.1  How it works ==
145 145  
146 146  
147 -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.
148 148  
149 -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:
150 150  
151 -[[image:image-20221021110615-5.png||height="996" width="492"]]
170 +[[image:image-20221021110615-5.png]]
152 152  
153 153  
154 -== 2.2 ​ Configure NMDS200 ==
155 155  
174 +== 2.2 ​ Configure CPN01 ==
156 156  
157 -To use NMDS200 in your city, make sure to meet below requirements:
158 158  
177 +=== 2.2.1 Test Requirement ===
178 +
179 +
180 +To use CPN01 in your city, make sure to meet below requirements:
181 +
159 159  * Your local operator has already distributed an NB-IoT Network.
160 -* The local NB-IoT network used the band that NMDS200 supports.
183 +* The local NB-IoT network used the band that CPN01 supports.
161 161  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
162 162  
163 -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.
164 164  
165 -[[image:image-20221208090742-1.png]]
188 +[[image:image-20221023000439-3.png]]
166 166  
190 + ​
167 167  
168 -=== 2.2.1 Insert NB-IoT SIM card ===
169 169  
193 +=== 2.2.2 Insert NB-IoT SIM card ===
170 170  
195 +
171 171  Insert the NB-IoT Card get from your provider.
172 172  
173 173  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -175,11 +175,12 @@
175 175  [[image:image-20221021110745-6.png]] ​
176 176  
177 177  
178 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
179 179  
204 +=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
180 180  
181 -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.
182 182  
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 +
183 183  (% style="color:blue" %)**Connection:**
184 184  
185 185  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -201,23 +201,24 @@
201 201  
202 202  * Flow Control: (% style="color:red" %)**None**
203 203  
204 -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**(%%).
205 205  
206 206  ​[[image:image-20221021110817-7.png]]
207 207  
208 -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.
209 209  
210 210  
211 211  (% 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]]
212 212  
213 213  
214 -=== 2.2.3 Use CoAP protocol to uplink data ===
215 215  
241 +=== 2.2.4 Use CoAP protocol to uplink data ===
216 216  
243 +
217 217  (% 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/]]
218 218  
219 219  
220 -(% style="color:blue" %)**Use below commands in NMDS200:**
247 +(% style="color:blue" %)**Use below commands in CPN01:**
221 221  
222 222  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
223 223  
... ... @@ -227,17 +227,18 @@
227 227  
228 228  For parameter description, please refer to AT command set
229 229  
230 -[[image:1670471530120-960.png||height="647" width="674"]]
257 +[[image:image-20221021110948-8.png]]
231 231  
232 232  
233 -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.
234 234  
235 -[[image:1670405841875-916.png]] ​
262 +[[image:image-20221021110956-9.png]] ​
236 236  
237 237  
238 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
239 239  
266 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
240 240  
268 +
241 241  (% style="color:blue" %)**AT Commands:**
242 242  
243 243  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
... ... @@ -246,7 +246,7 @@
246 246  
247 247  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
248 248  
249 -​ [[image:1670471559211-638.png]]
277 +​ [[image:image-20221021111025-10.png]]
250 250  
251 251  
252 252  [[image:image-20221021111033-11.png||height="241" width="576"]]
... ... @@ -253,9 +253,10 @@
253 253  
254 254  ​
255 255  
256 -=== 2.2.5 Use MQTT protocol to uplink data ===
257 257  
285 +=== 2.2.6 Use MQTT protocol to uplink data ===
258 258  
287 +
259 259  (% style="color:blue" %)**AT Commands:**
260 260  
261 261  * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
... ... @@ -272,10 +272,10 @@
272 272  
273 273  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
274 274  
275 -​ ​​​​​​​[[image:1670471584490-640.png]]
304 +​ [[image:image-20221021111058-12.png]]
276 276  
277 277  
278 -[[image:1670405928926-116.png]]
307 +[[image:image-20221021111201-16.png||height="472" width="653"]]
279 279  
280 280  ​
281 281  
... ... @@ -282,9 +282,10 @@
282 282  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.
283 283  
284 284  
285 -=== 2.2.6 Use TCP protocol to uplink data ===
286 286  
315 +=== 2.2.7 Use TCP protocol to uplink data ===
287 287  
317 +
288 288  (% style="color:blue" %)**AT Commands:**
289 289  
290 290  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
... ... @@ -291,76 +291,83 @@
291 291  
292 292  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
293 293  
294 -​ ​​​​​​​[[image:1670471613823-833.png]]
324 +​ [[image:image-20221021111125-14.png]]
295 295  
296 -
297 297  [[image:image-20221021111131-15.png]]
298 298  
299 299  ​
300 300  
301 -=== 2.2.7 Change Update Interval ===
302 302  
331 +=== 2.2.8 Change Update Interval ===
303 303  
333 +
304 304  User can use below command to change the (% style="color:blue" %)**uplink interval**.
305 305  
306 -* (% 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)
307 307  
308 308  (% style="color:red" %)**NOTE:**
309 309  
310 -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.
311 311  
312 312  
343 +
313 313  == 2.3  Uplink Payload ==
314 314  
315 315  
316 -The uplink payload includes 23 bytes in total by default.
347 +The uplink payload includes 123 bytes in total by default.
317 317  
318 -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.
319 319  
320 320  
321 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:450px" %)
322 -|=(% 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**
323 -|=(% 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"]]
324 324  
325 -(% border="1" style="background-color:#ffffcc; color:green; width:429px" %)
326 -|(% style="width:60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)(((
327 -**1-32 group**
328 -)))
329 -|(% 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" %)...
330 330  
331 -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.
332 332  
333 -[[image:1670406261143-723.png]]
362 +[[image:image-20221021111201-16.png||height="572" width="792"]]
334 334  
335 335  
336 -The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
365 +The payload is ASCII string, representative same HEX:
337 337  
338 -**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__(%%)**
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 __**
339 339  
340 340  **where:**
341 341  
342 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
371 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
343 343  
344 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
373 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
345 345  
346 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
375 +* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
347 347  
348 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
377 +* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
349 349  
350 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
379 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
351 351  
352 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
381 +* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
353 353  
354 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
383 +* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
355 355  
356 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
385 +* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
357 357  
358 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
387 +* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
359 359  
389 +* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
360 360  
391 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
361 361  
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 +
362 362  == 2.4  Payload Explanation and Sensor Interface ==
363 363  
400 +
364 364  === 2.4.1  Device ID ===
365 365  
366 366  
... ... @@ -375,18 +375,20 @@
375 375  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
376 376  
377 377  
415 +
378 378  === 2.4.2  Version Info ===
379 379  
380 380  
381 381  Specify the software version: 0x64=100, which means firmware version 1.00.
382 382  
383 -For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
421 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
384 384  
385 385  
424 +
386 386  === 2.4.3  Battery Info ===
387 387  
388 388  
389 -Check the battery voltage for NMDS200.
428 +Check the battery voltage for CPN01.
390 390  
391 391  Ex1: 0x0B45 = 2885mV
392 392  
... ... @@ -393,54 +393,89 @@
393 393  Ex2: 0x0B49 = 2889mV
394 394  
395 395  
435 +
396 396  === 2.4.4  Signal Strength ===
397 397  
398 398  
399 399  NB-IoT Network signal Strength.
400 400  
401 -(% style="color:blue" %)**Ex1: 0x1d = 29**
441 +**Ex1: 0x1d = 29**
402 402  
403 -(% style="color:#037691" %)**0** (%%) -113dBm or less
443 +**0**  -113dBm or less
404 404  
405 -(% style="color:#037691" %)**1**  (%%) -111dBm
445 +**1**  -111dBm
406 406  
407 -(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
447 +**2...30** -109dBm... -53dBm
408 408  
409 -(% style="color:#037691" %)**31** (%%) -51dBm or greater
449 +**31**   -51dBm or greater
410 410  
411 -(% style="color:#037691" %)**99** (%%) Not known or not detectable
451 +**99**    Not known or not detectable
412 412  
413 413  
414 -=== 2.4.5  Distance ===
415 415  
455 +=== 2.4.5  Calculate Flag ===
416 416  
417 -[[image:1670407401682-959.png]]
418 418  
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.
419 419  
420 -(% 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.
421 421  
422 -Distance between sensor probe to the first object. (unit: cm)
462 +Default value: 0. 
423 423  
424 -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
425 425  
426 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
427 427  
428 428  
429 -(% style="color:blue" %)**Object2 Distance:**
468 +=== 2.4.6  Alarm ===
430 430  
431 -Distance between sensor probe to the second object. (unit: cm)
432 432  
471 +See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
433 433  
434 -=== 2.4.6  Timestamp ===
435 435  
436 436  
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 +
437 437  Timestamp : 0x6315537b =1662342011
438 438  
509 +Convert Unix timestamp to time 2022-9-5 9:40:11.
439 439  
511 +**~ **
512 +
513 +
440 440  == 2.5  Downlink Payload ==
441 441  
442 442  
443 -By default, NMDS200 prints the downlink payload to console port.
517 +By default, CPN01 prints the downlink payload to console port.
444 444  
445 445  [[image:image-20221021111414-18.png]] ​
446 446  
... ... @@ -457,7 +457,7 @@
457 457  
458 458  * (% style="color:#037691" %)**Reset**
459 459  
460 -If payload = 0x04FF, it will reset the NMDS200
534 +If payload = 0x04FF, it will reset the NSE01
461 461  
462 462  * (% style="color:#037691" %)**INTMOD**
463 463  
... ... @@ -464,47 +464,116 @@
464 464  Downlink Payload: 06000003, Set AT+INTMOD=3
465 465  
466 466  
541 +
467 467  == 2.6  ​LED Indicator ==
468 468  
469 469  
470 -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.
471 471  
472 472  * When the device starts normally, the LED will light up for 1 second.
473 -* 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.
474 474  * For each uplink probe, LED will be on for 500ms.
475 475  
476 476  
552 +== 2.7  Alarm Base on Timeout ==
477 477  
478 -== 2.7  Distance alarm function ==
479 479  
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:
480 480  
481 -(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
482 482  
483 -(% style="color:#037691" %)**Example 1:**
558 +(% style="color:blue" %)**1. Keep Status: Status to be monitor**
484 484  
485 -AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
560 +Keep Status = 1: Monitor Close to Open event
486 486  
487 -AT+ ALARM2 =min,max
562 +Keep Status = 0: Monitor Open to Close event
488 488  
489 489  
490 -(% style="color:#037691" %)**Example 2:**
565 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
491 491  
492 -AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
567 +Range 0 ~~ 65535(0xFFFF) seconds.
493 493  
569 +If keep time = 0, Disable Alarm Base on Timeout feature.
494 494  
495 -== 2.8  Set the number of data to be uploaded and the recording time ==
571 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
496 496  
497 497  
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 +
498 498  (% style="color:blue" %)**AT Command:**
499 499  
500 -(% 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)
501 501  
502 -(% 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.
503 503  
504 504  
505 -== 2.9  Read or Clear cached data ==
506 506  
648 +== 2.14  Read or Clear cached data ==
507 507  
650 +
508 508  (% style="color:blue" %)**AT Command:**
509 509  
510 510  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -511,24 +511,27 @@
511 511  
512 512  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
513 513  
514 -[[image:1670408172929-569.png]]
657 +[[image:image-20221021111810-25.png||height="364" width="797"]]
515 515  
516 516  
517 -== 2.10  ​Firmware Change Log ==
518 518  
661 +== 2.15  ​Firmware Change Log ==
519 519  
520 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
521 521  
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 +
522 522  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
523 523  
524 524  
525 -== 2.11  ​Battery Analysis ==
526 526  
527 -=== 2.11.1  ​Battery Type ===
670 +== 2.16  ​Battery Analysis ==
528 528  
529 529  
530 -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.
673 +=== 2.16.1  ​Battery Type ===
531 531  
675 +
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 +
532 532  The battery is designed to last for several years depends on the actual use environment and update interval. 
533 533  
534 534  The battery-related documents as below:
... ... @@ -542,9 +542,10 @@
542 542  [[image:image-20221021111911-26.png]] ​
543 543  
544 544  
545 -=== 2.11.2  Power consumption Analyze ===
546 546  
692 +=== 2.16.2  Power consumption Analyze ===
547 547  
694 +
548 548  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.
549 549  
550 550  Instruction to use as below:
... ... @@ -564,18 +564,21 @@
564 564  [[image:1666596205057-567.png]] ​
565 565  
566 566  
567 -=== 2.11.3  ​Battery Note ===
568 568  
715 +=== 2.16.3  ​Battery Note ===
569 569  
717 +
570 570  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.
571 571  
572 572  
573 -=== 2.11.4  Replace the battery ===
574 574  
722 +=== 2.16.4  Replace the battery ===
575 575  
576 -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).
577 577  
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).
578 578  
727 +
728 +
579 579  = 3. ​ Access NB-IoT Module =
580 580  
581 581  
... ... @@ -583,12 +583,13 @@
583 583  
584 584  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/]] 
585 585  
736 +[[image:image-20221021112006-28.png]] ​
586 586  
587 -[[image:image-20221118094449-6.png]] ​
588 588  
589 589  
590 590  = 4.  Using the AT Commands =
591 591  
742 +
592 592  == 4.1  Access AT Commands ==
593 593  
594 594  
... ... @@ -619,63 +619,65 @@
619 619  
620 620  AT+INTMOD            : Set the trigger interrupt mode
621 621  
622 -AT+5VT  : Set extend the time of 5V power  
773 +AT+5VT  : Set extend the time of 5V power  
623 623  
624 -AT+PRO  : Choose agreement
775 +AT+PRO  : Choose agreement
625 625  
626 -AT+RXDL  : Extend the sending and receiving time
777 +AT+RXDL  : Extend the sending and receiving time
627 627  
628 -AT+SERVADDR  : Server Address
779 +AT+SERVADDR  : Server Address
629 629  
630 -AT+TR      :  Get or Set record time
781 +AT+TR      :  Get or Set record time
631 631  
632 -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
633 633  
634 634  AT+CDP     :  Read or Clear cached data
635 635  
636 -AT+DEBUG:  Enable or Disable debug mode
787 +AT+ DEBUG   : Enable or Disable debug mode
637 637  
638 -AT+ALARM1:  Get or Set alarm of distance1
789 +AT+ TTRIG   : Get or Set Alarm Base on Timeout
639 639  
640 -AT+ALARM2:  Get or Set alarm of distance2
791 +AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
641 641  
642 -AT+GETSENSORVALUE :  Returns the current sensor measurement
793 +AT+ CALCFLAG   : Get or Set the calculate flag
643 643  
644 -AT+POWERIC :  Get or set the Power IC flag
795 +AT+ CLRC   : Clear current door open count
645 645  
646 646  
647 647  (% style="color:blue" %)**COAP Management**      
648 648  
649 -AT+URI :  Resource parameters
800 +AT+URI            : Resource parameters
650 650  
651 651  
652 652  (% style="color:blue" %)**UDP Management**
653 653  
654 -AT+CFM :  Upload confirmation mode (only valid for UDP)
805 +AT+CFM          : Upload confirmation mode (only valid for UDP)
655 655  
656 656  
657 657  (% style="color:blue" %)**MQTT Management**
658 658  
659 -AT+CLIENT  : Get or Set MQTT client
810 +AT+CLIENT               : Get or Set MQTT client
660 660  
661 -AT+UNAME : Get or Set MQTT Username
812 +AT+UNAME  : Get or Set MQTT Username
662 662  
663 -AT+PWD  :  Get or Set MQTT password
814 +AT+PWD                  : Get or Set MQTT password
664 664  
665 -AT+PUBTOPIC :  Get or Set MQTT publish topic
816 +AT+PUBTOPIC  : Get or Set MQTT publish topic
666 666  
667 -AT+SUBTOPIC :  Get or Set MQTT subscription topic
818 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
668 668  
669 669  
670 670  (% style="color:blue" %)**Information**          
671 671  
672 -AT+FDR :  Factory Data Reset
823 +AT+FDR  : Factory Data Reset
673 673  
674 -AT+PWORD :  Serial Access Password
825 +AT+PWORD  : Serial Access Password
675 675  
676 676  
828 +
677 677  = ​5.  FAQ =
678 678  
831 +
679 679  == 5.1 ​ How to Upgrade Firmware ==
680 680  
681 681  
... ... @@ -683,11 +683,13 @@
683 683  
684 684  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]]
685 685  
686 -(% 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.**
687 687  
688 688  
842 +
689 689  = 6.  Trouble Shooting =
690 690  
845 +
691 691  == 6.1  ​Connection problem when uploading firmware ==
692 692  
693 693  
... ... @@ -694,6 +694,7 @@
694 694  (% 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]]
695 695  
696 696  
852 +
697 697  == 6.2  AT Command input doesn't work ==
698 698  
699 699  
... ... @@ -700,21 +700,29 @@
700 700  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.
701 701  
702 702  
859 +
703 703  = 7. ​ Order Info =
704 704  
705 705  
706 -Part Number:(% style="color:blue" %)** NMDS200**
863 +Part Number**:** CPN01
707 707  
708 708  
866 +
709 709  = 8.  Packing Info =
710 710  
711 711  
712 712  (% style="color:blue" %)**Package Includes**:
713 713  
714 -* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
872 +* CPN01 Open/Close Sensor x 1
873 +* External antenna x 1
715 715  
875 +(% style="color:blue" %)**Dimension and weight**:
716 716  
877 +* Size: 195 x 125 x 55 mm
878 +* Weight:   420g
717 717  
880 +
881 +
718 718  = 9.  Support =
719 719  
720 720  
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-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

Applications

Navigation

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