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, 19 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
- 1657520100595-569.png
- image-20220709144723-1.png
- image-20220709150546-2.png
- image-20220709161741-3.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,10 +1,12 @@ 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 + 9 + 8 8 **Table of Contents:** 9 9 10 10 {{toc/}} ... ... @@ -13,57 +13,59 @@ 13 13 14 14 15 15 16 - 17 17 = 1. Introduction = 18 18 19 -== 1.1 What is N DDS75Distance DetectionSensor ==20 +== 1.1 What is N95S31B NB-IoT Sensor Node == 20 20 21 21 ((( 22 22 23 23 24 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 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*. 27 +))) 26 26 29 +((( 30 +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. 31 +))) 27 27 28 -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. 33 +((( 34 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 35 +))) 29 29 37 +((( 38 +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). 39 +))) 30 30 31 -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. 41 +((( 42 + 43 +))) 32 32 33 - 34 -NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 35 - 36 - 37 -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) 38 - 39 - 40 -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. 45 +((( 46 +~* make sure you have NB-IoT coverage locally. 41 41 ))) 42 42 43 43 44 44 ))) 45 45 46 -[[image:165732 7959271-447.png]]52 +[[image:1657348284168-431.png]] 47 47 48 48 49 49 50 50 == 1.2 Features == 51 51 52 - 53 53 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 54 -* Ultra low power consumption 55 -* Distance Detection by Ultrasonic technology 56 -* Flat object range 280mm - 7500mm 57 -* Accuracy: ±(1cm+S*0.3%) (S: Distance) 58 -* Cable Length: 25cm 59 +* Monitor Temperature & Humidity via SHT31 59 59 * AT Commands to change parameters 60 60 * Uplink on periodically 61 61 * Downlink to change configure 62 62 * IP66 Waterproof Enclosure 64 +* Ultra-Low Power consumption 65 +* AT Commands to change parameters 63 63 * Micro SIM card slot for NB-IoT SIM 64 64 * 8500mAh Battery for long term use 65 65 66 66 70 + 67 67 == 1.3 Specification == 68 68 69 69 ... ... @@ -89,12 +89,8 @@ 89 89 * Max continuously current: 130mA 90 90 * Max boost current: 2A, 1 second 91 91 92 -(% style="color:#037691" %)**Power Consumption** 93 93 94 -* STOP Mode: 10uA @ 3.3v 95 -* Max transmit power: 350mA@3.3v 96 96 97 - 98 98 == 1.4 Applications == 99 99 100 100 * Smart Buildings & Home Automation ... ... @@ -108,24 +108,58 @@ 108 108 109 109 110 110 111 -== 1.5 Pin Definitions == 111 +== 1.5 Pin Definitions & Switch == 112 112 113 +N95S31B use the mother board from NBSN95 which as below. 113 113 114 -[[image: 1657328609906-564.png]]115 +[[image:image-20220709144723-1.png]] 115 115 116 116 118 +=== 1.5.1 Jumper JP2 === 117 117 118 - = 2. UseNDDS75 tocommunicate withIoTServer =120 +Power on Device when put this jumper. 119 119 122 + 123 + 124 +=== 1.5.2 BOOT MODE / SW1 === 125 + 126 +((( 127 +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. 128 +))) 129 + 130 +((( 131 +2) Flash: work mode, device starts to work and send out console output for further debug 132 +))) 133 + 134 + 135 + 136 +=== 1.5.3 Reset Button === 137 + 138 +Press to reboot the device. 139 + 140 + 141 + 142 +=== 1.5.4 LED === 143 + 144 +It will flash: 145 + 146 +1. When boot the device in flash mode 147 +1. Send an uplink packet 148 + 149 + 150 + 151 += 2. Use N95S31B to communicate with IoT Server = 152 + 120 120 == 2.1 How it works == 121 121 155 + 122 122 ((( 123 -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.157 +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. 124 124 ))) 125 125 126 126 127 127 ((( 128 -The diagram below shows the working flow in default firmware of N DDS75:162 +The diagram below shows the working flow in default firmware of N95S31B: 129 129 ))) 130 130 131 131 ((( ... ... @@ -132,7 +132,7 @@ 132 132 133 133 ))) 134 134 135 -[[image:1657 328659945-416.png]]169 +[[image:1657520100595-569.png]] 136 136 137 137 ((( 138 138 ... ... @@ -139,30 +139,67 @@ 139 139 ))) 140 140 141 141 142 -== 2.2 Configure the N DDS75 ==176 +== 2.2 Configure the N95S31B == 143 143 144 144 179 +=== 2.2.1 Power On N95S31B === 180 + 181 + 182 +[[image:image-20220709150546-2.png]] 183 + 184 + 145 145 === 2.2.1 Test Requirement === 146 146 187 + 147 147 ((( 148 -To use N DDS75 in your city, make sure meet below requirements:189 +To use N95S31B in your city, make sure meet below requirements: 149 149 ))) 150 150 151 -* Your local operator has already distributed a NB-IoT Network there. 152 -* The local NB-IoT network used the band that NSE01 supports. 153 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 192 +* ((( 193 +Your local operator has already distributed a NB-IoT Network there. 194 +))) 195 +* ((( 196 +The local NB-IoT network used the band that N95S31B supports. 197 +))) 198 +* ((( 199 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 200 +))) 154 154 155 155 ((( 156 -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 server203 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 157 157 ))) 158 158 206 +((( 207 +N95S31B supports different communication protocol such as : 208 +))) 159 159 160 -[[image:1657328756309-230.png]] 210 +((( 211 +* ((( 212 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 213 +))) 214 +* ((( 215 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 216 +))) 217 +* ((( 218 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 219 +))) 220 +* ((( 221 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 222 +))) 161 161 224 +((( 225 +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. 226 +))) 162 162 228 + 229 +))) 163 163 164 - ===2.2.2 Insert SIM card ===231 +[[image:1657350625843-586.png]] 165 165 233 + 234 + 235 +=== 2.2.3 Insert SIM card === 236 + 166 166 ((( 167 167 Insert the NB-IoT Card get from your provider. 168 168 ))) ... ... @@ -172,19 +172,19 @@ 172 172 ))) 173 173 174 174 175 -[[image:165732 8884227-504.png]]246 +[[image:1657351240556-536.png]] 176 176 177 177 178 178 179 -=== 2.2. 3DDS75 to configure it ===250 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 180 180 181 181 ((( 182 182 ((( 183 -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.254 +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. 184 184 ))) 185 185 ))) 186 186 187 -[[image: image-20220709092052-2.png]]258 +[[image:1657351312545-300.png]] 188 188 189 189 **Connection:** 190 190 ... ... @@ -204,18 +204,18 @@ 204 204 * Flow Control: (% style="color:green" %)**None** 205 205 206 206 ((( 207 -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.278 +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. 208 208 ))) 209 209 210 210 [[image:1657329814315-101.png]] 211 211 212 212 ((( 213 -(% 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/]]284 +(% 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/]] 214 214 ))) 215 215 216 216 217 217 218 -=== 2.2. 4289 +=== 2.2.5 Use CoAP protocol to uplink data === 219 219 220 220 (% 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/]] 221 221 ... ... @@ -235,10 +235,12 @@ 235 235 ))) 236 236 237 237 ((( 309 + 310 + 238 238 For parameter description, please refer to AT command set 239 239 ))) 240 240 241 -[[image:16573 30452568-615.png]]314 +[[image:1657352146020-183.png]] 242 242 243 243 244 244 ((( ... ... @@ -245,11 +245,11 @@ 245 245 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. 246 246 ))) 247 247 248 -[[image:16573 30472797-498.png]]321 +[[image:1657352185396-303.png]] 249 249 250 250 251 251 252 -=== 2.2. 5325 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 253 253 254 254 255 255 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -256,15 +256,16 @@ 256 256 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 257 257 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 258 258 259 -[[image:16573 30501006-241.png]]332 +[[image:1657352391268-297.png]] 260 260 261 261 262 -[[image:16573 30533775-472.png]]335 +[[image:1657352403317-397.png]] 263 263 264 264 265 265 266 -=== 2.2. 6339 +=== 2.2.7 Use MQTT protocol to uplink data === 267 267 341 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 268 268 269 269 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 270 270 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -271,35 +271,40 @@ 271 271 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 272 272 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 273 273 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 274 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB**(%%)~/~/Set the sending topic of MQTT275 -* (% style="color:blue" %)**AT+SUBTOPIC=N DDS75_SUB**(%%) ~/~/Set the subscription topic of MQTT348 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 349 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 276 276 277 -[[image:165724 9978444-674.png]]351 +[[image:1657352634421-276.png]] 278 278 279 279 280 -[[image:16573 30723006-866.png]]354 +[[image:1657352645687-385.png]] 281 281 356 +((( 357 +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. 358 +))) 282 282 360 + 283 283 ((( 284 -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.362 +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. 285 285 ))) 286 286 287 287 288 288 289 -=== 2.2. 7367 +=== 2.2.8 Use TCP protocol to uplink data === 290 290 369 +This feature is supported since firmware version v110 291 291 292 292 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 293 293 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 294 294 295 -[[image: image-20220709093918-1.png]]374 +[[image:1657352898400-901.png]] 296 296 297 297 298 -[[image: image-20220709093918-2.png]]377 +[[image:1657352914475-252.png]] 299 299 300 300 301 301 302 -=== 2.2. 8381 +=== 2.2.9 Change Update Interval === 303 303 304 304 User can use below command to change the (% style="color:green" %)**uplink interval**. 305 305 ... ... @@ -306,162 +306,155 @@ 306 306 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 307 307 308 308 ((( 309 - (%style="color:red" %)**NOTE:**388 + 310 310 ))) 311 311 312 -((( 313 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 314 -))) 315 315 316 316 317 - 318 318 == 2.3 Uplink Payload == 319 319 320 -In this mode, uplink payload includes in total 14 bytes 321 321 396 +((( 397 +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. 398 +))) 322 322 323 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 324 -|=(% style="width: 60px;" %)((( 325 -**Size(bytes)** 326 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %)**2**|=(% style="width: 60px;" %)**1** 327 -|(% 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"]] 328 328 329 329 ((( 330 - If we use the MQTT client tosubscribeto this MQTT topic, wecan see the following information when the NDDS751 uplink data.402 +For example: 331 331 ))) 332 332 405 +((( 406 + (% 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. 407 +))) 333 333 334 -[[image:1657331036973-987.png]] 335 335 336 336 ((( 337 -The payload is ASCIIstring,representative sameHEX:411 +The uplink payloads are composed in ASCII String. For example: 338 338 ))) 339 339 340 340 ((( 341 -0 x72403155615900640c6c19029200where:415 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 342 342 ))) 343 343 344 - *(((345 - DeviceID:0x724031556159=724031556159418 +((( 419 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 346 346 ))) 347 -* ((( 348 -Version: 0x0064=100=1.0.0 421 + 422 + 423 +((( 424 +(% style="color:red" %)**NOTE:** 349 349 ))) 350 350 351 -* ((( 352 -BAT: 0x0c6c = 3180 mV = 3.180V 427 +(% style="color:red" %) 428 +1. ((( 429 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 353 353 ))) 354 - *(((355 - Signal:0x19=25431 +1. ((( 432 +By default, the device will send an uplink message every 1 hour. 356 356 ))) 357 -* ((( 358 -Distance: 0x0292= 658 mm 359 -))) 360 -* ((( 361 -Interrupt: 0x00 = 0 362 362 435 +=== 2.3.1 Payload Analyze === 363 363 437 +N95S31B uplink payload includes in total 21 bytes 364 364 365 - 366 -))) 367 367 368 - ==2.4 PayloadExplanation andSensorInterface==369 - 370 - 371 -=== 2 .4.1DeviceID===372 - 440 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 441 +|=(% style="width: 60px;" %)((( 442 +**Size(bytes)** 443 +)))|=(% 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** 444 +|(% 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" %)((( 373 373 ((( 374 - By default, theDeviceID equal to thelast6bytes of IMEI.446 +Reserve/ Same as NBSN95 CFGMOD=1 375 375 ))) 376 376 377 377 ((( 378 - Usercanuse (% style="color:blue" %)**AT+DEUI**(%%)toset Device ID450 +No function here. 379 379 ))) 380 - 452 +)))|(% style="width:77px" %)((( 381 381 ((( 382 - **Example:**454 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 383 383 ))) 384 384 385 385 ((( 386 - AT+DEUI=A84041F15612458 +By SHT31 387 387 ))) 388 - 460 +)))|(% style="width:80px" %)((( 389 389 ((( 390 - The Device ID is storednane-erasearea, Upgradethe firmwareor run **AT+FDR** won'terase Device ID.462 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 391 391 ))) 392 392 393 - 394 - 395 -=== 2.4.2 Version Info === 396 - 397 397 ((( 398 - Specifythe software version: 0x64=100, means firmware version 1.00.466 +By SHT31 399 399 ))) 468 +))) 400 400 401 401 ((( 402 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 471 +((( 472 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 403 403 ))) 474 +))) 404 404 405 405 477 +[[image:1657354294009-643.png]] 406 406 407 -=== 2.4.3 Battery Info === 408 408 409 -((( 410 -Ex1: 0x0B45 = 2885mV 411 -))) 480 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 412 412 413 -((( 414 -Ex2: 0x0B49 = 2889mV 415 -))) 482 +* Device ID: 0x724031607457 = 724031607457 483 +* Version: 0x006e=110=1.1.0 416 416 485 +* BAT: 0x0ccd = 3277 mV = 3.277V 486 +* Signal: 0x1b = 27 487 +* Model: 0x01 = 1 488 +* 0x00dc000ccc= reserve, ignore in N95S31B 489 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 490 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 417 417 418 - 419 -=== 2.4.4 Signal Strength === 420 - 421 421 ((( 422 - NB-IoTNetwork signal Strength.493 + 423 423 ))) 424 424 425 425 ((( 426 - **Ex1:0x1d = 29**497 + 427 427 ))) 428 428 500 + 501 +=== 2.3.2 Device ID === 502 + 429 429 ((( 430 - (% style="color:blue"%)**0**(%%)-113dBmorless504 +By default, the Device ID equal to the last 6 bytes of IMEI. 431 431 ))) 432 432 433 433 ((( 434 -(% style="color:blue" %)** 1**(%%)-111dBm508 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 435 435 ))) 436 436 437 437 ((( 438 - (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm512 +**Example:** 439 439 ))) 440 440 441 441 ((( 442 - (% style="color:blue" %)**31** (%%) -51dBm or greater516 +AT+DEUI=A84041F15612 443 443 ))) 444 444 445 445 ((( 446 - (%style="color:blue"%)**99**(%%)Notknownor notdetectable520 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 447 447 ))) 448 448 449 449 450 450 451 -=== 2. 4.5Distance===525 +=== 2.3.3 Version Info === 452 452 453 -Get the distance. Flat object range 280mm - 7500mm. 527 +((( 528 +These bytes include the hardware and software version. 529 +))) 454 454 455 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 456 - 457 457 ((( 458 -((( 459 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 532 +Higher byte: Specify hardware version: always 0x00 for N95S31B 460 460 ))) 461 -))) 462 462 463 463 ((( 464 - 536 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 465 465 ))) 466 466 467 467 ((( ... ... @@ -468,63 +468,79 @@ 468 468 469 469 ))) 470 470 471 -=== 2.4.6 Digital Interrupt === 472 - 473 473 ((( 474 - Digital Interruptrefers topin (% style="color:blue"%)**GPIO_EXTI**(%%),andtherearedifferent triggermethods. When thereisa trigger, theNDDS75 will send a packetto theserver.544 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 475 475 ))) 476 476 477 477 ((( 478 - Thecommand is:548 + 479 479 ))) 480 480 551 + 552 +=== 2.3.4 Battery Info === 553 + 481 481 ((( 482 - (% style="color:blue"%)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**555 +Ex1: 0x0B45 = 2885mV 483 483 ))) 484 484 485 - 486 486 ((( 487 - Thelowerfourbits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.559 +Ex2: 0x0B49 = 2889mV 488 488 ))) 489 489 490 490 563 + 564 +=== 2.3.5 Signal Strength === 565 + 491 491 ((( 492 - Example:567 +NB-IoT Network signal Strength. 493 493 ))) 494 494 495 495 ((( 496 - 0x(00):Normaluplinkpacket.571 +**Ex1: 0x1d = 29** 497 497 ))) 498 498 499 499 ((( 500 - 0x(01):InterruptUplinkPacket.575 +(% style="color:blue" %)**0**(%%) -113dBm or less 501 501 ))) 502 502 503 - 504 - 505 -=== 2.4.7 +5V Output === 506 - 507 507 ((( 508 - NDDS75willenable +5Voutputbeforeallsamplinganddisablethe+5vafterall sampling.579 +(% style="color:blue" %)**1**(%%) -111dBm 509 509 ))) 510 510 511 - 512 512 ((( 513 - The5V output timean be controlledbyAT Command.583 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 514 514 ))) 515 515 516 516 ((( 517 -(% style="color:blue" %)** AT+5VT=1000**587 +(% style="color:blue" %)**31** (%%) -51dBm or greater 518 518 ))) 519 519 520 520 ((( 521 - Meansset5V valid timetohave 1000ms. Sothereal5V outputwillactuallyhave1000ms+samplingtime for othersensors.591 +(% style="color:blue" %)**99** (%%) Not known or not detectable 522 522 ))) 523 523 524 524 525 525 526 -== 2. 5Downlink Payload ==596 +=== 2.3.6 Temperature & Humidity === 527 527 598 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 599 + 600 +[[image:image-20220709161741-3.png]] 601 + 602 + 603 +Convert the read byte to decimal and divide it by ten. 604 + 605 + 606 +**Example:** 607 + 608 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 609 + 610 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 611 + 612 + 613 + 614 +== 2.4 Downlink Payload == 615 + 528 528 By default, NDDS75 prints the downlink payload to console port. 529 529 530 530 [[image:image-20220709100028-1.png]] ... ... @@ -575,47 +575,16 @@ 575 575 576 576 577 577 578 -== 2. 6LED Indicator ==666 +== 2.5 Battery Analysis == 579 579 668 +=== 2.5.1 Battery Type === 580 580 581 -The NDDS75 has an internal LED which is to show the status of different state. 582 582 583 - 584 -* 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) 585 -* Then the LED will be on for 1 second means device is boot normally. 586 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 587 -* For each uplink probe, LED will be on for 500ms. 588 - 589 589 ((( 590 - 672 +The N95S31B 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. 591 591 ))) 592 592 593 - 594 - 595 -== 2.7 Firmware Change Log == 596 - 597 - 598 -Download URL & Firmware Change log 599 - 600 600 ((( 601 -[[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/]] 602 -))) 603 - 604 - 605 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 606 - 607 - 608 - 609 -== 2.8 Battery Analysis == 610 - 611 -=== 2.8.1 Battery Type === 612 - 613 - 614 -((( 615 -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. 616 -))) 617 - 618 -((( 619 619 The battery is designed to last for several years depends on the actually use environment and update interval. 620 620 ))) 621 621 ... ... @@ -633,56 +633,35 @@ 633 633 634 634 635 635 636 -=== 2. 8.2 Power consumption Analyze ===693 +=== 2.5.2 Power consumption Analyze === 637 637 638 638 ((( 639 - Draginobatterypoweredproductareall runsinLow Powermode.Wehave an update battery calculatorwhichbaseonthe measurement oftherealdevice. User can usethis calculatortocheck the batterylifeandcalculatethe batterylifeifwant tousedifferenttransmit interval.696 +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/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project. 640 640 ))) 641 641 642 - 643 643 ((( 644 - Instructionto use as below:700 + 645 645 ))) 646 646 647 -((( 648 -(% 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/]] 649 -))) 650 650 704 +=== 2.5.3 Battery Note === 651 651 652 652 ((( 653 - (%style="color:blue"%)**Step2:**(%%)Open it andchoose707 +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 uplink data, then the battery life may be decreased. 654 654 ))) 655 655 656 -* ((( 657 -Product Model 658 -))) 659 -* ((( 660 -Uplink Interval 661 -))) 662 -* ((( 663 -Working Mode 664 -))) 665 665 666 -((( 667 -And the Life expectation in difference case will be shown on the right. 668 -))) 669 669 670 - [[image:image-20220709110451-3.png]]712 +=== 2.5.4 Replace the battery === 671 671 672 672 673 - 674 -=== 2.8.3 Battery Note === 675 - 676 676 ((( 677 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.716 +You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board. 678 678 ))) 679 679 680 680 681 - 682 -=== 2.8.4 Replace the battery === 683 - 684 684 ((( 685 -The default battery pack of N DDS75 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).721 +The default battery pack of N95S31B 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). 686 686 ))) 687 687 688 688 ... ... @@ -705,7 +705,7 @@ 705 705 706 706 == 4.1 Access AT Commands == 707 707 708 -See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N DDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]744 +See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]] 709 709 710 710 711 711 AT+<CMD>? : Help on <CMD> ... ... @@ -793,8 +793,12 @@ 793 793 ))) 794 794 795 795 ((( 796 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 832 + 833 + 834 +((( 835 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 797 797 ))) 837 +))) 798 798 799 799 800 800 ... ... @@ -825,7 +825,7 @@ 825 825 = 7. Order Info = 826 826 827 827 828 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**868 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 829 829 830 830 831 831 (% class="wikigeneratedid" %) ... ... @@ -840,7 +840,7 @@ 840 840 841 841 (% style="color:#037691" %)**Package Includes**: 842 842 843 -* NS E01DistanceDetectSensorNode x 1883 +* N95S31B NB-IoT Temperature and Humidity Sensor 844 844 * External antenna x 1 845 845 ))) 846 846 ... ... @@ -849,11 +849,10 @@ 849 849 850 850 (% style="color:#037691" %)**Dimension and weight**: 851 851 852 - 853 853 * Device Size: 13.0 x 5 x 4.5 cm 854 854 * Device Weight: 150g 855 -* Package Size / pcs : 1 5x12x 5.5cm856 -* Weight / pcs : 220g894 +* Package Size / pcs : 14.0 x 8x 5 cm 895 +* Weight / pcs : 180g 857 857 ))) 858 858 859 859 (((
- 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
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 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
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +111.2 KB - Content