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, 17 added, 0 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
- 1657352914475-252.png
- 1657354294009-643.png
- image-20220709144723-1.png
- image-20220709150546-2.png
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,56 +1,41 @@ 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 -((( 26 -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. 27 -))) 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*. 28 28 29 -((( 30 -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. 31 -))) 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. 32 32 33 -((( 34 -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. 35 -))) 28 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 36 36 37 -((( 38 -NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 39 -))) 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). 40 40 41 -((( 42 -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) 43 -))) 44 44 45 -((( 46 -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. 47 -))) 48 -))) 33 +~* make sure you have NB-IoT coverage locally. 49 49 50 50 51 51 ))) 52 52 53 -[[image:165732 7959271-447.png]]38 +[[image:1657348284168-431.png]] 54 54 55 55 56 56 ... ... @@ -58,18 +58,18 @@ 58 58 59 59 60 60 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 61 -* Ultra low power consumption 62 -* Distance Detection by Ultrasonic technology 63 -* Flat object range 280mm - 7500mm 64 -* Accuracy: ±(1cm+S*0.3%) (S: Distance) 65 -* Cable Length: 25cm 46 +* Monitor Temperature & Humidity via SHT31 66 66 * AT Commands to change parameters 67 67 * Uplink on periodically 68 68 * Downlink to change configure 69 69 * IP66 Waterproof Enclosure 51 +* Ultra-Low Power consumption 52 +* AT Commands to change parameters 70 70 * Micro SIM card slot for NB-IoT SIM 71 71 * 8500mAh Battery for long term use 72 72 56 + 57 + 73 73 == 1.3 Specification == 74 74 75 75 ... ... @@ -89,6 +89,7 @@ 89 89 90 90 (% style="color:#037691" %)**Battery:** 91 91 77 + 92 92 * Li/SOCI2 un-chargeable battery 93 93 * Capacity: 8500mAh 94 94 * Self Discharge: <1% / Year @ 25°C ... ... @@ -95,10 +95,7 @@ 95 95 * Max continuously current: 130mA 96 96 * Max boost current: 2A, 1 second 97 97 98 -(% style="color:#037691" %)**Power Consumption** 99 99 100 -* STOP Mode: 10uA @ 3.3v 101 -* Max transmit power: 350mA@3.3v 102 102 103 103 == 1.4 Applications == 104 104 ... ... @@ -115,22 +115,53 @@ 115 115 116 116 == 1.5 Pin Definitions == 117 117 101 +N95S31B use the mother board from NBSN95 which as below. 118 118 119 -[[image: 1657328609906-564.png]]103 +[[image:image-20220709144723-1.png]] 120 120 121 121 106 +=== 1.5.1 Jumper JP2 === 122 122 123 - = 2. UseNDDS75 tocommunicate withIoTServer =108 +Power on Device when put this jumper. 124 124 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 + 125 125 == 2.1 How it works == 126 126 140 + 127 127 ((( 128 -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. 129 129 ))) 130 130 131 131 132 132 ((( 133 -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: 134 134 ))) 135 135 136 136 ((( ... ... @@ -137,7 +137,7 @@ 137 137 138 138 ))) 139 139 140 -[[image:1657328 659945-416.png]]154 +[[image:1657350248151-650.png]] 141 141 142 142 ((( 143 143 ... ... @@ -144,30 +144,46 @@ 144 144 ))) 145 145 146 146 147 -== 2.2 Configure the N DDS75 ==161 +== 2.2 Configure the N95S31B == 148 148 149 149 164 +=== 2.2.1 Power On N95S31B === 165 + 166 + 167 +[[image:image-20220709150546-2.png]] 168 + 169 + 150 150 === 2.2.1 Test Requirement === 151 151 152 -((( 153 -To use NDDS75 in your city, make sure meet below requirements: 154 -))) 155 155 173 +To use N95S31B in your city, make sure meet below requirements: 174 + 156 156 * Your local operator has already distributed a NB-IoT Network there. 157 -* The local NB-IoT network used the band that NS E01 supports.176 +* The local NB-IoT network used the band that N95S31B supports. 158 158 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 159 159 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 + 160 160 ((( 161 -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 162 -))) 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(%%)) 163 163 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. 164 164 165 -[[image:1657328756309-230.png]] 192 + 193 +))) 166 166 195 +[[image:1657350625843-586.png]] 167 167 168 168 169 -=== 2.2.2 Insert SIM card === 170 170 199 +=== 2.2.3 Insert SIM card === 200 + 171 171 ((( 172 172 Insert the NB-IoT Card get from your provider. 173 173 ))) ... ... @@ -177,19 +177,19 @@ 177 177 ))) 178 178 179 179 180 -[[image:165732 8884227-504.png]]210 +[[image:1657351240556-536.png]] 181 181 182 182 183 183 184 -=== 2.2. 3DDS75 to configure it ===214 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 185 185 186 186 ((( 187 187 ((( 188 -User need to configure DDS75 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 toDDS75 and use AT Commands to configure it, as below.218 +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. 189 189 ))) 190 190 ))) 191 191 192 -[[image: image-20220709092052-2.png]]222 +[[image:1657351312545-300.png]] 193 193 194 194 **Connection:** 195 195 ... ... @@ -209,18 +209,18 @@ 209 209 * Flow Control: (% style="color:green" %)**None** 210 210 211 211 ((( 212 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N DDS75.DDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.242 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input. 213 213 ))) 214 214 215 215 [[image:1657329814315-101.png]] 216 216 217 217 ((( 218 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N DDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]248 +(% 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/]] 219 219 ))) 220 220 221 221 222 222 223 -=== 2.2. 4253 +=== 2.2.5 Use CoAP protocol to uplink data === 224 224 225 225 (% 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/]] 226 226 ... ... @@ -240,10 +240,12 @@ 240 240 ))) 241 241 242 242 ((( 273 + 274 + 243 243 For parameter description, please refer to AT command set 244 244 ))) 245 245 246 -[[image:16573 30452568-615.png]]278 +[[image:1657352146020-183.png]] 247 247 248 248 249 249 ((( ... ... @@ -250,11 +250,11 @@ 250 250 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. 251 251 ))) 252 252 253 -[[image:16573 30472797-498.png]]285 +[[image:1657352185396-303.png]] 254 254 255 255 256 256 257 -=== 2.2. 5289 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 258 258 259 259 260 260 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -261,15 +261,16 @@ 261 261 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 262 262 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 263 263 264 -[[image:16573 30501006-241.png]]296 +[[image:1657352391268-297.png]] 265 265 266 266 267 -[[image:16573 30533775-472.png]]299 +[[image:1657352403317-397.png]] 268 268 269 269 270 270 271 -=== 2.2. 6303 +=== 2.2.7 Use MQTT protocol to uplink data === 272 272 305 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 273 273 274 274 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 275 275 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -276,35 +276,40 @@ 276 276 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 277 277 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 278 278 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 279 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB280 -* (% style="color:blue" %)**AT+SUBTOPIC=N DDS75_SUB312 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 313 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 281 281 282 -[[image:165724 9978444-674.png]]315 +[[image:1657352634421-276.png]] 283 283 284 284 285 -[[image:16573 30723006-866.png]]318 +[[image:1657352645687-385.png]] 286 286 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 +))) 287 287 324 + 288 288 ((( 289 -MQTT protocol has a much high erpower consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.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. 290 290 ))) 291 291 292 292 293 293 294 -=== 2.2. 7331 +=== 2.2.8 Use TCP protocol to uplink data === 295 295 333 +This feature is supported since firmware version v110 296 296 297 297 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 298 298 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 299 299 300 -[[image: image-20220709093918-1.png]]338 +[[image:1657352898400-901.png]] 301 301 302 302 303 -[[image: image-20220709093918-2.png]]341 +[[image:1657352914475-252.png]] 304 304 305 305 306 306 307 -=== 2.2. 8345 +=== 2.2.9 Change Update Interval === 308 308 309 309 User can use below command to change the (% style="color:green" %)**uplink interval**. 310 310 ... ... @@ -311,15 +311,11 @@ 311 311 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 312 312 313 313 ((( 314 - (%style="color:red" %)**NOTE:**352 + 315 315 ))) 316 316 317 -((( 318 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 319 -))) 320 320 321 321 322 - 323 323 == 2.3 Uplink Payload == 324 324 325 325 In this mode, uplink payload includes in total 14 bytes
- 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
- 1657350625843-586.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +93.3 KB - Content
- 1657351240556-536.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +483.6 KB - Content
- 1657351312545-300.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +675.8 KB - Content
- 1657352146020-183.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +264.0 KB - Content
- 1657352185396-303.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +98.3 KB - Content
- 1657352391268-297.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +238.0 KB - Content
- 1657352403317-397.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +547.7 KB - Content
- 1657352634421-276.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +163.6 KB - Content
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +144.8 KB - Content
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +157.0 KB - Content
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +214.7 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