Changes for page NDDS75 -- NB-IoT Distance Detect Sensor User Manual
Last modified by Bei Jinggeng on 2024/05/31 09:53
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -16,6 +16,7 @@ 16 16 17 17 = 1. Introduction = 18 18 19 + 19 19 == 1.1 What is NDDS75 Distance Detection Sensor == 20 20 21 21 ((( ... ... @@ -22,20 +22,34 @@ 22 22 23 23 24 24 ((( 26 +((( 25 25 The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data. 26 -\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network. 27 -\\NarrowBand-Internet of Things (NB-IoT) is a 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. 28 -\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 29 -\\NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 30 -\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection. 31 31 ))) 32 32 33 - 30 +((( 31 +The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network. 34 34 ))) 35 35 36 -[[image:1654503236291-817.png]] 34 +((( 35 +NarrowBand-Internet of Things (NB-IoT) is a 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. 36 +))) 37 37 38 +((( 39 +NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 40 +))) 38 38 42 +((( 43 +NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 44 +))) 45 + 46 +((( 47 +To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection. 48 +))) 49 +))) 50 + 51 + 52 +))) 53 + 39 39 [[image:1657327959271-447.png]] 40 40 41 41 ... ... @@ -56,6 +56,9 @@ 56 56 * Micro SIM card slot for NB-IoT SIM 57 57 * 8500mAh Battery for long term use 58 58 74 + 75 + 76 + 59 59 == 1.3 Specification == 60 60 61 61 ... ... @@ -64,6 +64,8 @@ 64 64 * Supply Voltage: 2.1v ~~ 3.6v 65 65 * Operating Temperature: -40 ~~ 85°C 66 66 85 + 86 + 67 67 (% style="color:#037691" %)**NB-IoT Spec:** 68 68 69 69 * - B1 @H-FDD: 2100MHz ... ... @@ -73,6 +73,8 @@ 73 73 * - B20 @H-FDD: 800MHz 74 74 * - B28 @H-FDD: 700MHz 75 75 96 + 97 + 76 76 (% style="color:#037691" %)**Battery:** 77 77 78 78 * Li/SOCI2 un-chargeable battery ... ... @@ -81,14 +81,19 @@ 81 81 * Max continuously current: 130mA 82 82 * Max boost current: 2A, 1 second 83 83 106 + 107 + 84 84 (% style="color:#037691" %)**Power Consumption** 85 85 86 86 * STOP Mode: 10uA @ 3.3v 87 -* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]111 +* Max transmit power: 350mA@3.3v 88 88 89 89 114 + 115 + 90 90 == 1.4 Applications == 91 91 118 + 92 92 * Smart Buildings & Home Automation 93 93 * Logistics and Supply Chain Management 94 94 * Smart Metering ... ... @@ -101,6 +101,7 @@ 101 101 102 102 103 103 131 + 104 104 == 1.5 Pin Definitions == 105 105 106 106 ... ... @@ -110,8 +110,10 @@ 110 110 111 111 = 2. Use NDDS75 to communicate with IoT Server = 112 112 141 + 113 113 == 2.1 How it works == 114 114 144 + 115 115 ((( 116 116 The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75. 117 117 ))) ... ... @@ -137,16 +137,19 @@ 137 137 138 138 === 2.2.1 Test Requirement === 139 139 170 + 140 140 ((( 141 141 To use NDDS75 in your city, make sure meet below requirements: 142 142 ))) 143 143 144 144 * Your local operator has already distributed a NB-IoT Network there. 145 -* The local NB-IoT network used the band that NS E01supports.176 +* The local NB-IoT network used the band that NDDS75 supports. 146 146 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 147 147 179 + 180 + 148 148 ((( 149 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server 182 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server. 150 150 ))) 151 151 152 152 ... ... @@ -156,6 +156,7 @@ 156 156 157 157 === 2.2.2 Insert SIM card === 158 158 192 + 159 159 ((( 160 160 Insert the NB-IoT Card get from your provider. 161 161 ))) ... ... @@ -171,6 +171,7 @@ 171 171 172 172 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 173 173 208 + 174 174 ((( 175 175 ((( 176 176 User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below. ... ... @@ -179,6 +179,7 @@ 179 179 180 180 [[image:image-20220709092052-2.png]] 181 181 217 + 182 182 **Connection:** 183 183 184 184 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -202,8 +202,9 @@ 202 202 203 203 [[image:1657329814315-101.png]] 204 204 241 + 205 205 ((( 206 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]243 +(% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)**[[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]** 207 207 ))) 208 208 209 209 ... ... @@ -210,21 +210,38 @@ 210 210 211 211 === 2.2.4 Use CoAP protocol to uplink data === 212 212 213 -(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 214 214 251 +(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]** 215 215 253 + 254 +((( 216 216 **Use below commands:** 256 +))) 217 217 218 -* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 219 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 220 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 258 +* ((( 259 +(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 260 +))) 261 +* ((( 262 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 263 +))) 264 +* ((( 265 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 221 221 267 + 268 + 269 +))) 270 + 271 +((( 222 222 For parameter description, please refer to AT command set 273 +))) 223 223 224 224 [[image:1657330452568-615.png]] 225 225 226 226 278 + 279 +((( 227 227 After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server. 281 +))) 228 228 229 229 [[image:1657330472797-498.png]] 230 230 ... ... @@ -233,10 +233,12 @@ 233 233 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 234 234 235 235 236 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 290 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 237 237 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 238 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 292 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 239 239 294 + 295 + 240 240 [[image:1657330501006-241.png]] 241 241 242 242 ... ... @@ -247,14 +247,16 @@ 247 247 === 2.2.6 Use MQTT protocol to uplink data === 248 248 249 249 250 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 251 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 252 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 253 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 254 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 306 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 307 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 308 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 309 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 310 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 255 255 * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 256 256 * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 257 257 314 + 315 + 258 258 [[image:1657249978444-674.png]] 259 259 260 260 ... ... @@ -273,6 +273,8 @@ 273 273 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 274 274 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 275 275 334 + 335 + 276 276 [[image:image-20220709093918-1.png]] 277 277 278 278 ... ... @@ -282,16 +282,15 @@ 282 282 283 283 === 2.2.8 Change Update Interval === 284 284 345 + 285 285 User can use below command to change the (% style="color:green" %)**uplink interval**. 286 286 287 287 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 288 288 289 -((( 290 -(% style="color:red" %)**NOTE:** 291 -))) 292 292 351 + 293 293 ((( 294 -(% style="color:red" %) 1.By default, the device will send an uplink message every 1 hour.353 +(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.** 295 295 ))) 296 296 297 297 ... ... @@ -298,14 +298,15 @@ 298 298 299 299 == 2.3 Uplink Payload == 300 300 360 + 301 301 In this mode, uplink payload includes in total 14 bytes 302 302 303 303 304 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width: 510px" %)305 -|=(% style="width: 80px;" %)(((364 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 365 +|=(% style="width: 60px;" %)((( 306 306 **Size(bytes)** 307 -)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width:110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width:70px;" %)**1**308 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4. 8A0DigitalInterrupt"]]367 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 368 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]] 309 309 310 310 ((( 311 311 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. ... ... @@ -314,6 +314,7 @@ 314 314 315 315 [[image:1657331036973-987.png]] 316 316 377 + 317 317 ((( 318 318 The payload is ASCII string, representative same HEX: 319 319 ))) ... ... @@ -351,6 +351,7 @@ 351 351 352 352 === 2.4.1 Device ID === 353 353 415 + 354 354 ((( 355 355 By default, the Device ID equal to the last 6 bytes of IMEI. 356 356 ))) ... ... @@ -357,6 +357,8 @@ 357 357 358 358 ((( 359 359 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 422 + 423 + 360 360 ))) 361 361 362 362 ((( ... ... @@ -375,6 +375,7 @@ 375 375 376 376 === 2.4.2 Version Info === 377 377 442 + 378 378 ((( 379 379 Specify the software version: 0x64=100, means firmware version 1.00. 380 380 ))) ... ... @@ -387,9 +387,6 @@ 387 387 388 388 === 2.4.3 Battery Info === 389 389 390 -((( 391 -Check the battery voltage for LSE01. 392 -))) 393 393 394 394 ((( 395 395 Ex1: 0x0B45 = 2885mV ... ... @@ -403,6 +403,7 @@ 403 403 404 404 === 2.4.4 Signal Strength === 405 405 468 + 406 406 ((( 407 407 NB-IoT Network signal Strength. 408 408 ))) ... ... @@ -435,9 +435,12 @@ 435 435 436 436 === 2.4.5 Distance === 437 437 501 + 438 438 Get the distance. Flat object range 280mm - 7500mm. 439 439 504 +((( 440 440 For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 506 +))) 441 441 442 442 ((( 443 443 ((( ... ... @@ -455,6 +455,7 @@ 455 455 456 456 === 2.4.6 Digital Interrupt === 457 457 524 + 458 458 ((( 459 459 Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server. 460 460 ))) ... ... @@ -489,6 +489,7 @@ 489 489 490 490 === 2.4.7 +5V Output === 491 491 559 + 492 492 ((( 493 493 NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 494 494 ))) ... ... @@ -496,10 +496,14 @@ 496 496 497 497 ((( 498 498 The 5V output time can be controlled by AT Command. 567 + 568 + 499 499 ))) 500 500 501 501 ((( 502 502 (% style="color:blue" %)**AT+5VT=1000** 573 + 574 + 503 503 ))) 504 504 505 505 ((( ... ... @@ -510,6 +510,7 @@ 510 510 511 511 == 2.5 Downlink Payload == 512 512 585 + 513 513 By default, NDDS75 prints the downlink payload to console port. 514 514 515 515 [[image:image-20220709100028-1.png]] ... ... @@ -580,19 +580,23 @@ 580 580 == 2.7 Firmware Change Log == 581 581 582 582 583 -Download URL & Firmware Change log 656 +((( 657 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]] 658 +))) 584 584 585 585 ((( 586 - [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]]661 + 587 587 ))) 588 588 664 +((( 665 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 666 +))) 589 589 590 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 591 591 592 592 593 - 594 594 == 2.8 Battery Analysis == 595 595 672 + 596 596 === 2.8.1 Battery Type === 597 597 598 598 ... ... @@ -620,6 +620,7 @@ 620 620 621 621 === 2.8.2 Power consumption Analyze === 622 622 700 + 623 623 ((( 624 624 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. 625 625 ))) ... ... @@ -652,12 +652,13 @@ 652 652 And the Life expectation in difference case will be shown on the right. 653 653 ))) 654 654 655 -[[image:image-2022070 8141352-7.jpeg]]733 +[[image:image-20220709110451-3.png]] 656 656 657 657 658 658 659 659 === 2.8.3 Battery Note === 660 660 739 + 661 661 ((( 662 662 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. 663 663 ))) ... ... @@ -666,6 +666,7 @@ 666 666 667 667 === 2.8.4 Replace the battery === 668 668 748 + 669 669 ((( 670 670 The default battery pack of NDDS75 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). 671 671 ))) ... ... @@ -674,6 +674,7 @@ 674 674 675 675 = 3. Access NB-IoT Module = 676 676 757 + 677 677 ((( 678 678 Users can directly access the AT command set of the NB-IoT module. 679 679 ))) ... ... @@ -680,6 +680,8 @@ 680 680 681 681 ((( 682 682 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/]] 764 + 765 + 683 683 ))) 684 684 685 685 [[image:1657333200519-600.png]] ... ... @@ -688,11 +688,13 @@ 688 688 689 689 = 4. Using the AT Commands = 690 690 774 + 691 691 == 4.1 Access AT Commands == 692 692 693 -See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 694 694 778 +See this link for detail: [[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]] 695 695 780 + 696 696 AT+<CMD>? : Help on <CMD> 697 697 698 698 AT+<CMD> : Run <CMD> ... ... @@ -766,6 +766,7 @@ 766 766 767 767 = 5. FAQ = 768 768 854 + 769 769 == 5.1 How to Upgrade Firmware == 770 770 771 771 ... ... @@ -778,7 +778,7 @@ 778 778 ))) 779 779 780 780 ((( 781 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 867 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.** 782 782 ))) 783 783 784 784 ... ... @@ -785,6 +785,7 @@ 785 785 786 786 = 6. Trouble Shooting = 787 787 874 + 788 788 == 6.1 Connection problem when uploading firmware == 789 789 790 790 ... ... @@ -800,6 +800,7 @@ 800 800 801 801 == 6.2 AT Command input doesn't work == 802 802 890 + 803 803 ((( 804 804 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. 805 805 ... ... @@ -825,7 +825,7 @@ 825 825 826 826 (% style="color:#037691" %)**Package Includes**: 827 827 828 -* NS E01NB-IoT Distance Detect Sensor Node x 1916 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1 829 829 * External antenna x 1 830 830 ))) 831 831 ... ... @@ -832,9 +832,9 @@ 832 832 ((( 833 833 834 834 923 + 835 835 (% style="color:#037691" %)**Dimension and weight**: 836 836 837 - 838 838 * Device Size: 13.0 x 5 x 4.5 cm 839 839 * Device Weight: 150g 840 840 * Package Size / pcs : 15 x 12x 5.5 cm ... ... @@ -850,5 +850,8 @@ 850 850 851 851 = 9. Support = 852 852 941 + 853 853 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 854 854 * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]] 944 + 945 +
- image-20220709110451-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +611.5 KB - Content