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. Edwin1 +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 ((( ... ... @@ -57,7 +57,6 @@ 57 57 58 58 == 1.2 Features == 59 59 60 - 61 61 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 62 62 * Ultra low power consumption 63 63 * Distance Detection by Ultrasonic technology ... ... @@ -71,9 +71,10 @@ 71 71 * Micro SIM card slot for NB-IoT SIM 72 72 * 8500mAh Battery for long term use 73 73 74 -== 1.3 Specification == 75 75 76 76 74 +== 1.3 Specification == 75 + 77 77 (% style="color:#037691" %)**Common DC Characteristics:** 78 78 79 79 * Supply Voltage: 2.1v ~~ 3.6v ... ... @@ -101,9 +101,10 @@ 101 101 * STOP Mode: 10uA @ 3.3v 102 102 * Max transmit power: 350mA@3.3v 103 103 104 -== 1.4 Applications == 105 105 106 106 105 +== 1.4 Applications == 106 + 107 107 * Smart Buildings & Home Automation 108 108 * Logistics and Supply Chain Management 109 109 * Smart Metering ... ... @@ -115,8 +115,6 @@ 115 115 116 116 117 117 118 - 119 - 120 120 == 1.5 Pin Definitions == 121 121 122 122 ... ... @@ -126,10 +126,8 @@ 126 126 127 127 = 2. Use NDDS75 to communicate with IoT Server = 128 128 129 - 130 130 == 2.1 How it works == 131 131 132 - 133 133 ((( 134 134 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. 135 135 ))) ... ... @@ -155,7 +155,6 @@ 155 155 156 156 === 2.2.1 Test Requirement === 157 157 158 - 159 159 ((( 160 160 To use NDDS75 in your city, make sure meet below requirements: 161 161 ))) ... ... @@ -165,7 +165,7 @@ 165 165 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 166 166 167 167 ((( 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 +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 169 169 ))) 170 170 171 171 ... ... @@ -175,7 +175,6 @@ 175 175 176 176 === 2.2.2 Insert SIM card === 177 177 178 - 179 179 ((( 180 180 Insert the NB-IoT Card get from your provider. 181 181 ))) ... ... @@ -191,7 +191,6 @@ 191 191 192 192 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 193 193 194 - 195 195 ((( 196 196 ((( 197 197 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. ... ... @@ -200,7 +200,6 @@ 200 200 201 201 [[image:image-20220709092052-2.png]] 202 202 203 - 204 204 **Connection:** 205 205 206 206 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -224,9 +224,8 @@ 224 224 225 225 [[image:1657329814315-101.png]] 226 226 227 - 228 228 ((( 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 +(% 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/]] 230 230 ))) 231 231 232 232 ... ... @@ -233,10 +233,9 @@ 233 233 234 234 === 2.2.4 Use CoAP protocol to uplink data === 235 235 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/]] 236 236 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/]]** 238 238 239 - 240 240 ((( 241 241 **Use below commands:** 242 242 ))) ... ... @@ -249,9 +249,6 @@ 249 249 ))) 250 250 * ((( 251 251 (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 252 - 253 - 254 - 255 255 ))) 256 256 257 257 ((( ... ... @@ -261,7 +261,6 @@ 261 261 [[image:1657330452568-615.png]] 262 262 263 263 264 - 265 265 ((( 266 266 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. 267 267 ))) ... ... @@ -322,29 +322,25 @@ 322 322 323 323 === 2.2.8 Change Update Interval === 324 324 325 - 326 326 User can use below command to change the (% style="color:green" %)**uplink interval**. 327 327 328 328 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 329 329 330 330 ((( 331 -(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.** 316 +(% style="color:red" %)**NOTE:** 317 +))) 332 332 333 - 319 +((( 320 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 334 334 ))) 335 335 336 -**NOTE:When the firmware version is v1.3.2 and later firmware:** 337 337 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).** 339 339 340 - 341 341 == 2.3 Uplink Payload == 342 342 343 - 344 -=== 2.3.1 Before Firmware 1.3.2 === 345 - 346 346 In this mode, uplink payload includes in total 14 bytes 347 347 329 + 348 348 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 349 349 |=(% style="width: 60px;" %)((( 350 350 **Size(bytes)** ... ... @@ -358,7 +358,6 @@ 358 358 359 359 [[image:1657331036973-987.png]] 360 360 361 - 362 362 ((( 363 363 The payload is ASCII string, representative same HEX: 364 364 ))) ... ... @@ -386,43 +386,16 @@ 386 386 * ((( 387 387 Interrupt: 0x00 = 0 388 388 370 + 371 + 389 389 390 390 ))) 391 391 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 - 420 420 == 2.4 Payload Explanation and Sensor Interface == 421 421 422 422 423 423 === 2.4.1 Device ID === 424 424 425 - 426 426 ((( 427 427 By default, the Device ID equal to the last 6 bytes of IMEI. 428 428 ))) ... ... @@ -429,8 +429,6 @@ 429 429 430 430 ((( 431 431 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 432 - 433 - 434 434 ))) 435 435 436 436 ((( ... ... @@ -446,19 +446,9 @@ 446 446 ))) 447 447 448 448 449 -**NOTE:When the firmware version is v1.3.2 and later firmware:** 450 450 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 - 459 459 === 2.4.2 Version Info === 460 460 461 - 462 462 ((( 463 463 Specify the software version: 0x64=100, means firmware version 1.00. 464 464 ))) ... ... @@ -471,7 +471,6 @@ 471 471 472 472 === 2.4.3 Battery Info === 473 473 474 - 475 475 ((( 476 476 Ex1: 0x0B45 = 2885mV 477 477 ))) ... ... @@ -484,7 +484,6 @@ 484 484 485 485 === 2.4.4 Signal Strength === 486 486 487 - 488 488 ((( 489 489 NB-IoT Network signal Strength. 490 490 ))) ... ... @@ -517,7 +517,6 @@ 517 517 518 518 === 2.4.5 Distance === 519 519 520 - 521 521 Get the distance. Flat object range 280mm - 7500mm. 522 522 523 523 ((( ... ... @@ -540,7 +540,6 @@ 540 540 541 541 === 2.4.6 Digital Interrupt === 542 542 543 - 544 544 ((( 545 545 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. 546 546 ))) ... ... @@ -575,7 +575,6 @@ 575 575 576 576 === 2.4.7 +5V Output === 577 577 578 - 579 579 ((( 580 580 NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 581 581 ))) ... ... @@ -583,14 +583,10 @@ 583 583 584 584 ((( 585 585 The 5V output time can be controlled by AT Command. 586 - 587 - 588 588 ))) 589 589 590 590 ((( 591 591 (% style="color:blue" %)**AT+5VT=1000** 592 - 593 - 594 594 ))) 595 595 596 596 ((( ... ... @@ -601,7 +601,6 @@ 601 601 602 602 == 2.5 Downlink Payload == 603 603 604 - 605 605 By default, NDDS75 prints the downlink payload to console port. 606 606 607 607 [[image:image-20220709100028-1.png]] ... ... @@ -651,44 +651,10 @@ 651 651 ))) 652 652 653 653 654 -== 2.6 Distance alarm function(Since firmware v1.3.2) == 655 655 656 - ➢ATCommand:587 +== 2.6 LED Indicator == 657 657 658 -AT+ LDDSALARM=min,max 659 659 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 - 692 692 The NDDS75 has an internal LED which is to show the status of different state. 693 693 694 694 ... ... @@ -703,29 +703,29 @@ 703 703 704 704 705 705 706 -== 2. 10Firmware Change Log ==604 +== 2.7 Firmware Change Log == 707 707 708 708 709 709 ((( 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 +Download URL & Firmware Change log 711 711 ))) 712 712 713 713 ((( 714 - 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/]] 715 715 ))) 716 716 615 + 717 717 ((( 718 -Upgrade Instruction: [[Upgrade 617 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 719 719 ))) 720 720 721 721 722 722 723 -== 2. 11Battery Analysis ==622 +== 2.8 Battery Analysis == 724 724 624 +=== 2.8.1 Battery Type === 725 725 726 -=== 2.11.1 Battery Type === 727 727 728 - 729 729 ((( 730 730 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. 731 731 ))) ... ... @@ -748,9 +748,8 @@ 748 748 749 749 750 750 751 -=== 2. 11.2 Power consumption Analyze ===649 +=== 2.8.2 Power consumption Analyze === 752 752 753 - 754 754 ((( 755 755 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. 756 756 ))) ... ... @@ -787,9 +787,8 @@ 787 787 788 788 789 789 790 -=== 2. 11.3 Battery Note ===687 +=== 2.8.3 Battery Note === 791 791 792 - 793 793 ((( 794 794 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. 795 795 ))) ... ... @@ -796,9 +796,8 @@ 796 796 797 797 798 798 799 -=== 2. 11.4 Replace the battery ===695 +=== 2.8.4 Replace the battery === 800 800 801 - 802 802 ((( 803 803 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). 804 804 ))) ... ... @@ -807,7 +807,6 @@ 807 807 808 808 = 3. Access NB-IoT Module = 809 809 810 - 811 811 ((( 812 812 Users can directly access the AT command set of the NB-IoT module. 813 813 ))) ... ... @@ -814,8 +814,6 @@ 814 814 815 815 ((( 816 816 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 - 819 819 ))) 820 820 821 821 [[image:1657333200519-600.png]] ... ... @@ -824,13 +824,11 @@ 824 824 825 825 = 4. Using the AT Commands = 826 826 827 - 828 828 == 4.1 Access AT Commands == 829 829 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/]] 830 830 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]] 832 832 833 - 834 834 AT+<CMD>? : Help on <CMD> 835 835 836 836 AT+<CMD> : Run <CMD> ... ... @@ -870,23 +870,7 @@ 870 870 871 871 AT+SERVADDR : Server Address 872 872 873 -AT+TR : Get or Set record time" 874 874 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 - 890 890 (% style="color:#037691" %)**COAP Management** 891 891 892 892 AT+URI : Resource parameters ... ... @@ -920,7 +920,6 @@ 920 920 921 921 = 5. FAQ = 922 922 923 - 924 924 == 5.1 How to Upgrade Firmware == 925 925 926 926 ... ... @@ -933,7 +933,7 @@ 933 933 ))) 934 934 935 935 ((( 936 -(% style="color:red" %) **Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**809 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 937 937 ))) 938 938 939 939 ... ... @@ -940,7 +940,6 @@ 940 940 941 941 = 6. Trouble Shooting = 942 942 943 - 944 944 == 6.1 Connection problem when uploading firmware == 945 945 946 946 ... ... @@ -956,7 +956,6 @@ 956 956 957 957 == 6.2 AT Command input doesn't work == 958 958 959 - 960 960 ((( 961 961 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. 962 962 ... ... @@ -989,7 +989,6 @@ 989 989 ((( 990 990 991 991 992 - 993 993 (% style="color:#037691" %)**Dimension and weight**: 994 994 995 995 * Device Size: 13.0 x 5 x 4.5 cm ... ... @@ -1007,6 +1007,5 @@ 1007 1007 1008 1008 = 9. Support = 1009 1009 1010 - 1011 1011 * 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. 1012 1012 * 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