Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 61.5 >
edited by Xiaoling
on 2022/11/17 16:45
To version < 91.1 >
edited by Ellie Zhang
on 2023/08/14 16:31
>
Change comment: There is no comment for this version

Summary

Details

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