Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 61.3 >
edited by Xiaoling
on 2022/11/17 16:39
To version < 83.5 >
edited by Xiaoling
on 2022/12/08 09:52
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
1 +NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
Content
... ... @@ -1,14 +1,10 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20221117105556-1.png]]
2 +[[image:LMDS200_10.jpg]]
3 3  
4 4  
5 -
6 -
7 -
8 -
9 -
10 10  **Table of Contents：**
11 11  
7 +{{toc/}}
12 12  
13 13  
14 14  
... ... @@ -15,51 +15,35 @@
15 15  
16 16  = 1.  Introduction =
17 17  
18 -== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
14 +== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
19 19  
20 20  
21 21  (((
22 -The Dragino NDS03A is an (% style="color:blue" %)**Open/Close NB-IoT Door Sensor**(%%). It detects door (% style="color:blue" %)**open/close status**(%%) and (% style="color:blue" %)**uplinks**(%%) to IoT server via NB-IoT network. NDS03A can connect two door sensors. user can see the door status, open duration, open counts in the IoT Server.
23 -)))
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.
24 24  
25 -(((
26 -The NDS03A will send periodically data (% style="color:blue" %)**every 4 hours** (%%)as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically.
27 -)))
20 +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.
28 28  
29 -(((
30 -NDS03A has a (% style="color:blue" %)**Datalog feature**(%%), it will record the open/close event and the user can retrieve the history from NB-IoT.
31 -)))
22 +NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
32 32  
33 -(((
34 -NDS03A has the(% style="color:blue" %)**open alarm feature**(%%), user can set this feature so the device will send an alarm if the door has been open for a certain time.
35 -)))
24 +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.
36 36  
37 -(((
38 -NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
39 -)))
26 +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.
40 40  
41 -(((
42 -NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technologyTCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
43 -)))
28 +NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
44 44  
45 -(((
46 -NDS03A 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)
47 -)))
30 +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)
48 48  
49 -(((
50 -To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into NDS03A to get NB-IoT network connection.
32 +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.
51 51  )))
52 52  
53 53  
54 -
55 55  == ​1.2  Features ==
56 56  
57 57  
58 58  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
59 -* Open/Close detect
60 -* Open/Close statistics
40 +* Short uplink interval for Distance Alarm
61 61  * Monitor Battery Level
62 -* connect two door sensors
42 +* Microwave Radar for distance detection
63 63  * Datalog feature
64 64  * Uplink periodically
65 65  * Downlink to change configure
... ... @@ -70,32 +70,37 @@
70 70  * Micro SIM card slot for NB-IoT SIM
71 71  * 8500mAh Battery for long-term use
72 72  
73 -== 1.3  Storage & Operation ==
53 +== 1.3 Radar probe specification ==
74 74  
75 75  
76 -Temperature -40°C to +85°C
56 +* Measuring Method: FMCW
57 +* Frequency: 24.000 24.500 GHz
58 +* Measurement output power: 6dBm
59 +* Measure range: 0.5 20m
60 +* Accuracy: ±0.1m
61 +* Resolution: 0.01m
62 +* Horizontal Angel: 78°
63 +* Vertical Angel: 23°
77 77  
65 +== 1.4  Storage Temperature ==
78 78  
79 -== 1.4  Mechanical ==
80 80  
68 + -40°C to +85°C
81 81  
82 -[[image:image-20221117114937-4.png]]
83 83  
84 -
85 -[[image:image-20221117114949-5.png]]
86 -
87 -
88 -[[image:image-20221117115010-6.png]]
89 -
90 -
91 -
92 92  == 1.5 ​ Applications ==
93 93  
94 94  
95 -[[image:image-20221117114842-3.png]]
74 +* Horizontal distance measurement
75 +* Liquid level measurement
76 +* Parking management system
77 +* Object proximity and presence detection
78 +* Intelligent trash can management system
79 +* Robot obstacle avoidance
80 +* Automatic control
81 +* Sewer
82 +* Bottom water level monitoring
96 96  
97 -
98 -
99 99  == 1.6  Specification ==
100 100  
101 101  
... ... @@ -102,107 +102,62 @@
102 102  (% style="color:blue" %)**Common DC Characteristics:**
103 103  
104 104  * Supply Voltage: 2.1v ~~ 3.6v
105 -* Operating Temperature: -40 ~~ 85°C
90 +* Operating Temperature: 0 ~~ 70°C
106 106  
107 107  (% style="color:blue" %)**NB-IoT Spec:**
108 108  
109 -* - B1 @H-FDD: 2100MHz
110 -* - B3 @H-FDD: 1800MHz
111 -* - B8 @H-FDD: 900MHz
112 -* - B5 @H-FDD: 850MHz
113 -* - B20 @H-FDD: 800MHz
114 -* - B28 @H-FDD: 700MHz
94 +* B1 @H-FDD: 2100MHz
95 +* B3 @H-FDD: 1800MHz
96 +* B8 @H-FDD: 900MHz
97 +* B5 @H-FDD: 850MHz
98 +* B20 @H-FDD: 800MHz
99 +* B28 @H-FDD: 700MHz
115 115  
116 -== 1.7  Pin Definitions and Switch ==
101 +== 1.7  Installation ==
117 117  
118 118  
119 -[[image:image-20221021110429-4.png]]
104 +Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
120 120  
121 121  
122 -=== 1.7.1  Pin Definition ===
107 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
123 123  
124 124  
125 -The device is pre-configured to connect to a door sensor. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at:  [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]
126 126  
111 +== 1.8  Pin Definitions and Switch ==
127 127  
128 128  
129 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
114 +[[image:1670404362039-351.png]]
130 130  
131 131  
132 -Power on Device when putting this jumper.
117 += 2.  Use NMDS200 to communicate with IoT Server =
133 133  
134 -
135 -
136 -=== 1.7.3  BOOT MODE / SW1 ===
137 -
138 -
139 -1)  ISP:  upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run.
140 -
141 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
142 -
143 -
144 -
145 -=== 1.7.4  Reset Button ===
146 -
147 -
148 -Press to reboot the device.
149 -
150 -
151 -
152 -=== 1.7.5  LED ===
153 -
154 -
155 -The LED will blink when :
156 -
157 -1.  Boot the device in flash mode
158 -
159 -2.  Send an uplink packet
160 -
161 -
162 -
163 -== 1.8  Magnet Distance ==
164 -
165 -
166 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
167 -
168 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
169 -
170 -
171 -
172 -= 2.  Use CPN01 to communicate with IoT Server =
173 -
174 174  == 2.1  How it works ==
175 175  
176 176  
177 -In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A.
122 +The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
178 178  
179 -The diagram below shows the working flow in the default firmware of NDS03A:
124 +The diagram below shows the working flow in the default firmware of NMDS200:
180 180  
181 181  [[image:image-20221021110615-5.png]]
182 182  
183 183  
129 +== 2.2 ​ Configure NMDS200 ==
184 184  
185 -== 2.2 ​ Configure NDS03A ==
186 186  
187 -=== 2.2.1 Test Requirement ===
132 +To use NMDS200 in your city, make sure to meet below requirements:
188 188  
189 -
190 -To use NDS03A in your city, make sure to meet below requirements:
191 -
192 192  * Your local operator has already distributed an NB-IoT Network.
193 -* The local NB-IoT network used the band that NDS03A supports.
135 +* The local NB-IoT network used the band that NMDS200 supports.
194 194  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
195 195  
196 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDS03A 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.
138 +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.
197 197  
198 -[[image:image-20221117142300-1.png]]
140 +[[image:image-20221208090742-1.png]]
199 199  
200 - ​
201 201  
143 +=== 2.2.1 Insert NB-IoT SIM card ===
202 202  
203 -=== 2.2.2 Insert NB-IoT SIM card ===
204 204  
205 -
206 206  Insert the NB-IoT Card get from your provider.
207 207  
208 208  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -210,12 +210,11 @@
210 210  [[image:image-20221021110745-6.png]] ​
211 211  
212 212  
153 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
213 213  
214 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
215 215  
156 +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.
216 216  
217 -User need to configure NDS03A via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USB to TTL adapter to connect to NDS03A and use AT Commands to configure it, as below.
218 -
219 219  (% style="color:blue" %)**Connection:**
220 220  
221 221  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -237,11 +237,11 @@
237 237  
238 238  * Flow Control: (% style="color:red" %)**None**
239 239  
240 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
179 +Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
241 241  
242 242  ​[[image:image-20221021110817-7.png]]
243 243  
244 -NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
183 +NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
245 245  
246 246  
247 247  (% 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]]
... ... @@ -248,13 +248,13 @@
248 248  
249 249  
250 250  
251 -=== 2.2.4 Use CoAP protocol to uplink data ===
190 +=== 2.2.3 Use CoAP protocol to uplink data ===
252 252  
253 253  
254 254  (% 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/]]
255 255  
256 256  
257 -(% style="color:blue" %)**Use below commands in CPN01:**
196 +(% style="color:blue" %)**Use below commands in NMDS200:**
258 258  
259 259  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
260 260  
... ... @@ -267,15 +267,14 @@
267 267  [[image:image-20221021110948-8.png]]
268 268  
269 269  
270 -After configuring the server address and (% style="color:green" %)**reset CPN01**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
209 +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.
271 271  
272 -[[image:image-20221021110956-9.png]] ​
211 +[[image:1670405841875-916.png]] ​
273 273  
274 274  
214 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
275 275  
276 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
277 277  
278 -
279 279  (% style="color:blue" %)**AT Commands:**
280 280  
281 281  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
... ... @@ -291,10 +291,9 @@
291 291  
292 292  ​
293 293  
232 +=== 2.2.5 Use MQTT protocol to uplink data ===
294 294  
295 -=== 2.2.6 Use MQTT protocol to uplink data ===
296 296  
297 -
298 298  (% style="color:blue" %)**AT Commands:**
299 299  
300 300  * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
... ... @@ -311,10 +311,10 @@
311 311  
312 312  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
313 313  
314 -​ [[image:image-20221021111058-12.png]]
251 +​ [[image:image-20221118103445-7.png]]
315 315  
316 316  
317 -[[image:image-20221021111201-16.png||height="472" width="653"]]
254 +[[image:1670405928926-116.png]]
318 318  
319 319  ​
320 320  
... ... @@ -321,10 +321,9 @@
321 321  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.
322 322  
323 323  
261 +=== 2.2.6 Use TCP protocol to uplink data ===
324 324  
325 -=== 2.2.7 Use TCP protocol to uplink data ===
326 326  
327 -
328 328  (% style="color:blue" %)**AT Commands:**
329 329  
330 330  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
... ... @@ -331,19 +331,19 @@
331 331  
332 332  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
333 333  
334 -​ [[image:image-20221021111125-14.png]]
270 +​ [[image:1670406036256-101.png||height="676" width="713"]]
335 335  
272 +
336 336  [[image:image-20221021111131-15.png]]
337 337  
338 338  ​
339 339  
277 +=== 2.2.7 Change Update Interval ===
340 340  
341 -=== 2.2.8 Change Update Interval ===
342 342  
343 -
344 344  User can use below command to change the (% style="color:blue" %)**uplink interval**.
345 345  
346 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
282 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
347 347  
348 348  (% style="color:red" %)**NOTE:**
349 349  
... ... @@ -350,81 +350,57 @@
350 350  1.  By default, the device will send an uplink message every 4 hour.
351 351  
352 352  
353 -
354 354  == 2.3  Uplink Payload ==
355 355  
356 356  
357 -The uplink payload includes 26 bytes in total by default.
292 +The uplink payload includes 23 bytes in total by default.
358 358  
359 359  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.
360 360  
361 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
362 362  
363 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)
364 -|=(% scope="row" style="width: 93px;" %)**Size(bytes)**|(% style="width:67px" %)**8**|(% style="width:40px" %)**2**|(% style="width:45px" %)**2**|(% style="width:75px" %)**1**|(% style="width:54px" %)**1**|(% style="width:62px" %)**1**|(% style="width:60px" %)**1**|(% style="width:94px" %)**3**|(% style="width:93px" %)**3**
365 -|=(% 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" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.4.6A0Alarm"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
297 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
298 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:90px" %)**2**|(% style="width:100px" %)**2**
299 +|=(% 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.5A0A0Distance"]] |(% style="width:93px" %) [[Distance  2>>||anchor="H2.4.5A0A0Distance"]]
366 366  
367 -(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
368 -|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)(((
301 +(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
302 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
369 369  **1-32 group**
370 370  )))
371 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% style="width:115px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)|(% style="width:99px" %)last open time(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
305 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
372 372  
307 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
373 373  
374 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
309 +[[image:1670406261143-723.png]]
375 375  
376 376  
377 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
378 -|=(% scope="row" style="width: 96px;" %)**Size(bytes)**|(% style="width:66px" %)**8**|(% style="width:40px" %)**2**|(% style="width:46px" %)**2**|(% style="width:70px" %)**1**|(% style="width:54px" %)**1**|(% style="width:55px" %)**1**|(% style="width:57px" %)**1**|(% style="width:86px" %)**3**|(% style="width:82px" %)**3**
379 -|=(% style="width: 96px;" %)**Value**|(% style="width:66px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:70px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:55px" %)Door Status|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.4.6A0Alarm"]]|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
312 +The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
380 380  
381 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
382 -|(% style="width:59px" %)**1**|(% style="width:67px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:66px" %)**1**|(% style="width:92px" %)**3**
383 -|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPN01-%20NB-IoT%20Outdoor%20OpenClose%20Dry%20Contact%20Sensor%C2%A0User%20Manual/#H2.4.7A0ContactStatus]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)Time stamp|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
314 +**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__(%%)**
384 384  
385 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
386 -|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)(((
387 -**1-32 group**
388 -)))
389 -|(% style="width:102px" %)last open time (pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:88px" %)last open time(pb15)|(% style="width:63px" %)Time stamp|(% style="width:87px" %)...
390 -
391 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
392 -
393 -[[image:image-20221117145932-2.png]]
394 -
395 -
396 -The payload is ASCII string, representative same HEX:
397 -
398 -**0x **f867787050213317  0064  0ccf 19 01 00 00 000016 000017 637590df
399 -
400 -**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0ccf__(% style="color:#00b0f0" %) __19__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__(% style="color:#660066" %) (% style="color:#aaaa40" %)__000016__(% style="color:#663300" %) __000017__ (% style="color:#d60093" %)__637590df__(%%)**
401 -
402 402  **where:**
403 403  
404 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
318 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
405 405  
406 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
320 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
407 407  
408 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
322 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
409 409  
410 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
324 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
411 411  
412 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
326 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
413 413  
414 -* (% style="color:#037691" %)**Door Status:**(%%) 0x00=0
328 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
415 415  
416 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
330 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
417 417  
418 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
332 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
419 419  
420 -* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23
334 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
421 421  
422 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
423 423  
424 424  
425 425  == 2.4  Payload Explanation and Sensor Interface ==
426 426  
427 -
428 428  === 2.4.1  Device ID ===
429 429  
430 430  
... ... @@ -439,20 +439,18 @@
439 439  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
440 440  
441 441  
442 -
443 443  === 2.4.2  Version Info ===
444 444  
445 445  
446 446  Specify the software version: 0x64=100, which means firmware version 1.00.
447 447  
448 -For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
359 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
449 449  
450 450  
451 -
452 452  === 2.4.3  Battery Info ===
453 453  
454 454  
455 -Check the battery voltage for CPN01.
365 +Check the battery voltage for NMDS200.
456 456  
457 457  Ex1: 0x0B45 = 2885mV
458 458  
... ... @@ -459,89 +459,54 @@
459 459  Ex2: 0x0B49 = 2889mV
460 460  
461 461  
462 -
463 463  === 2.4.4  Signal Strength ===
464 464  
465 465  
466 466  NB-IoT Network signal Strength.
467 467  
468 -**Ex1: 0x1d = 29**
377 +(% style="color:blue" %)**Ex1: 0x1d = 29**
469 469  
470 -**0**  -113dBm or less
379 +(% style="color:#037691" %)**0** (%%) -113dBm or less
471 471  
472 -**1**  -111dBm
381 +(% style="color:#037691" %)**1**  (%%) -111dBm
473 473  
474 -**2...30** -109dBm... -53dBm
383 +(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
475 475  
476 -**31**   -51dBm or greater
385 +(% style="color:#037691" %)**31** (%%) -51dBm or greater
477 477  
478 -**99**    Not known or not detectable
387 +(% style="color:#037691" %)**99** (%%) Not known or not detectable
479 479  
480 480  
390 +=== 2.4.5  Distance ===
481 481  
482 -=== 2.4.5  Calculate Flag ===
483 483  
393 +[[image:1670407401682-959.png]]
484 484  
485 -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.
486 486  
487 -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.
396 +(% style="color:blue" %)**Object1 Distance:**
488 488  
489 -Default value: 0. 
398 +Distance between sensor probe to the first object. (unit: cm)
490 490  
491 -Range (6 bits): (b)000000 ~~ (b) 111111
400 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
492 492  
402 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
493 493  
494 494  
495 -=== 2.4.6  Alarm ===
405 +(% style="color:blue" %)**Object2 Distance:**
496 496  
407 +Distance between sensor probe to the second object. (unit: cm)
497 497  
498 -See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
499 499  
410 +=== 2.4.6  Timestamp ===
500 500  
501 501  
502 -=== 2.4.7  Contact Status ===
503 -
504 -
505 -0: Open
506 -
507 -1: Close
508 -
509 -
510 -
511 -=== 2.4.8  Total pulse ===
512 -
513 -
514 -Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
515 -
516 -Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
517 -
518 -
519 -
520 -=== 2.4.9  The last open duration ===
521 -
522 -
523 -Dry Contact last open duration.
524 -
525 -Unit: min.
526 -
527 -[[image:image-20221021111346-17.png||height="146" width="770"]]
528 -
529 -
530 -
531 -=== 2.4.10  Timestamp ===
532 -
533 -
534 534  Timestamp : 0x6315537b =1662342011
535 535  
536 -Convert Unix timestamp to time 2022-9-5 9:40:11.
537 537  
538 -**~ **
539 -
540 -
541 541  == 2.5  Downlink Payload ==
542 542  
543 543  
544 -By default, CPN01 prints the downlink payload to console port.
419 +By default, NMDS200 prints the downlink payload to console port.
545 545  
546 546  [[image:image-20221021111414-18.png]] ​
547 547  
... ... @@ -558,7 +558,7 @@
558 558  
559 559  * (% style="color:#037691" %)**Reset**
560 560  
561 -If payload = 0x04FF, it will reset the NSE01
436 +If payload = 0x04FF, it will reset the NMDS200
562 562  
563 563  * (% style="color:#037691" %)**INTMOD**
564 564  
... ... @@ -565,115 +565,49 @@
565 565  Downlink Payload: 06000003, Set AT+INTMOD=3
566 566  
567 567  
568 -
569 569  == 2.6  ​LED Indicator ==
570 570  
571 571  
572 -The CPN01 has an internal LED which is to show the status of different states.
446 +The NMDS200 has an internal LED which is to show the status of different states.
573 573  
574 574  * When the device starts normally, the LED will light up for 1 second.
575 -* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
449 +* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
576 576  * For each uplink probe, LED will be on for 500ms.
577 577  
578 -== 2.7  Alarm Base on Timeout ==
579 579  
580 580  
581 -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:
454 +== 2.7  Distance alarm function ==
582 582  
583 583  
584 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
457 +(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
585 585  
586 -Keep Status = 1: Monitor Close to Open event
459 +(% style="color:#037691" %)**Example 1:**
587 587  
588 -Keep Status = 0: Monitor Open to Close event
461 +AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
589 589  
463 +AT+ ALARM2 =min,max
590 590  
591 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
592 592  
593 -Range 0 ~~ 65535(0xFFFF) seconds.
466 +(% style="color:#037691" %)**Example 2:**
594 594  
595 -If keep time = 0, Disable Alarm Base on Timeout feature.
468 +AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
596 596  
597 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
598 598  
599 599  
600 -(% style="color:blue" %)**AT Command to configure:**
601 601  
602 -(% 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.
473 +== 2.8  Set the number of data to be uploaded and the recording time ==
603 603  
604 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
605 605  
606 -
607 -
608 -== 2.8  Set debug mode ==
609 -
610 -
611 -Feature: Enable or Disable debug mode
612 -
613 -(% style="color:blue" %)**AT Command: AT+DEBUG**
614 -
615 -[[image:image-20221021111629-21.png]]
616 -
617 -
618 -
619 -== 2.9  Clear Flash Record ==
620 -
621 -
622 -Feature: Clear flash storage for data log feature.
623 -
624 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
625 -
626 -[[image:image-20221021111527-19.png]]
627 -
628 -
629 -
630 -== 2.10  Set trigger mode ==
631 -
632 -
633 -(% style="color:blue" %)**AT Command: AT+TTRMOD**
634 -
635 -Feature: Set the trigger interrupt mode.
636 -
637 -[[image:image-20221021111552-20.png]]
638 -
639 -
640 -
641 -== 2.11  Set the calculate flag ==
642 -
643 -
644 -Feature: Set the calculate flag
645 -
646 -(% style="color:blue" %)**AT Command: AT+CALCFLAG**
647 -
648 -[[image:image-20221021111711-22.png]]
649 -
650 -
651 -
652 -== 2.12 Set count number ==
653 -
654 -
655 -Feature: Manually set the count number
656 -
657 -(% style="color:blue" %)**AT Command: AT+SETCNT**
658 -
659 -[[image:image-20221021111748-24.png]]
660 -
661 -
662 -
663 -== 2.13  Set the number of data to be uploaded and the recording time ==
664 -
665 -
666 666  (% style="color:blue" %)**AT Command:**
667 667  
668 -(% 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)
478 +(% 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)
669 669  
670 -(% 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.
480 +(% 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.
671 671  
672 672  
483 +== 2.9  Read or Clear cached data ==
673 673  
674 -== 2.14  Read or Clear cached data ==
675 675  
676 -
677 677  (% style="color:blue" %)**AT Command:**
678 678  
679 679  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -680,27 +680,24 @@
680 680  
681 681  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
682 682  
683 -[[image:image-20221021111810-25.png||height="364" width="797"]]
492 +[[image:1670408172929-569.png]]
684 684  
685 685  
495 +== 2.10  ​Firmware Change Log ==
686 686  
687 -== 2.15  ​Firmware Change Log ==
688 688  
498 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
689 689  
690 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
691 -
692 692  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
693 693  
694 694  
503 +== 2.11  ​Battery Analysis ==
695 695  
696 -== 2.16  ​Battery Analysis ==
505 +=== 2.11.1  ​Battery Type ===
697 697  
698 698  
699 -=== 2.16.1  ​Battery Type ===
508 +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.
700 700  
701 -
702 -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.
703 -
704 704  The battery is designed to last for several years depends on the actual use environment and update interval. 
705 705  
706 706  The battery-related documents as below:
... ... @@ -714,10 +714,9 @@
714 714  [[image:image-20221021111911-26.png]] ​
715 715  
716 716  
523 +=== 2.11.2  Power consumption Analyze ===
717 717  
718 -=== 2.16.2  Power consumption Analyze ===
719 719  
720 -
721 721  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.
722 722  
723 723  Instruction to use as below:
... ... @@ -737,21 +737,18 @@
737 737  [[image:1666596205057-567.png]] ​
738 738  
739 739  
545 +=== 2.11.3  ​Battery Note ===
740 740  
741 -=== 2.16.3  ​Battery Note ===
742 742  
743 -
744 744  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.
745 745  
746 746  
551 +=== 2.11.4  Replace the battery ===
747 747  
748 -=== 2.16.4  Replace the battery ===
749 749  
554 +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).
750 750  
751 -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).
752 752  
753 -
754 -
755 755  = 3. ​ Access NB-IoT Module =
756 756  
757 757  
... ... @@ -759,13 +759,12 @@
759 759  
760 760  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/]] 
761 761  
762 -[[image:image-20221021112006-28.png]] ​
763 763  
565 +[[image:image-20221118094449-6.png]] ​
764 764  
765 765  
766 766  = 4.  Using the AT Commands =
767 767  
768 -
769 769  == 4.1  Access AT Commands ==
770 770  
771 771  
... ... @@ -804,57 +804,55 @@
804 804  
805 805  AT+SERVADDR  : Server Address
806 806  
807 -AT+TR      :  Get or Set record time
608 +AT+TR      :  Get or Set record time
808 808  
809 -AT+NOUD      : Get or Set the number of data to be uploaded
610 +AT+NOUD :  Get or Set the number of data to be uploaded
810 810  
811 811  AT+CDP     :  Read or Clear cached data
812 812  
813 -AT+ DEBUG   : Enable or Disable debug mode
614 +AT+DEBUG:  Enable or Disable debug mode
814 814  
815 -AT+ TTRIG   : Get or Set Alarm Base on Timeout
616 +AT+ALARM1:  Get or Set alarm of distance1
816 816  
817 -AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
618 +AT+ALARM2:  Get or Set alarm of distance2
818 818  
819 -AT+ CALCFLAG   : Get or Set the calculate flag
620 +AT+GETSENSORVALUE :  Returns the current sensor measurement
820 820  
821 -AT+ CLRC   : Clear current door open count
622 +AT+POWERIC :  Get or set the Power IC flag
822 822  
823 823  
824 824  (% style="color:blue" %)**COAP Management**      
825 825  
826 -AT+URI            : Resource parameters
627 +AT+URI :  Resource parameters
827 827  
828 828  
829 829  (% style="color:blue" %)**UDP Management**
830 830  
831 -AT+CFM          : Upload confirmation mode (only valid for UDP)
632 +AT+CFM :  Upload confirmation mode (only valid for UDP)
832 832  
833 833  
834 834  (% style="color:blue" %)**MQTT Management**
835 835  
836 -AT+CLIENT               : Get or Set MQTT client
637 +AT+CLIENT  : Get or Set MQTT client
837 837  
838 -AT+UNAME  : Get or Set MQTT Username
639 +AT+UNAME : Get or Set MQTT Username
839 839  
840 -AT+PWD                  : Get or Set MQTT password
641 +AT+PWD  :  Get or Set MQTT password
841 841  
842 -AT+PUBTOPIC  : Get or Set MQTT publish topic
643 +AT+PUBTOPIC :  Get or Set MQTT publish topic
843 843  
844 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
645 +AT+SUBTOPIC :  Get or Set MQTT subscription topic
845 845  
846 846  
847 847  (% style="color:blue" %)**Information**          
848 848  
849 -AT+FDR  : Factory Data Reset
650 +AT+FDR :  Factory Data Reset
850 850  
851 -AT+PWORD  : Serial Access Password
652 +AT+PWORD :  Serial Access Password
852 852  
853 853  
854 -
855 855  = ​5.  FAQ =
856 856  
857 -
858 858  == 5.1 ​ How to Upgrade Firmware ==
859 859  
860 860  
... ... @@ -862,13 +862,11 @@
862 862  
863 863  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]]
864 864  
865 -(% 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.**
664 +(% 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.**
866 866  
867 867  
868 -
869 869  = 6.  Trouble Shooting =
870 870  
871 -
872 872  == 6.1  ​Connection problem when uploading firmware ==
873 873  
874 874  
... ... @@ -875,7 +875,6 @@
875 875  (% 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]]
876 876  
877 877  
878 -
879 879  == 6.2  AT Command input doesn't work ==
880 880  
881 881  
... ... @@ -882,27 +882,19 @@
882 882  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.
883 883  
884 884  
885 -
886 886  = 7. ​ Order Info =
887 887  
888 888  
889 -Part Number**:** CPN01
684 +Part Number:(% style="color:blue" %)** NMDS200**
890 890  
891 891  
892 -
893 893  = 8.  Packing Info =
894 894  
895 895  
896 896  (% style="color:blue" %)**Package Includes**:
897 897  
898 -* CPN01 Open/Close Sensor x 1
899 -* External antenna x 1
692 +* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
900 900  
901 -(% style="color:blue" %)**Dimension and weight**:
902 -
903 -* Size: 195 x 125 x 55 mm
904 -* Weight:   420g
905 -
906 906  = 9.  Support =
907 907  
908 908  
1670404362039-351.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +492.6 KB
Content
1670405841875-916.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.1 KB
Content
1670405928926-116.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.7 KB
Content
1670406036256-101.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +181.0 KB
Content
1670406261143-723.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.9 KB
Content
1670407401682-959.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +23.7 KB
Content
1670408172929-569.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +211.8 KB
Content
LMDS200_10.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +39.9 KB
Content
image-20221118092935-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +13.1 KB
Content
image-20221118093144-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +11.7 KB
Content
image-20221118093512-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +9.5 KB
Content
image-20221118093658-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +12.7 KB
Content
image-20221118094227-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +29.2 KB
Content
image-20221118094449-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.5 KB
Content
image-20221118103445-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +20.4 KB
Content
image-20221118103453-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +46.2 KB
Content
image-20221118103547-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +43.5 KB
Content
image-20221207170748-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.1 KB
Content
image-20221207170748-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +29.9 KB
Content
image-20221207173200-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.7 KB
Content
image-20221207173300-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.0 KB
Content
image-20221208090742-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +79.7 KB
Content

Applications

Navigation

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