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, 4 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 ... ... @@ -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 ... ... @@ -54,7 +54,6 @@ 54 54 * 8500mAh Battery for long term use 55 55 56 56 57 - 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -82,7 +82,6 @@ 82 82 * Max boost current: 2A, 1 second 83 83 84 84 85 - 86 86 == 1.4 Applications == 87 87 88 88 * Smart Buildings & Home Automation ... ... @@ -130,9 +130,6 @@ 130 130 1. When boot the device in flash mode 131 131 1. Send an uplink packet 132 132 133 - 134 - 135 - 136 136 = 2. Use N95S31B to communicate with IoT Server = 137 137 138 138 == 2.1 How it works == ... ... @@ -176,7 +176,6 @@ 176 176 * The local NB-IoT network used the band that N95S31B supports. 177 177 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 178 178 179 - 180 180 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 181 181 182 182 N95S31B supports different communication protocol such as : ... ... @@ -302,7 +302,7 @@ 302 302 303 303 === 2.2.7 Use MQTT protocol to uplink data === 304 304 305 -N95S31B supports only plain MQTT now it doesn ’t support TLS and other related encryption.299 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 306 306 307 307 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 308 308 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -309,8 +309,8 @@ 309 309 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 310 310 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 311 311 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 312 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 313 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 306 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 307 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 314 314 315 315 [[image:1657352634421-276.png]] 316 316 ... ... @@ -328,20 +328,21 @@ 328 328 329 329 330 330 331 -=== 2.2. 7325 +=== 2.2.8 Use TCP protocol to uplink data === 332 332 327 +This feature is supported since firmware version v110 333 333 334 334 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 335 335 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 336 336 337 -[[image: image-20220709093918-1.png]]332 +[[image:1657352898400-901.png]] 338 338 339 339 340 -[[image: image-20220709093918-2.png]]335 +[[image:1657352914475-252.png]] 341 341 342 342 343 343 344 -=== 2.2. 8339 +=== 2.2.9 Change Update Interval === 345 345 346 346 User can use below command to change the (% style="color:green" %)**uplink interval**. 347 347 ... ... @@ -348,69 +348,90 @@ 348 348 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 349 349 350 350 ((( 351 - (%style="color:red" %)**NOTE:**346 + 352 352 ))) 353 353 354 -((( 355 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 356 -))) 357 357 358 358 359 - 360 360 == 2.3 Uplink Payload == 361 361 362 -In this mode, uplink payload includes in total 14 bytes 363 363 354 +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. 364 364 365 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 356 + 357 +For example: 358 + 359 + (% 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. 360 + 361 + 362 +The uplink payloads are composed in ASCII String. For example: 363 + 364 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 365 + 366 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 367 + 368 + 369 +(% style="color:red" %)**NOTE:** 370 + 371 +(% style="color:red" %) 372 +1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 373 +1. By default, the device will send an uplink message every 1 hour. 374 + 375 +=== 2.3.1 Payload Analyze === 376 + 377 +N95S31B uplink payload includes in total 21 bytes 378 + 379 + 380 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 366 366 |=(% style="width: 60px;" %)((( 367 367 **Size(bytes)** 368 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 369 -|(% 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"]] 383 +)))|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2** 384 +|(% 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" %)((( 385 +Reserve/ Same as NBSN95 CFGMOD=1 370 370 371 - (((372 - Ifwe usethe MQTT client to subscribe to this MQTT topic,we can see the following information when the NDDS751 uplinkdata.373 - )))387 +No function here. 388 +)))|(% style="width:77px" %)((( 389 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 374 374 391 +By SHT31 392 +)))|(% style="width:80px" %)((( 393 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 375 375 376 -[[image:1657331036973-987.png]] 377 - 378 -((( 379 -The payload is ASCII string, representative same HEX: 395 +By SHT31 380 380 ))) 381 381 382 382 ((( 383 -0x72403155615900640c6c19029200 where: 399 +((( 400 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 384 384 ))) 385 - 386 -* ((( 387 -Device ID: 0x724031556159 = 724031556159 388 388 ))) 389 -* ((( 390 -Version: 0x0064=100=1.0.0 391 -))) 392 392 393 -* ((( 394 -BAT: 0x0c6c = 3180 mV = 3.180V 395 -))) 396 -* ((( 397 -Signal: 0x19 = 25 398 -))) 399 -* ((( 400 -Distance: 0x0292= 658 mm 401 -))) 402 -* ((( 403 -Interrupt: 0x00 = 0 404 404 405 +[[image:1657354294009-643.png]] 405 405 406 406 408 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 409 + 410 +* Device ID: 0x724031607457 = 724031607457 411 +* Version: 0x006e=110=1.1.0 412 + 413 +* BAT: 0x0ccd = 3277 mV = 3.277V 414 +* Signal: 0x1b = 27 415 +* Model: 0x01 = 1 416 +* 0x00dc000ccc= reserve, ignore in N95S31B 417 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 418 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 419 + 420 +((( 407 407 408 408 ))) 409 409 410 -== 2.4 Payload Explanation and Sensor Interface == 424 +((( 425 + 426 +))) 411 411 412 412 413 -=== 2. 4.1429 +=== 2.3.2 Device ID === 414 414 415 415 ((( 416 416 By default, the Device ID equal to the last 6 bytes of IMEI. ... ... @@ -434,20 +434,25 @@ 434 434 435 435 436 436 437 -=== 2. 4.2Version Info ===453 +=== 2.3.3 Version Info === 438 438 439 -((( 440 -Specify the software version: 0x64=100, means firmware version 1.00. 441 -))) 442 442 456 +These bytes include the hardware and software version. 457 + 458 +Higher byte: Specify hardware version: always 0x00 for N95S31B 459 + 460 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 461 + 462 + 463 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 464 + 443 443 ((( 444 - Forexample: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.466 + 445 445 ))) 446 446 447 447 470 +=== 2.3.4 Battery Info === 448 448 449 -=== 2.4.3 Battery Info === 450 - 451 451 ((( 452 452 Ex1: 0x0B45 = 2885mV 453 453 ))) ... ... @@ -458,7 +458,7 @@ 458 458 459 459 460 460 461 -=== 2. 4.4Signal Strength ===482 +=== 2.3.5 Signal Strength === 462 462 463 463 ((( 464 464 NB-IoT Network signal Strength. ... ... @@ -490,85 +490,26 @@ 490 490 491 491 492 492 493 -=== 2. 4.5Distance ===514 +=== 2.3.6 Temperature & Humidity === 494 494 495 - Get the distance.Flatobject range280mm-7500mm.516 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 496 496 497 -((( 498 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 499 -))) 518 +[[image:image-20220709161741-3.png]] 500 500 501 -((( 502 -((( 503 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 504 -))) 505 -))) 506 506 507 -((( 508 - 509 -))) 521 +Convert the read byte to decimal and divide it by ten. 510 510 511 -((( 512 - 513 -))) 514 514 515 - === 2.4.6 DigitalInterrupt ===524 +**Example:** 516 516 517 -((( 518 -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. 519 -))) 526 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 520 520 521 -((( 522 -The command is: 523 -))) 528 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 524 524 525 -((( 526 -(% 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]])**.** 527 -))) 528 528 529 529 530 -((( 531 -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. 532 -))) 532 +== 2.4 Downlink Payload == 533 533 534 - 535 -((( 536 -Example: 537 -))) 538 - 539 -((( 540 -0x(00): Normal uplink packet. 541 -))) 542 - 543 -((( 544 -0x(01): Interrupt Uplink Packet. 545 -))) 546 - 547 - 548 - 549 -=== 2.4.7 +5V Output === 550 - 551 -((( 552 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 553 -))) 554 - 555 - 556 -((( 557 -The 5V output time can be controlled by AT Command. 558 -))) 559 - 560 -((( 561 -(% style="color:blue" %)**AT+5VT=1000** 562 -))) 563 - 564 -((( 565 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 566 -))) 567 - 568 - 569 - 570 -== 2.5 Downlink Payload == 571 - 572 572 By default, NDDS75 prints the downlink payload to console port. 573 573 574 574 [[image:image-20220709100028-1.png]] ... ... @@ -619,51 +619,16 @@ 619 619 620 620 621 621 622 -== 2. 6LED Indicator ==584 +== 2.5 Battery Analysis == 623 623 586 +=== 2.5.1 Battery Type === 624 624 625 -The NDDS75 has an internal LED which is to show the status of different state. 626 626 627 - 628 -* 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) 629 -* Then the LED will be on for 1 second means device is boot normally. 630 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 631 -* For each uplink probe, LED will be on for 500ms. 632 - 633 633 ((( 634 - 590 +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. 635 635 ))) 636 636 637 - 638 - 639 -== 2.7 Firmware Change Log == 640 - 641 - 642 642 ((( 643 -Download URL & Firmware Change log 644 -))) 645 - 646 -((( 647 -[[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/]] 648 -))) 649 - 650 - 651 -((( 652 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 653 -))) 654 - 655 - 656 - 657 -== 2.8 Battery Analysis == 658 - 659 -=== 2.8.1 Battery Type === 660 - 661 - 662 -((( 663 -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. 664 -))) 665 - 666 -((( 667 667 The battery is designed to last for several years depends on the actually use environment and update interval. 668 668 ))) 669 669 ... ... @@ -681,56 +681,35 @@ 681 681 682 682 683 683 684 -=== 2. 8.2 Power consumption Analyze ===611 +=== 2.5.2 Power consumption Analyze === 685 685 686 686 ((( 687 - Draginobatterypoweredproductareall runsinLow Powermode.Wehave an update battery calculatorwhichbaseonthe measurement oftherealdevice. User can usethis calculatortocheck the batterylifeandcalculatethe batterylifeifwant tousedifferenttransmit interval.614 +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. 688 688 ))) 689 689 690 - 691 691 ((( 692 - Instructionto use as below:618 + 693 693 ))) 694 694 695 -((( 696 -(% 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/]] 697 -))) 698 698 622 +=== 2.5.3 Battery Note === 699 699 700 700 ((( 701 - (%style="color:blue"%)**Step2:**(%%)Open it andchoose625 +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. 702 702 ))) 703 703 704 -* ((( 705 -Product Model 706 -))) 707 -* ((( 708 -Uplink Interval 709 -))) 710 -* ((( 711 -Working Mode 712 -))) 713 713 714 -((( 715 -And the Life expectation in difference case will be shown on the right. 716 -))) 717 717 718 - [[image:image-20220709110451-3.png]]630 +=== 2.5.4 Replace the battery === 719 719 720 720 721 - 722 -=== 2.8.3 Battery Note === 723 - 724 724 ((( 725 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.634 +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. 726 726 ))) 727 727 728 728 729 - 730 -=== 2.8.4 Replace the battery === 731 - 732 732 ((( 733 -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).639 +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). 734 734 ))) 735 735 736 736 ... ... @@ -753,7 +753,7 @@ 753 753 754 754 == 4.1 Access AT Commands == 755 755 756 -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/]]662 +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/]] 757 757 758 758 759 759 AT+<CMD>? : Help on <CMD> ... ... @@ -841,7 +841,9 @@ 841 841 ))) 842 842 843 843 ((( 844 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 750 + 751 + 752 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 845 845 ))) 846 846 847 847 ... ... @@ -873,7 +873,7 @@ 873 873 = 7. Order Info = 874 874 875 875 876 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**784 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 877 877 878 878 879 879 (% class="wikigeneratedid" %) ... ... @@ -888,7 +888,7 @@ 888 888 889 889 (% style="color:#037691" %)**Package Includes**: 890 890 891 -* NS E01DistanceDetectSensorNode x 1799 +* N95S31B NB-IoT Temperature and Humidity Sensor 892 892 * External antenna x 1 893 893 ))) 894 894 ... ... @@ -897,11 +897,10 @@ 897 897 898 898 (% style="color:#037691" %)**Dimension and weight**: 899 899 900 - 901 901 * Device Size: 13.0 x 5 x 4.5 cm 902 902 * Device Weight: 150g 903 -* Package Size / pcs : 1 5x12x 5.5cm904 -* Weight / pcs : 220g810 +* Package Size / pcs : 14.0 x 8x 5 cm 811 +* Weight / pcs : 180g 905 905 ))) 906 906 907 907 (((
- 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