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

Applications

Navigation

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