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 ... ... @@ -67,8 +67,6 @@ 67 67 * 8500mAh Battery for long term use 68 68 69 69 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 76 + 93 93 * Li/SOCI2 un-chargeable battery 94 94 * Capacity: 8500mAh 95 95 * Self Discharge: <1% / Year @ 25°C ... ... @@ -97,8 +97,6 @@ 97 97 * Max boost current: 2A, 1 second 98 98 99 99 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 ... ... @@ -152,7 +152,6 @@ 152 152 153 153 154 154 155 - 156 156 = 2. Use N95S31B to communicate with IoT Server = 157 157 158 158 == 2.1 How it works == ... ... @@ -190,45 +190,23 @@ 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 -))) 172 +* Your local operator has already distributed a NB-IoT Network there. 173 +* The local NB-IoT network used the band that N95S31B supports. 174 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 206 206 207 -((( 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 -))) 181 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 182 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 183 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 184 +* 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 ))) ... ... @@ -398,80 +398,52 @@ 398 398 == 2.3 Uplink Payload == 399 399 400 400 401 -((( 402 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 -))) 404 404 405 405 406 -((( 407 407 For example: 408 -))) 409 409 410 -((( 411 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 -))) 413 413 414 414 415 -((( 416 416 The uplink payloads are composed in ASCII String. For example: 417 -))) 418 418 419 -((( 420 420 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 421 -))) 422 422 423 -((( 424 424 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 425 -))) 426 426 427 427 428 -((( 429 429 (% style="color:red" %)**NOTE:** 430 -))) 431 431 432 432 (% style="color:red" %) 433 -1. ((( 434 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 435 -))) 436 -1. ((( 437 -By default, the device will send an uplink message every 1 hour. 438 -))) 374 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]]. 375 +1. By default, the device will send an uplink message every 1 hour. 439 439 440 440 378 + 379 + 441 441 === 2.3.1 Payload Analyze === 442 442 443 443 N95S31B uplink payload includes in total 21 bytes 444 444 445 445 446 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width: 520px" %)385 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 447 447 |=(% style="width: 60px;" %)((( 448 448 **Size(bytes)** 449 -)))|=(% 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** 450 -|(% 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" %)((( 451 -((( 388 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1** 389 +|(% 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:123px" %)MOD 0X01|(% style="width:99px" %)((( 452 452 Reserve/ Same as NBSN95 CFGMOD=1 453 -))) 454 454 455 -((( 456 456 No function here. 457 -))) 458 458 )))|(% style="width:77px" %)((( 459 -((( 460 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 461 -))) 394 +[[Temperature >>||anchor="H2.4.5A0Distance"]] 462 462 463 -((( 464 464 By SHT31 465 -))) 466 466 )))|(% style="width:80px" %)((( 467 -((( 468 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 469 -))) 398 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 470 470 471 -((( 472 472 By SHT31 473 473 ))) 474 -))) 475 475 476 476 ((( 477 477 ((( ... ... @@ -482,30 +482,43 @@ 482 482 483 483 [[image:1657354294009-643.png]] 484 484 412 +((( 413 +The payload is ASCII string, representative same HEX: 414 +))) 485 485 486 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 416 +((( 417 +0x72403155615900640c6c19029200 where: 418 +))) 487 487 488 -* Device ID: 0x724031607457 = 724031607457 489 -* Version: 0x006e=110=1.1.0 420 +* ((( 421 +Device ID: 0x724031556159 = 724031556159 422 +))) 423 +* ((( 424 +Version: 0x0064=100=1.0.0 425 +))) 490 490 491 -* BAT: 0x0ccd = 3277 mV = 3.277V 492 -* Signal: 0x1b = 27 493 -* Model: 0x01 = 1 494 -* 0x00dc000ccc= reserve, ignore in N95S31B 495 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 496 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 497 - 498 -((( 499 - 427 +* ((( 428 +BAT: 0x0c6c = 3180 mV = 3.180V 500 500 ))) 430 +* ((( 431 +Signal: 0x19 = 25 432 +))) 433 +* ((( 434 +Distance: 0x0292= 658 mm 435 +))) 436 +* ((( 437 +Interrupt: 0x00 = 0 501 501 502 -((( 439 + 440 + 503 503 504 504 ))) 505 505 444 +== 2.4 Payload Explanation and Sensor Interface == 506 506 507 -=== 2.3.2 Device ID === 508 508 447 +=== 2.4.1 Device ID === 448 + 509 509 ((( 510 510 By default, the Device ID equal to the last 6 bytes of IMEI. 511 511 ))) ... ... @@ -528,25 +528,20 @@ 528 528 529 529 530 530 531 -=== 2. 3.3Version Info ===471 +=== 2.4.2 Version Info === 532 532 473 +((( 474 +Specify the software version: 0x64=100, means firmware version 1.00. 475 +))) 533 533 534 -These bytes include the hardware and software version. 535 - 536 -Higher byte: Specify hardware version: always 0x00 for N95S31B 537 - 538 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110 539 - 540 - 541 -For example: 0x00 6E: this device is N95S31B with firmware version 110. 542 - 543 543 ((( 544 - 478 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 545 545 ))) 546 546 547 547 548 -=== 2.3.4 Battery Info === 549 549 483 +=== 2.4.3 Battery Info === 484 + 550 550 ((( 551 551 Ex1: 0x0B45 = 2885mV 552 552 ))) ... ... @@ -557,7 +557,7 @@ 557 557 558 558 559 559 560 -=== 2. 3.5Signal Strength ===495 +=== 2.4.4 Signal Strength === 561 561 562 562 ((( 563 563 NB-IoT Network signal Strength. ... ... @@ -589,26 +589,85 @@ 589 589 590 590 591 591 592 -=== 2. 3.6Temperature& Humidity===527 +=== 2.4.5 Distance === 593 593 594 - The devicewill beabletogetthe SHT31 temperatureand humiditydatanow and upload to IoT Server.529 +Get the distance. Flat object range 280mm - 7500mm. 595 595 596 -[[image:image-20220709161741-3.png]] 531 +((( 532 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 533 +))) 597 597 535 +((( 536 +((( 537 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 538 +))) 539 +))) 598 598 599 -Convert the read byte to decimal and divide it by ten. 541 +((( 542 + 543 +))) 600 600 545 +((( 546 + 547 +))) 601 601 602 - **Example:**549 +=== 2.4.6 Digital Interrupt === 603 603 604 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 551 +((( 552 +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. 553 +))) 605 605 606 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 555 +((( 556 +The command is: 557 +))) 607 607 559 +((( 560 +(% 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]])**.** 561 +))) 608 608 609 609 610 -== 2.4 Downlink Payload == 564 +((( 565 +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. 566 +))) 611 611 568 + 569 +((( 570 +Example: 571 +))) 572 + 573 +((( 574 +0x(00): Normal uplink packet. 575 +))) 576 + 577 +((( 578 +0x(01): Interrupt Uplink Packet. 579 +))) 580 + 581 + 582 + 583 +=== 2.4.7 +5V Output === 584 + 585 +((( 586 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 587 +))) 588 + 589 + 590 +((( 591 +The 5V output time can be controlled by AT Command. 592 +))) 593 + 594 +((( 595 +(% style="color:blue" %)**AT+5VT=1000** 596 +))) 597 + 598 +((( 599 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 600 +))) 601 + 602 + 603 + 604 +== 2.5 Downlink Payload == 605 + 612 612 By default, NDDS75 prints the downlink payload to console port. 613 613 614 614 [[image:image-20220709100028-1.png]] ... ... @@ -659,16 +659,51 @@ 659 659 660 660 661 661 662 -== 2. 5BatteryAnalysis==656 +== 2.6 LED Indicator == 663 663 664 -=== 2.5.1 Battery Type === 665 665 659 +The NDDS75 has an internal LED which is to show the status of different state. 666 666 661 + 662 +* 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) 663 +* Then the LED will be on for 1 second means device is boot normally. 664 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 665 +* For each uplink probe, LED will be on for 500ms. 666 + 667 667 ((( 668 - 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.668 + 669 669 ))) 670 670 671 + 672 + 673 +== 2.7 Firmware Change Log == 674 + 675 + 671 671 ((( 677 +Download URL & Firmware Change log 678 +))) 679 + 680 +((( 681 +[[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/]] 682 +))) 683 + 684 + 685 +((( 686 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 687 +))) 688 + 689 + 690 + 691 +== 2.8 Battery Analysis == 692 + 693 +=== 2.8.1 Battery Type === 694 + 695 + 696 +((( 697 +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. 698 +))) 699 + 700 +((( 672 672 The battery is designed to last for several years depends on the actually use environment and update interval. 673 673 ))) 674 674 ... ... @@ -686,35 +686,56 @@ 686 686 687 687 688 688 689 -=== 2. 5.2 Power consumption Analyze ===718 +=== 2.8.2 Power consumption Analyze === 690 690 691 691 ((( 692 - 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.721 +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. 693 693 ))) 694 694 724 + 695 695 ((( 696 - 726 +Instruction to use as below: 697 697 ))) 698 698 729 +((( 730 +(% 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/]] 731 +))) 699 699 700 -=== 2.5.3 Battery Note === 701 701 702 702 ((( 703 - 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.735 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 704 704 ))) 705 705 738 +* ((( 739 +Product Model 740 +))) 741 +* ((( 742 +Uplink Interval 743 +))) 744 +* ((( 745 +Working Mode 746 +))) 706 706 748 +((( 749 +And the Life expectation in difference case will be shown on the right. 750 +))) 707 707 708 - === 2.5.4 Replacethe battery ===752 +[[image:image-20220709110451-3.png]] 709 709 710 710 755 + 756 +=== 2.8.3 Battery Note === 757 + 711 711 ((( 712 - 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.759 +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. 713 713 ))) 714 714 715 715 763 + 764 +=== 2.8.4 Replace the battery === 765 + 716 716 ((( 717 -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).767 +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). 718 718 ))) 719 719 720 720 ... ... @@ -737,7 +737,7 @@ 737 737 738 738 == 4.1 Access AT Commands == 739 739 740 -See NBSN95 AT Command inthis link for detail:BSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]790 +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/]] 741 741 742 742 743 743 AT+<CMD>? : Help on <CMD> ... ... @@ -825,9 +825,7 @@ 825 825 ))) 826 826 827 827 ((( 828 - 829 - 830 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 878 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 831 831 ))) 832 832 833 833 ... ... @@ -859,7 +859,7 @@ 859 859 = 7. Order Info = 860 860 861 861 862 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**910 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 863 863 864 864 865 865 (% class="wikigeneratedid" %) ... ... @@ -874,7 +874,7 @@ 874 874 875 875 (% style="color:#037691" %)**Package Includes**: 876 876 877 -* N 95S31BNB-IoTTemperatureandHumiditySensor925 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 878 878 * External antenna x 1 879 879 ))) 880 880 ... ... @@ -883,10 +883,11 @@ 883 883 884 884 (% style="color:#037691" %)**Dimension and weight**: 885 885 934 + 886 886 * Device Size: 13.0 x 5 x 4.5 cm 887 887 * Device Weight: 150g 888 -* Package Size / pcs : 1 4.0x8x 5 cm889 -* Weight / pcs : 180g937 +* Package Size / pcs : 15 x 12x 5.5 cm 938 +* Weight / pcs : 220g 890 890 ))) 891 891 892 892 (((
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.2 KB - Content