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, 0 added, 8 removed)
Details
- Page properties
-
- Content
-
... ... @@ -9,7 +9,6 @@ 9 9 10 10 **Table of Contents:** 11 11 12 -{{toc/}} 13 13 14 14 15 15 ... ... @@ -22,29 +22,16 @@ 22 22 ((( 23 23 24 24 25 -((( 26 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 -))) 28 28 29 -((( 30 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 -))) 32 32 33 -((( 34 34 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 35 -))) 36 36 37 -((( 38 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 -))) 40 40 41 -((( 42 - 43 -))) 44 44 45 -((( 46 46 ~* make sure you have NB-IoT coverage locally. 47 -))) 48 48 49 49 50 50 ))) ... ... @@ -55,6 +55,7 @@ 55 55 56 56 == 1.2 Features == 57 57 44 + 58 58 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 59 59 * Monitor Temperature & Humidity via SHT31 60 60 * AT Commands to change parameters ... ... @@ -68,7 +68,6 @@ 68 68 69 69 70 70 71 - 72 72 == 1.3 Specification == 73 73 74 74 ... ... @@ -77,7 +77,6 @@ 77 77 * Supply Voltage: 2.1v ~~ 3.6v 78 78 * Operating Temperature: -40 ~~ 85°C 79 79 80 - 81 81 (% style="color:#037691" %)**NB-IoT Spec:** 82 82 83 83 * - B1 @H-FDD: 2100MHz ... ... @@ -87,9 +87,9 @@ 87 87 * - B20 @H-FDD: 800MHz 88 88 * - B28 @H-FDD: 700MHz 89 89 90 - 91 91 (% style="color:#037691" %)**Battery:** 92 92 77 + 93 93 * Li/SOCI2 un-chargeable battery 94 94 * Capacity: 8500mAh 95 95 * Self Discharge: <1% / Year @ 25°C ... ... @@ -98,7 +98,6 @@ 98 98 99 99 100 100 101 - 102 102 == 1.4 Applications == 103 103 104 104 * Smart Buildings & Home Automation ... ... @@ -127,13 +127,9 @@ 127 127 128 128 === 1.5.2 BOOT MODE / SW1 === 129 129 130 -((( 131 131 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. 132 -))) 133 133 134 -((( 135 135 2) Flash: work mode, device starts to work and send out console output for further debug 136 -))) 137 137 138 138 139 139 ... ... @@ -196,6 +196,7 @@ 196 196 * The local NB-IoT network used the band that N95S31B supports. 197 197 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 198 198 179 + 199 199 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 200 200 201 201 N95S31B supports different communication protocol such as : ... ... @@ -230,7 +230,7 @@ 230 230 231 231 232 232 233 -=== 2.2. 4Connect USB – TTL to N95S31B to configure it ===214 +=== 2.2.3 Connect USB – TTL to N95S31B to configure it === 234 234 235 235 ((( 236 236 ((( ... ... @@ -269,7 +269,7 @@ 269 269 270 270 271 271 272 -=== 2.2. 5Use CoAP protocol to uplink data ===253 +=== 2.2.4 Use CoAP protocol to uplink data === 273 273 274 274 (% 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/]] 275 275 ... ... @@ -289,12 +289,10 @@ 289 289 ))) 290 290 291 291 ((( 292 - 293 - 294 294 For parameter description, please refer to AT command set 295 295 ))) 296 296 297 -[[image:1657352 146020-183.png]]276 +[[image:1657330452568-615.png]] 298 298 299 299 300 300 ((( ... ... @@ -301,11 +301,11 @@ 301 301 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. 302 302 ))) 303 303 304 -[[image:16573 52185396-303.png]]283 +[[image:1657330472797-498.png]] 305 305 306 306 307 307 308 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===287 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 309 309 310 310 311 311 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -312,16 +312,15 @@ 312 312 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 313 313 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 314 314 315 -[[image:16573 52391268-297.png]]294 +[[image:1657330501006-241.png]] 316 316 317 317 318 -[[image:16573 52403317-397.png]]297 +[[image:1657330533775-472.png]] 319 319 320 320 321 321 322 -=== 2.2. 7Use MQTT protocol to uplink data ===301 +=== 2.2.6 Use MQTT protocol to uplink data === 323 323 324 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 325 325 326 326 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 327 327 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -328,40 +328,35 @@ 328 328 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 329 329 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 330 330 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 331 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527332 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)309 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 310 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 333 333 334 -[[image:1657 352634421-276.png]]312 +[[image:1657249978444-674.png]] 335 335 336 336 337 -[[image:16573 52645687-385.png]]315 +[[image:1657330723006-866.png]] 338 338 339 -((( 340 -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. 341 -))) 342 342 343 - 344 344 ((( 345 -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.319 +MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 346 346 ))) 347 347 348 348 349 349 350 -=== 2.2. 8Use TCP protocol to uplink data ===324 +=== 2.2.7 Use TCP protocol to uplink data === 351 351 352 -This feature is supported since firmware version v110 353 353 354 354 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 355 355 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 356 356 357 -[[image: 1657352898400-901.png]]330 +[[image:image-20220709093918-1.png]] 358 358 359 359 360 -[[image: 1657352914475-252.png]]333 +[[image:image-20220709093918-2.png]] 361 361 362 362 363 363 364 -=== 2.2. 9Change Update Interval ===337 +=== 2.2.8 Change Update Interval === 365 365 366 366 User can use below command to change the (% style="color:green" %)**uplink interval**. 367 367 ... ... @@ -368,207 +368,227 @@ 368 368 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 369 369 370 370 ((( 371 - 344 +(% style="color:red" %)**NOTE:** 372 372 ))) 373 373 347 +((( 348 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 349 +))) 374 374 375 375 352 + 376 376 == 2.3 Uplink Payload == 377 377 355 +In this mode, uplink payload includes in total 14 bytes 378 378 379 -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. 380 380 358 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 359 +|=(% style="width: 60px;" %)((( 360 +**Size(bytes)** 361 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 362 +|(% 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"]] 381 381 382 -For example: 364 +((( 365 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 366 +))) 383 383 384 - (% 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. 385 385 369 +[[image:1657331036973-987.png]] 386 386 387 -The uplink payloads are composed in ASCII String. For example: 371 +((( 372 +The payload is ASCII string, representative same HEX: 373 +))) 388 388 389 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 375 +((( 376 +0x72403155615900640c6c19029200 where: 377 +))) 390 390 391 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 379 +* ((( 380 +Device ID: 0x724031556159 = 724031556159 381 +))) 382 +* ((( 383 +Version: 0x0064=100=1.0.0 384 +))) 392 392 386 +* ((( 387 +BAT: 0x0c6c = 3180 mV = 3.180V 388 +))) 389 +* ((( 390 +Signal: 0x19 = 25 391 +))) 392 +* ((( 393 +Distance: 0x0292= 658 mm 394 +))) 395 +* ((( 396 +Interrupt: 0x00 = 0 393 393 394 -(% style="color:red" %)**NOTE:** 395 395 396 -(% style="color:red" %) 397 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 398 -1. By default, the device will send an uplink message every 1 hour. 399 399 400 + 401 +))) 400 400 401 -== =2.3.1PayloadAnalyze ===403 +== 2.4 Payload Explanation and Sensor Interface == 402 402 403 -N95S31B uplink payload includes in total 21 bytes 404 404 406 +=== 2.4.1 Device ID === 405 405 406 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 407 -|=(% style="width: 60px;" %)((( 408 -**Size(bytes)** 409 -)))|=(% 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** 410 -|(% 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" %)((( 411 411 ((( 412 - Reserve/Same asNBSN95CFGMOD=1409 +By default, the Device ID equal to the last 6 bytes of IMEI. 413 413 ))) 414 414 415 415 ((( 416 - Nofunctionhere.413 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 417 417 ))) 418 - )))|(% style="width:77px" %)(((415 + 419 419 ((( 420 - [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]417 +**Example:** 421 421 ))) 422 422 423 423 ((( 424 - By SHT31421 +AT+DEUI=A84041F15612 425 425 ))) 426 - )))|(% style="width:80px" %)(((423 + 427 427 ((( 428 - [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]425 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 429 429 ))) 430 430 428 + 429 + 430 +=== 2.4.2 Version Info === 431 + 431 431 ((( 432 - BySHT31433 +Specify the software version: 0x64=100, means firmware version 1.00. 433 433 ))) 434 -))) 435 435 436 436 ((( 437 -((( 438 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 437 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 439 439 ))) 440 -))) 441 441 442 442 443 -[[image:1657354294009-643.png]] 444 444 442 +=== 2.4.3 Battery Info === 445 445 446 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 447 - 448 -* Device ID: 0x724031607457 = 724031607457 449 -* Version: 0x006e=110=1.1.0 450 - 451 -* BAT: 0x0ccd = 3277 mV = 3.277V 452 -* Signal: 0x1b = 27 453 -* Model: 0x01 = 1 454 -* 0x00dc000ccc= reserve, ignore in N95S31B 455 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 456 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 457 - 458 458 ((( 459 - 445 +Ex1: 0x0B45 = 2885mV 460 460 ))) 461 461 462 462 ((( 463 - 449 +Ex2: 0x0B49 = 2889mV 464 464 ))) 465 465 466 466 467 -=== 2.3.2 Device ID === 468 468 454 +=== 2.4.4 Signal Strength === 455 + 469 469 ((( 470 -B ydefault,the Device ID equal to thelast6 bytes of IMEI.457 +NB-IoT Network signal Strength. 471 471 ))) 472 472 473 473 ((( 474 - User can use (% style="color:blue" %)**AT+DEUI**(%%)tosetDevice ID461 +**Ex1: 0x1d = 29** 475 475 ))) 476 476 477 477 ((( 478 - **Example:**465 +(% style="color:blue" %)**0**(%%) -113dBm or less 479 479 ))) 480 480 481 481 ((( 482 - AT+DEUI=A84041F15612469 +(% style="color:blue" %)**1**(%%) -111dBm 483 483 ))) 484 484 485 485 ((( 486 - TheDevice ID isstored in a none-erase area, Upgrade the firmwareorrun**AT+FDR**won't erase Device ID.473 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 487 487 ))) 488 488 476 +((( 477 +(% style="color:blue" %)**31** (%%) -51dBm or greater 478 +))) 489 489 480 +((( 481 +(% style="color:blue" %)**99** (%%) Not known or not detectable 482 +))) 490 490 491 -=== 2.3.3 Version Info === 492 492 493 493 494 - Thesebytesinclude the hardware andsoftwareversion.486 +=== 2.4.5 Distance === 495 495 496 - Higherbyte:Specifyhardwareversion: always0x00forN95S31B488 +Get the distance. Flat object range 280mm - 7500mm. 497 497 498 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110 490 +((( 491 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 492 +))) 499 499 500 - 501 -For example: 0x00 6E: this device is N95S31B with firmware version 110. 502 - 503 503 ((( 504 - 495 +((( 496 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 505 505 ))) 498 +))) 506 506 507 - 508 -=== 2.3.4 Battery Info === 509 - 510 510 ((( 511 - Ex1:0x0B45 = 2885mV501 + 512 512 ))) 513 513 514 514 ((( 515 - Ex2:0x0B49 = 2889mV505 + 516 516 ))) 517 517 508 +=== 2.4.6 Digital Interrupt === 518 518 519 - 520 -=== 2.3.5 Signal Strength === 521 - 522 522 ((( 523 - NB-IoTNetworksignalStrength.511 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server. 524 524 ))) 525 525 526 526 ((( 527 - **Ex1:0x1d= 29**515 +The command is: 528 528 ))) 529 529 530 530 ((( 531 -(% style="color:blue" %)** 0**(%%)-113dBmor less519 +(% 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]])**.** 532 532 ))) 533 533 522 + 534 534 ((( 535 - (%style="color:blue"%)**1**(%%)-111dBm524 +The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up. 536 536 ))) 537 537 527 + 538 538 ((( 539 - (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm529 +Example: 540 540 ))) 541 541 542 542 ((( 543 -( %style="color:blue"%)**31** (%%) -51dBm or greater533 +0x(00): Normal uplink packet. 544 544 ))) 545 545 546 546 ((( 547 -( %style="color:blue" %)**99** (%%) Notknownor not detectable537 +0x(01): Interrupt Uplink Packet. 548 548 ))) 549 549 550 550 551 551 552 -=== 2. 3.6Temperature& Humidity===542 +=== 2.4.7 +5V Output === 553 553 554 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 544 +((( 545 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 546 +))) 555 555 556 -[[image:image-20220709161741-3.png]] 557 557 549 +((( 550 +The 5V output time can be controlled by AT Command. 551 +))) 558 558 559 -Convert the read byte to decimal and divide it by ten. 553 +((( 554 +(% style="color:blue" %)**AT+5VT=1000** 555 +))) 560 560 557 +((( 558 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 559 +))) 561 561 562 -**Example:** 563 563 564 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 565 565 566 - Humidity:Read:0295(H)=661(D)Value:661 / 10=66.1, So66.1%563 +== 2.5 Downlink Payload == 567 567 568 - 569 - 570 -== 2.4 Downlink Payload == 571 - 572 572 By default, NDDS75 prints the downlink payload to console port. 573 573 574 574 [[image:image-20220709100028-1.png]] ... ... @@ -619,16 +619,51 @@ 619 619 620 620 621 621 622 -== 2. 5BatteryAnalysis==615 +== 2.6 LED Indicator == 623 623 624 -=== 2.5.1 Battery Type === 625 625 618 +The NDDS75 has an internal LED which is to show the status of different state. 626 626 620 + 621 +* 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) 622 +* Then the LED will be on for 1 second means device is boot normally. 623 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 624 +* For each uplink probe, LED will be on for 500ms. 625 + 627 627 ((( 628 - TheN95S31B 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.627 + 629 629 ))) 630 630 630 + 631 + 632 +== 2.7 Firmware Change Log == 633 + 634 + 631 631 ((( 636 +Download URL & Firmware Change log 637 +))) 638 + 639 +((( 640 +[[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/]] 641 +))) 642 + 643 + 644 +((( 645 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 646 +))) 647 + 648 + 649 + 650 +== 2.8 Battery Analysis == 651 + 652 +=== 2.8.1 Battery Type === 653 + 654 + 655 +((( 656 +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. 657 +))) 658 + 659 +((( 632 632 The battery is designed to last for several years depends on the actually use environment and update interval. 633 633 ))) 634 634 ... ... @@ -646,35 +646,56 @@ 646 646 647 647 648 648 649 -=== 2. 5.2 Power consumption Analyze ===677 +=== 2.8.2 Power consumption Analyze === 650 650 651 651 ((( 652 - 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/]] describesadetailmeasurementtoanalyzethepowerconsumption indifferentcase. User can useitfordesignguideline fortheirproject.680 +Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval. 653 653 ))) 654 654 683 + 655 655 ((( 656 - 685 +Instruction to use as below: 657 657 ))) 658 658 688 +((( 689 +(% 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/]] 690 +))) 659 659 660 -=== 2.5.3 Battery Note === 661 661 662 662 ((( 663 - TheLi-SICO batteryis designed for small current / long period application. It is not good tousea high current, short periodtransmitmethod.Therecommendedminimum period for use ofthisbattery is 5 minutes.If you use a shorter period time to uplink data, then the battery life may be decreased.694 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 664 664 ))) 665 665 697 +* ((( 698 +Product Model 699 +))) 700 +* ((( 701 +Uplink Interval 702 +))) 703 +* ((( 704 +Working Mode 705 +))) 666 666 707 +((( 708 +And the Life expectation in difference case will be shown on the right. 709 +))) 667 667 668 - === 2.5.4 Replacethe battery ===711 +[[image:image-20220709110451-3.png]] 669 669 670 670 714 + 715 +=== 2.8.3 Battery Note === 716 + 671 671 ((( 672 - You can changethebattery intheN95S31B.Thetype ofbatteryis notlimitedaslongas theutput isbetween3vto3.6v.Onthemainboard,there isa diode(D1)betweenthebatteryandthemaincircuit. If youneed touse abatterywith less than 3.3v,pleaseremove the D1 andshortcut the twopadsofitso there won'tbe voltagedropbetween batteryandmainboard.718 +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 transmit LoRa, then the battery life may be decreased. 673 673 ))) 674 674 675 675 722 + 723 +=== 2.8.4 Replace the battery === 724 + 676 676 ((( 677 -The default battery pack of N 95S31Bincludes 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).726 +The default battery pack of NDDS75 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). 678 678 ))) 679 679 680 680 ... ... @@ -697,7 +697,7 @@ 697 697 698 698 == 4.1 Access AT Commands == 699 699 700 -See NBSN95 AT Command inthis link for detail:BSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]749 +See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 701 701 702 702 703 703 AT+<CMD>? : Help on <CMD> ... ... @@ -785,9 +785,7 @@ 785 785 ))) 786 786 787 787 ((( 788 - 789 - 790 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 837 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 791 791 ))) 792 792 793 793 ... ... @@ -819,7 +819,7 @@ 819 819 = 7. Order Info = 820 820 821 821 822 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**869 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 823 823 824 824 825 825 (% class="wikigeneratedid" %) ... ... @@ -834,7 +834,7 @@ 834 834 835 835 (% style="color:#037691" %)**Package Includes**: 836 836 837 -* N 95S31BNB-IoTTemperatureandHumiditySensor884 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 838 838 * External antenna x 1 839 839 ))) 840 840 ... ... @@ -843,10 +843,11 @@ 843 843 844 844 (% style="color:#037691" %)**Dimension and weight**: 845 845 893 + 846 846 * Device Size: 13.0 x 5 x 4.5 cm 847 847 * Device Weight: 150g 848 -* Package Size / pcs : 1 4.0x8x 5 cm849 -* Weight / pcs : 180g896 +* Package Size / pcs : 15 x 12x 5.5 cm 897 +* Weight / pcs : 220g 850 850 ))) 851 851 852 852 (((
- 1657352391268-297.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -238.0 KB - Content
- 1657352403317-397.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -547.7 KB - Content
- 1657352634421-276.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -163.6 KB - Content
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -144.8 KB - Content
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -157.0 KB - Content
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.2 KB - Content