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, 0 added, 5 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -N 95S31BNB-IoTTemperature& HumiditySensor User Manual1 +NDDS75 NB-IoT Distance Detect Sensor User Manual - Content
-
... ... @@ -1,60 +1,61 @@ 1 1 (% style="text-align:center" %) 2 -[[image: 1657348034241-728.png||height="470" width="470"]]2 +[[image:image-20220709085040-1.png||height="542" width="524"]] 3 3 4 4 5 5 6 6 7 7 8 - 9 - 10 10 **Table of Contents:** 11 11 10 +{{toc/}} 12 12 13 13 14 14 15 15 16 16 16 + 17 17 = 1. Introduction = 18 18 19 -== 1.1 What is N 95S31BNB-IoTSensorNode==19 +== 1.1 What is NDDS75 Distance Detection Sensor == 20 20 21 21 ((( 22 22 23 23 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*. 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 +))) 25 25 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. 27 - 28 -N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 29 - 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). 31 - 32 - 33 -~* make sure you have NB-IoT coverage locally. 34 - 35 35 36 36 ))) 37 37 38 -[[image:165 7348284168-431.png]]36 +[[image:1654503236291-817.png]] 39 39 40 40 39 +[[image:1657327959271-447.png]] 41 41 41 + 42 + 42 42 == 1.2 Features == 43 43 44 44 45 45 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 46 -* Monitor Temperature & Humidity via SHT31 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 47 47 * AT Commands to change parameters 48 48 * Uplink on periodically 49 49 * Downlink to change configure 50 50 * IP66 Waterproof Enclosure 51 -* Ultra-Low Power consumption 52 -* AT Commands to change parameters 53 53 * Micro SIM card slot for NB-IoT SIM 54 54 * 8500mAh Battery for long term use 55 55 56 - 57 - 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -74,7 +74,6 @@ 74 74 75 75 (% style="color:#037691" %)**Battery:** 76 76 77 - 78 78 * Li/SOCI2 un-chargeable battery 79 79 * Capacity: 8500mAh 80 80 * Self Discharge: <1% / Year @ 25°C ... ... @@ -81,8 +81,12 @@ 81 81 * Max continuously current: 130mA 82 82 * Max boost current: 2A, 1 second 83 83 84 +(% style="color:#037691" %)**Power Consumption** 84 84 86 +* STOP Mode: 10uA @ 3.3v 87 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 85 85 89 + 86 86 == 1.4 Applications == 87 87 88 88 * Smart Buildings & Home Automation ... ... @@ -96,55 +96,25 @@ 96 96 97 97 98 98 103 + 99 99 == 1.5 Pin Definitions == 100 100 101 -N95S31B use the mother board from NBSN95 which as below. 102 102 103 -[[image: image-20220709144723-1.png]]107 +[[image:1657328609906-564.png]] 104 104 105 105 106 -=== 1.5.1 Jumper JP2 === 107 107 108 - PoweronDevice when putthisjumper.111 += 2. Use NDDS75 to communicate with IoT Server = 109 109 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 - 138 138 == 2.1 How it works == 139 139 140 - 141 141 ((( 142 -The N 95S31Bis equipped with a NB-IoT module, the pre-loaded firmware in N95S31Bwill 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.116 +The NDDS75 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. 143 143 ))) 144 144 145 145 146 146 ((( 147 -The diagram below shows the working flow in default firmware of N 95S31B:121 +The diagram below shows the working flow in default firmware of NDDS75: 148 148 ))) 149 149 150 150 ((( ... ... @@ -239,30 +239,18 @@ 239 239 (% 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/]] 240 240 241 241 242 -((( 243 243 **Use below commands:** 244 -))) 245 245 246 -* ((( 247 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 248 -))) 249 -* ((( 250 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 251 -))) 252 -* ((( 253 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 254 -))) 218 +* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 219 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 220 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 255 255 256 -((( 257 257 For parameter description, please refer to AT command set 258 -))) 259 259 260 260 [[image:1657330452568-615.png]] 261 261 262 262 263 -((( 264 264 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. 265 -))) 266 266 267 267 [[image:1657330472797-498.png]] 268 268 ... ... @@ -271,9 +271,9 @@ 271 271 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 272 272 273 273 274 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) 236 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 275 275 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 276 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 238 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 277 277 278 278 [[image:1657330501006-241.png]] 279 279 ... ... @@ -285,11 +285,11 @@ 285 285 === 2.2.6 Use MQTT protocol to uplink data === 286 286 287 287 288 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) 289 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) 290 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** 291 -* (% style="color:blue" %)**AT+UNAME=UNAME 292 -* (% style="color:blue" %)**AT+PWD=PWD 250 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 251 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 252 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 253 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 254 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 293 293 * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 294 294 * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 295 295 ... ... @@ -339,11 +339,11 @@ 339 339 In this mode, uplink payload includes in total 14 bytes 340 340 341 341 342 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width: 440px" %)343 -|=(% style="width: 60px;" %)(((304 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 305 +|=(% style="width: 80px;" %)((( 344 344 **Size(bytes)** 345 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width:80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width:60px;" %)**1**346 -|(% 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"]]307 +)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1** 308 +|(% 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"]] 347 347 348 348 ((( 349 349 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. ... ... @@ -426,6 +426,10 @@ 426 426 === 2.4.3 Battery Info === 427 427 428 428 ((( 391 +Check the battery voltage for LSE01. 392 +))) 393 + 394 +((( 429 429 Ex1: 0x0B45 = 2885mV 430 430 ))) 431 431 ... ... @@ -471,9 +471,7 @@ 471 471 472 472 Get the distance. Flat object range 280mm - 7500mm. 473 473 474 -((( 475 475 For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 476 -))) 477 477 478 478 ((( 479 479 ((( ... ... @@ -616,9 +616,7 @@ 616 616 == 2.7 Firmware Change Log == 617 617 618 618 619 -((( 620 620 Download URL & Firmware Change log 621 -))) 622 622 623 623 ((( 624 624 [[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/]] ... ... @@ -625,9 +625,7 @@ 625 625 ))) 626 626 627 627 628 -((( 629 629 Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 630 -))) 631 631 632 632 633 633 ... ... @@ -692,7 +692,7 @@ 692 692 And the Life expectation in difference case will be shown on the right. 693 693 ))) 694 694 695 -[[image:image-2022070 9110451-3.png]]655 +[[image:image-20220708141352-7.jpeg]] 696 696 697 697 698 698
- 1657348034241-728.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -127.8 KB - Content
- 1657348284168-431.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -93.5 KB - Content
- 1657350248151-650.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- image-20220709144723-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -413.1 KB - Content
- image-20220709150546-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -333.5 KB - Content