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, 2 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -9,6 +9,7 @@ 9 9 10 10 **Table of Contents:** 11 11 12 +{{toc/}} 12 12 13 13 14 14 ... ... @@ -21,16 +21,29 @@ 21 21 ((( 22 22 23 23 25 +((( 24 24 The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*. 27 +))) 25 25 29 +((( 26 26 The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use. 31 +))) 27 27 33 +((( 28 28 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 35 +))) 29 29 37 +((( 30 30 N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report). 39 +))) 31 31 41 +((( 42 + 43 +))) 32 32 45 +((( 33 33 ~* make sure you have NB-IoT coverage locally. 47 +))) 34 34 35 35 36 36 ))) ... ... @@ -41,7 +41,6 @@ 41 41 42 42 == 1.2 Features == 43 43 44 - 45 45 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 46 46 * Monitor Temperature & Humidity via SHT31 47 47 * AT Commands to change parameters ... ... @@ -55,6 +55,7 @@ 55 55 56 56 57 57 71 + 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -63,6 +63,7 @@ 63 63 * Supply Voltage: 2.1v ~~ 3.6v 64 64 * Operating Temperature: -40 ~~ 85°C 65 65 80 + 66 66 (% style="color:#037691" %)**NB-IoT Spec:** 67 67 68 68 * - B1 @H-FDD: 2100MHz ... ... @@ -72,9 +72,9 @@ 72 72 * - B20 @H-FDD: 800MHz 73 73 * - B28 @H-FDD: 700MHz 74 74 90 + 75 75 (% style="color:#037691" %)**Battery:** 76 76 77 - 78 78 * Li/SOCI2 un-chargeable battery 79 79 * Capacity: 8500mAh 80 80 * Self Discharge: <1% / Year @ 25°C ... ... @@ -83,6 +83,7 @@ 83 83 84 84 85 85 101 + 86 86 == 1.4 Applications == 87 87 88 88 * Smart Buildings & Home Automation ... ... @@ -111,9 +111,13 @@ 111 111 112 112 === 1.5.2 BOOT MODE / SW1 === 113 113 130 +((( 114 114 1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. 132 +))) 115 115 134 +((( 116 116 2) Flash: work mode, device starts to work and send out console output for further debug 136 +))) 117 117 118 118 119 119 ... ... @@ -170,24 +170,45 @@ 170 170 === 2.2.1 Test Requirement === 171 171 172 172 193 +((( 173 173 To use N95S31B in your city, make sure meet below requirements: 195 +))) 174 174 175 -* Your local operator has already distributed a NB-IoT Network there. 176 -* The local NB-IoT network used the band that N95S31B supports. 177 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 197 +* ((( 198 +Your local operator has already distributed a NB-IoT Network there. 199 +))) 200 +* ((( 201 +The local NB-IoT network used the band that N95S31B supports. 202 +))) 203 +* ((( 204 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 205 +))) 178 178 179 - 207 +((( 180 180 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 209 +))) 181 181 211 +((( 182 182 N95S31B supports different communication protocol such as : 213 +))) 183 183 184 184 ((( 185 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 186 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 187 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 188 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 216 +* ((( 217 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 218 +))) 219 +* ((( 220 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 221 +))) 222 +* ((( 223 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 224 +))) 225 +* ((( 226 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 227 +))) 189 189 229 +((( 190 190 We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server. 231 +))) 191 191 192 192 193 193 ))) ... ... @@ -309,8 +309,8 @@ 309 309 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 310 310 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 311 311 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 312 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 313 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 353 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 354 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 314 314 315 315 [[image:1657352634421-276.png]] 316 316 ... ... @@ -356,216 +356,220 @@ 356 356 357 357 == 2.3 Uplink Payload == 358 358 359 -In this mode, uplink payload includes in total 14 bytes 360 360 401 +((( 402 +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. 403 +))) 361 361 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"]] 367 367 368 368 ((( 369 - If we use the MQTT client tosubscribeto this MQTT topic, wecan see the following information when the NDDS751 uplink data.407 +For example: 370 370 ))) 371 371 410 +((( 411 + (% 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. 412 +))) 372 372 373 -[[image:1657331036973-987.png]] 374 374 375 375 ((( 376 -The payload is ASCIIstring,representative sameHEX:416 +The uplink payloads are composed in ASCII String. For example: 377 377 ))) 378 378 379 379 ((( 380 -0 x72403155615900640c6c19029200where:420 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 381 381 ))) 382 382 383 - *(((384 - DeviceID:0x724031556159=724031556159423 +((( 424 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 385 385 ))) 386 -* ((( 387 -Version: 0x0064=100=1.0.0 426 + 427 + 428 +((( 429 +(% style="color:red" %)**NOTE:** 388 388 ))) 389 389 390 -* ((( 391 -BAT: 0x0c6c = 3180 mV = 3.180V 432 +(% style="color:red" %) 433 +1. ((( 434 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 392 392 ))) 393 - *(((394 - Signal:0x19=25436 +1. ((( 437 +By default, the device will send an uplink message every 1 hour. 395 395 ))) 396 -* ((( 397 -Distance: 0x0292= 658 mm 398 -))) 399 -* ((( 400 -Interrupt: 0x00 = 0 401 401 402 402 403 403 404 - 405 -))) 406 406 407 -== 2. 4PayloadExplanation and SensorInterface==443 +=== 2.3.1 Payload Analyze === 408 408 445 +N95S31B uplink payload includes in total 21 bytes 409 409 410 -=== 2.4.1 Device ID === 411 411 448 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 449 +|=(% style="width: 60px;" %)((( 450 +**Size(bytes)** 451 +)))|=(% 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** 452 +|(% 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" %)((( 412 412 ((( 413 - By default, theDeviceID equal to thelast6bytes of IMEI.454 +Reserve/ Same as NBSN95 CFGMOD=1 414 414 ))) 415 415 416 416 ((( 417 - Usercanuse (% style="color:blue" %)**AT+DEUI**(%%)toset Device ID458 +No function here. 418 418 ))) 419 - 460 +)))|(% style="width:77px" %)((( 420 420 ((( 421 - **Example:**462 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 422 422 ))) 423 423 424 424 ((( 425 - AT+DEUI=A84041F15612466 +By SHT31 426 426 ))) 427 - 468 +)))|(% style="width:80px" %)((( 428 428 ((( 429 - The Device ID is storednane-erasearea, Upgradethe firmwareor run **AT+FDR** won'terase Device ID.470 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 430 430 ))) 431 431 432 - 433 - 434 -=== 2.4.2 Version Info === 435 - 436 436 ((( 437 - Specifythe software version: 0x64=100, means firmware version 1.00.474 +By SHT31 438 438 ))) 476 +))) 439 439 440 440 ((( 441 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 479 +((( 480 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 442 442 ))) 482 +))) 443 443 444 444 485 +[[image:1657354294009-643.png]] 445 445 446 -=== 2.4.3 Battery Info === 447 447 488 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 489 + 490 +* Device ID: 0x724031607457 = 724031607457 491 +* Version: 0x006e=110=1.1.0 492 + 493 +* BAT: 0x0ccd = 3277 mV = 3.277V 494 +* Signal: 0x1b = 27 495 +* Model: 0x01 = 1 496 +* 0x00dc000ccc= reserve, ignore in N95S31B 497 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 498 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 499 + 448 448 ((( 449 - Ex1:0x0B45 = 2885mV501 + 450 450 ))) 451 451 452 452 ((( 453 - Ex2:0x0B49 = 2889mV505 + 454 454 ))) 455 455 456 456 509 +=== 2.3.2 Device ID === 457 457 458 -=== 2.4.4 Signal Strength === 459 - 460 460 ((( 461 - NB-IoTNetworksignalStrength.512 +By default, the Device ID equal to the last 6 bytes of IMEI. 462 462 ))) 463 463 464 464 ((( 465 - **Ex1:0x1d=29**516 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 466 466 ))) 467 467 468 468 ((( 469 - (% style="color:blue" %)**0**(%%) -113dBmorless520 +**Example:** 470 470 ))) 471 471 472 472 ((( 473 - (% style="color:blue" %)**1**(%%) -111dBm524 +AT+DEUI=A84041F15612 474 474 ))) 475 475 476 476 ((( 477 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm528 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 478 478 ))) 479 479 480 -((( 481 -(% style="color:blue" %)**31** (%%) -51dBm or greater 482 -))) 483 483 484 -((( 485 -(% style="color:blue" %)**99** (%%) Not known or not detectable 486 -))) 487 487 533 +=== 2.3.3 Version Info === 488 488 489 489 490 - ===2.4.5Distance===536 +These bytes include the hardware and software version. 491 491 492 - Get thedistance.Flat objectrange280mm-7500mm.538 +Higher byte: Specify hardware version: always 0x00 for N95S31B 493 493 494 -((( 495 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 496 -))) 540 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 497 497 542 + 543 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 544 + 498 498 ((( 499 -((( 500 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 546 + 501 501 ))) 502 -))) 503 503 549 + 550 +=== 2.3.4 Battery Info === 551 + 504 504 ((( 505 - 553 +Ex1: 0x0B45 = 2885mV 506 506 ))) 507 507 508 508 ((( 509 - 557 +Ex2: 0x0B49 = 2889mV 510 510 ))) 511 511 512 -=== 2.4.6 Digital Interrupt === 513 513 561 + 562 +=== 2.3.5 Signal Strength === 563 + 514 514 ((( 515 - DigitalInterrupt refers topin (% style="color:blue" %)**GPIO_EXTI**(%%),and there are differenttrigger methods. When thereisa trigger, the NDDS75 will sendapacketto the server.565 +NB-IoT Network signal Strength. 516 516 ))) 517 517 518 518 ((( 519 - Thecommandis:569 +**Ex1: 0x1d = 29** 520 520 ))) 521 521 522 522 ((( 523 -(% 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]])**.**573 +(% style="color:blue" %)**0**(%%) -113dBm or less 524 524 ))) 525 525 526 - 527 527 ((( 528 - Thelower four bitsofthis data field shows if this packet is generatedby interruptornot.Clickhereforthehardwareandsoftware set up.577 +(% style="color:blue" %)**1**(%%) -111dBm 529 529 ))) 530 530 531 - 532 532 ((( 533 - Example:581 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 534 534 ))) 535 535 536 536 ((( 537 - 0x(00):Normalplinkpacket.585 +(% style="color:blue" %)**31** (%%) -51dBm or greater 538 538 ))) 539 539 540 540 ((( 541 - 0x(01):InterruptUplinkPacket.589 +(% style="color:blue" %)**99** (%%) Not known or not detectable 542 542 ))) 543 543 544 544 545 545 546 -=== 2. 4.7+5VOutput===594 +=== 2.3.6 Temperature & Humidity === 547 547 548 -((( 549 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 550 -))) 596 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 551 551 598 +[[image:image-20220709161741-3.png]] 552 552 553 -((( 554 -The 5V output time can be controlled by AT Command. 555 -))) 556 556 557 -((( 558 -(% style="color:blue" %)**AT+5VT=1000** 559 -))) 601 +Convert the read byte to decimal and divide it by ten. 560 560 561 -((( 562 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 563 -))) 564 564 604 +**Example:** 565 565 606 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 566 566 567 - ==2.5Downlink Payload==608 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 568 568 610 + 611 + 612 +== 2.4 Downlink Payload == 613 + 569 569 By default, NDDS75 prints the downlink payload to console port. 570 570 571 571 [[image:image-20220709100028-1.png]] ... ... @@ -616,51 +616,16 @@ 616 616 617 617 618 618 619 -== 2. 6LED Indicator ==664 +== 2.5 Battery Analysis == 620 620 666 +=== 2.5.1 Battery Type === 621 621 622 -The NDDS75 has an internal LED which is to show the status of different state. 623 623 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 - 630 630 ((( 631 - 670 +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. 632 632 ))) 633 633 634 - 635 - 636 -== 2.7 Firmware Change Log == 637 - 638 - 639 639 ((( 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 -((( 664 664 The battery is designed to last for several years depends on the actually use environment and update interval. 665 665 ))) 666 666 ... ... @@ -678,56 +678,35 @@ 678 678 679 679 680 680 681 -=== 2. 8.2 Power consumption Analyze ===691 +=== 2.5.2 Power consumption Analyze === 682 682 683 683 ((( 684 - Draginobatterypoweredproductareall runsinLow Powermode.Wehave an update battery calculatorwhichbaseonthe measurement oftherealdevice. User can usethis calculatortocheck the batterylifeandcalculatethe batterylifeifwant tousedifferenttransmit interval.694 +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. 685 685 ))) 686 686 687 - 688 688 ((( 689 - Instructionto use as below:698 + 690 690 ))) 691 691 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 -))) 695 695 702 +=== 2.5.3 Battery Note === 696 696 697 697 ((( 698 - (%style="color:blue"%)**Step2:**(%%)Open it andchoose705 +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. 699 699 ))) 700 700 701 -* ((( 702 -Product Model 703 -))) 704 -* ((( 705 -Uplink Interval 706 -))) 707 -* ((( 708 -Working Mode 709 -))) 710 710 711 -((( 712 -And the Life expectation in difference case will be shown on the right. 713 -))) 714 714 715 - [[image:image-20220709110451-3.png]]710 +=== 2.5.4 Replace the battery === 716 716 717 717 718 - 719 -=== 2.8.3 Battery Note === 720 - 721 721 ((( 722 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.714 +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. 723 723 ))) 724 724 725 725 726 - 727 -=== 2.8.4 Replace the battery === 728 - 729 729 ((( 730 -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).719 +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). 731 731 ))) 732 732 733 733 ... ... @@ -750,7 +750,7 @@ 750 750 751 751 == 4.1 Access AT Commands == 752 752 753 -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/]]742 +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/]] 754 754 755 755 756 756 AT+<CMD>? : Help on <CMD> ... ... @@ -838,8 +838,12 @@ 838 838 ))) 839 839 840 840 ((( 841 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 830 + 831 + 832 +((( 833 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 842 842 ))) 835 +))) 843 843 844 844 845 845 ... ... @@ -870,7 +870,7 @@ 870 870 = 7. Order Info = 871 871 872 872 873 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**866 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 874 874 875 875 876 876 (% class="wikigeneratedid" %) ... ... @@ -885,7 +885,7 @@ 885 885 886 886 (% style="color:#037691" %)**Package Includes**: 887 887 888 -* NS E01DistanceDetectSensorNode x 1881 +* N95S31B NB-IoT Temperature and Humidity Sensor 889 889 * External antenna x 1 890 890 ))) 891 891 ... ... @@ -894,11 +894,10 @@ 894 894 895 895 (% style="color:#037691" %)**Dimension and weight**: 896 896 897 - 898 898 * Device Size: 13.0 x 5 x 4.5 cm 899 899 * Device Weight: 150g 900 -* Package Size / pcs : 1 5x12x 5.5cm901 -* Weight / pcs : 220g892 +* Package Size / pcs : 14.0 x 8x 5 cm 893 +* Weight / pcs : 180g 902 902 ))) 903 903 904 904 (((
- 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