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, 7 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -9,6 +9,7 @@ 9 9 10 10 **Table of Contents:** 11 11 12 +{{toc/}} 12 12 13 13 14 14 ... ... @@ -21,16 +21,29 @@ 21 21 ((( 22 22 23 23 25 +((( 24 24 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 +))) 25 25 29 +((( 26 26 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 +))) 27 27 33 +((( 28 28 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 35 +))) 29 29 37 +((( 30 30 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 +))) 31 31 41 +((( 42 + 43 +))) 32 32 45 +((( 33 33 ~* make sure you have NB-IoT coverage locally. 47 +))) 34 34 35 35 36 36 ))) ... ... @@ -41,7 +41,6 @@ 41 41 42 42 == 1.2 Features == 43 43 44 - 45 45 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 46 46 * Monitor Temperature & Humidity via SHT31 47 47 * AT Commands to change parameters ... ... @@ -55,6 +55,7 @@ 55 55 56 56 57 57 71 + 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -63,6 +63,7 @@ 63 63 * Supply Voltage: 2.1v ~~ 3.6v 64 64 * Operating Temperature: -40 ~~ 85°C 65 65 80 + 66 66 (% style="color:#037691" %)**NB-IoT Spec:** 67 67 68 68 * - B1 @H-FDD: 2100MHz ... ... @@ -72,9 +72,9 @@ 72 72 * - B20 @H-FDD: 800MHz 73 73 * - B28 @H-FDD: 700MHz 74 74 90 + 75 75 (% style="color:#037691" %)**Battery:** 76 76 77 - 78 78 * Li/SOCI2 un-chargeable battery 79 79 * Capacity: 8500mAh 80 80 * Self Discharge: <1% / Year @ 25°C ... ... @@ -83,6 +83,7 @@ 83 83 84 84 85 85 101 + 86 86 == 1.4 Applications == 87 87 88 88 * Smart Buildings & Home Automation ... ... @@ -111,9 +111,13 @@ 111 111 112 112 === 1.5.2 BOOT MODE / SW1 === 113 113 130 +((( 114 114 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 +))) 115 115 134 +((( 116 116 2) Flash: work mode, device starts to work and send out console output for further debug 136 +))) 117 117 118 118 119 119 ... ... @@ -170,24 +170,45 @@ 170 170 === 2.2.1 Test Requirement === 171 171 172 172 193 +((( 173 173 To use N95S31B in your city, make sure meet below requirements: 195 +))) 174 174 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. 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 +))) 178 178 179 - 207 +((( 180 180 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 209 +))) 181 181 211 +((( 182 182 N95S31B supports different communication protocol such as : 213 +))) 183 183 184 184 ((( 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(%%)) 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 +))) 189 189 229 +((( 190 190 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 +))) 191 191 192 192 193 193 ))) ... ... @@ -293,15 +293,16 @@ 293 293 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 294 294 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 295 295 296 -[[image:16573 30501006-241.png]]337 +[[image:1657352391268-297.png]] 297 297 298 298 299 -[[image:16573 30533775-472.png]]340 +[[image:1657352403317-397.png]] 300 300 301 301 302 302 303 -=== 2.2. 6344 +=== 2.2.7 Use MQTT protocol to uplink data === 304 304 346 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 305 305 306 306 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 307 307 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -308,35 +308,40 @@ 308 308 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 309 309 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 310 310 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 311 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB**(%%)~/~/Set the sending topic of MQTT312 -* (% style="color:blue" %)**AT+SUBTOPIC=N DDS75_SUB**(%%) ~/~/Set the subscription topic of MQTT353 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 354 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 313 313 314 -[[image:165724 9978444-674.png]]356 +[[image:1657352634421-276.png]] 315 315 316 316 317 -[[image:16573 30723006-866.png]]359 +[[image:1657352645687-385.png]] 318 318 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 +))) 319 319 365 + 320 320 ((( 321 -MQTT protocol has a much high erpower consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.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. 322 322 ))) 323 323 324 324 325 325 326 -=== 2.2. 7372 +=== 2.2.8 Use TCP protocol to uplink data === 327 327 374 +This feature is supported since firmware version v110 328 328 329 329 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 330 330 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 331 331 332 -[[image: image-20220709093918-1.png]]379 +[[image:1657352898400-901.png]] 333 333 334 334 335 -[[image: image-20220709093918-2.png]]382 +[[image:1657352914475-252.png]] 336 336 337 337 338 338 339 -=== 2.2. 8386 +=== 2.2.9 Change Update Interval === 340 340 341 341 User can use below command to change the (% style="color:green" %)**uplink interval**. 342 342 ... ... @@ -343,227 +343,227 @@ 343 343 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 344 344 345 345 ((( 346 - (%style="color:red" %)**NOTE:**393 + 347 347 ))) 348 348 349 -((( 350 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 351 -))) 352 352 353 353 354 - 355 355 == 2.3 Uplink Payload == 356 356 357 -In this mode, uplink payload includes in total 14 bytes 358 358 401 +((( 402 +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. 403 +))) 359 359 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"]] 365 365 366 366 ((( 367 - If we use the MQTT client tosubscribeto this MQTT topic, wecan see the following information when the NDDS751 uplink data.407 +For example: 368 368 ))) 369 369 410 +((( 411 + (% 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. 412 +))) 370 370 371 -[[image:1657331036973-987.png]] 372 372 373 373 ((( 374 -The payload is ASCIIstring,representative sameHEX:416 +The uplink payloads are composed in ASCII String. For example: 375 375 ))) 376 376 377 377 ((( 378 -0 x72403155615900640c6c19029200where:420 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 379 379 ))) 380 380 381 - *(((382 - DeviceID:0x724031556159=724031556159423 +((( 424 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 383 383 ))) 384 -* ((( 385 -Version: 0x0064=100=1.0.0 426 + 427 + 428 +((( 429 +(% style="color:red" %)**NOTE:** 386 386 ))) 387 387 388 -* ((( 389 -BAT: 0x0c6c = 3180 mV = 3.180V 432 +(% style="color:red" %) 433 +1. ((( 434 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 390 390 ))) 391 - *(((392 - Signal:0x19=25436 +1. ((( 437 +By default, the device will send an uplink message every 1 hour. 393 393 ))) 394 -* ((( 395 -Distance: 0x0292= 658 mm 396 -))) 397 -* ((( 398 -Interrupt: 0x00 = 0 399 399 400 400 401 401 402 - 403 -))) 404 404 405 -== 2. 4PayloadExplanation and SensorInterface==443 +=== 2.3.1 Payload Analyze === 406 406 445 +N95S31B uplink payload includes in total 21 bytes 407 407 408 -=== 2.4.1 Device ID === 409 409 448 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 449 +|=(% style="width: 60px;" %)((( 450 +**Size(bytes)** 451 +)))|=(% 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** 452 +|(% 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" %)((( 410 410 ((( 411 - By default, theDeviceID equal to thelast6bytes of IMEI.454 +Reserve/ Same as NBSN95 CFGMOD=1 412 412 ))) 413 413 414 414 ((( 415 - Usercanuse (% style="color:blue" %)**AT+DEUI**(%%)toset Device ID458 +No function here. 416 416 ))) 417 - 460 +)))|(% style="width:77px" %)((( 418 418 ((( 419 - **Example:**462 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 420 420 ))) 421 421 422 422 ((( 423 - AT+DEUI=A84041F15612466 +By SHT31 424 424 ))) 425 - 468 +)))|(% style="width:80px" %)((( 426 426 ((( 427 - The Device ID is storednane-erasearea, Upgradethe firmwareor run **AT+FDR** won'terase Device ID.470 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 428 428 ))) 429 429 430 - 431 - 432 -=== 2.4.2 Version Info === 433 - 434 434 ((( 435 - Specifythe software version: 0x64=100, means firmware version 1.00.474 +By SHT31 436 436 ))) 476 +))) 437 437 438 438 ((( 439 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 479 +((( 480 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 440 440 ))) 482 +))) 441 441 442 442 485 +[[image:1657354294009-643.png]] 443 443 444 -=== 2.4.3 Battery Info === 445 445 488 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 489 + 490 +* Device ID: 0x724031607457 = 724031607457 491 +* Version: 0x006e=110=1.1.0 492 + 493 +* BAT: 0x0ccd = 3277 mV = 3.277V 494 +* Signal: 0x1b = 27 495 +* Model: 0x01 = 1 496 +* 0x00dc000ccc= reserve, ignore in N95S31B 497 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 498 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 499 + 446 446 ((( 447 - Ex1:0x0B45 = 2885mV501 + 448 448 ))) 449 449 450 450 ((( 451 - Ex2:0x0B49 = 2889mV505 + 452 452 ))) 453 453 454 454 509 +=== 2.3.2 Device ID === 455 455 456 -=== 2.4.4 Signal Strength === 457 - 458 458 ((( 459 - NB-IoTNetworksignalStrength.512 +By default, the Device ID equal to the last 6 bytes of IMEI. 460 460 ))) 461 461 462 462 ((( 463 - **Ex1:0x1d=29**516 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 464 464 ))) 465 465 466 466 ((( 467 - (% style="color:blue" %)**0**(%%) -113dBmorless520 +**Example:** 468 468 ))) 469 469 470 470 ((( 471 - (% style="color:blue" %)**1**(%%) -111dBm524 +AT+DEUI=A84041F15612 472 472 ))) 473 473 474 474 ((( 475 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm528 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 476 476 ))) 477 477 478 -((( 479 -(% style="color:blue" %)**31** (%%) -51dBm or greater 480 -))) 481 481 482 -((( 483 -(% style="color:blue" %)**99** (%%) Not known or not detectable 484 -))) 485 485 533 +=== 2.3.3 Version Info === 486 486 487 487 488 - ===2.4.5Distance===536 +These bytes include the hardware and software version. 489 489 490 - Get thedistance.Flat objectrange280mm-7500mm.538 +Higher byte: Specify hardware version: always 0x00 for N95S31B 491 491 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 -))) 540 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 495 495 542 + 543 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 544 + 496 496 ((( 497 -((( 498 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 546 + 499 499 ))) 500 -))) 501 501 549 + 550 +=== 2.3.4 Battery Info === 551 + 502 502 ((( 503 - 553 +Ex1: 0x0B45 = 2885mV 504 504 ))) 505 505 506 506 ((( 507 - 557 +Ex2: 0x0B49 = 2889mV 508 508 ))) 509 509 510 -=== 2.4.6 Digital Interrupt === 511 511 561 + 562 +=== 2.3.5 Signal Strength === 563 + 512 512 ((( 513 - DigitalInterrupt refers topin (% style="color:blue" %)**GPIO_EXTI**(%%),and there are differenttrigger methods. When thereisa trigger, the NDDS75 will sendapacketto the server.565 +NB-IoT Network signal Strength. 514 514 ))) 515 515 516 516 ((( 517 - Thecommandis:569 +**Ex1: 0x1d = 29** 518 518 ))) 519 519 520 520 ((( 521 -(% style="color:blue" %)** AT+INTMOD=3**(%%)~/~/(moreinfoaboutINMODpleaserefer[[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**573 +(% style="color:blue" %)**0**(%%) -113dBm or less 522 522 ))) 523 523 524 - 525 525 ((( 526 - Thelower four bitsofthis data field shows if this packet is generatedby interruptornot.Clickhereforthehardwareandsoftware set up.577 +(% style="color:blue" %)**1**(%%) -111dBm 527 527 ))) 528 528 529 - 530 530 ((( 531 - Example:581 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 532 532 ))) 533 533 534 534 ((( 535 - 0x(00):Normalplinkpacket.585 +(% style="color:blue" %)**31** (%%) -51dBm or greater 536 536 ))) 537 537 538 538 ((( 539 - 0x(01):InterruptUplinkPacket.589 +(% style="color:blue" %)**99** (%%) Not known or not detectable 540 540 ))) 541 541 542 542 543 543 544 -=== 2. 4.7+5VOutput===594 +=== 2.3.6 Temperature & Humidity === 545 545 546 -((( 547 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 548 -))) 596 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 549 549 598 +[[image:image-20220709161741-3.png]] 550 550 551 -((( 552 -The 5V output time can be controlled by AT Command. 553 -))) 554 554 555 -((( 556 -(% style="color:blue" %)**AT+5VT=1000** 557 -))) 601 +Convert the read byte to decimal and divide it by ten. 558 558 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 -))) 562 562 604 +**Example:** 563 563 606 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 564 564 565 - ==2.5Downlink Payload==608 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 566 566 610 + 611 + 612 +== 2.4 Downlink Payload == 613 + 567 567 By default, NDDS75 prints the downlink payload to console port. 568 568 569 569 [[image:image-20220709100028-1.png]] ... ... @@ -614,51 +614,16 @@ 614 614 615 615 616 616 617 -== 2. 6LED Indicator ==664 +== 2.5 Battery Analysis == 618 618 666 +=== 2.5.1 Battery Type === 619 619 620 -The NDDS75 has an internal LED which is to show the status of different state. 621 621 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 - 628 628 ((( 629 - 670 +The N95S31B 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. 630 630 ))) 631 631 632 - 633 - 634 -== 2.7 Firmware Change Log == 635 - 636 - 637 637 ((( 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 -((( 662 662 The battery is designed to last for several years depends on the actually use environment and update interval. 663 663 ))) 664 664 ... ... @@ -676,56 +676,35 @@ 676 676 677 677 678 678 679 -=== 2. 8.2 Power consumption Analyze ===691 +=== 2.5.2 Power consumption Analyze === 680 680 681 681 ((( 682 - Draginobatterypoweredproductareall runsinLow Powermode.Wehave an update battery calculatorwhichbaseonthe measurement oftherealdevice. User can usethis calculatortocheck the batterylifeandcalculatethe batterylifeifwant tousedifferenttransmit interval.694 +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/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project. 683 683 ))) 684 684 685 - 686 686 ((( 687 - Instructionto use as below:698 + 688 688 ))) 689 689 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 -))) 693 693 702 +=== 2.5.3 Battery Note === 694 694 695 695 ((( 696 - (%style="color:blue"%)**Step2:**(%%)Open it andchoose705 +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 uplink data, then the battery life may be decreased. 697 697 ))) 698 698 699 -* ((( 700 -Product Model 701 -))) 702 -* ((( 703 -Uplink Interval 704 -))) 705 -* ((( 706 -Working Mode 707 -))) 708 708 709 -((( 710 -And the Life expectation in difference case will be shown on the right. 711 -))) 712 712 713 - [[image:image-20220709110451-3.png]]710 +=== 2.5.4 Replace the battery === 714 714 715 715 716 - 717 -=== 2.8.3 Battery Note === 718 - 719 719 ((( 720 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.714 +You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board. 721 721 ))) 722 722 723 723 724 - 725 -=== 2.8.4 Replace the battery === 726 - 727 727 ((( 728 -The default battery pack of N DDS75 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).719 +The default battery pack of N95S31B 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). 729 729 ))) 730 730 731 731 ... ... @@ -748,7 +748,7 @@ 748 748 749 749 == 4.1 Access AT Commands == 750 750 751 -See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N DDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]742 +See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]] 752 752 753 753 754 754 AT+<CMD>? : Help on <CMD> ... ... @@ -836,8 +836,12 @@ 836 836 ))) 837 837 838 838 ((( 839 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 830 + 831 + 832 +((( 833 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 840 840 ))) 835 +))) 841 841 842 842 843 843 ... ... @@ -868,7 +868,7 @@ 868 868 = 7. Order Info = 869 869 870 870 871 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**866 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 872 872 873 873 874 874 (% class="wikigeneratedid" %) ... ... @@ -883,7 +883,7 @@ 883 883 884 884 (% style="color:#037691" %)**Package Includes**: 885 885 886 -* NS E01DistanceDetectSensorNode x 1881 +* N95S31B NB-IoT Temperature and Humidity Sensor 887 887 * External antenna x 1 888 888 ))) 889 889 ... ... @@ -892,11 +892,10 @@ 892 892 893 893 (% style="color:#037691" %)**Dimension and weight**: 894 894 895 - 896 896 * Device Size: 13.0 x 5 x 4.5 cm 897 897 * Device Weight: 150g 898 -* Package Size / pcs : 1 5x12x 5.5cm899 -* Weight / pcs : 220g892 +* Package Size / pcs : 14.0 x 8x 5 cm 893 +* Weight / pcs : 180g 900 900 ))) 901 901 902 902 (((
- 1657352403317-397.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +547.7 KB - Content
- 1657352634421-276.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +163.6 KB - Content
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +144.8 KB - Content
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +157.0 KB - Content
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +214.7 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +111.2 KB - Content