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