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, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -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 57 + 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -83,6 +83,7 @@ 83 83 84 84 85 85 86 + 86 86 == 1.4 Applications == 87 87 88 88 * Smart Buildings & Home Automation ... ... @@ -131,8 +131,6 @@ 131 131 1. Send an uplink packet 132 132 133 133 134 - 135 - 136 136 = 2. Use N95S31B to communicate with IoT Server = 137 137 138 138 == 2.1 How it works == ... ... @@ -176,7 +176,6 @@ 176 176 * The local NB-IoT network used the band that N95S31B supports. 177 177 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 178 178 179 - 180 180 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 181 181 182 182 N95S31B supports different communication protocol such as : ... ... @@ -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 310 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 311 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 314 314 315 315 [[image:1657352634421-276.png]] 316 316 ... ... @@ -356,58 +356,85 @@ 356 356 357 357 == 2.3 Uplink Payload == 358 358 359 -In this mode, uplink payload includes in total 14 bytes 360 360 358 +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. 361 361 360 + 361 +For example: 362 + 363 + (% 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. 364 + 365 + 366 +The uplink payloads are composed in ASCII String. For example: 367 + 368 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 369 + 370 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 371 + 372 + 373 +(% style="color:red" %)**NOTE:** 374 + 375 +(% style="color:red" %) 376 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]]. 377 +1. By default, the device will send an uplink message every 1 hour. 378 + 379 + 380 + 381 +=== 2.3.1 Payload Analyze === 382 + 383 +N95S31B uplink payload includes in total 21 bytes 384 + 385 + 362 362 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 363 363 |=(% style="width: 60px;" %)((( 364 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"]] 389 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1** 390 +|(% 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:123px" %)MOD 0X01|(% style="width:99px" %)((( 391 +Reserve/ Same as NBSN95 CFGMOD=1 367 367 368 - (((369 - Ifwe usethe MQTT client to subscribe to this MQTT topic,we can see the following information when the NDDS751 uplinkdata.370 - )))393 +No function here. 394 +)))|(% style="width:77px" %)((( 395 +[[Temperature >>||anchor="H2.4.5A0Distance"]] 371 371 397 +By SHT31 398 +)))|(% style="width:80px" %)((( 399 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 372 372 373 -[[image:1657331036973-987.png]] 374 - 375 -((( 376 -The payload is ASCII string, representative same HEX: 401 +By SHT31 377 377 ))) 378 378 379 379 ((( 380 -0x72403155615900640c6c19029200 where: 405 +((( 406 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 381 381 ))) 382 - 383 -* ((( 384 -Device ID: 0x724031556159 = 724031556159 385 385 ))) 386 -* ((( 387 -Version: 0x0064=100=1.0.0 388 -))) 389 389 390 -* ((( 391 -BAT: 0x0c6c = 3180 mV = 3.180V 392 -))) 393 -* ((( 394 -Signal: 0x19 = 25 395 -))) 396 -* ((( 397 -Distance: 0x0292= 658 mm 398 -))) 399 -* ((( 400 -Interrupt: 0x00 = 0 401 401 411 +[[image:1657354294009-643.png]] 402 402 403 403 414 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 415 + 416 +* Device ID: 0x724031607457 = 724031607457 417 +* Version: 0x006e=110=1.1.0 418 + 419 +* BAT: 0x0ccd = 3277 mV = 3.277V 420 +* Signal: 0x1b = 27 421 +* Model: 0x01 = 1 422 +* 0x00dc000ccc= reserve, ignore in N95S31B 423 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 424 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 425 + 426 +((( 404 404 405 405 ))) 406 406 407 -== 2.4 Payload Explanation and Sensor Interface == 430 +((( 431 + 432 +))) 408 408 409 409 410 -=== 2. 4.1435 +=== 2.3.2 Device ID === 411 411 412 412 ((( 413 413 By default, the Device ID equal to the last 6 bytes of IMEI. ... ... @@ -431,20 +431,25 @@ 431 431 432 432 433 433 434 -=== 2. 4.2Version Info ===459 +=== 2.3.3 Version Info === 435 435 436 -((( 437 -Specify the software version: 0x64=100, means firmware version 1.00. 438 -))) 439 439 462 +These bytes include the hardware and software version. 463 + 464 +Higher byte: Specify hardware version: always 0x00 for N95S31B 465 + 466 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 467 + 468 + 469 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 470 + 440 440 ((( 441 - Forexample: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.472 + 442 442 ))) 443 443 444 444 476 +=== 2.3.4 Battery Info === 445 445 446 -=== 2.4.3 Battery Info === 447 - 448 448 ((( 449 449 Ex1: 0x0B45 = 2885mV 450 450 ))) ... ... @@ -455,7 +455,7 @@ 455 455 456 456 457 457 458 -=== 2. 4.4Signal Strength ===488 +=== 2.3.5 Signal Strength === 459 459 460 460 ((( 461 461 NB-IoT Network signal Strength. ... ... @@ -487,83 +487,24 @@ 487 487 488 488 489 489 490 -=== 2. 4.5Distance ===520 +=== 2.3.6 Temperature & Humidity === 491 491 492 - Get the distance.Flatobject range280mm-7500mm.522 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 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 -))) 524 +[[image:image-20220709161741-3.png]] 497 497 498 -((( 499 -((( 500 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 501 -))) 502 -))) 503 503 504 -((( 505 - 506 -))) 527 +Convert the read byte to decimal and divide it by ten. 507 507 508 -((( 509 - 510 -))) 511 511 512 - === 2.4.6 DigitalInterrupt ===530 +**Example:** 513 513 514 -((( 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. 516 -))) 532 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 517 517 518 -((( 519 -The command is: 520 -))) 534 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 521 521 522 -((( 523 -(% 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]])**.** 524 -))) 525 525 526 526 527 -((( 528 -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 -))) 530 - 531 - 532 -((( 533 -Example: 534 -))) 535 - 536 -((( 537 -0x(00): Normal uplink packet. 538 -))) 539 - 540 -((( 541 -0x(01): Interrupt Uplink Packet. 542 -))) 543 - 544 - 545 - 546 -=== 2.4.7 +5V Output === 547 - 548 -((( 549 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 550 -))) 551 - 552 - 553 -((( 554 -The 5V output time can be controlled by AT Command. 555 -))) 556 - 557 -((( 558 -(% style="color:blue" %)**AT+5VT=1000** 559 -))) 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 - 565 - 566 - 567 567 == 2.5 Downlink Payload == 568 568 569 569 By default, NDDS75 prints the downlink payload to console port. ... ... @@ -616,41 +616,6 @@ 616 616 617 617 618 618 619 -== 2.6 LED Indicator == 620 - 621 - 622 -The NDDS75 has an internal LED which is to show the status of different state. 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 -((( 631 - 632 -))) 633 - 634 - 635 - 636 -== 2.7 Firmware Change Log == 637 - 638 - 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 654 == 2.8 Battery Analysis == 655 655 656 656 === 2.8.1 Battery Type ===
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +111.2 KB - Content