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 (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 6 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -N DDS75 NB-IoTDistanceDetect Sensor User Manual1 +N95S31B NB-IoT Temperature & Humidity Sensor User Manual - Content
-
... ... @@ -1,62 +1,60 @@ 1 1 (% style="text-align:center" %) 2 -[[image: image-20220709085040-1.png||height="542" width="524"]]2 +[[image:1657348034241-728.png||height="470" width="470"]] 3 3 4 4 5 5 6 6 7 7 8 -**Table of Contents:** 9 9 10 -{{toc/}} 11 11 10 +**Table of Contents:** 12 12 13 13 14 14 15 15 16 16 16 + 17 17 = 1. Introduction = 18 18 19 -== 1.1 What is N DDS75Distance DetectionSensor ==19 +== 1.1 What is N95S31B NB-IoT Sensor Node == 20 20 21 21 ((( 22 22 23 23 24 -((( 25 -The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data. 26 -\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network. 27 -\\NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage. 28 -\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 29 -\\NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 30 -\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection. 31 -))) 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*. 32 32 33 - 34 -))) 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. 35 35 36 - [[image:1654503236291-817.png]]28 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 37 37 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). 38 38 39 -[[image:1657327959271-447.png]] 40 40 33 +~* make sure you have NB-IoT coverage locally. 41 41 35 + 36 +))) 42 42 38 +[[image:1657348284168-431.png]] 39 + 40 + 41 + 43 43 == 1.2 Features == 44 44 45 45 46 46 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 47 -* Ultra low power consumption 48 -* Distance Detection by Ultrasonic technology 49 -* Flat object range 280mm - 7500mm 50 -* Accuracy: ±(1cm+S*0.3%) (S: Distance) 51 -* Cable Length: 25cm 46 +* Monitor Temperature & Humidity via SHT31 52 52 * AT Commands to change parameters 53 53 * Uplink on periodically 54 54 * Downlink to change configure 55 55 * IP66 Waterproof Enclosure 51 +* Ultra-Low Power consumption 52 +* AT Commands to change parameters 56 56 * Micro SIM card slot for NB-IoT SIM 57 57 * 8500mAh Battery for long term use 58 58 59 59 57 + 60 60 == 1.3 Specification == 61 61 62 62 ... ... @@ -76,6 +76,7 @@ 76 76 77 77 (% style="color:#037691" %)**Battery:** 78 78 77 + 79 79 * Li/SOCI2 un-chargeable battery 80 80 * Capacity: 8500mAh 81 81 * Self Discharge: <1% / Year @ 25°C ... ... @@ -82,13 +82,8 @@ 82 82 * Max continuously current: 130mA 83 83 * Max boost current: 2A, 1 second 84 84 85 -(% style="color:#037691" %)**Power Consumption** 86 86 87 -* STOP Mode: 10uA @ 3.3v 88 -* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 89 89 90 - 91 - 92 92 == 1.4 Applications == 93 93 94 94 * Smart Buildings & Home Automation ... ... @@ -102,25 +102,55 @@ 102 102 103 103 104 104 105 - 106 106 == 1.5 Pin Definitions == 107 107 101 +N95S31B use the mother board from NBSN95 which as below. 108 108 109 -[[image: 1657328609906-564.png]]103 +[[image:image-20220709144723-1.png]] 110 110 111 111 106 +=== 1.5.1 Jumper JP2 === 112 112 113 - = 2. UseNDDS75 tocommunicate withIoTServer =108 +Power on Device when put this jumper. 114 114 110 + 111 + 112 +=== 1.5.2 BOOT MODE / SW1 === 113 + 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. 115 + 116 +2) Flash: work mode, device starts to work and send out console output for further debug 117 + 118 + 119 + 120 +=== 1.5.3 Reset Button === 121 + 122 +Press to reboot the device. 123 + 124 + 125 + 126 +=== 1.5.4 LED === 127 + 128 +It will flash: 129 + 130 +1. When boot the device in flash mode 131 +1. Send an uplink packet 132 + 133 + 134 + 135 + 136 += 2. Use N95S31B to communicate with IoT Server = 137 + 115 115 == 2.1 How it works == 116 116 140 + 117 117 ((( 118 -The N DDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.142 +The N95S31B is equipped with a NB-IoT module, the pre-loaded firmware in N95S31B will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by N95S31B. 119 119 ))) 120 120 121 121 122 122 ((( 123 -The diagram below shows the working flow in default firmware of N DDS75:147 +The diagram below shows the working flow in default firmware of N95S31B: 124 124 ))) 125 125 126 126 ((( ... ... @@ -127,7 +127,7 @@ 127 127 128 128 ))) 129 129 130 -[[image:1657328 659945-416.png]]154 +[[image:1657350248151-650.png]] 131 131 132 132 ((( 133 133 ... ... @@ -134,20 +134,41 @@ 134 134 ))) 135 135 136 136 137 -== 2.2 Configure the N DDS75 ==161 +== 2.2 Configure the N95S31B == 138 138 139 139 164 +=== 2.2.1 Power On N95S31B === 165 + 166 + 167 +[[image:image-20220709150546-2.png]] 168 + 169 + 140 140 === 2.2.1 Test Requirement === 141 141 142 -((( 143 -To use NDDS75 in your city, make sure meet below requirements: 144 -))) 145 145 173 +To use N95S31B in your city, make sure meet below requirements: 174 + 146 146 * Your local operator has already distributed a NB-IoT Network there. 147 -* The local NB-IoT network used the band that NS E01 supports.176 +* The local NB-IoT network used the band that N95S31B supports. 148 148 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 149 149 179 + 180 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 181 + 182 +N95S31B supports different communication protocol such as : 183 + 150 150 ((( 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(%%)) 189 + 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. 191 + 192 + 193 +))) 194 + 195 +((( 151 151 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server 152 152 ))) 153 153 ... ... @@ -215,18 +215,30 @@ 215 215 (% 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/]] 216 216 217 217 263 +((( 218 218 **Use below commands:** 265 +))) 219 219 220 -* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 221 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 222 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 267 +* ((( 268 +(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 269 +))) 270 +* ((( 271 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 272 +))) 273 +* ((( 274 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 275 +))) 223 223 277 +((( 224 224 For parameter description, please refer to AT command set 279 +))) 225 225 226 226 [[image:1657330452568-615.png]] 227 227 228 228 284 +((( 229 229 After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server. 286 +))) 230 230 231 231 [[image:1657330472797-498.png]] 232 232 ... ... @@ -235,9 +235,9 @@ 235 235 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 236 236 237 237 238 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 295 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 239 239 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 240 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 297 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 241 241 242 242 [[image:1657330501006-241.png]] 243 243 ... ... @@ -249,11 +249,11 @@ 249 249 === 2.2.6 Use MQTT protocol to uplink data === 250 250 251 251 252 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 253 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 254 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 255 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 256 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 309 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 310 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 311 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 312 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 313 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 257 257 * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 258 258 * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 259 259 ... ... @@ -303,11 +303,11 @@ 303 303 In this mode, uplink payload includes in total 14 bytes 304 304 305 305 306 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width: 510px" %)307 -|=(% style="width: 80px;" %)(((363 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 364 +|=(% style="width: 60px;" %)((( 308 308 **Size(bytes)** 309 -)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width:110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width:70px;" %)**1**310 -|(% 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. 8A0DigitalInterrupt"]]366 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 367 +|(% 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"]] 311 311 312 312 ((( 313 313 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. ... ... @@ -342,9 +342,12 @@ 342 342 ))) 343 343 * ((( 344 344 Interrupt: 0x00 = 0 345 -))) 346 346 347 347 404 + 405 + 406 +))) 407 + 348 348 == 2.4 Payload Explanation and Sensor Interface == 349 349 350 350 ... ... @@ -387,10 +387,6 @@ 387 387 === 2.4.3 Battery Info === 388 388 389 389 ((( 390 -Check the battery voltage for LSE01. 391 -))) 392 - 393 -((( 394 394 Ex1: 0x0B45 = 2885mV 395 395 ))) 396 396 ... ... @@ -436,7 +436,9 @@ 436 436 437 437 Get the distance. Flat object range 280mm - 7500mm. 438 438 495 +((( 439 439 For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 497 +))) 440 440 441 441 ((( 442 442 ((( ... ... @@ -579,7 +579,9 @@ 579 579 == 2.7 Firmware Change Log == 580 580 581 581 640 +((( 582 582 Download URL & Firmware Change log 642 +))) 583 583 584 584 ((( 585 585 [[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/]] ... ... @@ -586,7 +586,9 @@ 586 586 ))) 587 587 588 588 649 +((( 589 589 Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 651 +))) 590 590 591 591 592 592 ... ... @@ -651,7 +651,7 @@ 651 651 And the Life expectation in difference case will be shown on the right. 652 652 ))) 653 653 654 -[[image:image-2022070 8141352-7.jpeg]]716 +[[image:image-20220709110451-3.png]] 655 655 656 656 657 657
- 1657348034241-728.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +127.8 KB - Content
- 1657348284168-431.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +93.5 KB - Content
- 1657350248151-650.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content
- image-20220709110451-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +611.5 KB - Content
- image-20220709144723-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +413.1 KB - Content
- image-20220709150546-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +333.5 KB - Content