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, 13 added, 0 removed)
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 ... ... @@ -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 ... ... @@ -111,9 +111,13 @@ 111 111 112 112 === 1.5.2 BOOT MODE / SW1 === 113 113 126 +((( 114 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. 128 +))) 115 115 130 +((( 116 116 2) Flash: work mode, device starts to work and send out console output for further debug 132 +))) 117 117 118 118 119 119 ... ... @@ -132,7 +132,6 @@ 132 132 133 133 134 134 135 - 136 136 = 2. Use N95S31B to communicate with IoT Server = 137 137 138 138 == 2.1 How it works == ... ... @@ -170,39 +170,55 @@ 170 170 === 2.2.1 Test Requirement === 171 171 172 172 188 +((( 173 173 To use N95S31B in your city, make sure meet below requirements: 190 +))) 174 174 175 -* Your local operator has already distributed a NB-IoT Network there. 176 -* The local NB-IoT network used the band that N95S31B supports. 177 -* 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 +))) 178 178 179 - 202 +((( 180 180 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 204 +))) 181 181 206 +((( 182 182 N95S31B supports different communication protocol such as : 208 +))) 183 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(%%)) 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 +))) 189 189 224 +((( 190 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. 226 +))) 191 191 192 192 193 193 ))) 194 194 195 -((( 196 -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 197 -))) 231 +[[image:1657350625843-586.png]] 198 198 199 199 200 -[[image:1657328756309-230.png]] 201 201 235 +=== 2.2.3 Insert SIM card === 202 202 203 - 204 -=== 2.2.2 Insert SIM card === 205 - 206 206 ((( 207 207 Insert the NB-IoT Card get from your provider. 208 208 ))) ... ... @@ -212,19 +212,19 @@ 212 212 ))) 213 213 214 214 215 -[[image:165732 8884227-504.png]]246 +[[image:1657351240556-536.png]] 216 216 217 217 218 218 219 -=== 2.2. 3DDS75 to configure it ===250 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 220 220 221 221 ((( 222 222 ((( 223 -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. 224 224 ))) 225 225 ))) 226 226 227 -[[image: image-20220709092052-2.png]]258 +[[image:1657351312545-300.png]] 228 228 229 229 **Connection:** 230 230 ... ... @@ -244,18 +244,18 @@ 244 244 * Flow Control: (% style="color:green" %)**None** 245 245 246 246 ((( 247 -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. 248 248 ))) 249 249 250 250 [[image:1657329814315-101.png]] 251 251 252 252 ((( 253 -(% 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/]] 254 254 ))) 255 255 256 256 257 257 258 -=== 2.2. 4289 +=== 2.2.5 Use CoAP protocol to uplink data === 259 259 260 260 (% 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/]] 261 261 ... ... @@ -275,10 +275,12 @@ 275 275 ))) 276 276 277 277 ((( 309 + 310 + 278 278 For parameter description, please refer to AT command set 279 279 ))) 280 280 281 -[[image:16573 30452568-615.png]]314 +[[image:1657352146020-183.png]] 282 282 283 283 284 284 ((( ... ... @@ -285,11 +285,11 @@ 285 285 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. 286 286 ))) 287 287 288 -[[image:16573 30472797-498.png]]321 +[[image:1657352185396-303.png]] 289 289 290 290 291 291 292 -=== 2.2. 5325 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 293 293 294 294 295 295 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -296,15 +296,16 @@ 296 296 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 297 297 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 298 298 299 -[[image:16573 30501006-241.png]]332 +[[image:1657352391268-297.png]] 300 300 301 301 302 -[[image:16573 30533775-472.png]]335 +[[image:1657352403317-397.png]] 303 303 304 304 305 305 306 -=== 2.2. 6339 +=== 2.2.7 Use MQTT protocol to uplink data === 307 307 341 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 308 308 309 309 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 310 310 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -311,35 +311,40 @@ 311 311 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 312 312 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 313 313 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 314 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB**(%%)~/~/Set the sending topic of MQTT315 -* (% 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 316 316 317 -[[image:165724 9978444-674.png]]351 +[[image:1657352634421-276.png]] 318 318 319 319 320 -[[image:16573 30723006-866.png]]354 +[[image:1657352645687-385.png]] 321 321 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 +))) 322 322 360 + 323 323 ((( 324 -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. 325 325 ))) 326 326 327 327 328 328 329 -=== 2.2. 7367 +=== 2.2.8 Use TCP protocol to uplink data === 330 330 369 +This feature is supported since firmware version v110 331 331 332 332 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 333 333 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 334 334 335 -[[image: image-20220709093918-1.png]]374 +[[image:1657352898400-901.png]] 336 336 337 337 338 -[[image: image-20220709093918-2.png]]377 +[[image:1657352914475-252.png]] 339 339 340 340 341 341 342 -=== 2.2. 8381 +=== 2.2.9 Change Update Interval === 343 343 344 344 User can use below command to change the (% style="color:green" %)**uplink interval**. 345 345 ... ... @@ -346,164 +346,157 @@ 346 346 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 347 347 348 348 ((( 349 - (%style="color:red" %)**NOTE:**388 + 350 350 ))) 351 351 352 -((( 353 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 354 -))) 355 355 356 356 357 - 358 358 == 2.3 Uplink Payload == 359 359 360 -In this mode, uplink payload includes in total 14 bytes 361 361 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 +))) 362 362 363 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 364 -|=(% style="width: 60px;" %)((( 365 -**Size(bytes)** 366 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 367 -|(% 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"]] 368 368 369 369 ((( 370 - If we use the MQTT client tosubscribeto this MQTT topic, wecan see the following information when the NDDS751 uplink data.402 +For example: 371 371 ))) 372 372 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 +))) 373 373 374 -[[image:1657331036973-987.png]] 375 375 376 376 ((( 377 -The payload is ASCIIstring,representative sameHEX:411 +The uplink payloads are composed in ASCII String. For example: 378 378 ))) 379 379 380 380 ((( 381 -0 x72403155615900640c6c19029200where:415 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 382 382 ))) 383 383 384 - *(((385 - DeviceID:0x724031556159=724031556159418 +((( 419 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 386 386 ))) 387 -* ((( 388 -Version: 0x0064=100=1.0.0 421 + 422 + 423 +((( 424 +(% style="color:red" %)**NOTE:** 389 389 ))) 390 390 391 -* ((( 392 -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"]]. 393 393 ))) 394 - *(((395 - Signal:0x19=25431 +1. ((( 432 +By default, the device will send an uplink message every 1 hour. 396 396 ))) 397 -* ((( 398 -Distance: 0x0292= 658 mm 399 -))) 400 -* ((( 401 -Interrupt: 0x00 = 0 402 402 403 403 404 404 405 - 406 -))) 437 +=== 2.3.1 Payload Analyze === 407 407 408 - ==2.4PayloadExplanationandSensorInterface==439 +N95S31B uplink payload includes in total 21 bytes 409 409 410 410 411 -=== 2.4.1 Device ID === 412 - 442 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 443 +|=(% style="width: 60px;" %)((( 444 +**Size(bytes)** 445 +)))|=(% 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** 446 +|(% 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" %)((( 413 413 ((( 414 - By default, theDeviceID equal to thelast6bytes of IMEI.448 +Reserve/ Same as NBSN95 CFGMOD=1 415 415 ))) 416 416 417 417 ((( 418 - Usercanuse (% style="color:blue" %)**AT+DEUI**(%%)toset Device ID452 +No function here. 419 419 ))) 420 - 454 +)))|(% style="width:77px" %)((( 421 421 ((( 422 - **Example:**456 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 423 423 ))) 424 424 425 425 ((( 426 - AT+DEUI=A84041F15612460 +By SHT31 427 427 ))) 428 - 462 +)))|(% style="width:80px" %)((( 429 429 ((( 430 - The Device ID is storednane-erasearea, Upgradethe firmwareor run **AT+FDR** won'terase Device ID.464 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 431 431 ))) 432 432 433 - 434 - 435 -=== 2.4.2 Version Info === 436 - 437 437 ((( 438 - Specifythe software version: 0x64=100, means firmware version 1.00.468 +By SHT31 439 439 ))) 470 +))) 440 440 441 441 ((( 442 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 473 +((( 474 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 443 443 ))) 476 +))) 444 444 445 445 479 +[[image:1657354294009-643.png]] 446 446 447 -=== 2.4.3 Battery Info === 448 448 449 -((( 450 -Ex1: 0x0B45 = 2885mV 451 -))) 482 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 452 452 453 -((( 454 -Ex2: 0x0B49 = 2889mV 455 -))) 484 +* Device ID: 0x724031607457 = 724031607457 485 +* Version: 0x006e=110=1.1.0 456 456 487 +* BAT: 0x0ccd = 3277 mV = 3.277V 488 +* Signal: 0x1b = 27 489 +* Model: 0x01 = 1 490 +* 0x00dc000ccc= reserve, ignore in N95S31B 491 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 492 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 457 457 458 - 459 -=== 2.4.4 Signal Strength === 460 - 461 461 ((( 462 - NB-IoTNetwork signal Strength.495 + 463 463 ))) 464 464 465 465 ((( 466 - **Ex1:0x1d = 29**499 + 467 467 ))) 468 468 502 + 503 +=== 2.3.2 Device ID === 504 + 469 469 ((( 470 - (% style="color:blue"%)**0**(%%)-113dBmorless506 +By default, the Device ID equal to the last 6 bytes of IMEI. 471 471 ))) 472 472 473 473 ((( 474 -(% style="color:blue" %)** 1**(%%)-111dBm510 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 475 475 ))) 476 476 477 477 ((( 478 - (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm514 +**Example:** 479 479 ))) 480 480 481 481 ((( 482 - (% style="color:blue" %)**31** (%%) -51dBm or greater518 +AT+DEUI=A84041F15612 483 483 ))) 484 484 485 485 ((( 486 - (%style="color:blue"%)**99**(%%)Notknownor notdetectable522 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 487 487 ))) 488 488 489 489 490 490 491 -=== 2. 4.5Distance===527 +=== 2.3.3 Version Info === 492 492 493 -Get the distance. Flat object range 280mm - 7500mm. 494 - 495 495 ((( 496 - Forexample,if the datayou getfrom theregisteris **__0x0B 0x05__**, the distancebetweenthesensorand the measuredobject is530 +These bytes include the hardware and software version. 497 497 ))) 498 498 499 499 ((( 500 -((( 501 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 534 +Higher byte: Specify hardware version: always 0x00 for N95S31B 502 502 ))) 503 -))) 504 504 505 505 ((( 506 - 538 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 507 507 ))) 508 508 509 509 ((( ... ... @@ -510,63 +510,79 @@ 510 510 511 511 ))) 512 512 513 -=== 2.4.6 Digital Interrupt === 514 - 515 515 ((( 516 - Digital Interruptrefers topin (% style="color:blue"%)**GPIO_EXTI**(%%),andtherearedifferent triggermethods. When thereisa trigger, theNDDS75 will send a packetto theserver.546 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 517 517 ))) 518 518 519 519 ((( 520 - Thecommand is:550 + 521 521 ))) 522 522 553 + 554 +=== 2.3.4 Battery Info === 555 + 523 523 ((( 524 - (% 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]])**.**557 +Ex1: 0x0B45 = 2885mV 525 525 ))) 526 526 527 - 528 528 ((( 529 - Thelowerfourbits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.561 +Ex2: 0x0B49 = 2889mV 530 530 ))) 531 531 532 532 565 + 566 +=== 2.3.5 Signal Strength === 567 + 533 533 ((( 534 - Example:569 +NB-IoT Network signal Strength. 535 535 ))) 536 536 537 537 ((( 538 - 0x(00):Normaluplinkpacket.573 +**Ex1: 0x1d = 29** 539 539 ))) 540 540 541 541 ((( 542 - 0x(01):InterruptUplinkPacket.577 +(% style="color:blue" %)**0**(%%) -113dBm or less 543 543 ))) 544 544 545 - 546 - 547 -=== 2.4.7 +5V Output === 548 - 549 549 ((( 550 - NDDS75willenable +5Voutputbeforeallsamplinganddisablethe+5vafterall sampling.581 +(% style="color:blue" %)**1**(%%) -111dBm 551 551 ))) 552 552 553 - 554 554 ((( 555 - The5V output timean be controlledbyAT Command.585 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 556 556 ))) 557 557 558 558 ((( 559 -(% style="color:blue" %)** AT+5VT=1000**589 +(% style="color:blue" %)**31** (%%) -51dBm or greater 560 560 ))) 561 561 562 562 ((( 563 - Meansset5V valid timetohave 1000ms. Sothereal5V outputwillactuallyhave1000ms+samplingtime for othersensors.593 +(% style="color:blue" %)**99** (%%) Not known or not detectable 564 564 ))) 565 565 566 566 567 567 568 -== 2. 5Downlink Payload ==598 +=== 2.3.6 Temperature & Humidity === 569 569 600 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 601 + 602 +[[image:image-20220709161741-3.png]] 603 + 604 + 605 +Convert the read byte to decimal and divide it by ten. 606 + 607 + 608 +**Example:** 609 + 610 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 611 + 612 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 613 + 614 + 615 + 616 +== 2.4 Downlink Payload == 617 + 570 570 By default, NDDS75 prints the downlink payload to console port. 571 571 572 572 [[image:image-20220709100028-1.png]] ... ... @@ -617,51 +617,16 @@ 617 617 618 618 619 619 620 -== 2. 6LED Indicator ==668 +== 2.5 Battery Analysis == 621 621 670 +=== 2.5.1 Battery Type === 622 622 623 -The NDDS75 has an internal LED which is to show the status of different state. 624 624 625 - 626 -* 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) 627 -* Then the LED will be on for 1 second means device is boot normally. 628 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 629 -* For each uplink probe, LED will be on for 500ms. 630 - 631 631 ((( 632 - 674 +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. 633 633 ))) 634 634 635 - 636 - 637 -== 2.7 Firmware Change Log == 638 - 639 - 640 640 ((( 641 -Download URL & Firmware Change log 642 -))) 643 - 644 -((( 645 -[[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/]] 646 -))) 647 - 648 - 649 -((( 650 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 651 -))) 652 - 653 - 654 - 655 -== 2.8 Battery Analysis == 656 - 657 -=== 2.8.1 Battery Type === 658 - 659 - 660 -((( 661 -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. 662 -))) 663 - 664 -((( 665 665 The battery is designed to last for several years depends on the actually use environment and update interval. 666 666 ))) 667 667 ... ... @@ -679,56 +679,35 @@ 679 679 680 680 681 681 682 -=== 2. 8.2 Power consumption Analyze ===695 +=== 2.5.2 Power consumption Analyze === 683 683 684 684 ((( 685 - Draginobatterypoweredproductareall runsinLow Powermode.Wehave an update battery calculatorwhichbaseonthe measurement oftherealdevice. User can usethis calculatortocheck the batterylifeandcalculatethe batterylifeifwant tousedifferenttransmit interval.698 +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. 686 686 ))) 687 687 688 - 689 689 ((( 690 - Instructionto use as below:702 + 691 691 ))) 692 692 693 -((( 694 -(% 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/]] 695 -))) 696 696 706 +=== 2.5.3 Battery Note === 697 697 698 698 ((( 699 - (%style="color:blue"%)**Step2:**(%%)Open it andchoose709 +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. 700 700 ))) 701 701 702 -* ((( 703 -Product Model 704 -))) 705 -* ((( 706 -Uplink Interval 707 -))) 708 -* ((( 709 -Working Mode 710 -))) 711 711 712 -((( 713 -And the Life expectation in difference case will be shown on the right. 714 -))) 715 715 716 - [[image:image-20220709110451-3.png]]714 +=== 2.5.4 Replace the battery === 717 717 718 718 719 - 720 -=== 2.8.3 Battery Note === 721 - 722 722 ((( 723 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.718 +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. 724 724 ))) 725 725 726 726 727 - 728 -=== 2.8.4 Replace the battery === 729 - 730 730 ((( 731 -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).723 +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). 732 732 ))) 733 733 734 734 ... ... @@ -751,7 +751,7 @@ 751 751 752 752 == 4.1 Access AT Commands == 753 753 754 -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/]]746 +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/]] 755 755 756 756 757 757 AT+<CMD>? : Help on <CMD> ... ... @@ -839,8 +839,12 @@ 839 839 ))) 840 840 841 841 ((( 842 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 834 + 835 + 836 +((( 837 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 843 843 ))) 839 +))) 844 844 845 845 846 846 ... ... @@ -871,7 +871,7 @@ 871 871 = 7. Order Info = 872 872 873 873 874 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**870 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 875 875 876 876 877 877 (% class="wikigeneratedid" %) ... ... @@ -886,7 +886,7 @@ 886 886 887 887 (% style="color:#037691" %)**Package Includes**: 888 888 889 -* NS E01DistanceDetectSensorNode x 1885 +* N95S31B NB-IoT Temperature and Humidity Sensor 890 890 * External antenna x 1 891 891 ))) 892 892 ... ... @@ -895,11 +895,10 @@ 895 895 896 896 (% style="color:#037691" %)**Dimension and weight**: 897 897 898 - 899 899 * Device Size: 13.0 x 5 x 4.5 cm 900 900 * Device Weight: 150g 901 -* Package Size / pcs : 1 5x12x 5.5cm902 -* Weight / pcs : 220g896 +* Package Size / pcs : 14.0 x 8x 5 cm 897 +* Weight / pcs : 180g 903 903 ))) 904 904 905 905 (((
- 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-20220709161741-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +111.2 KB - Content