Changes for page NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 17:03
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 4 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -51,8 +51,6 @@ 51 51 * Micro SIM card slot for NB-IoT SIM 52 52 * 8500mAh Battery for long-term use 53 53 54 - 55 - 56 56 == 1.3 Radar probe specification == 57 57 58 58 ... ... @@ -66,8 +66,6 @@ 66 66 * Vertical Angel: 23° 67 67 68 68 69 - 70 - 71 71 == 1.4 Storage Temperature == 72 72 73 73 ... ... @@ -91,8 +91,6 @@ 91 91 * Sewer 92 92 * Bottom water level monitoring 93 93 94 - 95 - 96 96 == 1.6 Specification == 97 97 98 98 ... ... @@ -110,8 +110,6 @@ 110 110 * B20 @H-FDD: 800MHz 111 111 * B28 @H-FDD: 700MHz 112 112 113 - 114 - 115 115 == 1.7 Installation == 116 116 117 117 ... ... @@ -303,69 +303,50 @@ 303 303 == 2.3 Uplink Payload == 304 304 305 305 306 -The uplink payload includes 2 6bytes in total by default.298 +The uplink payload includes 23 bytes in total by default. 307 307 308 308 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. 309 309 310 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:** 311 311 312 312 (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 313 -|=(% 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**314 -|=(% 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" %)dooropennum(pb14)|(% style="width:93px" %)lastopentime(pb14)304 +|=(% 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** 305 +|=(% 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 |(% style="width:93px" %) Distance 2 315 315 316 316 (% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %) 317 -|(% style="width:50px" %)**4**|(% style="width:90px" %)** 1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((308 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)((( 318 318 **1-32 group** 319 319 ))) 320 -|(% 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" %)lastopentime(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...311 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance 2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)... 321 321 322 - (%style="color:blue"%)**WhenAT+TTRCHANNEL=2:**313 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data. 323 323 315 +[[image:1670406261143-723.png]] 324 324 325 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 326 -|=(% 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** 327 -|=(% 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) 328 328 329 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 330 -|(% 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** 331 -|(% 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) 318 +The payload is ASCII string, representative same HEX: f867787050471071 0064 0cc3 09 01 00 00ef 013d 6390453d 332 332 333 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 334 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)((( 335 -**1-32 group** 336 -))) 337 -|(% 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" %)...... 320 +**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__(%%)** 338 338 339 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data. 340 - 341 -[[image:image-20221117145932-2.png]] 342 - 343 - 344 -The payload is ASCII string, representative same HEX: 345 - 346 -**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__(%%)** 347 - 348 348 **where:** 349 349 350 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050 213317 = f867787050213317324 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071 351 351 352 352 * (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 353 353 354 -* (% style="color:#037691" %)**BAT :**(%%) 0x0cc f= 3279mV = 3.279V328 +* (% style="color:#037691" %)**BAT :**(%%) 0x0cc3 = 3267 mV = 3.267V 355 355 356 -* (% style="color:#037691" %)**Singal: **(%%)0x 19 =25330 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9 357 357 358 358 * (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 359 359 360 -* (% style="color:#037691" %)** Door Status:**(%%)334 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0 361 361 362 -* (% style="color:#037691" %)** Alarm Status: **(%%)0x000336 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239 363 363 364 -* (% style="color:#037691" %)** door opennum: **(%%)0x000016=22338 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317 365 365 366 -* (% style="color:#037691" %)** last open time:00017=23340 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time) 367 367 368 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time) 369 369 370 370 == 2.4 Payload Explanation and Sensor Interface == 371 371 ... ... @@ -388,13 +388,13 @@ 388 388 389 389 Specify the software version: 0x64=100, which means firmware version 1.00. 390 390 391 -For example 0x00 64 : This device is NDS0 3A1 with firmware version 1.0.0.364 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0. 392 392 393 393 394 394 === 2.4.3 Battery Info === 395 395 396 396 397 -Check the battery voltage for NDS0 3A.370 +Check the battery voltage for NMDS200. 398 398 399 399 Ex1: 0x0B45 = 2885mV 400 400 ... ... @@ -419,38 +419,35 @@ 419 419 **99** Not known or not detectable 420 420 421 421 422 -=== 2.4.5 Disa larm: (default:0)===395 +=== 2.4.5 Distance === 423 423 424 424 425 - (% style="color:blue" %)**If Disalarm= 1**(%%), NDS03A will only send uplinkatevery TDC periodically.This is normally use forpulse meter application, in this application, there are many open/close event, and platform only care about the total number of pulse.398 +[[image:1670407401682-959.png]] 426 426 427 -(% style="color:blue" %)** If Disalarm = 0**(%%), NDS03A will send uplink atevery TDC periodically andsend dataoneach open/close event. This is useful for the application user need to monitor the open/close event in real-time.400 +(% style="color:blue" %)**Object1 Distance:** 428 428 429 - (%style="color:red"%)**Note:**(%%) WhenDisalarm=0, a high frequentlyopen/closeeventwillcauselotsofuplink and drain batteryvery fast.402 +Distance between sensor probe to the first object. (unit: cm) 430 430 404 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is 431 431 432 - ===2.4.6 KeepStatus&KeepTime===406 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.** 433 433 434 434 435 - Showsthenfigure valueof Alarm Baseon TimeoutFeature409 +(% style="color:blue" %)**Object2 Distance:** 436 436 411 +Distance between sensor probe to the second object. (unit: cm) 437 437 438 -=== 2.4.7 Timestamp === 439 439 414 +=== 2.4.6 Timestamp === 440 440 416 + 441 441 Timestamp : 0x6315537b =1662342011 442 442 443 443 444 -=== 2.4.8 Switch Dual Channel Mode === 445 - 446 - 447 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function. 448 - 449 - 450 450 == 2.5 Downlink Payload == 451 451 452 452 453 -By default, NDS0 3Aprints the downlink payload to console port.423 +By default, NMDS200 prints the downlink payload to console port. 454 454 455 455 [[image:image-20221021111414-18.png]] 456 456 ... ... @@ -467,7 +467,7 @@ 467 467 468 468 * (% style="color:#037691" %)**Reset** 469 469 470 -If payload = 0x04FF, it will reset the NDS0 3A440 +If payload = 0x04FF, it will reset the NMDS200 471 471 472 472 * (% style="color:#037691" %)**INTMOD** 473 473 ... ... @@ -477,112 +477,34 @@ 477 477 == 2.6 LED Indicator == 478 478 479 479 480 -The NDS0 3Ahas an internal LED which is to show the status of different states.450 +The NMDS200 has an internal LED which is to show the status of different states. 481 481 482 482 * When the device starts normally, the LED will light up for 1 second. 483 483 * After NDS03A join NB-IoT network. The LED will be ON for 3 seconds. 484 484 * For each uplink probe, LED will be on for 500ms. 485 485 486 -== 2.7 Alarm Base on Timeout == 487 487 488 488 489 - NDS03Acanmonitor the timeout for astatus change,this feature can be used to monitorsomeevents such as door openingtoo longetc. Related Parameters are:458 +== 2.7 Distance alarm function == 490 490 491 491 492 -(% style="color:blue" %)** 1.Keep Status:Status to bemonitor**461 +(% style="color:blue" %)**AT Command: AT+ALARM1=min,max** 493 493 494 - Keep Status = 1: Monitor Closeto Open event463 +**Example 1:** 495 495 496 - KeepStatus=:MonitorOpentoCloseevent465 +AT+ ALARM1 =60,200 ~/~/ Alarm when moisture lower than 60. 497 497 467 +AT+ ALARM2 =min,max 498 498 499 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm** 500 500 501 - Range0 ~~ 65535(0xFFFF) seconds.470 +**Example 2:** 502 502 503 - Ifkeeptime=DisableAlarmBaseonTimeoutfeature.472 +AT+ ALARM2 =200,1500 ~/~/ Alarm when temperature lower than 1500 504 504 505 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout. 506 506 475 +== 2.8 Set the number of data to be uploaded and the recording time == 507 507 508 -(% style="color:blue" %)**AT Command to configure:** 509 509 510 -(% style="color:blue" %)**PB14 PIN:** 511 - 512 -(% 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. 513 - 514 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm. 515 - 516 - 517 -(% style="color:blue" %)**PB15 PIN:** 518 - 519 -(% style="color:#037691" %)**AT+TTRIG2=1,30** 520 - 521 -(% style="color:#037691" %)**AT+TTRIG2=0,0 ** 522 - 523 - 524 -== 2.8 Set debug mode == 525 - 526 - 527 -Feature: Enable or Disable debug mode 528 - 529 -(% style="color:blue" %)**AT Command: AT+DEBUG** 530 - 531 -[[image:image-20221021111629-21.png]] 532 - 533 - 534 - 535 -== 2.9 Clear Flash Record == 536 - 537 - 538 -Feature: Clear flash storage for data log feature. 539 - 540 -(% style="color:blue" %)**AT Command: AT+CLRDTA** 541 - 542 -[[image:image-20221021111527-19.png]] 543 - 544 - 545 -== 2.10 Count Mod == 546 - 547 - 548 -(% style="color:blue" %)**AT Command: AT+COUNTMOD** 549 - 550 -[[image:image-20221118092935-1.png]] 551 - 552 - 553 -== 2.11 Interrupt Pin Channel Mod == 554 - 555 - 556 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL** 557 - 558 -[[image:image-20221118093144-2.png]] 559 - 560 - 561 -== 2.12 TTRIG1/2 timeout status alarm == 562 - 563 - 564 -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. 565 - 566 -(% style="color:blue" %)**AT Command: AT+TTRALARM** 567 - 568 -[[image:image-20221118093512-3.png]] 569 - 570 - 571 -== 2.13 Select counting mode == 572 - 573 - 574 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b** 575 - 576 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted. 577 - 578 -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. 579 - 580 -[[image:image-20221118093658-4.png]] 581 - 582 - 583 -== 2.14 Set the number of data to be uploaded and the recording time == 584 - 585 - 586 586 (% style="color:blue" %)**AT Command:** 587 587 588 588 (% 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) ... ... @@ -590,7 +590,7 @@ 590 590 (% 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. 591 591 592 592 593 -== 2. 15Read or Clear cached data ==485 +== 2.9 Read or Clear cached data == 594 594 595 595 596 596 (% style="color:blue" %)**AT Command:** ... ... @@ -599,10 +599,10 @@ 599 599 600 600 (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 601 601 602 -[[image: image-20221118094227-5.png]]494 +[[image:1670408172929-569.png]] 603 603 604 604 605 -== 2.1 6Firmware Change Log ==497 +== 2.10 Firmware Change Log == 606 606 607 607 608 608 Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]] ... ... @@ -610,12 +610,12 @@ 610 610 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 611 611 612 612 613 -== 2.1 7Battery Analysis ==505 +== 2.11 Battery Analysis == 614 614 615 -=== 2.1 7.1 Battery Type ===507 +=== 2.11.1 Battery Type === 616 616 617 617 618 -The NDS0 3Abattery 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 +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 619 620 620 The battery is designed to last for several years depends on the actual use environment and update interval. 621 621 ... ... @@ -630,7 +630,7 @@ 630 630 [[image:image-20221021111911-26.png]] 631 631 632 632 633 -=== 2.1 7.2 Power consumption Analyze ===525 +=== 2.11.2 Power consumption Analyze === 634 634 635 635 636 636 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. ... ... @@ -652,16 +652,16 @@ 652 652 [[image:1666596205057-567.png]] 653 653 654 654 655 -=== 2.1 7.3 Battery Note ===547 +=== 2.11.3 Battery Note === 656 656 657 657 658 658 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. 659 659 660 660 661 -=== 2.1 7.4 Replace the battery ===553 +=== 2.11.4 Replace the battery === 662 662 663 663 664 -The default battery pack of NDS0 3Aincludes 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 +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 665 666 666 667 667 = 3. Access NB-IoT Module =
- 1670406261143-723.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +77.9 KB - Content
- 1670407401682-959.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +23.7 KB - Content
- 1670408172929-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +211.8 KB - Content
- image-20221208090742-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +79.7 KB - Content