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, 1 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 ... ... @@ -95,6 +95,8 @@ 95 95 * Max continuously current: 130mA 96 96 * Max boost current: 2A, 1 second 97 97 84 + 85 + 98 98 == 1.4 Applications == 99 99 100 100 * Smart Buildings & Home Automation ... ... @@ -142,6 +142,9 @@ 142 142 1. When boot the device in flash mode 143 143 1. Send an uplink packet 144 144 133 + 134 + 135 + 145 145 = 2. Use N95S31B to communicate with IoT Server = 146 146 147 147 == 2.1 How it works == ... ... @@ -185,6 +185,7 @@ 185 185 * The local NB-IoT network used the band that N95S31B supports. 186 186 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 187 187 179 + 188 188 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 189 189 190 190 N95S31B supports different communication protocol such as : ... ... @@ -317,8 +317,8 @@ 317 317 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 318 318 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 319 319 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 320 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 321 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 312 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 313 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 322 322 323 323 [[image:1657352634421-276.png]] 324 324 ... ... @@ -364,200 +364,216 @@ 364 364 365 365 == 2.3 Uplink Payload == 366 366 359 +In this mode, uplink payload includes in total 14 bytes 367 367 368 -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. 369 369 362 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 363 +|=(% style="width: 60px;" %)((( 364 +**Size(bytes)** 365 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 366 +|(% 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"]] 370 370 371 -For example: 368 +((( 369 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 370 +))) 372 372 373 - (% 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. 374 374 373 +[[image:1657331036973-987.png]] 375 375 376 -The uplink payloads are composed in ASCII String. For example: 375 +((( 376 +The payload is ASCII string, representative same HEX: 377 +))) 377 377 378 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 379 +((( 380 +0x72403155615900640c6c19029200 where: 381 +))) 379 379 380 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 383 +* ((( 384 +Device ID: 0x724031556159 = 724031556159 385 +))) 386 +* ((( 387 +Version: 0x0064=100=1.0.0 388 +))) 381 381 390 +* ((( 391 +BAT: 0x0c6c = 3180 mV = 3.180V 392 +))) 393 +* ((( 394 +Signal: 0x19 = 25 395 +))) 396 +* ((( 397 +Distance: 0x0292= 658 mm 398 +))) 399 +* ((( 400 +Interrupt: 0x00 = 0 382 382 383 -(% style="color:red" %)**NOTE:** 384 384 385 -(% style="color:red" %) 386 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 387 -1. By default, the device will send an uplink message every 1 hour. 388 388 404 + 405 +))) 389 389 390 -== =2.3.1PayloadAnalyze ===407 +== 2.4 Payload Explanation and Sensor Interface == 391 391 392 -N95S31B uplink payload includes in total 21 bytes 393 393 410 +=== 2.4.1 Device ID === 394 394 395 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 396 -|=(% style="width: 60px;" %)((( 397 -**Size(bytes)** 398 -)))|=(% 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** 399 -|(% 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" %)((( 400 400 ((( 401 - Reserve/Same asNBSN95CFGMOD=1413 +By default, the Device ID equal to the last 6 bytes of IMEI. 402 402 ))) 403 403 404 404 ((( 405 - Nofunctionhere.417 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 406 406 ))) 407 - )))|(% style="width:77px" %)(((419 + 408 408 ((( 409 - [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]421 +**Example:** 410 410 ))) 411 411 412 412 ((( 413 - By SHT31425 +AT+DEUI=A84041F15612 414 414 ))) 415 - )))|(% style="width:80px" %)(((427 + 416 416 ((( 417 - [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]429 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 418 418 ))) 419 419 432 + 433 + 434 +=== 2.4.2 Version Info === 435 + 420 420 ((( 421 - BySHT31437 +Specify the software version: 0x64=100, means firmware version 1.00. 422 422 ))) 423 -))) 424 424 425 425 ((( 426 -((( 427 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 441 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 428 428 ))) 429 -))) 430 430 431 431 432 -[[image:1657354294009-643.png]] 433 433 446 +=== 2.4.3 Battery Info === 434 434 435 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 436 - 437 -* Device ID: 0x724031607457 = 724031607457 438 -* Version: 0x006e=110=1.1.0 439 - 440 -* BAT: 0x0ccd = 3277 mV = 3.277V 441 -* Signal: 0x1b = 27 442 -* Model: 0x01 = 1 443 -* 0x00dc000ccc= reserve, ignore in N95S31B 444 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 445 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 446 - 447 447 ((( 448 - 449 +Ex1: 0x0B45 = 2885mV 449 449 ))) 450 450 451 451 ((( 452 - 453 +Ex2: 0x0B49 = 2889mV 453 453 ))) 454 454 455 455 456 -=== 2.3.2 Device ID === 457 457 458 +=== 2.4.4 Signal Strength === 459 + 458 458 ((( 459 -B ydefault,the Device ID equal to thelast6 bytes of IMEI.461 +NB-IoT Network signal Strength. 460 460 ))) 461 461 462 462 ((( 463 - User can use (% style="color:blue" %)**AT+DEUI**(%%)tosetDevice ID465 +**Ex1: 0x1d = 29** 464 464 ))) 465 465 466 466 ((( 467 - **Example:**469 +(% style="color:blue" %)**0**(%%) -113dBm or less 468 468 ))) 469 469 470 470 ((( 471 - AT+DEUI=A84041F15612473 +(% style="color:blue" %)**1**(%%) -111dBm 472 472 ))) 473 473 474 474 ((( 475 - TheDevice ID isstored in a none-erase area, Upgrade the firmwareorrun**AT+FDR**won't erase Device ID.477 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 476 476 ))) 477 477 480 +((( 481 +(% style="color:blue" %)**31** (%%) -51dBm or greater 482 +))) 478 478 484 +((( 485 +(% style="color:blue" %)**99** (%%) Not known or not detectable 486 +))) 479 479 480 -=== 2.3.3 Version Info === 481 481 482 482 483 - Thesebytesinclude the hardware andsoftwareversion.490 +=== 2.4.5 Distance === 484 484 485 - Higherbyte:Specifyhardwareversion: always0x00forN95S31B492 +Get the distance. Flat object range 280mm - 7500mm. 486 486 487 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110 494 +((( 495 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 496 +))) 488 488 489 - 490 -For example: 0x00 6E: this device is N95S31B with firmware version 110. 491 - 492 492 ((( 493 - 499 +((( 500 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 494 494 ))) 502 +))) 495 495 496 - 497 -=== 2.3.4 Battery Info === 498 - 499 499 ((( 500 - Ex1:0x0B45 = 2885mV505 + 501 501 ))) 502 502 503 503 ((( 504 - Ex2:0x0B49 = 2889mV509 + 505 505 ))) 506 506 512 +=== 2.4.6 Digital Interrupt === 507 507 508 - 509 -=== 2.3.5 Signal Strength === 510 - 511 511 ((( 512 - NB-IoTNetworksignalStrength.515 +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. 513 513 ))) 514 514 515 515 ((( 516 - **Ex1:0x1d= 29**519 +The command is: 517 517 ))) 518 518 519 519 ((( 520 -(% style="color:blue" %)** 0**(%%)-113dBmor less523 +(% 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]])**.** 521 521 ))) 522 522 526 + 523 523 ((( 524 - (%style="color:blue"%)**1**(%%)-111dBm528 +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. 525 525 ))) 526 526 531 + 527 527 ((( 528 - (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm533 +Example: 529 529 ))) 530 530 531 531 ((( 532 -( %style="color:blue"%)**31** (%%) -51dBm or greater537 +0x(00): Normal uplink packet. 533 533 ))) 534 534 535 535 ((( 536 -( %style="color:blue" %)**99** (%%) Notknownor not detectable541 +0x(01): Interrupt Uplink Packet. 537 537 ))) 538 538 539 539 540 540 541 -=== 2. 3.6Temperature& Humidity===546 +=== 2.4.7 +5V Output === 542 542 543 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 548 +((( 549 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 550 +))) 544 544 545 -[[image:image-20220709161741-3.png]] 546 546 553 +((( 554 +The 5V output time can be controlled by AT Command. 555 +))) 547 547 548 -Convert the read byte to decimal and divide it by ten. 557 +((( 558 +(% style="color:blue" %)**AT+5VT=1000** 559 +))) 549 549 561 +((( 562 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 563 +))) 550 550 551 -**Example:** 552 552 553 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 554 554 555 - Humidity:Read:0295(H)=661(D)Value:661 / 10=66.1, So66.1%567 +== 2.5 Downlink Payload == 556 556 557 - 558 - 559 -== 2.4 Downlink Payload == 560 - 561 561 By default, NDDS75 prints the downlink payload to console port. 562 562 563 563 [[image:image-20220709100028-1.png]] ... ... @@ -608,16 +608,51 @@ 608 608 609 609 610 610 611 -== 2. 5BatteryAnalysis==619 +== 2.6 LED Indicator == 612 612 613 -=== 2.5.1 Battery Type === 614 614 622 +The NDDS75 has an internal LED which is to show the status of different state. 615 615 624 + 625 +* 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) 626 +* Then the LED will be on for 1 second means device is boot normally. 627 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 628 +* For each uplink probe, LED will be on for 500ms. 629 + 616 616 ((( 617 - 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.631 + 618 618 ))) 619 619 634 + 635 + 636 +== 2.7 Firmware Change Log == 637 + 638 + 620 620 ((( 640 +Download URL & Firmware Change log 641 +))) 642 + 643 +((( 644 +[[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/]] 645 +))) 646 + 647 + 648 +((( 649 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 650 +))) 651 + 652 + 653 + 654 +== 2.8 Battery Analysis == 655 + 656 +=== 2.8.1 Battery Type === 657 + 658 + 659 +((( 660 +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. 661 +))) 662 + 663 +((( 621 621 The battery is designed to last for several years depends on the actually use environment and update interval. 622 622 ))) 623 623 ... ... @@ -635,35 +635,56 @@ 635 635 636 636 637 637 638 -=== 2. 5.2 Power consumption Analyze ===681 +=== 2.8.2 Power consumption Analyze === 639 639 640 640 ((( 641 - 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.684 +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. 642 642 ))) 643 643 687 + 644 644 ((( 645 - 689 +Instruction to use as below: 646 646 ))) 647 647 692 +((( 693 +(% 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/]] 694 +))) 648 648 649 -=== 2.5.3 Battery Note === 650 650 651 651 ((( 652 - 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.698 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 653 653 ))) 654 654 701 +* ((( 702 +Product Model 703 +))) 704 +* ((( 705 +Uplink Interval 706 +))) 707 +* ((( 708 +Working Mode 709 +))) 655 655 711 +((( 712 +And the Life expectation in difference case will be shown on the right. 713 +))) 656 656 657 - === 2.5.4 Replacethe battery ===715 +[[image:image-20220709110451-3.png]] 658 658 659 659 718 + 719 +=== 2.8.3 Battery Note === 720 + 660 660 ((( 661 - 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.722 +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. 662 662 ))) 663 663 664 664 726 + 727 +=== 2.8.4 Replace the battery === 728 + 665 665 ((( 666 -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).730 +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). 667 667 ))) 668 668 669 669 ... ... @@ -686,7 +686,7 @@ 686 686 687 687 == 4.1 Access AT Commands == 688 688 689 -See NBSN95 AT Command inthis link for detail:BSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]753 +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/]] 690 690 691 691 692 692 AT+<CMD>? : Help on <CMD> ... ... @@ -774,9 +774,7 @@ 774 774 ))) 775 775 776 776 ((( 777 - 778 - 779 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 841 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 780 780 ))) 781 781 782 782 ... ... @@ -808,7 +808,7 @@ 808 808 = 7. Order Info = 809 809 810 810 811 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**873 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 812 812 813 813 814 814 (% class="wikigeneratedid" %) ... ... @@ -823,7 +823,7 @@ 823 823 824 824 (% style="color:#037691" %)**Package Includes**: 825 825 826 -* N 95S31BNB-IoTTemperatureandHumiditySensor888 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 827 827 * External antenna x 1 828 828 ))) 829 829 ... ... @@ -832,10 +832,11 @@ 832 832 833 833 (% style="color:#037691" %)**Dimension and weight**: 834 834 897 + 835 835 * Device Size: 13.0 x 5 x 4.5 cm 836 836 * Device Weight: 150g 837 -* Package Size / pcs : 1 4.0x8x 5 cm838 -* Weight / pcs : 180g900 +* Package Size / pcs : 15 x 12x 5.5 cm 901 +* Weight / pcs : 220g 839 839 ))) 840 840 841 841 (((
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.2 KB - Content