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 (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 5 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -N MDS200- NB-IoTMicrowaveRadarDistanceSensor User Manual1 +NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual - Content
-
... ... @@ -1,35 +1,55 @@ 1 1 (% style="text-align:center" %) 2 -[[image: LMDS200_10.jpg]]2 +[[image:image-20221117105556-1.png]] 3 3 4 4 5 + 6 + 7 + 8 + 9 + 5 5 **Table of Contents:** 6 6 12 +{{toc/}} 7 7 8 8 9 9 10 10 17 + 11 11 = 1. Introduction = 12 12 13 -== 1.1 What is N MDS200NB-IoTMicrowaveRadarDistanceSensor ==20 +== 1.1 What is NDS03A NB-IoT Open/Close Door Sensor == 14 14 15 15 16 16 ((( 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. 24 +The Dragino NDS03A is an (% style="color:blue" %)**Open/Close NB-IoT Door Sensor**(%%). It detects door (% style="color:blue" %)**open/close status**(%%) and (% style="color:blue" %)**uplinks**(%%) to IoT server via NB-IoT network. NDS03A can connect two door sensors. user can see the door status, open duration, open counts in the IoT Server. 25 +))) 18 18 27 +((( 28 +The NDS03A will send periodically data (% style="color:blue" %)**every 4 hours** (%%)as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically. 29 +))) 19 19 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. 31 +((( 32 +NDS03A has a (% style="color:blue" %)**Datalog feature**(%%), it will record the open/close event and the user can retrieve the history from NB-IoT. 33 +))) 21 21 22 -NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one. 35 +((( 36 +NDS03A has the(% style="color:blue" %)**open alarm feature**(%%), user can set this feature so the device will send an alarm if the door has been open for a certain time. 37 +))) 23 23 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. 39 +((( 40 +NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures. 41 +))) 25 25 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. 43 +((( 44 +NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technologyTCP, MQTT, UDP, and CoAP**(%%) for different application requirements. 45 +))) 27 27 28 -NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements. 47 +((( 48 +NDS03A 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) 49 +))) 29 29 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) 31 - 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. 51 +((( 52 +To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into NDS03A to get NB-IoT network connection. 33 33 ))) 34 34 35 35 ... ... @@ -38,9 +38,10 @@ 38 38 39 39 40 40 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 41 -* Short uplink interval for Distance Alarm 61 +* Open/Close detect 62 +* Open/Close statistics 42 42 * Monitor Battery Level 43 -* MicrowaveRadarfordistancedetection64 +* connect two door sensors 44 44 * Datalog feature 45 45 * Uplink periodically 46 46 * Downlink to change configure ... ... @@ -53,27 +53,22 @@ 53 53 54 54 55 55 56 -== 1.3 Radar probespecification ==77 +== 1.3 Storage & Operation == 57 57 58 58 59 -* Measuring Method: FMCW 60 -* Frequency: 24.000 24.500 GHz 61 -* Measurement output power: 6dBm 62 -* Measure range: 0.5 20m 63 -* Accuracy: ±0.1m 64 -* Resolution: 0.01m 65 -* Horizontal Angel: 78° 66 -* Vertical Angel: 23° 80 +Temperature -40°C to +85°C 67 67 68 68 83 +== 1.4 Mechanical == 69 69 70 70 71 - == 1.4 StorageTemperature==86 +[[image:image-20221117114937-4.png]] 72 72 73 73 74 - 40°C to +85°C89 +[[image:image-20221117114949-5.png]] 75 75 76 76 92 +[[image:image-20221117115010-6.png]] 77 77 78 78 79 79 ... ... @@ -80,19 +80,10 @@ 80 80 == 1.5 Applications == 81 81 82 82 99 +[[image:image-20221117114842-3.png]] 83 83 84 -* Horizontal distance measurement 85 -* Liquid level measurement 86 -* Parking management system 87 -* Object proximity and presence detection 88 -* Intelligent trash can management system 89 -* Robot obstacle avoidance 90 -* Automatic control 91 -* Sewer 92 -* Bottom water level monitoring 93 93 94 94 95 - 96 96 == 1.6 Specification == 97 97 98 98 ... ... @@ -99,47 +99,88 @@ 99 99 (% style="color:blue" %)**Common DC Characteristics:** 100 100 101 101 * Supply Voltage: 2.1v ~~ 3.6v 102 -* Operating Temperature: 0 ~~ 70°C109 +* Operating Temperature: -40 ~~ 85°C 103 103 104 104 (% style="color:blue" %)**NB-IoT Spec:** 105 105 106 -* B1 @H-FDD: 2100MHz 107 -* B3 @H-FDD: 1800MHz 108 -* B8 @H-FDD: 900MHz 109 -* B5 @H-FDD: 850MHz 110 -* B20 @H-FDD: 800MHz 111 -* B28 @H-FDD: 700MHz 113 +* - B1 @H-FDD: 2100MHz 114 +* - B3 @H-FDD: 1800MHz 115 +* - B8 @H-FDD: 900MHz 116 +* - B5 @H-FDD: 850MHz 117 +* - B20 @H-FDD: 800MHz 118 +* - B28 @H-FDD: 700MHz 112 112 113 113 114 114 115 -== 1.7 Installation ==122 +== 1.7 Pin Definitions and Switch == 116 116 117 117 118 - Sensormeasuredirectionand angleis as below.When install the sensor,please make sure the sensor direct to object.125 +[[image:image-20221021110429-4.png]] 119 119 120 120 121 - [[image:image-20221207170748-1.png]][[image:image-20221207170748-2.png||height="366" width="672"]]128 +=== 1.7.1 Pin Definition === 122 122 123 123 131 +The device is pre-configured to connect to a door sensor. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at: [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]] 124 124 125 -== 1.8 Pin Definitions and Switch == 126 126 127 127 128 - [[image:1670404362039-351.png]]135 +=== 1.7.2 Jumper JP2(Power ON/OFF) === 129 129 130 130 131 - = 2. UseNMDS200 tocommunicate withIoT Server =138 +Power on Device when putting this jumper. 132 132 140 + 141 + 142 +=== 1.7.3 BOOT MODE / SW1 === 143 + 144 + 145 +1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run. 146 + 147 +2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging. 148 + 149 + 150 + 151 +=== 1.7.4 Reset Button === 152 + 153 + 154 +Press to reboot the device. 155 + 156 + 157 + 158 +=== 1.7.5 LED === 159 + 160 + 161 +The LED will blink when : 162 + 163 +1. Boot the device in flash mode 164 + 165 +2. Send an uplink packet 166 + 167 + 168 + 169 +== 1.8 Magnet Distance == 170 + 171 + 172 +(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm 173 + 174 +(% style="color:blue" %)**Iron Door:**(%%)** **30 ~~ 45mm 175 + 176 + 177 + 178 += 2. Use NDS03A to communicate with IoT Server = 179 + 133 133 == 2.1 How it works == 134 134 135 135 136 -The NB-IoT network will forward this value to IoT server via the protocol defined by N MDS200.183 +In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A. 137 137 138 -The diagram below shows the working flow in the default firmware of N MDS200:185 +The diagram below shows the working flow in the default firmware of NDS03A: 139 139 140 140 [[image:image-20221021110615-5.png]] 141 141 142 142 190 + 143 143 == 2.2 Configure NDS03A == 144 144 145 145 === 2.2.1 Test Requirement === ... ... @@ -155,7 +155,9 @@ 155 155 156 156 [[image:image-20221117142300-1.png]] 157 157 206 + 158 158 208 + 159 159 === 2.2.2 Insert NB-IoT SIM card === 160 160 161 161 ... ... @@ -166,6 +166,7 @@ 166 166 [[image:image-20221021110745-6.png]] 167 167 168 168 219 + 169 169 === 2.2.3 Connect USB – TTL to NDS03A and configure it === 170 170 171 171 ... ... @@ -227,6 +227,7 @@ 227 227 [[image:image-20221118103547-9.png||height="605" width="837"]] 228 228 229 229 281 + 230 230 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 231 231 232 232 ... ... @@ -245,6 +245,7 @@ 245 245 246 246 247 247 300 + 248 248 === 2.2.6 Use MQTT protocol to uplink data === 249 249 250 250 ... ... @@ -274,6 +274,7 @@ 274 274 MQTT protocol has a much higher power consumption compare with UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 275 275 276 276 330 + 277 277 === 2.2.7 Use TCP protocol to uplink data === 278 278 279 279 ... ... @@ -289,6 +289,7 @@ 289 289 290 290 291 291 346 + 292 292 === 2.2.8 Change Update Interval === 293 293 294 294 ... ... @@ -301,6 +301,7 @@ 301 301 1. By default, the device will send an uplink message every 4 hour. 302 302 303 303 359 + 304 304 == 2.3 Uplink Payload == 305 305 306 306 ... ... @@ -310,32 +310,34 @@ 310 310 311 311 (% style="color:blue" %)**When AT+TTRCHANNEL=1:** 312 312 313 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width: 510px" %)314 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:60px" %)**1**|(% style="width:90px" %)**3**|(% style="width:100px" %)**3**369 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %) 370 +|=(% 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** 315 315 |=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14) 316 316 317 -(% border="1.5" style="background-color:#ffffcc; color:green; width:4 50px" %)318 -|(% style="width:50px" %)**4**|(% style="width: 90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((373 +(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %) 374 +|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:99px" %)**3**|(% style="width:67px" %)4|(% style="width:50px" %)((( 319 319 **1-32 group** 320 320 ))) 321 321 |(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:115px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)|(% style="width:99px" %)last open time(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)... 322 322 379 + 380 + 323 323 (% style="color:blue" %)**When AT+TTRCHANNEL=2:** 324 324 325 325 326 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:5 10px" %)327 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:45px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:60px" %)**1**|(% style="width:60px" %)**1**|(% style="width:87px" %)**3**|(% style="width:80px" %)**3**384 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %) 385 +|=(% 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** 328 328 |=(% style="width: 96px;" %)**Value**|(% style="width:66px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:70px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:55px" %)Door Status(pb14)|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb14)|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14) 329 329 330 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:5 10px" %)331 -|(% style="width: 80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:75px" %)**1**|(% style="width:75px" %)**3**388 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %) 389 +|(% 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** 332 332 |(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14) 333 333 334 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:5 10px" %)335 -|(% style="width:10 0px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((392 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %) 393 +|(% style="width:102px" %)**3**|(% style="width:93px" %)**1**|(% style="width:91px" %)**3**|(% style="width:88px" %)**3**|(% style="width:63px" %)**4**|(% style="width:87px" %)((( 336 336 **1-32 group** 337 337 ))) 338 -|(% style="width:102px" %)last open time(pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width: 100px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......396 +|(% 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>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)...... 339 339 340 340 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data. 341 341 ... ... @@ -364,10 +364,12 @@ 364 364 365 365 * (% style="color:#037691" %)**door open num: **(%%)0x000016 =22 366 366 367 -* (% style="color:#037691" %)**last open time: 425 +* (% style="color:#037691" %)**last open time: **(%%)0x000017 =23 368 368 369 369 * (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time) 370 370 429 + 430 + 371 371 == 2.4 Payload Explanation and Sensor Interface == 372 372 373 373 === 2.4.1 Device ID === ... ... @@ -484,6 +484,8 @@ 484 484 * 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 547 + 548 + 487 487 == 2.7 Alarm Base on Timeout == 488 488 489 489 ... ... @@ -543,6 +543,7 @@ 543 543 [[image:image-20221021111527-19.png]] 544 544 545 545 608 + 546 546 == 2.10 Count Mod == 547 547 548 548 ... ... @@ -551,6 +551,7 @@ 551 551 [[image:image-20221118092935-1.png]] 552 552 553 553 617 + 554 554 == 2.11 Interrupt Pin Channel Mod == 555 555 556 556 ... ... @@ -559,6 +559,7 @@ 559 559 [[image:image-20221118093144-2.png]] 560 560 561 561 626 + 562 562 == 2.12 TTRIG1/2 timeout status alarm == 563 563 564 564 ... ... @@ -569,6 +569,7 @@ 569 569 [[image:image-20221118093512-3.png]] 570 570 571 571 637 + 572 572 == 2.13 Select counting mode == 573 573 574 574 ... ... @@ -581,6 +581,8 @@ 581 581 [[image:image-20221118093658-4.png]] 582 582 583 583 650 + 651 + 584 584 == 2.14 Set the number of data to be uploaded and the recording time == 585 585 586 586 ... ... @@ -603,6 +603,7 @@ 603 603 [[image:image-20221118094227-5.png]] 604 604 605 605 674 + 606 606 == 2.16 Firmware Change Log == 607 607 608 608 ... ... @@ -611,8 +611,10 @@ 611 611 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 612 612 613 613 683 + 614 614 == 2.17 Battery Analysis == 615 615 686 + 616 616 === 2.17.1 Battery Type === 617 617 618 618 ... ... @@ -631,6 +631,7 @@ 631 631 [[image:image-20221021111911-26.png]] 632 632 633 633 705 + 634 634 === 2.17.2 Power consumption Analyze === 635 635 636 636 ... ... @@ -653,6 +653,7 @@ 653 653 [[image:1666596205057-567.png]] 654 654 655 655 728 + 656 656 === 2.17.3 Battery Note === 657 657 658 658 ... ... @@ -659,6 +659,7 @@ 659 659 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. 660 660 661 661 735 + 662 662 === 2.17.4 Replace the battery === 663 663 664 664 ... ... @@ -665,6 +665,7 @@ 665 665 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). 666 666 667 667 742 + 668 668 = 3. Access NB-IoT Module = 669 669 670 670 ... ... @@ -672,12 +672,13 @@ 672 672 673 673 The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 674 674 675 - 676 676 [[image:image-20221118094449-6.png]] 677 677 678 678 753 + 679 679 = 4. Using the AT Commands = 680 680 756 + 681 681 == 4.1 Access AT Commands == 682 682 683 683 ... ... @@ -769,8 +769,10 @@ 769 769 AT+PWORD : Serial Access Password 770 770 771 771 848 + 772 772 = 5. FAQ = 773 773 851 + 774 774 == 5.1 How to Upgrade Firmware == 775 775 776 776 ... ... @@ -781,8 +781,10 @@ 781 781 (% 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.** 782 782 783 783 862 + 784 784 = 6. Trouble Shooting = 785 785 865 + 786 786 == 6.1 Connection problem when uploading firmware == 787 787 788 788 ... ... @@ -789,6 +789,7 @@ 789 789 (% style="color:blue" %)**Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]] 790 790 791 791 872 + 792 792 == 6.2 AT Command input doesn't work == 793 793 794 794 ... ... @@ -795,6 +795,7 @@ 795 795 In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER** (%%)while press the send key, user need to add ENTER in their string. 796 796 797 797 879 + 798 798 = 7. Order Info = 799 799 800 800 ... ... @@ -801,6 +801,7 @@ 801 801 Part Number**:** NDS03A 802 802 803 803 886 + 804 804 = 8. Packing Info = 805 805 806 806
- 1670404362039-351.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -492.6 KB - Content
- LMDS200_10.jpg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -39.9 KB - Content
- image-20221207170748-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -26.1 KB - Content
- image-20221207170748-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -29.9 KB - Content
- image-20221207173200-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -76.7 KB - Content