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, 3 added, 0 removed)
Details
- Page properties
-
- 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 ... ... @@ -67,8 +67,6 @@ 67 67 * 8500mAh Battery for long term use 68 68 69 69 70 - 71 - 72 72 == 1.3 Specification == 73 73 74 74 ... ... @@ -77,7 +77,6 @@ 77 77 * Supply Voltage: 2.1v ~~ 3.6v 78 78 * Operating Temperature: -40 ~~ 85°C 79 79 80 - 81 81 (% style="color:#037691" %)**NB-IoT Spec:** 82 82 83 83 * - B1 @H-FDD: 2100MHz ... ... @@ -87,7 +87,6 @@ 87 87 * - B20 @H-FDD: 800MHz 88 88 * - B28 @H-FDD: 700MHz 89 89 90 - 91 91 (% style="color:#037691" %)**Battery:** 92 92 93 93 * Li/SOCI2 un-chargeable battery ... ... @@ -97,10 +97,9 @@ 97 97 * Max boost current: 2A, 1 second 98 98 99 99 100 - 101 - 102 102 == 1.4 Applications == 103 103 100 + 104 104 * Smart Buildings & Home Automation 105 105 * Logistics and Supply Chain Management 106 106 * Smart Metering ... ... @@ -112,15 +112,21 @@ 112 112 113 113 114 114 115 -== 1.5 Pin Definitions == 116 116 113 + 114 +== 1.5 Pin Definitions & Switch == 115 + 116 + 117 117 N95S31B use the mother board from NBSN95 which as below. 118 118 119 + 119 119 [[image:image-20220709144723-1.png]] 120 120 121 121 123 + 122 122 === 1.5.1 Jumper JP2 === 123 123 126 + 124 124 Power on Device when put this jumper. 125 125 126 126 ... ... @@ -127,6 +127,7 @@ 127 127 128 128 === 1.5.2 BOOT MODE / SW1 === 129 129 133 + 130 130 ((( 131 131 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 132 ))) ... ... @@ -139,6 +139,7 @@ 139 139 140 140 === 1.5.3 Reset Button === 141 141 146 + 142 142 Press to reboot the device. 143 143 144 144 ... ... @@ -145,6 +145,7 @@ 145 145 146 146 === 1.5.4 LED === 147 147 153 + 148 148 It will flash: 149 149 150 150 1. When boot the device in flash mode ... ... @@ -151,10 +151,9 @@ 151 151 1. Send an uplink packet 152 152 153 153 154 - 155 - 156 156 = 2. Use N95S31B to communicate with IoT Server = 157 157 162 + 158 158 == 2.1 How it works == 159 159 160 160 ... ... @@ -171,7 +171,7 @@ 171 171 172 172 ))) 173 173 174 -[[image:1657 350248151-650.png]]179 +[[image:1657520100595-569.png]] 175 175 176 176 ((( 177 177 ... ... @@ -187,6 +187,7 @@ 187 187 [[image:image-20220709150546-2.png]] 188 188 189 189 195 + 190 190 === 2.2.1 Test Requirement === 191 191 192 192 ... ... @@ -239,6 +239,7 @@ 239 239 240 240 === 2.2.3 Insert SIM card === 241 241 248 + 242 242 ((( 243 243 Insert the NB-IoT Card get from your provider. 244 244 ))) ... ... @@ -254,14 +254,18 @@ 254 254 255 255 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 256 256 264 + 257 257 ((( 258 258 ((( 259 259 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. 268 + 269 + 260 260 ))) 261 261 ))) 262 262 263 263 [[image:1657351312545-300.png]] 264 264 275 + 265 265 **Connection:** 266 266 267 267 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -285,8 +285,9 @@ 285 285 286 286 [[image:1657329814315-101.png]] 287 287 299 + 288 288 ((( 289 -(% 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/]]301 +(% 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]]** 290 290 ))) 291 291 292 292 ... ... @@ -293,9 +293,10 @@ 293 293 294 294 === 2.2.5 Use CoAP protocol to uplink data === 295 295 296 -(% 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/]] 297 297 309 +(% 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/]]** 298 298 311 + 299 299 ((( 300 300 **Use below commands:** 301 301 ))) ... ... @@ -343,6 +343,7 @@ 343 343 344 344 === 2.2.7 Use MQTT protocol to uplink data === 345 345 359 + 346 346 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 347 347 348 348 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink ... ... @@ -358,6 +358,7 @@ 358 358 359 359 [[image:1657352645687-385.png]] 360 360 375 + 361 361 ((( 362 362 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. 363 363 ))) ... ... @@ -371,6 +371,7 @@ 371 371 372 372 === 2.2.8 Use TCP protocol to uplink data === 373 373 389 + 374 374 This feature is supported since firmware version v110 375 375 376 376 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -385,6 +385,7 @@ 385 385 386 386 === 2.2.9 Change Update Interval === 387 387 404 + 388 388 User can use below command to change the (% style="color:green" %)**uplink interval**. 389 389 390 390 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -393,13 +393,21 @@ 393 393 394 394 ))) 395 395 413 +((( 414 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 415 +))) 396 396 417 +((( 418 +(% 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).** 419 +))) 397 397 421 + 422 + 398 398 == 2.3 Uplink Payload == 399 399 400 400 401 401 ((( 402 -N BSN95427 +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. 403 403 ))) 404 404 405 405 ... ... @@ -408,7 +408,7 @@ 408 408 ))) 409 409 410 410 ((( 411 - (% 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.436 + (% 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. 412 412 ))) 413 413 414 414 ... ... @@ -431,25 +431,30 @@ 431 431 432 432 (% style="color:red" %) 433 433 1. ((( 434 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 459 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 435 435 ))) 436 436 1. ((( 437 -By default, the device will send an uplink message every 1 hour. 438 -))) 462 +**By default, the device will send an uplink message every 1 hour.** 439 439 440 440 441 441 466 + 467 +))) 442 442 443 443 === 2.3.1 Payload Analyze === 444 444 471 + 472 +==== 2.3.1.1 Before Firmware v1.2 ==== 473 + 474 + 445 445 N95S31B uplink payload includes in total 21 bytes 446 446 447 447 448 -(% border=" 1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)478 +(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:760px" %) 449 449 |=(% style="width: 60px;" %)((( 450 450 **Size(bytes)** 451 -)))|=(% 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**452 -|(% 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" %)(((481 +)))|=(% 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** 482 +|(% 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" %)((( 453 453 ((( 454 454 Reserve/ Same as NBSN95 CFGMOD=1 455 455 ))) ... ... @@ -457,7 +457,7 @@ 457 457 ((( 458 458 No function here. 459 459 ))) 460 -)))|(% style="width: 77px" %)(((490 +)))|(% style="width:106px" %)((( 461 461 ((( 462 462 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 463 463 ))) ... ... @@ -465,7 +465,7 @@ 465 465 ((( 466 466 By SHT31 467 467 ))) 468 -)))|(% style="width:8 0px" %)(((498 +)))|(% style="width:85px" %)((( 469 469 ((( 470 470 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 471 471 ))) ... ... @@ -476,6 +476,8 @@ 476 476 ))) 477 477 478 478 ((( 509 + 510 + 479 479 ((( 480 480 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 481 481 ))) ... ... @@ -487,27 +487,83 @@ 487 487 488 488 The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 489 489 490 -* Device ID: 0x724031607457 = 724031607457 491 -* Version: 0x006e=110=1.1.0 522 +* Device ID: 0x724031607457 = 724031607457 492 492 493 -* BAT: 0x0ccd = 3277 mV = 3.277V 494 -* Signal: 0x1b = 27 495 -* Model: 0x01 = 1 524 +* Version: 0x006e=110=1.1.0 525 + 526 +* BAT: 0x0ccd = 3277 mV = 3.277V 527 + 528 +* Signal: 0x1b = 27 529 + 530 +* Model: 0x01 = 1 531 + 496 496 * 0x00dc000ccc= reserve, ignore in N95S31B 497 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 498 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 499 499 534 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 535 + 536 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 537 + 500 500 ((( 501 501 502 -))) 503 503 504 - (((541 + 505 505 506 506 ))) 507 507 545 +==== 2.3.1.2 Since Firmware v1.2 ==== 508 508 547 + 548 +In this mode, uplink payload includes 91 bytes in total by default. 549 + 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 + 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 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 558 + 559 + 560 +[[image:image-20220908154949-1.png]] 561 + 562 + 563 +The payload is ASCII string, representative same HEX: 564 + 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 + 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 + 577 +* TemDS18B20: 0x0000= 0 = 0 578 + 579 +* (% style="color:green" %)Interrupt: 0x00= 0 580 + 581 +* (% style="color:green" %)adc: 0x0030= 48 582 + 583 +* SHTTEM: 0x0114= 276 = 27.6 584 + 585 +* SHTHUM:0x0231 =561=56.1% 586 + 587 +* (% style="color:red" %)Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 588 + 589 +* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12 590 + 591 +* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,....... 592 + 593 + 594 + 595 + 509 509 === 2.3.2 Device ID === 510 510 598 + 511 511 ((( 512 512 By default, the Device ID equal to the last 6 bytes of IMEI. 513 513 ))) ... ... @@ -526,21 +526,44 @@ 526 526 527 527 ((( 528 528 The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 617 + 618 + 529 529 ))) 530 530 621 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:** 531 531 532 532 624 +By default, the Device ID equal to the last 15 bits of IMEI. 625 + 626 +User can use **AT+DEUI** to set Device ID 627 + 628 +**Example:** 629 + 630 +AT+DEUI=868411056754138 631 + 632 + 533 533 === 2.3.3 Version Info === 534 534 535 535 636 +((( 536 536 These bytes include the hardware and software version. 638 +))) 537 537 640 +((( 538 538 Higher byte: Specify hardware version: always 0x00 for N95S31B 642 +))) 539 539 644 +((( 540 540 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 646 +))) 541 541 648 +((( 649 + 650 +))) 542 542 652 +((( 543 543 For example: 0x00 6E: this device is N95S31B with firmware version 110. 654 +))) 544 544 545 545 ((( 546 546 ... ... @@ -549,6 +549,7 @@ 549 549 550 550 === 2.3.4 Battery Info === 551 551 663 + 552 552 ((( 553 553 Ex1: 0x0B45 = 2885mV 554 554 ))) ... ... @@ -561,6 +561,7 @@ 561 561 562 562 === 2.3.5 Signal Strength === 563 563 676 + 564 564 ((( 565 565 NB-IoT Network signal Strength. 566 566 ))) ... ... @@ -593,6 +593,7 @@ 593 593 594 594 === 2.3.6 Temperature & Humidity === 595 595 709 + 596 596 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 597 597 598 598 [[image:image-20220709161741-3.png]] ... ... @@ -611,8 +611,9 @@ 611 611 612 612 == 2.4 Downlink Payload == 613 613 614 -By default, NDDS75 prints the downlink payload to console port. 615 615 729 +By default, N95S31B prints the downlink payload to console port. 730 + 616 616 [[image:image-20220709100028-1.png]] 617 617 618 618 ... ... @@ -649,7 +649,7 @@ 649 649 ))) 650 650 651 651 ((( 652 -If payload = 0x04FF, it will reset the DDS75767 +If payload = 0x04FF, it will reset the N95S31B 653 653 ))) 654 654 655 655 ... ... @@ -660,12 +660,59 @@ 660 660 ))) 661 661 662 662 778 +== 2.5 Humidity and Temperature alarm function == 663 663 664 - ==2.5Battery Analysis ==780 +➢ AT Command: 665 665 666 - === 2.5.1 BatteryType===782 +AT+ SHHUM=min,max 667 667 784 +² When min=0, and max≠0, Alarm higher than max 668 668 786 +² When min≠0, and max=0, Alarm lower than min 787 + 788 +² When min≠0 and max≠0, Alarm higher than max or lower than min 789 + 790 +Example: 791 + 792 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 793 + 794 + 795 +AT+ SHTEMP=min,max 796 + 797 +² When min=0, and max≠0, Alarm higher than max 798 + 799 +² When min≠0, and max=0, Alarm lower than min 800 + 801 +² When min≠0 and max≠0, Alarm higher than max or lower than min 802 + 803 +Example: 804 + 805 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 806 + 807 +== 2.6 Set the number of data to be uploaded and the recording time == 808 + 809 +➢ AT Command: 810 + 811 +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) 812 + 813 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 814 + 815 +== 2.7 Read or Clear cached data == 816 + 817 +➢ AT Command: 818 + 819 +AT+CDP ~/~/ Read cached data 820 + 821 +[[image:image-20220908163102-2.png]] 822 + 823 +AT+CDP=0 ~/~/ Clear cached data 824 + 825 +== 2.8 Battery Analysis == 826 + 827 + 828 +=== 2.8.1 Battery Type === 829 + 830 + 669 669 ((( 670 670 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. 671 671 ))) ... ... @@ -688,10 +688,11 @@ 688 688 689 689 690 690 691 -=== 2. 5.2 Power consumption Analyze ===853 +=== 2.8.2 Power consumption Analyze === 692 692 855 + 693 693 ((( 694 -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/]]857 +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. 695 695 ))) 696 696 697 697 ((( ... ... @@ -699,8 +699,9 @@ 699 699 ))) 700 700 701 701 702 -=== 2. 5.3 Battery Note ===865 +=== 2.8.3 Battery Note === 703 703 867 + 704 704 ((( 705 705 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. 706 706 ))) ... ... @@ -707,7 +707,7 @@ 707 707 708 708 709 709 710 -=== 2. 5.4 Replace the battery ===874 +=== 2.8.4 Replace the battery === 711 711 712 712 713 713 ((( ... ... @@ -723,6 +723,7 @@ 723 723 724 724 = 3. Access NB-IoT Module = 725 725 890 + 726 726 ((( 727 727 Users can directly access the AT command set of the NB-IoT module. 728 728 ))) ... ... @@ -729,6 +729,8 @@ 729 729 730 730 ((( 731 731 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/]] 897 + 898 + 732 732 ))) 733 733 734 734 [[image:1657333200519-600.png]] ... ... @@ -737,11 +737,13 @@ 737 737 738 738 = 4. Using the AT Commands = 739 739 907 + 740 740 == 4.1 Access AT Commands == 741 741 742 -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/]] 743 743 911 +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]] 744 744 913 + 745 745 AT+<CMD>? : Help on <CMD> 746 746 747 747 AT+<CMD> : Run <CMD> ... ... @@ -781,7 +781,24 @@ 781 781 782 782 AT+SERVADDR : Server Address 783 783 953 +AT+TR : Get or Set record time 784 784 955 +AT+APN : Get or set the APN 956 + 957 +AT+FBAND : Get or Set whether to automatically modify the frequency band 958 + 959 +AT+DNSCFG : Get or Set DNS Server 960 + 961 +AT+GETSENSORVALUE : Returns the current sensor measurement 962 + 963 +AT+NOUD : Get or Set the number of data to be uploaded 964 + 965 +AT+CDP : Read or Clear cached data 966 + 967 +AT+SHTEMP: Get or Set alarm of temp 968 + 969 +AT+SHHUM: Get or Set alarm of moisture 970 + 785 785 (% style="color:#037691" %)**COAP Management** 786 786 787 787 AT+URI : Resource parameters ... ... @@ -815,6 +815,7 @@ 815 815 816 816 = 5. FAQ = 817 817 1004 + 818 818 == 5.1 How to Upgrade Firmware == 819 819 820 820 ... ... @@ -829,13 +829,16 @@ 829 829 ((( 830 830 831 831 832 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 1019 +((( 1020 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 833 833 ))) 1022 +))) 834 834 835 835 836 836 837 837 = 6. Trouble Shooting = 838 838 1028 + 839 839 == 6.1 Connection problem when uploading firmware == 840 840 841 841 ... ... @@ -851,6 +851,7 @@ 851 851 852 852 == 6.2 AT Command input doesn't work == 853 853 1044 + 854 854 ((( 855 855 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. 856 856 ... ... @@ -900,5 +900,6 @@ 900 900 901 901 = 9. Support = 902 902 1094 + 903 903 * 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. 904 904 * 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]]
- 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