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, 0 added, 3 removed)
Details
- Page properties
-
- Content
-
... ... @@ -53,6 +53,7 @@ 53 53 [[image:1657327959271-447.png]] 54 54 55 55 56 + 56 56 == 1.2 Features == 57 57 58 58 ... ... @@ -81,12 +81,12 @@ 81 81 82 82 (% style="color:#037691" %)**NB-IoT Spec:** 83 83 84 -* B1 @H-FDD: 2100MHz 85 -* B3 @H-FDD: 1800MHz 86 -* B8 @H-FDD: 900MHz 87 -* B5 @H-FDD: 850MHz 88 -* B20 @H-FDD: 800MHz 89 -* B28 @H-FDD: 700MHz 85 +* - B1 @H-FDD: 2100MHz 86 +* - B3 @H-FDD: 1800MHz 87 +* - B8 @H-FDD: 900MHz 88 +* - B5 @H-FDD: 850MHz 89 +* - B20 @H-FDD: 800MHz 90 +* - B28 @H-FDD: 700MHz 90 90 91 91 (% style="color:#037691" %)**Battery:** 92 92 ... ... @@ -99,7 +99,7 @@ 99 99 (% style="color:#037691" %)**Power Consumption** 100 100 101 101 * STOP Mode: 10uA @ 3.3v 102 -* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]103 +* Max transmit power: 350mA@3.3v 103 103 104 104 105 105 ... ... @@ -123,6 +123,7 @@ 123 123 [[image:1657328609906-564.png]] 124 124 125 125 127 + 126 126 = 2. Use NDDS75 to communicate with IoT Server = 127 127 128 128 == 2.1 How it works == ... ... @@ -147,8 +147,10 @@ 147 147 148 148 ))) 149 149 152 + 150 150 == 2.2 Configure the NDDS75 == 151 151 155 + 152 152 === 2.2.1 Test Requirement === 153 153 154 154 ... ... @@ -168,6 +168,7 @@ 168 168 [[image:1657328756309-230.png]] 169 169 170 170 175 + 171 171 === 2.2.2 Insert SIM card === 172 172 173 173 ... ... @@ -183,6 +183,7 @@ 183 183 [[image:1657328884227-504.png]] 184 184 185 185 191 + 186 186 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 187 187 188 188 ... ... @@ -194,16 +194,15 @@ 194 194 195 195 [[image:image-20220709092052-2.png]] 196 196 203 +**Connection:** 197 197 198 -(% style="color: blue" %)**Connection:**205 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 199 199 200 - (% style="background-color:yellow" %) **USB TTLGND <~-~-~-~->GND**207 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 201 201 202 - **~(% style="background-color:yellow" %)USB TTLTXD <~-~-~-~-> UART_RXD(%%)**209 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 203 203 204 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 205 205 206 - 207 207 In the PC, use below serial tool settings: 208 208 209 209 * Baud: (% style="color:green" %)**9600** ... ... @@ -218,12 +218,12 @@ 218 218 219 219 [[image:1657329814315-101.png]] 220 220 221 - 222 222 ((( 223 -(% 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]]**227 +(% 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/]] 224 224 ))) 225 225 226 226 231 + 227 227 === 2.2.4 Use CoAP protocol to uplink data === 228 228 229 229 ... ... @@ -238,40 +238,33 @@ 238 238 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 239 239 ))) 240 240 * ((( 241 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ 246 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 242 242 ))) 243 243 * ((( 244 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 245 - 246 - 247 - 249 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 248 248 ))) 249 249 250 250 ((( 251 251 For parameter description, please refer to AT command set 252 - 253 - 254 254 ))) 255 255 256 256 [[image:1657330452568-615.png]] 257 257 258 258 259 - 260 260 ((( 261 261 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. 262 - 263 - 264 264 ))) 265 265 266 266 [[image:1657330472797-498.png]] 267 267 268 268 266 + 269 269 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 270 270 271 271 272 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ 273 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ 274 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 270 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 271 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 272 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 275 275 276 276 [[image:1657330501006-241.png]] 277 277 ... ... @@ -279,16 +279,17 @@ 279 279 [[image:1657330533775-472.png]] 280 280 281 281 280 + 282 282 === 2.2.6 Use MQTT protocol to uplink data === 283 283 284 284 285 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ 286 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ 287 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ 288 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ 289 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ 290 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/ 291 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/ 284 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 285 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 286 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 287 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 288 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 289 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 290 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 292 292 293 293 [[image:1657249978444-674.png]] 294 294 ... ... @@ -301,11 +301,12 @@ 301 301 ))) 302 302 303 303 303 + 304 304 === 2.2.7 Use TCP protocol to uplink data === 305 305 306 306 307 -* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ 308 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ 307 +* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 308 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 309 309 310 310 [[image:image-20220709093918-1.png]] 311 311 ... ... @@ -313,34 +313,30 @@ 313 313 [[image:image-20220709093918-2.png]] 314 314 315 315 316 + 316 316 === 2.2.8 Change Update Interval === 317 317 318 318 319 319 User can use below command to change the (% style="color:green" %)**uplink interval**. 320 320 321 -* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ 322 +* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 322 322 323 323 ((( 324 - 325 - 326 - 327 327 (% style="color:red" %)**NOTE:** 326 +))) 328 328 328 +((( 329 329 (% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** 330 - 331 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:** 332 332 ))) 333 333 334 -(% 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).** 335 335 336 336 337 337 == 2.3 Uplink Payload == 338 338 339 -=== 2.3.1 Before Firmware v1.3.2 === 340 340 341 - 342 342 In this mode, uplink payload includes in total 14 bytes 343 343 339 + 344 344 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 345 345 |=(% style="width: 60px;" %)((( 346 346 **Size(bytes)** ... ... @@ -348,79 +348,47 @@ 348 348 |(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]] 349 349 350 350 ((( 351 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 347 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 352 352 ))) 353 353 354 354 355 355 [[image:1657331036973-987.png]] 356 356 357 - 358 -The payload is **ASCII** string, representative same HEX: 359 - 360 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 ** 361 - 362 -**where :** 363 - 364 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159 365 - 366 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 367 - 368 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V 369 - 370 -* (% style="color:#037691" %)**Signal:**(%%) 0x19 = 25 371 - 372 -* (% style="color:#037691" %)**Distance:** (%%)0x0292= 658 mm 373 - 374 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0 375 - 376 - 377 - 378 -=== 2.3.2 Since firmware v1.3.2 === 379 - 380 - 381 -In this mode, uplink payload includes 69 bytes in total by default. 382 - 383 -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. 384 - 385 -(% border="1" style="background-color:#ffffcc; color:green; width:490px" %) 386 -|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:70px" %)**4**|(% style="width:40px" %)**2**|(% style="width:60px" %)**4** 387 -|=(% 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....... 388 - 389 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 390 - 391 -[[image:image-20220908175246-1.png]] 392 - 393 - 353 +((( 394 394 The payload is ASCII string, representative same HEX: 355 +))) 395 395 396 -**0x (% style="color:red" %)f867787050213317 (% style="color:blue" %)0084 (% style="color:green" %)0cf4 (% style="color:#00b0f0" %)1e (% style="color:#7030a0" %)01 (% style="color:#d60093" %)00(% style="color:#a14d07" %) 0039 (% style="color:#0020b0" %)6315537b (% style="color:#663300" %)00396319baf0 00396319ba3c 00396319b988 00396319b8d4 00396319b820 00396319b76c 00396319b6b8 00396319b604 (%%)** 357 +((( 358 +0x72403155615900640c6c19029200 where: 359 +))) 397 397 398 -**where:** 361 +* ((( 362 +Device ID: 0x724031556159 = 724031556159 363 +))) 364 +* ((( 365 +Version: 0x0064=100=1.0.0 366 +))) 399 399 400 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317 368 +* ((( 369 +BAT: 0x0c6c = 3180 mV = 3.180V 370 +))) 371 +* ((( 372 +Signal: 0x19 = 25 373 +))) 374 +* ((( 375 +Distance: 0x0292= 658 mm 376 +))) 377 +* ((( 378 +Interrupt: 0x00 = 0 401 401 402 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2 403 403 404 -* (% style="color:#037691" %)**BAT:**(%%) 0x0cf4 = 3316 mV = 3.316V 405 405 406 -* (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 382 + 383 +))) 407 407 408 -* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 409 - 410 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 411 - 412 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57 413 - 414 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 415 - 416 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0 417 - 418 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 419 - 420 - 421 - 422 422 == 2.4 Payload Explanation and Sensor Interface == 423 423 387 + 424 424 === 2.4.1 Device ID === 425 425 426 426 ... ... @@ -430,12 +430,10 @@ 430 430 431 431 ((( 432 432 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 433 - 434 - 435 435 ))) 436 436 437 437 ((( 438 - (% style="color:blue" %)**Example400 +**Example:** 439 439 ))) 440 440 441 441 ((( ... ... @@ -443,22 +443,11 @@ 443 443 ))) 444 444 445 445 ((( 446 -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.408 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 447 447 ))) 448 448 449 449 450 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:** 451 451 452 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.** 453 - 454 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 455 - 456 - 457 -(% style="color:blue" %)**Example :** 458 - 459 -AT+DEUI=868411056754138 460 - 461 - 462 462 === 2.4.2 Version Info === 463 463 464 464 ... ... @@ -471,6 +471,7 @@ 471 471 ))) 472 472 473 473 425 + 474 474 === 2.4.3 Battery Info === 475 475 476 476 ... ... @@ -483,6 +483,7 @@ 483 483 ))) 484 484 485 485 438 + 486 486 === 2.4.4 Signal Strength === 487 487 488 488 ... ... @@ -515,6 +515,7 @@ 515 515 ))) 516 516 517 517 471 + 518 518 === 2.4.5 Distance === 519 519 520 520 ... ... @@ -534,6 +534,10 @@ 534 534 535 535 ))) 536 536 491 +((( 492 + 493 +))) 494 + 537 537 === 2.4.6 Digital Interrupt === 538 538 539 539 ... ... @@ -546,7 +546,7 @@ 546 546 ))) 547 547 548 548 ((( 549 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/ 507 +(% 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]])**.** 550 550 ))) 551 551 552 552 ... ... @@ -568,6 +568,7 @@ 568 568 ))) 569 569 570 570 529 + 571 571 === 2.4.7 +5V Output === 572 572 573 573 ... ... @@ -578,14 +578,10 @@ 578 578 579 579 ((( 580 580 The 5V output time can be controlled by AT Command. 581 - 582 - 583 583 ))) 584 584 585 585 ((( 586 586 (% style="color:blue" %)**AT+5VT=1000** 587 - 588 - 589 589 ))) 590 590 591 591 ((( ... ... @@ -593,6 +593,7 @@ 593 593 ))) 594 594 595 595 551 + 596 596 == 2.5 Downlink Payload == 597 597 598 598 ... ... @@ -645,85 +645,126 @@ 645 645 ))) 646 646 647 647 648 -== 2.6 Distance alarm function(Since firmware v1.3.2) == 649 649 605 +== 2.6 LED Indicator == 650 650 651 -(% style="color:blue" %)** ➢ AT Command:** 652 652 653 - (%style="color:#037691"%)**AT+LDDSALARM=min,max**608 +The NDDS75 has an internal LED which is to show the status of different state. 654 654 655 -² When min=0, and max≠0, Alarm higher than max 656 656 657 -² When min≠0, and max=0, Alarm lower than min 611 +* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 612 +* Then the LED will be on for 1 second means device is boot normally. 613 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 614 +* For each uplink probe, LED will be on for 500ms. 658 658 659 -² When min≠0 and max≠0, Alarm higher than max or lower than min 616 +((( 617 + 618 +))) 660 660 661 661 662 -(% style="color:blue" %)** Example:** 663 663 664 - **AT+ LDDSALARM=260,2000**~/~/ Alarmhendistancelowerthan 260.622 +== 2.7 Firmware Change Log == 665 665 666 666 667 -== 2.7 Set the number of data to be uploaded and the recording time == 625 +((( 626 +Download URL & Firmware Change log 627 +))) 668 668 629 +((( 630 +[[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/]] 631 +))) 669 669 670 -(% style="color:blue" %)** ➢ AT Command:** 671 671 672 -* (% 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) 673 -* (% 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. 634 +((( 635 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 636 +))) 674 674 675 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 676 676 677 -[[image:image-20221009001114-1.png||height="687" width="955"]] 678 678 640 +== 2.8 Battery Analysis == 679 679 680 -== 2.8 Read or Clearcacheddata==642 +=== 2.8.1 Battery Type === 681 681 682 682 683 -(% style="color:blue" %)** ➢ AT Command:** 645 +((( 646 +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. 647 +))) 684 684 685 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 686 -* (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 649 +((( 650 +The battery is designed to last for several years depends on the actually use environment and update interval. 651 +))) 687 687 688 -[[image:image-20220908175333-2.png]] 653 +((( 654 +The battery related documents as below: 655 +))) 689 689 657 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 658 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 659 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 690 690 691 -== 2.9 LED Indicator == 661 +((( 662 +[[image:image-20220709101450-2.png]] 663 +))) 692 692 693 693 694 -The NDDS75 has an internal LED which is to show the status of different state. 695 695 667 +=== 2.8.2 Power consumption Analyze === 696 696 697 -* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 698 -* Then the LED will be on for 1 second means device is boot normally. 699 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 700 -* For each uplink probe, LED will be on for 500ms. 701 701 702 702 ((( 703 - 671 +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. 704 704 ))) 705 705 706 706 707 -== 2.10 Firmware Change Log == 675 +((( 676 +Instruction to use as below: 677 +))) 708 708 679 +((( 680 +(% style="color:blue" %)**Step 1: **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]] 681 +))) 709 709 683 + 710 710 ((( 711 - Download URL & FirmwareChangelog:[[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]]685 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 712 712 ))) 713 713 688 +* ((( 689 +Product Model 690 +))) 691 +* ((( 692 +Uplink Interval 693 +))) 694 +* ((( 695 +Working Mode 696 +))) 697 + 714 714 ((( 715 - UpgradeInstruction:[[UpgradeFirmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]699 +And the Life expectation in difference case will be shown on the right. 716 716 ))) 717 717 702 +[[image:image-20220709110451-3.png]] 718 718 719 -== 2.11 Battery & Power Consumption == 720 720 721 721 722 - NDDS75uses ER26500 + SPC1520 battery pack.See below link for detail information aboutthebatteryinfoand howto replace.706 +=== 2.8.3 Battery Note === 723 723 724 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 725 725 709 +((( 710 +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. 711 +))) 726 726 713 + 714 + 715 +=== 2.8.4 Replace the battery === 716 + 717 + 718 +((( 719 +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). 720 +))) 721 + 722 + 723 + 727 727 = 3. Access NB-IoT Module = 728 728 729 729 ... ... @@ -733,107 +733,91 @@ 733 733 734 734 ((( 735 735 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/]] 736 - 737 - 738 738 ))) 739 739 740 740 [[image:1657333200519-600.png]] 741 741 742 742 738 + 743 743 = 4. Using the AT Commands = 744 744 745 745 == 4.1 Access AT Commands == 746 746 747 747 748 -See this link for detail: pbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]744 +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/]] 749 749 750 750 751 -AT+<CMD>? : 747 +AT+<CMD>? : Help on <CMD> 752 752 753 -AT+<CMD> : 749 +AT+<CMD> : Run <CMD> 754 754 755 -AT+<CMD>=<value> : 751 +AT+<CMD>=<value> : Set the value 756 756 757 -AT+<CMD>=? : 753 +AT+<CMD>=? : Get the value 758 758 759 759 760 760 (% style="color:#037691" %)**General Commands**(%%) 761 761 762 -AT : 758 +AT : Attention 763 763 764 -AT? : 760 +AT? : Short Help 765 765 766 -ATZ : 762 +ATZ : MCU Reset 767 767 768 -AT+TDC : 764 +AT+TDC : Application Data Transmission Interval 769 769 770 -AT+CFG : 766 +AT+CFG : Print all configurations 771 771 772 -AT+CFGMOD : 768 +AT+CFGMOD : Working mode selection 773 773 774 -AT+INTMOD : 770 +AT+INTMOD : Set the trigger interrupt mode 775 775 776 -AT+5VT : 772 +AT+5VT : Set extend the time of 5V power 777 777 778 -AT+PRO : 774 +AT+PRO : Choose agreement 779 779 780 -AT+WEIGRE : 776 +AT+WEIGRE : Get weight or set weight to 0 781 781 782 -AT+WEIGAP : 778 +AT+WEIGAP : Get or Set the GapValue of weight 783 783 784 -AT+RXDL : 780 +AT+RXDL : Extend the sending and receiving time 785 785 786 -AT+CNTFAC : 782 +AT+CNTFAC : Get or set counting parameters 787 787 788 -AT+SERVADDR : 784 +AT+SERVADDR : Server Address 789 789 790 -AT+TR : Get or Set record time" 791 791 792 -AT+APN : Get or set the APN 793 - 794 -AT+FBAND : Get or Set whether to automatically modify the frequency band 795 - 796 -AT+DNSCFG : Get or Set DNS Server 797 - 798 -AT+GETSENSORVALUE : Returns the current sensor measurement 799 - 800 -AT+NOUD : Get or Set the number of data to be uploaded 801 - 802 -AT+CDP : Read or Clear cached data 803 - 804 -AT+LDDSALARM : Get or Set alarm of distance 805 - 806 - 807 807 (% style="color:#037691" %)**COAP Management** 808 808 809 -AT+URI : 789 +AT+URI : Resource parameters 810 810 811 811 812 812 (% style="color:#037691" %)**UDP Management** 813 813 814 -AT+CFM : 794 +AT+CFM : Upload confirmation mode (only valid for UDP) 815 815 816 816 817 817 (% style="color:#037691" %)**MQTT Management** 818 818 819 -AT+CLIENT 799 +AT+CLIENT : Get or Set MQTT client 820 820 821 -AT+UNAME :Get or Set MQTT Username801 +AT+UNAME : Get or Set MQTT Username 822 822 823 -AT+PWD 803 +AT+PWD : Get or Set MQTT password 824 824 825 -AT+PUBTOPIC :Get or Set MQTT publish topic805 +AT+PUBTOPIC : Get or Set MQTT publish topic 826 826 827 -AT+SUBTOPIC :Get or Set MQTT subscription topic807 +AT+SUBTOPIC : Get or Set MQTT subscription topic 828 828 829 829 830 830 (% style="color:#037691" %)**Information** 831 831 832 -AT+FDR : 812 +AT+FDR : Factory Data Reset 833 833 834 -AT+PWORD : 814 +AT+PWORD : Serial Access Password 835 835 836 836 817 + 837 837 = 5. FAQ = 838 838 839 839 == 5.1 How to Upgrade Firmware == ... ... @@ -852,6 +852,7 @@ 852 852 ))) 853 853 854 854 836 + 855 855 = 6. Trouble Shooting = 856 856 857 857 == 6.1 Connection problem when uploading firmware == ... ... @@ -866,11 +866,14 @@ 866 866 867 867 ))) 868 868 851 + 869 869 == 6.2 AT Command input doesn't work == 870 870 871 871 872 872 ((( 873 873 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. 857 + 858 + 874 874 ))) 875 875 876 876 ... ... @@ -880,6 +880,11 @@ 880 880 Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 881 881 882 882 868 +(% class="wikigeneratedid" %) 869 +((( 870 + 871 +))) 872 + 883 883 = 8. Packing Info = 884 884 885 885 ((( ... ... @@ -905,6 +905,7 @@ 905 905 ((( 906 906 907 907 898 + 908 908 909 909 ))) 910 910
- 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
- image-20221009001114-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content