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, 8 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,28 +1,13 @@ 1 1 (% style="text-align:center" %) 2 -[[image:LMDS200_10.jpg ||height="572" width="572"]]2 +[[image:LMDS200_10.jpg]] 3 3 4 4 5 - 6 - 7 - 8 -(% style="display:none" %) (%%) 9 - 10 - 11 - 12 - 13 - 14 14 **Table of Contents:** 15 15 16 -{{toc/}} 17 17 18 18 19 19 20 20 21 - 22 - 23 - 24 - 25 - 26 26 = 1. Introduction = 27 27 28 28 == 1.1 What is NMDS200 NB-IoT Microwave Radar Distance Sensor == ... ... @@ -30,37 +30,25 @@ 30 30 31 31 ((( 32 32 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 -))) 34 34 35 - (((19 + 36 36 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 -))) 38 38 39 -((( 40 40 NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one. 41 -))) 42 42 43 -((( 44 44 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 -))) 46 46 47 -((( 48 48 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 -))) 50 50 51 -((( 52 52 NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements. 53 -))) 54 54 55 -((( 56 56 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 -))) 58 58 59 -((( 60 60 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. 61 61 ))) 62 62 63 63 36 + 64 64 == 1.2 Features == 65 65 66 66 ... ... @@ -78,15 +78,13 @@ 78 78 * Micro SIM card slot for NB-IoT SIM 79 79 * 8500mAh Battery for long-term use 80 80 81 - 82 - 83 83 == 1.3 Radar probe specification == 84 84 85 85 86 86 * Measuring Method: FMCW 87 -* Frequency: 24.000 ~~24.500 GHz58 +* Frequency: 24.000 24.500 GHz 88 88 * Measurement output power: 6dBm 89 -* Measure range: 0.5 ~~20m60 +* Measure range: 0.5 20m 90 90 * Accuracy: ±0.1m 91 91 * Resolution: 0.01m 92 92 * Horizontal Angel: 78° ... ... @@ -93,7 +93,6 @@ 93 93 * Vertical Angel: 23° 94 94 95 95 96 - 97 97 == 1.4 Storage Temperature == 98 98 99 99 ... ... @@ -100,9 +100,13 @@ 100 100 -40°C to +85°C 101 101 102 102 73 + 74 + 75 + 103 103 == 1.5 Applications == 104 104 105 105 79 + 106 106 * Horizontal distance measurement 107 107 * Liquid level measurement 108 108 * Parking management system ... ... @@ -113,8 +113,6 @@ 113 113 * Sewer 114 114 * Bottom water level monitoring 115 115 116 - 117 - 118 118 == 1.6 Specification == 119 119 120 120 ... ... @@ -132,8 +132,6 @@ 132 132 * B20 @H-FDD: 800MHz 133 133 * B28 @H-FDD: 700MHz 134 134 135 - 136 - 137 137 == 1.7 Installation == 138 138 139 139 ... ... @@ -140,12 +140,10 @@ 140 140 Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object. 141 141 142 142 143 -[[image:image-20221207170748-1.png]] 113 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]] 144 144 145 145 146 - [[image:image-20221207170748-2.png||height="345" width="634"]] 147 147 148 - 149 149 == 1.8 Pin Definitions and Switch == 150 150 151 151 ... ... @@ -161,7 +161,7 @@ 161 161 162 162 The diagram below shows the working flow in the default firmware of NMDS200: 163 163 164 -[[image:image-20221021110615-5.png ||height="996" width="492"]]132 +[[image:image-20221021110615-5.png]] 165 165 166 166 167 167 == 2.2 Configure NMDS200 == ... ... @@ -175,7 +175,7 @@ 175 175 176 176 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. 177 177 178 -[[image:image-2022120 9090938-1.png]]146 +[[image:image-20221207173300-4.png]] 179 179 180 180 181 181 === 2.2.1 Insert NB-IoT SIM card === ... ... @@ -224,6 +224,7 @@ 224 224 (% 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]] 225 225 226 226 195 + 227 227 === 2.2.3 Use CoAP protocol to uplink data === 228 228 229 229 ... ... @@ -230,7 +230,7 @@ 230 230 (% 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/]] 231 231 232 232 233 -(% style="color:blue" %)**Use below commands in N MDS200:**202 +(% style="color:blue" %)**Use below commands in NDS03A:** 234 234 235 235 * (% style="color:#037691" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 236 236 ... ... @@ -240,7 +240,7 @@ 240 240 241 241 For parameter description, please refer to AT command set 242 242 243 -[[image: 1670471530120-960.png||height="647" width="674"]]212 +[[image:image-20221021110948-8.png]] 244 244 245 245 246 246 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. ... ... @@ -259,7 +259,7 @@ 259 259 260 260 * (% style="color:#037691" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 261 261 262 - [[image: 1670471559211-638.png]]231 + [[image:image-20221021111025-10.png]] 263 263 264 264 265 265 [[image:image-20221021111033-11.png||height="241" width="576"]] ... ... @@ -285,7 +285,7 @@ 285 285 286 286 * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB ** (%%) ~/~/ Set the subscription topic of MQTT 287 287 288 - [[image: 1670471584490-640.png]]257 + [[image:image-20221118103445-7.png]] 289 289 290 290 291 291 [[image:1670405928926-116.png]] ... ... @@ -304,7 +304,7 @@ 304 304 305 305 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ Set TCP server address and port 306 306 307 - [[image:16704 71613823-833.png]]276 + [[image:1670406036256-101.png||height="676" width="713"]] 308 308 309 309 310 310 [[image:image-20221021111131-15.png]] ... ... @@ -331,15 +331,15 @@ 331 331 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. 332 332 333 333 334 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width: 450px" %)335 -|=(% 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**336 -|=(% 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"]]303 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 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 337 337 338 -(% border="1" style="background-color:#ffffcc; color:green; width:4 29px" %)339 -|(% style="width: 60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)(((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" %)((( 340 340 **1-32 group** 341 341 ))) 342 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4. 6A0Timestamp"]]| Distance 1 | Distance 2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)...311 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance 2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)... 343 343 344 344 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data. 345 345 ... ... @@ -346,8 +346,10 @@ 346 346 [[image:1670406261143-723.png]] 347 347 348 348 349 -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__(%%)**318 +The payload is ASCII string, representative same HEX: f867787050471071 0064 0cc3 09 01 00 00ef 013d 6390453d 350 350 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 + 351 351 **where:** 352 352 353 353 * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071 ... ... @@ -369,7 +369,6 @@ 369 369 * (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time) 370 370 371 371 372 - 373 373 == 2.4 Payload Explanation and Sensor Interface == 374 374 375 375 === 2.4.1 Device ID === ... ... @@ -391,7 +391,7 @@ 391 391 392 392 Specify the software version: 0x64=100, which means firmware version 1.00. 393 393 394 -For example 0x00 64 : This device is NMDS200 with firmware version 1.0.0. 364 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0. 395 395 396 396 397 397 === 2.4.3 Battery Info === ... ... @@ -409,17 +409,17 @@ 409 409 410 410 NB-IoT Network signal Strength. 411 411 412 - (% style="color:blue" %)**Ex1: 0x1d = 29**382 +**Ex1: 0x1d = 29** 413 413 414 - (% style="color:#037691" %)**0**(%%)384 +**0** -113dBm or less 415 415 416 - (% style="color:#037691" %)**1**(%%)386 +**1** -111dBm 417 417 418 - (% style="color:#037691" %)**2...30**(%%)-109dBm... -53dBm388 +**2...30** -109dBm... -53dBm 419 419 420 - (% style="color:#037691" %)**31**(%%)390 +**31** -51dBm or greater 421 421 422 - (% style="color:#037691" %)**99**(%%)392 +**99** Not known or not detectable 423 423 424 424 425 425 === 2.4.5 Distance === ... ... @@ -427,7 +427,6 @@ 427 427 428 428 [[image:1670407401682-959.png]] 429 429 430 - 431 431 (% style="color:blue" %)**Object1 Distance:** 432 432 433 433 Distance between sensor probe to the first object. (unit: cm) ... ... @@ -481,7 +481,7 @@ 481 481 The NMDS200 has an internal LED which is to show the status of different states. 482 482 483 483 * When the device starts normally, the LED will light up for 1 second. 484 -* After N MDS200join NB-IoT network. The LED will be ON for 3 seconds.453 +* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds. 485 485 * For each uplink probe, LED will be on for 500ms. 486 486 487 487 ... ... @@ -489,23 +489,103 @@ 489 489 == 2.7 Distance alarm function == 490 490 491 491 492 - (%style="color:blue"%)**ATCommand:AT+ALARM1=min,max**461 +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: 493 493 494 -(% style="color:#037691" %)**Example 1:** 495 495 496 - AT+ALARM1=60,200 ~/~/ Alarmwhendistance1lowerthan60.464 +(% style="color:blue" %)**1. Keep Status: Status to be monitor** 497 497 498 - AT+ALARM2=min,max466 +Keep Status = 1: Monitor Close to Open event 499 499 468 +Keep Status = 0: Monitor Open to Close event 500 500 501 -(% style="color:#037691" %)**Example 2:** 502 502 503 - AT+ALARM2=200,1500~/~/ Alarmwhendistance2lowerthan1500.471 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm** 504 504 473 +Range 0 ~~ 65535(0xFFFF) seconds. 505 505 506 - ==2.8 Set thenumberofdatatobeuploadedand therecordingtime==475 +If keep time = 0, Disable Alarm Base on Timeout feature. 507 507 477 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout. 508 508 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 + 509 509 (% style="color:blue" %)**AT Command:** 510 510 511 511 (% 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) ... ... @@ -513,7 +513,7 @@ 513 513 (% 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. 514 514 515 515 516 -== 2. 9Read or Clear cached data ==565 +== 2.15 Read or Clear cached data == 517 517 518 518 519 519 (% style="color:blue" %)**AT Command:** ... ... @@ -522,25 +522,71 @@ 522 522 523 523 (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 524 524 525 -[[image:1 670408172929-569.png]]574 +[[image:image-20221118094227-5.png]] 526 526 527 527 528 -== 2.1 0Firmware Change Log ==577 +== 2.16 Firmware Change Log == 529 529 530 530 531 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8 elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0>>https://www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0]]580 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]] 532 532 533 533 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 534 534 535 535 536 -== 2.1 1& Power Consumption==585 +== 2.17 Battery Analysis == 537 537 587 +=== 2.17.1 Battery Type === 538 538 539 -NMDS200 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 540 540 541 - [[**BatteryInfo&Power ConsumptionAnalyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]].590 +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. 542 542 592 +The battery is designed to last for several years depends on the actual use environment and update interval. 543 543 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 + 544 544 = 3. Access NB-IoT Module = 545 545 546 546 ... ... @@ -584,59 +584,65 @@ 584 584 585 585 AT+INTMOD : Set the trigger interrupt mode 586 586 587 -AT+5VT : Set extend the time of 5V power 682 +AT+5VT : Set extend the time of 5V power 588 588 589 -AT+PRO : Choose agreement 684 +AT+PRO : Choose agreement 590 590 591 -AT+RXDL : Extend the sending and receiving time 686 +AT+RXDL : Extend the sending and receiving time 592 592 593 -AT+SERVADDR : Server Address 688 +AT+SERVADDR : Server Address 594 594 595 -AT+TR : Get or Set record time 690 +AT+TR : Get or Set record time 596 596 597 -AT+NOUD : 692 +AT+NOUD : Get or Set the number of data to be uploaded 598 598 599 599 AT+CDP : Read or Clear cached data 600 600 601 -AT+DEBUG :Enable or Disable debug mode696 +AT+ DEBUG : Enable or Disable debug mode 602 602 603 -AT+ ALARM1:Get or Setalarm ofdistance1698 +AT+ TTRIG1 : Get or Set PB14 PIN Alarm Base on Timeout 604 604 605 -AT+ ALARM2:Get or Setalarm ofdistance2700 +AT+ TTRIG2 : Get or Set PB15 PIN Alarm Base on Timeout 606 606 607 -AT+ GETSENSORVALUE:Returnsthe currentsensormeasurement702 +AT+COUNTMOD : Get or Set the count mode 608 608 609 -AT+ POWERIC :set thePowerICflag704 +AT+TTRCHANNEL : Get or Set the number of interrupt channels 610 610 706 +AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute) 611 611 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 + 612 612 (% style="color:blue" %)**COAP Management** 613 613 614 -AT+URI : 715 +AT+URI : Resource parameters 615 615 616 616 617 617 (% style="color:blue" %)**UDP Management** 618 618 619 -AT+CFM : 720 +AT+CFM : Upload confirmation mode (only valid for UDP) 620 620 621 621 622 622 (% style="color:blue" %)**MQTT Management** 623 623 624 -AT+CLIENT : Get or Set MQTT client 725 +AT+CLIENT : Get or Set MQTT client 625 625 626 -AT+UNAME : Get or Set MQTT Username 727 +AT+UNAME : Get or Set MQTT Username 627 627 628 -AT+PWD : 729 +AT+PWD : Get or Set MQTT password 629 629 630 -AT+PUBTOPIC :Get or Set MQTT publish topic731 +AT+PUBTOPIC : Get or Set MQTT publish topic 631 631 632 -AT+SUBTOPIC :Get or Set MQTT subscription topic733 +AT+SUBTOPIC : Get or Set MQTT subscription topic 633 633 634 634 635 635 (% style="color:blue" %)**Information** 636 636 637 -AT+FDR :Factory Data Reset738 +AT+FDR : Factory Data Reset 638 638 639 -AT+PWORD :Serial Access Password740 +AT+PWORD : Serial Access Password 640 640 641 641 642 642 = 5. FAQ = ... ... @@ -648,7 +648,7 @@ 648 648 649 649 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]] 650 650 651 -(% 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.**752 +(% 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.** 652 652 653 653 654 654 = 6. Trouble Shooting = ... ... @@ -668,7 +668,7 @@ 668 668 = 7. Order Info = 669 669 670 670 671 -Part Number: (% style="color:blue" %)** NMDS200**772 +Part Number**:** NDS03A 672 672 673 673 674 674 = 8. Packing Info = ... ... @@ -676,10 +676,8 @@ 676 676 677 677 (% style="color:blue" %)**Package Includes**: 678 678 679 -* N MDS200NB-IoT MicrowaveRadarDistanceSensor x 1780 +* NDS03A Open/Close Door Sensor x 1 680 680 681 - 682 - 683 683 = 9. Support = 684 684 685 685
- 1670408172929-569.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -211.8 KB - Content
- 1670471530120-960.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -67.6 KB - Content
- 1670471559211-638.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -170.6 KB - Content
- 1670471584490-640.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -91.1 KB - Content
- 1670471613823-833.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -181.0 KB - Content
- image-20221208090742-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -79.7 KB - Content
- image-20221209090938-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -121.9 KB - Content
- image-20221212171610-1.jpeg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -756.0 KB - Content