Changes for page NDDS75 -- NB-IoT Distance Detect Sensor User Manual
Last modified by Bei Jinggeng on 2024/05/31 09:53
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. David1 +XWiki.Xiaoling - Content
-
... ... @@ -16,7 +16,6 @@ 16 16 17 17 = 1. Introduction = 18 18 19 - 20 20 == 1.1 What is NDDS75 Distance Detection Sensor == 21 21 22 22 ((( ... ... @@ -23,34 +23,20 @@ 23 23 24 24 25 25 ((( 26 -((( 27 27 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. 28 28 ))) 29 29 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. 33 + 32 32 ))) 33 33 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 -))) 36 +[[image:1654503236291-817.png]] 37 37 38 -((( 39 -NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 40 -))) 41 41 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 - 54 54 [[image:1657327959271-447.png]] 55 55 56 56 ... ... @@ -72,6 +72,7 @@ 72 72 * 8500mAh Battery for long term use 73 73 74 74 60 + 75 75 == 1.3 Specification == 76 76 77 77 ... ... @@ -100,12 +100,12 @@ 100 100 (% style="color:#037691" %)**Power Consumption** 101 101 102 102 * STOP Mode: 10uA @ 3.3v 103 -* Max transmit power: 350mA@3.3v 89 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 104 104 105 105 92 + 106 106 == 1.4 Applications == 107 107 108 - 109 109 * Smart Buildings & Home Automation 110 110 * Logistics and Supply Chain Management 111 111 * Smart Metering ... ... @@ -117,8 +117,6 @@ 117 117 118 118 119 119 120 - 121 - 122 122 == 1.5 Pin Definitions == 123 123 124 124 ... ... @@ -128,10 +128,8 @@ 128 128 129 129 = 2. Use NDDS75 to communicate with IoT Server = 130 130 131 - 132 132 == 2.1 How it works == 133 133 134 - 135 135 ((( 136 136 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. 137 137 ))) ... ... @@ -157,17 +157,16 @@ 157 157 158 158 === 2.2.1 Test Requirement === 159 159 160 - 161 161 ((( 162 162 To use NDDS75 in your city, make sure meet below requirements: 163 163 ))) 164 164 165 165 * Your local operator has already distributed a NB-IoT Network there. 166 -* The local NB-IoT network used the band that N DDS75supports.147 +* The local NB-IoT network used the band that NSE01 supports. 167 167 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 168 168 169 169 ((( 170 -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 .151 +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 171 171 ))) 172 172 173 173 ... ... @@ -177,7 +177,6 @@ 177 177 178 178 === 2.2.2 Insert SIM card === 179 179 180 - 181 181 ((( 182 182 Insert the NB-IoT Card get from your provider. 183 183 ))) ... ... @@ -193,7 +193,6 @@ 193 193 194 194 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 195 195 196 - 197 197 ((( 198 198 ((( 199 199 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. ... ... @@ -202,7 +202,6 @@ 202 202 203 203 [[image:image-20220709092052-2.png]] 204 204 205 - 206 206 **Connection:** 207 207 208 208 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -226,9 +226,8 @@ 226 226 227 227 [[image:1657329814315-101.png]] 228 228 229 - 230 230 ((( 231 -(% 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]]**208 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]] 232 232 ))) 233 233 234 234 ... ... @@ -235,38 +235,21 @@ 235 235 236 236 === 2.2.4 Use CoAP protocol to uplink data === 237 237 215 +(% 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/]] 238 238 239 -(% 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/]]** 240 240 241 - 242 -((( 243 243 **Use below commands:** 244 -))) 245 245 246 -* ((( 247 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 248 -))) 249 -* ((( 250 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 251 -))) 252 -* ((( 253 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 220 +* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 221 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 222 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 254 254 255 - 256 - 257 -))) 258 - 259 -((( 260 260 For parameter description, please refer to AT command set 261 -))) 262 262 263 263 [[image:1657330452568-615.png]] 264 264 265 265 266 - 267 -((( 268 268 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. 269 -))) 270 270 271 271 [[image:1657330472797-498.png]] 272 272 ... ... @@ -275,9 +275,9 @@ 275 275 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 276 276 277 277 278 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) 238 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 279 279 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 280 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 240 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 281 281 282 282 [[image:1657330501006-241.png]] 283 283 ... ... @@ -289,11 +289,11 @@ 289 289 === 2.2.6 Use MQTT protocol to uplink data === 290 290 291 291 292 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) 293 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) 294 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** 295 -* (% style="color:blue" %)**AT+UNAME=UNAME 296 -* (% style="color:blue" %)**AT+PWD=PWD 252 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 253 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 254 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 255 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 256 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 297 297 * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 298 298 * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 299 299 ... ... @@ -324,32 +324,29 @@ 324 324 325 325 === 2.2.8 Change Update Interval === 326 326 327 - 328 328 User can use below command to change the (% style="color:green" %)**uplink interval**. 329 329 330 330 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 331 331 332 332 ((( 333 -(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.** 292 +(% style="color:red" %)**NOTE:** 293 +))) 334 334 335 - 295 +((( 296 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 336 336 ))) 337 337 338 -**NOTE:When the firmware version is v1.3.2 and later firmware:** 339 339 340 -**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).** 341 341 342 - 343 343 == 2.3 Uplink Payload == 344 344 345 - 346 346 In this mode, uplink payload includes in total 14 bytes 347 347 348 348 349 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width: 440px" %)350 -|=(% style="width: 60px;" %)(((306 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 307 +|=(% style="width: 80px;" %)((( 351 351 **Size(bytes)** 352 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width:80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width:60px;" %)**1**309 +)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1** 353 353 |(% 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"]] 354 354 355 355 ((( ... ... @@ -359,7 +359,6 @@ 359 359 360 360 [[image:1657331036973-987.png]] 361 361 362 - 363 363 ((( 364 364 The payload is ASCII string, representative same HEX: 365 365 ))) ... ... @@ -387,43 +387,16 @@ 387 387 * ((( 388 388 Interrupt: 0x00 = 0 389 389 346 + 347 + 390 390 391 391 ))) 392 392 393 -**NOTE:When the firmware version is v1.3.2 and later firmware:** 394 - 395 -In this mode, uplink payload includes 69 bytes in total by default. 396 - 397 -Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded. 398 - 399 -|**Size(bytes)**|**8**|2|2|1|1|1|2|4|2|4 400 -|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Distance|Timestamp|Distance|Timestamp....... 401 - 402 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 403 - 404 -[[image:image-20220908175246-1.png]] 405 - 406 -The payload is ASCII string, representative same HEX: 407 - 408 -0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%) where: 409 - 410 -* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317 411 -* (% style="color:red" %)Version: 0x0084=132=1.3.2 412 -* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V 413 -* (% style="color:blue" %)Singal: 0x1e = 30 414 -* (% style="color:red" %)Mod: 0x01 = 1 415 -* Interrupt: 0x00= 0 416 -* Distance: 0x0039= 57 = 57 417 -* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 418 -* Distance,Time stamp : 00396319baf0 419 -* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,....... 420 - 421 421 == 2.4 Payload Explanation and Sensor Interface == 422 422 423 423 424 424 === 2.4.1 Device ID === 425 425 426 - 427 427 ((( 428 428 By default, the Device ID equal to the last 6 bytes of IMEI. 429 429 ))) ... ... @@ -430,8 +430,6 @@ 430 430 431 431 ((( 432 432 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 433 - 434 - 435 435 ))) 436 436 437 437 ((( ... ... @@ -447,19 +447,9 @@ 447 447 ))) 448 448 449 449 450 -**NOTE:When the firmware version is v1.3.2 and later firmware:** 451 451 452 -By default, the Device ID equal to the last 15 bits of IMEI. 453 - 454 -User can use **AT+DEUI** to set Device ID 455 - 456 -**Example:** 457 - 458 -AT+DEUI=868411056754138 459 - 460 460 === 2.4.2 Version Info === 461 461 462 - 463 463 ((( 464 464 Specify the software version: 0x64=100, means firmware version 1.00. 465 465 ))) ... ... @@ -472,6 +472,9 @@ 472 472 473 473 === 2.4.3 Battery Info === 474 474 392 +((( 393 +Check the battery voltage for LSE01. 394 +))) 475 475 476 476 ((( 477 477 Ex1: 0x0B45 = 2885mV ... ... @@ -485,7 +485,6 @@ 485 485 486 486 === 2.4.4 Signal Strength === 487 487 488 - 489 489 ((( 490 490 NB-IoT Network signal Strength. 491 491 ))) ... ... @@ -518,12 +518,9 @@ 518 518 519 519 === 2.4.5 Distance === 520 520 521 - 522 522 Get the distance. Flat object range 280mm - 7500mm. 523 523 524 -((( 525 525 For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 526 -))) 527 527 528 528 ((( 529 529 ((( ... ... @@ -541,7 +541,6 @@ 541 541 542 542 === 2.4.6 Digital Interrupt === 543 543 544 - 545 545 ((( 546 546 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. 547 547 ))) ... ... @@ -576,7 +576,6 @@ 576 576 577 577 === 2.4.7 +5V Output === 578 578 579 - 580 580 ((( 581 581 NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 582 582 ))) ... ... @@ -584,14 +584,10 @@ 584 584 585 585 ((( 586 586 The 5V output time can be controlled by AT Command. 587 - 588 - 589 589 ))) 590 590 591 591 ((( 592 592 (% style="color:blue" %)**AT+5VT=1000** 593 - 594 - 595 595 ))) 596 596 597 597 ((( ... ... @@ -602,7 +602,6 @@ 602 602 603 603 == 2.5 Downlink Payload == 604 604 605 - 606 606 By default, NDDS75 prints the downlink payload to console port. 607 607 608 608 [[image:image-20220709100028-1.png]] ... ... @@ -652,44 +652,10 @@ 652 652 ))) 653 653 654 654 655 -== 2.6 Distance alarm function == 656 656 657 - ➢ATCommand:565 +== 2.6 LED Indicator == 658 658 659 -AT+ LDDSALARM=min,max 660 660 661 -² When min=0, and max≠0, Alarm higher than max 662 - 663 -² When min≠0, and max=0, Alarm lower than min 664 - 665 -² When min≠0 and max≠0, Alarm higher than max or lower than min 666 - 667 -Example: 668 - 669 -AT+ LDDSALARM=260,2000 ~/~/ Alarm when distance lower than 260. 670 - 671 - 672 -== 2.7 Set the number of data to be uploaded and the recording time == 673 - 674 -➢ AT Command: 675 - 676 -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) 677 - 678 -AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 679 - 680 -== 2.8 Read or Clear cached data == 681 - 682 -➢ AT Command: 683 - 684 -AT+CDP ~/~/ Read cached data 685 - 686 -[[image:image-20220908175333-2.png]] 687 - 688 -AT+CDP=0 ~/~/ Clear cached data 689 - 690 -== 2.9 LED Indicator == 691 - 692 - 693 693 The NDDS75 has an internal LED which is to show the status of different state. 694 694 695 695 ... ... @@ -704,27 +704,23 @@ 704 704 705 705 706 706 707 -== 2. 10Firmware Change Log ==582 +== 2.7 Firmware Change Log == 708 708 709 709 710 -((( 711 -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]] 712 -))) 585 +Download URL & Firmware Change log 713 713 714 714 ((( 715 - 588 +[[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/]] 716 716 ))) 717 717 718 -((( 719 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 720 -))) 721 721 592 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 722 722 723 723 724 -== 2.11 Battery Analysis == 725 725 596 +== 2.8 Battery Analysis == 726 726 727 -=== 2. 11.1 Battery Type ===598 +=== 2.8.1 Battery Type === 728 728 729 729 730 730 ((( ... ... @@ -749,9 +749,8 @@ 749 749 750 750 751 751 752 -=== 2. 11.2 Power consumption Analyze ===623 +=== 2.8.2 Power consumption Analyze === 753 753 754 - 755 755 ((( 756 756 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. 757 757 ))) ... ... @@ -788,9 +788,8 @@ 788 788 789 789 790 790 791 -=== 2. 11.3 Battery Note ===661 +=== 2.8.3 Battery Note === 792 792 793 - 794 794 ((( 795 795 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. 796 796 ))) ... ... @@ -797,9 +797,8 @@ 797 797 798 798 799 799 800 -=== 2. 11.4 Replace the battery ===669 +=== 2.8.4 Replace the battery === 801 801 802 - 803 803 ((( 804 804 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). 805 805 ))) ... ... @@ -808,7 +808,6 @@ 808 808 809 809 = 3. Access NB-IoT Module = 810 810 811 - 812 812 ((( 813 813 Users can directly access the AT command set of the NB-IoT module. 814 814 ))) ... ... @@ -815,8 +815,6 @@ 815 815 816 816 ((( 817 817 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/]] 818 - 819 - 820 820 ))) 821 821 822 822 [[image:1657333200519-600.png]] ... ... @@ -825,13 +825,11 @@ 825 825 826 826 = 4. Using the AT Commands = 827 827 828 - 829 829 == 4.1 Access AT Commands == 830 830 695 +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/]] 831 831 832 -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]] 833 833 834 - 835 835 AT+<CMD>? : Help on <CMD> 836 836 837 837 AT+<CMD> : Run <CMD> ... ... @@ -871,23 +871,7 @@ 871 871 872 872 AT+SERVADDR : Server Address 873 873 874 -AT+TR : Get or Set record time" 875 875 876 -AT+APN : Get or set the APN 877 - 878 -AT+FBAND : Get or Set whether to automatically modify the frequency band 879 - 880 -AT+DNSCFG : Get or Set DNS Server 881 - 882 -AT+GETSENSORVALUE : Returns the current sensor measurement 883 - 884 -AT+NOUD : Get or Set the number of data to be uploaded 885 - 886 -AT+CDP : Read or Clear cached data 887 - 888 -AT+LDDSALARM : Get or Set alarm of distance 889 - 890 - 891 891 (% style="color:#037691" %)**COAP Management** 892 892 893 893 AT+URI : Resource parameters ... ... @@ -921,7 +921,6 @@ 921 921 922 922 = 5. FAQ = 923 923 924 - 925 925 == 5.1 How to Upgrade Firmware == 926 926 927 927 ... ... @@ -934,7 +934,7 @@ 934 934 ))) 935 935 936 936 ((( 937 -(% style="color:red" %) **Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**783 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 938 938 ))) 939 939 940 940 ... ... @@ -941,7 +941,6 @@ 941 941 942 942 = 6. Trouble Shooting = 943 943 944 - 945 945 == 6.1 Connection problem when uploading firmware == 946 946 947 947 ... ... @@ -957,7 +957,6 @@ 957 957 958 958 == 6.2 AT Command input doesn't work == 959 959 960 - 961 961 ((( 962 962 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. 963 963 ... ... @@ -983,7 +983,7 @@ 983 983 984 984 (% style="color:#037691" %)**Package Includes**: 985 985 986 -* N DDS75NB-IoT Distance Detect Sensor Node x 1830 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 987 987 * External antenna x 1 988 988 ))) 989 989 ... ... @@ -990,9 +990,9 @@ 990 990 ((( 991 991 992 992 993 - 994 994 (% style="color:#037691" %)**Dimension and weight**: 995 995 839 + 996 996 * Device Size: 13.0 x 5 x 4.5 cm 997 997 * Device Weight: 150g 998 998 * Package Size / pcs : 15 x 12x 5.5 cm ... ... @@ -1008,6 +1008,5 @@ 1008 1008 1009 1009 = 9. Support = 1010 1010 1011 - 1012 1012 * 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. 1013 1013 * 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]]
- image-20220908175246-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -55.7 KB - Content
- image-20220908175333-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.1 KB - Content