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, 1 removed)
Details
- Page properties
-
- Content
-
... ... @@ -41,6 +41,7 @@ 41 41 42 42 == 1.2 Features == 43 43 44 + 44 44 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 45 45 * Monitor Temperature & Humidity via SHT31 46 46 * AT Commands to change parameters ... ... @@ -54,7 +54,6 @@ 54 54 55 55 56 56 57 - 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -83,7 +83,6 @@ 83 83 84 84 85 85 86 - 87 87 == 1.4 Applications == 88 88 89 89 * Smart Buildings & Home Automation ... ... @@ -132,6 +132,8 @@ 132 132 1. Send an uplink packet 133 133 134 134 134 + 135 + 135 135 = 2. Use N95S31B to communicate with IoT Server = 136 136 137 137 == 2.1 How it works == ... ... @@ -175,6 +175,7 @@ 175 175 * The local NB-IoT network used the band that N95S31B supports. 176 176 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 177 177 179 + 178 178 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 179 179 180 180 N95S31B supports different communication protocol such as : ... ... @@ -307,8 +307,8 @@ 307 307 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 308 308 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 309 309 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 310 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 311 -* (% 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 312 312 313 313 [[image:1657352634421-276.png]] 314 314 ... ... @@ -354,85 +354,58 @@ 354 354 355 355 == 2.3 Uplink Payload == 356 356 359 +In this mode, uplink payload includes in total 14 bytes 357 357 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. 359 359 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 - 386 386 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 387 387 |=(% style="width: 60px;" %)((( 388 388 **Size(bytes)** 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 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"]] 392 392 393 - No function here.394 - )))|(%style="width:77px"%)(((395 - [[Temperature >>||anchor="H2.4.5A0Distance"]]368 +((( 369 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 370 +))) 396 396 397 -By SHT31 398 -)))|(% style="width:80px" %)((( 399 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 400 400 401 -By SHT31 373 +[[image:1657331036973-987.png]] 374 + 375 +((( 376 +The payload is ASCII string, representative same HEX: 402 402 ))) 403 403 404 404 ((( 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. 380 +0x72403155615900640c6c19029200 where: 407 407 ))) 382 + 383 +* ((( 384 +Device ID: 0x724031556159 = 724031556159 408 408 ))) 386 +* ((( 387 +Version: 0x0064=100=1.0.0 388 +))) 409 409 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 410 410 411 -[[image:1657354294009-643.png]] 412 412 413 413 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 -((( 427 427 428 428 ))) 429 429 430 -((( 431 - 432 -))) 407 +== 2.4 Payload Explanation and Sensor Interface == 433 433 434 434 435 -=== 2. 3.2410 +=== 2.4.1 Device ID === 436 436 437 437 ((( 438 438 By default, the Device ID equal to the last 6 bytes of IMEI. ... ... @@ -456,25 +456,20 @@ 456 456 457 457 458 458 459 -=== 2. 3.3Version Info ===434 +=== 2.4.2 Version Info === 460 460 436 +((( 437 +Specify the software version: 0x64=100, means firmware version 1.00. 438 +))) 461 461 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 - 471 471 ((( 472 - 441 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 473 473 ))) 474 474 475 475 476 -=== 2.3.4 Battery Info === 477 477 446 +=== 2.4.3 Battery Info === 447 + 478 478 ((( 479 479 Ex1: 0x0B45 = 2885mV 480 480 ))) ... ... @@ -485,7 +485,7 @@ 485 485 486 486 487 487 488 -=== 2. 3.5Signal Strength ===458 +=== 2.4.4 Signal Strength === 489 489 490 490 ((( 491 491 NB-IoT Network signal Strength. ... ... @@ -517,24 +517,83 @@ 517 517 518 518 519 519 520 -=== 2. 3.6Temperature& Humidity===490 +=== 2.4.5 Distance === 521 521 522 - The devicewill beabletogetthe SHT31 temperatureand humiditydatanow and upload to IoT Server.492 +Get the distance. Flat object range 280mm - 7500mm. 523 523 524 -[[image:image-20220709161741-3.png]] 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 +))) 525 525 498 +((( 499 +((( 500 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 501 +))) 502 +))) 526 526 527 -Convert the read byte to decimal and divide it by ten. 504 +((( 505 + 506 +))) 528 528 508 +((( 509 + 510 +))) 529 529 530 - **Example:**512 +=== 2.4.6 Digital Interrupt === 531 531 532 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 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 +))) 533 533 534 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 518 +((( 519 +The command is: 520 +))) 535 535 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 +))) 536 536 537 537 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 + 538 538 == 2.5 Downlink Payload == 539 539 540 540 By default, NDDS75 prints the downlink payload to console port. ... ... @@ -587,12 +587,47 @@ 587 587 588 588 589 589 590 -== 2. 5BatteryAnalysis==619 +== 2.6 LED Indicator == 591 591 592 -=== 2.5.1 Battery Type === 593 593 622 +The NDDS75 has an internal LED which is to show the status of different state. 594 594 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 + 595 595 ((( 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 +== 2.8 Battery Analysis == 655 + 656 +=== 2.8.1 Battery Type === 657 + 658 + 659 +((( 596 596 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. 597 597 ))) 598 598
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.2 KB - Content