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 ... ... @@ -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 == ... ... @@ -176,7 +176,6 @@ 176 176 * The local NB-IoT network used the band that N95S31B supports. 177 177 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 178 178 179 - 180 180 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 181 181 182 182 N95S31B supports different communication protocol such as : ... ... @@ -192,17 +192,12 @@ 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 -))) 187 +[[image:1657350625843-586.png]] 198 198 199 199 200 -[[image:1657328756309-230.png]] 201 201 191 +=== 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]]202 +[[image:1657351240556-536.png]] 216 216 217 217 218 218 219 -=== 2.2. 3DDS75 to configure it ===206 +=== 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.210 +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]]214 +[[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.234 +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/]]240 +(% 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. 4245 +=== 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 ((( 265 + 266 + 278 278 For parameter description, please refer to AT command set 279 279 ))) 280 280 281 -[[image:16573 30452568-615.png]]270 +[[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]]277 +[[image:1657352185396-303.png]] 289 289 290 290 291 291 292 -=== 2.2. 5281 +=== 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]]288 +[[image:1657352391268-297.png]] 300 300 301 301 302 -[[image:16573 30533775-472.png]]291 +[[image:1657352403317-397.png]] 303 303 304 304 305 305 306 -=== 2.2. 6295 +=== 2.2.7 Use MQTT protocol to uplink data === 307 307 297 +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 MQTT304 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 305 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 316 316 317 -[[image:165724 9978444-674.png]]307 +[[image:1657352634421-276.png]] 318 318 319 319 320 -[[image:16573 30723006-866.png]]310 +[[image:1657352645687-385.png]] 321 321 312 +((( 313 +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. 314 +))) 322 322 316 + 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.318 +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. 7323 +=== 2.2.8 Use TCP protocol to uplink data === 330 330 325 +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]]330 +[[image:1657352898400-901.png]] 336 336 337 337 338 -[[image: image-20220709093918-2.png]]333 +[[image:1657352914475-252.png]] 339 339 340 340 341 341 342 -=== 2.2. 8337 +=== 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,227 +346,209 @@ 346 346 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 347 347 348 348 ((( 349 - (%style="color:red" %)**NOTE:**344 + 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 352 +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. 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 -((( 370 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 371 -))) 355 +For example: 372 372 357 + (% 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. 373 373 374 -[[image:1657331036973-987.png]] 375 375 376 -((( 377 -The payload is ASCII string, representative same HEX: 378 -))) 360 +The uplink payloads are composed in ASCII String. For example: 379 379 380 -((( 381 -0x72403155615900640c6c19029200 where: 382 -))) 362 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 383 383 384 -* ((( 385 -Device ID: 0x724031556159 = 724031556159 386 -))) 387 -* ((( 388 -Version: 0x0064=100=1.0.0 389 -))) 364 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 390 390 391 -* ((( 392 -BAT: 0x0c6c = 3180 mV = 3.180V 393 -))) 394 -* ((( 395 -Signal: 0x19 = 25 396 -))) 397 -* ((( 398 -Distance: 0x0292= 658 mm 399 -))) 400 -* ((( 401 -Interrupt: 0x00 = 0 402 402 367 +(% style="color:red" %)**NOTE:** 403 403 369 +(% style="color:red" %) 370 +1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 371 +1. By default, the device will send an uplink message every 1 hour. 404 404 405 - 406 -))) 407 407 408 -== 2.4 Payload Explanation and Sensor Interface == 409 409 410 410 411 -=== 2. 4.1DeviceID===376 +=== 2.3.1 Payload Analyze === 412 412 378 +N95S31B uplink payload includes in total 21 bytes 379 + 380 + 381 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 382 +|=(% style="width: 60px;" %)((( 383 +**Size(bytes)** 384 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2** 385 +|(% 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.387 +Reserve/ Same as NBSN95 CFGMOD=1 415 415 ))) 416 416 417 417 ((( 418 - Usercanuse (% style="color:blue" %)**AT+DEUI**(%%)toset Device ID391 +No function here. 419 419 ))) 420 - 393 +)))|(% style="width:77px" %)((( 421 421 ((( 422 - **Example:**395 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 423 423 ))) 424 424 425 425 ((( 426 - AT+DEUI=A84041F15612399 +By SHT31 427 427 ))) 428 - 401 +)))|(% style="width:80px" %)((( 429 429 ((( 430 - The Device ID is storednane-erasearea, Upgradethe firmwareor run **AT+FDR** won'terase Device ID.403 +[[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.407 +By SHT31 439 439 ))) 409 +))) 440 440 441 441 ((( 442 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 412 +((( 413 +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 ))) 415 +))) 444 444 445 445 418 +[[image:1657354294009-643.png]] 446 446 447 -=== 2.4.3 Battery Info === 448 448 421 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 422 + 423 +* Device ID: 0x724031607457 = 724031607457 424 +* Version: 0x006e=110=1.1.0 425 + 426 +* BAT: 0x0ccd = 3277 mV = 3.277V 427 +* Signal: 0x1b = 27 428 +* Model: 0x01 = 1 429 +* 0x00dc000ccc= reserve, ignore in N95S31B 430 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 431 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 432 + 449 449 ((( 450 - Ex1:0x0B45 = 2885mV434 + 451 451 ))) 452 452 453 453 ((( 454 - Ex2:0x0B49 = 2889mV438 + 455 455 ))) 456 456 457 457 442 +=== 2.3.2 Device ID === 458 458 459 -=== 2.4.4 Signal Strength === 460 - 461 461 ((( 462 - NB-IoTNetworksignalStrength.445 +By default, the Device ID equal to the last 6 bytes of IMEI. 463 463 ))) 464 464 465 465 ((( 466 - **Ex1:0x1d=29**449 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 467 467 ))) 468 468 469 469 ((( 470 - (% style="color:blue" %)**0**(%%) -113dBmorless453 +**Example:** 471 471 ))) 472 472 473 473 ((( 474 - (% style="color:blue" %)**1**(%%) -111dBm457 +AT+DEUI=A84041F15612 475 475 ))) 476 476 477 477 ((( 478 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm461 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 479 479 ))) 480 480 481 -((( 482 -(% style="color:blue" %)**31** (%%) -51dBm or greater 483 -))) 484 484 485 -((( 486 -(% style="color:blue" %)**99** (%%) Not known or not detectable 487 -))) 488 488 466 +=== 2.3.3 Version Info === 489 489 490 490 491 - ===2.4.5Distance===469 +These bytes include the hardware and software version. 492 492 493 - Get thedistance.Flat objectrange280mm-7500mm.471 +Higher byte: Specify hardware version: always 0x00 for N95S31B 494 494 495 -((( 496 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 497 -))) 473 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 498 498 475 + 476 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 477 + 499 499 ((( 500 -((( 501 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 479 + 502 502 ))) 503 -))) 504 504 482 + 483 +=== 2.3.4 Battery Info === 484 + 505 505 ((( 506 - 486 +Ex1: 0x0B45 = 2885mV 507 507 ))) 508 508 509 509 ((( 510 - 490 +Ex2: 0x0B49 = 2889mV 511 511 ))) 512 512 513 -=== 2.4.6 Digital Interrupt === 514 514 494 + 495 +=== 2.3.5 Signal Strength === 496 + 515 515 ((( 516 - DigitalInterrupt refers topin (% style="color:blue" %)**GPIO_EXTI**(%%),and there are differenttrigger methods. When thereisa trigger, the NDDS75 will sendapacketto the server.498 +NB-IoT Network signal Strength. 517 517 ))) 518 518 519 519 ((( 520 - Thecommandis:502 +**Ex1: 0x1d = 29** 521 521 ))) 522 522 523 523 ((( 524 -(% 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]])**.**506 +(% style="color:blue" %)**0**(%%) -113dBm or less 525 525 ))) 526 526 527 - 528 528 ((( 529 - Thelower four bitsofthis data field shows if this packet is generatedby interruptornot.Clickhereforthehardwareandsoftware set up.510 +(% style="color:blue" %)**1**(%%) -111dBm 530 530 ))) 531 531 532 - 533 533 ((( 534 - Example:514 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 535 535 ))) 536 536 537 537 ((( 538 - 0x(00):Normalplinkpacket.518 +(% style="color:blue" %)**31** (%%) -51dBm or greater 539 539 ))) 540 540 541 541 ((( 542 - 0x(01):InterruptUplinkPacket.522 +(% style="color:blue" %)**99** (%%) Not known or not detectable 543 543 ))) 544 544 545 545 546 546 547 -=== 2. 4.7+5VOutput===527 +=== 2.3.6 Temperature & Humidity === 548 548 549 -((( 550 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 551 -))) 529 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 552 552 531 +[[image:image-20220709161741-3.png]] 553 553 554 -((( 555 -The 5V output time can be controlled by AT Command. 556 -))) 557 557 558 -((( 559 -(% style="color:blue" %)**AT+5VT=1000** 560 -))) 534 +Convert the read byte to decimal and divide it by ten. 561 561 562 -((( 563 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 564 -))) 565 565 537 +**Example:** 566 566 539 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 567 567 568 - ==2.5Downlink Payload==541 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 569 569 543 + 544 + 545 +== 2.4 Downlink Payload == 546 + 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 ==597 +== 2.5 Battery Analysis == 621 621 599 +=== 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 - 603 +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 ===624 +=== 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.627 +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:631 + 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 635 +=== 2.5.3 Battery Note === 697 697 698 698 ((( 699 - (%style="color:blue"%)**Step2:**(%%)Open it andchoose638 +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]]643 +=== 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.647 +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).652 +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/]]675 +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,7 +839,9 @@ 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. 763 + 764 + 765 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 843 843 ))) 844 844 845 845 ... ... @@ -871,7 +871,7 @@ 871 871 = 7. Order Info = 872 872 873 873 874 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**797 +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 1812 +* 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 : 220g823 +* Package Size / pcs : 14.0 x 8x 5 cm 824 +* 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