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, 0 added, 5 removed)
Details
- Page properties
-
- Content
-
... ... @@ -70,6 +70,7 @@ 70 70 * Micro SIM card slot for NB-IoT SIM 71 71 * 8500mAh Battery for long-term use 72 72 73 + 73 73 == 1.3 Storage & Operation == 74 74 75 75 ... ... @@ -113,6 +113,7 @@ 113 113 * - B20 @H-FDD: 800MHz 114 114 * - B28 @H-FDD: 700MHz 115 115 117 + 116 116 == 1.7 Pin Definitions and Switch == 117 117 118 118 ... ... @@ -354,39 +354,19 @@ 354 354 == 2.3 Uplink Payload == 355 355 356 356 357 -The uplink payload includes 2 6bytes in total by default.359 +The uplink payload includes 123 bytes in total by default. 358 358 359 -Each time the device uploads a data package .Theuser can usethe AT+NOUD commandto upload therecorded data.Up to 32 sets of recorded data can be uploaded.361 +Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded. 360 360 361 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:** 362 362 363 -(% border="1 " cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)364 -|=(% scope="row" style="width: 93px;" %)**Size(bytes)**|(% style="width:67px" %)**8**|(% style="width:40px" %)**2**|(% style="width:45px" %)**2**|(% style="width:75px" %)**1**|(% style="width:54px" %)**1**|(% style="width:62px" %)**1**|(% style="width:60px" %)**1**|(% style="width:94px" %)**3**|(% style="width:93px" %)**3**365 -|=(% style="width: 9 3px;" %)**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" %)DoorStatus|(% style="width:60px" %)[[AlarmStatus>>||anchor="H2.4.6A0Alarm"]]|(% style="width:94px" %)dooropen num(pb14)|(% style="width:93px" %)lastopenime(pb14)364 +(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %) 365 +|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:60px" %)**3** 366 +|=(% style="width: 96px;" %)**Value**|(% style="width:84px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:44px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:121px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:52px" %)MOD|(% style="width:84px" %)[[ Calculate Flag>>||anchor="H2.4.5A0CalculateFlag"]]|(% style="width:116px" %)[[Contact Status>>||anchor="H2.4.7A0ContactStatus"]]|(% style="width:57px" %)[[Alarm>>||anchor="H2.4.6A0Alarm"]]|(% style="width:91px" %)[[Total pulse>>||anchor="H2.4.8A0Totalpulse"]] 366 366 367 367 (% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %) 368 -|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)((( 369 -**1-32 group** 370 -))) 371 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% 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" %)... 369 +|(% style="width:100px" %)**3**|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:100px" %)**3**|(% style="width:80px" %)4|(% style="width:50px" %)**8 group** 370 +|(% style="width:176px" %)[[The last open duration>>||anchor="H2.4.9A0Thelastopenduration"]]|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% style="width:115px" %)Contact Status|(% style="width:92px" %)Total pulse|(% style="width:169px" %)The last open duration|(% style="width:97px" %)Time stamp|(% style="width:74px" %)... 372 372 373 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:** 374 - 375 - 376 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %) 377 -|=(% scope="row" style="width: 96px;" %)**Size(bytes)**|(% style="width:66px" %)**8**|(% style="width:40px" %)**2**|(% style="width:46px" %)**2**|(% style="width:70px" %)**1**|(% style="width:54px" %)**1**|(% style="width:55px" %)**1**|(% style="width:57px" %)**1**|(% style="width:86px" %)**3**|(% style="width:82px" %)**3** 378 -|=(% 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|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.4.6A0Alarm"]]|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14) 379 - 380 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %) 381 -|(% style="width:59px" %)**1**|(% style="width:67px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:66px" %)**1**|(% style="width:92px" %)**3** 382 -|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPN01-%20NB-IoT%20Outdoor%20OpenClose%20Dry%20Contact%20Sensor%C2%A0User%20Manual/#H2.4.7A0ContactStatus]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)Time stamp|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14) 383 - 384 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %) 385 -|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)((( 386 -**1-32 group** 387 -))) 388 -|(% style="width:102px" %)last open time (pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:88px" %)last open time(pb15)|(% style="width:63px" %)Time stamp|(% style="width:87px" %)... 389 - 390 390 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data. 391 391 392 392 [[image:image-20221117145932-2.png]] ... ... @@ -394,6 +394,8 @@ 394 394 395 395 The payload is ASCII string, representative same HEX: 396 396 379 +**0x **f867787050213317 0064 0ccf 19 01 00 00 000016 000017 637590df 380 + 397 397 **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__(%%)** 398 398 399 399 **where:** ... ... @@ -418,6 +418,8 @@ 418 418 419 419 * (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time) 420 420 405 + 406 + 421 421 == 2.4 Payload Explanation and Sensor Interface == 422 422 423 423 ... ... @@ -435,18 +435,20 @@ 435 435 The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID. 436 436 437 437 424 + 438 438 === 2.4.2 Version Info === 439 439 440 440 441 441 Specify the software version: 0x64=100, which means firmware version 1.00. 442 442 443 -For example 0x00 64 : This device is N DS03A1 with firmware version 1.0.0.430 +For example 0x00 64 : This device is CPN01 with firmware version 1.0.0. 444 444 445 445 433 + 446 446 === 2.4.3 Battery Info === 447 447 448 448 449 -Check the battery voltage for N DS03A.437 +Check the battery voltage for CPN01. 450 450 451 451 Ex1: 0x0B45 = 2885mV 452 452 ... ... @@ -453,6 +453,7 @@ 453 453 Ex2: 0x0B49 = 2889mV 454 454 455 455 444 + 456 456 === 2.4.4 Signal Strength === 457 457 458 458 ... ... @@ -471,39 +471,70 @@ 471 471 **99** Not known or not detectable 472 472 473 473 474 -=== 2.4.5 Disalarm: (default: 0) === 475 475 464 +=== 2.4.5 Calculate Flag === 476 476 477 -(% 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. 478 478 479 - (% style="color:blue"%)**IfDisalarm= 0**(%%), NDS03A willsenduplinkateveryTDC periodically andsenddataoneachopen/close event.This isuseful fortheapplicationuserneedtomonitor theopen/closeeventinreal-time.467 +The calculate flag is a user defined field, IoT server can use this filed to handle different meters with different pulse factors. For example, if there are 100 water meters, meter 1~~50 are 1 liter/pulse and meter 51 ~~ 100 has 1.5 liter/pulse. 480 480 481 - (%style="color:red" %)**Note:**(%%)When Disalarm=0,ahighfrequentlyopen/closeeventwillcauselotsofuplink anddrainbattery very fast.469 +User can set calculate flag to 1 for meter 1~~50 and 2 for meter 51 ~~ 100, So IoT Server can use this field for calculation. 482 482 471 +Default value: 0. 483 483 484 - ===2.4.6Keep Status&KeepTime===473 +Range (6 bits): (b)000000 ~~ (b) 111111 485 485 486 486 487 -Shows the configure value of Alarm Base on Timeout Feature 488 488 477 +=== 2.4.6 Alarm === 489 489 490 -=== 2.4.7 Timestamp === 491 491 480 +See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]] 492 492 493 -Timestamp : 0x6315537b =1662342011 494 494 495 495 484 +=== 2.4.7 Contact Status === 496 496 497 -=== 2.4.8 Switch Dual Channel Mode === 498 498 487 +0: Open 499 499 500 - NDS03A can connect two door sensors. Another door sensor can be connected to PB15pin. Both channels support alarm function.489 +1: Close 501 501 502 502 492 + 493 +=== 2.4.8 Total pulse === 494 + 495 + 496 +Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]] 497 + 498 +Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215 499 + 500 + 501 + 502 +=== 2.4.9 The last open duration === 503 + 504 + 505 +Dry Contact last open duration. 506 + 507 +Unit: min. 508 + 509 +[[image:image-20221021111346-17.png||height="146" width="770"]] 510 + 511 + 512 + 513 +=== 2.4.10 Timestamp === 514 + 515 + 516 +Timestamp : 0x6315537b =1662342011 517 + 518 +Convert Unix timestamp to time 2022-9-5 9:40:11. 519 + 520 +**~ ** 521 + 522 + 503 503 == 2.5 Downlink Payload == 504 504 505 505 506 -By default, N DS03Aprints the downlink payload to console port.526 +By default, CPN01 prints the downlink payload to console port. 507 507 508 508 [[image:image-20221021111414-18.png]] 509 509 ... ... @@ -520,7 +520,7 @@ 520 520 521 521 * (% style="color:#037691" %)**Reset** 522 522 523 -If payload = 0x04FF, it will reset the N DS03A543 +If payload = 0x04FF, it will reset the NSE01 524 524 525 525 * (% style="color:#037691" %)**INTMOD** 526 526 ... ... @@ -531,17 +531,16 @@ 531 531 == 2.6 LED Indicator == 532 532 533 533 534 -The N DS03Ahas an internal LED which is to show the status of different states.554 +The CPN01 has an internal LED which is to show the status of different states. 535 535 536 536 * When the device starts normally, the LED will light up for 1 second. 537 537 * After CPN01 join NB-IoT network. The LED will be ON for 3 seconds. 538 538 * For each uplink probe, LED will be on for 500ms. 539 539 540 - 541 541 == 2.7 Alarm Base on Timeout == 542 542 543 543 544 -N DS03Acan 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:563 +CPN01 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: 545 545 546 546 547 547 (% style="color:blue" %)**1. Keep Status: Status to be monitor** ... ... @@ -557,25 +557,17 @@ 557 557 558 558 If keep time = 0, Disable Alarm Base on Timeout feature. 559 559 560 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn 't change after timeout.579 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout. 561 561 562 562 563 563 (% style="color:blue" %)**AT Command to configure:** 564 564 565 -(% style="color:blue" %)**PB14 PIN:** 566 - 567 567 (% 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. CPN01 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. 568 568 569 569 (% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm. 570 570 571 571 572 -(% style="color:blue" %)**PB15 PIN:** 573 573 574 -(% style="color:#037691" %)**AT+TTRIG2=1,30** 575 - 576 -(% style="color:#037691" %)**AT+TTRIG2=0,0 ** 577 - 578 - 579 579 == 2.8 Set debug mode == 580 580 581 581 ... ... @@ -598,50 +598,50 @@ 598 598 599 599 600 600 601 -== 2.10 CountMod ==612 +== 2.10 Set trigger mode == 602 602 603 603 604 -(% style="color:blue" %)**AT Command: AT+ COUNTMOD**615 +(% style="color:blue" %)**AT Command: AT+TTRMOD** 605 605 606 - [[image:image-20221118092935-1.png]]617 +Feature: Set the trigger interrupt mode. 607 607 619 +[[image:image-20221021111552-20.png]] 608 608 609 609 610 -== 2.11 Interrupt Pin Channel Mod == 611 611 623 +== 2.11 Set the calculate flag == 612 612 613 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL** 614 614 615 - [[image:image-20221118093144-2.png]]626 +Feature: Set the calculate flag 616 616 628 +(% style="color:blue" %)**AT Command: AT+CALCFLAG** 617 617 630 +[[image:image-20221021111711-22.png]] 618 618 619 -== 2.12 TTRIG1/2 timeout status alarm == 620 620 621 621 622 - Itneeds to be used with AT+TTRIG1 or AT+TTRIG2.When TTRIG1or TTRIG2timesout and causes an alarm, andthestatus does notchange subsequently,analarmpacket willbesent at the alarminterval.634 +== 2.12 Set count number == 623 623 624 -(% style="color:blue" %)**AT Command: AT+TTRALARM** 625 625 626 - [[image:image-20221118093512-3.png]]637 +Feature: Manually set the count number 627 627 639 +(% style="color:blue" %)**AT Command: AT+SETCNT** 628 628 641 +[[image:image-20221021111748-24.png]] 629 629 630 -== 2.13 Select counting mode == 631 631 632 632 633 - (%style="color:blue"%)**AT Command:AT+TTRMODx=a,b**645 +== 2.13 Set the number of data to be uploaded and the recording time == 634 634 635 635 636 - When(% style="color:red" %)**a=0**(%%), thedoor is opened to count,andwhen (% style="color:red" %)**a=1**(%%),the closed door is counted.648 +(% style="color:blue" %)**AT Command:** 637 637 638 - When(% style="color:red" %)**b=0**(%%),it is thelastdooropenduration,and when (%style="color:red" %)**b=1**(%%),thelastdoorcloseduration.650 +(% 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) 639 639 640 - [[image:image-20221118093658-4.png]]652 +(% style="color:#037691" %)**AT+NOUD=8 ** (%%)~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 641 641 642 642 643 643 644 - 645 645 == 2.14 Read or Clear cached data == 646 646 647 647
- image-20221118092935-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -13.1 KB - Content
- image-20221118093144-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -11.7 KB - Content
- image-20221118093512-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -9.5 KB - Content
- image-20221118093658-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -12.7 KB - Content
- image-20221118094227-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -29.2 KB - Content