Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 83.8 >
edited by Xiaoling
on 2022/12/08 11:29
To version < 76.1 >
edited by Xiaoling
on 2022/12/07 17:33
>
Change comment: Uploaded new attachment "image-20221207173300-4.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -4,7 +4,6 @@
4 4  
5 5  **Table of Contents：**
6 6  
7 -{{toc/}}
8 8  
9 9  
10 10  
... ... @@ -17,6 +17,7 @@
17 17  (((
18 18  The Dragino NMDS200 is a(% style="color:blue" %)** NB-IoT Microwave Radar distance sensor**(%%). It uses (% style="color:blue" %)**24Ghz Microwave**(%%) to detect the distance between sensor and different objects. Compare vs ultrasonic or Lidar measurement method, Microwave Radar is (% style="color:blue" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or thick dust on top of the sensor.
19 19  
19 +
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.
21 21  
22 22  NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
... ... @@ -33,6 +33,7 @@
33 33  )))
34 34  
35 35  
36 +
36 36  == ​1.2  Features ==
37 37  
38 38  
... ... @@ -50,6 +50,8 @@
50 50  * Micro SIM card slot for NB-IoT SIM
51 51  * 8500mAh Battery for long-term use
52 52  
54 +
55 +
53 53  == 1.3 Radar probe specification ==
54 54  
55 55  
... ... @@ -62,6 +62,9 @@
62 62  * Horizontal Angel: 78°
63 63  * Vertical Angel: 23°
64 64  
68 +
69 +
70 +
65 65  == 1.4  Storage Temperature ==
66 66  
67 67  
... ... @@ -68,9 +68,13 @@
68 68   -40°C to +85°C
69 69  
70 70  
77 +
78 +
79 +
71 71  == 1.5 ​ Applications ==
72 72  
73 73  
83 +
74 74  * Horizontal distance measurement
75 75  * Liquid level measurement
76 76  * Parking management system
... ... @@ -81,6 +81,8 @@
81 81  * Sewer
82 82  * Bottom water level monitoring
83 83  
94 +
95 +
84 84  == 1.6  Specification ==
85 85  
86 86  
... ... @@ -98,6 +98,8 @@
98 98  * B20 @H-FDD: 800MHz
99 99  * B28 @H-FDD: 700MHz
100 100  
113 +
114 +
101 101  == 1.7  Installation ==
102 102  
103 103  
... ... @@ -126,21 +126,23 @@
126 126  [[image:image-20221021110615-5.png]]
127 127  
128 128  
129 -== 2.2 ​ Configure NMDS200 ==
143 +== 2.2 ​ Configure NDS03A ==
130 130  
145 +=== 2.2.1 Test Requirement ===
131 131  
132 -To use NMDS200 in your city, make sure to meet below requirements:
133 133  
148 +To use NDS03A in your city, make sure to meet below requirements:
149 +
134 134  * Your local operator has already distributed an NB-IoT Network.
135 -* The local NB-IoT network used the band that NMDS200 supports.
151 +* The local NB-IoT network used the band that NDS03A supports.
136 136  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
137 137  
138 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NMDS200 will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
154 +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.
139 139  
140 -[[image:image-20221208090742-1.png]]
156 +[[image:image-20221117142300-1.png]]
141 141  
142 142  
143 -=== 2.2.1 Insert NB-IoT SIM card ===
159 +=== 2.2.2 Insert NB-IoT SIM card ===
144 144  
145 145  
146 146  Insert the NB-IoT Card get from your provider.
... ... @@ -150,10 +150,10 @@
150 150  [[image:image-20221021110745-6.png]] ​
151 151  
152 152  
153 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
169 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
154 154  
155 155  
156 -User need to configure NMDS200 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NMDS200 support AT Commands, user can use a USB to TTL adapter to connect to NMDS200 and use AT Commands to configure it, as below.
172 +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.
157 157  
158 158  (% style="color:blue" %)**Connection:**
159 159  
... ... @@ -176,11 +176,11 @@
176 176  
177 177  * Flow Control: (% style="color:red" %)**None**
178 178  
179 -Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
195 +Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
180 180  
181 181  ​[[image:image-20221021110817-7.png]]
182 182  
183 -NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
199 +NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
184 184  
185 185  
186 186  (% 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]]
... ... @@ -187,13 +187,13 @@
187 187  
188 188  
189 189  
190 -=== 2.2.3 Use CoAP protocol to uplink data ===
206 +=== 2.2.4 Use CoAP protocol to uplink data ===
191 191  
192 192  
193 193  (% 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/]]
194 194  
195 195  
196 -(% style="color:blue" %)**Use below commands in NMDS200:**
212 +(% style="color:blue" %)**Use below commands in NDS03A:**
197 197  
198 198  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
199 199  
... ... @@ -206,12 +206,12 @@
206 206  [[image:image-20221021110948-8.png]]
207 207  
208 208  
209 -After configuring the server address and (% style="color:green" %)**reset NMDS200**(%%) (via AT+ATZ ), NMDS200 will start to uplink sensor values to the CoAP server.
225 +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.
210 210  
211 -[[image:1670405841875-916.png]] ​
227 +[[image:image-20221118103547-9.png||height="605" width="837"]] ​
212 212  
213 213  
214 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
230 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
215 215  
216 216  
217 217  (% style="color:blue" %)**AT Commands:**
... ... @@ -229,7 +229,7 @@
229 229  
230 230  ​
231 231  
232 -=== 2.2.5 Use MQTT protocol to uplink data ===
248 +=== 2.2.6 Use MQTT protocol to uplink data ===
233 233  
234 234  
235 235  (% style="color:blue" %)**AT Commands:**
... ... @@ -251,7 +251,7 @@
251 251  ​ [[image:image-20221118103445-7.png]]
252 252  
253 253  
254 -[[image:1670405928926-116.png]]
270 +[[image:image-20221118103453-8.png||height="608" width="841"]]
255 255  
256 256  ​
257 257  
... ... @@ -258,7 +258,7 @@
258 258  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.
259 259  
260 260  
261 -=== 2.2.6 Use TCP protocol to uplink data ===
277 +=== 2.2.7 Use TCP protocol to uplink data ===
262 262  
263 263  
264 264  (% style="color:blue" %)**AT Commands:**
... ... @@ -267,19 +267,18 @@
267 267  
268 268  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
269 269  
270 -​ [[image:1670406036256-101.png||height="676" width="713"]]
286 +​ [[image:image-20221021111125-14.png]]
271 271  
272 -
273 273  [[image:image-20221021111131-15.png]]
274 274  
275 275  ​
276 276  
277 -=== 2.2.7 Change Update Interval ===
292 +=== 2.2.8 Change Update Interval ===
278 278  
279 279  
280 280  User can use below command to change the (% style="color:blue" %)**uplink interval**.
281 281  
282 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
297 +* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
283 283  
284 284  (% style="color:red" %)**NOTE:**
285 285  
... ... @@ -289,52 +289,70 @@
289 289  == 2.3  Uplink Payload ==
290 290  
291 291  
292 -The uplink payload includes 23 bytes in total by default.
307 +The uplink payload includes 26 bytes in total by default.
293 293  
294 294  Each time the device uploads a data package. The user can use the AT+NOUD command to upload the recorded data.Up to 32 sets of recorded data can be uploaded.
295 295  
311 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
296 296  
297 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:450px" %)
298 -|=(% 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**
299 -|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Exit flag|(% style="width:94px" %) [[Distance 1>>||anchor="H2.4.5A0Distance"]] |(% style="width:93px" %) [[Distance 2>>||anchor="H2.4.5A0Distance"]]
313 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
314 +|=(% 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**
315 +|=(% 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)
300 300  
301 -(% border="1" style="background-color:#ffffcc; color:green; width:350px" %)
302 -|(% style="width:60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)(((
317 +(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
318 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
303 303  **1-32 group**
304 304  )))
305 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:98px" %)...
321 +|(% 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" %)...
306 306  
307 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
323 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
308 308  
309 -[[image:1670406261143-723.png]]
310 310  
326 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
327 +|=(% 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**
328 +|=(% 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)
311 311  
312 -The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
330 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
331 +|(% 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**
332 +|(% 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)
313 313  
314 -**0x (% style="color:red" %)__f867787050471071__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)**
334 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
335 +|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
336 +**1-32 group**
337 +)))
338 +|(% 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" %)......
315 315  
340 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
341 +
342 +[[image:image-20221117145932-2.png]]
343 +
344 +
345 +The payload is ASCII string, representative same HEX:
346 +
347 +**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__(%%)**
348 +
316 316  **where:**
317 317  
318 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
351 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
319 319  
320 320  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
321 321  
322 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
355 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
323 323  
324 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
357 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
325 325  
326 326  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
327 327  
328 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
361 +* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
329 329  
330 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
363 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
331 331  
332 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
365 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
333 333  
334 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
367 +* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
335 335  
369 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
336 336  
337 -
338 338  == 2.4  Payload Explanation and Sensor Interface ==
339 339  
340 340  === 2.4.1  Device ID ===
... ... @@ -356,13 +356,13 @@
356 356  
357 357  Specify the software version: 0x64=100, which means firmware version 1.00.
358 358  
359 -For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
392 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
360 360  
361 361  
362 362  === 2.4.3  Battery Info ===
363 363  
364 364  
365 -Check the battery voltage for NMDS200.
398 +Check the battery voltage for NDS03A.
366 366  
367 367  Ex1: 0x0B45 = 2885mV
368 368  
... ... @@ -374,49 +374,51 @@
374 374  
375 375  NB-IoT Network signal Strength.
376 376  
377 -(% style="color:blue" %)**Ex1: 0x1d = 29**
410 +**Ex1: 0x1d = 29**
378 378  
379 -(% style="color:#037691" %)**0** (%%) -113dBm or less
412 +**0**  -113dBm or less
380 380  
381 -(% style="color:#037691" %)**1**  (%%) -111dBm
414 +**1**  -111dBm
382 382  
383 -(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
416 +**2...30** -109dBm... -53dBm
384 384  
385 -(% style="color:#037691" %)**31** (%%) -51dBm or greater
418 +**31**   -51dBm or greater
386 386  
387 -(% style="color:#037691" %)**99** (%%) Not known or not detectable
420 +**99**    Not known or not detectable
388 388  
389 389  
390 -=== 2.4.5  Distance ===
423 +=== 2.4.5  Disalarm: (default: 0) ===
391 391  
392 392  
393 -[[image:1670407401682-959.png]]
426 +(% 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.
394 394  
428 +(% 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.
395 395  
396 -(% style="color:blue" %)**Object1 Distance:**
430 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
397 397  
398 -Distance between sensor probe to the first object. (unit: cm)
399 399  
400 -For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
433 +=== 2.4.6  Keep Status & Keep Time ===
401 401  
402 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
403 403  
436 +Shows the configure value of Alarm Base on Timeout Feature
404 404  
405 -(% style="color:blue" %)**Object2 Distance:**
406 406  
407 -Distance between sensor probe to the second object. (unit: cm)
439 +=== 2.4.7  Timestamp ===
408 408  
409 409  
410 -=== 2.4.6  Timestamp ===
442 +Timestamp : 0x6315537b =1662342011
411 411  
412 412  
413 -Timestamp : 0x6315537b =1662342011
445 +=== 2.4.8  Switch Dual Channel Mode ===
414 414  
415 415  
448 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
449 +
450 +
416 416  == 2.5  Downlink Payload ==
417 417  
418 418  
419 -By default, NMDS200 prints the downlink payload to console port.
454 +By default, NDS03A prints the downlink payload to console port.
420 420  
421 421  [[image:image-20221021111414-18.png]] ​
422 422  
... ... @@ -433,7 +433,7 @@
433 433  
434 434  * (% style="color:#037691" %)**Reset**
435 435  
436 -If payload = 0x04FF, it will reset the NMDS200
471 +If payload = 0x04FF, it will reset the NDS03A
437 437  
438 438  * (% style="color:#037691" %)**INTMOD**
439 439  
... ... @@ -443,34 +443,112 @@
443 443  == 2.6  ​LED Indicator ==
444 444  
445 445  
446 -The NMDS200 has an internal LED which is to show the status of different states.
481 +The NDS03A has an internal LED which is to show the status of different states.
447 447  
448 448  * When the device starts normally, the LED will light up for 1 second.
449 -* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
484 +* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
450 450  * For each uplink probe, LED will be on for 500ms.
451 451  
487 +== 2.7  Alarm Base on Timeout ==
452 452  
453 453  
454 -== 2.7  Distance alarm function ==
490 +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:
455 455  
456 456  
457 -(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
493 +(% style="color:blue" %)**1. Keep Status: Status to be monitor**
458 458  
459 -(% style="color:#037691" %)**Example 1:**
495 +Keep Status = 1: Monitor Close to Open event
460 460  
461 -AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
497 +Keep Status = 0: Monitor Open to Close event
462 462  
463 -AT+ ALARM2 =min,max
464 464  
500 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
465 465  
466 -(% style="color:#037691" %)**Example 2:**
502 +Range 0 ~~ 65535(0xFFFF) seconds.
467 467  
468 -AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
504 +If keep time = 0, Disable Alarm Base on Timeout feature.
469 469  
506 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
470 470  
471 -== 2.8  Set the number of data to be uploaded and the recording time ==
472 472  
509 +(% style="color:blue" %)**AT Command to configure:**
473 473  
511 +(% style="color:blue" %)**PB14 PIN:**
512 +
513 +(% 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.
514 +
515 +(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
516 +
517 +
518 +(% style="color:blue" %)**PB15 PIN:**
519 +
520 +(% style="color:#037691" %)**AT+TTRIG2=1,30**
521 +
522 +(% style="color:#037691" %)**AT+TTRIG2=0,0 **
523 +
524 +
525 +== 2.8  Set debug mode ==
526 +
527 +
528 +Feature: Enable or Disable debug mode
529 +
530 +(% style="color:blue" %)**AT Command: AT+DEBUG**
531 +
532 +[[image:image-20221021111629-21.png]]
533 +
534 +
535 +
536 +== 2.9  Clear Flash Record ==
537 +
538 +
539 +Feature: Clear flash storage for data log feature.
540 +
541 +(% style="color:blue" %)**AT Command: AT+CLRDTA**
542 +
543 +[[image:image-20221021111527-19.png]]
544 +
545 +
546 +== 2.10  Count Mod ==
547 +
548 +
549 +(% style="color:blue" %)**AT Command: AT+COUNTMOD**
550 +
551 +[[image:image-20221118092935-1.png]]
552 +
553 +
554 +== 2.11  Interrupt Pin Channel Mod ==
555 +
556 +
557 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
558 +
559 +[[image:image-20221118093144-2.png]]
560 +
561 +
562 +== 2.12 TTRIG1/2 timeout status alarm ==
563 +
564 +
565 +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.
566 +
567 +(% style="color:blue" %)**AT Command: AT+TTRALARM**
568 +
569 +[[image:image-20221118093512-3.png]]
570 +
571 +
572 +== 2.13  Select counting mode ==
573 +
574 +
575 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
576 +
577 +When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
578 +
579 +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.
580 +
581 +[[image:image-20221118093658-4.png]]
582 +
583 +
584 +== 2.14  Set the number of data to be uploaded and the recording time ==
585 +
586 +
474 474  (% style="color:blue" %)**AT Command:**
475 475  
476 476  (% style="color:#037691" %)**AT+TR=900**(%%)  ~/~/  The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
... ... @@ -478,7 +478,7 @@
478 478  (% 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.
479 479  
480 480  
481 -== 2.9  Read or Clear cached data ==
594 +== 2.15  Read or Clear cached data ==
482 482  
483 483  
484 484  (% style="color:blue" %)**AT Command:**
... ... @@ -487,10 +487,10 @@
487 487  
488 488  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
489 489  
490 -[[image:1670408172929-569.png]]
603 +[[image:image-20221118094227-5.png]]
491 491  
492 492  
493 -== 2.10  ​Firmware Change Log ==
606 +== 2.16  ​Firmware Change Log ==
494 494  
495 495  
496 496  Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
... ... @@ -498,12 +498,12 @@
498 498  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
499 499  
500 500  
501 -== 2.11  ​Battery Analysis ==
614 +== 2.17  ​Battery Analysis ==
502 502  
503 -=== 2.11.1  ​Battery Type ===
616 +=== 2.17.1  ​Battery Type ===
504 504  
505 505  
506 -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.
619 +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.
507 507  
508 508  The battery is designed to last for several years depends on the actual use environment and update interval. 
509 509  
... ... @@ -518,7 +518,7 @@
518 518  [[image:image-20221021111911-26.png]] ​
519 519  
520 520  
521 -=== 2.11.2  Power consumption Analyze ===
634 +=== 2.17.2  Power consumption Analyze ===
522 522  
523 523  
524 524  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.
... ... @@ -540,16 +540,16 @@
540 540  [[image:1666596205057-567.png]] ​
541 541  
542 542  
543 -=== 2.11.3  ​Battery Note ===
656 +=== 2.17.3  ​Battery Note ===
544 544  
545 545  
546 546  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.
547 547  
548 548  
549 -=== 2.11.4  Replace the battery ===
662 +=== 2.17.4  Replace the battery ===
550 550  
551 551  
552 -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).
665 +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).
553 553  
554 554  
555 555  = 3. ​ Access NB-IoT Module =
... ... @@ -595,59 +595,65 @@
595 595  
596 596  AT+INTMOD            : Set the trigger interrupt mode
597 597  
598 -AT+5VT  : Set extend the time of 5V power  
711 +AT+5VT  : Set extend the time of 5V power  
599 599  
600 -AT+PRO  : Choose agreement
713 +AT+PRO  : Choose agreement
601 601  
602 -AT+RXDL  : Extend the sending and receiving time
715 +AT+RXDL  : Extend the sending and receiving time
603 603  
604 -AT+SERVADDR  : Server Address
717 +AT+SERVADDR  : Server Address
605 605  
606 -AT+TR      :  Get or Set record time
719 +AT+TR      :  Get or Set record time
607 607  
608 -AT+NOUD :  Get or Set the number of data to be uploaded
721 +AT+NOUD      : Get or Set the number of data to be uploaded
609 609  
610 610  AT+CDP     :  Read or Clear cached data
611 611  
612 -AT+DEBUG:  Enable or Disable debug mode
725 +AT+ DEBUG   : Enable or Disable debug mode
613 613  
614 -AT+ALARM1:  Get or Set alarm of distance1
727 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
615 615  
616 -AT+ALARM2:  Get or Set alarm of distance2
729 +AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
617 617  
618 -AT+GETSENSORVALUE :  Returns the current sensor measurement
731 +AT+COUNTMOD  :  Get or Set the count mode
619 619  
620 -AT+POWERIC :  Get or set the Power IC flag
733 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
621 621  
735 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
622 622  
737 +AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
738 +
739 +AT+ CLRC   :  Clear current door open count
740 +
741 +
623 623  (% style="color:blue" %)**COAP Management**      
624 624  
625 -AT+URI :  Resource parameters
744 +AT+URI            : Resource parameters
626 626  
627 627  
628 628  (% style="color:blue" %)**UDP Management**
629 629  
630 -AT+CFM :  Upload confirmation mode (only valid for UDP)
749 +AT+CFM          : Upload confirmation mode (only valid for UDP)
631 631  
632 632  
633 633  (% style="color:blue" %)**MQTT Management**
634 634  
635 -AT+CLIENT  : Get or Set MQTT client
754 +AT+CLIENT               : Get or Set MQTT client
636 636  
637 -AT+UNAME : Get or Set MQTT Username
756 +AT+UNAME  : Get or Set MQTT Username
638 638  
639 -AT+PWD  :  Get or Set MQTT password
758 +AT+PWD                  : Get or Set MQTT password
640 640  
641 -AT+PUBTOPIC :  Get or Set MQTT publish topic
760 +AT+PUBTOPIC  : Get or Set MQTT publish topic
642 642  
643 -AT+SUBTOPIC :  Get or Set MQTT subscription topic
762 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
644 644  
645 645  
646 646  (% style="color:blue" %)**Information**          
647 647  
648 -AT+FDR :  Factory Data Reset
767 +AT+FDR  : Factory Data Reset
649 649  
650 -AT+PWORD :  Serial Access Password
769 +AT+PWORD  : Serial Access Password
651 651  
652 652  
653 653  = ​5.  FAQ =
... ... @@ -659,7 +659,7 @@
659 659  
660 660  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]]
661 661  
662 -(% 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.**
781 +(% 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.**
663 663  
664 664  
665 665  = 6.  Trouble Shooting =
... ... @@ -679,7 +679,7 @@
679 679  = 7. ​ Order Info =
680 680  
681 681  
682 -Part Number:(% style="color:blue" %)** NMDS200**
801 +Part Number**:** NDS03A
683 683  
684 684  
685 685  = 8.  Packing Info =
... ... @@ -687,10 +687,8 @@
687 687  
688 688  (% style="color:blue" %)**Package Includes**:
689 689  
690 -* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
809 +* NDS03A Open/Close Door Sensor x 1
691 691  
692 -
693 -
694 694  = 9.  Support =
695 695  
696 696  
1670405841875-916.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.1 KB
Content
1670405928926-116.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.7 KB
Content
1670406036256-101.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.0 KB
Content
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
image-20221208090742-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.7 KB
Content

Applications

Navigation

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