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, 2 removed)
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 ... ... @@ -16,37 +16,25 @@ 16 16 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 -))) 20 20 21 - (((19 + 22 22 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. 23 -))) 24 24 25 -((( 26 26 NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one. 27 -))) 28 28 29 -((( 30 30 NMDS200 (% style="color:blue" %)**supports Alarm Feature**(%%), user can set the NMDS200 to uplink data in a short interval when the distance is out of configured range. 31 -))) 32 32 33 -((( 34 34 NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technology**(%%) developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage. 35 -))) 36 36 37 -((( 38 38 NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements. 39 -))) 40 40 41 -((( 42 42 NMDS200 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**,(%%) It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 43 -))) 44 44 45 -((( 46 46 To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection. 47 47 ))) 48 48 49 49 36 + 50 50 == 1.2 Features == 51 51 52 52 ... ... @@ -64,6 +64,7 @@ 64 64 * Micro SIM card slot for NB-IoT SIM 65 65 * 8500mAh Battery for long-term use 66 66 54 + 67 67 == 1.3 Radar probe specification == 68 68 69 69 ... ... @@ -76,6 +76,8 @@ 76 76 * Horizontal Angel: 78° 77 77 * Vertical Angel: 23° 78 78 67 + 68 + 79 79 == 1.4 Storage Temperature == 80 80 81 81 ... ... @@ -82,9 +82,13 @@ 82 82 -40°C to +85°C 83 83 84 84 75 + 76 + 77 + 85 85 == 1.5 Applications == 86 86 87 87 81 + 88 88 * Horizontal distance measurement 89 89 * Liquid level measurement 90 90 * Parking management system ... ... @@ -95,6 +95,7 @@ 95 95 * Sewer 96 96 * Bottom water level monitoring 97 97 92 + 98 98 == 1.6 Specification == 99 99 100 100 ... ... @@ -112,6 +112,7 @@ 112 112 * B20 @H-FDD: 800MHz 113 113 * B28 @H-FDD: 700MHz 114 114 110 + 115 115 == 1.7 Installation == 116 116 117 117 ... ... @@ -118,7 +118,7 @@ 118 118 Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object. 119 119 120 120 121 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height=" 294" width="540"]]117 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]] 122 122 123 123 124 124 ... ... @@ -151,7 +151,7 @@ 151 151 152 152 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. 153 153 154 -[[image:image-2022120 8090742-1.png]]150 +[[image:image-20221207173300-4.png]] 155 155 156 156 157 157 === 2.2.1 Insert NB-IoT SIM card === ... ... @@ -207,7 +207,7 @@ 207 207 (% 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/]] 208 208 209 209 210 -(% style="color:blue" %)**Use below commands in N MDS200:**206 +(% style="color:blue" %)**Use below commands in NDS03A:** 211 211 212 212 * (% style="color:#037691" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 213 213 ... ... @@ -308,15 +308,15 @@ 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 310 311 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width: 450px" %)312 -|=(% 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**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" %)Exit flag|(% style="width:94px" %) [[Distance 1>>||anchor="H2.4.5A0Distance"]]|(% style="width:93px" %)[[Distance 2>>||anchor="H2.4.5A0Distance"]]307 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 308 +|=(% 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** 309 +|=(% 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 314 314 315 -(% border="1" style="background-color:#ffffcc; color:green; width: 350px" %)316 -|(% style="width: 60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)(((311 +(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %) 312 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)((( 317 317 **1-32 group** 318 318 ))) 319 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4. 6A0Timestamp"]]| Distance 1 | Distance 2|(% style="width:67px" %)Time stamp|(% style="width:98px" %)...315 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance 2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)... 320 320 321 321 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data. 322 322 ... ... @@ -348,6 +348,7 @@ 348 348 * (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time) 349 349 350 350 347 + 351 351 == 2.4 Payload Explanation and Sensor Interface == 352 352 353 353 === 2.4.1 Device ID === ... ... @@ -369,13 +369,13 @@ 369 369 370 370 Specify the software version: 0x64=100, which means firmware version 1.00. 371 371 372 -For example 0x00 64 : This device is N MDS2001 with firmware version 1.0.0.369 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0. 373 373 374 374 375 375 === 2.4.3 Battery Info === 376 376 377 377 378 -Check the battery voltage for N MDS200.375 +Check the battery voltage for NDS03A. 379 379 380 380 Ex1: 0x0B45 = 2885mV 381 381 ... ... @@ -387,49 +387,51 @@ 387 387 388 388 NB-IoT Network signal Strength. 389 389 390 - (% style="color:blue" %)**Ex1: 0x1d = 29**387 +**Ex1: 0x1d = 29** 391 391 392 - (% style="color:#037691" %)**0**(%%)389 +**0** -113dBm or less 393 393 394 - (% style="color:#037691" %)**1**(%%)391 +**1** -111dBm 395 395 396 - (% style="color:#037691" %)**2...30**(%%)-109dBm... -53dBm393 +**2...30** -109dBm... -53dBm 397 397 398 - (% style="color:#037691" %)**31**(%%)395 +**31** -51dBm or greater 399 399 400 - (% style="color:#037691" %)**99**(%%)397 +**99** Not known or not detectable 401 401 402 402 403 -=== 2.4.5 Dis tance ===400 +=== 2.4.5 Disalarm: (default: 0) === 404 404 405 405 406 - [[image:1670407401682-959.png]]403 +(% 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. 407 407 405 +(% 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. 408 408 409 -(% style="color: blue" %)**Object1Distance:**407 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast. 410 410 411 -Distance between sensor probe to the first object. (unit: cm) 412 412 413 - Forexample,ifthe data youget from the registeris0x02 0x05, thedistancebetween the sensor and themeasuredobject is410 +=== 2.4.6 Keep Status & Keep Time === 414 414 415 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.** 416 416 413 +Shows the configure value of Alarm Base on Timeout Feature 417 417 418 -(% style="color:blue" %)**Object2 Distance:** 419 419 420 - Distancebetweensensor probeto the second object. (unit: cm)416 +=== 2.4.7 Timestamp === 421 421 422 422 423 - === 2.4.6Timestamp ===419 +Timestamp : 0x6315537b =1662342011 424 424 425 425 426 - Timestamp:0x6315537b=1662342011422 +=== 2.4.8 Switch Dual Channel Mode === 427 427 428 428 425 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function. 426 + 427 + 429 429 == 2.5 Downlink Payload == 430 430 431 431 432 -By default, N MDS200prints the downlink payload to console port.431 +By default, NDS03A prints the downlink payload to console port. 433 433 434 434 [[image:image-20221021111414-18.png]] 435 435 ... ... @@ -446,7 +446,7 @@ 446 446 447 447 * (% style="color:#037691" %)**Reset** 448 448 449 -If payload = 0x04FF, it will reset the N MDS200448 +If payload = 0x04FF, it will reset the NDS03A 450 450 451 451 * (% style="color:#037691" %)**INTMOD** 452 452 ... ... @@ -456,33 +456,112 @@ 456 456 == 2.6 LED Indicator == 457 457 458 458 459 -The N MDS200has an internal LED which is to show the status of different states.458 +The NDS03A has an internal LED which is to show the status of different states. 460 460 461 461 * When the device starts normally, the LED will light up for 1 second. 462 -* After N MDS200join NB-IoT network. The LED will be ON for 3 seconds.461 +* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds. 463 463 * For each uplink probe, LED will be on for 500ms. 464 464 464 +== 2.7 Alarm Base on Timeout == 465 465 466 -== 2.7 Distance alarm function == 467 467 467 +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: 468 468 469 -(% style="color:blue" %)**AT Command: AT+ALARM1=min,max** 470 470 471 -(% style="color: #037691" %)**Example1:**470 +(% style="color:blue" %)**1. Keep Status: Status to be monitor** 472 472 473 - AT+ALARM1=60,200~/~/ Alarm when moisturelowerthan60.472 +Keep Status = 1: Monitor Close to Open event 474 474 475 - AT+ALARM2=min,max474 +Keep Status = 0: Monitor Open to Close event 476 476 477 477 478 -(% style="color: #037691" %)**Example2:**477 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm** 479 479 480 - AT+ ALARM2=200,1500/~/Alarmwhen temperature lower than1500479 +Range 0 ~~ 65535(0xFFFF) seconds. 481 481 481 +If keep time = 0, Disable Alarm Base on Timeout feature. 482 482 483 - ==2.8Set thenumberof dataobeuploaded andtherecording time==483 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout. 484 484 485 485 486 +(% style="color:blue" %)**AT Command to configure:** 487 + 488 +(% style="color:blue" %)**PB14 PIN:** 489 + 490 +(% 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. 491 + 492 +(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm. 493 + 494 + 495 +(% style="color:blue" %)**PB15 PIN:** 496 + 497 +(% style="color:#037691" %)**AT+TTRIG2=1,30** 498 + 499 +(% style="color:#037691" %)**AT+TTRIG2=0,0 ** 500 + 501 + 502 +== 2.8 Set debug mode == 503 + 504 + 505 +Feature: Enable or Disable debug mode 506 + 507 +(% style="color:blue" %)**AT Command: AT+DEBUG** 508 + 509 +[[image:image-20221021111629-21.png]] 510 + 511 + 512 + 513 +== 2.9 Clear Flash Record == 514 + 515 + 516 +Feature: Clear flash storage for data log feature. 517 + 518 +(% style="color:blue" %)**AT Command: AT+CLRDTA** 519 + 520 +[[image:image-20221021111527-19.png]] 521 + 522 + 523 +== 2.10 Count Mod == 524 + 525 + 526 +(% style="color:blue" %)**AT Command: AT+COUNTMOD** 527 + 528 +[[image:image-20221118092935-1.png]] 529 + 530 + 531 +== 2.11 Interrupt Pin Channel Mod == 532 + 533 + 534 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL** 535 + 536 +[[image:image-20221118093144-2.png]] 537 + 538 + 539 +== 2.12 TTRIG1/2 timeout status alarm == 540 + 541 + 542 +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. 543 + 544 +(% style="color:blue" %)**AT Command: AT+TTRALARM** 545 + 546 +[[image:image-20221118093512-3.png]] 547 + 548 + 549 +== 2.13 Select counting mode == 550 + 551 + 552 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b** 553 + 554 +When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted. 555 + 556 +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. 557 + 558 +[[image:image-20221118093658-4.png]] 559 + 560 + 561 +== 2.14 Set the number of data to be uploaded and the recording time == 562 + 563 + 486 486 (% style="color:blue" %)**AT Command:** 487 487 488 488 (% 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) ... ... @@ -490,7 +490,7 @@ 490 490 (% 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. 491 491 492 492 493 -== 2. 9Read or Clear cached data ==571 +== 2.15 Read or Clear cached data == 494 494 495 495 496 496 (% style="color:blue" %)**AT Command:** ... ... @@ -499,10 +499,10 @@ 499 499 500 500 (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 501 501 502 -[[image:1 670408172929-569.png]]580 +[[image:image-20221118094227-5.png]] 503 503 504 504 505 -== 2.1 0Firmware Change Log ==583 +== 2.16 Firmware Change Log == 506 506 507 507 508 508 Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]] ... ... @@ -510,12 +510,12 @@ 510 510 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 511 511 512 512 513 -== 2.1 1Battery Analysis ==591 +== 2.17 Battery Analysis == 514 514 515 -=== 2.1 1.1 Battery Type ===593 +=== 2.17.1 Battery Type === 516 516 517 517 518 -The N MDS200battery 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.596 +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. 519 519 520 520 The battery is designed to last for several years depends on the actual use environment and update interval. 521 521 ... ... @@ -530,7 +530,7 @@ 530 530 [[image:image-20221021111911-26.png]] 531 531 532 532 533 -=== 2.1 1.2 Power consumption Analyze ===611 +=== 2.17.2 Power consumption Analyze === 534 534 535 535 536 536 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. ... ... @@ -552,16 +552,16 @@ 552 552 [[image:1666596205057-567.png]] 553 553 554 554 555 -=== 2.1 1.3 Battery Note ===633 +=== 2.17.3 Battery Note === 556 556 557 557 558 558 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. 559 559 560 560 561 -=== 2.1 1.4 Replace the battery ===639 +=== 2.17.4 Replace the battery === 562 562 563 563 564 -The default battery pack of N MDS200includes 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).642 +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). 565 565 566 566 567 567 = 3. Access NB-IoT Module = ... ... @@ -607,59 +607,65 @@ 607 607 608 608 AT+INTMOD : Set the trigger interrupt mode 609 609 610 -AT+5VT : Set extend the time of 5V power 688 +AT+5VT : Set extend the time of 5V power 611 611 612 -AT+PRO : Choose agreement 690 +AT+PRO : Choose agreement 613 613 614 -AT+RXDL : Extend the sending and receiving time 692 +AT+RXDL : Extend the sending and receiving time 615 615 616 -AT+SERVADDR : Server Address 694 +AT+SERVADDR : Server Address 617 617 618 -AT+TR : Get or Set record time 696 +AT+TR : Get or Set record time 619 619 620 -AT+NOUD : 698 +AT+NOUD : Get or Set the number of data to be uploaded 621 621 622 622 AT+CDP : Read or Clear cached data 623 623 624 -AT+DEBUG :Enable or Disable debug mode702 +AT+ DEBUG : Enable or Disable debug mode 625 625 626 -AT+ ALARM1:Get or Setalarm ofdistance1704 +AT+ TTRIG1 : Get or Set PB14 PIN Alarm Base on Timeout 627 627 628 -AT+ ALARM2:Get or Setalarm ofdistance2706 +AT+ TTRIG2 : Get or Set PB15 PIN Alarm Base on Timeout 629 629 630 -AT+ GETSENSORVALUE:Returnsthe currentsensormeasurement708 +AT+COUNTMOD : Get or Set the count mode 631 631 632 -AT+ POWERIC :set thePowerICflag710 +AT+TTRCHANNEL : Get or Set the number of interrupt channels 633 633 712 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute) 634 634 714 +AT+DISALARM : Enable/Disable Alarm for door open/close or water leak event 715 + 716 +AT+ CLRC : Clear current door open count 717 + 718 + 635 635 (% style="color:blue" %)**COAP Management** 636 636 637 -AT+URI : 721 +AT+URI : Resource parameters 638 638 639 639 640 640 (% style="color:blue" %)**UDP Management** 641 641 642 -AT+CFM : 726 +AT+CFM : Upload confirmation mode (only valid for UDP) 643 643 644 644 645 645 (% style="color:blue" %)**MQTT Management** 646 646 647 -AT+CLIENT : Get or Set MQTT client 731 +AT+CLIENT : Get or Set MQTT client 648 648 649 -AT+UNAME : Get or Set MQTT Username 733 +AT+UNAME : Get or Set MQTT Username 650 650 651 -AT+PWD : 735 +AT+PWD : Get or Set MQTT password 652 652 653 -AT+PUBTOPIC :Get or Set MQTT publish topic737 +AT+PUBTOPIC : Get or Set MQTT publish topic 654 654 655 -AT+SUBTOPIC :Get or Set MQTT subscription topic739 +AT+SUBTOPIC : Get or Set MQTT subscription topic 656 656 657 657 658 658 (% style="color:blue" %)**Information** 659 659 660 -AT+FDR :Factory Data Reset744 +AT+FDR : Factory Data Reset 661 661 662 -AT+PWORD :Serial Access Password746 +AT+PWORD : Serial Access Password 663 663 664 664 665 665 = 5. FAQ = ... ... @@ -671,7 +671,7 @@ 671 671 672 672 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]] 673 673 674 -(% style="color:red" %)**Notice: **(% style="color:blue" %)**N MDS200** (%%)**and (% style="color:blue" %)LMDS200(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**758 +(% 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.** 675 675 676 676 677 677 = 6. Trouble Shooting = ... ... @@ -691,7 +691,7 @@ 691 691 = 7. Order Info = 692 692 693 693 694 -Part Number: (% style="color:blue" %)** NMDS200**778 +Part Number**:** NDS03A 695 695 696 696 697 697 = 8. Packing Info = ... ... @@ -699,9 +699,8 @@ 699 699 700 700 (% style="color:blue" %)**Package Includes**: 701 701 702 -* N MDS200NB-IoT MicrowaveRadarDistanceSensor x 1786 +* NDS03A Open/Close Door Sensor x 1 703 703 704 - 705 705 = 9. Support = 706 706 707 707
- 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