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,7 +69,6 @@ 69 69 * Micro SIM card slot for NB-IoT SIM 70 70 * 8500mAh Battery for long term use 71 71 72 - 73 73 == 1.3 Specification == 74 74 75 75 ... ... @@ -100,9 +100,9 @@ 100 100 * STOP Mode: 10uA @ 3.3v 101 101 * Max transmit power: 350mA@3.3v 102 102 103 - 104 104 == 1.4 Applications == 105 105 106 + 106 106 * Smart Buildings & Home Automation 107 107 * Logistics and Supply Chain Management 108 108 * Smart Metering ... ... @@ -114,6 +114,8 @@ 114 114 115 115 116 116 118 + 119 + 117 117 == 1.5 Pin Definitions == 118 118 119 119 ... ... @@ -123,8 +123,10 @@ 123 123 124 124 = 2. Use NDDS75 to communicate with IoT Server = 125 125 129 + 126 126 == 2.1 How it works == 127 127 132 + 128 128 ((( 129 129 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. 130 130 ))) ... ... @@ -150,16 +150,17 @@ 150 150 151 151 === 2.2.1 Test Requirement === 152 152 158 + 153 153 ((( 154 154 To use NDDS75 in your city, make sure meet below requirements: 155 155 ))) 156 156 157 157 * Your local operator has already distributed a NB-IoT Network there. 158 -* The local NB-IoT network used the band that NS E01supports.164 +* The local NB-IoT network used the band that NDDS75 supports. 159 159 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 160 160 161 161 ((( 162 -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. 163 163 ))) 164 164 165 165 ... ... @@ -169,6 +169,7 @@ 169 169 170 170 === 2.2.2 Insert SIM card === 171 171 178 + 172 172 ((( 173 173 Insert the NB-IoT Card get from your provider. 174 174 ))) ... ... @@ -184,6 +184,7 @@ 184 184 185 185 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 186 186 194 + 187 187 ((( 188 188 ((( 189 189 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. ... ... @@ -192,6 +192,7 @@ 192 192 193 193 [[image:image-20220709092052-2.png]] 194 194 203 + 195 195 **Connection:** 196 196 197 197 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -215,8 +215,9 @@ 215 215 216 216 [[image:1657329814315-101.png]] 217 217 227 + 218 218 ((( 219 -(% 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]]** 220 220 ))) 221 221 222 222 ... ... @@ -223,9 +223,10 @@ 223 223 224 224 === 2.2.4 Use CoAP protocol to uplink data === 225 225 226 -(% 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/]] 227 227 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/]]** 228 228 239 + 229 229 ((( 230 230 **Use below commands:** 231 231 ))) ... ... @@ -238,6 +238,9 @@ 238 238 ))) 239 239 * ((( 240 240 (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 252 + 253 + 254 + 241 241 ))) 242 242 243 243 ((( ... ... @@ -247,6 +247,7 @@ 247 247 [[image:1657330452568-615.png]] 248 248 249 249 264 + 250 250 ((( 251 251 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. 252 252 ))) ... ... @@ -307,25 +307,29 @@ 307 307 308 308 === 2.2.8 Change Update Interval === 309 309 325 + 310 310 User can use below command to change the (% style="color:green" %)**uplink interval**. 311 311 312 312 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 313 313 314 314 ((( 315 -(% style="color:red" %)**NOTE:** 316 -))) 331 +(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.** 317 317 318 -((( 319 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 333 + 320 320 ))) 321 321 336 +**NOTE:When the firmware version is v1.3.2 and later firmware:** 322 322 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).** 323 323 340 + 324 324 == 2.3 Uplink Payload == 325 325 326 -In this mode, uplink payload includes in total 14 bytes 327 327 344 +=== 2.3.1 Before Firmware 1.3.2 === 328 328 346 +In this mode, uplink payload includes in total 14 bytes 347 + 329 329 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 330 330 |=(% style="width: 60px;" %)((( 331 331 **Size(bytes)** ... ... @@ -339,6 +339,7 @@ 339 339 340 340 [[image:1657331036973-987.png]] 341 341 361 + 342 342 ((( 343 343 The payload is ASCII string, representative same HEX: 344 344 ))) ... ... @@ -366,16 +366,43 @@ 366 366 * ((( 367 367 Interrupt: 0x00 = 0 368 368 369 - 370 - 371 371 372 372 ))) 373 373 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 + 374 374 == 2.4 Payload Explanation and Sensor Interface == 375 375 376 376 377 377 === 2.4.1 Device ID === 378 378 425 + 379 379 ((( 380 380 By default, the Device ID equal to the last 6 bytes of IMEI. 381 381 ))) ... ... @@ -382,6 +382,8 @@ 382 382 383 383 ((( 384 384 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 432 + 433 + 385 385 ))) 386 386 387 387 ((( ... ... @@ -397,9 +397,19 @@ 397 397 ))) 398 398 399 399 449 +**NOTE:When the firmware version is v1.3.2 and later firmware:** 400 400 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 + 401 401 === 2.4.2 Version Info === 402 402 461 + 403 403 ((( 404 404 Specify the software version: 0x64=100, means firmware version 1.00. 405 405 ))) ... ... @@ -412,6 +412,7 @@ 412 412 413 413 === 2.4.3 Battery Info === 414 414 474 + 415 415 ((( 416 416 Ex1: 0x0B45 = 2885mV 417 417 ))) ... ... @@ -424,6 +424,7 @@ 424 424 425 425 === 2.4.4 Signal Strength === 426 426 487 + 427 427 ((( 428 428 NB-IoT Network signal Strength. 429 429 ))) ... ... @@ -456,6 +456,7 @@ 456 456 457 457 === 2.4.5 Distance === 458 458 520 + 459 459 Get the distance. Flat object range 280mm - 7500mm. 460 460 461 461 ((( ... ... @@ -478,6 +478,7 @@ 478 478 479 479 === 2.4.6 Digital Interrupt === 480 480 543 + 481 481 ((( 482 482 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. 483 483 ))) ... ... @@ -512,6 +512,7 @@ 512 512 513 513 === 2.4.7 +5V Output === 514 514 578 + 515 515 ((( 516 516 NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 517 517 ))) ... ... @@ -519,10 +519,14 @@ 519 519 520 520 ((( 521 521 The 5V output time can be controlled by AT Command. 586 + 587 + 522 522 ))) 523 523 524 524 ((( 525 525 (% style="color:blue" %)**AT+5VT=1000** 592 + 593 + 526 526 ))) 527 527 528 528 ((( ... ... @@ -533,6 +533,7 @@ 533 533 534 534 == 2.5 Downlink Payload == 535 535 604 + 536 536 By default, NDDS75 prints the downlink payload to console port. 537 537 538 538 [[image:image-20220709100028-1.png]] ... ... @@ -582,10 +582,44 @@ 582 582 ))) 583 583 584 584 654 +== 2.6 Distance alarm function(Since firmware v1.3.2) == 585 585 586 - ==2.6LED Indicator ==656 +➢ AT Command: 587 587 658 +AT+ LDDSALARM=min,max 588 588 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 + 589 589 The NDDS75 has an internal LED which is to show the status of different state. 590 590 591 591 ... ... @@ -600,29 +600,29 @@ 600 600 601 601 602 602 603 -== 2. 7Firmware Change Log ==706 +== 2.10 Firmware Change Log == 604 604 605 605 606 606 ((( 607 -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]] 608 608 ))) 609 609 610 610 ((( 611 - [[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 + 612 612 ))) 613 613 614 - 615 615 ((( 616 -Upgrade Instruction: [[Upgrade _Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]718 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 617 617 ))) 618 618 619 619 620 620 621 -== 2. 8Battery Analysis ==723 +== 2.11 Battery Analysis == 622 622 623 -=== 2.8.1 Battery Type === 624 624 726 +=== 2.11.1 Battery Type === 625 625 728 + 626 626 ((( 627 627 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. 628 628 ))) ... ... @@ -645,8 +645,9 @@ 645 645 646 646 647 647 648 -=== 2. 8.2 Power consumption Analyze ===751 +=== 2.11.2 Power consumption Analyze === 649 649 753 + 650 650 ((( 651 651 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. 652 652 ))) ... ... @@ -683,8 +683,9 @@ 683 683 684 684 685 685 686 -=== 2. 8.3 Battery Note ===790 +=== 2.11.3 Battery Note === 687 687 792 + 688 688 ((( 689 689 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. 690 690 ))) ... ... @@ -691,8 +691,9 @@ 691 691 692 692 693 693 694 -=== 2. 8.4 Replace the battery ===799 +=== 2.11.4 Replace the battery === 695 695 801 + 696 696 ((( 697 697 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). 698 698 ))) ... ... @@ -701,6 +701,7 @@ 701 701 702 702 = 3. Access NB-IoT Module = 703 703 810 + 704 704 ((( 705 705 Users can directly access the AT command set of the NB-IoT module. 706 706 ))) ... ... @@ -707,6 +707,8 @@ 707 707 708 708 ((( 709 709 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 + 710 710 ))) 711 711 712 712 [[image:1657333200519-600.png]] ... ... @@ -715,11 +715,13 @@ 715 715 716 716 = 4. Using the AT Commands = 717 717 827 + 718 718 == 4.1 Access AT Commands == 719 719 720 -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/]] 721 721 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]] 722 722 833 + 723 723 AT+<CMD>? : Help on <CMD> 724 724 725 725 AT+<CMD> : Run <CMD> ... ... @@ -759,7 +759,23 @@ 759 759 760 760 AT+SERVADDR : Server Address 761 761 873 +AT+TR : Get or Set record time" 762 762 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 + 763 763 (% style="color:#037691" %)**COAP Management** 764 764 765 765 AT+URI : Resource parameters ... ... @@ -793,6 +793,7 @@ 793 793 794 794 = 5. FAQ = 795 795 923 + 796 796 == 5.1 How to Upgrade Firmware == 797 797 798 798 ... ... @@ -805,7 +805,7 @@ 805 805 ))) 806 806 807 807 ((( 808 -(% 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.** 809 809 ))) 810 810 811 811 ... ... @@ -812,6 +812,7 @@ 812 812 813 813 = 6. Trouble Shooting = 814 814 943 + 815 815 == 6.1 Connection problem when uploading firmware == 816 816 817 817 ... ... @@ -827,6 +827,7 @@ 827 827 828 828 == 6.2 AT Command input doesn't work == 829 829 959 + 830 830 ((( 831 831 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. 832 832 ... ... @@ -859,6 +859,7 @@ 859 859 ((( 860 860 861 861 992 + 862 862 (% style="color:#037691" %)**Dimension and weight**: 863 863 864 864 * Device Size: 13.0 x 5 x 4.5 cm ... ... @@ -876,5 +876,6 @@ 876 876 877 877 = 9. Support = 878 878 1010 + 879 879 * 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. 880 880 * 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