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, 3 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -53,7 +53,6 @@ 53 53 [[image:1657327959271-447.png]] 54 54 55 55 56 - 57 57 == 1.2 Features == 58 58 59 59 ... ... @@ -82,12 +82,12 @@ 82 82 83 83 (% style="color:#037691" %)**NB-IoT Spec:** 84 84 85 -* -B1 @H-FDD: 2100MHz86 -* -B3 @H-FDD: 1800MHz87 -* -B8 @H-FDD: 900MHz88 -* -B5 @H-FDD: 850MHz89 -* -B20 @H-FDD: 800MHz90 -* -B28 @H-FDD: 700MHz84 +* 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 91 91 92 92 (% style="color:#037691" %)**Battery:** 93 93 ... ... @@ -100,7 +100,7 @@ 100 100 (% style="color:#037691" %)**Power Consumption** 101 101 102 102 * STOP Mode: 10uA @ 3.3v 103 -* Max transmit power: 350mA@3.3v 102 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 104 104 105 105 106 106 ... ... @@ -124,7 +124,6 @@ 124 124 [[image:1657328609906-564.png]] 125 125 126 126 127 - 128 128 = 2. Use NDDS75 to communicate with IoT Server = 129 129 130 130 == 2.1 How it works == ... ... @@ -149,10 +149,8 @@ 149 149 150 150 ))) 151 151 152 - 153 153 == 2.2 Configure the NDDS75 == 154 154 155 - 156 156 === 2.2.1 Test Requirement === 157 157 158 158 ... ... @@ -172,7 +172,6 @@ 172 172 [[image:1657328756309-230.png]] 173 173 174 174 175 - 176 176 === 2.2.2 Insert SIM card === 177 177 178 178 ... ... @@ -188,7 +188,6 @@ 188 188 [[image:1657328884227-504.png]] 189 189 190 190 191 - 192 192 === 2.2.3 Connect USB – TTL to NDDS75 to configure it === 193 193 194 194 ... ... @@ -200,15 +200,16 @@ 200 200 201 201 [[image:image-20220709092052-2.png]] 202 202 203 -**Connection:** 204 204 205 - background-color:yellow" %)USB TTL GND <~-~-~-~-> GND198 +(% style="color:blue" %)**Connection:** 206 206 207 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~->UART_RXD200 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 208 208 209 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD202 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 210 210 204 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 211 211 206 + 212 212 In the PC, use below serial tool settings: 213 213 214 214 * Baud: (% style="color:green" %)**9600** ... ... @@ -223,12 +223,12 @@ 223 223 224 224 [[image:1657329814315-101.png]] 225 225 221 + 226 226 ((( 227 -(% 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/]]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]]** 228 228 ))) 229 229 230 230 231 - 232 232 === 2.2.4 Use CoAP protocol to uplink data === 233 233 234 234 ... ... @@ -243,33 +243,40 @@ 243 243 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 244 244 ))) 245 245 * ((( 246 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 241 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 247 247 ))) 248 248 * ((( 249 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 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 + 250 250 ))) 251 251 252 252 ((( 253 253 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 + 259 259 ((( 260 260 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 + 261 261 ))) 262 262 263 263 [[image:1657330472797-498.png]] 264 264 265 265 266 - 267 267 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 268 268 269 269 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 272 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 273 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 274 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 273 273 274 274 [[image:1657330501006-241.png]] 275 275 ... ... @@ -277,17 +277,16 @@ 277 277 [[image:1657330533775-472.png]] 278 278 279 279 280 - 281 281 === 2.2.6 Use MQTT protocol to uplink data === 282 282 283 283 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 285 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 286 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 287 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 288 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 289 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 290 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/ Set the sending topic of MQTT 291 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/ Set the subscription topic of MQTT 291 291 292 292 [[image:1657249978444-674.png]] 293 293 ... ... @@ -300,12 +300,11 @@ 300 300 ))) 301 301 302 302 303 - 304 304 === 2.2.7 Use TCP protocol to uplink data === 305 305 306 306 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 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,30 +313,34 @@ 313 313 [[image:image-20220709093918-2.png]] 314 314 315 315 316 - 317 317 === 2.2.8 Change Update Interval === 318 318 319 319 320 320 User can use below command to change the (% style="color:green" %)**uplink interval**. 321 321 322 -* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 321 +* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 323 323 324 324 ((( 324 + 325 + 326 + 325 325 (% style="color:red" %)**NOTE:** 326 -))) 327 327 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:** 330 330 ))) 331 331 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).** 332 332 333 333 334 334 == 2.3 Uplink Payload == 335 335 339 +=== 2.3.1 Before Firmware v1.3.2 === 336 336 341 + 337 337 In this mode, uplink payload includes in total 14 bytes 338 338 339 - 340 340 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 341 341 |=(% style="width: 60px;" %)((( 342 342 **Size(bytes)** ... ... @@ -344,47 +344,79 @@ 344 344 |(% 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"]] 345 345 346 346 ((( 347 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 1uplink data.351 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 348 348 ))) 349 349 350 350 351 351 [[image:1657331036973-987.png]] 352 352 353 -((( 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 + 354 354 The payload is ASCII string, representative same HEX: 355 -))) 356 356 357 -((( 358 -0x72403155615900640c6c19029200 where: 359 -))) 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 (%%)** 360 360 361 -* ((( 362 -Device ID: 0x724031556159 = 724031556159 363 -))) 364 -* ((( 365 -Version: 0x0064=100=1.0.0 366 -))) 398 +**where:** 367 367 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 400 +* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317 379 379 402 +* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2 380 380 404 +* (% style="color:#037691" %)**BAT:**(%%) 0x0cf4 = 3316 mV = 3.316V 381 381 382 - 383 -))) 406 +* (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 384 384 385 - ==2.4Payload ExplanationandSensorInterface==408 +* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 386 386 410 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 387 387 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 +== 2.4 Payload Explanation and Sensor Interface == 423 + 388 388 === 2.4.1 Device ID === 389 389 390 390 ... ... @@ -394,10 +394,12 @@ 394 394 395 395 ((( 396 396 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 433 + 434 + 397 397 ))) 398 398 399 399 ((( 400 -**Example:** 438 +(% style="color:blue" %)**Example :** 401 401 ))) 402 402 403 403 ((( ... ... @@ -405,11 +405,22 @@ 405 405 ))) 406 406 407 407 ((( 408 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 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. 409 409 ))) 410 410 411 411 450 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:** 412 412 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 + 413 413 === 2.4.2 Version Info === 414 414 415 415 ... ... @@ -422,7 +422,6 @@ 422 422 ))) 423 423 424 424 425 - 426 426 === 2.4.3 Battery Info === 427 427 428 428 ... ... @@ -435,7 +435,6 @@ 435 435 ))) 436 436 437 437 438 - 439 439 === 2.4.4 Signal Strength === 440 440 441 441 ... ... @@ -468,7 +468,6 @@ 468 468 ))) 469 469 470 470 471 - 472 472 === 2.4.5 Distance === 473 473 474 474 ... ... @@ -488,10 +488,6 @@ 488 488 489 489 ))) 490 490 491 -((( 492 - 493 -))) 494 - 495 495 === 2.4.6 Digital Interrupt === 496 496 497 497 ... ... @@ -504,7 +504,7 @@ 504 504 ))) 505 505 506 506 ((( 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]])**.** 549 +(% 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]])**.** 508 508 ))) 509 509 510 510 ... ... @@ -526,7 +526,6 @@ 526 526 ))) 527 527 528 528 529 - 530 530 === 2.4.7 +5V Output === 531 531 532 532 ... ... @@ -537,10 +537,14 @@ 537 537 538 538 ((( 539 539 The 5V output time can be controlled by AT Command. 581 + 582 + 540 540 ))) 541 541 542 542 ((( 543 543 (% style="color:blue" %)**AT+5VT=1000** 587 + 588 + 544 544 ))) 545 545 546 546 ((( ... ... @@ -548,7 +548,6 @@ 548 548 ))) 549 549 550 550 551 - 552 552 == 2.5 Downlink Payload == 553 553 554 554 ... ... @@ -601,126 +601,85 @@ 601 601 ))) 602 602 603 603 648 +== 2.6 Distance alarm function(Since firmware v1.3.2) == 604 604 605 -== 2.6 LED Indicator == 606 606 651 +(% style="color:blue" %)** ➢ AT Command:** 607 607 608 - TheNDDS75 hasan internalLED which is toshowthestatusof different state.653 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max** 609 609 655 +² When min=0, and max≠0, Alarm higher than max 610 610 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. 657 +² When min≠0, and max=0, Alarm lower than min 615 615 616 -((( 617 - 618 -))) 659 +² When min≠0 and max≠0, Alarm higher than max or lower than min 619 619 620 620 662 +(% style="color:blue" %)** Example:** 621 621 622 - ==2.7FirmwareChangeLog==664 +**AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 623 623 624 624 625 -((( 626 -Download URL & Firmware Change log 627 -))) 667 +== 2.7 Set the number of data to be uploaded and the recording time == 628 628 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 -))) 632 632 670 +(% style="color:blue" %)** ➢ AT Command:** 633 633 634 -((( 635 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 636 -))) 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. 637 637 675 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 638 638 677 +[[image:image-20221009001114-1.png||height="687" width="955"]] 639 639 640 -== 2.8 Battery Analysis == 641 641 642 -== =2.8.1BatteryType ===680 +== 2.8 Read or Clear cached data == 643 643 644 644 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 -))) 683 +(% style="color:blue" %)** ➢ AT Command:** 648 648 649 -((( 650 -The battery is designed to last for several years depends on the actually use environment and update interval. 651 -))) 685 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 686 +* (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 652 652 653 -((( 654 -The battery related documents as below: 655 -))) 688 +[[image:image-20220908175333-2.png]] 656 656 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/]] 660 660 661 -((( 662 -[[image:image-20220709101450-2.png]] 663 -))) 691 +== 2.9 LED Indicator == 664 664 665 665 694 +The NDDS75 has an internal LED which is to show the status of different state. 666 666 667 -=== 2.8.2 Power consumption Analyze === 668 668 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. 669 669 670 670 ((( 671 - Draginobattery 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.703 + 672 672 ))) 673 673 674 674 675 -((( 676 -Instruction to use as below: 677 -))) 707 +== 2.10 Firmware Change Log == 678 678 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 -))) 682 682 683 - 684 684 ((( 685 - (% style="color:blue"%)**Step2:**(%%) Openitchoose711 +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]] 686 686 ))) 687 687 688 -* ((( 689 -Product Model 690 -))) 691 -* ((( 692 -Uplink Interval 693 -))) 694 -* ((( 695 -Working Mode 696 -))) 697 - 698 698 ((( 699 - AndtheLife expectationin difference casewill beshownontheright.715 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 700 700 ))) 701 701 702 -[[image:image-20220709110451-3.png]] 703 703 719 +== 2.11 Battery & Power Consumption == 704 704 705 705 706 - ===2.8.3BatteryNote===722 +NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 707 707 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/]] . 708 708 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 -))) 712 712 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 - 724 724 = 3. Access NB-IoT Module = 725 725 726 726 ... ... @@ -730,91 +730,107 @@ 730 730 731 731 ((( 732 732 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 + 733 733 ))) 734 734 735 735 [[image:1657333200519-600.png]] 736 736 737 737 738 - 739 739 = 4. Using the AT Commands = 740 740 741 741 == 4.1 Access AT Commands == 742 742 743 743 744 -See this link for detail: [[https:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]748 +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]] 745 745 746 746 747 -AT+<CMD>? : Help on <CMD> 751 +AT+<CMD>? : Help on <CMD> 748 748 749 -AT+<CMD> : Run <CMD> 753 +AT+<CMD> : Run <CMD> 750 750 751 -AT+<CMD>=<value> : Set the value 755 +AT+<CMD>=<value> : Set the value 752 752 753 -AT+<CMD>=? : Get the value 757 +AT+<CMD>=? : Get the value 754 754 755 755 756 756 (% style="color:#037691" %)**General Commands**(%%) 757 757 758 -AT : Attention 762 +AT : Attention 759 759 760 -AT? : Short Help 764 +AT? : Short Help 761 761 762 -ATZ : MCU Reset 766 +ATZ : MCU Reset 763 763 764 -AT+TDC : Application Data Transmission Interval 768 +AT+TDC : Application Data Transmission Interval 765 765 766 -AT+CFG : Print all configurations 770 +AT+CFG : Print all configurations 767 767 768 -AT+CFGMOD : Working mode selection 772 +AT+CFGMOD : Working mode selection 769 769 770 -AT+INTMOD : Set the trigger interrupt mode 774 +AT+INTMOD : Set the trigger interrupt mode 771 771 772 -AT+5VT : Set extend the time of 5V power 776 +AT+5VT : Set extend the time of 5V power 773 773 774 -AT+PRO : Choose agreement 778 +AT+PRO : Choose agreement 775 775 776 -AT+WEIGRE : Get weight or set weight to 0 780 +AT+WEIGRE : Get weight or set weight to 0 777 777 778 -AT+WEIGAP : Get or Set the GapValue of weight 782 +AT+WEIGAP : Get or Set the GapValue of weight 779 779 780 -AT+RXDL : Extend the sending and receiving time 784 +AT+RXDL : Extend the sending and receiving time 781 781 782 -AT+CNTFAC : Get or set counting parameters 786 +AT+CNTFAC : Get or set counting parameters 783 783 784 -AT+SERVADDR 788 +AT+SERVADDR : Server Address 785 785 790 +AT+TR : Get or Set record time" 786 786 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 + 787 787 (% style="color:#037691" %)**COAP Management** 788 788 789 -AT+URI : Resource parameters 809 +AT+URI : Resource parameters 790 790 791 791 792 792 (% style="color:#037691" %)**UDP Management** 793 793 794 -AT+CFM : Upload confirmation mode (only valid for UDP) 814 +AT+CFM : Upload confirmation mode (only valid for UDP) 795 795 796 796 797 797 (% style="color:#037691" %)**MQTT Management** 798 798 799 -AT+CLIENT 819 +AT+CLIENT : Get or Set MQTT client 800 800 801 -AT+UNAME 821 +AT+UNAME : Get or Set MQTT Username 802 802 803 -AT+PWD 823 +AT+PWD : Get or Set MQTT password 804 804 805 -AT+PUBTOPIC 825 +AT+PUBTOPIC : Get or Set MQTT publish topic 806 806 807 -AT+SUBTOPIC 827 +AT+SUBTOPIC : Get or Set MQTT subscription topic 808 808 809 809 810 810 (% style="color:#037691" %)**Information** 811 811 812 -AT+FDR : Factory Data Reset 832 +AT+FDR : Factory Data Reset 813 813 814 -AT+PWORD : Serial Access Password 834 +AT+PWORD : Serial Access Password 815 815 816 816 817 - 818 818 = 5. FAQ = 819 819 820 820 == 5.1 How to Upgrade Firmware == ... ... @@ -833,7 +833,6 @@ 833 833 ))) 834 834 835 835 836 - 837 837 = 6. Trouble Shooting = 838 838 839 839 == 6.1 Connection problem when uploading firmware == ... ... @@ -848,14 +848,11 @@ 848 848 849 849 ))) 850 850 851 - 852 852 == 6.2 AT Command input doesn't work == 853 853 854 854 855 855 ((( 856 856 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 - 859 859 ))) 860 860 861 861 ... ... @@ -865,11 +865,6 @@ 865 865 Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 866 866 867 867 868 -(% class="wikigeneratedid" %) 869 -((( 870 - 871 -))) 872 - 873 873 = 8. Packing Info = 874 874 875 875 ((( ... ... @@ -895,7 +895,6 @@ 895 895 ((( 896 896 897 897 898 - 899 899 900 900 ))) 901 901
- 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
- image-20221009001114-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +282.9 KB - Content