Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 79.1 >
edited by Xiaoling
on 2022/12/07 17:40
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
Content
... ... @@ -1,13 +1,28 @@
1 1  (% style="text-align:center" %)
2 -[[image:LMDS200_10.jpg]]
2 +[[image:LMDS200_10.jpg||height="572" width="572"]]
3 3  
4 4  
5 +
6 +
7 +
8 +(% style="display:none" %) (%%)
9 +
10 +
11 +
12 +
13 +
5 5  **Table of Contents：**
6 6  
16 +{{toc/}}
7 7  
8 8  
9 9  
10 10  
21 +
22 +
23 +
24 +
25 +
11 11  = 1.  Introduction =
12 12  
13 13  == 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
... ... @@ -15,25 +15,37 @@
15 15  
16 16  (((
17 17  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 +)))
18 18  
19 -
35 +(((
20 20  The NMDS200 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
37 +)))
21 21  
39 +(((
22 22  NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
41 +)))
23 23  
43 +(((
24 24  NMDS200 (% style="color:blue" %)**supports Alarm Feature**(%%), user can set the NMDS200 to uplink data in a short interval when the distance is out of configured range.
45 +)))
25 25  
47 +(((
26 26  NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technology**(%%) developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.
49 +)))
27 27  
51 +(((
28 28  NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
53 +)))
29 29  
55 +(((
30 30  NMDS200 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**,(%%) It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
57 +)))
31 31  
59 +(((
32 32  To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection.
33 33  )))
34 34  
35 35  
36 -
37 37  == ​1.2  Features ==
38 38  
39 39  
... ... @@ -52,14 +52,13 @@
52 52  * 8500mAh Battery for long-term use
53 53  
54 54  
55 -
56 56  == 1.3 Radar probe specification ==
57 57  
58 58  
59 59  * Measuring Method: FMCW
60 -* Frequency: 24.000 24.500 GHz
86 +* Frequency: 24.000 ~~ 24.500 GHz
61 61  * Measurement output power: 6dBm
62 -* Measure range: 0.5 20m
88 +* Measure range: 0.5 ~~ 20m
63 63  * Accuracy: ±0.1m
64 64  * Resolution: 0.01m
65 65  * Horizontal Angel: 78°
... ... @@ -66,8 +66,6 @@
66 66  * Vertical Angel: 23°
67 67  
68 68  
69 -
70 -
71 71  == 1.4  Storage Temperature ==
72 72  
73 73  
... ... @@ -74,13 +74,9 @@
74 74   -40°C to +85°C
75 75  
76 76  
77 -
78 -
79 -
80 80  == 1.5 ​ Applications ==
81 81  
82 82  
83 -
84 84  * Horizontal distance measurement
85 85  * Liquid level measurement
86 86  * Parking management system
... ... @@ -92,7 +92,6 @@
92 92  * Bottom water level monitoring
93 93  
94 94  
95 -
96 96  == 1.6  Specification ==
97 97  
98 98  
... ... @@ -111,7 +111,6 @@
111 111  * B28 @H-FDD: 700MHz
112 112  
113 113  
114 -
115 115  == 1.7  Installation ==
116 116  
117 117  
... ... @@ -118,10 +118,12 @@
118 118  Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
119 119  
120 120  
121 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
139 +[[image:image-20221207170748-1.png]]
122 122  
123 123  
142 + [[image:image-20221207170748-2.png||height="345" width="634"]]
124 124  
144 +
125 125  == 1.8  Pin Definitions and Switch ==
126 126  
127 127  
... ... @@ -137,7 +137,7 @@
137 137  
138 138  The diagram below shows the working flow in the default firmware of NMDS200:
139 139  
140 -[[image:image-20221021110615-5.png]]
160 +[[image:image-20221021110615-5.png||height="996" width="492"]]
141 141  
142 142  
143 143  == 2.2 ​ Configure NMDS200 ==
... ... @@ -151,7 +151,7 @@
151 151  
152 152  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.
153 153  
154 -[[image:image-20221207173300-4.png]]
174 +[[image:image-20221209090938-1.png]]
155 155  
156 156  
157 157  === 2.2.1 Insert NB-IoT SIM card ===
... ... @@ -164,10 +164,10 @@
164 164  [[image:image-20221021110745-6.png]] ​
165 165  
166 166  
167 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
187 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
168 168  
169 169  
170 -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.
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.
171 171  
172 172  (% style="color:blue" %)**Connection:**
173 173  
... ... @@ -190,24 +190,23 @@
190 190  
191 191  * Flow Control: (% style="color:red" %)**None**
192 192  
193 -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**(%%).
194 194  
195 195  ​[[image:image-20221021110817-7.png]]
196 196  
197 -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.
198 198  
199 199  
200 200  (% 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]]
201 201  
202 202  
223 +=== 2.2.3 Use CoAP protocol to uplink data ===
203 203  
204 -=== 2.2.4 Use CoAP protocol to uplink data ===
205 205  
206 -
207 207  (% 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/]]
208 208  
209 209  
210 -(% style="color:blue" %)**Use below commands in NDS03A:**
229 +(% style="color:blue" %)**Use below commands in NMDS200:**
211 211  
212 212  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
213 213  
... ... @@ -217,15 +217,15 @@
217 217  
218 218  For parameter description, please refer to AT command set
219 219  
220 -[[image:image-20221021110948-8.png]]
239 +[[image:1670471530120-960.png||height="647" width="674"]]
221 221  
222 222  
223 -After configuring the server address and (% style="color:green" %)**reset NDS03A**(%%) (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.
224 224  
225 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
244 +[[image:1670405841875-916.png]] ​
226 226  
227 227  
228 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
247 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
229 229  
230 230  
231 231  (% style="color:blue" %)**AT Commands:**
... ... @@ -236,7 +236,7 @@
236 236  
237 237  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
238 238  
239 -​ [[image:image-20221021111025-10.png]]
258 +​ [[image:1670471559211-638.png]]
240 240  
241 241  
242 242  [[image:image-20221021111033-11.png||height="241" width="576"]]
... ... @@ -243,7 +243,7 @@
243 243  
244 244  ​
245 245  
246 -=== 2.2.6 Use MQTT protocol to uplink data ===
265 +=== 2.2.5 Use MQTT protocol to uplink data ===
247 247  
248 248  
249 249  (% style="color:blue" %)**AT Commands:**
... ... @@ -262,10 +262,10 @@
262 262  
263 263  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
264 264  
265 -​ [[image:image-20221118103445-7.png]]
284 +​ [[image:1670471584490-640.png]]
266 266  
267 267  
268 -[[image:image-20221118103453-8.png||height="608" width="841"]]
287 +[[image:1670405928926-116.png]]
269 269  
270 270  ​
271 271  
... ... @@ -272,7 +272,7 @@
272 272  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.
273 273  
274 274  
275 -=== 2.2.7 Use TCP protocol to uplink data ===
294 +=== 2.2.6 Use TCP protocol to uplink data ===
276 276  
277 277  
278 278  (% style="color:blue" %)**AT Commands:**
... ... @@ -281,18 +281,19 @@
281 281  
282 282  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
283 283  
284 -​ [[image:image-20221021111125-14.png]]
303 +​ [[image:1670471613823-833.png]]
285 285  
305 +
286 286  [[image:image-20221021111131-15.png]]
287 287  
288 288  ​
289 289  
290 -=== 2.2.8 Change Update Interval ===
310 +=== 2.2.7 Change Update Interval ===
291 291  
292 292  
293 293  User can use below command to change the (% style="color:blue" %)**uplink interval**.
294 294  
295 -* (% 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)
296 296  
297 297  (% style="color:red" %)**NOTE:**
298 298  
... ... @@ -302,70 +302,48 @@
302 302  == 2.3  Uplink Payload ==
303 303  
304 304  
305 -The uplink payload includes 26 bytes in total by default.
325 +The uplink payload includes 23 bytes in total by default.
306 306  
307 307  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.
308 308  
309 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
310 310  
311 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
312 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:60px" %)**1**|(% style="width:90px" %)**3**|(% style="width:100px" %)**3**
313 -|=(% 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.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
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"]]
314 314  
315 -(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
316 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
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" %)(((
317 317  **1-32 group**
318 318  )))
319 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% 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" %)...
320 320  
321 -(% 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.
322 322  
342 +[[image:1670406261143-723.png]]
323 323  
324 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
325 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:45px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:60px" %)**1**|(% style="width:60px" %)**1**|(% style="width:87px" %)**3**|(% style="width:80px" %)**3**
326 -|=(% 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(pb14)|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb14)|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
327 327  
328 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
329 -|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:75px" %)**1**|(% style="width:75px" %)**3**
330 -|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% 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__(%%)**
331 331  
332 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
333 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
334 -**1-32 group**
335 -)))
336 -|(% style="width:102px" %)last open time(pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:100px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......
337 -
338 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
339 -
340 -[[image:image-20221117145932-2.png]]
341 -
342 -
343 -The payload is ASCII string, representative same HEX:
344 -
345 -**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__(%%)**
346 -
347 347  **where:**
348 348  
349 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
349 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
350 350  
351 351  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
352 352  
353 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
353 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
354 354  
355 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
355 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
356 356  
357 357  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
358 358  
359 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
359 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
360 360  
361 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
361 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
362 362  
363 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
363 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
364 364  
365 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
365 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
366 366  
367 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
368 -
369 369  == 2.4  Payload Explanation and Sensor Interface ==
370 370  
371 371  === 2.4.1  Device ID ===
... ... @@ -387,13 +387,13 @@
387 387  
388 388  Specify the software version: 0x64=100, which means firmware version 1.00.
389 389  
390 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
388 +For example 0x00 64 : This device is NMDS200 with firmware version 1.0.0.
391 391  
392 392  
393 393  === 2.4.3  Battery Info ===
394 394  
395 395  
396 -Check the battery voltage for NDS03A.
394 +Check the battery voltage for NMDS200.
397 397  
398 398  Ex1: 0x0B45 = 2885mV
399 399  
... ... @@ -405,51 +405,49 @@
405 405  
406 406  NB-IoT Network signal Strength.
407 407  
408 -**Ex1: 0x1d = 29**
406 +(% style="color:blue" %)**Ex1: 0x1d = 29**
409 409  
410 -**0**  -113dBm or less
408 +(% style="color:#037691" %)**0** (%%) -113dBm or less
411 411  
412 -**1**  -111dBm
410 +(% style="color:#037691" %)**1**  (%%) -111dBm
413 413  
414 -**2...30** -109dBm... -53dBm
412 +(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
415 415  
416 -**31**   -51dBm or greater
414 +(% style="color:#037691" %)**31** (%%) -51dBm or greater
417 417  
418 -**99**    Not known or not detectable
416 +(% style="color:#037691" %)**99** (%%) Not known or not detectable
419 419  
420 420  
421 -=== 2.4.5  Disalarm: (default: 0) ===
419 +=== 2.4.5  Distance ===
422 422  
423 423  
424 -(% 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.
422 +[[image:1670407401682-959.png]]
425 425  
426 -(% 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.
427 427  
428 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
425 +(% style="color:blue" %)**Object1 Distance:**
429 429  
427 +Distance between sensor probe to the first object. (unit: cm)
430 430  
431 -=== 2.4.6  Keep Status & Keep Time ===
429 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
432 432  
431 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
433 433  
434 -Shows the configure value of Alarm Base on Timeout Feature
435 435  
434 +(% style="color:blue" %)**Object2 Distance:**
436 436  
437 -=== 2.4.7  Timestamp ===
436 +Distance between sensor probe to the second object. (unit: cm)
438 438  
439 439  
440 -Timestamp : 0x6315537b =1662342011
439 +=== 2.4.6  Timestamp ===
441 441  
442 442  
443 -=== 2.4.8  Switch Dual Channel Mode ===
442 +Timestamp : 0x6315537b =1662342011
444 444  
445 445  
446 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
447 -
448 -
449 449  == 2.5  Downlink Payload ==
450 450  
451 451  
452 -By default, NDS03A prints the downlink payload to console port.
448 +By default, NMDS200 prints the downlink payload to console port.
453 453  
454 454  [[image:image-20221021111414-18.png]] ​
455 455  
... ... @@ -466,7 +466,7 @@
466 466  
467 467  * (% style="color:#037691" %)**Reset**
468 468  
469 -If payload = 0x04FF, it will reset the NDS03A
465 +If payload = 0x04FF, it will reset the NMDS200
470 470  
471 471  * (% style="color:#037691" %)**INTMOD**
472 472  
... ... @@ -476,112 +476,32 @@
476 476  == 2.6  ​LED Indicator ==
477 477  
478 478  
479 -The NDS03A 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.
480 480  
481 481  * When the device starts normally, the LED will light up for 1 second.
482 -* After NDS03A 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.
483 483  * For each uplink probe, LED will be on for 500ms.
484 484  
485 -== 2.7  Alarm Base on Timeout ==
481 +== 2.7  Distance alarm function ==
486 486  
487 487  
488 -NDS03A 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:
484 +(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
489 489  
486 +(% style="color:#037691" %)**Example 1:**
490 490  
491 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
488 +AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
492 492  
493 -Keep Status = 1: Monitor Close to Open event
490 +AT+ ALARM2 =min,max
494 494  
495 -Keep Status = 0: Monitor Open to Close event
496 496  
493 +(% style="color:#037691" %)**Example 2:**
497 497  
498 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
495 +AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
499 499  
500 -Range 0 ~~ 65535(0xFFFF) seconds.
501 501  
502 -If keep time = 0, Disable Alarm Base on Timeout feature.
498 +== 2.8  Set the number of data to be uploaded and the recording time ==
503 503  
504 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
505 505  
506 -
507 -(% style="color:blue" %)**AT Command to configure:**
508 -
509 -(% style="color:blue" %)**PB14 PIN:**
510 -
511 -(% 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. NDS03A 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.
512 -
513 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
514 -
515 -
516 -(% style="color:blue" %)**PB15 PIN:**
517 -
518 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
519 -
520 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
521 -
522 -
523 -== 2.8  Set debug mode ==
524 -
525 -
526 -Feature: Enable or Disable debug mode
527 -
528 -(% style="color:blue" %)**AT Command: AT+DEBUG**
529 -
530 -[[image:image-20221021111629-21.png]]
531 -
532 -
533 -
534 -== 2.9  Clear Flash Record ==
535 -
536 -
537 -Feature: Clear flash storage for data log feature.
538 -
539 -(% style="color:blue" %)**AT Command: AT+CLRDTA**
540 -
541 -[[image:image-20221021111527-19.png]]
542 -
543 -
544 -== 2.10  Count Mod ==
545 -
546 -
547 -(% style="color:blue" %)**AT Command: AT+COUNTMOD**
548 -
549 -[[image:image-20221118092935-1.png]]
550 -
551 -
552 -== 2.11  Interrupt Pin Channel Mod ==
553 -
554 -
555 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
556 -
557 -[[image:image-20221118093144-2.png]]
558 -
559 -
560 -== 2.12 TTRIG1/2 timeout status alarm ==
561 -
562 -
563 -It needs to be used with AT+TTRIG1 or AT+TTRIG2. When TTRIG1 or TTRIG2 times out and causes an alarm, and the status does not change subsequently, an alarm packet will be sent at the alarm interval.
564 -
565 -(% style="color:blue" %)**AT Command: AT+TTRALARM**
566 -
567 -[[image:image-20221118093512-3.png]]
568 -
569 -
570 -== 2.13  Select counting mode ==
571 -
572 -
573 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
574 -
575 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
576 -
577 -When (% style="color:red" %)**b=0**(%%), it is the last door open duration, and when (% style="color:red" %)**b=1**(%%),the last door close duration.
578 -
579 -[[image:image-20221118093658-4.png]]
580 -
581 -
582 -== 2.14  Set the number of data to be uploaded and the recording time ==
583 -
584 -
585 585  (% style="color:blue" %)**AT Command:**
586 586  
587 587  (% 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)
... ... @@ -589,7 +589,7 @@
589 589  (% 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.
590 590  
591 591  
592 -== 2.15  Read or Clear cached data ==
508 +== 2.9  Read or Clear cached data ==
593 593  
594 594  
595 595  (% style="color:blue" %)**AT Command:**
... ... @@ -598,71 +598,25 @@
598 598  
599 599  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
600 600  
601 -[[image:image-20221118094227-5.png]]
517 +[[image:1670408172929-569.png]]
602 602  
603 603  
604 -== 2.16  ​Firmware Change Log ==
520 +== 2.10  ​Firmware Change Log ==
605 605  
606 606  
607 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
523 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0>>https://www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0]]
608 608  
609 609  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
610 610  
611 611  
612 -== 2.17  ​Battery Analysis ==
528 +== 2.11 Battery & Power Consumption ==
613 613  
614 -=== 2.17.1  ​Battery Type ===
615 615  
531 +NMDS200 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
616 616  
617 -The NDS03A 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.
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/]] .
618 618  
619 -The battery is designed to last for several years depends on the actual use environment and update interval. 
620 620  
621 -The battery-related documents as below:
622 -
623 -* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
624 -
625 -* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
626 -
627 -* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
628 -
629 -[[image:image-20221021111911-26.png]] ​
630 -
631 -
632 -=== 2.17.2  Power consumption Analyze ===
633 -
634 -
635 -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.
636 -
637 -Instruction to use as below:
638 -
639 -(% 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/]]
640 -
641 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
642 -
643 -* Product Model
644 -
645 -* Uplink Interval
646 -
647 -* Working Mode
648 -
649 -And the Life expectation in difference case will be shown on the right.
650 -
651 -[[image:1666596205057-567.png]] ​
652 -
653 -
654 -=== 2.17.3  ​Battery Note ===
655 -
656 -
657 -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.
658 -
659 -
660 -=== 2.17.4  Replace the battery ===
661 -
662 -
663 -The default battery pack of NDS03A 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).
664 -
665 -
666 666  = 3. ​ Access NB-IoT Module =
667 667  
668 668  
... ... @@ -706,65 +706,59 @@
706 706  
707 707  AT+INTMOD            : Set the trigger interrupt mode
708 708  
709 -AT+5VT  : Set extend the time of 5V power  
579 +AT+5VT  : Set extend the time of 5V power  
710 710  
711 -AT+PRO  : Choose agreement
581 +AT+PRO  : Choose agreement
712 712  
713 -AT+RXDL  : Extend the sending and receiving time
583 +AT+RXDL  : Extend the sending and receiving time
714 714  
715 -AT+SERVADDR  : Server Address
585 +AT+SERVADDR  : Server Address
716 716  
717 -AT+TR      :  Get or Set record time
587 +AT+TR      :  Get or Set record time
718 718  
719 -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
720 720  
721 721  AT+CDP     :  Read or Clear cached data
722 722  
723 -AT+ DEBUG   : Enable or Disable debug mode
593 +AT+DEBUG:  Enable or Disable debug mode
724 724  
725 -AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
595 +AT+ALARM1:  Get or Set alarm of distance1
726 726  
727 -AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
597 +AT+ALARM2:  Get or Set alarm of distance2
728 728  
729 -AT+COUNTMOD  :  Get or Set the count mode
599 +AT+GETSENSORVALUE :  Returns the current sensor measurement
730 730  
731 -AT+TTRCHANNEL  : Get or Set the number of interrupt channels
601 +AT+POWERIC :  Get or set the Power IC flag
732 732  
733 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
734 734  
735 -AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
736 -
737 -AT+ CLRC   :  Clear current door open count
738 -
739 -
740 740  (% style="color:blue" %)**COAP Management**      
741 741  
742 -AT+URI            : Resource parameters
606 +AT+URI :  Resource parameters
743 743  
744 744  
745 745  (% style="color:blue" %)**UDP Management**
746 746  
747 -AT+CFM          : Upload confirmation mode (only valid for UDP)
611 +AT+CFM :  Upload confirmation mode (only valid for UDP)
748 748  
749 749  
750 750  (% style="color:blue" %)**MQTT Management**
751 751  
752 -AT+CLIENT               : Get or Set MQTT client
616 +AT+CLIENT  : Get or Set MQTT client
753 753  
754 -AT+UNAME  : Get or Set MQTT Username
618 +AT+UNAME : Get or Set MQTT Username
755 755  
756 -AT+PWD                  : Get or Set MQTT password
620 +AT+PWD  :  Get or Set MQTT password
757 757  
758 -AT+PUBTOPIC  : Get or Set MQTT publish topic
622 +AT+PUBTOPIC :  Get or Set MQTT publish topic
759 759  
760 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
624 +AT+SUBTOPIC :  Get or Set MQTT subscription topic
761 761  
762 762  
763 763  (% style="color:blue" %)**Information**          
764 764  
765 -AT+FDR  : Factory Data Reset
629 +AT+FDR :  Factory Data Reset
766 766  
767 -AT+PWORD  : Serial Access Password
631 +AT+PWORD :  Serial Access Password
768 768  
769 769  
770 770  = ​5.  FAQ =
... ... @@ -776,7 +776,7 @@
776 776  
777 777  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]]
778 778  
779 -(% style="color:red" %)**Notice: **(% style="color:blue" %)**NDS03A** (%%)**and (% style="color:blue" %)LDS03A(%%)**(% 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.**
780 780  
781 781  
782 782  = 6.  Trouble Shooting =
... ... @@ -793,10 +793,16 @@
793 793  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.
794 794  
795 795  
660 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
661 +
662 +
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]]//**.
664 +
665 +
796 796  = 7. ​ Order Info =
797 797  
798 798  
799 -Part Number**:** NDS03A
669 +Part Number:(% style="color:blue" %)** NMDS200**
800 800  
801 801  
802 802  = 8.  Packing Info =
... ... @@ -804,8 +804,9 @@
804 804  
805 805  (% style="color:blue" %)**Package Includes**:
806 806  
807 -* NDS03A Open/Close Door Sensor x 1
677 +* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
808 808  
679 +
809 809  = 9.  Support =
810 810  
811 811  
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
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