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, 2 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Edwin - 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 ((( ... ... @@ -56,6 +56,7 @@ 56 56 57 57 == 1.2 Features == 58 58 60 + 59 59 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 60 60 * Ultra low power consumption 61 61 * Distance Detection by Ultrasonic technology ... ... @@ -69,10 +69,9 @@ 69 69 * Micro SIM card slot for NB-IoT SIM 70 70 * 8500mAh Battery for long term use 71 71 72 - 73 - 74 74 == 1.3 Specification == 75 75 76 + 76 76 (% style="color:#037691" %)**Common DC Characteristics:** 77 77 78 78 * Supply Voltage: 2.1v ~~ 3.6v ... ... @@ -100,10 +100,9 @@ 100 100 * STOP Mode: 10uA @ 3.3v 101 101 * Max transmit power: 350mA@3.3v 102 102 103 - 104 - 105 105 == 1.4 Applications == 106 106 106 + 107 107 * Smart Buildings & Home Automation 108 108 * Logistics and Supply Chain Management 109 109 * Smart Metering ... ... @@ -115,6 +115,8 @@ 115 115 116 116 117 117 118 + 119 + 118 118 == 1.5 Pin Definitions == 119 119 120 120 ... ... @@ -124,8 +124,10 @@ 124 124 125 125 = 2. Use NDDS75 to communicate with IoT Server = 126 126 129 + 127 127 == 2.1 How it works == 128 128 132 + 129 129 ((( 130 130 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. 131 131 ))) ... ... @@ -151,6 +151,7 @@ 151 151 152 152 === 2.2.1 Test Requirement === 153 153 158 + 154 154 ((( 155 155 To use NDDS75 in your city, make sure meet below requirements: 156 156 ))) ... ... @@ -160,7 +160,7 @@ 160 160 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 161 161 162 162 ((( 163 -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 168 +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. 164 164 ))) 165 165 166 166 ... ... @@ -170,6 +170,7 @@ 170 170 171 171 === 2.2.2 Insert SIM card === 172 172 178 + 173 173 ((( 174 174 Insert the NB-IoT Card get from your provider. 175 175 ))) ... ... @@ -185,6 +185,7 @@ 185 185 186 186 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 187 187 194 + 188 188 ((( 189 189 ((( 190 190 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. ... ... @@ -193,6 +193,7 @@ 193 193 194 194 [[image:image-20220709092052-2.png]] 195 195 203 + 196 196 **Connection:** 197 197 198 198 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -216,8 +216,9 @@ 216 216 217 217 [[image:1657329814315-101.png]] 218 218 227 + 219 219 ((( 220 -(% 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/]]229 +(% 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]]** 221 221 ))) 222 222 223 223 ... ... @@ -224,9 +224,10 @@ 224 224 225 225 === 2.2.4 Use CoAP protocol to uplink data === 226 226 227 -(% 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/]] 228 228 237 +(% 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/]]** 229 229 239 + 230 230 ((( 231 231 **Use below commands:** 232 232 ))) ... ... @@ -239,6 +239,9 @@ 239 239 ))) 240 240 * ((( 241 241 (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 252 + 253 + 254 + 242 242 ))) 243 243 244 244 ((( ... ... @@ -248,6 +248,7 @@ 248 248 [[image:1657330452568-615.png]] 249 249 250 250 264 + 251 251 ((( 252 252 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. 253 253 ))) ... ... @@ -308,25 +308,29 @@ 308 308 309 309 === 2.2.8 Change Update Interval === 310 310 325 + 311 311 User can use below command to change the (% style="color:green" %)**uplink interval**. 312 312 313 313 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 314 314 315 315 ((( 316 -(% style="color:red" %)**NOTE:** 317 -))) 331 +(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.** 318 318 319 -((( 320 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 333 + 321 321 ))) 322 322 336 +**NOTE:When the firmware version is v1.3.2 and later firmware:** 323 323 338 +**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).** 324 324 340 + 325 325 == 2.3 Uplink Payload == 326 326 327 -In this mode, uplink payload includes in total 14 bytes 328 328 344 +=== 2.3.1 Before Firmware 1.3.2 === 329 329 346 +In this mode, uplink payload includes in total 14 bytes 347 + 330 330 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 331 331 |=(% style="width: 60px;" %)((( 332 332 **Size(bytes)** ... ... @@ -340,6 +340,7 @@ 340 340 341 341 [[image:1657331036973-987.png]] 342 342 361 + 343 343 ((( 344 344 The payload is ASCII string, representative same HEX: 345 345 ))) ... ... @@ -367,16 +367,43 @@ 367 367 * ((( 368 368 Interrupt: 0x00 = 0 369 369 370 - 371 - 372 372 373 373 ))) 374 374 392 +=== **2.3.2 Since firmware v1.3.2** === 393 + 394 +In this mode, uplink payload includes 69 bytes in total by default. 395 + 396 +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. 397 + 398 +|**Size(bytes)**|**8**|2|2|1|1|1|2|4|2|4 399 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Distance|Timestamp|Distance|Timestamp....... 400 + 401 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 402 + 403 +[[image:image-20220908175246-1.png]] 404 + 405 +The payload is ASCII string, representative same HEX: 406 + 407 +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: 408 + 409 +* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317 410 +* (% style="color:red" %)Version: 0x0084=132=1.3.2 411 +* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V 412 +* (% style="color:blue" %)Singal: 0x1e = 30 413 +* (% style="color:red" %)Mod: 0x01 = 1 414 +* Interrupt: 0x00= 0 415 +* Distance: 0x0039= 57 = 57 416 +* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 417 +* Distance,Time stamp : 00396319baf0 418 +* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,....... 419 + 375 375 == 2.4 Payload Explanation and Sensor Interface == 376 376 377 377 378 378 === 2.4.1 Device ID === 379 379 425 + 380 380 ((( 381 381 By default, the Device ID equal to the last 6 bytes of IMEI. 382 382 ))) ... ... @@ -383,6 +383,8 @@ 383 383 384 384 ((( 385 385 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 432 + 433 + 386 386 ))) 387 387 388 388 ((( ... ... @@ -398,9 +398,19 @@ 398 398 ))) 399 399 400 400 449 +**NOTE:When the firmware version is v1.3.2 and later firmware:** 401 401 451 +By default, the Device ID equal to the last 15 bits of IMEI. 452 + 453 +User can use **AT+DEUI** to set Device ID 454 + 455 +**Example:** 456 + 457 +AT+DEUI=868411056754138 458 + 402 402 === 2.4.2 Version Info === 403 403 461 + 404 404 ((( 405 405 Specify the software version: 0x64=100, means firmware version 1.00. 406 406 ))) ... ... @@ -413,6 +413,7 @@ 413 413 414 414 === 2.4.3 Battery Info === 415 415 474 + 416 416 ((( 417 417 Ex1: 0x0B45 = 2885mV 418 418 ))) ... ... @@ -425,6 +425,7 @@ 425 425 426 426 === 2.4.4 Signal Strength === 427 427 487 + 428 428 ((( 429 429 NB-IoT Network signal Strength. 430 430 ))) ... ... @@ -457,6 +457,7 @@ 457 457 458 458 === 2.4.5 Distance === 459 459 520 + 460 460 Get the distance. Flat object range 280mm - 7500mm. 461 461 462 462 ((( ... ... @@ -479,6 +479,7 @@ 479 479 480 480 === 2.4.6 Digital Interrupt === 481 481 543 + 482 482 ((( 483 483 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. 484 484 ))) ... ... @@ -513,6 +513,7 @@ 513 513 514 514 === 2.4.7 +5V Output === 515 515 578 + 516 516 ((( 517 517 NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 518 518 ))) ... ... @@ -520,10 +520,14 @@ 520 520 521 521 ((( 522 522 The 5V output time can be controlled by AT Command. 586 + 587 + 523 523 ))) 524 524 525 525 ((( 526 526 (% style="color:blue" %)**AT+5VT=1000** 592 + 593 + 527 527 ))) 528 528 529 529 ((( ... ... @@ -534,6 +534,7 @@ 534 534 535 535 == 2.5 Downlink Payload == 536 536 604 + 537 537 By default, NDDS75 prints the downlink payload to console port. 538 538 539 539 [[image:image-20220709100028-1.png]] ... ... @@ -583,10 +583,44 @@ 583 583 ))) 584 584 585 585 654 +== 2.6 Distance alarm function(Since firmware v1.3.2) == 586 586 587 - ==2.6LED Indicator ==656 +➢ AT Command: 588 588 658 +AT+ LDDSALARM=min,max 589 589 660 +² When min=0, and max≠0, Alarm higher than max 661 + 662 +² When min≠0, and max=0, Alarm lower than min 663 + 664 +² When min≠0 and max≠0, Alarm higher than max or lower than min 665 + 666 +Example: 667 + 668 +AT+ LDDSALARM=260,2000 ~/~/ Alarm when distance lower than 260. 669 + 670 + 671 +== 2.7 Set the number of data to be uploaded and the recording time == 672 + 673 +➢ AT Command: 674 + 675 +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) 676 + 677 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 678 + 679 +== 2.8 Read or Clear cached data == 680 + 681 +➢ AT Command: 682 + 683 +AT+CDP ~/~/ Read cached data 684 + 685 +[[image:image-20220908175333-2.png]] 686 + 687 +AT+CDP=0 ~/~/ Clear cached data 688 + 689 +== 2.9 LED Indicator == 690 + 691 + 590 590 The NDDS75 has an internal LED which is to show the status of different state. 591 591 592 592 ... ... @@ -601,29 +601,29 @@ 601 601 602 602 603 603 604 -== 2. 7Firmware Change Log ==706 +== 2.10 Firmware Change Log == 605 605 606 606 607 607 ((( 608 -Download URL & Firmware Change log 710 +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]] 609 609 ))) 610 610 611 611 ((( 612 - [[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/]]714 + 613 613 ))) 614 614 615 - 616 616 ((( 617 -Upgrade Instruction: [[Upgrade _Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]718 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 618 618 ))) 619 619 620 620 621 621 622 -== 2. 8Battery Analysis ==723 +== 2.11 Battery Analysis == 623 623 624 -=== 2.8.1 Battery Type === 625 625 726 +=== 2.11.1 Battery Type === 626 626 728 + 627 627 ((( 628 628 The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-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. 629 629 ))) ... ... @@ -646,8 +646,9 @@ 646 646 647 647 648 648 649 -=== 2. 8.2 Power consumption Analyze ===751 +=== 2.11.2 Power consumption Analyze === 650 650 753 + 651 651 ((( 652 652 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. 653 653 ))) ... ... @@ -684,8 +684,9 @@ 684 684 685 685 686 686 687 -=== 2. 8.3 Battery Note ===790 +=== 2.11.3 Battery Note === 688 688 792 + 689 689 ((( 690 690 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. 691 691 ))) ... ... @@ -692,8 +692,9 @@ 692 692 693 693 694 694 695 -=== 2. 8.4 Replace the battery ===799 +=== 2.11.4 Replace the battery === 696 696 801 + 697 697 ((( 698 698 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). 699 699 ))) ... ... @@ -702,6 +702,7 @@ 702 702 703 703 = 3. Access NB-IoT Module = 704 704 810 + 705 705 ((( 706 706 Users can directly access the AT command set of the NB-IoT module. 707 707 ))) ... ... @@ -708,6 +708,8 @@ 708 708 709 709 ((( 710 710 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/]] 817 + 818 + 711 711 ))) 712 712 713 713 [[image:1657333200519-600.png]] ... ... @@ -716,11 +716,13 @@ 716 716 717 717 = 4. Using the AT Commands = 718 718 827 + 719 719 == 4.1 Access AT Commands == 720 720 721 -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/]] 722 722 831 +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]] 723 723 833 + 724 724 AT+<CMD>? : Help on <CMD> 725 725 726 726 AT+<CMD> : Run <CMD> ... ... @@ -760,7 +760,23 @@ 760 760 761 761 AT+SERVADDR : Server Address 762 762 873 +AT+TR : Get or Set record time" 763 763 875 +AT+APN : Get or set the APN 876 + 877 +AT+FBAND : Get or Set whether to automatically modify the frequency band 878 + 879 +AT+DNSCFG : Get or Set DNS Server 880 + 881 +AT+GETSENSORVALUE : Returns the current sensor measurement 882 + 883 +AT+NOUD : Get or Set the number of data to be uploaded 884 + 885 +AT+CDP : Read or Clear cached data 886 + 887 +AT+LDDSALARM : Get or Set alarm of distance 888 + 889 + 764 764 (% style="color:#037691" %)**COAP Management** 765 765 766 766 AT+URI : Resource parameters ... ... @@ -794,6 +794,7 @@ 794 794 795 795 = 5. FAQ = 796 796 923 + 797 797 == 5.1 How to Upgrade Firmware == 798 798 799 799 ... ... @@ -806,7 +806,7 @@ 806 806 ))) 807 807 808 808 ((( 809 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 936 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.** 810 810 ))) 811 811 812 812 ... ... @@ -813,6 +813,7 @@ 813 813 814 814 = 6. Trouble Shooting = 815 815 943 + 816 816 == 6.1 Connection problem when uploading firmware == 817 817 818 818 ... ... @@ -828,6 +828,7 @@ 828 828 829 829 == 6.2 AT Command input doesn't work == 830 830 959 + 831 831 ((( 832 832 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. 833 833 ... ... @@ -860,6 +860,7 @@ 860 860 ((( 861 861 862 862 992 + 863 863 (% style="color:#037691" %)**Dimension and weight**: 864 864 865 865 * Device Size: 13.0 x 5 x 4.5 cm ... ... @@ -877,5 +877,6 @@ 877 877 878 878 = 9. Support = 879 879 1010 + 880 880 * 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. 881 881 * 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,0 +1,1 @@ 1 +XWiki.David - Size
-
... ... @@ -1,0 +1,1 @@ 1 +55.7 KB - Content
- image-20220908175333-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.David - Size
-
... ... @@ -1,0 +1,1 @@ 1 +31.1 KB - Content