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, 2 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 ... ... @@ -87,6 +87,7 @@ 87 87 88 88 (% style="color:#037691" %)**Battery:** 89 89 77 + 90 90 * Li/SOCI2 un-chargeable battery 91 91 * Capacity: 8500mAh 92 92 * Self Discharge: <1% / Year @ 25°C ... ... @@ -108,7 +108,7 @@ 108 108 109 109 110 110 111 -== 1.5 Pin Definitions & Switch==99 +== 1.5 Pin Definitions == 112 112 113 113 N95S31B use the mother board from NBSN95 which as below. 114 114 ... ... @@ -123,13 +123,9 @@ 123 123 124 124 === 1.5.2 BOOT MODE / SW1 === 125 125 126 -((( 127 127 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 -))) 129 129 130 -((( 131 131 2) Flash: work mode, device starts to work and send out console output for further debug 132 -))) 133 133 134 134 135 135 ... ... @@ -147,6 +147,8 @@ 147 147 1. Send an uplink packet 148 148 149 149 134 + 135 + 150 150 = 2. Use N95S31B to communicate with IoT Server = 151 151 152 152 == 2.1 How it works == ... ... @@ -165,7 +165,7 @@ 165 165 166 166 ))) 167 167 168 -[[image:16575 20100595-569.png]]154 +[[image:1657350248151-650.png]] 169 169 170 170 ((( 171 171 ... ... @@ -184,45 +184,24 @@ 184 184 === 2.2.1 Test Requirement === 185 185 186 186 187 -((( 188 188 To use N95S31B in your city, make sure meet below requirements: 189 -))) 190 190 191 -* ((( 192 -Your local operator has already distributed a NB-IoT Network there. 193 -))) 194 -* ((( 195 -The local NB-IoT network used the band that N95S31B supports. 196 -))) 197 -* ((( 198 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 199 -))) 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. 200 200 201 - (((179 + 202 202 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 203 -))) 204 204 205 -((( 206 206 N95S31B supports different communication protocol such as : 207 -))) 208 208 209 209 ((( 210 -* ((( 211 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 212 -))) 213 -* ((( 214 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 215 -))) 216 -* ((( 217 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 218 -))) 219 -* ((( 220 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 221 -))) 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(%%)) 222 222 223 -((( 224 224 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. 225 -))) 226 226 227 227 228 228 ))) ... ... @@ -344,8 +344,8 @@ 344 344 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 345 345 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 346 346 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 347 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 348 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 312 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 313 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 349 349 350 350 [[image:1657352634421-276.png]] 351 351 ... ... @@ -391,44 +391,48 @@ 391 391 392 392 == 2.3 Uplink Payload == 393 393 359 +In this mode, uplink payload includes in total 14 bytes 394 394 395 -((( 396 -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. 397 -))) 398 398 362 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 363 +|=(% style="width: 60px;" %)((( 364 +**Size(bytes)** 365 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 366 +|(% 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"]] 399 399 400 400 ((( 401 - For example:369 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 402 402 ))) 403 403 404 -((( 405 - (% 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. 406 -))) 407 407 373 +[[image:1657331036973-987.png]] 408 408 409 409 ((( 410 -The uplink payloadsare composedinASCIIString.Forxample:376 +The payload is ASCII string, representative same HEX: 411 411 ))) 412 412 413 413 ((( 414 -0 a cd00ed0acc0ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:380 +0x72403155615900640c6c19029200 where: 415 415 ))) 416 416 417 -((( 418 - 0x 0acd 00ed0acc0000ef 02d21d Total12 bytes383 +* ((( 384 +Device ID: 0x724031556159 = 724031556159 419 419 ))) 420 - 421 - 422 -((( 423 -(% style="color:red" %)**NOTE:** 386 +* ((( 387 +Version: 0x0064=100=1.0.0 424 424 ))) 425 425 426 -(% style="color:red" %) 427 -1. ((( 428 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 390 +* ((( 391 +BAT: 0x0c6c = 3180 mV = 3.180V 429 429 ))) 430 -1. ((( 431 -By default, the device will send an uplink message every 1 hour. 393 +* ((( 394 +Signal: 0x19 = 25 395 +))) 396 +* ((( 397 +Distance: 0x0292= 658 mm 398 +))) 399 +* ((( 400 +Interrupt: 0x00 = 0 432 432 433 433 434 434 ... ... @@ -435,108 +435,105 @@ 435 435 436 436 ))) 437 437 438 -== =2.3.1PayloadAnalyze ===407 +== 2.4 Payload Explanation and Sensor Interface == 439 439 440 -N95S31B uplink payload includes in total 21 bytes 441 441 410 +=== 2.4.1 Device ID === 442 442 443 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 444 -|=(% style="width: 60px;" %)((( 445 -**Size(bytes)** 446 -)))|=(% 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** 447 -|(% 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" %)((( 448 448 ((( 449 - Reserve/Same asNBSN95CFGMOD=1413 +By default, the Device ID equal to the last 6 bytes of IMEI. 450 450 ))) 451 451 452 452 ((( 453 - Nofunctionhere.417 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 454 454 ))) 455 - )))|(% style="width:77px" %)(((419 + 456 456 ((( 457 - [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]421 +**Example:** 458 458 ))) 459 459 460 460 ((( 461 - By SHT31425 +AT+DEUI=A84041F15612 462 462 ))) 463 - )))|(% style="width:80px" %)(((427 + 464 464 ((( 465 - [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]429 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 466 466 ))) 467 467 432 + 433 + 434 +=== 2.4.2 Version Info === 435 + 468 468 ((( 469 - BySHT31437 +Specify the software version: 0x64=100, means firmware version 1.00. 470 470 ))) 471 -))) 472 472 473 473 ((( 474 -((( 475 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 441 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 476 476 ))) 477 -))) 478 478 479 479 480 -[[image:1657354294009-643.png]] 481 481 446 +=== 2.4.3 Battery Info === 482 482 483 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 448 +((( 449 +Ex1: 0x0B45 = 2885mV 450 +))) 484 484 485 -* Device ID: 0x724031607457 = 724031607457 486 -* Version: 0x006e=110=1.1.0 452 +((( 453 +Ex2: 0x0B49 = 2889mV 454 +))) 487 487 488 -* BAT: 0x0ccd = 3277 mV = 3.277V 489 -* Signal: 0x1b = 27 490 -* Model: 0x01 = 1 491 -* 0x00dc000ccc= reserve, ignore in N95S31B 492 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 493 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 494 494 457 + 458 +=== 2.4.4 Signal Strength === 459 + 495 495 ((( 496 - 461 +NB-IoT Network signal Strength. 497 497 ))) 498 498 499 499 ((( 500 - 465 +**Ex1: 0x1d = 29** 501 501 ))) 502 502 503 - 504 -=== 2.3.2 Device ID === 505 - 506 506 ((( 507 - Bydefault, theDeviceIDequaltothelast6bytesofIMEI.469 +(% style="color:blue" %)**0**(%%) -113dBm or less 508 508 ))) 509 509 510 510 ((( 511 - User can use(% style="color:blue" %)**AT+DEUI**(%%)tosetDeviceID473 +(% style="color:blue" %)**1**(%%) -111dBm 512 512 ))) 513 513 514 514 ((( 515 - **Example:**477 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 516 516 ))) 517 517 518 518 ((( 519 - AT+DEUI=A84041F15612481 +(% style="color:blue" %)**31** (%%) -51dBm or greater 520 520 ))) 521 521 522 522 ((( 523 - TheDevice ID isstoredinanone-erasearea,Upgradethefirmwareorrun**AT+FDR** won't eraseDeviceID.485 +(% style="color:blue" %)**99** (%%) Not known or not detectable 524 524 ))) 525 525 526 526 527 527 528 -=== 2. 3.3VersionInfo===490 +=== 2.4.5 Distance === 529 529 492 +Get the distance. Flat object range 280mm - 7500mm. 493 + 530 530 ((( 531 - Thesebytes include the hardware andsoftwareversion.495 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 532 532 ))) 533 533 534 534 ((( 535 -Higher byte: Specify hardware version: always 0x00 for N95S31B 499 +((( 500 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 536 536 ))) 502 +))) 537 537 538 538 ((( 539 - Lowerbyte: Specify the software version: 0x6E=110, means firmware version 110505 + 540 540 ))) 541 541 542 542 ((( ... ... @@ -543,81 +543,65 @@ 543 543 544 544 ))) 545 545 512 +=== 2.4.6 Digital Interrupt === 513 + 546 546 ((( 547 - For example:0x00 6E:thisdevice isN95S31Bwithfirmwareversion110.515 +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. 548 548 ))) 549 549 550 550 ((( 551 - 519 +The command is: 552 552 ))) 553 553 554 - 555 -=== 2.3.4 Battery Info === 556 - 557 557 ((( 558 - Ex1:0x0B45=2885mV523 +(% 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]])**.** 559 559 ))) 560 560 526 + 561 561 ((( 562 - Ex2:0x0B49=2889mV528 +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. 563 563 ))) 564 564 565 565 566 - 567 -=== 2.3.5 Signal Strength === 568 - 569 569 ((( 570 - NB-IoT Network signalStrength.533 +Example: 571 571 ))) 572 572 573 573 ((( 574 - **Ex1:0x1d=29**537 +0x(00): Normal uplink packet. 575 575 ))) 576 576 577 577 ((( 578 -( %style="color:blue"%)**0**(%%) -113dBm orless541 +0x(01): Interrupt Uplink Packet. 579 579 ))) 580 580 544 + 545 + 546 +=== 2.4.7 +5V Output === 547 + 581 581 ((( 582 - (%style="color:blue"%)**1**(%%)-111dBm549 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 583 583 ))) 584 584 552 + 585 585 ((( 586 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm554 +The 5V output time can be controlled by AT Command. 587 587 ))) 588 588 589 589 ((( 590 -(% style="color:blue" %)** 31**(%%) -51dBm or greater558 +(% style="color:blue" %)**AT+5VT=1000** 591 591 ))) 592 592 593 593 ((( 594 - (%style="color:blue"%)**99**(%%)Notknownornotdetectable562 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 595 595 ))) 596 596 597 597 598 598 599 -== =2.3.6Temperature & Humidity ===567 +== 2.5 Downlink Payload == 600 600 601 - Thedevice will beabletoget theSHT31temperature and humiditydatanowandupload toIoT Server.569 +By default, NDDS75 prints the downlink payload to console port. 602 602 603 -[[image:image-20220709161741-3.png]] 604 - 605 - 606 -Convert the read byte to decimal and divide it by ten. 607 - 608 - 609 -**Example:** 610 - 611 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 612 - 613 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 614 - 615 - 616 - 617 -== 2.4 Downlink Payload == 618 - 619 -By default, N95S31B prints the downlink payload to console port. 620 - 621 621 [[image:image-20220709100028-1.png]] 622 622 623 623 ... ... @@ -654,7 +654,7 @@ 654 654 ))) 655 655 656 656 ((( 657 -If payload = 0x04FF, it will reset the 95S31B607 +If payload = 0x04FF, it will reset the NDDS75 658 658 ))) 659 659 660 660 ... ... @@ -666,16 +666,51 @@ 666 666 667 667 668 668 669 -== 2. 5BatteryAnalysis==619 +== 2.6 LED Indicator == 670 670 671 -=== 2.5.1 Battery Type === 672 672 622 +The NDDS75 has an internal LED which is to show the status of different state. 673 673 624 + 625 +* 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) 626 +* Then the LED will be on for 1 second means device is boot normally. 627 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 628 +* For each uplink probe, LED will be on for 500ms. 629 + 674 674 ((( 675 - 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.631 + 676 676 ))) 677 677 634 + 635 + 636 +== 2.7 Firmware Change Log == 637 + 638 + 678 678 ((( 640 +Download URL & Firmware Change log 641 +))) 642 + 643 +((( 644 +[[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/]] 645 +))) 646 + 647 + 648 +((( 649 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 650 +))) 651 + 652 + 653 + 654 +== 2.8 Battery Analysis == 655 + 656 +=== 2.8.1 Battery Type === 657 + 658 + 659 +((( 660 +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. 661 +))) 662 + 663 +((( 679 679 The battery is designed to last for several years depends on the actually use environment and update interval. 680 680 ))) 681 681 ... ... @@ -693,35 +693,56 @@ 693 693 694 694 695 695 696 -=== 2. 5.2 Power consumption Analyze ===681 +=== 2.8.2 Power consumption Analyze === 697 697 698 698 ((( 699 - 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.684 +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. 700 700 ))) 701 701 687 + 702 702 ((( 703 - 689 +Instruction to use as below: 704 704 ))) 705 705 692 +((( 693 +(% 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/]] 694 +))) 706 706 707 -=== 2.5.3 Battery Note === 708 708 709 709 ((( 710 - 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.698 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 711 711 ))) 712 712 701 +* ((( 702 +Product Model 703 +))) 704 +* ((( 705 +Uplink Interval 706 +))) 707 +* ((( 708 +Working Mode 709 +))) 713 713 711 +((( 712 +And the Life expectation in difference case will be shown on the right. 713 +))) 714 714 715 - === 2.5.4 Replacethe battery ===715 +[[image:image-20220709110451-3.png]] 716 716 717 717 718 + 719 +=== 2.8.3 Battery Note === 720 + 718 718 ((( 719 - 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.722 +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. 720 720 ))) 721 721 722 722 726 + 727 +=== 2.8.4 Replace the battery === 728 + 723 723 ((( 724 -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).730 +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). 725 725 ))) 726 726 727 727 ... ... @@ -744,7 +744,7 @@ 744 744 745 745 == 4.1 Access AT Commands == 746 746 747 -See NBSN95 AT Command inthis link for detail:BSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]753 +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/]] 748 748 749 749 750 750 AT+<CMD>? : Help on <CMD> ... ... @@ -832,12 +832,8 @@ 832 832 ))) 833 833 834 834 ((( 835 - 836 - 837 -((( 838 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 841 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 839 839 ))) 840 -))) 841 841 842 842 843 843 ... ... @@ -868,7 +868,7 @@ 868 868 = 7. Order Info = 869 869 870 870 871 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**873 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 872 872 873 873 874 874 (% class="wikigeneratedid" %) ... ... @@ -883,7 +883,7 @@ 883 883 884 884 (% style="color:#037691" %)**Package Includes**: 885 885 886 -* N 95S31BNB-IoTTemperatureandHumiditySensor888 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 887 887 * External antenna x 1 888 888 ))) 889 889 ... ... @@ -892,10 +892,11 @@ 892 892 893 893 (% style="color:#037691" %)**Dimension and weight**: 894 894 897 + 895 895 * Device Size: 13.0 x 5 x 4.5 cm 896 896 * Device Weight: 150g 897 -* Package Size / pcs : 1 4.0x8x 5 cm898 -* Weight / pcs : 180g900 +* Package Size / pcs : 15 x 12x 5.5 cm 901 +* Weight / pcs : 220g 899 899 ))) 900 900 901 901 (((
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.2 KB - Content