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)
Details
- Page properties
-
- Content
-
... ... @@ -69,6 +69,7 @@ 69 69 * 8500mAh Battery for long term use 70 70 71 71 72 + 72 72 == 1.3 Specification == 73 73 74 74 ... ... @@ -95,6 +95,7 @@ 95 95 * Max boost current: 2A, 1 second 96 96 97 97 99 + 98 98 == 1.4 Applications == 99 99 100 100 ... ... @@ -157,6 +157,7 @@ 157 157 1. Send an uplink packet 158 158 159 159 162 + 160 160 = 2. Use N95S31B to communicate with IoT Server = 161 161 162 162 ... ... @@ -544,55 +544,35 @@ 544 544 545 545 ==== 2.3.1.2 Since Firmware v1.2 ==== 546 546 547 - 548 548 In this mode, uplink payload includes 91 bytes in total by default. 549 549 550 550 Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded. 551 551 554 +|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4 555 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp ..... 552 552 553 -(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %) 554 -|(% style="width:95px" %)**Size(bytes)**|(% style="width:82px" %)**8**|(% style="width:43px" %)**2**|(% style="width:47px" %)**2**|(% style="width:124px" %)**1**|(% style="width:56px" %)**1**|(% style="width:109px" %)**2**|(% style="width:80px" %)**1**|(% style="width:51px" %)**2**|(% style="width:79px" %)**2**|(% style="width:84px" %)**2**|(% style="width:100px" %)**4**|(% style="width:76px" %)**2**|(% style="width:81px" %)**2**|(% style="width:121px" %)**4** 555 -|(% style="width:95px" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:47px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:56px" %)MOD|(% style="width:109px" %)TemDS18B20|(% style="width:80px" %)Interrupt|(% style="width:51px" %)ADC|(% style="width:79px" %)SHTTEM|(% style="width:84px" %)SHTHUM|(% style="width:100px" %)Time stamp |(% style="width:76px" %)SHTTEM|(% style="width:81px" %)SHTHUM|(% style="width:121px" %)Time stamp ..... 556 - 557 557 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 558 558 559 - 560 560 [[image:image-20220908154949-1.png]] 561 561 562 - 563 563 The payload is ASCII string, representative same HEX: 564 564 565 565 0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where: 566 566 567 -* (% style="color:red" %)Device ID: f868411056758782 = f868411056758782 568 - 569 -* (% style="color:blue" %)Version: 0x000c=120=1.2 570 - 571 -* (% style="color:green" %)BAT: 0x0d0f = 3343 mV = 3.343V 572 - 573 -* (% style="color:red" %)Singal: 0x0c = 12 574 - 575 -* (% style="color:blue" %)Mod: 0x01 = 1 576 - 565 +* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782 566 +* (% style="color:blue" %) Version: 0x000c=120=1.2 567 +* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V 568 +* (% style="color:red" %) Singal: 0x0c = 12 569 +* (% style="color:blue" %) Mod: 0x01 = 1 577 577 * TemDS18B20: 0x0000= 0 = 0 578 - 579 579 * (% style="color:green" %)Interrupt: 0x00= 0 580 - 581 581 * (% style="color:green" %)adc: 0x0030= 48 582 - 583 583 * SHTTEM: 0x0114= 276 = 27.6 584 - 585 585 * SHTHUM:0x0231 =561=56.1% 586 - 587 -* (% style="color:red" %)Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 588 - 575 +* (% style="color:red" %) Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 589 589 * (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12 590 - 591 591 * 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,....... 592 592 593 - 594 - 595 - 596 596 === 2.3.2 Device ID === 597 597 598 598 ... ... @@ -602,12 +602,10 @@ 602 602 603 603 ((( 604 604 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 605 - 606 - 607 607 ))) 608 608 609 609 ((( 610 -** (% style="color:blue" %)Example:**591 +**Example:** 611 611 ))) 612 612 613 613 ((( ... ... @@ -615,25 +615,23 @@ 615 615 ))) 616 616 617 617 ((( 618 -The Device ID is stored in a none-erase area, Upgrade the firmware or run ** (% style="color:blue" %)AT+FDR**(%%)won't erase Device ID.599 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 619 619 620 620 621 621 ))) 622 622 623 -(% style="color:red" %)**NOTE: 604 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:** 624 624 625 625 626 626 By default, the Device ID equal to the last 15 bits of IMEI. 627 627 628 -User can use ** (% style="color:blue" %)AT+DEUI**(%%)to set Device ID609 +User can use **AT+DEUI** to set Device ID 629 629 611 +**Example:** 630 630 631 -** (% style="color:blue" %)Example:** 632 - 633 633 AT+DEUI=868411056754138 634 634 635 635 636 - 637 637 === 2.3.3 Version Info === 638 638 639 639