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 ... ... @@ -146,6 +146,9 @@ 146 146 1. When boot the device in flash mode 147 147 1. Send an uplink packet 148 148 133 + 134 + 135 + 149 149 = 2. Use N95S31B to communicate with IoT Server = 150 150 151 151 == 2.1 How it works == ... ... @@ -189,6 +189,7 @@ 189 189 * The local NB-IoT network used the band that N95S31B supports. 190 190 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 191 191 179 + 192 192 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 193 193 194 194 N95S31B supports different communication protocol such as : ... ... @@ -305,16 +305,15 @@ 305 305 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 306 306 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 307 307 308 -[[image:16573 52391268-297.png]]296 +[[image:1657330501006-241.png]] 309 309 310 310 311 -[[image:16573 52403317-397.png]]299 +[[image:1657330533775-472.png]] 312 312 313 313 314 314 315 -=== 2.2. 7Use MQTT protocol to uplink data ===303 +=== 2.2.6 Use MQTT protocol to uplink data === 316 316 317 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 318 318 319 319 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 320 320 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -321,40 +321,35 @@ 321 321 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 322 322 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 323 323 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 324 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527325 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)311 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 312 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 326 326 327 -[[image:1657 352634421-276.png]]314 +[[image:1657249978444-674.png]] 328 328 329 329 330 -[[image:16573 52645687-385.png]]317 +[[image:1657330723006-866.png]] 331 331 332 -((( 333 -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. 334 -))) 335 335 336 - 337 337 ((( 338 -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.321 +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. 339 339 ))) 340 340 341 341 342 342 343 -=== 2.2. 8Use TCP protocol to uplink data ===326 +=== 2.2.7 Use TCP protocol to uplink data === 344 344 345 -This feature is supported since firmware version v110 346 346 347 347 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 348 348 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 349 349 350 -[[image: 1657352898400-901.png]]332 +[[image:image-20220709093918-1.png]] 351 351 352 352 353 -[[image: 1657352914475-252.png]]335 +[[image:image-20220709093918-2.png]] 354 354 355 355 356 356 357 -=== 2.2. 9Change Update Interval ===339 +=== 2.2.8 Change Update Interval === 358 358 359 359 User can use below command to change the (% style="color:green" %)**uplink interval**. 360 360 ... ... @@ -361,207 +361,227 @@ 361 361 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 362 362 363 363 ((( 364 - 346 +(% style="color:red" %)**NOTE:** 365 365 ))) 366 366 349 +((( 350 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 351 +))) 367 367 368 368 354 + 369 369 == 2.3 Uplink Payload == 370 370 357 +In this mode, uplink payload includes in total 14 bytes 371 371 372 -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. 373 373 360 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 361 +|=(% style="width: 60px;" %)((( 362 +**Size(bytes)** 363 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 364 +|(% 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"]] 374 374 375 -For example: 366 +((( 367 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 368 +))) 376 376 377 - (% 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. 378 378 371 +[[image:1657331036973-987.png]] 379 379 380 -The uplink payloads are composed in ASCII String. For example: 373 +((( 374 +The payload is ASCII string, representative same HEX: 375 +))) 381 381 382 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 377 +((( 378 +0x72403155615900640c6c19029200 where: 379 +))) 383 383 384 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 381 +* ((( 382 +Device ID: 0x724031556159 = 724031556159 383 +))) 384 +* ((( 385 +Version: 0x0064=100=1.0.0 386 +))) 385 385 388 +* ((( 389 +BAT: 0x0c6c = 3180 mV = 3.180V 390 +))) 391 +* ((( 392 +Signal: 0x19 = 25 393 +))) 394 +* ((( 395 +Distance: 0x0292= 658 mm 396 +))) 397 +* ((( 398 +Interrupt: 0x00 = 0 386 386 387 -(% style="color:red" %)**NOTE:** 388 388 389 -(% style="color:red" %) 390 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 391 -1. By default, the device will send an uplink message every 1 hour. 392 392 402 + 403 +))) 393 393 394 -== =2.3.1PayloadAnalyze ===405 +== 2.4 Payload Explanation and Sensor Interface == 395 395 396 -N95S31B uplink payload includes in total 21 bytes 397 397 408 +=== 2.4.1 Device ID === 398 398 399 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 400 -|=(% style="width: 60px;" %)((( 401 -**Size(bytes)** 402 -)))|=(% 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** 403 -|(% 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" %)((( 404 404 ((( 405 - Reserve/Same asNBSN95CFGMOD=1411 +By default, the Device ID equal to the last 6 bytes of IMEI. 406 406 ))) 407 407 408 408 ((( 409 - Nofunctionhere.415 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 410 410 ))) 411 - )))|(% style="width:77px" %)(((417 + 412 412 ((( 413 - [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]419 +**Example:** 414 414 ))) 415 415 416 416 ((( 417 - By SHT31423 +AT+DEUI=A84041F15612 418 418 ))) 419 - )))|(% style="width:80px" %)(((425 + 420 420 ((( 421 - [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]427 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 422 422 ))) 423 423 430 + 431 + 432 +=== 2.4.2 Version Info === 433 + 424 424 ((( 425 - BySHT31435 +Specify the software version: 0x64=100, means firmware version 1.00. 426 426 ))) 427 -))) 428 428 429 429 ((( 430 -((( 431 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 439 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 432 432 ))) 433 -))) 434 434 435 435 436 -[[image:1657354294009-643.png]] 437 437 444 +=== 2.4.3 Battery Info === 438 438 439 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 440 - 441 -* Device ID: 0x724031607457 = 724031607457 442 -* Version: 0x006e=110=1.1.0 443 - 444 -* BAT: 0x0ccd = 3277 mV = 3.277V 445 -* Signal: 0x1b = 27 446 -* Model: 0x01 = 1 447 -* 0x00dc000ccc= reserve, ignore in N95S31B 448 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 449 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 450 - 451 451 ((( 452 - 447 +Ex1: 0x0B45 = 2885mV 453 453 ))) 454 454 455 455 ((( 456 - 451 +Ex2: 0x0B49 = 2889mV 457 457 ))) 458 458 459 459 460 -=== 2.3.2 Device ID === 461 461 456 +=== 2.4.4 Signal Strength === 457 + 462 462 ((( 463 -B ydefault,the Device ID equal to thelast6 bytes of IMEI.459 +NB-IoT Network signal Strength. 464 464 ))) 465 465 466 466 ((( 467 - User can use (% style="color:blue" %)**AT+DEUI**(%%)tosetDevice ID463 +**Ex1: 0x1d = 29** 468 468 ))) 469 469 470 470 ((( 471 - **Example:**467 +(% style="color:blue" %)**0**(%%) -113dBm or less 472 472 ))) 473 473 474 474 ((( 475 - AT+DEUI=A84041F15612471 +(% style="color:blue" %)**1**(%%) -111dBm 476 476 ))) 477 477 478 478 ((( 479 - TheDevice ID isstored in a none-erase area, Upgrade the firmwareorrun**AT+FDR**won't erase Device ID.475 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 480 480 ))) 481 481 478 +((( 479 +(% style="color:blue" %)**31** (%%) -51dBm or greater 480 +))) 482 482 482 +((( 483 +(% style="color:blue" %)**99** (%%) Not known or not detectable 484 +))) 483 483 484 -=== 2.3.3 Version Info === 485 485 486 486 487 - Thesebytesinclude the hardware andsoftwareversion.488 +=== 2.4.5 Distance === 488 488 489 - Higherbyte:Specifyhardwareversion: always0x00forN95S31B490 +Get the distance. Flat object range 280mm - 7500mm. 490 490 491 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110 492 +((( 493 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 494 +))) 492 492 493 - 494 -For example: 0x00 6E: this device is N95S31B with firmware version 110. 495 - 496 496 ((( 497 - 497 +((( 498 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 498 498 ))) 500 +))) 499 499 500 - 501 -=== 2.3.4 Battery Info === 502 - 503 503 ((( 504 - Ex1:0x0B45 = 2885mV503 + 505 505 ))) 506 506 507 507 ((( 508 - Ex2:0x0B49 = 2889mV507 + 509 509 ))) 510 510 510 +=== 2.4.6 Digital Interrupt === 511 511 512 - 513 -=== 2.3.5 Signal Strength === 514 - 515 515 ((( 516 - NB-IoTNetworksignalStrength.513 +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. 517 517 ))) 518 518 519 519 ((( 520 - **Ex1:0x1d= 29**517 +The command is: 521 521 ))) 522 522 523 523 ((( 524 -(% style="color:blue" %)** 0**(%%)-113dBmor less521 +(% 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]])**.** 525 525 ))) 526 526 524 + 527 527 ((( 528 - (%style="color:blue"%)**1**(%%)-111dBm526 +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. 529 529 ))) 530 530 529 + 531 531 ((( 532 - (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm531 +Example: 533 533 ))) 534 534 535 535 ((( 536 -( %style="color:blue"%)**31** (%%) -51dBm or greater535 +0x(00): Normal uplink packet. 537 537 ))) 538 538 539 539 ((( 540 -( %style="color:blue" %)**99** (%%) Notknownor not detectable539 +0x(01): Interrupt Uplink Packet. 541 541 ))) 542 542 543 543 544 544 545 -=== 2. 3.6Temperature& Humidity===544 +=== 2.4.7 +5V Output === 546 546 547 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 546 +((( 547 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 548 +))) 548 548 549 -[[image:image-20220709161741-3.png]] 550 550 551 +((( 552 +The 5V output time can be controlled by AT Command. 553 +))) 551 551 552 -Convert the read byte to decimal and divide it by ten. 555 +((( 556 +(% style="color:blue" %)**AT+5VT=1000** 557 +))) 553 553 559 +((( 560 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 561 +))) 554 554 555 -**Example:** 556 556 557 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 558 558 559 - Humidity:Read:0295(H)=661(D)Value:661 / 10=66.1, So66.1%565 +== 2.5 Downlink Payload == 560 560 561 - 562 - 563 -== 2.4 Downlink Payload == 564 - 565 565 By default, NDDS75 prints the downlink payload to console port. 566 566 567 567 [[image:image-20220709100028-1.png]] ... ... @@ -612,16 +612,51 @@ 612 612 613 613 614 614 615 -== 2. 5BatteryAnalysis==617 +== 2.6 LED Indicator == 616 616 617 -=== 2.5.1 Battery Type === 618 618 620 +The NDDS75 has an internal LED which is to show the status of different state. 619 619 622 + 623 +* 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) 624 +* Then the LED will be on for 1 second means device is boot normally. 625 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 626 +* For each uplink probe, LED will be on for 500ms. 627 + 620 620 ((( 621 - 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.629 + 622 622 ))) 623 623 632 + 633 + 634 +== 2.7 Firmware Change Log == 635 + 636 + 624 624 ((( 638 +Download URL & Firmware Change log 639 +))) 640 + 641 +((( 642 +[[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/]] 643 +))) 644 + 645 + 646 +((( 647 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 648 +))) 649 + 650 + 651 + 652 +== 2.8 Battery Analysis == 653 + 654 +=== 2.8.1 Battery Type === 655 + 656 + 657 +((( 658 +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. 659 +))) 660 + 661 +((( 625 625 The battery is designed to last for several years depends on the actually use environment and update interval. 626 626 ))) 627 627 ... ... @@ -639,35 +639,56 @@ 639 639 640 640 641 641 642 -=== 2. 5.2 Power consumption Analyze ===679 +=== 2.8.2 Power consumption Analyze === 643 643 644 644 ((( 645 - 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.682 +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. 646 646 ))) 647 647 685 + 648 648 ((( 649 - 687 +Instruction to use as below: 650 650 ))) 651 651 690 +((( 691 +(% 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/]] 692 +))) 652 652 653 -=== 2.5.3 Battery Note === 654 654 655 655 ((( 656 - 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.696 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 657 657 ))) 658 658 699 +* ((( 700 +Product Model 701 +))) 702 +* ((( 703 +Uplink Interval 704 +))) 705 +* ((( 706 +Working Mode 707 +))) 659 659 709 +((( 710 +And the Life expectation in difference case will be shown on the right. 711 +))) 660 660 661 - === 2.5.4 Replacethe battery ===713 +[[image:image-20220709110451-3.png]] 662 662 663 663 716 + 717 +=== 2.8.3 Battery Note === 718 + 664 664 ((( 665 - 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.720 +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. 666 666 ))) 667 667 668 668 724 + 725 +=== 2.8.4 Replace the battery === 726 + 669 669 ((( 670 -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).728 +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). 671 671 ))) 672 672 673 673 ... ... @@ -690,7 +690,7 @@ 690 690 691 691 == 4.1 Access AT Commands == 692 692 693 -See NBSN95 AT Command inthis link for detail:BSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]751 +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/]] 694 694 695 695 696 696 AT+<CMD>? : Help on <CMD> ... ... @@ -778,9 +778,7 @@ 778 778 ))) 779 779 780 780 ((( 781 - 782 - 783 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 839 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 784 784 ))) 785 785 786 786 ... ... @@ -812,7 +812,7 @@ 812 812 = 7. Order Info = 813 813 814 814 815 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**871 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 816 816 817 817 818 818 (% class="wikigeneratedid" %) ... ... @@ -827,7 +827,7 @@ 827 827 828 828 (% style="color:#037691" %)**Package Includes**: 829 829 830 -* N 95S31BNB-IoTTemperatureandHumiditySensor886 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 831 831 * External antenna x 1 832 832 ))) 833 833 ... ... @@ -836,10 +836,11 @@ 836 836 837 837 (% style="color:#037691" %)**Dimension and weight**: 838 838 895 + 839 839 * Device Size: 13.0 x 5 x 4.5 cm 840 840 * Device Weight: 150g 841 -* Package Size / pcs : 1 4.0x8x 5 cm842 -* Weight / pcs : 180g898 +* Package Size / pcs : 15 x 12x 5.5 cm 899 +* Weight / pcs : 220g 843 843 ))) 844 844 845 845 (((
- 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