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 ... ... @@ -17,35 +17,21 @@ 17 17 18 18 = 1. Introduction = 19 19 20 - 21 21 == 1.1 What is N95S31B NB-IoT Sensor Node == 22 22 23 23 ((( 24 24 25 25 26 -((( 27 27 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*. 28 -))) 29 29 30 -((( 31 31 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. 32 -))) 33 33 34 -((( 35 35 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 36 -))) 37 37 38 -((( 39 39 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). 40 -))) 41 41 42 -((( 43 - 44 -))) 45 45 46 -((( 47 47 ~* make sure you have NB-IoT coverage locally. 48 -))) 49 49 50 50 51 51 ))) ... ... @@ -56,7 +56,6 @@ 56 56 57 57 == 1.2 Features == 58 58 59 - 60 60 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 61 61 * Monitor Temperature & Humidity via SHT31 62 62 * AT Commands to change parameters ... ... @@ -79,8 +79,6 @@ 79 79 * Supply Voltage: 2.1v ~~ 3.6v 80 80 * Operating Temperature: -40 ~~ 85°C 81 81 82 - 83 - 84 84 (% style="color:#037691" %)**NB-IoT Spec:** 85 85 86 86 * - B1 @H-FDD: 2100MHz ... ... @@ -90,10 +90,9 @@ 90 90 * - B20 @H-FDD: 800MHz 91 91 * - B28 @H-FDD: 700MHz 92 92 93 - 94 - 95 95 (% style="color:#037691" %)**Battery:** 96 96 77 + 97 97 * Li/SOCI2 un-chargeable battery 98 98 * Capacity: 8500mAh 99 99 * Self Discharge: <1% / Year @ 25°C ... ... @@ -105,7 +105,6 @@ 105 105 106 106 == 1.4 Applications == 107 107 108 - 109 109 * Smart Buildings & Home Automation 110 110 * Logistics and Supply Chain Management 111 111 * Smart Metering ... ... @@ -117,20 +117,15 @@ 117 117 118 118 119 119 100 +== 1.5 Pin Definitions == 120 120 121 -== 1.5 Pin Definitions & Switch == 122 - 123 - 124 124 N95S31B use the mother board from NBSN95 which as below. 125 125 126 - 127 127 [[image:image-20220709144723-1.png]] 128 128 129 129 130 - 131 131 === 1.5.1 Jumper JP2 === 132 132 133 - 134 134 Power on Device when put this jumper. 135 135 136 136 ... ... @@ -137,20 +137,14 @@ 137 137 138 138 === 1.5.2 BOOT MODE / SW1 === 139 139 140 - 141 -((( 142 142 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. 143 -))) 144 144 145 -((( 146 146 2) Flash: work mode, device starts to work and send out console output for further debug 147 -))) 148 148 149 149 150 150 151 151 === 1.5.3 Reset Button === 152 152 153 - 154 154 Press to reboot the device. 155 155 156 156 ... ... @@ -157,7 +157,6 @@ 157 157 158 158 === 1.5.4 LED === 159 159 160 - 161 161 It will flash: 162 162 163 163 1. When boot the device in flash mode ... ... @@ -164,11 +164,8 @@ 164 164 1. Send an uplink packet 165 165 166 166 167 - 168 - 169 169 = 2. Use N95S31B to communicate with IoT Server = 170 170 171 - 172 172 == 2.1 How it works == 173 173 174 174 ... ... @@ -185,7 +185,7 @@ 185 185 186 186 ))) 187 187 188 -[[image:16575 20100595-569.png]]153 +[[image:1657350248151-650.png]] 189 189 190 190 ((( 191 191 ... ... @@ -201,49 +201,26 @@ 201 201 [[image:image-20220709150546-2.png]] 202 202 203 203 204 - 205 205 === 2.2.1 Test Requirement === 206 206 207 207 208 -((( 209 209 To use N95S31B in your city, make sure meet below requirements: 210 -))) 211 211 212 -* ((( 213 -Your local operator has already distributed a NB-IoT Network there. 214 -))) 215 -* ((( 216 -The local NB-IoT network used the band that N95S31B supports. 217 -))) 218 -* ((( 219 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 220 -))) 174 +* Your local operator has already distributed a NB-IoT Network there. 175 +* The local NB-IoT network used the band that N95S31B supports. 176 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 221 221 222 -((( 223 223 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 224 -))) 225 225 226 -((( 227 227 N95S31B supports different communication protocol such as : 228 -))) 229 229 230 230 ((( 231 -* ((( 232 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 233 -))) 234 -* ((( 235 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 236 -))) 237 -* ((( 238 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 239 -))) 240 -* ((( 241 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 242 -))) 183 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 184 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 185 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 186 +* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 243 243 244 -((( 245 245 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. 246 -))) 247 247 248 248 249 249 ))) ... ... @@ -254,7 +254,6 @@ 254 254 255 255 === 2.2.3 Insert SIM card === 256 256 257 - 258 258 ((( 259 259 Insert the NB-IoT Card get from your provider. 260 260 ))) ... ... @@ -270,18 +270,14 @@ 270 270 271 271 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 272 272 273 - 274 274 ((( 275 275 ((( 276 276 User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below. 277 - 278 - 279 279 ))) 280 280 ))) 281 281 282 282 [[image:1657351312545-300.png]] 283 283 284 - 285 285 **Connection:** 286 286 287 287 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -305,9 +305,8 @@ 305 305 306 306 [[image:1657329814315-101.png]] 307 307 308 - 309 309 ((( 310 -(% style="color:red" %) **Note: the valid AT Commands can be found at:**(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**246 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] 311 311 ))) 312 312 313 313 ... ... @@ -314,10 +314,9 @@ 314 314 315 315 === 2.2.5 Use CoAP protocol to uplink data === 316 316 253 +(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 317 317 318 -(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]** 319 319 320 - 321 321 ((( 322 322 **Use below commands:** 323 323 ))) ... ... @@ -420,83 +420,51 @@ 420 420 == 2.3 Uplink Payload == 421 421 422 422 423 -((( 424 -N95S31B 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. 425 -))) 358 +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. 426 426 427 427 428 -((( 429 429 For example: 430 -))) 431 431 432 -((( 433 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 434 -))) 363 + (% 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. 435 435 436 436 437 -((( 438 438 The uplink payloads are composed in ASCII String. For example: 439 -))) 440 440 441 -((( 442 442 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 443 -))) 444 444 445 -((( 446 446 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 447 -))) 448 448 449 449 450 -((( 451 451 (% style="color:red" %)**NOTE:** 452 -))) 453 453 454 454 (% style="color:red" %) 455 -1. ((( 456 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 457 -))) 458 -1. ((( 459 -By default, the device will send an uplink message every 1 hour. 376 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]]. 377 +1. By default, the device will send an uplink message every 1 hour. 460 460 461 461 462 462 463 - 464 -))) 465 - 466 466 === 2.3.1 Payload Analyze === 467 467 468 468 N95S31B uplink payload includes in total 21 bytes 469 469 470 470 471 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width: 520px" %)386 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 472 472 |=(% style="width: 60px;" %)((( 473 473 **Size(bytes)** 474 -)))|=(% 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** 475 -|(% 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" %)((( 476 -((( 389 +)))|=(% 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** 390 +|(% 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" %)((( 477 477 Reserve/ Same as NBSN95 CFGMOD=1 478 -))) 479 479 480 -((( 481 481 No function here. 482 -))) 483 483 )))|(% style="width:77px" %)((( 484 -((( 485 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 486 -))) 395 +[[Temperature >>||anchor="H2.4.5A0Distance"]] 487 487 488 -((( 489 489 By SHT31 490 -))) 491 491 )))|(% style="width:80px" %)((( 492 -((( 493 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 494 -))) 399 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 495 495 496 -((( 497 497 By SHT31 498 498 ))) 499 -))) 500 500 501 501 ((( 502 502 ((( ... ... @@ -555,25 +555,15 @@ 555 555 556 556 === 2.3.3 Version Info === 557 557 558 - (((461 + 559 559 These bytes include the hardware and software version. 560 -))) 561 561 562 -((( 563 563 Higher byte: Specify hardware version: always 0x00 for N95S31B 564 -))) 565 565 566 -((( 567 567 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 568 -))) 569 569 570 -((( 571 - 572 -))) 573 573 574 -((( 575 575 For example: 0x00 6E: this device is N95S31B with firmware version 110. 576 -))) 577 577 578 578 ((( 579 579 ... ... @@ -642,9 +642,9 @@ 642 642 643 643 644 644 645 -== 2. 4Downlink Payload ==538 +== 2.5 Downlink Payload == 646 646 647 -By default, 95S31Bprints the downlink payload to console port.540 +By default, NDDS75 prints the downlink payload to console port. 648 648 649 649 [[image:image-20220709100028-1.png]] 650 650 ... ... @@ -682,7 +682,7 @@ 682 682 ))) 683 683 684 684 ((( 685 -If payload = 0x04FF, it will reset the 95S31B578 +If payload = 0x04FF, it will reset the NDDS75 686 686 ))) 687 687 688 688 ... ... @@ -694,16 +694,51 @@ 694 694 695 695 696 696 697 -== 2. 5BatteryAnalysis==590 +== 2.6 LED Indicator == 698 698 699 -=== 2.5.1 Battery Type === 700 700 593 +The NDDS75 has an internal LED which is to show the status of different state. 701 701 595 + 596 +* 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) 597 +* Then the LED will be on for 1 second means device is boot normally. 598 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 599 +* For each uplink probe, LED will be on for 500ms. 600 + 702 702 ((( 703 - 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.602 + 704 704 ))) 705 705 605 + 606 + 607 +== 2.7 Firmware Change Log == 608 + 609 + 706 706 ((( 611 +Download URL & Firmware Change log 612 +))) 613 + 614 +((( 615 +[[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/]] 616 +))) 617 + 618 + 619 +((( 620 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 621 +))) 622 + 623 + 624 + 625 +== 2.8 Battery Analysis == 626 + 627 +=== 2.8.1 Battery Type === 628 + 629 + 630 +((( 631 +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. 632 +))) 633 + 634 +((( 707 707 The battery is designed to last for several years depends on the actually use environment and update interval. 708 708 ))) 709 709 ... ... @@ -721,35 +721,56 @@ 721 721 722 722 723 723 724 -=== 2. 5.2 Power consumption Analyze ===652 +=== 2.8.2 Power consumption Analyze === 725 725 726 726 ((( 727 - 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.655 +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. 728 728 ))) 729 729 658 + 730 730 ((( 731 - 660 +Instruction to use as below: 732 732 ))) 733 733 663 +((( 664 +(% 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/]] 665 +))) 734 734 735 -=== 2.5.3 Battery Note === 736 736 737 737 ((( 738 - 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.669 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 739 739 ))) 740 740 672 +* ((( 673 +Product Model 674 +))) 675 +* ((( 676 +Uplink Interval 677 +))) 678 +* ((( 679 +Working Mode 680 +))) 741 741 682 +((( 683 +And the Life expectation in difference case will be shown on the right. 684 +))) 742 742 743 - === 2.5.4 Replacethe battery ===686 +[[image:image-20220709110451-3.png]] 744 744 745 745 689 + 690 +=== 2.8.3 Battery Note === 691 + 746 746 ((( 747 - 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.693 +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. 748 748 ))) 749 749 750 750 697 + 698 +=== 2.8.4 Replace the battery === 699 + 751 751 ((( 752 -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).701 +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). 753 753 ))) 754 754 755 755 ... ... @@ -772,7 +772,7 @@ 772 772 773 773 == 4.1 Access AT Commands == 774 774 775 -See NBSN95 AT Command inthis link for detail:BSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]724 +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/]] 776 776 777 777 778 778 AT+<CMD>? : Help on <CMD> ... ... @@ -860,12 +860,8 @@ 860 860 ))) 861 861 862 862 ((( 863 - 864 - 865 -((( 866 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 812 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 867 867 ))) 868 -))) 869 869 870 870 871 871 ... ... @@ -896,7 +896,7 @@ 896 896 = 7. Order Info = 897 897 898 898 899 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**844 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 900 900 901 901 902 902 (% class="wikigeneratedid" %) ... ... @@ -911,7 +911,7 @@ 911 911 912 912 (% style="color:#037691" %)**Package Includes**: 913 913 914 -* N 95S31BNB-IoTTemperatureandHumiditySensor859 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 915 915 * External antenna x 1 916 916 ))) 917 917 ... ... @@ -920,10 +920,11 @@ 920 920 921 921 (% style="color:#037691" %)**Dimension and weight**: 922 922 868 + 923 923 * Device Size: 13.0 x 5 x 4.5 cm 924 924 * Device Weight: 150g 925 -* Package Size / pcs : 1 4.0x8x 5 cm926 -* Weight / pcs : 180g871 +* Package Size / pcs : 15 x 12x 5.5 cm 872 +* Weight / pcs : 220g 927 927 ))) 928 928 929 929 (((
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content