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)
Details
- Page properties
-
- Content
-
... ... @@ -70,9 +70,6 @@ 70 70 * Micro SIM card slot for NB-IoT SIM 71 71 * 8500mAh Battery for long term use 72 72 73 - 74 - 75 - 76 76 == 1.3 Specification == 77 77 78 78 ... ... @@ -81,8 +81,6 @@ 81 81 * Supply Voltage: 2.1v ~~ 3.6v 82 82 * Operating Temperature: -40 ~~ 85°C 83 83 84 - 85 - 86 86 (% style="color:#037691" %)**NB-IoT Spec:** 87 87 88 88 * - B1 @H-FDD: 2100MHz ... ... @@ -92,8 +92,6 @@ 92 92 * - B20 @H-FDD: 800MHz 93 93 * - B28 @H-FDD: 700MHz 94 94 95 - 96 - 97 97 (% style="color:#037691" %)**Battery:** 98 98 99 99 * Li/SOCI2 un-chargeable battery ... ... @@ -102,20 +102,13 @@ 102 102 * Max continuously current: 130mA 103 103 * Max boost current: 2A, 1 second 104 104 105 - 106 - 107 107 (% style="color:#037691" %)**Power Consumption** 108 108 109 109 * STOP Mode: 10uA @ 3.3v 110 110 * Max transmit power: 350mA@3.3v 111 111 112 - 113 - 114 - 115 - 116 116 == 1.4 Applications == 117 117 118 - 119 119 * Smart Buildings & Home Automation 120 120 * Logistics and Supply Chain Management 121 121 * Smart Metering ... ... @@ -127,8 +127,6 @@ 127 127 128 128 129 129 130 - 131 - 132 132 == 1.5 Pin Definitions == 133 133 134 134 ... ... @@ -138,10 +138,8 @@ 138 138 139 139 = 2. Use NDDS75 to communicate with IoT Server = 140 140 141 - 142 142 == 2.1 How it works == 143 143 144 - 145 145 ((( 146 146 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. 147 147 ))) ... ... @@ -167,17 +167,16 @@ 167 167 168 168 === 2.2.1 Test Requirement === 169 169 170 - 171 171 ((( 172 172 To use NDDS75 in your city, make sure meet below requirements: 173 173 ))) 174 174 175 175 * Your local operator has already distributed a NB-IoT Network there. 176 -* The local NB-IoT network used the band that N DDS75supports.157 +* The local NB-IoT network used the band that NSE01 supports. 177 177 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 178 178 179 179 ((( 180 -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 .161 +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 181 181 ))) 182 182 183 183 ... ... @@ -187,7 +187,6 @@ 187 187 188 188 === 2.2.2 Insert SIM card === 189 189 190 - 191 191 ((( 192 192 Insert the NB-IoT Card get from your provider. 193 193 ))) ... ... @@ -203,7 +203,6 @@ 203 203 204 204 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 205 205 206 - 207 207 ((( 208 208 ((( 209 209 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. ... ... @@ -212,7 +212,6 @@ 212 212 213 213 [[image:image-20220709092052-2.png]] 214 214 215 - 216 216 **Connection:** 217 217 218 218 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -236,9 +236,8 @@ 236 236 237 237 [[image:1657329814315-101.png]] 238 238 239 - 240 240 ((( 241 -(% 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]]**218 +(% 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/]] 242 242 ))) 243 243 244 244 ... ... @@ -245,10 +245,9 @@ 245 245 246 246 === 2.2.4 Use CoAP protocol to uplink data === 247 247 225 +(% 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/]] 248 248 249 -(% 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/]]** 250 250 251 - 252 252 ((( 253 253 **Use below commands:** 254 254 ))) ... ... @@ -270,7 +270,6 @@ 270 270 [[image:1657330452568-615.png]] 271 271 272 272 273 - 274 274 ((( 275 275 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. 276 276 ))) ... ... @@ -286,8 +286,6 @@ 286 286 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 287 287 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 288 288 289 - 290 - 291 291 [[image:1657330501006-241.png]] 292 292 293 293 ... ... @@ -306,8 +306,6 @@ 306 306 * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 307 307 * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 308 308 309 - 310 - 311 311 [[image:1657249978444-674.png]] 312 312 313 313 ... ... @@ -326,8 +326,6 @@ 326 326 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 327 327 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 328 328 329 - 330 - 331 331 [[image:image-20220709093918-1.png]] 332 332 333 333 ... ... @@ -337,7 +337,6 @@ 337 337 338 338 === 2.2.8 Change Update Interval === 339 339 340 - 341 341 User can use below command to change the (% style="color:green" %)**uplink interval**. 342 342 343 343 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -347,7 +347,7 @@ 347 347 ))) 348 348 349 349 ((( 350 -(% style="color:red" %) **1. By default, the device will send an uplink message every 1 hour.**318 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 351 351 ))) 352 352 353 353 ... ... @@ -354,7 +354,6 @@ 354 354 355 355 == 2.3 Uplink Payload == 356 356 357 - 358 358 In this mode, uplink payload includes in total 14 bytes 359 359 360 360 ... ... @@ -371,7 +371,6 @@ 371 371 372 372 [[image:1657331036973-987.png]] 373 373 374 - 375 375 ((( 376 376 The payload is ASCII string, representative same HEX: 377 377 ))) ... ... @@ -409,7 +409,6 @@ 409 409 410 410 === 2.4.1 Device ID === 411 411 412 - 413 413 ((( 414 414 By default, the Device ID equal to the last 6 bytes of IMEI. 415 415 ))) ... ... @@ -416,8 +416,6 @@ 416 416 417 417 ((( 418 418 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 419 - 420 - 421 421 ))) 422 422 423 423 ((( ... ... @@ -436,7 +436,6 @@ 436 436 437 437 === 2.4.2 Version Info === 438 438 439 - 440 440 ((( 441 441 Specify the software version: 0x64=100, means firmware version 1.00. 442 442 ))) ... ... @@ -449,7 +449,6 @@ 449 449 450 450 === 2.4.3 Battery Info === 451 451 452 - 453 453 ((( 454 454 Ex1: 0x0B45 = 2885mV 455 455 ))) ... ... @@ -462,7 +462,6 @@ 462 462 463 463 === 2.4.4 Signal Strength === 464 464 465 - 466 466 ((( 467 467 NB-IoT Network signal Strength. 468 468 ))) ... ... @@ -495,7 +495,6 @@ 495 495 496 496 === 2.4.5 Distance === 497 497 498 - 499 499 Get the distance. Flat object range 280mm - 7500mm. 500 500 501 501 ((( ... ... @@ -518,7 +518,6 @@ 518 518 519 519 === 2.4.6 Digital Interrupt === 520 520 521 - 522 522 ((( 523 523 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. 524 524 ))) ... ... @@ -553,7 +553,6 @@ 553 553 554 554 === 2.4.7 +5V Output === 555 555 556 - 557 557 ((( 558 558 NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 559 559 ))) ... ... @@ -561,14 +561,10 @@ 561 561 562 562 ((( 563 563 The 5V output time can be controlled by AT Command. 564 - 565 - 566 566 ))) 567 567 568 568 ((( 569 569 (% style="color:blue" %)**AT+5VT=1000** 570 - 571 - 572 572 ))) 573 573 574 574 ((( ... ... @@ -579,7 +579,6 @@ 579 579 580 580 == 2.5 Downlink Payload == 581 581 582 - 583 583 By default, NDDS75 prints the downlink payload to console port. 584 584 585 585 [[image:image-20220709100028-1.png]] ... ... @@ -651,15 +651,16 @@ 651 651 652 652 653 653 ((( 654 -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]]606 +Download URL & Firmware Change log 655 655 ))) 656 656 657 657 ((( 658 - 610 +[[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/]] 659 659 ))) 660 660 613 + 661 661 ((( 662 -Upgrade Instruction: [[Upgrade 615 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 663 663 ))) 664 664 665 665 ... ... @@ -666,7 +666,6 @@ 666 666 667 667 == 2.8 Battery Analysis == 668 668 669 - 670 670 === 2.8.1 Battery Type === 671 671 672 672 ... ... @@ -694,7 +694,6 @@ 694 694 695 695 === 2.8.2 Power consumption Analyze === 696 696 697 - 698 698 ((( 699 699 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. 700 700 ))) ... ... @@ -733,7 +733,6 @@ 733 733 734 734 === 2.8.3 Battery Note === 735 735 736 - 737 737 ((( 738 738 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. 739 739 ))) ... ... @@ -742,7 +742,6 @@ 742 742 743 743 === 2.8.4 Replace the battery === 744 744 745 - 746 746 ((( 747 747 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). 748 748 ))) ... ... @@ -751,7 +751,6 @@ 751 751 752 752 = 3. Access NB-IoT Module = 753 753 754 - 755 755 ((( 756 756 Users can directly access the AT command set of the NB-IoT module. 757 757 ))) ... ... @@ -758,8 +758,6 @@ 758 758 759 759 ((( 760 760 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/]] 761 - 762 - 763 763 ))) 764 764 765 765 [[image:1657333200519-600.png]] ... ... @@ -768,13 +768,11 @@ 768 768 769 769 = 4. Using the AT Commands = 770 770 771 - 772 772 == 4.1 Access AT Commands == 773 773 719 +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/]] 774 774 775 -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]] 776 776 777 - 778 778 AT+<CMD>? : Help on <CMD> 779 779 780 780 AT+<CMD> : Run <CMD> ... ... @@ -848,7 +848,6 @@ 848 848 849 849 = 5. FAQ = 850 850 851 - 852 852 == 5.1 How to Upgrade Firmware == 853 853 854 854 ... ... @@ -861,7 +861,7 @@ 861 861 ))) 862 862 863 863 ((( 864 -(% style="color:red" %) **Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**807 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 865 865 ))) 866 866 867 867 ... ... @@ -868,7 +868,6 @@ 868 868 869 869 = 6. Trouble Shooting = 870 870 871 - 872 872 == 6.1 Connection problem when uploading firmware == 873 873 874 874 ... ... @@ -884,7 +884,6 @@ 884 884 885 885 == 6.2 AT Command input doesn't work == 886 886 887 - 888 888 ((( 889 889 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. 890 890 ... ... @@ -910,7 +910,7 @@ 910 910 911 911 (% style="color:#037691" %)**Package Includes**: 912 912 913 -* N DDS75NB-IoT Distance Detect Sensor Node x 1854 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 914 914 * External antenna x 1 915 915 ))) 916 916 ... ... @@ -919,6 +919,7 @@ 919 919 920 920 (% style="color:#037691" %)**Dimension and weight**: 921 921 863 + 922 922 * Device Size: 13.0 x 5 x 4.5 cm 923 923 * Device Weight: 150g 924 924 * Package Size / pcs : 15 x 12x 5.5 cm ... ... @@ -934,9 +934,5 @@ 934 934 935 935 = 9. Support = 936 936 937 - 938 938 * 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. 939 939 * 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]] 940 - 941 - 942 -