Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Bei1 +XWiki.David - Content
-
... ... @@ -17,6 +17,7 @@ 17 17 18 18 = 1. Introduction = 19 19 20 + 20 20 == 1.1 What is N95S31B NB-IoT Sensor Node == 21 21 22 22 ((( ... ... @@ -67,7 +67,6 @@ 67 67 * Micro SIM card slot for NB-IoT SIM 68 68 * 8500mAh Battery for long term use 69 69 70 - 71 71 == 1.3 Specification == 72 72 73 73 ... ... @@ -78,12 +78,12 @@ 78 78 79 79 (% style="color:#037691" %)**NB-IoT Spec:** 80 80 81 -* B1 @H-FDD: 2100MHz 82 -* B3 @H-FDD: 1800MHz 83 -* B8 @H-FDD: 900MHz 84 -* B5 @H-FDD: 850MHz 85 -* B20 @H-FDD: 800MHz 86 -* B28 @H-FDD: 700MHz 81 +* - B1 @H-FDD: 2100MHz 82 +* - B3 @H-FDD: 1800MHz 83 +* - B8 @H-FDD: 900MHz 84 +* - B5 @H-FDD: 850MHz 85 +* - B20 @H-FDD: 800MHz 86 +* - B28 @H-FDD: 700MHz 87 87 88 88 (% style="color:#037691" %)**Battery:** 89 89 ... ... @@ -93,7 +93,6 @@ 93 93 * Max continuously current: 130mA 94 94 * Max boost current: 2A, 1 second 95 95 96 - 97 97 == 1.4 Applications == 98 98 99 99 ... ... @@ -108,6 +108,7 @@ 108 108 109 109 110 110 110 + 111 111 == 1.5 Pin Definitions & Switch == 112 112 113 113 ... ... @@ -117,6 +117,7 @@ 117 117 [[image:image-20220709144723-1.png]] 118 118 119 119 120 + 120 120 === 1.5.1 Jumper JP2 === 121 121 122 122 ... ... @@ -123,18 +123,20 @@ 123 123 Power on Device when put this jumper. 124 124 125 125 127 + 126 126 === 1.5.2 BOOT MODE / SW1 === 127 127 128 128 129 129 ((( 130 - **1) ISP:**upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.132 +1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. 131 131 ))) 132 132 133 133 ((( 134 - **2) Flash:**work mode, device starts to work and send out console output for further debug136 +2) Flash: work mode, device starts to work and send out console output for further debug 135 135 ))) 136 136 137 137 140 + 138 138 === 1.5.3 Reset Button === 139 139 140 140 ... ... @@ -141,18 +141,18 @@ 141 141 Press to reboot the device. 142 142 143 143 147 + 144 144 === 1.5.4 LED === 145 145 146 146 147 147 It will flash: 148 148 149 -1. When boot the device in flash mode 153 +1. When boot the device in flash mode 154 +1. Send an uplink packet 150 150 151 -2. Send an uplink packet 152 - 153 - 154 154 = 2. Use N95S31B to communicate with IoT Server = 155 155 158 + 156 156 == 2.1 How it works == 157 157 158 158 ... ... @@ -178,6 +178,7 @@ 178 178 179 179 == 2.2 Configure the N95S31B == 180 180 184 + 181 181 === 2.2.1 Power On N95S31B === 182 182 183 183 ... ... @@ -184,9 +184,10 @@ 184 184 [[image:image-20220709150546-2.png]] 185 185 186 186 187 -=== 2.2.2 Test Requirement === 188 188 192 +=== 2.2.1 Test Requirement === 189 189 194 + 190 190 ((( 191 191 To use N95S31B in your city, make sure meet below requirements: 192 192 ))) ... ... @@ -233,6 +233,7 @@ 233 233 [[image:1657350625843-586.png]] 234 234 235 235 241 + 236 236 === 2.2.3 Insert SIM card === 237 237 238 238 ... ... @@ -248,6 +248,7 @@ 248 248 [[image:1657351240556-536.png]] 249 249 250 250 257 + 251 251 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 252 252 253 253 ... ... @@ -262,13 +262,13 @@ 262 262 [[image:1657351312545-300.png]] 263 263 264 264 265 - (% style="color:blue" %)**Connection:**272 +**Connection:** 266 266 267 - (% style="background-color:yellow" %) **USB TTL GND <~-~-~-~-> GND**274 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 268 268 269 - **~(% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**276 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 270 270 271 - **~(% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**278 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 272 272 273 273 274 274 In the PC, use below serial tool settings: ... ... @@ -291,6 +291,7 @@ 291 291 ))) 292 292 293 293 301 + 294 294 === 2.2.5 Use CoAP protocol to uplink data === 295 295 296 296 ... ... @@ -305,10 +305,10 @@ 305 305 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 306 306 ))) 307 307 * ((( 308 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** 316 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 309 309 ))) 310 310 * ((( 311 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ 319 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 312 312 ))) 313 313 314 314 ((( ... ... @@ -327,6 +327,7 @@ 327 327 [[image:1657352185396-303.png]] 328 328 329 329 338 + 330 330 === 2.2.6 Use UDP protocol to uplink data(Default protocol) === 331 331 332 332 ... ... @@ -340,18 +340,19 @@ 340 340 [[image:1657352403317-397.png]] 341 341 342 342 352 + 343 343 === 2.2.7 Use MQTT protocol to uplink data === 344 344 345 345 346 346 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 347 347 348 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ 349 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ 350 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ 351 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ 352 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ 353 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/ 354 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/ 358 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 359 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 360 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 361 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 362 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 363 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 364 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 355 355 356 356 [[image:1657352634421-276.png]] 357 357 ... ... @@ -369,6 +369,7 @@ 369 369 ))) 370 370 371 371 382 + 372 372 === 2.2.8 Use TCP protocol to uplink data === 373 373 374 374 ... ... @@ -383,6 +383,7 @@ 383 383 [[image:1657352914475-252.png]] 384 384 385 385 397 + 386 386 === 2.2.9 Change Update Interval === 387 387 388 388 ... ... @@ -394,13 +394,9 @@ 394 394 395 395 ))) 396 396 397 -((( 398 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 399 -))) 409 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:** 400 400 401 -((( 402 -(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).** 403 -))) 411 +**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).** 404 404 405 405 406 406 == 2.3 Uplink Payload == ... ... @@ -407,7 +407,7 @@ 407 407 408 408 409 409 ((( 410 -N95S31B has different working mode sfor the connections of different typesof sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.418 +N95S31B 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. 411 411 ))) 412 412 413 413 ... ... @@ -445,20 +445,21 @@ 445 445 **By default, the device will send an uplink message every 1 hour.** 446 446 447 447 456 + 448 448 449 449 ))) 450 450 451 451 === 2.3.1 Payload Analyze === 452 452 453 -==== 2.3.1.1 Before Firmware v1.2 ==== 454 454 455 - 456 456 N95S31B uplink payload includes in total 21 bytes 457 457 458 458 459 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 460 -|=(% style="width: 50px;" %)**Size(bytes)**|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 65px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**2** 461 -|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:162px" %)((( 466 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 467 +|=(% style="width: 60px;" %)((( 468 +**Size(bytes)** 469 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2** 470 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)((( 462 462 ((( 463 463 Reserve/ Same as NBSN95 CFGMOD=1 464 464 ))) ... ... @@ -466,7 +466,7 @@ 466 466 ((( 467 467 No function here. 468 468 ))) 469 -)))|(% style="width: 102px" %)(((478 +)))|(% style="width:77px" %)((( 470 470 ((( 471 471 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 472 472 ))) ... ... @@ -474,7 +474,7 @@ 474 474 ((( 475 475 By SHT31 476 476 ))) 477 -)))|(% style="width:8 1px" %)(((486 +)))|(% style="width:80px" %)((( 478 478 ((( 479 479 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 480 480 ))) ... ... @@ -496,85 +496,55 @@ 496 496 [[image:1657354294009-643.png]] 497 497 498 498 499 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457**508 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 500 500 501 -**where:** 510 +* Device ID: 0x724031607457 = 724031607457 511 +* Version: 0x006e=110=1.1.0 502 502 503 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 513 +* BAT: 0x0ccd = 3277 mV = 3.277V 514 +* Signal: 0x1b = 27 515 +* Model: 0x01 = 1 516 +* 0x00dc000ccc= reserve, ignore in N95S31B 517 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 518 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 504 504 505 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 506 - 507 -* (% style="color:#037691" %)**BAT:** (%%) 0x0ccd = 3277 mV = 3.277V 508 - 509 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 510 - 511 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 512 - 513 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 514 - 515 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 516 - 517 -* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 518 - 519 519 ((( 520 520 522 +))) 521 521 522 - 524 +((( 525 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:** 523 523 ))) 524 524 525 -==== 2.3.1.2 Since Firmware v1.2 ==== 526 - 527 - 528 528 In this mode, uplink payload includes 91 bytes in total by default. 529 529 530 530 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. 531 531 532 +|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4 533 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp ..... 532 532 533 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 534 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:30px" %)**1**|(% style="width:20px" %)**1**|(% style="width:55px" %)**2**|(% style="width:35px" %)**1**|(% style="width:20px" %)**2**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:30px" %)**4**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:35px" %)**4** 535 -|=(% 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 ..... 536 - 537 537 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 538 538 539 - 540 540 [[image:image-20220908154949-1.png]] 541 541 542 - 543 543 The payload is ASCII string, representative same HEX: 544 544 545 - **0x__f868411056758782__(% style="color:blue" %)__000c__(% style="color:green" %)__0d0f__(% style="color:#00b0f0" %)__0c__(% style="color:#7030a0" %)__01__(% style="color:#d60093" %)__0000__(% style="color:#a14d07" %)__00__ __0030__(% style="color:#0020b0" %)__0114__(% style="color:#420042" %)__0231__(% style="color:#663300" %)__63199d3c__ (%%)__0113023163199d12__ __0113023163199c5e__////__0112023763199baa__ __0112023263199af6__////__0111023b631999a7__**541 +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: 546 546 547 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 543 +* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782 544 +* (% style="color:blue" %) Version: 0x000c=120=1.2 545 +* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V 546 +* (% style="color:red" %) Singal: 0x0c = 12 547 +* (% style="color:blue" %) Mod: 0x01 = 1 548 +* TemDS18B20: 0x0000= 0 = 0 549 +* (% style="color:green" %)Interrupt: 0x00= 0 550 +* (% style="color:green" %)adc: 0x0030= 48 551 +* SHTTEM: 0x0114= 276 = 27.6 552 +* SHTHUM:0x0231 =561=56.1% 553 +* (% style="color:red" %) Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 554 +* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12 555 +* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,....... 548 548 549 -**where:** 550 - 551 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 552 - 553 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 554 - 555 -* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 556 - 557 -* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 558 - 559 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 560 - 561 -* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 562 - 563 -* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 564 - 565 -* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 566 - 567 -* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 568 - 569 -* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 570 - 571 -* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 572 - 573 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 574 - 575 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 576 - 577 - 578 578 === 2.3.2 Device ID === 579 579 580 580 ... ... @@ -584,12 +584,10 @@ 584 584 585 585 ((( 586 586 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 587 - 588 - 589 589 ))) 590 590 591 591 ((( 592 - (% style="color:blue" %)**Example:**569 +**Example:** 593 593 ))) 594 594 595 595 ((( ... ... @@ -597,21 +597,20 @@ 597 597 ))) 598 598 599 599 ((( 600 -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.577 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 601 601 602 602 603 603 ))) 604 604 605 -(% style="color:red" %)**NOTE: 582 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:** 606 606 607 607 608 608 By default, the Device ID equal to the last 15 bits of IMEI. 609 609 610 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID587 +User can use **AT+DEUI** to set Device ID 611 611 589 +**Example:** 612 612 613 -(% style="color:blue" %)**Example:** 614 - 615 615 AT+DEUI=868411056754138 616 616 617 617 ... ... @@ -642,6 +642,7 @@ 642 642 643 643 ))) 644 644 621 + 645 645 === 2.3.4 Battery Info === 646 646 647 647 ... ... @@ -654,6 +654,7 @@ 654 654 ))) 655 655 656 656 634 + 657 657 === 2.3.5 Signal Strength === 658 658 659 659 ... ... @@ -686,6 +686,7 @@ 686 686 ))) 687 687 688 688 667 + 689 689 === 2.3.6 Temperature & Humidity === 690 690 691 691 ... ... @@ -704,6 +704,7 @@ 704 704 Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 705 705 706 706 686 + 707 707 == 2.4 Downlink Payload == 708 708 709 709 ... ... @@ -756,15 +756,12 @@ 756 756 ))) 757 757 758 758 759 -== 2.5 739 +== 2.5 Humidity and Temperature alarm function == 760 760 741 +➢ AT Command: 761 761 762 - **~ (% style="color:blue" %)➢ATCommand:(%%)**743 +AT+ SHHUM=min,max 763 763 764 - 765 -(% style="color:#037691" %)**AT+ SHHUM=min,max** 766 - 767 - 768 768 ² When min=0, and max≠0, Alarm higher than max 769 769 770 770 ² When min≠0, and max=0, Alarm lower than min ... ... @@ -771,13 +771,12 @@ 771 771 772 772 ² When min≠0 and max≠0, Alarm higher than max or lower than min 773 773 751 +Example: 774 774 775 - (% style="color:blue" %)**Example:** 776 - 777 777 AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 778 778 779 779 780 - (% style="color:#037691" %)**AT+ SHTEMP=min,max**756 +AT+ SHTEMP=min,max 781 781 782 782 ² When min=0, and max≠0, Alarm higher than max 783 783 ... ... @@ -785,44 +785,91 @@ 785 785 786 786 ² When min≠0 and max≠0, Alarm higher than max or lower than min 787 787 764 +Example: 788 788 789 -**~ (% style="color:blue" %)Example:(%%)** 790 - 791 791 AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 792 792 793 - 794 794 == 2.6 Set the number of data to be uploaded and the recording time == 795 795 770 +➢ AT Command: 796 796 797 - **~(%style="color:blue"%)➢ATCommand:(%%)**772 +AT+TR=900 ~/~/The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds) 798 798 799 -* (% style="color:#037691" %)**AT+TR=900** (%%)~/~/ The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds) 800 -* (% style="color:#037691" %)**AT+NOUD=8** (%%)~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 774 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 801 801 802 - Thediagrambelowexplainstherelationship between TR, NOUD,andTDC more clearly**:**776 +== 2.7 Read or Clear cached data == 803 803 804 - [[image:image-20221009001045-1.png||height="726" width="1009"]]778 +➢ AT Command: 805 805 780 +AT+CDP ~/~/ Read cached data 806 806 807 - == 2.7 Read or Clear cached data ==782 +[[image:image-20220908163102-2.png]] 808 808 784 +AT+CDP=0 ~/~/ Clear cached data 809 809 810 - **~(%style="color:blue"%)➢AT Command:(%%)**786 +== 2.8 Battery Analysis == 811 811 812 -* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 813 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 814 814 815 - [[image:image-20220908163102-2.png]]789 +=== 2.8.1 Battery Type === 816 816 817 817 818 -== 2.8 Battery & Power Consumption == 792 +((( 793 +The N95S31B 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. 794 +))) 819 819 796 +((( 797 +The battery is designed to last for several years depends on the actually use environment and update interval. 798 +))) 820 820 821 -N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 800 +((( 801 +The battery related documents as below: 802 +))) 822 822 823 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 804 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 805 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 806 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 824 824 808 +((( 809 +[[image:image-20220709101450-2.png]] 810 +))) 825 825 812 + 813 + 814 +=== 2.8.2 Power consumption Analyze === 815 + 816 + 817 +((( 818 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project. 819 +))) 820 + 821 +((( 822 + 823 +))) 824 + 825 + 826 +=== 2.8.3 Battery Note === 827 + 828 + 829 +((( 830 +The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to uplink data, then the battery life may be decreased. 831 +))) 832 + 833 + 834 + 835 +=== 2.8.4 Replace the battery === 836 + 837 + 838 +((( 839 +You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board. 840 +))) 841 + 842 + 843 +((( 844 +The default battery pack of N95S31B includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes). 845 +))) 846 + 847 + 848 + 826 826 = 3. Access NB-IoT Module = 827 827 828 828 ... ... @@ -839,8 +839,10 @@ 839 839 [[image:1657333200519-600.png]] 840 840 841 841 865 + 842 842 = 4. Using the AT Commands = 843 843 868 + 844 844 == 4.1 Access AT Commands == 845 845 846 846 ... ... @@ -934,8 +934,10 @@ 934 934 AT+PWORD : Serial Access Password 935 935 936 936 962 + 937 937 = 5. FAQ = 938 938 965 + 939 939 == 5.1 How to Upgrade Firmware == 940 940 941 941 ... ... @@ -948,7 +948,7 @@ 948 948 ))) 949 949 950 950 ((( 951 - firmware:[[Dropbox- Firmware - 简化您的生活>>url:https://www.dropbox.com/sh/ap9k142hfnlh5w6/AACJeN_St0ryUl3AggrNB5x0a/N95S31B/Firmware?dl=0&subfolder_nav_tracking=1]]978 + 952 952 953 953 ((( 954 954 (% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** ... ... @@ -956,8 +956,10 @@ 956 956 ))) 957 957 958 958 986 + 959 959 = 6. Trouble Shooting = 960 960 989 + 961 961 == 6.1 Connection problem when uploading firmware == 962 962 963 963 ... ... @@ -970,6 +970,7 @@ 970 970 971 971 ))) 972 972 1002 + 973 973 == 6.2 AT Command input doesn't work == 974 974 975 975 ... ... @@ -979,6 +979,7 @@ 979 979 980 980 ))) 981 981 1012 + 982 982 = 7. Order Info = 983 983 984 984 ... ... @@ -985,6 +985,11 @@ 985 985 Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 986 986 987 987 1019 +(% class="wikigeneratedid" %) 1020 +((( 1021 + 1022 +))) 1023 + 988 988 = 8. Packing Info = 989 989 990 990 ((( ... ... @@ -1010,6 +1010,7 @@ 1010 1010 ((( 1011 1011 1012 1012 1049 + 1013 1013 1014 1014 ))) 1015 1015 ... ... @@ -1019,4 +1019,3 @@ 1019 1019 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 1020 1020 * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]] 1021 1021 1022 -
- image-20221009001045-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content