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,7 +69,6 @@ 69 69 * 8500mAh Battery for long term use 70 70 71 71 72 - 73 73 == 1.3 Specification == 74 74 75 75 ... ... @@ -96,7 +96,6 @@ 96 96 * Max boost current: 2A, 1 second 97 97 98 98 99 - 100 100 == 1.4 Applications == 101 101 102 102 ... ... @@ -159,7 +159,6 @@ 159 159 1. Send an uplink packet 160 160 161 161 162 - 163 163 = 2. Use N95S31B to communicate with IoT Server = 164 164 165 165 ... ... @@ -547,35 +547,55 @@ 547 547 548 548 ==== 2.3.1.2 Since Firmware v1.2 ==== 549 549 547 + 550 550 In this mode, uplink payload includes 91 bytes in total by default. 551 551 552 552 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. 553 553 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 ..... 556 556 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 + 559 559 [[image:image-20220908154949-1.png]] 560 560 562 + 561 561 The payload is ASCII string, representative same HEX: 562 562 563 563 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: 564 564 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 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 + 570 570 * TemDS18B20: 0x0000= 0 = 0 578 + 571 571 * (% style="color:green" %)Interrupt: 0x00= 0 580 + 572 572 * (% style="color:green" %)adc: 0x0030= 48 582 + 573 573 * SHTTEM: 0x0114= 276 = 27.6 584 + 574 574 * SHTHUM:0x0231 =561=56.1% 575 -* (% style="color:red" %) Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 586 + 587 +* (% style="color:red" %)Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 588 + 576 576 * (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12 590 + 577 577 * 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,....... 578 578 593 + 594 + 595 + 579 579 === 2.3.2 Device ID === 580 580 581 581 ... ... @@ -585,10 +585,12 @@ 585 585 586 586 ((( 587 587 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 605 + 606 + 588 588 ))) 589 589 590 590 ((( 591 -**Example:** 610 +** (% style="color:blue" %)Example:** 592 592 ))) 593 593 594 594 ((( ... ... @@ -596,23 +596,25 @@ 596 596 ))) 597 597 598 598 ((( 599 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 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. 600 600 601 601 602 602 ))) 603 603 604 -(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:** 623 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 605 605 606 606 607 607 By default, the Device ID equal to the last 15 bits of IMEI. 608 608 609 -User can use **AT+DEUI** to set Device ID 628 +User can use ** (% style="color:blue" %)AT+DEUI**(%%) to set Device ID 610 610 611 -**Example:** 612 612 631 +** (% style="color:blue" %)Example:** 632 + 613 613 AT+DEUI=868411056754138 614 614 615 615 636 + 616 616 === 2.3.3 Version Info === 617 617 618 618