Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 83.3 >
edited by Xiaoling
on 2022/12/08 09:33
To version < 76.2 >
edited by Xiaoling
on 2022/12/07 17:33
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,6 +16,7 @@
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.
18 18  
19 +
19 19  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.
20 20  
21 21  NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
... ... @@ -32,6 +32,7 @@
32 32  )))
33 33  
34 34  
36 +
35 35  == ​1.2  Features ==
36 36  
37 37  
... ... @@ -49,6 +49,8 @@
49 49  * Micro SIM card slot for NB-IoT SIM
50 50  * 8500mAh Battery for long-term use
51 51  
54 +
55 +
52 52  == 1.3 Radar probe specification ==
53 53  
54 54  
... ... @@ -61,6 +61,9 @@
61 61  * Horizontal Angel: 78°
62 62  * Vertical Angel: 23°
63 63  
68 +
69 +
70 +
64 64  == 1.4  Storage Temperature ==
65 65  
66 66  
... ... @@ -67,9 +67,13 @@
67 67   -40°C to +85°C
68 68  
69 69  
77 +
78 +
79 +
70 70  == 1.5 ​ Applications ==
71 71  
72 72  
83 +
73 73  * Horizontal distance measurement
74 74  * Liquid level measurement
75 75  * Parking management system
... ... @@ -80,6 +80,8 @@
80 80  * Sewer
81 81  * Bottom water level monitoring
82 82  
94 +
95 +
83 83  == 1.6  Specification ==
84 84  
85 85  
... ... @@ -97,6 +97,8 @@
97 97  * B20 @H-FDD: 800MHz
98 98  * B28 @H-FDD: 700MHz
99 99  
113 +
114 +
100 100  == 1.7  Installation ==
101 101  
102 102  
... ... @@ -136,7 +136,7 @@
136 136  
137 137  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.
138 138  
139 -[[image:image-20221208090742-1.png]]
154 +[[image:image-20221207173300-4.png]]
140 140  
141 141  
142 142  === 2.2.1 Insert NB-IoT SIM card ===
... ... @@ -149,10 +149,10 @@
149 149  [[image:image-20221021110745-6.png]] ​
150 150  
151 151  
152 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
167 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
153 153  
154 154  
155 -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.
156 156  
157 157  (% style="color:blue" %)**Connection:**
158 158  
... ... @@ -175,11 +175,11 @@
175 175  
176 176  * Flow Control: (% style="color:red" %)**None**
177 177  
178 -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**(%%).
179 179  
180 180  ​[[image:image-20221021110817-7.png]]
181 181  
182 -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.
183 183  
184 184  
185 185  (% 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]]
... ... @@ -186,13 +186,13 @@
186 186  
187 187  
188 188  
189 -=== 2.2.3 Use CoAP protocol to uplink data ===
204 +=== 2.2.4 Use CoAP protocol to uplink data ===
190 190  
191 191  
192 192  (% 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/]]
193 193  
194 194  
195 -(% style="color:blue" %)**Use below commands in NMDS200:**
210 +(% style="color:blue" %)**Use below commands in NDS03A:**
196 196  
197 197  * (% style="color:#037691" %)**AT+PRO=1**                (%%) ~/~/ Set to use CoAP protocol to uplink
198 198  
... ... @@ -205,12 +205,12 @@
205 205  [[image:image-20221021110948-8.png]]
206 206  
207 207  
208 -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.
209 209  
210 -[[image:1670405841875-916.png]] ​
225 +[[image:image-20221118103547-9.png||height="605" width="837"]] ​
211 211  
212 212  
213 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
228 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
214 214  
215 215  
216 216  (% style="color:blue" %)**AT Commands:**
... ... @@ -228,7 +228,7 @@
228 228  
229 229  ​
230 230  
231 -=== 2.2.5 Use MQTT protocol to uplink data ===
246 +=== 2.2.6 Use MQTT protocol to uplink data ===
232 232  
233 233  
234 234  (% style="color:blue" %)**AT Commands:**
... ... @@ -250,7 +250,7 @@
250 250  ​ [[image:image-20221118103445-7.png]]
251 251  
252 252  
253 -[[image:1670405928926-116.png]]
268 +[[image:image-20221118103453-8.png||height="608" width="841"]]
254 254  
255 255  ​
256 256  
... ... @@ -257,7 +257,7 @@
257 257  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.
258 258  
259 259  
260 -=== 2.2.6 Use TCP protocol to uplink data ===
275 +=== 2.2.7 Use TCP protocol to uplink data ===
261 261  
262 262  
263 263  (% style="color:blue" %)**AT Commands:**
... ... @@ -266,19 +266,18 @@
266 266  
267 267  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
268 268  
269 -​ [[image:1670406036256-101.png||height="676" width="713"]]
284 +​ [[image:image-20221021111125-14.png]]
270 270  
271 -
272 272  [[image:image-20221021111131-15.png]]
273 273  
274 274  ​
275 275  
276 -=== 2.2.7 Change Update Interval ===
290 +=== 2.2.8 Change Update Interval ===
277 277  
278 278  
279 279  User can use below command to change the (% style="color:blue" %)**uplink interval**.
280 280  
281 -* (% 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)
282 282  
283 283  (% style="color:red" %)**NOTE:**
284 284  
... ... @@ -288,53 +288,70 @@
288 288  == 2.3  Uplink Payload ==
289 289  
290 290  
291 -The uplink payload includes 23 bytes in total by default.
305 +The uplink payload includes 26 bytes in total by default.
292 292  
293 293  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.
294 294  
309 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
295 295  
296 296  (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
297 -|=(% 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:90px" %)**2**|(% style="width:100px" %)**2**
298 -|=(% 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.5A0A0Distance"]] |(% style="width:93px" %) [[Distance  2>>||anchor="H2.4.5A0A0Distance"]]
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)
299 299  
300 300  (% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
301 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
316 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
302 302  **1-32 group**
303 303  )))
304 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
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" %)...
305 305  
306 -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:**
307 307  
308 -[[image:1670406261143-723.png]]
309 309  
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)
310 310  
311 -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)
312 312  
313 -**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" %)......
314 314  
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 +
315 315  **where:**
316 316  
317 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
349 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
318 318  
319 319  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
320 320  
321 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
353 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
322 322  
323 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
355 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
324 324  
325 325  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
326 326  
327 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
359 +* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
328 328  
329 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
361 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
330 330  
331 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
363 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
332 332  
333 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
365 +* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
334 334  
367 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
335 335  
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.
390 +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.
396 +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**
408 +**Ex1: 0x1d = 29**
378 378  
379 -**(% style="color:#037691" %)0** (%%) -113dBm or less
410 +**0**  -113dBm or less
380 380  
381 -**(% style="color:#037691" %)1**  (%%) -111dBm
412 +**1**  -111dBm
382 382  
383 -**(% style="color:#037691" %)2...30** (%%) -109dBm... -53dBm
414 +**2...30** -109dBm... -53dBm
384 384  
385 -**(% style="color:#037691" %)31** (%%)  -51dBm or greater
416 +**31**   -51dBm or greater
386 386  
387 -**(% style="color:#037691" %)99** (%%)   Not known or not detectable
418 +**99**    Not known or not detectable
388 388  
389 389  
390 -=== 2.4.5  Distance ===
421 +=== 2.4.5  Disalarm: (default: 0) ===
391 391  
392 392  
393 -[[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.
394 394  
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.
395 395  
396 -(% 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.
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
431 +=== 2.4.6  Keep Status & Keep Time ===
401 401  
402 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
403 403  
434 +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)
437 +=== 2.4.7  Timestamp ===
408 408  
409 409  
410 -=== 2.4.6  Timestamp ===
440 +Timestamp : 0x6315537b =1662342011
411 411  
412 412  
413 -Timestamp : 0x6315537b =1662342011
443 +=== 2.4.8  Switch Dual Channel Mode ===
414 414  
415 415  
446 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
447 +
448 +
416 416  == 2.5  Downlink Payload ==
417 417  
418 418  
419 -By default, NMDS200 prints the downlink payload to console port.
452 +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
469 +If payload = 0x04FF, it will reset the NDS03A
437 437  
438 438  * (% style="color:#037691" %)**INTMOD**
439 439  
... ... @@ -443,37 +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.
479 +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.
482 +* 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  
485 +== 2.7  Alarm Base on Timeout ==
452 452  
453 453  
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:
454 454  
455 -== 2.7  Distance alarm function ==
456 456  
491 +(% style="color:blue" %)**1. Keep Status: Status to be monitor**
457 457  
458 -(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
493 +Keep Status = 1: Monitor Close to Open event
459 459  
460 -**(% style="color:blue" %)Example 1:**
495 +Keep Status = 0: Monitor Open to Close event
461 461  
462 -AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
463 463  
464 -AT+ ALARM2 =min,max
498 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
465 465  
500 +Range 0 ~~ 65535(0xFFFF) seconds.
466 466  
467 -**(% style="color:blue" %)Example 2:**
502 +If keep time = 0, Disable Alarm Base on Timeout feature.
468 468  
469 -AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
504 +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 471  
507 +(% style="color:blue" %)**AT Command to configure:**
472 472  
509 +(% style="color:blue" %)**PB14 PIN:**
473 473  
474 -== 2.8  Set the number of data to be uploaded and the recording time ==
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.
475 475  
513 +(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
476 476  
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 +
477 477  (% style="color:blue" %)**AT Command:**
478 478  
479 479  (% 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)
... ... @@ -481,7 +481,7 @@
481 481  (% 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.
482 482  
483 483  
484 -== 2.9  Read or Clear cached data ==
592 +== 2.15  Read or Clear cached data ==
485 485  
486 486  
487 487  (% style="color:blue" %)**AT Command:**
... ... @@ -490,10 +490,10 @@
490 490  
491 491  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
492 492  
493 -[[image:1670408172929-569.png]]
601 +[[image:image-20221118094227-5.png]]
494 494  
495 495  
496 -== 2.10  ​Firmware Change Log ==
604 +== 2.16  ​Firmware Change Log ==
497 497  
498 498  
499 499  Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
... ... @@ -501,12 +501,12 @@
501 501  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
502 502  
503 503  
504 -== 2.11  ​Battery Analysis ==
612 +== 2.17  ​Battery Analysis ==
505 505  
506 -=== 2.11.1  ​Battery Type ===
614 +=== 2.17.1  ​Battery Type ===
507 507  
508 508  
509 -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.
510 510  
511 511  The battery is designed to last for several years depends on the actual use environment and update interval. 
512 512  
... ... @@ -521,7 +521,7 @@
521 521  [[image:image-20221021111911-26.png]] ​
522 522  
523 523  
524 -=== 2.11.2  Power consumption Analyze ===
632 +=== 2.17.2  Power consumption Analyze ===
525 525  
526 526  
527 527  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.
... ... @@ -543,16 +543,16 @@
543 543  [[image:1666596205057-567.png]] ​
544 544  
545 545  
546 -=== 2.11.3  ​Battery Note ===
654 +=== 2.17.3  ​Battery Note ===
547 547  
548 548  
549 549  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.
550 550  
551 551  
552 -=== 2.11.4  Replace the battery ===
660 +=== 2.17.4  Replace the battery ===
553 553  
554 554  
555 -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).
556 556  
557 557  
558 558  = 3. ​ Access NB-IoT Module =
... ... @@ -606,51 +606,57 @@
606 606  
607 607  AT+SERVADDR  : Server Address
608 608  
609 -AT+TR      :  Get or Set record time
717 +AT+TR      :  Get or Set record time
610 610  
611 -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
612 612  
613 613  AT+CDP     :  Read or Clear cached data
614 614  
615 -AT+DEBUG:  Enable or Disable debug mode
723 +AT+ DEBUG   : Enable or Disable debug mode
616 616  
617 -AT+ALARM1:  Get or Set alarm of distance1
725 +AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
618 618  
619 -AT+ALARM2:  Get or Set alarm of distance2
727 +AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
620 620  
621 -AT+GETSENSORVALUE :  Returns the current sensor measurement
729 +AT+COUNTMOD  :  Get or Set the count mode
622 622  
623 -AT+POWERIC :  Get or set the Power IC flag
731 +AT+TTRCHANNEL  : Get or Set the number of interrupt channels
624 624  
733 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
625 625  
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 +
626 626  (% style="color:blue" %)**COAP Management**      
627 627  
628 -AT+URI :  Resource parameters
742 +AT+URI            : Resource parameters
629 629  
630 630  
631 631  (% style="color:blue" %)**UDP Management**
632 632  
633 -AT+CFM :  Upload confirmation mode (only valid for UDP)
747 +AT+CFM          : Upload confirmation mode (only valid for UDP)
634 634  
635 635  
636 636  (% style="color:blue" %)**MQTT Management**
637 637  
638 -AT+CLIENT  : Get or Set MQTT client
752 +AT+CLIENT               : Get or Set MQTT client
639 639  
640 -AT+UNAME : Get or Set MQTT Username
754 +AT+UNAME  : Get or Set MQTT Username
641 641  
642 -AT+PWD  :  Get or Set MQTT password
756 +AT+PWD                  : Get or Set MQTT password
643 643  
644 -AT+PUBTOPIC :  Get or Set MQTT publish topic
758 +AT+PUBTOPIC  : Get or Set MQTT publish topic
645 645  
646 -AT+SUBTOPIC :  Get or Set MQTT subscription topic
760 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
647 647  
648 648  
649 649  (% style="color:blue" %)**Information**          
650 650  
651 -AT+FDR :  Factory Data Reset
765 +AT+FDR  : Factory Data Reset
652 652  
653 -AT+PWORD :  Serial Access Password
767 +AT+PWORD  : Serial Access Password
654 654  
655 655  
656 656  = ​5.  FAQ =
... ... @@ -662,7 +662,7 @@
662 662  
663 663  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]]
664 664  
665 -(% 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.**
666 666  
667 667  
668 668  = 6.  Trouble Shooting =
... ... @@ -682,7 +682,7 @@
682 682  = 7. ​ Order Info =
683 683  
684 684  
685 -Part Number:**(% style="color:blue" %) NMDS200**
799 +Part Number**:** NDS03A
686 686  
687 687  
688 688  = 8.  Packing Info =
... ... @@ -690,7 +690,7 @@
690 690  
691 691  (% style="color:blue" %)**Package Includes**:
692 692  
693 -* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
807 +* NDS03A Open/Close Door Sensor x 1
694 694  
695 695  = 9.  Support =
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-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0