Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 90.2 >
edited by Xiaoling
on 2022/12/12 17:19
To version < 79.1 >
edited by Xiaoling
on 2022/12/07 17:40
>
Change comment: Uploaded new attachment "1670406036256-101.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,28 +1,13 @@
1 1  (% style="text-align:center" %)
2 -[[image:LMDS200_10.jpg||height="572" width="572"]]
2 +[[image:LMDS200_10.jpg]]
3 3  
4 4  
5 -
6 -
7 -
8 -(% style="display:none" %) (%%)
9 -
10 -
11 -
12 -
13 -
14 14  **Table of Contents：**
15 15  
16 -{{toc/}}
17 17  
18 18  
19 19  
20 20  
21 -
22 -
23 -
24 -
25 -
26 26  = 1.  Introduction =
27 27  
28 28  == 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
... ... @@ -30,37 +30,25 @@
30 30  
31 31  (((
32 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 -)))
34 34  
35 -(((
19 +
36 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.
37 -)))
38 38  
39 -(((
40 40  NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
41 -)))
42 42  
43 -(((
44 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.
45 -)))
46 46  
47 -(((
48 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.
49 -)))
50 50  
51 -(((
52 52  NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
53 -)))
54 54  
55 -(((
56 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 -)))
58 58  
59 -(((
60 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 61  )))
62 62  
63 63  
36 +
64 64  == ​1.2  Features ==
65 65  
66 66  
... ... @@ -84,9 +84,9 @@
84 84  
85 85  
86 86  * Measuring Method: FMCW
87 -* Frequency: 24.000 ~~ 24.500 GHz
60 +* Frequency: 24.000 24.500 GHz
88 88  * Measurement output power: 6dBm
89 -* Measure range: 0.5 ~~ 20m
62 +* Measure range: 0.5 20m
90 90  * Accuracy: ±0.1m
91 91  * Resolution: 0.01m
92 92  * Horizontal Angel: 78°
... ... @@ -94,6 +94,7 @@
94 94  
95 95  
96 96  
70 +
97 97  == 1.4  Storage Temperature ==
98 98  
99 99  
... ... @@ -100,9 +100,13 @@
100 100   -40°C to +85°C
101 101  
102 102  
77 +
78 +
79 +
103 103  == 1.5 ​ Applications ==
104 104  
105 105  
83 +
106 106  * Horizontal distance measurement
107 107  * Liquid level measurement
108 108  * Parking management system
... ... @@ -140,12 +140,10 @@
140 140  Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
141 141  
142 142  
143 -[[image:image-20221207170748-1.png]]
121 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
144 144  
145 145  
146 - [[image:image-20221207170748-2.png||height="345" width="634"]]
147 147  
148 -
149 149  == 1.8  Pin Definitions and Switch ==
150 150  
151 151  
... ... @@ -161,7 +161,7 @@
161 161  
162 162  The diagram below shows the working flow in the default firmware of NMDS200:
163 163  
164 -[[image:image-20221021110615-5.png||height="996" width="492"]]
140 +[[image:image-20221021110615-5.png]]
165 165  
166 166  
167 167  == 2.2 ​ Configure NMDS200 ==
... ... @@ -175,7 +175,7 @@
175 175  
176 176  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.
177 177  
178 -[[image:image-20221209090938-1.png]]
154 +[[image:image-20221207173300-4.png]]
179 179  
180 180  
181 181  === 2.2.1 Insert NB-IoT SIM card ===
... ... @@ -188,10 +188,10 @@
188 188  [[image:image-20221021110745-6.png]] ​
189 189  
190 190  
191 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
167 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
192 192  
193 193  
194 -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.
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.
195 195  
196 196  (% style="color:blue" %)**Connection:**
197 197  
... ... @@ -214,23 +214,24 @@
214 214  
215 215  * Flow Control: (% style="color:red" %)**None**
216 216  
217 -Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
193 +Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
218 218  
219 219  ​[[image:image-20221021110817-7.png]]
220 220  
221 -NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
197 +NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
222 222  
223 223  
224 224  (% 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]]
225 225  
226 226  
227 -=== 2.2.3 Use CoAP protocol to uplink data ===
228 228  
204 +=== 2.2.4 Use CoAP protocol to uplink data ===
229 229  
206 +
230 230  (% 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/]]
231 231  
232 232  
233 -(% style="color:blue" %)**Use below commands in NMDS200:**
210 +(% style="color:blue" %)**Use below commands in NDS03A:**
234 234  
235 235  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
236 236  
... ... @@ -240,15 +240,15 @@
240 240  
241 241  For parameter description, please refer to AT command set
242 242  
243 -[[image:1670471530120-960.png||height="647" width="674"]]
220 +[[image:image-20221021110948-8.png]]
244 244  
245 245  
246 -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.
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.
247 247  
248 -[[image:1670405841875-916.png]] ​
225 +[[image:image-20221118103547-9.png||height="605" width="837"]] ​
249 249  
250 250  
251 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
228 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
252 252  
253 253  
254 254  (% style="color:blue" %)**AT Commands:**
... ... @@ -259,7 +259,7 @@
259 259  
260 260  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
261 261  
262 -​ [[image:1670471559211-638.png]]
239 +​ [[image:image-20221021111025-10.png]]
263 263  
264 264  
265 265  [[image:image-20221021111033-11.png||height="241" width="576"]]
... ... @@ -266,7 +266,7 @@
266 266  
267 267  ​
268 268  
269 -=== 2.2.5 Use MQTT protocol to uplink data ===
246 +=== 2.2.6 Use MQTT protocol to uplink data ===
270 270  
271 271  
272 272  (% style="color:blue" %)**AT Commands:**
... ... @@ -285,10 +285,10 @@
285 285  
286 286  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
287 287  
288 -​ [[image:1670471584490-640.png]]
265 +​ [[image:image-20221118103445-7.png]]
289 289  
290 290  
291 -[[image:1670405928926-116.png]]
268 +[[image:image-20221118103453-8.png||height="608" width="841"]]
292 292  
293 293  ​
294 294  
... ... @@ -295,7 +295,7 @@
295 295  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.
296 296  
297 297  
298 -=== 2.2.6 Use TCP protocol to uplink data ===
275 +=== 2.2.7 Use TCP protocol to uplink data ===
299 299  
300 300  
301 301  (% style="color:blue" %)**AT Commands:**
... ... @@ -304,19 +304,18 @@
304 304  
305 305  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
306 306  
307 -​ [[image:1670471613823-833.png]]
284 +​ [[image:image-20221021111125-14.png]]
308 308  
309 -
310 310  [[image:image-20221021111131-15.png]]
311 311  
312 312  ​
313 313  
314 -=== 2.2.7 Change Update Interval ===
290 +=== 2.2.8 Change Update Interval ===
315 315  
316 316  
317 317  User can use below command to change the (% style="color:blue" %)**uplink interval**.
318 318  
319 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
295 +* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
320 320  
321 321  (% style="color:red" %)**NOTE:**
322 322  
... ... @@ -326,52 +326,70 @@
326 326  == 2.3  Uplink Payload ==
327 327  
328 328  
329 -The uplink payload includes 23 bytes in total by default.
305 +The uplink payload includes 26 bytes in total by default.
330 330  
331 331  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.
332 332  
309 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
333 333  
334 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:450px" %)
335 -|=(% 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**
336 -|=(% 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"]]
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)
337 337  
338 -(% border="1" style="background-color:#ffffcc; color:green; width:429px" %)
339 -|(% style="width:60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)(((
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" %)(((
340 340  **1-32 group**
341 341  )))
342 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)...
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" %)...
343 343  
344 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
321 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
345 345  
346 -[[image:1670406261143-723.png]]
347 347  
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)
348 348  
349 -The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
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)
350 350  
351 -**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__(%%)**
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" %)......
352 352  
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 +
353 353  **where:**
354 354  
355 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
349 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
356 356  
357 357  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
358 358  
359 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
353 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
360 360  
361 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
355 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
362 362  
363 363  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
364 364  
365 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
359 +* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
366 366  
367 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
361 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
368 368  
369 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
363 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
370 370  
371 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
365 +* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
372 372  
367 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
373 373  
374 -
375 375  == 2.4  Payload Explanation and Sensor Interface ==
376 376  
377 377  === 2.4.1  Device ID ===
... ... @@ -393,13 +393,13 @@
393 393  
394 394  Specify the software version: 0x64=100, which means firmware version 1.00.
395 395  
396 -For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
390 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
397 397  
398 398  
399 399  === 2.4.3  Battery Info ===
400 400  
401 401  
402 -Check the battery voltage for NMDS200.
396 +Check the battery voltage for NDS03A.
403 403  
404 404  Ex1: 0x0B45 = 2885mV
405 405  
... ... @@ -411,49 +411,51 @@
411 411  
412 412  NB-IoT Network signal Strength.
413 413  
414 -(% style="color:blue" %)**Ex1: 0x1d = 29**
408 +**Ex1: 0x1d = 29**
415 415  
416 -(% style="color:#037691" %)**0** (%%) -113dBm or less
410 +**0**  -113dBm or less
417 417  
418 -(% style="color:#037691" %)**1**  (%%) -111dBm
412 +**1**  -111dBm
419 419  
420 -(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
414 +**2...30** -109dBm... -53dBm
421 421  
422 -(% style="color:#037691" %)**31** (%%) -51dBm or greater
416 +**31**   -51dBm or greater
423 423  
424 -(% style="color:#037691" %)**99** (%%) Not known or not detectable
418 +**99**    Not known or not detectable
425 425  
426 426  
427 -=== 2.4.5  Distance ===
421 +=== 2.4.5  Disalarm: (default: 0) ===
428 428  
429 429  
430 -[[image:1670407401682-959.png]]
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.
431 431  
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.
432 432  
433 -(% style="color:blue" %)**Object1 Distance:**
428 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
434 434  
435 -Distance between sensor probe to the first object. (unit: cm)
436 436  
437 -For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
431 +=== 2.4.6  Keep Status & Keep Time ===
438 438  
439 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
440 440  
434 +Shows the configure value of Alarm Base on Timeout Feature
441 441  
442 -(% style="color:blue" %)**Object2 Distance:**
443 443  
444 -Distance between sensor probe to the second object. (unit: cm)
437 +=== 2.4.7  Timestamp ===
445 445  
446 446  
447 -=== 2.4.6  Timestamp ===
440 +Timestamp : 0x6315537b =1662342011
448 448  
449 449  
450 -Timestamp : 0x6315537b =1662342011
443 +=== 2.4.8  Switch Dual Channel Mode ===
451 451  
452 452  
446 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
447 +
448 +
453 453  == 2.5  Downlink Payload ==
454 454  
455 455  
456 -By default, NMDS200 prints the downlink payload to console port.
452 +By default, NDS03A prints the downlink payload to console port.
457 457  
458 458  [[image:image-20221021111414-18.png]] ​
459 459  
... ... @@ -470,7 +470,7 @@
470 470  
471 471  * (% style="color:#037691" %)**Reset**
472 472  
473 -If payload = 0x04FF, it will reset the NMDS200
469 +If payload = 0x04FF, it will reset the NDS03A
474 474  
475 475  * (% style="color:#037691" %)**INTMOD**
476 476  
... ... @@ -480,34 +480,112 @@
480 480  == 2.6  ​LED Indicator ==
481 481  
482 482  
483 -The NMDS200 has an internal LED which is to show the status of different states.
479 +The NDS03A has an internal LED which is to show the status of different states.
484 484  
485 485  * When the device starts normally, the LED will light up for 1 second.
486 -* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
482 +* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
487 487  * For each uplink probe, LED will be on for 500ms.
488 488  
485 +== 2.7  Alarm Base on Timeout ==
489 489  
490 490  
491 -== 2.7  Distance alarm function ==
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:
492 492  
493 493  
494 -(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
491 +(% style="color:blue" %)**1. Keep Status: Status to be monitor**
495 495  
496 -(% style="color:#037691" %)**Example 1:**
493 +Keep Status = 1: Monitor Close to Open event
497 497  
498 -AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
495 +Keep Status = 0: Monitor Open to Close event
499 499  
500 -AT+ ALARM2 =min,max
501 501  
498 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
502 502  
503 -(% style="color:#037691" %)**Example 2:**
500 +Range 0 ~~ 65535(0xFFFF) seconds.
504 504  
505 -AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
502 +If keep time = 0, Disable Alarm Base on Timeout feature.
506 506  
504 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
507 507  
508 -== 2.8  Set the number of data to be uploaded and the recording time ==
509 509  
507 +(% style="color:blue" %)**AT Command to configure:**
510 510  
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 +
511 511  (% style="color:blue" %)**AT Command:**
512 512  
513 513  (% 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)
... ... @@ -515,7 +515,7 @@
515 515  (% 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.
516 516  
517 517  
518 -== 2.9  Read or Clear cached data ==
592 +== 2.15  Read or Clear cached data ==
519 519  
520 520  
521 521  (% style="color:blue" %)**AT Command:**
... ... @@ -524,10 +524,10 @@
524 524  
525 525  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
526 526  
527 -[[image:1670408172929-569.png]]
601 +[[image:image-20221118094227-5.png]]
528 528  
529 529  
530 -== 2.10  ​Firmware Change Log ==
604 +== 2.16  ​Firmware Change Log ==
531 531  
532 532  
533 533  Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
... ... @@ -535,12 +535,12 @@
535 535  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
536 536  
537 537  
538 -== 2.11  ​Battery Analysis ==
612 +== 2.17  ​Battery Analysis ==
539 539  
540 -=== 2.11.1  ​Battery Type ===
614 +=== 2.17.1  ​Battery Type ===
541 541  
542 542  
543 -The NMDS200 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
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.
544 544  
545 545  The battery is designed to last for several years depends on the actual use environment and update interval. 
546 546  
... ... @@ -555,7 +555,7 @@
555 555  [[image:image-20221021111911-26.png]] ​
556 556  
557 557  
558 -=== 2.11.2  Power consumption Analyze ===
632 +=== 2.17.2  Power consumption Analyze ===
559 559  
560 560  
561 561  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.
... ... @@ -577,16 +577,16 @@
577 577  [[image:1666596205057-567.png]] ​
578 578  
579 579  
580 -=== 2.11.3  ​Battery Note ===
654 +=== 2.17.3  ​Battery Note ===
581 581  
582 582  
583 583  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.
584 584  
585 585  
586 -=== 2.11.4  Replace the battery ===
660 +=== 2.17.4  Replace the battery ===
587 587  
588 588  
589 -The default battery pack of NMDS200 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
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).
590 590  
591 591  
592 592  = 3. ​ Access NB-IoT Module =
... ... @@ -632,59 +632,65 @@
632 632  
633 633  AT+INTMOD            : Set the trigger interrupt mode
634 634  
635 -AT+5VT  : Set extend the time of 5V power  
709 +AT+5VT  : Set extend the time of 5V power  
636 636  
637 -AT+PRO  : Choose agreement
711 +AT+PRO  : Choose agreement
638 638  
639 -AT+RXDL  : Extend the sending and receiving time
713 +AT+RXDL  : Extend the sending and receiving time
640 640  
641 -AT+SERVADDR  : Server Address
715 +AT+SERVADDR  : Server Address
642 642  
643 -AT+TR      :  Get or Set record time
717 +AT+TR      :  Get or Set record time
644 644  
645 -AT+NOUD :  Get or Set the number of data to be uploaded
719 +AT+NOUD      : Get or Set the number of data to be uploaded
646 646  
647 647  AT+CDP     :  Read or Clear cached data
648 648  
649 -AT+DEBUG:  Enable or Disable debug mode
723 +AT+ DEBUG   : Enable or Disable debug mode
650 650  
651 -AT+ALARM1:  Get or Set alarm of distance1
725 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
652 652  
653 -AT+ALARM2:  Get or Set alarm of distance2
727 +AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
654 654  
655 -AT+GETSENSORVALUE :  Returns the current sensor measurement
729 +AT+COUNTMOD  :  Get or Set the count mode
656 656  
657 -AT+POWERIC :  Get or set the Power IC flag
731 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
658 658  
733 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
659 659  
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 +
660 660  (% style="color:blue" %)**COAP Management**      
661 661  
662 -AT+URI :  Resource parameters
742 +AT+URI            : Resource parameters
663 663  
664 664  
665 665  (% style="color:blue" %)**UDP Management**
666 666  
667 -AT+CFM :  Upload confirmation mode (only valid for UDP)
747 +AT+CFM          : Upload confirmation mode (only valid for UDP)
668 668  
669 669  
670 670  (% style="color:blue" %)**MQTT Management**
671 671  
672 -AT+CLIENT  : Get or Set MQTT client
752 +AT+CLIENT               : Get or Set MQTT client
673 673  
674 -AT+UNAME : Get or Set MQTT Username
754 +AT+UNAME  : Get or Set MQTT Username
675 675  
676 -AT+PWD  :  Get or Set MQTT password
756 +AT+PWD                  : Get or Set MQTT password
677 677  
678 -AT+PUBTOPIC :  Get or Set MQTT publish topic
758 +AT+PUBTOPIC  : Get or Set MQTT publish topic
679 679  
680 -AT+SUBTOPIC :  Get or Set MQTT subscription topic
760 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
681 681  
682 682  
683 683  (% style="color:blue" %)**Information**          
684 684  
685 -AT+FDR :  Factory Data Reset
765 +AT+FDR  : Factory Data Reset
686 686  
687 -AT+PWORD :  Serial Access Password
767 +AT+PWORD  : Serial Access Password
688 688  
689 689  
690 690  = ​5.  FAQ =
... ... @@ -696,7 +696,7 @@
696 696  
697 697  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]]
698 698  
699 -(% 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.**
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.**
700 700  
701 701  
702 702  = 6.  Trouble Shooting =
... ... @@ -716,7 +716,7 @@
716 716  = 7. ​ Order Info =
717 717  
718 718  
719 -Part Number:(% style="color:blue" %)** NMDS200**
799 +Part Number**:** NDS03A
720 720  
721 721  
722 722  = 8.  Packing Info =
... ... @@ -724,10 +724,8 @@
724 724  
725 725  (% style="color:blue" %)**Package Includes**:
726 726  
727 -* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
807 +* NDS03A Open/Close Door Sensor x 1
728 728  
729 -
730 -
731 731  = 9.  Support =
732 732  
733 733  
1670406261143-723.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.9 KB
Content
1670407401682-959.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -23.7 KB
Content
1670408172929-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -211.8 KB
Content
1670471530120-960.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -67.6 KB
Content
1670471559211-638.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -170.6 KB
Content
1670471584490-640.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -91.1 KB
Content
1670471613823-833.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.0 KB
Content
image-20221208090742-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.7 KB
Content
image-20221209090938-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -121.9 KB
Content
image-20221212171610-1.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -756.0 KB
Content

Applications

Navigation

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