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, 8 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,13 +1,28 @@ 1 1 (% style="text-align:center" %) 2 -[[image:LMDS200_10.jpg]] 2 +[[image:LMDS200_10.jpg||height="572" width="572"]] 3 3 4 4 5 + 6 + 7 + 8 +(% style="display:none" %) (%%) 9 + 10 + 11 + 12 + 13 + 5 5 **Table of Contents:** 6 6 16 +{{toc/}} 7 7 8 8 9 9 10 10 21 + 22 + 23 + 24 + 25 + 11 11 = 1. Introduction = 12 12 13 13 == 1.1 What is NMDS200 NB-IoT Microwave Radar Distance Sensor == ... ... @@ -15,25 +15,37 @@ 15 15 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. 33 +))) 18 18 19 - 35 +((( 20 20 The NMDS200 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc. 37 +))) 21 21 39 +((( 22 22 NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one. 41 +))) 23 23 43 +((( 24 24 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. 45 +))) 25 25 47 +((( 26 26 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. 49 +))) 27 27 51 +((( 28 28 NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements. 53 +))) 29 29 55 +((( 30 30 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) 57 +))) 31 31 59 +((( 32 32 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. 33 33 ))) 34 34 35 35 36 - 37 37 == 1.2 Features == 38 38 39 39 ... ... @@ -51,13 +51,14 @@ 51 51 * Micro SIM card slot for NB-IoT SIM 52 52 * 8500mAh Battery for long-term use 53 53 81 + 54 54 == 1.3 Radar probe specification == 55 55 56 56 57 57 * Measuring Method: FMCW 58 -* Frequency: 24.000 24.500 GHz 86 +* Frequency: 24.000 ~~ 24.500 GHz 59 59 * Measurement output power: 6dBm 60 -* Measure range: 0.5 20m 88 +* Measure range: 0.5 ~~ 20m 61 61 * Accuracy: ±0.1m 62 62 * Resolution: 0.01m 63 63 * Horizontal Angel: 78° ... ... @@ -70,13 +70,9 @@ 70 70 -40°C to +85°C 71 71 72 72 73 - 74 - 75 - 76 76 == 1.5 Applications == 77 77 78 78 79 - 80 80 * Horizontal distance measurement 81 81 * Liquid level measurement 82 82 * Parking management system ... ... @@ -87,6 +87,7 @@ 87 87 * Sewer 88 88 * Bottom water level monitoring 89 89 114 + 90 90 == 1.6 Specification == 91 91 92 92 ... ... @@ -104,6 +104,7 @@ 104 104 * B20 @H-FDD: 800MHz 105 105 * B28 @H-FDD: 700MHz 106 106 132 + 107 107 == 1.7 Installation == 108 108 109 109 ... ... @@ -110,10 +110,12 @@ 110 110 Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object. 111 111 112 112 113 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]139 +[[image:image-20221207170748-1.png]] 114 114 115 115 142 + [[image:image-20221207170748-2.png||height="345" width="634"]] 116 116 144 + 117 117 == 1.8 Pin Definitions and Switch == 118 118 119 119 ... ... @@ -129,7 +129,7 @@ 129 129 130 130 The diagram below shows the working flow in the default firmware of NMDS200: 131 131 132 -[[image:image-20221021110615-5.png]] 160 +[[image:image-20221021110615-5.png||height="996" width="492"]] 133 133 134 134 135 135 == 2.2 Configure NMDS200 == ... ... @@ -143,7 +143,7 @@ 143 143 144 144 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. 145 145 146 -[[image:image-2022120 7173300-4.png]]174 +[[image:image-20221209090938-1.png]] 147 147 148 148 149 149 === 2.2.1 Insert NB-IoT SIM card === ... ... @@ -192,7 +192,6 @@ 192 192 (% 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]] 193 193 194 194 195 - 196 196 === 2.2.3 Use CoAP protocol to uplink data === 197 197 198 198 ... ... @@ -199,7 +199,7 @@ 199 199 (% 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/]] 200 200 201 201 202 -(% style="color:blue" %)**Use below commands in NDS0 3A:**229 +(% style="color:blue" %)**Use below commands in NMDS200:** 203 203 204 204 * (% style="color:#037691" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 205 205 ... ... @@ -209,7 +209,7 @@ 209 209 210 210 For parameter description, please refer to AT command set 211 211 212 -[[image: image-20221021110948-8.png]]239 +[[image:1670471530120-960.png||height="647" width="674"]] 213 213 214 214 215 215 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. ... ... @@ -228,7 +228,7 @@ 228 228 229 229 * (% style="color:#037691" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 230 230 231 - [[image: image-20221021111025-10.png]]258 + [[image:1670471559211-638.png]] 232 232 233 233 234 234 [[image:image-20221021111033-11.png||height="241" width="576"]] ... ... @@ -254,7 +254,7 @@ 254 254 255 255 * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB ** (%%) ~/~/ Set the subscription topic of MQTT 256 256 257 - [[image: image-20221118103445-7.png]]284 + [[image:1670471584490-640.png]] 258 258 259 259 260 260 [[image:1670405928926-116.png]] ... ... @@ -273,7 +273,7 @@ 273 273 274 274 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ Set TCP server address and port 275 275 276 - [[image:16704 06036256-101.png||height="676" width="713"]]303 + [[image:1670471613823-833.png]] 277 277 278 278 279 279 [[image:image-20221021111131-15.png]] ... ... @@ -300,15 +300,15 @@ 300 300 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. 301 301 302 302 303 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:5 10px" %)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 330 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:450px" %) 331 +|=(% 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** 332 +|=(% 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"]] 306 306 307 -(% border="1 .5" style="background-color:#ffffcc; color:green; width:450px" %)308 -|(% style="width: 50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((334 +(% border="1" style="background-color:#ffffcc; color:green; width:429px" %) 335 +|(% style="width:60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)((( 309 309 **1-32 group** 310 310 ))) 311 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4. 7A0Timestamp"]]| Distance 1 | Distance 2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...338 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance 2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)... 312 312 313 313 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data. 314 314 ... ... @@ -315,10 +315,8 @@ 315 315 [[image:1670406261143-723.png]] 316 316 317 317 318 -The payload is ASCII string, representative same HEX: f867787050471071 0064 90100 00ef345 +The payload is ASCII string, representative same HEX: **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__(%%)** 319 319 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__(%%)** 321 - 322 322 **where:** 323 323 324 324 * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071 ... ... @@ -339,7 +339,6 @@ 339 339 340 340 * (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time) 341 341 342 - 343 343 == 2.4 Payload Explanation and Sensor Interface == 344 344 345 345 === 2.4.1 Device ID === ... ... @@ -361,7 +361,7 @@ 361 361 362 362 Specify the software version: 0x64=100, which means firmware version 1.00. 363 363 364 -For example 0x00 64 : This device is NMDS200 1with firmware version 1.0.0.388 +For example 0x00 64 : This device is NMDS200 with firmware version 1.0.0. 365 365 366 366 367 367 === 2.4.3 Battery Info === ... ... @@ -379,17 +379,17 @@ 379 379 380 380 NB-IoT Network signal Strength. 381 381 382 -**Ex1: 0x1d = 29** 406 +(% style="color:blue" %)**Ex1: 0x1d = 29** 383 383 384 -**0** 408 +(% style="color:#037691" %)**0** (%%) -113dBm or less 385 385 386 -**1** -111dBm 410 +(% style="color:#037691" %)**1** (%%) -111dBm 387 387 388 -**2...30** -109dBm... -53dBm 412 +(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm 389 389 390 -**31** 414 +(% style="color:#037691" %)**31** (%%) -51dBm or greater 391 391 392 -**99** 416 +(% style="color:#037691" %)**99** (%%) Not known or not detectable 393 393 394 394 395 395 === 2.4.5 Distance === ... ... @@ -397,6 +397,7 @@ 397 397 398 398 [[image:1670407401682-959.png]] 399 399 424 + 400 400 (% style="color:blue" %)**Object1 Distance:** 401 401 402 402 Distance between sensor probe to the first object. (unit: cm) ... ... @@ -450,111 +450,30 @@ 450 450 The NMDS200 has an internal LED which is to show the status of different states. 451 451 452 452 * When the device starts normally, the LED will light up for 1 second. 453 -* After NDS0 3Ajoin NB-IoT network. The LED will be ON for 3 seconds.478 +* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds. 454 454 * For each uplink probe, LED will be on for 500ms. 455 455 456 456 457 - 458 458 == 2.7 Distance alarm function == 459 459 460 460 461 - NDS03Acan monitor thetimeout fora status change, this feature canbeusedtomonitor some events suchasdooropening too long etc. Related Parametersare:485 +(% style="color:blue" %)**AT Command: AT+ALARM1=min,max** 462 462 487 +(% style="color:#037691" %)**Example 1:** 463 463 464 - (%style="color:blue"%)**1.KeepStatus:Statustobemonitor**489 +AT+ ALARM1 =60,200 ~/~/ Alarm when distance1 lower than 60. 465 465 466 - KeepStatus=1: Monitor Close to Openevent491 +AT+ ALARM2 =min,max 467 467 468 -Keep Status = 0: Monitor Open to Close event 469 469 494 +(% style="color:#037691" %)**Example 2:** 470 470 471 - (%style="color:blue"%)**2.KeepTime:TimeouttosendanAlarm**496 +AT+ ALARM2 =200,1500 ~/~/ Alarm when distance2 lower than 1500. 472 472 473 -Range 0 ~~ 65535(0xFFFF) seconds. 474 474 475 - Ifkeeptime=0, DisableAlarmBase onTimeoutfeature.499 +== 2.8 Set the number of data to be uploaded and the recording time == 476 476 477 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout. 478 478 479 - 480 -(% style="color:blue" %)**AT Command to configure:** 481 - 482 -(% style="color:blue" %)**PB14 PIN:** 483 - 484 -(% 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. 485 - 486 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm. 487 - 488 - 489 -(% style="color:blue" %)**PB15 PIN:** 490 - 491 -(% style="color:#037691" %)**AT+TTRIG2=1,30** 492 - 493 -(% style="color:#037691" %)**AT+TTRIG2=0,0 ** 494 - 495 - 496 -== 2.8 Set debug mode == 497 - 498 - 499 -Feature: Enable or Disable debug mode 500 - 501 -(% style="color:blue" %)**AT Command: AT+DEBUG** 502 - 503 -[[image:image-20221021111629-21.png]] 504 - 505 - 506 - 507 -== 2.9 Clear Flash Record == 508 - 509 - 510 -Feature: Clear flash storage for data log feature. 511 - 512 -(% style="color:blue" %)**AT Command: AT+CLRDTA** 513 - 514 -[[image:image-20221021111527-19.png]] 515 - 516 - 517 -== 2.10 Count Mod == 518 - 519 - 520 -(% style="color:blue" %)**AT Command: AT+COUNTMOD** 521 - 522 -[[image:image-20221118092935-1.png]] 523 - 524 - 525 -== 2.11 Interrupt Pin Channel Mod == 526 - 527 - 528 -(% style="color:blue" %)**AT Command: AT+TTRCHANNEL** 529 - 530 -[[image:image-20221118093144-2.png]] 531 - 532 - 533 -== 2.12 TTRIG1/2 timeout status alarm == 534 - 535 - 536 -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. 537 - 538 -(% style="color:blue" %)**AT Command: AT+TTRALARM** 539 - 540 -[[image:image-20221118093512-3.png]] 541 - 542 - 543 -== 2.13 Select counting mode == 544 - 545 - 546 -(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b** 547 - 548 -When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted. 549 - 550 -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. 551 - 552 -[[image:image-20221118093658-4.png]] 553 - 554 - 555 -== 2.14 Set the number of data to be uploaded and the recording time == 556 - 557 - 558 558 (% style="color:blue" %)**AT Command:** 559 559 560 560 (% 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) ... ... @@ -562,7 +562,7 @@ 562 562 (% 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. 563 563 564 564 565 -== 2. 15Read or Clear cached data ==509 +== 2.9 Read or Clear cached data == 566 566 567 567 568 568 (% style="color:blue" %)**AT Command:** ... ... @@ -571,71 +571,24 @@ 571 571 572 572 (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 573 573 574 -[[image: image-20221118094227-5.png]]518 +[[image:1670408172929-569.png]] 575 575 576 576 577 -== 2.1 6Firmware Change Log ==521 +== 2.10 Firmware Change Log == 578 578 579 579 580 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/ hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]524 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0>>https://www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0]] 581 581 582 582 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 583 583 584 584 585 -== 2.1 7BatteryAnalysis==529 +== 2.11 Battery & Power Consumption == 586 586 587 -=== 2.17.1 Battery Type === 588 588 532 +NMDS200 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 589 589 590 - The NDS03A batteryisacombinationof an 8500mAh Li/SOCI2 Battery andaSuperCapacitor. The batteryisnon-rechargeablebattery typewithaow discharge rate(<2%per year). Thistypeofbatterys commonly used inIoT devicessuch as water meter.534 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 591 591 592 -The battery is designed to last for several years depends on the actual use environment and update interval. 593 - 594 -The battery-related documents as below: 595 - 596 -* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 597 - 598 -* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 599 - 600 -* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 601 - 602 -[[image:image-20221021111911-26.png]] 603 - 604 - 605 -=== 2.17.2 Power consumption Analyze === 606 - 607 - 608 -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. 609 - 610 -Instruction to use as below: 611 - 612 -(% style="color:blue" %)**Step 1: **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]] 613 - 614 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose 615 - 616 -* Product Model 617 - 618 -* Uplink Interval 619 - 620 -* Working Mode 621 - 622 -And the Life expectation in difference case will be shown on the right. 623 - 624 -[[image:1666596205057-567.png]] 625 - 626 - 627 -=== 2.17.3 Battery Note === 628 - 629 - 630 -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. 631 - 632 - 633 -=== 2.17.4 Replace the battery === 634 - 635 - 636 -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). 637 - 638 - 639 639 = 3. Access NB-IoT Module = 640 640 641 641 ... ... @@ -679,65 +679,59 @@ 679 679 680 680 AT+INTMOD : Set the trigger interrupt mode 681 681 682 -AT+5VT 579 +AT+5VT : Set extend the time of 5V power 683 683 684 -AT+PRO 581 +AT+PRO : Choose agreement 685 685 686 -AT+RXDL 583 +AT+RXDL : Extend the sending and receiving time 687 687 688 -AT+SERVADDR 585 +AT+SERVADDR : Server Address 689 689 690 -AT+TR : 587 +AT+TR : Get or Set record time 691 691 692 -AT+NOUD 589 +AT+NOUD : Get or Set the number of data to be uploaded 693 693 694 694 AT+CDP : Read or Clear cached data 695 695 696 -AT+ :Enable or Disable debug mode593 +AT+DEBUG: Enable or Disable debug mode 697 697 698 -AT+ TTRIG1:Get or SetPB14 PIN AlarmBaseonTimeout595 +AT+ALARM1: Get or Set alarm of distance1 699 699 700 -AT+ TTRIG2:Get or SetPB15 PIN AlarmBaseonTimeout597 +AT+ALARM2: Get or Set alarm of distance2 701 701 702 -AT+ COUNTMOD:GetorSetthe countmode599 +AT+GETSENSORVALUE : Returns the current sensor measurement 703 703 704 -AT+ TTRCHANNEL: Get orSet thenumberof interruptchannels601 +AT+POWERIC : Get or set the Power IC flag 705 705 706 -AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute) 707 707 708 -AT+DISALARM : Enable/Disable Alarm for door open/close or water leak event 709 - 710 -AT+ CLRC : Clear current door open count 711 - 712 - 713 713 (% style="color:blue" %)**COAP Management** 714 714 715 -AT+URI 606 +AT+URI : Resource parameters 716 716 717 717 718 718 (% style="color:blue" %)**UDP Management** 719 719 720 -AT+CFM 611 +AT+CFM : Upload confirmation mode (only valid for UDP) 721 721 722 722 723 723 (% style="color:blue" %)**MQTT Management** 724 724 725 -AT+CLIENT 616 +AT+CLIENT : Get or Set MQTT client 726 726 727 -AT+UNAME 618 +AT+UNAME : Get or Set MQTT Username 728 728 729 -AT+PWD 620 +AT+PWD : Get or Set MQTT password 730 730 731 -AT+PUBTOPIC :Get or Set MQTT publish topic622 +AT+PUBTOPIC : Get or Set MQTT publish topic 732 732 733 -AT+SUBTOPIC :Get or Set MQTT subscription topic624 +AT+SUBTOPIC : Get or Set MQTT subscription topic 734 734 735 735 736 736 (% style="color:blue" %)**Information** 737 737 738 -AT+FDR :Factory Data Reset629 +AT+FDR : Factory Data Reset 739 739 740 -AT+PWORD 631 +AT+PWORD : Serial Access Password 741 741 742 742 743 743 = 5. FAQ = ... ... @@ -749,7 +749,7 @@ 749 749 750 750 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]] 751 751 752 -(% style="color:red" %)**Notice: **(% style="color:blue" %)**NDS0 3A** (%%)**and (% style="color:blue" %)LDS03A(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**643 +(% 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.** 753 753 754 754 755 755 = 6. Trouble Shooting = ... ... @@ -769,7 +769,7 @@ 769 769 = 7. Order Info = 770 770 771 771 772 -Part Number **:** NDS03A663 +Part Number:(% style="color:blue" %)** NMDS200** 773 773 774 774 775 775 = 8. Packing Info = ... ... @@ -777,8 +777,9 @@ 777 777 778 778 (% style="color:blue" %)**Package Includes**: 779 779 780 -* NDS0 3AOpen/CloseDoor Sensor x 1671 +* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1 781 781 673 + 782 782 = 9. Support = 783 783 784 784
- 1670408172929-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +211.8 KB - Content
- 1670471530120-960.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +67.6 KB - Content
- 1670471559211-638.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +170.6 KB - Content
- 1670471584490-640.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +91.1 KB - Content
- 1670471613823-833.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +181.0 KB - Content
- image-20221208090742-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +79.7 KB - Content
- image-20221209090938-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +121.9 KB - Content
- image-20221212171610-1.jpeg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +756.0 KB - Content