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 (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 15 added, 0 removed)
- 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-20220709150546-2.png
- image-20220709161741-3.png
Details
- Page properties
-
- Content
-
... ... @@ -9,6 +9,7 @@ 9 9 10 10 **Table of Contents:** 11 11 12 +{{toc/}} 12 12 13 13 14 14 ... ... @@ -21,16 +21,29 @@ 21 21 ((( 22 22 23 23 25 +((( 24 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*. 27 +))) 25 25 29 +((( 26 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. 31 +))) 27 27 33 +((( 28 28 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 35 +))) 29 29 37 +((( 30 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). 39 +))) 31 31 41 +((( 42 + 43 +))) 32 32 45 +((( 33 33 ~* make sure you have NB-IoT coverage locally. 47 +))) 34 34 35 35 36 36 ))) ... ... @@ -41,7 +41,6 @@ 41 41 42 42 == 1.2 Features == 43 43 44 - 45 45 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 46 46 * Monitor Temperature & Humidity via SHT31 47 47 * AT Commands to change parameters ... ... @@ -53,8 +53,6 @@ 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 ... ... @@ -81,8 +81,6 @@ 81 81 * Max continuously current: 130mA 82 82 * Max boost current: 2A, 1 second 83 83 84 - 85 - 86 86 == 1.4 Applications == 87 87 88 88 * Smart Buildings & Home Automation ... ... @@ -130,9 +130,6 @@ 130 130 1. When boot the device in flash mode 131 131 1. Send an uplink packet 132 132 133 - 134 - 135 - 136 136 = 2. Use N95S31B to communicate with IoT Server = 137 137 138 138 == 2.1 How it works == ... ... @@ -151,7 +151,7 @@ 151 151 152 152 ))) 153 153 154 -[[image:1657328 659945-416.png]]160 +[[image:1657350248151-650.png]] 155 155 156 156 ((( 157 157 ... ... @@ -158,30 +158,45 @@ 158 158 ))) 159 159 160 160 161 -== 2.2 Configure the N DDS75 ==167 +== 2.2 Configure the N95S31B == 162 162 163 163 170 +=== 2.2.1 Power On N95S31B === 171 + 172 + 173 +[[image:image-20220709150546-2.png]] 174 + 175 + 164 164 === 2.2.1 Test Requirement === 165 165 166 -((( 167 -To use NDDS75 in your city, make sure meet below requirements: 168 -))) 169 169 179 +To use N95S31B in your city, make sure meet below requirements: 180 + 170 170 * Your local operator has already distributed a NB-IoT Network there. 171 -* The local NB-IoT network used the band that NS E01 supports.182 +* The local NB-IoT network used the band that N95S31B supports. 172 172 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 173 173 185 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 186 + 187 +N95S31B supports different communication protocol such as : 188 + 174 174 ((( 175 -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 176 -))) 190 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 191 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 192 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 193 +* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 177 177 195 +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. 178 178 179 -[[image:1657328756309-230.png]] 197 + 198 +))) 180 180 200 +[[image:1657350625843-586.png]] 181 181 182 182 183 -=== 2.2.2 Insert SIM card === 184 184 204 +=== 2.2.3 Insert SIM card === 205 + 185 185 ((( 186 186 Insert the NB-IoT Card get from your provider. 187 187 ))) ... ... @@ -191,19 +191,19 @@ 191 191 ))) 192 192 193 193 194 -[[image:165732 8884227-504.png]]215 +[[image:1657351240556-536.png]] 195 195 196 196 197 197 198 -=== 2.2. 3DDS75 to configure it ===219 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 199 199 200 200 ((( 201 201 ((( 202 -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.223 +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. 203 203 ))) 204 204 ))) 205 205 206 -[[image: image-20220709092052-2.png]]227 +[[image:1657351312545-300.png]] 207 207 208 208 **Connection:** 209 209 ... ... @@ -223,18 +223,18 @@ 223 223 * Flow Control: (% style="color:green" %)**None** 224 224 225 225 ((( 226 -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.247 +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. 227 227 ))) 228 228 229 229 [[image:1657329814315-101.png]] 230 230 231 231 ((( 232 -(% 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/]]253 +(% 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/]] 233 233 ))) 234 234 235 235 236 236 237 -=== 2.2. 4258 +=== 2.2.5 Use CoAP protocol to uplink data === 238 238 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 ... ... @@ -254,10 +254,12 @@ 254 254 ))) 255 255 256 256 ((( 278 + 279 + 257 257 For parameter description, please refer to AT command set 258 258 ))) 259 259 260 -[[image:16573 30452568-615.png]]283 +[[image:1657352146020-183.png]] 261 261 262 262 263 263 ((( ... ... @@ -264,11 +264,11 @@ 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 265 ))) 266 266 267 -[[image:16573 30472797-498.png]]290 +[[image:1657352185396-303.png]] 268 268 269 269 270 270 271 -=== 2.2. 5294 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 272 272 273 273 274 274 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -275,15 +275,16 @@ 275 275 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 276 276 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 277 277 278 -[[image:16573 30501006-241.png]]301 +[[image:1657352391268-297.png]] 279 279 280 280 281 -[[image:16573 30533775-472.png]]304 +[[image:1657352403317-397.png]] 282 282 283 283 284 284 285 -=== 2.2. 6308 +=== 2.2.7 Use MQTT protocol to uplink data === 286 286 310 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 287 287 288 288 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 289 289 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -290,35 +290,40 @@ 290 290 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 291 291 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 292 292 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 293 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB**(%%)~/~/Set the sending topic of MQTT294 -* (% style="color:blue" %)**AT+SUBTOPIC=N DDS75_SUB**(%%) ~/~/Set the subscription topic of MQTT317 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 318 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 295 295 296 -[[image:165724 9978444-674.png]]320 +[[image:1657352634421-276.png]] 297 297 298 298 299 -[[image:16573 30723006-866.png]]323 +[[image:1657352645687-385.png]] 300 300 325 +((( 326 +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. 327 +))) 301 301 329 + 302 302 ((( 303 -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.331 +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. 304 304 ))) 305 305 306 306 307 307 308 -=== 2.2. 7336 +=== 2.2.8 Use TCP protocol to uplink data === 309 309 338 +This feature is supported since firmware version v110 310 310 311 311 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 312 312 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 313 313 314 -[[image: image-20220709093918-1.png]]343 +[[image:1657352898400-901.png]] 315 315 316 316 317 -[[image: image-20220709093918-2.png]]346 +[[image:1657352914475-252.png]] 318 318 319 319 320 320 321 -=== 2.2. 8350 +=== 2.2.9 Change Update Interval === 322 322 323 323 User can use below command to change the (% style="color:green" %)**uplink interval**. 324 324 ... ... @@ -325,227 +325,207 @@ 325 325 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 326 326 327 327 ((( 328 - (%style="color:red" %)**NOTE:**357 + 329 329 ))) 330 330 331 -((( 332 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 333 -))) 334 334 335 335 336 - 337 337 == 2.3 Uplink Payload == 338 338 339 -In this mode, uplink payload includes in total 14 bytes 340 340 365 +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. 341 341 342 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 343 -|=(% style="width: 60px;" %)((( 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"]] 347 347 348 -((( 349 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 350 -))) 368 +For example: 351 351 370 + (% 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. 352 352 353 -[[image:1657331036973-987.png]] 354 354 355 -((( 356 -The payload is ASCII string, representative same HEX: 357 -))) 373 +The uplink payloads are composed in ASCII String. For example: 358 358 359 -((( 360 -0x72403155615900640c6c19029200 where: 361 -))) 375 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 362 362 363 -* ((( 364 -Device ID: 0x724031556159 = 724031556159 365 -))) 366 -* ((( 367 -Version: 0x0064=100=1.0.0 368 -))) 377 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 369 369 370 -* ((( 371 -BAT: 0x0c6c = 3180 mV = 3.180V 372 -))) 373 -* ((( 374 -Signal: 0x19 = 25 375 -))) 376 -* ((( 377 -Distance: 0x0292= 658 mm 378 -))) 379 -* ((( 380 -Interrupt: 0x00 = 0 381 381 380 +(% style="color:red" %)**NOTE:** 382 382 382 +(% style="color:red" %) 383 +1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 384 +1. By default, the device will send an uplink message every 1 hour. 383 383 384 - 385 -))) 386 386 387 -== 2. 4PayloadExplanation and SensorInterface==387 +=== 2.3.1 Payload Analyze === 388 388 389 +N95S31B uplink payload includes in total 21 bytes 389 389 390 -=== 2.4.1 Device ID === 391 391 392 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 393 +|=(% style="width: 60px;" %)((( 394 +**Size(bytes)** 395 +)))|=(% 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** 396 +|(% 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" %)((( 392 392 ((( 393 - By default, theDeviceID equal to thelast6bytes of IMEI.398 +Reserve/ Same as NBSN95 CFGMOD=1 394 394 ))) 395 395 396 396 ((( 397 - Usercanuse (% style="color:blue" %)**AT+DEUI**(%%)toset Device ID402 +No function here. 398 398 ))) 399 - 404 +)))|(% style="width:77px" %)((( 400 400 ((( 401 - **Example:**406 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 402 402 ))) 403 403 404 404 ((( 405 - AT+DEUI=A84041F15612410 +By SHT31 406 406 ))) 407 - 412 +)))|(% style="width:80px" %)((( 408 408 ((( 409 - The Device ID is storednane-erasearea, Upgradethe firmwareor run **AT+FDR** won'terase Device ID.414 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 410 410 ))) 411 411 412 - 413 - 414 -=== 2.4.2 Version Info === 415 - 416 416 ((( 417 - Specifythe software version: 0x64=100, means firmware version 1.00.418 +By SHT31 418 418 ))) 420 +))) 419 419 420 420 ((( 421 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 423 +((( 424 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 422 422 ))) 426 +))) 423 423 424 424 429 +[[image:1657354294009-643.png]] 425 425 426 -=== 2.4.3 Battery Info === 427 427 432 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 433 + 434 +* Device ID: 0x724031607457 = 724031607457 435 +* Version: 0x006e=110=1.1.0 436 + 437 +* BAT: 0x0ccd = 3277 mV = 3.277V 438 +* Signal: 0x1b = 27 439 +* Model: 0x01 = 1 440 +* 0x00dc000ccc= reserve, ignore in N95S31B 441 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 442 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 443 + 428 428 ((( 429 - Ex1:0x0B45 = 2885mV445 + 430 430 ))) 431 431 432 432 ((( 433 - Ex2:0x0B49 = 2889mV449 + 434 434 ))) 435 435 436 436 453 +=== 2.3.2 Device ID === 437 437 438 -=== 2.4.4 Signal Strength === 439 - 440 440 ((( 441 - NB-IoTNetworksignalStrength.456 +By default, the Device ID equal to the last 6 bytes of IMEI. 442 442 ))) 443 443 444 444 ((( 445 - **Ex1:0x1d=29**460 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 446 446 ))) 447 447 448 448 ((( 449 - (% style="color:blue" %)**0**(%%) -113dBmorless464 +**Example:** 450 450 ))) 451 451 452 452 ((( 453 - (% style="color:blue" %)**1**(%%) -111dBm468 +AT+DEUI=A84041F15612 454 454 ))) 455 455 456 456 ((( 457 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm472 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 458 458 ))) 459 459 460 -((( 461 -(% style="color:blue" %)**31** (%%) -51dBm or greater 462 -))) 463 463 464 -((( 465 -(% style="color:blue" %)**99** (%%) Not known or not detectable 466 -))) 467 467 477 +=== 2.3.3 Version Info === 468 468 469 469 470 - ===2.4.5Distance===480 +These bytes include the hardware and software version. 471 471 472 - Get thedistance.Flat objectrange280mm-7500mm.482 +Higher byte: Specify hardware version: always 0x00 for N95S31B 473 473 474 -((( 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 -))) 484 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 477 477 486 + 487 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 488 + 478 478 ((( 479 -((( 480 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 490 + 481 481 ))) 482 -))) 483 483 493 + 494 +=== 2.3.4 Battery Info === 495 + 484 484 ((( 485 - 497 +Ex1: 0x0B45 = 2885mV 486 486 ))) 487 487 488 488 ((( 489 - 501 +Ex2: 0x0B49 = 2889mV 490 490 ))) 491 491 492 -=== 2.4.6 Digital Interrupt === 493 493 505 + 506 +=== 2.3.5 Signal Strength === 507 + 494 494 ((( 495 - DigitalInterrupt refers topin (% style="color:blue" %)**GPIO_EXTI**(%%),and there are differenttrigger methods. When thereisa trigger, the NDDS75 will sendapacketto the server.509 +NB-IoT Network signal Strength. 496 496 ))) 497 497 498 498 ((( 499 - Thecommandis:513 +**Ex1: 0x1d = 29** 500 500 ))) 501 501 502 502 ((( 503 -(% style="color:blue" %)** AT+INTMOD=3**(%%)~/~/(moreinfoaboutINMODpleaserefer[[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**517 +(% style="color:blue" %)**0**(%%) -113dBm or less 504 504 ))) 505 505 506 - 507 507 ((( 508 - Thelower four bitsofthis data field shows if this packet is generatedby interruptornot.Clickhereforthehardwareandsoftware set up.521 +(% style="color:blue" %)**1**(%%) -111dBm 509 509 ))) 510 510 511 - 512 512 ((( 513 - Example:525 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 514 514 ))) 515 515 516 516 ((( 517 - 0x(00):Normalplinkpacket.529 +(% style="color:blue" %)**31** (%%) -51dBm or greater 518 518 ))) 519 519 520 520 ((( 521 - 0x(01):InterruptUplinkPacket.533 +(% style="color:blue" %)**99** (%%) Not known or not detectable 522 522 ))) 523 523 524 524 525 525 526 -=== 2. 4.7+5VOutput===538 +=== 2.3.6 Temperature & Humidity === 527 527 528 -((( 529 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 530 -))) 540 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 531 531 542 +[[image:image-20220709161741-3.png]] 532 532 533 -((( 534 -The 5V output time can be controlled by AT Command. 535 -))) 536 536 537 -((( 538 -(% style="color:blue" %)**AT+5VT=1000** 539 -))) 545 +Convert the read byte to decimal and divide it by ten. 540 540 541 -((( 542 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 543 -))) 544 544 548 +**Example:** 545 545 550 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 546 546 547 - ==2.5Downlink Payload==552 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 548 548 554 + 555 + 556 +== 2.4 Downlink Payload == 557 + 549 549 By default, NDDS75 prints the downlink payload to console port. 550 550 551 551 [[image:image-20220709100028-1.png]] ... ... @@ -596,51 +596,16 @@ 596 596 597 597 598 598 599 -== 2. 6LED Indicator ==608 +== 2.5 Battery Analysis == 600 600 610 +=== 2.5.1 Battery Type === 601 601 602 -The NDDS75 has an internal LED which is to show the status of different state. 603 603 604 - 605 -* 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) 606 -* Then the LED will be on for 1 second means device is boot normally. 607 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 608 -* For each uplink probe, LED will be on for 500ms. 609 - 610 610 ((( 611 - 614 +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. 612 612 ))) 613 613 614 - 615 - 616 -== 2.7 Firmware Change Log == 617 - 618 - 619 619 ((( 620 -Download URL & Firmware Change log 621 -))) 622 - 623 -((( 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 -))) 626 - 627 - 628 -((( 629 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 630 -))) 631 - 632 - 633 - 634 -== 2.8 Battery Analysis == 635 - 636 -=== 2.8.1 Battery Type === 637 - 638 - 639 -((( 640 -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. 641 -))) 642 - 643 -((( 644 644 The battery is designed to last for several years depends on the actually use environment and update interval. 645 645 ))) 646 646 ... ... @@ -658,56 +658,35 @@ 658 658 659 659 660 660 661 -=== 2. 8.2 Power consumption Analyze ===635 +=== 2.5.2 Power consumption Analyze === 662 662 663 663 ((( 664 - Draginobatterypoweredproductareall runsinLow Powermode.Wehave an update battery calculatorwhichbaseonthe measurement oftherealdevice. User can usethis calculatortocheck the batterylifeandcalculatethe batterylifeifwant tousedifferenttransmit interval.638 +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. 665 665 ))) 666 666 667 - 668 668 ((( 669 - Instructionto use as below:642 + 670 670 ))) 671 671 672 -((( 673 -(% 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/]] 674 -))) 675 675 646 +=== 2.5.3 Battery Note === 676 676 677 677 ((( 678 - (%style="color:blue"%)**Step2:**(%%)Open it andchoose649 +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. 679 679 ))) 680 680 681 -* ((( 682 -Product Model 683 -))) 684 -* ((( 685 -Uplink Interval 686 -))) 687 -* ((( 688 -Working Mode 689 -))) 690 690 691 -((( 692 -And the Life expectation in difference case will be shown on the right. 693 -))) 694 694 695 - [[image:image-20220709110451-3.png]]654 +=== 2.5.4 Replace the battery === 696 696 697 697 698 - 699 -=== 2.8.3 Battery Note === 700 - 701 701 ((( 702 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.658 +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. 703 703 ))) 704 704 705 705 706 - 707 -=== 2.8.4 Replace the battery === 708 - 709 709 ((( 710 -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).663 +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). 711 711 ))) 712 712 713 713 ... ... @@ -730,7 +730,7 @@ 730 730 731 731 == 4.1 Access AT Commands == 732 732 733 -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/]]686 +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/]] 734 734 735 735 736 736 AT+<CMD>? : Help on <CMD> ... ... @@ -818,7 +818,9 @@ 818 818 ))) 819 819 820 820 ((( 821 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 774 + 775 + 776 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 822 822 ))) 823 823 824 824 ... ... @@ -850,7 +850,7 @@ 850 850 = 7. Order Info = 851 851 852 852 853 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**808 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 854 854 855 855 856 856 (% class="wikigeneratedid" %) ... ... @@ -865,7 +865,7 @@ 865 865 866 866 (% style="color:#037691" %)**Package Includes**: 867 867 868 -* NS E01DistanceDetectSensorNode x 1823 +* N95S31B NB-IoT Temperature and Humidity Sensor 869 869 * External antenna x 1 870 870 ))) 871 871 ... ... @@ -874,11 +874,10 @@ 874 874 875 875 (% style="color:#037691" %)**Dimension and weight**: 876 876 877 - 878 878 * Device Size: 13.0 x 5 x 4.5 cm 879 879 * Device Weight: 150g 880 -* Package Size / pcs : 1 5x12x 5.5cm881 -* Weight / pcs : 220g834 +* Package Size / pcs : 14.0 x 8x 5 cm 835 +* Weight / pcs : 180g 882 882 ))) 883 883 884 884 (((
- 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-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