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

Applications

Navigation

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