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
-
... ... @@ -54,6 +54,7 @@ 54 54 * 8500mAh Battery for long term use 55 55 56 56 57 + 57 57 == 1.3 Specification == 58 58 59 59 ... ... @@ -81,6 +81,7 @@ 81 81 * Max boost current: 2A, 1 second 82 82 83 83 85 + 84 84 == 1.4 Applications == 85 85 86 86 * Smart Buildings & Home Automation ... ... @@ -130,6 +130,7 @@ 130 130 131 131 132 132 135 + 133 133 = 2. Use N95S31B to communicate with IoT Server = 134 134 135 135 == 2.1 How it works == ... ... @@ -173,6 +173,7 @@ 173 173 * The local NB-IoT network used the band that N95S31B supports. 174 174 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 175 175 179 + 176 176 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 177 177 178 178 N95S31B supports different communication protocol such as : ... ... @@ -305,8 +305,8 @@ 305 305 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 306 306 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 307 307 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 308 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 309 -* (% 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 310 310 311 311 [[image:1657352634421-276.png]] 312 312 ... ... @@ -352,86 +352,58 @@ 352 352 353 353 == 2.3 Uplink Payload == 354 354 359 +In this mode, uplink payload includes in total 14 bytes 355 355 356 -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. 357 357 358 - 359 -For example: 360 - 361 - (% 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. 362 - 363 - 364 -The uplink payloads are composed in ASCII String. For example: 365 - 366 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 367 - 368 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 369 - 370 - 371 -(% style="color:red" %)**NOTE:** 372 - 373 -(% style="color:red" %) 374 -1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]]. 375 -1. By default, the device will send an uplink message every 1 hour. 376 - 377 - 378 - 379 - 380 -=== 2.3.1 Payload Analyze === 381 - 382 -N95S31B uplink payload includes in total 21 bytes 383 - 384 - 385 385 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 386 386 |=(% style="width: 60px;" %)((( 387 387 **Size(bytes)** 388 -)))|=(% 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** 389 -|(% 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" %)((( 390 -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"]] 391 391 392 - No function here.393 - )))|(%style="width:77px"%)(((394 - [[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 +))) 395 395 396 -By SHT31 397 -)))|(% style="width:80px" %)((( 398 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 399 399 400 -By SHT31 373 +[[image:1657331036973-987.png]] 374 + 375 +((( 376 +The payload is ASCII string, representative same HEX: 401 401 ))) 402 402 403 403 ((( 404 -((( 405 -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: 406 406 ))) 382 + 383 +* ((( 384 +Device ID: 0x724031556159 = 724031556159 407 407 ))) 386 +* ((( 387 +Version: 0x0064=100=1.0.0 388 +))) 408 408 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 409 409 410 -[[image:1657354294009-643.png]] 411 411 412 412 413 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 414 - 415 -* Device ID: 0x724031607457 = 724031607457 416 -* Version: 0x006e=110=1.1.0 417 - 418 -* BAT: 0x0ccd = 3277 mV = 3.277V 419 -* Signal: 0x1b = 27 420 -* Model: 0x01 = 1 421 -* 0x00dc000ccc= reserve, ignore in N95S31B 422 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 423 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 424 - 425 -((( 426 426 427 427 ))) 428 428 429 -((( 430 - 431 -))) 407 +== 2.4 Payload Explanation and Sensor Interface == 432 432 433 433 434 -=== 2. 3.2410 +=== 2.4.1 Device ID === 435 435 436 436 ((( 437 437 By default, the Device ID equal to the last 6 bytes of IMEI. ... ... @@ -455,25 +455,20 @@ 455 455 456 456 457 457 458 -=== 2. 3.3Version Info ===434 +=== 2.4.2 Version Info === 459 459 436 +((( 437 +Specify the software version: 0x64=100, means firmware version 1.00. 438 +))) 460 460 461 -These bytes include the hardware and software version. 462 - 463 -Higher byte: Specify hardware version: always 0x00 for N95S31B 464 - 465 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110 466 - 467 - 468 -For example: 0x00 6E: this device is N95S31B with firmware version 110. 469 - 470 470 ((( 471 - 441 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 472 472 ))) 473 473 474 474 475 -=== 2.3.4 Battery Info === 476 476 446 +=== 2.4.3 Battery Info === 447 + 477 477 ((( 478 478 Ex1: 0x0B45 = 2885mV 479 479 ))) ... ... @@ -484,7 +484,7 @@ 484 484 485 485 486 486 487 -=== 2. 3.5Signal Strength ===458 +=== 2.4.4 Signal Strength === 488 488 489 489 ((( 490 490 NB-IoT Network signal Strength. ... ... @@ -516,24 +516,83 @@ 516 516 517 517 518 518 519 -=== 2. 3.6Temperature& Humidity===490 +=== 2.4.5 Distance === 520 520 521 - The devicewill beabletogetthe SHT31 temperatureand humiditydatanow and upload to IoT Server.492 +Get the distance. Flat object range 280mm - 7500mm. 522 522 523 -[[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 +))) 524 524 498 +((( 499 +((( 500 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 501 +))) 502 +))) 525 525 526 -Convert the read byte to decimal and divide it by ten. 504 +((( 505 + 506 +))) 527 527 508 +((( 509 + 510 +))) 528 528 529 - **Example:**512 +=== 2.4.6 Digital Interrupt === 530 530 531 -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 +))) 532 532 533 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 518 +((( 519 +The command is: 520 +))) 534 534 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 +))) 535 535 536 536 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 + 537 537 == 2.5 Downlink Payload == 538 538 539 539 By default, NDDS75 prints the downlink payload to console port.
- 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