Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 49.1 >
edited by Edwin Chen
on 2022/10/24 22:37
To version < 83.5 >
edited by Xiaoling
on 2022/12/08 09:52
>
Change comment: There is no comment for this version

Summary

Details

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

Applications

Navigation

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