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, 3 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Edwin - 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 ((( ... ... @@ -55,6 +55,7 @@ 55 55 56 56 == 1.2 Features == 57 57 59 + 58 58 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 59 59 * Monitor Temperature & Humidity via SHT31 60 60 * AT Commands to change parameters ... ... @@ -66,8 +66,6 @@ 66 66 * Micro SIM card slot for NB-IoT SIM 67 67 * 8500mAh Battery for long term use 68 68 69 - 70 - 71 71 == 1.3 Specification == 72 72 73 73 ... ... @@ -93,10 +93,9 @@ 93 93 * Max continuously current: 130mA 94 94 * Max boost current: 2A, 1 second 95 95 96 - 97 - 98 98 == 1.4 Applications == 99 99 98 + 100 100 * Smart Buildings & Home Automation 101 101 * Logistics and Supply Chain Management 102 102 * Smart Metering ... ... @@ -108,15 +108,21 @@ 108 108 109 109 110 110 111 -== 1.5 Pin Definitions == 112 112 111 + 112 +== 1.5 Pin Definitions & Switch == 113 + 114 + 113 113 N95S31B use the mother board from NBSN95 which as below. 114 114 117 + 115 115 [[image:image-20220709144723-1.png]] 116 116 117 117 121 + 118 118 === 1.5.1 Jumper JP2 === 119 119 124 + 120 120 Power on Device when put this jumper. 121 121 122 122 ... ... @@ -123,6 +123,7 @@ 123 123 124 124 === 1.5.2 BOOT MODE / SW1 === 125 125 131 + 126 126 ((( 127 127 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. 128 128 ))) ... ... @@ -135,6 +135,7 @@ 135 135 136 136 === 1.5.3 Reset Button === 137 137 144 + 138 138 Press to reboot the device. 139 139 140 140 ... ... @@ -141,15 +141,15 @@ 141 141 142 142 === 1.5.4 LED === 143 143 151 + 144 144 It will flash: 145 145 146 146 1. When boot the device in flash mode 147 147 1. Send an uplink packet 148 148 149 - 150 - 151 151 = 2. Use N95S31B to communicate with IoT Server = 152 152 159 + 153 153 == 2.1 How it works == 154 154 155 155 ... ... @@ -166,7 +166,7 @@ 166 166 167 167 ))) 168 168 169 -[[image:1657 350248151-650.png]]176 +[[image:1657520100595-569.png]] 170 170 171 171 ((( 172 172 ... ... @@ -182,6 +182,7 @@ 182 182 [[image:image-20220709150546-2.png]] 183 183 184 184 192 + 185 185 === 2.2.1 Test Requirement === 186 186 187 187 ... ... @@ -234,6 +234,7 @@ 234 234 235 235 === 2.2.3 Insert SIM card === 236 236 245 + 237 237 ((( 238 238 Insert the NB-IoT Card get from your provider. 239 239 ))) ... ... @@ -249,14 +249,18 @@ 249 249 250 250 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 251 251 261 + 252 252 ((( 253 253 ((( 254 254 User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below. 265 + 266 + 255 255 ))) 256 256 ))) 257 257 258 258 [[image:1657351312545-300.png]] 259 259 272 + 260 260 **Connection:** 261 261 262 262 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -280,8 +280,9 @@ 280 280 281 281 [[image:1657329814315-101.png]] 282 282 296 + 283 283 ((( 284 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]298 +(% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]** 285 285 ))) 286 286 287 287 ... ... @@ -288,9 +288,10 @@ 288 288 289 289 === 2.2.5 Use CoAP protocol to uplink data === 290 290 291 -(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 292 292 306 +(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]** 293 293 308 + 294 294 ((( 295 295 **Use below commands:** 296 296 ))) ... ... @@ -338,6 +338,7 @@ 338 338 339 339 === 2.2.7 Use MQTT protocol to uplink data === 340 340 356 + 341 341 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 342 342 343 343 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink ... ... @@ -353,6 +353,7 @@ 353 353 354 354 [[image:1657352645687-385.png]] 355 355 372 + 356 356 ((( 357 357 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. 358 358 ))) ... ... @@ -366,6 +366,7 @@ 366 366 367 367 === 2.2.8 Use TCP protocol to uplink data === 368 368 386 + 369 369 This feature is supported since firmware version v110 370 370 371 371 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -380,6 +380,7 @@ 380 380 381 381 === 2.2.9 Change Update Interval === 382 382 401 + 383 383 User can use below command to change the (% style="color:green" %)**uplink interval**. 384 384 385 385 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -388,13 +388,21 @@ 388 388 389 389 ))) 390 390 410 +((( 411 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 412 +))) 391 391 414 +((( 415 +(% 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).** 416 +))) 392 392 418 + 419 + 393 393 == 2.3 Uplink Payload == 394 394 395 395 396 396 ((( 397 -N BSN95424 +N95S31B has different working modes for the connections of different types 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. 398 398 ))) 399 399 400 400 ... ... @@ -403,7 +403,7 @@ 403 403 ))) 404 404 405 405 ((( 406 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the BSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.433 + (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 407 407 ))) 408 408 409 409 ... ... @@ -426,24 +426,30 @@ 426 426 427 427 (% style="color:red" %) 428 428 1. ((( 429 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 456 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 430 430 ))) 431 431 1. ((( 432 -By default, the device will send an uplink message every 1 hour. 433 -))) 459 +**By default, the device will send an uplink message every 1 hour.** 434 434 435 435 436 436 463 + 464 +))) 465 + 437 437 === 2.3.1 Payload Analyze === 438 438 468 + 469 +==== 2.3.1.1 Before Firmware v1.2 ==== 470 + 471 + 439 439 N95S31B uplink payload includes in total 21 bytes 440 440 441 441 442 -(% border=" 1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)475 +(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:760px" %) 443 443 |=(% style="width: 60px;" %)((( 444 444 **Size(bytes)** 445 -)))|=(% style="width: 5 0px;" %)**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**446 -|(% 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" %)(((478 +)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 174px;" %)5|=(% style="width: 106px;" %)**2**|=(% style="width: 85px;" %)**2** 479 +|(% 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:174px" %)((( 447 447 ((( 448 448 Reserve/ Same as NBSN95 CFGMOD=1 449 449 ))) ... ... @@ -451,7 +451,7 @@ 451 451 ((( 452 452 No function here. 453 453 ))) 454 -)))|(% style="width: 77px" %)(((487 +)))|(% style="width:106px" %)((( 455 455 ((( 456 456 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 457 457 ))) ... ... @@ -459,7 +459,7 @@ 459 459 ((( 460 460 By SHT31 461 461 ))) 462 -)))|(% style="width:8 0px" %)(((495 +)))|(% style="width:85px" %)((( 463 463 ((( 464 464 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 465 465 ))) ... ... @@ -470,6 +470,8 @@ 470 470 ))) 471 471 472 472 ((( 506 + 507 + 473 473 ((( 474 474 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 475 475 ))) ... ... @@ -481,27 +481,80 @@ 481 481 482 482 The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 483 483 484 -* Device ID: 0x724031607457 = 724031607457 485 -* Version: 0x006e=110=1.1.0 519 +* Device ID: 0x724031607457 = 724031607457 486 486 487 -* BAT: 0x0ccd = 3277 mV = 3.277V 488 -* Signal: 0x1b = 27 489 -* Model: 0x01 = 1 521 +* Version: 0x006e=110=1.1.0 522 + 523 +* BAT: 0x0ccd = 3277 mV = 3.277V 524 + 525 +* Signal: 0x1b = 27 526 + 527 +* Model: 0x01 = 1 528 + 490 490 * 0x00dc000ccc= reserve, ignore in N95S31B 491 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 492 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 493 493 531 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 532 + 533 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 534 + 494 494 ((( 495 495 496 -))) 497 497 498 - (((538 + 499 499 500 500 ))) 501 501 542 +==== 2.3.1.2 Since Firmware v1.2 ==== 502 502 544 + 545 +In this mode, uplink payload includes 91 bytes in total by default. 546 + 547 +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. 548 + 549 + 550 +(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %) 551 +|(% 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** 552 +|(% 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 ..... 553 + 554 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 555 + 556 + 557 +[[image:image-20220908154949-1.png]] 558 + 559 + 560 +The payload is ASCII string, representative same HEX: 561 + 562 +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: 563 + 564 +* (% style="color:red" %)Device ID: f868411056758782 = f868411056758782 565 + 566 +* (% style="color:blue" %)Version: 0x000c=120=1.2 567 + 568 +* (% style="color:green" %)BAT: 0x0d0f = 3343 mV = 3.343V 569 + 570 +* (% style="color:red" %)Singal: 0x0c = 12 571 + 572 +* (% style="color:blue" %)Mod: 0x01 = 1 573 + 574 +* TemDS18B20: 0x0000= 0 = 0 575 + 576 +* (% style="color:green" %)Interrupt: 0x00= 0 577 + 578 +* (% style="color:green" %)adc: 0x0030= 48 579 + 580 +* SHTTEM: 0x0114= 276 = 27.6 581 + 582 +* SHTHUM:0x0231 =561=56.1% 583 + 584 +* (% style="color:red" %)Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 585 + 586 +* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12 587 + 588 +* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,....... 589 + 503 503 === 2.3.2 Device ID === 504 504 592 + 505 505 ((( 506 506 By default, the Device ID equal to the last 6 bytes of IMEI. 507 507 ))) ... ... @@ -508,10 +508,12 @@ 508 508 509 509 ((( 510 510 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 599 + 600 + 511 511 ))) 512 512 513 513 ((( 514 -**Example:** 604 +(% style="color:blue" %)**Example:** 515 515 ))) 516 516 517 517 ((( ... ... @@ -519,13 +519,28 @@ 519 519 ))) 520 520 521 521 ((( 522 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 612 +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. 613 + 614 + 523 523 ))) 524 524 617 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 525 525 526 526 620 +By default, the Device ID equal to the last 15 bits of IMEI. 621 + 622 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 623 + 624 + 625 +**(% style="color:blue" %)Example:(%%)** 626 + 627 +AT+DEUI=868411056754138 628 + 629 + 630 + 527 527 === 2.3.3 Version Info === 528 528 633 + 529 529 ((( 530 530 These bytes include the hardware and software version. 531 531 ))) ... ... @@ -553,6 +553,7 @@ 553 553 554 554 === 2.3.4 Battery Info === 555 555 661 + 556 556 ((( 557 557 Ex1: 0x0B45 = 2885mV 558 558 ))) ... ... @@ -565,6 +565,7 @@ 565 565 566 566 === 2.3.5 Signal Strength === 567 567 674 + 568 568 ((( 569 569 NB-IoT Network signal Strength. 570 570 ))) ... ... @@ -597,6 +597,7 @@ 597 597 598 598 === 2.3.6 Temperature & Humidity === 599 599 707 + 600 600 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 601 601 602 602 [[image:image-20220709161741-3.png]] ... ... @@ -615,8 +615,9 @@ 615 615 616 616 == 2.4 Downlink Payload == 617 617 618 -By default, NDDS75 prints the downlink payload to console port. 619 619 727 +By default, N95S31B prints the downlink payload to console port. 728 + 620 620 [[image:image-20220709100028-1.png]] 621 621 622 622 ... ... @@ -653,7 +653,7 @@ 653 653 ))) 654 654 655 655 ((( 656 -If payload = 0x04FF, it will reset the DDS75765 +If payload = 0x04FF, it will reset the N95S31B 657 657 ))) 658 658 659 659 ... ... @@ -665,11 +665,74 @@ 665 665 666 666 667 667 668 -== 2.5 BatteryAnalysis==777 +== 2.5 Humidity and Temperature alarm function == 669 669 670 -=== 2.5.1 Battery Type === 671 671 780 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 672 672 782 + 783 +(% style="color:#037691" %)**AT+ SHHUM=min,max** 784 + 785 + 786 +² When min=0, and max≠0, Alarm higher than max 787 + 788 +² When min≠0, and max=0, Alarm lower than min 789 + 790 +² When min≠0 and max≠0, Alarm higher than max or lower than min 791 + 792 + 793 + (% style="color:blue" %)**Example:** 794 + 795 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 796 + 797 + 798 +(% style="color:#037691" %)**AT+ SHTEMP=min,max** 799 + 800 +² When min=0, and max≠0, Alarm higher than max 801 + 802 +² When min≠0, and max=0, Alarm lower than min 803 + 804 +² When min≠0 and max≠0, Alarm higher than max or lower than min 805 + 806 + 807 +**~ (% style="color:blue" %)Example:(%%)** 808 + 809 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 810 + 811 + 812 + 813 +== 2.6 Set the number of data to be uploaded and the recording time == 814 + 815 + 816 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 817 + 818 +* (% 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) 819 +* (% 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. 820 + 821 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 822 + 823 +[[image:image-20221009000513-1.png||height="732" width="1018"]] 824 + 825 + 826 + 827 +== 2.7 Read or Clear cached data == 828 + 829 + 830 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 831 + 832 +* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 833 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 834 + 835 +[[image:image-20220908163102-2.png]] 836 + 837 + 838 + 839 +== 2.8 Battery Analysis == 840 + 841 + 842 +=== 2.8.1 Battery Type === 843 + 844 + 673 673 ((( 674 674 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. 675 675 ))) ... ... @@ -692,10 +692,11 @@ 692 692 693 693 694 694 695 -=== 2. 5.2 Power consumption Analyze ===867 +=== 2.8.2 Power consumption Analyze === 696 696 869 + 697 697 ((( 698 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]871 +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. 699 699 ))) 700 700 701 701 ((( ... ... @@ -703,8 +703,9 @@ 703 703 ))) 704 704 705 705 706 -=== 2. 5.3 Battery Note ===879 +=== 2.8.3 Battery Note === 707 707 881 + 708 708 ((( 709 709 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. 710 710 ))) ... ... @@ -711,7 +711,7 @@ 711 711 712 712 713 713 714 -=== 2. 5.4 Replace the battery ===888 +=== 2.8.4 Replace the battery === 715 715 716 716 717 717 ((( ... ... @@ -727,6 +727,7 @@ 727 727 728 728 = 3. Access NB-IoT Module = 729 729 904 + 730 730 ((( 731 731 Users can directly access the AT command set of the NB-IoT module. 732 732 ))) ... ... @@ -733,6 +733,8 @@ 733 733 734 734 ((( 735 735 The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 911 + 912 + 736 736 ))) 737 737 738 738 [[image:1657333200519-600.png]] ... ... @@ -741,11 +741,13 @@ 741 741 742 742 = 4. Using the AT Commands = 743 743 921 + 744 744 == 4.1 Access AT Commands == 745 745 746 -See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]] 747 747 925 +See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]] 748 748 927 + 749 749 AT+<CMD>? : Help on <CMD> 750 750 751 751 AT+<CMD> : Run <CMD> ... ... @@ -785,7 +785,24 @@ 785 785 786 786 AT+SERVADDR : Server Address 787 787 967 +AT+TR : Get or Set record time 788 788 969 +AT+APN : Get or set the APN 970 + 971 +AT+FBAND : Get or Set whether to automatically modify the frequency band 972 + 973 +AT+DNSCFG : Get or Set DNS Server 974 + 975 +AT+GETSENSORVALUE : Returns the current sensor measurement 976 + 977 +AT+NOUD : Get or Set the number of data to be uploaded 978 + 979 +AT+CDP : Read or Clear cached data 980 + 981 +AT+SHTEMP: Get or Set alarm of temp 982 + 983 +AT+SHHUM: Get or Set alarm of moisture 984 + 789 789 (% style="color:#037691" %)**COAP Management** 790 790 791 791 AT+URI : Resource parameters ... ... @@ -819,6 +819,7 @@ 819 819 820 820 = 5. FAQ = 821 821 1018 + 822 822 == 5.1 How to Upgrade Firmware == 823 823 824 824 ... ... @@ -834,7 +834,7 @@ 834 834 835 835 836 836 ((( 837 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 1034 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 838 838 ))) 839 839 ))) 840 840 ... ... @@ -842,6 +842,7 @@ 842 842 843 843 = 6. Trouble Shooting = 844 844 1042 + 845 845 == 6.1 Connection problem when uploading firmware == 846 846 847 847 ... ... @@ -857,6 +857,7 @@ 857 857 858 858 == 6.2 AT Command input doesn't work == 859 859 1058 + 860 860 ((( 861 861 In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string. 862 862 ... ... @@ -906,5 +906,8 @@ 906 906 907 907 = 9. Support = 908 908 1108 + 909 909 * 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. 910 910 * 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]] 1111 + 1112 +
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content
- image-20220908154949-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.David - Size
-
... ... @@ -1,0 +1,1 @@ 1 +58.5 KB - Content
- image-20220908163102-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.David - Size
-
... ... @@ -1,0 +1,1 @@ 1 +29.7 KB - Content