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)
-
Attachments (0 modified, 2 added, 0 removed)
Details
- Page properties
-
- 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 ... ... @@ -73,6 +73,7 @@ 73 73 74 74 == 1.3 Specification == 75 75 78 + 76 76 (% style="color:#037691" %)**Common DC Characteristics:** 77 77 78 78 * Supply Voltage: 2.1v ~~ 3.6v ... ... @@ -104,6 +104,7 @@ 104 104 105 105 == 1.4 Applications == 106 106 110 + 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 122 + 123 + 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 133 + 127 127 == 2.1 How it works == 128 128 136 + 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 162 + 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 172 +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 182 + 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 198 + 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,15 +193,16 @@ 193 193 194 194 [[image:image-20220709092052-2.png]] 195 195 196 -**Connection:** 197 197 198 - background-color:yellow" %)USB TTL GND <~-~-~-~-> GND208 +(% style="color:blue" %)**Connection:** 199 199 200 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~->UART_RXD210 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 201 201 202 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD212 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 203 203 214 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 204 204 216 + 205 205 In the PC, use below serial tool settings: 206 206 207 207 * Baud: (% style="color:green" %)**9600** ... ... @@ -216,8 +216,9 @@ 216 216 217 217 [[image:1657329814315-101.png]] 218 218 231 + 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/]]233 +(% 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 241 +(% 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 243 + 230 230 ((( 231 231 **Use below commands:** 232 232 ))) ... ... @@ -235,21 +235,29 @@ 235 235 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 236 236 ))) 237 237 * ((( 238 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 252 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 239 239 ))) 240 240 * ((( 241 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 255 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 256 + 257 + 258 + 242 242 ))) 243 243 244 244 ((( 245 245 For parameter description, please refer to AT command set 263 + 264 + 246 246 ))) 247 247 248 248 [[image:1657330452568-615.png]] 249 249 250 250 270 + 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. 273 + 274 + 253 253 ))) 254 254 255 255 [[image:1657330472797-498.png]] ... ... @@ -259,10 +259,12 @@ 259 259 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 260 260 261 261 262 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 263 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 264 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 284 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 285 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 286 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 265 265 288 + 289 + 266 266 [[image:1657330501006-241.png]] 267 267 268 268 ... ... @@ -273,13 +273,13 @@ 273 273 === 2.2.6 Use MQTT protocol to uplink data === 274 274 275 275 276 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 277 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 278 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 279 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 280 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 281 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 282 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 300 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 301 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 302 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 303 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 304 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 305 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/ Set the sending topic of MQTT 306 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/ Set the subscription topic of MQTT 283 283 284 284 [[image:1657249978444-674.png]] 285 285 ... ... @@ -296,8 +296,8 @@ 296 296 === 2.2.7 Use TCP protocol to uplink data === 297 297 298 298 299 -* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 300 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 323 +* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 324 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 301 301 302 302 [[image:image-20220709093918-1.png]] 303 303 ... ... @@ -308,25 +308,34 @@ 308 308 309 309 === 2.2.8 Change Update Interval === 310 310 335 + 311 311 User can use below command to change the (% style="color:green" %)**uplink interval**. 312 312 313 -* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 338 +* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 314 314 315 315 ((( 341 + 342 + 343 + 316 316 (% style="color:red" %)**NOTE:** 317 -))) 318 318 319 -((( 320 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 346 +(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** 347 + 348 +(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:** 321 321 ))) 322 322 351 +(% style="color:red" %)**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 324 324 354 + 325 325 == 2.3 Uplink Payload == 326 326 327 -In this mode, uplink payload includes in total 14 bytes 328 328 358 +=== 2.3.1 Before Firmware v1.3.2 === 329 329 360 + 361 +In this mode, uplink payload includes in total 14 bytes 362 + 330 330 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 331 331 |=(% style="width: 60px;" %)((( 332 332 **Size(bytes)** ... ... @@ -340,8 +340,9 @@ 340 340 341 341 [[image:1657331036973-987.png]] 342 342 376 + 343 343 ((( 344 -The payload is ASCII string, representative same HEX: 378 +The payload is **ASCII** string, representative same HEX: 345 345 ))) 346 346 347 347 ((( ... ... @@ -352,11 +352,11 @@ 352 352 Device ID: 0x724031556159 = 724031556159 353 353 ))) 354 354 * ((( 355 -Version: 0x0064=100=1.0.0 389 +Version: 0x0064=100=1.0.0 356 356 ))) 357 357 358 358 * ((( 359 -BAT: 0x0c6c = 3180 mV = 3.180V 393 +BAT: 0x0c6c = 3180 mV = 3.180V 360 360 ))) 361 361 * ((( 362 362 Signal: 0x19 = 25 ... ... @@ -369,14 +369,49 @@ 369 369 370 370 371 371 406 + 372 372 373 373 ))) 374 374 410 +=== **2.3.2 Since firmware v1.3.2** === 411 + 412 + 413 +In this mode, uplink payload includes 69 bytes in total by default. 414 + 415 +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. 416 + 417 +(% border="2" style="background-color:#ffffcc; color:green; width:896px" %) 418 +|(% style="width:95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)4 419 +|(% style="width:95px" %)**Value**|(% style="width:84px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:48px" %)BAT|(% style="width:123px" %)Signal Strength|(% style="width:55px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:77px" %)Distance|(% style="width:94px" %)Timestamp|(% style="width:77px" %)Distance|(% style="width:116px" %)Timestamp....... 420 + 421 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 422 + 423 +[[image:image-20220908175246-1.png]] 424 + 425 + 426 +The payload is ASCII string, representative same HEX: 427 + 428 +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: 429 + 430 +* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317 431 +* (% style="color:red" %)Version: 0x0084=132=1.3.2 432 +* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V 433 +* (% style="color:blue" %)Singal: 0x1e = 30 434 +* (% style="color:red" %)Mod: 0x01 = 1 435 +* Interrupt: 0x00= 0 436 +* Distance: 0x0039= 57 = 57 437 +* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 438 +* Distance,Time stamp : 00396319baf0 439 +* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,....... 440 + 441 + 442 + 375 375 == 2.4 Payload Explanation and Sensor Interface == 376 376 377 377 378 378 === 2.4.1 Device ID === 379 379 448 + 380 380 ((( 381 381 By default, the Device ID equal to the last 6 bytes of IMEI. 382 382 ))) ... ... @@ -383,10 +383,12 @@ 383 383 384 384 ((( 385 385 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 455 + 456 + 386 386 ))) 387 387 388 388 ((( 389 -**Example:** 460 +(% style="color:blue" %)**Example :** 390 390 ))) 391 391 392 392 ((( ... ... @@ -394,13 +394,26 @@ 394 394 ))) 395 395 396 396 ((( 397 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 468 +The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID. 398 398 ))) 399 399 400 400 472 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:** 401 401 474 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.** 475 + 476 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 477 + 478 + 479 +(% style="color:blue" %)**Example :** 480 + 481 +AT+DEUI=868411056754138 482 + 483 + 484 + 402 402 === 2.4.2 Version Info === 403 403 487 + 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 500 + 416 416 ((( 417 417 Ex1: 0x0B45 = 2885mV 418 418 ))) ... ... @@ -425,6 +425,7 @@ 425 425 426 426 === 2.4.4 Signal Strength === 427 427 513 + 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 546 + 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 569 + 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 ))) ... ... @@ -488,7 +488,7 @@ 488 488 ))) 489 489 490 490 ((( 491 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.** 579 +(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/ (more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.** 492 492 ))) 493 493 494 494 ... ... @@ -513,6 +513,7 @@ 513 513 514 514 === 2.4.7 +5V Output === 515 515 604 + 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. 612 + 613 + 523 523 ))) 524 524 525 525 ((( 526 526 (% style="color:blue" %)**AT+5VT=1000** 618 + 619 + 527 527 ))) 528 528 529 529 ((( ... ... @@ -534,6 +534,7 @@ 534 534 535 535 == 2.5 Downlink Payload == 536 536 630 + 537 537 By default, NDDS75 prints the downlink payload to console port. 538 538 539 539 [[image:image-20220709100028-1.png]] ... ... @@ -584,9 +584,52 @@ 584 584 585 585 586 586 587 -== 2.6 LEDIndicator ==681 +== 2.6 Distance alarm function(Since firmware v1.3.2) == 588 588 589 589 684 +(% style="color:blue" %)** ➢ AT Command:** 685 + 686 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max** 687 + 688 +² When min=0, and max≠0, Alarm higher than max 689 + 690 +² When min≠0, and max=0, Alarm lower than min 691 + 692 +² When min≠0 and max≠0, Alarm higher than max or lower than min 693 + 694 + 695 +(% style="color:blue" %)** Example:** 696 + 697 +**AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 698 + 699 + 700 + 701 +== 2.7 Set the number of data to be uploaded and the recording time == 702 + 703 + 704 +(% style="color:blue" %)** ➢ AT Command:** 705 + 706 +* (% style="color:#037691" %)** 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) 707 +* (% style="color:#037691" %)** AT+NOUD=8** (%%) ~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 708 + 709 + 710 + 711 + 712 +== 2.8 Read or Clear cached data == 713 + 714 + 715 +(% style="color:blue" %)** ➢ AT Command:** 716 + 717 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 718 +* (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 719 + 720 +[[image:image-20220908175333-2.png]] 721 + 722 + 723 + 724 +== 2.9 LED Indicator == 725 + 726 + 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 ==741 +== 2.10 Firmware Change Log == 605 605 606 606 607 607 ((( 608 -Download URL & Firmware Change log 745 +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/]]749 + 613 613 ))) 614 614 615 - 616 616 ((( 617 -Upgrade Instruction: [[Upgrade _Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]753 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 618 618 ))) 619 619 620 620 621 621 622 -== 2. 8Battery Analysis ==758 +== 2.11 Battery Analysis == 623 623 624 -=== 2.8.1 Battery Type === 625 625 761 +=== 2.11.1 Battery Type === 626 626 763 + 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 ===786 +=== 2.11.2 Power consumption Analyze === 650 650 788 + 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 ===825 +=== 2.11.3 Battery Note === 688 688 827 + 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 ===834 +=== 2.11.4 Replace the battery === 696 696 836 + 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 845 + 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/]] 852 + 853 + 711 711 ))) 712 712 713 713 [[image:1657333200519-600.png]] ... ... @@ -716,84 +716,103 @@ 716 716 717 717 = 4. Using the AT Commands = 718 718 862 + 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 866 +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 724 -AT+<CMD>? : Help on <CMD> 725 725 726 -AT+<CMD> Run <CMD>869 +AT+<CMD>? : Help on <CMD> 727 727 728 -AT+<CMD> =<value>:Setthevalue871 +AT+<CMD> : Run <CMD> 729 729 730 -AT+<CMD>= ?Get the value873 +AT+<CMD>=<value> : Set the value 731 731 875 +AT+<CMD>=? : Get the value 732 732 877 + 733 733 (% style="color:#037691" %)**General Commands**(%%) 734 734 735 -AT : Attention 880 +AT : Attention 736 736 737 -AT? : Short Help 882 +AT? : Short Help 738 738 739 -ATZ : MCU Reset 884 +ATZ : MCU Reset 740 740 741 -AT+TDC : Application Data Transmission Interval 886 +AT+TDC : Application Data Transmission Interval 742 742 743 -AT+CFG : Print all configurations 888 +AT+CFG : Print all configurations 744 744 745 -AT+CFGMOD : Working mode selection 890 +AT+CFGMOD : Working mode selection 746 746 747 -AT+INTMOD : Set the trigger interrupt mode 892 +AT+INTMOD : Set the trigger interrupt mode 748 748 749 -AT+5VT : Set extend the time of 5V power 894 +AT+5VT : Set extend the time of 5V power 750 750 751 -AT+PRO : Choose agreement 896 +AT+PRO : Choose agreement 752 752 753 -AT+WEIGRE : Get weight or set weight to 0 898 +AT+WEIGRE : Get weight or set weight to 0 754 754 755 -AT+WEIGAP : Get or Set the GapValue of weight 900 +AT+WEIGAP : Get or Set the GapValue of weight 756 756 757 -AT+RXDL : Extend the sending and receiving time 902 +AT+RXDL : Extend the sending and receiving time 758 758 759 -AT+CNTFAC : Get or set counting parameters 904 +AT+CNTFAC : Get or set counting parameters 760 760 761 -AT+SERVADDR 906 +AT+SERVADDR : Server Address 762 762 908 +AT+TR : Get or Set record time" 763 763 910 +AT+APN : Get or set the APN 911 + 912 +AT+FBAND : Get or Set whether to automatically modify the frequency band 913 + 914 +AT+DNSCFG : Get or Set DNS Server 915 + 916 +AT+GETSENSORVALUE : Returns the current sensor measurement 917 + 918 +AT+NOUD : Get or Set the number of data to be uploaded 919 + 920 +AT+CDP : Read or Clear cached data 921 + 922 +AT+LDDSALARM : Get or Set alarm of distance 923 + 924 + 764 764 (% style="color:#037691" %)**COAP Management** 765 765 766 -AT+URI : Resource parameters 927 +AT+URI : Resource parameters 767 767 768 768 769 769 (% style="color:#037691" %)**UDP Management** 770 770 771 -AT+CFM : Upload confirmation mode (only valid for UDP) 932 +AT+CFM : Upload confirmation mode (only valid for UDP) 772 772 773 773 774 774 (% style="color:#037691" %)**MQTT Management** 775 775 776 -AT+CLIENT 937 +AT+CLIENT : Get or Set MQTT client 777 777 778 -AT+UNAME 939 +AT+UNAME : Get or Set MQTT Username 779 779 780 -AT+PWD 941 +AT+PWD : Get or Set MQTT password 781 781 782 -AT+PUBTOPIC 943 +AT+PUBTOPIC : Get or Set MQTT publish topic 783 783 784 -AT+SUBTOPIC 945 +AT+SUBTOPIC : Get or Set MQTT subscription topic 785 785 786 786 787 787 (% style="color:#037691" %)**Information** 788 788 789 -AT+FDR : Factory Data Reset 950 +AT+FDR : Factory Data Reset 790 790 791 -AT+PWORD : Serial Access Password 952 +AT+PWORD : Serial Access Password 792 792 793 793 794 794 795 795 = 5. FAQ = 796 796 958 + 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. 971 +(% 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 978 + 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 994 + 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 1027 + 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 1045 + 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