Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 58.4 >
edited by Xiaoling
on 2022/11/17 14:02
To version < 90.6 >
edited by Xiaoling
on 2023/04/04 14:50
>
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,66 +1,73 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20221117105556-1.png]]
2 +[[image:LMDS200_10.jpg||height="572" width="572"]]
3 3  
4 4  
5 5  
6 6  
7 7  
8 +(% style="display:none" %) (%%)
8 8  
9 9  
11 +
12 +
13 +
10 10  **Table of Contents：**
11 11  
16 +{{toc/}}
12 12  
13 13  
14 14  
15 15  
16 -= 1.  Introduction =
17 17  
18 18  
19 -== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
20 20  
21 21  
25 +
26 += 1.  Introduction =
27 +
28 +== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
29 +
30 +
22 22  (((
23 -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.
32 +The Dragino NMDS200 is a(% style="color:blue" %)** NB-IoT Microwave Radar distance sensor**(%%). It uses (% style="color:blue" %)**24Ghz Microwave**(%%) to detect the distance between sensor and different objects. Compare vs ultrasonic or Lidar measurement method, Microwave Radar is (% style="color:blue" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or thick dust on top of the sensor.
24 24  )))
25 25  
26 26  (((
27 -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.
36 +The NMDS200 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
28 28  )))
29 29  
30 30  (((
31 -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.
40 +NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
32 32  )))
33 33  
34 34  (((
35 -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.
44 +NMDS200 (% style="color:blue" %)**supports Alarm Feature**(%%), user can set the NMDS200 to uplink data in a short interval when the distance is out of configured range.
36 36  )))
37 37  
38 38  (((
39 -NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
48 +NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technology**(%%) developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
40 40  )))
41 41  
42 42  (((
43 -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.
52 +NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
44 44  )))
45 45  
46 46  (((
47 -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)
56 +NMDS200 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**,(%%) It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
48 48  )))
49 49  
50 50  (((
51 -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.
60 +To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection.
52 52  )))
53 53  
54 54  
55 -
56 56  == ​1.2  Features ==
57 57  
58 58  
59 59  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
60 -* Open/Close detect
61 -* Open/Close statistics
68 +* Short uplink interval for Distance Alarm
62 62  * Monitor Battery Level
63 -* connect two door sensors
70 +* Microwave Radar for distance detection
64 64  * Datalog feature
65 65  * Uplink periodically
66 66  * Downlink to change configure
... ... @@ -72,33 +72,39 @@
72 72  * 8500mAh Battery for long-term use
73 73  
74 74  
82 +== 1.3 Radar probe specification ==
75 75  
76 -== 1.3  Storage & Operation ==
77 77  
85 +* Measuring Method: FMCW
86 +* Frequency: 24.000 ~~ 24.500 GHz
87 +* Measurement output power: 6dBm
88 +* Measure range: 0.5 ~~ 20m
89 +* Accuracy: ±0.1m
90 +* Resolution: 0.01m
91 +* Horizontal Angel: 78°
92 +* Vertical Angel: 23°
78 78  
79 -Temperature -40°C to +85°C
80 80  
95 +== 1.4  Storage Temperature ==
81 81  
82 -== 1.4  Mechanical ==
83 83  
98 + -40°C to +85°C
84 84  
85 -[[image:image-20221117114937-4.png]]
86 86  
87 -
88 -[[image:image-20221117114949-5.png]]
89 -
90 -
91 -[[image:image-20221117115010-6.png]]
92 -
93 -
94 -
95 95  == 1.5 ​ Applications ==
96 96  
97 97  
98 -[[image:image-20221117114842-3.png]]
104 +* Horizontal distance measurement
105 +* Liquid level measurement
106 +* Parking management system
107 +* Object proximity and presence detection
108 +* Intelligent trash can management system
109 +* Robot obstacle avoidance
110 +* Automatic control
111 +* Sewer
112 +* Bottom water level monitoring
99 99  
100 100  
101 -
102 102  == 1.6  Specification ==
103 103  
104 104  
... ... @@ -105,111 +105,65 @@
105 105  (% style="color:blue" %)**Common DC Characteristics:**
106 106  
107 107  * Supply Voltage: 2.1v ~~ 3.6v
108 -* Operating Temperature: -40 ~~ 85°C
121 +* Operating Temperature: 0 ~~ 70°C
109 109  
110 110  (% style="color:blue" %)**NB-IoT Spec:**
111 111  
112 -* - B1 @H-FDD: 2100MHz
113 -* - B3 @H-FDD: 1800MHz
114 -* - B8 @H-FDD: 900MHz
115 -* - B5 @H-FDD: 850MHz
116 -* - B20 @H-FDD: 800MHz
117 -* - B28 @H-FDD: 700MHz
125 +* B1 @H-FDD: 2100MHz
126 +* B3 @H-FDD: 1800MHz
127 +* B8 @H-FDD: 900MHz
128 +* B5 @H-FDD: 850MHz
129 +* B20 @H-FDD: 800MHz
130 +* B28 @H-FDD: 700MHz
118 118  
119 119  
133 +== 1.7  Installation ==
120 120  
121 -== 1.7  Pin Definitions and Switch ==
122 122  
136 +Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
123 123  
124 -[[image:image-20221021110429-4.png]]
125 125  
139 +[[image:image-20221207170748-1.png]]
126 126  
127 -=== 1.7.1  Pin Definition ===
128 128  
142 + [[image:image-20221207170748-2.png||height="345" width="634"]]
129 129  
130 -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]]
131 131  
145 +== 1.8  Pin Definitions and Switch ==
132 132  
133 133  
134 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
148 +[[image:1670404362039-351.png]]
135 135  
136 136  
137 -Power on Device when putting this jumper.
151 += 2.  Use NMDS200 to communicate with IoT Server =
138 138  
139 -
140 -
141 -=== 1.7.3  BOOT MODE / SW1 ===
142 -
143 -
144 -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.
145 -
146 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
147 -
148 -
149 -
150 -=== 1.7.4  Reset Button ===
151 -
152 -
153 -Press to reboot the device.
154 -
155 -
156 -
157 -=== 1.7.5  LED ===
158 -
159 -
160 -The LED will blink when :
161 -
162 -1.  Boot the device in flash mode
163 -
164 -2.  Send an uplink packet
165 -
166 -
167 -
168 -== 1.8  Magnet Distance ==
169 -
170 -
171 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
172 -
173 -(% style="color:blue" %)**Iron Door:**(%%)**  **30 ~~ 45mm
174 -
175 -
176 -
177 -= 2.  Use CPN01 to communicate with IoT Server =
178 -
179 -
180 180  == 2.1  How it works ==
181 181  
182 182  
183 -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.
156 +The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
184 184  
185 -The diagram below shows the working flow in the default firmware of CPN01:
158 +The diagram below shows the working flow in the default firmware of NMDS200:
186 186  
187 -[[image:image-20221021110615-5.png]]
160 +[[image:image-20221021110615-5.png||height="996" width="492"]]
188 188  
189 189  
163 +== 2.2 ​ Configure NMDS200 ==
190 190  
191 -== 2.2 ​ Configure CPN01 ==
192 192  
166 +To use NMDS200 in your city, make sure to meet below requirements:
193 193  
194 -=== 2.2.1 Test Requirement ===
195 -
196 -
197 -To use CPN01 in your city, make sure to meet below requirements:
198 -
199 199  * Your local operator has already distributed an NB-IoT Network.
200 -* The local NB-IoT network used the band that CPN01 supports.
169 +* The local NB-IoT network used the band that NMDS200 supports.
201 201  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
202 202  
203 -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.
172 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NMDS200 will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
204 204  
205 -[[image:image-20221023000439-3.png]]
174 +[[image:image-20221209090938-1.png]]
206 206  
207 - ​
208 208  
177 +=== 2.2.1 Insert NB-IoT SIM card ===
209 209  
210 -=== 2.2.2 Insert NB-IoT SIM card ===
211 211  
212 -
213 213  Insert the NB-IoT Card get from your provider.
214 214  
215 215  User needs to take out the NB-IoT module and insert the SIM card like below:
... ... @@ -217,12 +217,11 @@
217 217  [[image:image-20221021110745-6.png]] ​
218 218  
219 219  
187 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
220 220  
221 -=== 2.2.3 Connect USB – TTL to CPN01 and configure it ===
222 222  
190 +User need to configure NMDS200 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NMDS200 support AT Commands, user can use a USB to TTL adapter to connect to NMDS200 and use AT Commands to configure it, as below.
223 223  
224 -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.
225 -
226 226  (% style="color:blue" %)**Connection:**
227 227  
228 228  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
... ... @@ -244,24 +244,23 @@
244 244  
245 245  * Flow Control: (% style="color:red" %)**None**
246 246  
247 -Make sure the switch is in FLASH position, then power on CPN01 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
213 +Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
248 248  
249 249  ​[[image:image-20221021110817-7.png]]
250 250  
251 -CPN01 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
217 +NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
252 252  
253 253  
254 254  (% 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]]
255 255  
256 256  
223 +=== 2.2.3 Use CoAP protocol to uplink data ===
257 257  
258 -=== 2.2.4 Use CoAP protocol to uplink data ===
259 259  
260 -
261 261  (% 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/]]
262 262  
263 263  
264 -(% style="color:blue" %)**Use below commands in CPN01:**
229 +(% style="color:blue" %)**Use below commands in NMDS200:**
265 265  
266 266  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
267 267  
... ... @@ -271,18 +271,17 @@
271 271  
272 272  For parameter description, please refer to AT command set
273 273  
274 -[[image:image-20221021110948-8.png]]
239 +[[image:1670471530120-960.png||height="647" width="674"]]
275 275  
276 276  
277 -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.
242 +After configuring the server address and (% style="color:green" %)**reset NMDS200**(%%) (via AT+ATZ ), NMDS200 will start to uplink sensor values to the CoAP server.
278 278  
279 -[[image:image-20221021110956-9.png]] ​
244 +[[image:1670405841875-916.png]] ​
280 280  
281 281  
247 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
282 282  
283 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
284 284  
285 -
286 286  (% style="color:blue" %)**AT Commands:**
287 287  
288 288  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
... ... @@ -291,7 +291,7 @@
291 291  
292 292  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
293 293  
294 -​ [[image:image-20221021111025-10.png]]
258 +​ [[image:1670471559211-638.png]]
295 295  
296 296  
297 297  [[image:image-20221021111033-11.png||height="241" width="576"]]
... ... @@ -298,10 +298,9 @@
298 298  
299 299  ​
300 300  
265 +=== 2.2.5 Use MQTT protocol to uplink data ===
301 301  
302 -=== 2.2.6 Use MQTT protocol to uplink data ===
303 303  
304 -
305 305  (% style="color:blue" %)**AT Commands:**
306 306  
307 307  * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
... ... @@ -318,10 +318,10 @@
318 318  
319 319  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
320 320  
321 -​ [[image:image-20221021111058-12.png]]
284 +​ [[image:1670471584490-640.png]]
322 322  
323 323  
324 -[[image:image-20221021111201-16.png||height="472" width="653"]]
287 +[[image:1670405928926-116.png]]
325 325  
326 326  ​
327 327  
... ... @@ -328,10 +328,9 @@
328 328  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.
329 329  
330 330  
294 +=== 2.2.6 Use TCP protocol to uplink data ===
331 331  
332 -=== 2.2.7 Use TCP protocol to uplink data ===
333 333  
334 -
335 335  (% style="color:blue" %)**AT Commands:**
336 336  
337 337  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
... ... @@ -338,82 +338,72 @@
338 338  
339 339  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
340 340  
341 -​ [[image:image-20221021111125-14.png]]
303 +​ [[image:1670471613823-833.png]]
342 342  
305 +
343 343  [[image:image-20221021111131-15.png]]
344 344  
345 345  ​
346 346  
310 +=== 2.2.7 Change Update Interval ===
347 347  
348 -=== 2.2.8 Change Update Interval ===
349 349  
350 -
351 351  User can use below command to change the (% style="color:blue" %)**uplink interval**.
352 352  
353 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
315 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
354 354  
355 355  (% style="color:red" %)**NOTE:**
356 356  
357 -1.  By default, the device will send an uplink message every 1 hour.
319 +1.  By default, the device will send an uplink message every 4 hour.
358 358  
359 359  
360 -
361 361  == 2.3  Uplink Payload ==
362 362  
363 363  
364 -The uplink payload includes 123 bytes in total by default.
325 +The uplink payload includes 23 bytes in total by default.
365 365  
366 -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.
327 +Each time the device uploads a data package. The user can use the AT+NOUD command to upload the recorded data.Up to 32 sets of recorded data can be uploaded.
367 367  
368 368  
369 -(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
370 -|=(% 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**
371 -|=(% 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"]]
330 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:450px" %)
331 +|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:30px" %)**2**|(% style="width:30px" %)**2**|(% style="width:75px" %)**1**|(% style="width:30px" %)**1**|(% style="width:50px" %)**1**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**
332 +|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Exit flag|(% style="width:94px" %) [[Distance 1>>||anchor="H2.4.5A0Distance"]] |(% style="width:93px" %) [[Distance 2>>||anchor="H2.4.5A0Distance"]]
372 372  
373 -(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
374 -|(% 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**
375 -|(% 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" %)...
334 +(% border="1" style="background-color:#ffffcc; color:green; width:429px" %)
335 +|(% style="width:60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)(((
336 +**1-32 group**
337 +)))
338 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)...
376 376  
377 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
340 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
378 378  
379 -[[image:image-20221021111201-16.png||height="572" width="792"]]
342 +[[image:1670406261143-723.png]]
380 380  
381 381  
382 -The payload is ASCII string, representative same HEX:
345 +The payload is ASCII string, representative same HEX: **0x (% style="color:red" %)__f867787050471071__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)**
383 383  
384 -**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 __**
385 -
386 386  **where:**
387 387  
388 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
349 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
389 389  
390 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
351 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
391 391  
392 -* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
353 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
393 393  
394 -* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
355 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
395 395  
396 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
357 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
397 397  
398 -* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
359 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
399 399  
400 -* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
361 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
401 401  
402 -* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
363 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
403 403  
404 -* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
365 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
405 405  
406 -* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
407 -
408 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
409 -
410 -* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
411 -
412 -* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
413 -
414 414  == 2.4  Payload Explanation and Sensor Interface ==
415 415  
416 -
417 417  === 2.4.1  Device ID ===
418 418  
419 419  
... ... @@ -428,20 +428,18 @@
428 428  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
429 429  
430 430  
431 -
432 432  === 2.4.2  Version Info ===
433 433  
434 434  
435 435  Specify the software version: 0x64=100, which means firmware version 1.00.
436 436  
437 -For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
388 +For example 0x00 64 : This device is NMDS200 with firmware version 1.0.0.
438 438  
439 439  
440 -
441 441  === 2.4.3  Battery Info ===
442 442  
443 443  
444 -Check the battery voltage for CPN01.
394 +Check the battery voltage for NMDS200.
445 445  
446 446  Ex1: 0x0B45 = 2885mV
447 447  
... ... @@ -448,89 +448,54 @@
448 448  Ex2: 0x0B49 = 2889mV
449 449  
450 450  
451 -
452 452  === 2.4.4  Signal Strength ===
453 453  
454 454  
455 455  NB-IoT Network signal Strength.
456 456  
457 -**Ex1: 0x1d = 29**
406 +(% style="color:blue" %)**Ex1: 0x1d = 29**
458 458  
459 -**0**  -113dBm or less
408 +(% style="color:#037691" %)**0** (%%) -113dBm or less
460 460  
461 -**1**  -111dBm
410 +(% style="color:#037691" %)**1**  (%%) -111dBm
462 462  
463 -**2...30** -109dBm... -53dBm
412 +(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
464 464  
465 -**31**   -51dBm or greater
414 +(% style="color:#037691" %)**31** (%%) -51dBm or greater
466 466  
467 -**99**    Not known or not detectable
416 +(% style="color:#037691" %)**99** (%%) Not known or not detectable
468 468  
469 469  
419 +=== 2.4.5  Distance ===
470 470  
471 -=== 2.4.5  Calculate Flag ===
472 472  
422 +[[image:1670407401682-959.png]]
473 473  
474 -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.
475 475  
476 -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.
425 +(% style="color:blue" %)**Object1 Distance:**
477 477  
478 -Default value: 0. 
427 +Distance between sensor probe to the first object. (unit: cm)
479 479  
480 -Range (6 bits): (b)000000 ~~ (b) 111111
429 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
481 481  
431 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
482 482  
483 483  
484 -=== 2.4.6  Alarm ===
434 +(% style="color:blue" %)**Object2 Distance:**
485 485  
436 +Distance between sensor probe to the second object. (unit: cm)
486 486  
487 -See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
488 488  
439 +=== 2.4.6  Timestamp ===
489 489  
490 490  
491 -=== 2.4.7  Contact Status ===
492 -
493 -
494 -0: Open
495 -
496 -1: Close
497 -
498 -
499 -
500 -=== 2.4.8  Total pulse ===
501 -
502 -
503 -Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
504 -
505 -Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
506 -
507 -
508 -
509 -=== 2.4.9  The last open duration ===
510 -
511 -
512 -Dry Contact last open duration.
513 -
514 -Unit: min.
515 -
516 -[[image:image-20221021111346-17.png||height="146" width="770"]]
517 -
518 -
519 -
520 -=== 2.4.10  Timestamp ===
521 -
522 -
523 523  Timestamp : 0x6315537b =1662342011
524 524  
525 -Convert Unix timestamp to time 2022-9-5 9:40:11.
526 526  
527 -**~ **
528 -
529 -
530 530  == 2.5  Downlink Payload ==
531 531  
532 532  
533 -By default, CPN01 prints the downlink payload to console port.
448 +By default, NMDS200 prints the downlink payload to console port.
534 534  
535 535  [[image:image-20221021111414-18.png]] ​
536 536  
... ... @@ -547,7 +547,7 @@
547 547  
548 548  * (% style="color:#037691" %)**Reset**
549 549  
550 -If payload = 0x04FF, it will reset the NSE01
465 +If payload = 0x04FF, it will reset the NMDS200
551 551  
552 552  * (% style="color:#037691" %)**INTMOD**
553 553  
... ... @@ -554,115 +554,46 @@
554 554  Downlink Payload: 06000003, Set AT+INTMOD=3
555 555  
556 556  
557 -
558 558  == 2.6  ​LED Indicator ==
559 559  
560 560  
561 -The CPN01 has an internal LED which is to show the status of different states.
475 +The NMDS200 has an internal LED which is to show the status of different states.
562 562  
563 563  * When the device starts normally, the LED will light up for 1 second.
564 -* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
478 +* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
565 565  * For each uplink probe, LED will be on for 500ms.
566 566  
567 -== 2.7  Alarm Base on Timeout ==
568 568  
482 +== 2.7  Distance alarm function ==
569 569  
570 -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:
571 571  
485 +(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
572 572  
573 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
487 +(% style="color:#037691" %)**Example 1:**
574 574  
575 -Keep Status = 1: Monitor Close to Open event
489 +AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
576 576  
577 -Keep Status = 0: Monitor Open to Close event
491 +AT+ ALARM2 =min,max
578 578  
579 579  
580 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
494 +(% style="color:#037691" %)**Example 2:**
581 581  
582 -Range 0 ~~ 65535(0xFFFF) seconds.
496 +AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
583 583  
584 -If keep time = 0, Disable Alarm Base on Timeout feature.
585 585  
586 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
499 +== 2.8  Set the number of data to be uploaded and the recording time ==
587 587  
588 588  
589 -(% style="color:blue" %)**AT Command to configure:**
590 -
591 -(% 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.
592 -
593 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
594 -
595 -
596 -
597 -== 2.8  Set debug mode ==
598 -
599 -
600 -Feature: Enable or Disable debug mode
601 -
602 -(% style="color:blue" %)**AT Command: AT+DEBUG**
603 -
604 -[[image:image-20221021111629-21.png]]
605 -
606 -
607 -
608 -== 2.9  Clear Flash Record ==
609 -
610 -
611 -Feature: Clear flash storage for data log feature.
612 -
613 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
614 -
615 -[[image:image-20221021111527-19.png]]
616 -
617 -
618 -
619 -== 2.10  Set trigger mode ==
620 -
621 -
622 -(% style="color:blue" %)**AT Command: AT+TTRMOD**
623 -
624 -Feature: Set the trigger interrupt mode.
625 -
626 -[[image:image-20221021111552-20.png]]
627 -
628 -
629 -
630 -== 2.11  Set the calculate flag ==
631 -
632 -
633 -Feature: Set the calculate flag
634 -
635 -(% style="color:blue" %)**AT Command: AT+CALCFLAG**
636 -
637 -[[image:image-20221021111711-22.png]]
638 -
639 -
640 -
641 -== 2.12 Set count number ==
642 -
643 -
644 -Feature: Manually set the count number
645 -
646 -(% style="color:blue" %)**AT Command: AT+SETCNT**
647 -
648 -[[image:image-20221021111748-24.png]]
649 -
650 -
651 -
652 -== 2.13  Set the number of data to be uploaded and the recording time ==
653 -
654 -
655 655  (% style="color:blue" %)**AT Command:**
656 656  
657 -(% 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)
504 +(% 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)
658 658  
659 -(% 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.
506 +(% 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.
660 660  
661 661  
509 +== 2.9  Read or Clear cached data ==
662 662  
663 -== 2.14  Read or Clear cached data ==
664 664  
665 -
666 666  (% style="color:blue" %)**AT Command:**
667 667  
668 668  (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
... ... @@ -669,78 +669,24 @@
669 669  
670 670  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
671 671  
672 -[[image:image-20221021111810-25.png||height="364" width="797"]]
518 +[[image:1670408172929-569.png]]
673 673  
674 674  
521 +== 2.10  ​Firmware Change Log ==
675 675  
676 -== 2.15  ​Firmware Change Log ==
677 677  
524 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0>>https://www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0]]
678 678  
679 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
680 -
681 681  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
682 682  
683 683  
529 +== 2.11 Battery & Power Consumption ==
684 684  
685 -== 2.16  ​Battery Analysis ==
686 686  
532 +NMDS200 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
687 687  
688 -=== 2.16.1  ​Battery Type ===
534 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
689 689  
690 -
691 -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.
692 -
693 -The battery is designed to last for several years depends on the actual use environment and update interval. 
694 -
695 -The battery-related documents as below:
696 -
697 -* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
698 -
699 -* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
700 -
701 -* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
702 -
703 -[[image:image-20221021111911-26.png]] ​
704 -
705 -
706 -
707 -=== 2.16.2  Power consumption Analyze ===
708 -
709 -
710 -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.
711 -
712 -Instruction to use as below:
713 -
714 -(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
715 -
716 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
717 -
718 -* Product Model
719 -
720 -* Uplink Interval
721 -
722 -* Working Mode
723 -
724 -And the Life expectation in difference case will be shown on the right.
725 -
726 -[[image:1666596205057-567.png]] ​
727 -
728 -
729 -
730 -=== 2.16.3  ​Battery Note ===
731 -
732 -
733 -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.
734 -
735 -
736 -
737 -=== 2.16.4  Replace the battery ===
738 -
739 -
740 -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).
741 -
742 -
743 -
744 744  = 3. ​ Access NB-IoT Module =
745 745  
746 746  
... ... @@ -748,13 +748,12 @@
748 748  
749 749  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/]] 
750 750  
751 -[[image:image-20221021112006-28.png]] ​
752 752  
544 +[[image:image-20221118094449-6.png]] ​
753 753  
754 754  
755 755  = 4.  Using the AT Commands =
756 756  
757 -
758 758  == 4.1  Access AT Commands ==
759 759  
760 760  
... ... @@ -785,65 +785,63 @@
785 785  
786 786  AT+INTMOD            : Set the trigger interrupt mode
787 787  
788 -AT+5VT  : Set extend the time of 5V power  
579 +AT+5VT  : Set extend the time of 5V power  
789 789  
790 -AT+PRO  : Choose agreement
581 +AT+PRO  : Choose agreement
791 791  
792 -AT+RXDL  : Extend the sending and receiving time
583 +AT+RXDL  : Extend the sending and receiving time
793 793  
794 -AT+SERVADDR  : Server Address
585 +AT+SERVADDR  : Server Address
795 795  
796 -AT+TR      :  Get or Set record time
587 +AT+TR      :  Get or Set record time
797 797  
798 -AT+NOUD      : Get or Set the number of data to be uploaded
589 +AT+NOUD :  Get or Set the number of data to be uploaded
799 799  
800 800  AT+CDP     :  Read or Clear cached data
801 801  
802 -AT+ DEBUG   : Enable or Disable debug mode
593 +AT+DEBUG:  Enable or Disable debug mode
803 803  
804 -AT+ TTRIG   : Get or Set Alarm Base on Timeout
595 +AT+ALARM1:  Get or Set alarm of distance1
805 805  
806 -AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
597 +AT+ALARM2:  Get or Set alarm of distance2
807 807  
808 -AT+ CALCFLAG   : Get or Set the calculate flag
599 +AT+GETSENSORVALUE :  Returns the current sensor measurement
809 809  
810 -AT+ CLRC   : Clear current door open count
601 +AT+POWERIC :  Get or set the Power IC flag
811 811  
812 812  
813 813  (% style="color:blue" %)**COAP Management**      
814 814  
815 -AT+URI            : Resource parameters
606 +AT+URI :  Resource parameters
816 816  
817 817  
818 818  (% style="color:blue" %)**UDP Management**
819 819  
820 -AT+CFM          : Upload confirmation mode (only valid for UDP)
611 +AT+CFM :  Upload confirmation mode (only valid for UDP)
821 821  
822 822  
823 823  (% style="color:blue" %)**MQTT Management**
824 824  
825 -AT+CLIENT               : Get or Set MQTT client
616 +AT+CLIENT  : Get or Set MQTT client
826 826  
827 -AT+UNAME  : Get or Set MQTT Username
618 +AT+UNAME : Get or Set MQTT Username
828 828  
829 -AT+PWD                  : Get or Set MQTT password
620 +AT+PWD  :  Get or Set MQTT password
830 830  
831 -AT+PUBTOPIC  : Get or Set MQTT publish topic
622 +AT+PUBTOPIC :  Get or Set MQTT publish topic
832 832  
833 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
624 +AT+SUBTOPIC :  Get or Set MQTT subscription topic
834 834  
835 835  
836 836  (% style="color:blue" %)**Information**          
837 837  
838 -AT+FDR  : Factory Data Reset
629 +AT+FDR :  Factory Data Reset
839 839  
840 -AT+PWORD  : Serial Access Password
631 +AT+PWORD :  Serial Access Password
841 841  
842 842  
843 -
844 844  = ​5.  FAQ =
845 845  
846 -
847 847  == 5.1 ​ How to Upgrade Firmware ==
848 848  
849 849  
... ... @@ -851,13 +851,11 @@
851 851  
852 852  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]]
853 853  
854 -(% 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.**
643 +(% 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.**
855 855  
856 856  
857 -
858 858  = 6.  Trouble Shooting =
859 859  
860 -
861 861  == 6.1  ​Connection problem when uploading firmware ==
862 862  
863 863  
... ... @@ -864,7 +864,6 @@
864 864  (% 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]]
865 865  
866 866  
867 -
868 868  == 6.2  AT Command input doesn't work ==
869 869  
870 870  
... ... @@ -871,27 +871,20 @@
871 871  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.
872 872  
873 873  
874 -
875 875  = 7. ​ Order Info =
876 876  
877 877  
878 -Part Number**:** CPN01
663 +Part Number:(% style="color:blue" %)** NMDS200**
879 879  
880 880  
881 -
882 882  = 8.  Packing Info =
883 883  
884 884  
885 885  (% style="color:blue" %)**Package Includes**:
886 886  
887 -* CPN01 Open/Close Sensor x 1
888 -* External antenna x 1
671 +* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
889 889  
890 -(% style="color:blue" %)**Dimension and weight**:
891 891  
892 -* Size: 195 x 125 x 55 mm
893 -* Weight:   420g
894 -
895 895  = 9.  Support =
896 896  
897 897  
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
1670471530120-960.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +67.6 KB
Content
1670471559211-638.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +170.6 KB
Content
1670471584490-640.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +91.1 KB
Content
1670471613823-833.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +181.0 KB
Content
LMDS200_10.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +39.9 KB
Content
image-20221117142300-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +147.8 KB
Content
image-20221117145932-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +51.9 KB
Content
image-20221117150312-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +8.7 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
image-20221209090938-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +121.9 KB
Content
image-20221212171610-1.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +756.0 KB
Content

Applications

Navigation

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