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, 15 removed)
- 1657348034241-728.png
- 1657348284168-431.png
- 1657350248151-650.png
- 1657350625843-586.png
- 1657351240556-536.png
- 1657351312545-300.png
- 1657352146020-183.png
- 1657352185396-303.png
- 1657352391268-297.png
- 1657352403317-397.png
- 1657352634421-276.png
- 1657352645687-385.png
- 1657352898400-901.png
- image-20220709144723-1.png
- image-20220709150546-2.png
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,41 +1,39 @@ 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:16573 48284168-431.png]]36 +[[image:1657327959271-447.png]] 39 39 40 40 41 41 ... ... @@ -43,13 +43,15 @@ 43 43 44 44 45 45 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 46 -* Monitor Temperature & Humidity via SHT31 44 +* Ultra low power consumption 45 +* Distance Detection by Ultrasonic technology 46 +* Flat object range 280mm - 7500mm 47 +* Accuracy: ±(1cm+S*0.3%) (S: Distance) 48 +* 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 ... ... @@ -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,13 @@ 81 81 * Max continuously current: 130mA 82 82 * Max boost current: 2A, 1 second 83 83 83 +(% style="color:#037691" %)**Power Consumption** 84 84 85 +* STOP Mode: 10uA @ 3.3v 86 +* Max transmit power: 350mA@3.3v 85 85 88 + 89 + 86 86 == 1.4 Applications == 87 87 88 88 * Smart Buildings & Home Automation ... ... @@ -98,53 +98,22 @@ 98 98 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]]106 +[[image:1657328609906-564.png]] 104 104 105 105 106 -=== 1.5.1 Jumper JP2 === 107 107 108 - PoweronDevice when putthisjumper.110 += 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.115 +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:120 +The diagram below shows the working flow in default firmware of NDDS75: 148 148 ))) 149 149 150 150 ((( ... ... @@ -151,7 +151,7 @@ 151 151 152 152 ))) 153 153 154 -[[image:16573 50248151-650.png]]127 +[[image:1657328659945-416.png]] 155 155 156 156 ((( 157 157 ... ... @@ -158,46 +158,30 @@ 158 158 ))) 159 159 160 160 161 -== 2.2 Configure the N 95S31B==134 +== 2.2 Configure the NDDS75 == 162 162 163 163 164 -=== 2.2.1 Power On N95S31B === 165 - 166 - 167 -[[image:image-20220709150546-2.png]] 168 - 169 - 170 170 === 2.2.1 Test Requirement === 171 171 139 +((( 140 +To use NDDS75 in your city, make sure meet below requirements: 141 +))) 172 172 173 -To use N95S31B in your city, make sure meet below requirements: 174 - 175 175 * Your local operator has already distributed a NB-IoT Network there. 176 -* The local NB-IoT network used the band that N 95S31Bsupports.144 +* The local NB-IoT network used the band that NSE01 supports. 177 177 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 178 178 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 - 184 184 ((( 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 - 148 +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 193 193 ))) 194 194 195 -[[image:1657350625843-586.png]] 196 196 152 +[[image:1657328756309-230.png]] 197 197 198 198 199 -=== 2.2.3 Insert SIM card === 200 200 156 +=== 2.2.2 Insert SIM card === 157 + 201 201 ((( 202 202 Insert the NB-IoT Card get from your provider. 203 203 ))) ... ... @@ -207,19 +207,19 @@ 207 207 ))) 208 208 209 209 210 -[[image:16573 51240556-536.png]]167 +[[image:1657328884227-504.png]] 211 211 212 212 213 213 214 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===171 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 215 215 216 216 ((( 217 217 ((( 218 -User need to configure 95S31Bvia serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31Bsupport AT Commands, user can use a USB to TTL adapter to connect to95S31Band use AT Commands to configure it, as below.175 +User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below. 219 219 ))) 220 220 ))) 221 221 222 -[[image: 1657351312545-300.png]]179 +[[image:image-20220709092052-2.png]] 223 223 224 224 **Connection:** 225 225 ... ... @@ -239,18 +239,18 @@ 239 239 * Flow Control: (% style="color:green" %)**None** 240 240 241 241 ((( 242 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N 95S31B.95S31Bwill output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.199 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input. 243 243 ))) 244 244 245 245 [[image:1657329814315-101.png]] 246 246 247 247 ((( 248 -(% style="color:red" %)Note: the valid AT Commands can be found at: 95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]205 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]] 249 249 ))) 250 250 251 251 252 252 253 -=== 2.2. 5Use CoAP protocol to uplink data ===210 +=== 2.2.4 Use CoAP protocol to uplink data === 254 254 255 255 (% 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/]] 256 256 ... ... @@ -270,23 +270,19 @@ 270 270 ))) 271 271 272 272 ((( 273 - 274 - 275 275 For parameter description, please refer to AT command set 276 276 ))) 277 277 278 -[[image:1657352 146020-183.png]]233 +[[image:1657330452568-615.png]] 279 279 280 280 281 -((( 282 282 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. 283 -))) 284 284 285 -[[image:16573 52185396-303.png]]238 +[[image:1657330472797-498.png]] 286 286 287 287 288 288 289 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===242 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 290 290 291 291 292 292 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -293,37 +293,32 @@ 293 293 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 294 294 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 295 295 296 -[[image:16573 52391268-297.png]]249 +[[image:1657330501006-241.png]] 297 297 298 298 299 -[[image:16573 52403317-397.png]]252 +[[image:1657330533775-472.png]] 300 300 301 301 302 302 303 -=== 2.2. 7Use MQTT protocol to uplink data ===256 +=== 2.2.6 Use MQTT protocol to uplink data === 304 304 305 -N95S31B supports only plain MQTT now it doesn’t support TLS and other related encryption. 306 306 307 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) 308 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) 309 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** 310 -* (% style="color:blue" %)**AT+UNAME=UNAME 311 -* (% style="color:blue" %)**AT+PWD=PWD 312 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527313 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527259 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 260 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 261 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 262 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 263 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 264 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 265 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 314 314 315 -[[image:1657 352634421-276.png]]267 +[[image:1657249978444-674.png]] 316 316 317 317 318 -[[image:16573 52645687-385.png]]270 +[[image:1657330723006-866.png]] 319 319 320 -((( 321 -To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period. 322 -))) 323 323 324 - 325 325 ((( 326 -MQTT protocol has a much high -power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.274 +MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 327 327 ))) 328 328 329 329 ... ... @@ -362,10 +362,10 @@ 362 362 In this mode, uplink payload includes in total 14 bytes 363 363 364 364 365 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width: 440px" %)366 -|=(% style="width: 60px;" %)(((313 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 314 +|=(% style="width: 80px;" %)((( 367 367 **Size(bytes)** 368 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width:80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width:60px;" %)**1**316 +)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1** 369 369 |(% 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 371 ((( ... ... @@ -494,9 +494,7 @@ 494 494 495 495 Get the distance. Flat object range 280mm - 7500mm. 496 496 497 -((( 498 498 For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 499 -))) 500 500 501 501 ((( 502 502 ((( ... ... @@ -639,9 +639,7 @@ 639 639 == 2.7 Firmware Change Log == 640 640 641 641 642 -((( 643 643 Download URL & Firmware Change log 644 -))) 645 645 646 646 ((( 647 647 [[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/]] ... ... @@ -648,9 +648,7 @@ 648 648 ))) 649 649 650 650 651 -((( 652 652 Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 653 -))) 654 654 655 655 656 656
- 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
- 1657350625843-586.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -93.3 KB - Content
- 1657351240556-536.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -483.6 KB - Content
- 1657351312545-300.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -675.8 KB - Content
- 1657352146020-183.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -264.0 KB - Content
- 1657352185396-303.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -98.3 KB - Content
- 1657352391268-297.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -238.0 KB - Content
- 1657352403317-397.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -547.7 KB - Content
- 1657352634421-276.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -163.6 KB - Content
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -144.8 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