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, 7 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 : ... ... @@ -291,16 +291,15 @@ 291 291 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 292 292 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 293 293 294 -[[image:16573 52391268-297.png]]296 +[[image:1657330501006-241.png]] 295 295 296 296 297 -[[image:16573 52403317-397.png]]299 +[[image:1657330533775-472.png]] 298 298 299 299 300 300 301 -=== 2.2. 7Use MQTT protocol to uplink data ===303 +=== 2.2.6 Use MQTT protocol to uplink data === 302 302 303 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 304 304 305 305 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 306 306 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -307,40 +307,35 @@ 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= f9527311 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)311 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 312 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 312 312 313 -[[image:1657 352634421-276.png]]314 +[[image:1657249978444-674.png]] 314 314 315 315 316 -[[image:16573 52645687-385.png]]317 +[[image:1657330723006-866.png]] 317 317 318 -((( 319 -To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period. 320 -))) 321 321 322 - 323 323 ((( 324 -MQTT protocol has a much high -power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.321 +MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 325 325 ))) 326 326 327 327 328 328 329 -=== 2.2. 8Use TCP protocol to uplink data ===326 +=== 2.2.7 Use TCP protocol to uplink data === 330 330 331 -This feature is supported since firmware version v110 332 332 333 333 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 334 334 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 335 335 336 -[[image: 1657352898400-901.png]]332 +[[image:image-20220709093918-1.png]] 337 337 338 338 339 -[[image: 1657352914475-252.png]]335 +[[image:image-20220709093918-2.png]] 340 340 341 341 342 342 343 -=== 2.2. 9Change Update Interval ===339 +=== 2.2.8 Change Update Interval === 344 344 345 345 User can use below command to change the (% style="color:green" %)**uplink interval**. 346 346 ... ... @@ -347,92 +347,69 @@ 347 347 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 348 348 349 349 ((( 350 - 346 +(% style="color:red" %)**NOTE:** 351 351 ))) 352 352 349 +((( 350 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 351 +))) 353 353 354 354 354 + 355 355 == 2.3 Uplink Payload == 356 356 357 +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 363 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 364 +|(% 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"]]366 +((( 367 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 368 +))) 396 396 397 -By SHT31 398 -)))|(% style="width:80px" %)((( 399 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 400 400 401 -By SHT31 371 +[[image:1657331036973-987.png]] 372 + 373 +((( 374 +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. 378 +0x72403155615900640c6c19029200 where: 407 407 ))) 380 + 381 +* ((( 382 +Device ID: 0x724031556159 = 724031556159 408 408 ))) 384 +* ((( 385 +Version: 0x0064=100=1.0.0 386 +))) 409 409 388 +* ((( 389 +BAT: 0x0c6c = 3180 mV = 3.180V 390 +))) 391 +* ((( 392 +Signal: 0x19 = 25 393 +))) 394 +* ((( 395 +Distance: 0x0292= 658 mm 396 +))) 397 +* ((( 398 +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 -))) 405 +== 2.4 Payload Explanation and Sensor Interface == 433 433 434 434 435 -=== 2. 3.2408 +=== 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 ===432 +=== 2.4.2 Version Info === 460 460 434 +((( 435 +Specify the software version: 0x64=100, means firmware version 1.00. 436 +))) 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 - 439 +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 444 +=== 2.4.3 Battery Info === 445 + 478 478 ((( 479 479 Ex1: 0x0B45 = 2885mV 480 480 ))) ... ... @@ -485,7 +485,7 @@ 485 485 486 486 487 487 488 -=== 2. 3.5Signal Strength ===456 +=== 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===488 +=== 2.4.5 Distance === 521 521 522 - The devicewill beabletogetthe SHT31 temperatureand humiditydatanow and upload to IoT Server.490 +Get the distance. Flat object range 280mm - 7500mm. 523 523 524 -[[image:image-20220709161741-3.png]] 492 +((( 493 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 494 +))) 525 525 496 +((( 497 +((( 498 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 499 +))) 500 +))) 526 526 527 -Convert the read byte to decimal and divide it by ten. 502 +((( 503 + 504 +))) 528 528 506 +((( 507 + 508 +))) 529 529 530 - **Example:**510 +=== 2.4.6 Digital Interrupt === 531 531 532 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 512 +((( 513 +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. 514 +))) 533 533 534 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 516 +((( 517 +The command is: 518 +))) 535 535 520 +((( 521 +(% 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]])**.** 522 +))) 536 536 537 537 525 +((( 526 +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. 527 +))) 528 + 529 + 530 +((( 531 +Example: 532 +))) 533 + 534 +((( 535 +0x(00): Normal uplink packet. 536 +))) 537 + 538 +((( 539 +0x(01): Interrupt Uplink Packet. 540 +))) 541 + 542 + 543 + 544 +=== 2.4.7 +5V Output === 545 + 546 +((( 547 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 548 +))) 549 + 550 + 551 +((( 552 +The 5V output time can be controlled by AT Command. 553 +))) 554 + 555 +((( 556 +(% style="color:blue" %)**AT+5VT=1000** 557 +))) 558 + 559 +((( 560 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 561 +))) 562 + 563 + 564 + 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==617 +== 2.6 LED Indicator == 591 591 592 -=== 2.5.1 Battery Type === 593 593 620 +The NDDS75 has an internal LED which is to show the status of different state. 594 594 622 + 623 +* 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) 624 +* Then the LED will be on for 1 second means device is boot normally. 625 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 626 +* For each uplink probe, LED will be on for 500ms. 627 + 595 595 ((( 629 + 630 +))) 631 + 632 + 633 + 634 +== 2.7 Firmware Change Log == 635 + 636 + 637 +((( 638 +Download URL & Firmware Change log 639 +))) 640 + 641 +((( 642 +[[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/]] 643 +))) 644 + 645 + 646 +((( 647 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 648 +))) 649 + 650 + 651 + 652 +== 2.8 Battery Analysis == 653 + 654 +=== 2.8.1 Battery Type === 655 + 656 + 657 +((( 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
- 1657352403317-397.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -547.7 KB - Content
- 1657352634421-276.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -163.6 KB - Content
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -144.8 KB - Content
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -157.0 KB - Content
- 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