Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 5 removed)
Details
- Page properties
-
- Content
-
... ... @@ -9,7 +9,6 @@ 9 9 10 10 **Table of Contents:** 11 11 12 -{{toc/}} 13 13 14 14 15 15 ... ... @@ -22,29 +22,16 @@ 22 22 ((( 23 23 24 24 25 -((( 26 26 The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*. 27 -))) 28 28 29 -((( 30 30 The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use. 31 -))) 32 32 33 -((( 34 34 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 35 -))) 36 36 37 -((( 38 38 N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report). 39 -))) 40 40 41 -((( 42 - 43 -))) 44 44 45 -((( 46 46 ~* make sure you have NB-IoT coverage locally. 47 -))) 48 48 49 49 50 50 ))) ... ... @@ -55,6 +55,7 @@ 55 55 56 56 == 1.2 Features == 57 57 44 + 58 58 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 59 59 * Monitor Temperature & Humidity via SHT31 60 60 * AT Commands to change parameters ... ... @@ -68,7 +68,6 @@ 68 68 69 69 70 70 71 - 72 72 == 1.3 Specification == 73 73 74 74 ... ... @@ -77,7 +77,6 @@ 77 77 * Supply Voltage: 2.1v ~~ 3.6v 78 78 * Operating Temperature: -40 ~~ 85°C 79 79 80 - 81 81 (% style="color:#037691" %)**NB-IoT Spec:** 82 82 83 83 * - B1 @H-FDD: 2100MHz ... ... @@ -87,9 +87,9 @@ 87 87 * - B20 @H-FDD: 800MHz 88 88 * - B28 @H-FDD: 700MHz 89 89 90 - 91 91 (% style="color:#037691" %)**Battery:** 92 92 77 + 93 93 * Li/SOCI2 un-chargeable battery 94 94 * Capacity: 8500mAh 95 95 * Self Discharge: <1% / Year @ 25°C ... ... @@ -98,7 +98,6 @@ 98 98 99 99 100 100 101 - 102 102 == 1.4 Applications == 103 103 104 104 * Smart Buildings & Home Automation ... ... @@ -127,13 +127,9 @@ 127 127 128 128 === 1.5.2 BOOT MODE / SW1 === 129 129 130 -((( 131 131 1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. 132 -))) 133 133 134 -((( 135 135 2) Flash: work mode, device starts to work and send out console output for further debug 136 -))) 137 137 138 138 139 139 ... ... @@ -190,45 +190,24 @@ 190 190 === 2.2.1 Test Requirement === 191 191 192 192 193 -((( 194 194 To use N95S31B in your city, make sure meet below requirements: 195 -))) 196 196 197 -* ((( 198 -Your local operator has already distributed a NB-IoT Network there. 199 -))) 200 -* ((( 201 -The local NB-IoT network used the band that N95S31B supports. 202 -))) 203 -* ((( 204 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 205 -))) 175 +* Your local operator has already distributed a NB-IoT Network there. 176 +* The local NB-IoT network used the band that N95S31B supports. 177 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 206 206 207 - (((179 + 208 208 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 209 -))) 210 210 211 -((( 212 212 N95S31B supports different communication protocol such as : 213 -))) 214 214 215 215 ((( 216 -* ((( 217 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 218 -))) 219 -* ((( 220 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 221 -))) 222 -* ((( 223 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 224 -))) 225 -* ((( 226 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 227 -))) 185 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 186 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 187 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 188 +* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 228 228 229 -((( 230 230 We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server. 231 -))) 232 232 233 233 234 234 ))) ... ... @@ -334,16 +334,15 @@ 334 334 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 335 335 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 336 336 337 -[[image:16573 52391268-297.png]]296 +[[image:1657330501006-241.png]] 338 338 339 339 340 -[[image:16573 52403317-397.png]]299 +[[image:1657330533775-472.png]] 341 341 342 342 343 343 344 -=== 2.2. 7Use MQTT protocol to uplink data ===303 +=== 2.2.6 Use MQTT protocol to uplink data === 345 345 346 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 347 347 348 348 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 349 349 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -350,40 +350,35 @@ 350 350 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 351 351 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 352 352 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 353 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527354 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)311 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 312 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 355 355 356 -[[image:1657 352634421-276.png]]314 +[[image:1657249978444-674.png]] 357 357 358 358 359 -[[image:16573 52645687-385.png]]317 +[[image:1657330723006-866.png]] 360 360 361 -((( 362 -To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period. 363 -))) 364 364 365 - 366 366 ((( 367 -MQTT protocol has a much high -power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.321 +MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 368 368 ))) 369 369 370 370 371 371 372 -=== 2.2. 8Use TCP protocol to uplink data ===326 +=== 2.2.7 Use TCP protocol to uplink data === 373 373 374 -This feature is supported since firmware version v110 375 375 376 376 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 377 377 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 378 378 379 -[[image: 1657352898400-901.png]]332 +[[image:image-20220709093918-1.png]] 380 380 381 381 382 -[[image: 1657352914475-252.png]]335 +[[image:image-20220709093918-2.png]] 383 383 384 384 385 385 386 -=== 2.2. 9Change Update Interval ===339 +=== 2.2.8 Change Update Interval === 387 387 388 388 User can use below command to change the (% style="color:green" %)**uplink interval**. 389 389 ... ... @@ -390,207 +390,227 @@ 390 390 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 391 391 392 392 ((( 393 - 346 +(% style="color:red" %)**NOTE:** 394 394 ))) 395 395 349 +((( 350 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 351 +))) 396 396 397 397 354 + 398 398 == 2.3 Uplink Payload == 399 399 357 +In this mode, uplink payload includes in total 14 bytes 400 400 401 -NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes. 402 402 360 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 361 +|=(% style="width: 60px;" %)((( 362 +**Size(bytes)** 363 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 364 +|(% 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"]] 403 403 404 -For example: 366 +((( 367 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 368 +))) 405 405 406 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 407 407 371 +[[image:1657331036973-987.png]] 408 408 409 -The uplink payloads are composed in ASCII String. For example: 373 +((( 374 +The payload is ASCII string, representative same HEX: 375 +))) 410 410 411 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 377 +((( 378 +0x72403155615900640c6c19029200 where: 379 +))) 412 412 413 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 381 +* ((( 382 +Device ID: 0x724031556159 = 724031556159 383 +))) 384 +* ((( 385 +Version: 0x0064=100=1.0.0 386 +))) 414 414 388 +* ((( 389 +BAT: 0x0c6c = 3180 mV = 3.180V 390 +))) 391 +* ((( 392 +Signal: 0x19 = 25 393 +))) 394 +* ((( 395 +Distance: 0x0292= 658 mm 396 +))) 397 +* ((( 398 +Interrupt: 0x00 = 0 415 415 416 -(% style="color:red" %)**NOTE:** 417 417 418 -(% style="color:red" %) 419 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 420 -1. By default, the device will send an uplink message every 1 hour. 421 421 402 + 403 +))) 422 422 423 -== =2.3.1PayloadAnalyze ===405 +== 2.4 Payload Explanation and Sensor Interface == 424 424 425 -N95S31B uplink payload includes in total 21 bytes 426 426 408 +=== 2.4.1 Device ID === 427 427 428 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 429 -|=(% style="width: 60px;" %)((( 430 -**Size(bytes)** 431 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2** 432 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)((( 433 433 ((( 434 - Reserve/Same asNBSN95CFGMOD=1411 +By default, the Device ID equal to the last 6 bytes of IMEI. 435 435 ))) 436 436 437 437 ((( 438 - Nofunctionhere.415 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 439 439 ))) 440 - )))|(% style="width:77px" %)(((417 + 441 441 ((( 442 - [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]419 +**Example:** 443 443 ))) 444 444 445 445 ((( 446 - By SHT31423 +AT+DEUI=A84041F15612 447 447 ))) 448 - )))|(% style="width:80px" %)(((425 + 449 449 ((( 450 - [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]427 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 451 451 ))) 452 452 430 + 431 + 432 +=== 2.4.2 Version Info === 433 + 453 453 ((( 454 - BySHT31435 +Specify the software version: 0x64=100, means firmware version 1.00. 455 455 ))) 456 -))) 457 457 458 458 ((( 459 -((( 460 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 439 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 461 461 ))) 462 -))) 463 463 464 464 465 -[[image:1657354294009-643.png]] 466 466 444 +=== 2.4.3 Battery Info === 467 467 468 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 469 - 470 -* Device ID: 0x724031607457 = 724031607457 471 -* Version: 0x006e=110=1.1.0 472 - 473 -* BAT: 0x0ccd = 3277 mV = 3.277V 474 -* Signal: 0x1b = 27 475 -* Model: 0x01 = 1 476 -* 0x00dc000ccc= reserve, ignore in N95S31B 477 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 478 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 479 - 480 480 ((( 481 - 447 +Ex1: 0x0B45 = 2885mV 482 482 ))) 483 483 484 484 ((( 485 - 451 +Ex2: 0x0B49 = 2889mV 486 486 ))) 487 487 488 488 489 -=== 2.3.2 Device ID === 490 490 456 +=== 2.4.4 Signal Strength === 457 + 491 491 ((( 492 -B ydefault,the Device ID equal to thelast6 bytes of IMEI.459 +NB-IoT Network signal Strength. 493 493 ))) 494 494 495 495 ((( 496 - User can use (% style="color:blue" %)**AT+DEUI**(%%)tosetDevice ID463 +**Ex1: 0x1d = 29** 497 497 ))) 498 498 499 499 ((( 500 - **Example:**467 +(% style="color:blue" %)**0**(%%) -113dBm or less 501 501 ))) 502 502 503 503 ((( 504 - AT+DEUI=A84041F15612471 +(% style="color:blue" %)**1**(%%) -111dBm 505 505 ))) 506 506 507 507 ((( 508 - TheDevice ID isstored in a none-erase area, Upgrade the firmwareorrun**AT+FDR**won't erase Device ID.475 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 509 509 ))) 510 510 478 +((( 479 +(% style="color:blue" %)**31** (%%) -51dBm or greater 480 +))) 511 511 482 +((( 483 +(% style="color:blue" %)**99** (%%) Not known or not detectable 484 +))) 512 512 513 -=== 2.3.3 Version Info === 514 514 515 515 516 - Thesebytesinclude the hardware andsoftwareversion.488 +=== 2.4.5 Distance === 517 517 518 - Higherbyte:Specifyhardwareversion: always0x00forN95S31B490 +Get the distance. Flat object range 280mm - 7500mm. 519 519 520 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110 492 +((( 493 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 494 +))) 521 521 522 - 523 -For example: 0x00 6E: this device is N95S31B with firmware version 110. 524 - 525 525 ((( 526 - 497 +((( 498 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 527 527 ))) 500 +))) 528 528 529 - 530 -=== 2.3.4 Battery Info === 531 - 532 532 ((( 533 - Ex1:0x0B45 = 2885mV503 + 534 534 ))) 535 535 536 536 ((( 537 - Ex2:0x0B49 = 2889mV507 + 538 538 ))) 539 539 510 +=== 2.4.6 Digital Interrupt === 540 540 541 - 542 -=== 2.3.5 Signal Strength === 543 - 544 544 ((( 545 - NB-IoTNetworksignalStrength.513 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server. 546 546 ))) 547 547 548 548 ((( 549 - **Ex1:0x1d= 29**517 +The command is: 550 550 ))) 551 551 552 552 ((( 553 -(% style="color:blue" %)** 0**(%%)-113dBmor less521 +(% 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]])**.** 554 554 ))) 555 555 524 + 556 556 ((( 557 - (%style="color:blue"%)**1**(%%)-111dBm526 +The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up. 558 558 ))) 559 559 529 + 560 560 ((( 561 - (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm531 +Example: 562 562 ))) 563 563 564 564 ((( 565 -( %style="color:blue"%)**31** (%%) -51dBm or greater535 +0x(00): Normal uplink packet. 566 566 ))) 567 567 568 568 ((( 569 -( %style="color:blue" %)**99** (%%) Notknownor not detectable539 +0x(01): Interrupt Uplink Packet. 570 570 ))) 571 571 572 572 573 573 574 -=== 2. 3.6Temperature& Humidity===544 +=== 2.4.7 +5V Output === 575 575 576 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 546 +((( 547 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 548 +))) 577 577 578 -[[image:image-20220709161741-3.png]] 579 579 551 +((( 552 +The 5V output time can be controlled by AT Command. 553 +))) 580 580 581 -Convert the read byte to decimal and divide it by ten. 555 +((( 556 +(% style="color:blue" %)**AT+5VT=1000** 557 +))) 582 582 559 +((( 560 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 561 +))) 583 583 584 -**Example:** 585 585 586 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 587 587 588 - Humidity:Read:0295(H)=661(D)Value:661 / 10=66.1, So66.1%565 +== 2.5 Downlink Payload == 589 589 590 - 591 - 592 -== 2.4 Downlink Payload == 593 - 594 594 By default, NDDS75 prints the downlink payload to console port. 595 595 596 596 [[image:image-20220709100028-1.png]] ... ... @@ -641,16 +641,51 @@ 641 641 642 642 643 643 644 -== 2. 5BatteryAnalysis==617 +== 2.6 LED Indicator == 645 645 646 -=== 2.5.1 Battery Type === 647 647 620 +The NDDS75 has an internal LED which is to show the status of different state. 648 648 622 + 623 +* 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) 624 +* Then the LED will be on for 1 second means device is boot normally. 625 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 626 +* For each uplink probe, LED will be on for 500ms. 627 + 649 649 ((( 650 - TheN95S31B 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 + 651 651 ))) 652 652 632 + 633 + 634 +== 2.7 Firmware Change Log == 635 + 636 + 653 653 ((( 638 +Download URL & Firmware Change log 639 +))) 640 + 641 +((( 642 +[[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/]] 643 +))) 644 + 645 + 646 +((( 647 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 648 +))) 649 + 650 + 651 + 652 +== 2.8 Battery Analysis == 653 + 654 +=== 2.8.1 Battery Type === 655 + 656 + 657 +((( 658 +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. 659 +))) 660 + 661 +((( 654 654 The battery is designed to last for several years depends on the actually use environment and update interval. 655 655 ))) 656 656 ... ... @@ -668,35 +668,56 @@ 668 668 669 669 670 670 671 -=== 2. 5.2 Power consumption Analyze ===679 +=== 2.8.2 Power consumption Analyze === 672 672 673 673 ((( 674 - The file**DRAGINO_N95S31B-Power-Analyzer.pdf**from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describesadetailmeasurementtoanalyzethepowerconsumption indifferentcase. User can useitfordesignguideline fortheirproject.682 +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. 675 675 ))) 676 676 685 + 677 677 ((( 678 - 687 +Instruction to use as below: 679 679 ))) 680 680 690 +((( 691 +(% 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/]] 692 +))) 681 681 682 -=== 2.5.3 Battery Note === 683 683 684 684 ((( 685 - TheLi-SICO batteryis designed for small current / long period application. It is not good tousea high current, short periodtransmitmethod.Therecommendedminimum period for use ofthisbattery is 5 minutes.If you use a shorter period time to uplink data, then the battery life may be decreased.696 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 686 686 ))) 687 687 699 +* ((( 700 +Product Model 701 +))) 702 +* ((( 703 +Uplink Interval 704 +))) 705 +* ((( 706 +Working Mode 707 +))) 688 688 709 +((( 710 +And the Life expectation in difference case will be shown on the right. 711 +))) 689 689 690 - === 2.5.4 Replacethe battery ===713 +[[image:image-20220709110451-3.png]] 691 691 692 692 716 + 717 +=== 2.8.3 Battery Note === 718 + 693 693 ((( 694 - You can changethebattery intheN95S31B.Thetype ofbatteryis notlimitedaslongas theutput isbetween3vto3.6v.Onthemainboard,there isa diode(D1)betweenthebatteryandthemaincircuit. If youneed touse abatterywith less than 3.3v,pleaseremove the D1 andshortcut the twopadsofitso there won'tbe voltagedropbetween batteryandmainboard.720 +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. 695 695 ))) 696 696 697 697 724 + 725 +=== 2.8.4 Replace the battery === 726 + 698 698 ((( 699 -The default battery pack of N 95S31Bincludes 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).728 +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). 700 700 ))) 701 701 702 702 ... ... @@ -719,7 +719,7 @@ 719 719 720 720 == 4.1 Access AT Commands == 721 721 722 -See NBSN95 AT Command inthis link for detail:BSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]751 +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/]] 723 723 724 724 725 725 AT+<CMD>? : Help on <CMD> ... ... @@ -807,9 +807,7 @@ 807 807 ))) 808 808 809 809 ((( 810 - 811 - 812 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 839 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 813 813 ))) 814 814 815 815 ... ... @@ -841,7 +841,7 @@ 841 841 = 7. Order Info = 842 842 843 843 844 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**871 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 845 845 846 846 847 847 (% class="wikigeneratedid" %) ... ... @@ -856,7 +856,7 @@ 856 856 857 857 (% style="color:#037691" %)**Package Includes**: 858 858 859 -* N 95S31BNB-IoTTemperatureandHumiditySensor886 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 860 860 * External antenna x 1 861 861 ))) 862 862 ... ... @@ -865,10 +865,11 @@ 865 865 866 866 (% style="color:#037691" %)**Dimension and weight**: 867 867 895 + 868 868 * Device Size: 13.0 x 5 x 4.5 cm 869 869 * Device Weight: 150g 870 -* Package Size / pcs : 1 4.0x8x 5 cm871 -* Weight / pcs : 180g898 +* Package Size / pcs : 15 x 12x 5.5 cm 899 +* Weight / pcs : 220g 872 872 ))) 873 873 874 874 (((
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -144.8 KB - Content
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -157.0 KB - Content
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.2 KB - Content