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
-
... ... @@ -17,8 +17,11 @@ 17 17 18 18 = 1. Introduction = 19 19 20 + 20 20 == 1.1 What is N95S31B NB-IoT Sensor Node == 21 21 23 +((( 24 + 22 22 23 23 ((( 24 24 The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*. ... ... @@ -37,13 +37,20 @@ 37 37 ))) 38 38 39 39 ((( 43 + 44 +))) 45 + 46 +((( 40 40 ~* make sure you have NB-IoT coverage locally. 41 41 ))) 42 42 50 + 51 +))) 43 43 44 44 [[image:1657348284168-431.png]] 45 45 46 46 56 + 47 47 == 1.2 Features == 48 48 49 49 ... ... @@ -59,6 +59,7 @@ 59 59 * 8500mAh Battery for long term use 60 60 61 61 72 + 62 62 == 1.3 Specification == 63 63 64 64 ... ... @@ -69,12 +69,12 @@ 69 69 70 70 (% style="color:#037691" %)**NB-IoT Spec:** 71 71 72 -* B1 @H-FDD: 2100MHz 73 -* B3 @H-FDD: 1800MHz 74 -* B8 @H-FDD: 900MHz 75 -* B5 @H-FDD: 850MHz 76 -* B20 @H-FDD: 800MHz 77 -* B28 @H-FDD: 700MHz 83 +* - B1 @H-FDD: 2100MHz 84 +* - B3 @H-FDD: 1800MHz 85 +* - B8 @H-FDD: 900MHz 86 +* - B5 @H-FDD: 850MHz 87 +* - B20 @H-FDD: 800MHz 88 +* - B28 @H-FDD: 700MHz 78 78 79 79 (% style="color:#037691" %)**Battery:** 80 80 ... ... @@ -85,6 +85,7 @@ 85 85 * Max boost current: 2A, 1 second 86 86 87 87 99 + 88 88 == 1.4 Applications == 89 89 90 90 ... ... @@ -99,6 +99,7 @@ 99 99 100 100 101 101 114 + 102 102 == 1.5 Pin Definitions & Switch == 103 103 104 104 ... ... @@ -108,6 +108,7 @@ 108 108 [[image:image-20220709144723-1.png]] 109 109 110 110 124 + 111 111 === 1.5.1 Jumper JP2 === 112 112 113 113 ... ... @@ -114,18 +114,20 @@ 114 114 Power on Device when put this jumper. 115 115 116 116 131 + 117 117 === 1.5.2 BOOT MODE / SW1 === 118 118 119 119 120 120 ((( 121 - **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.136 +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. 122 122 ))) 123 123 124 124 ((( 125 - **2) Flash:**work mode, device starts to work and send out console output for further debug140 +2) Flash: work mode, device starts to work and send out console output for further debug 126 126 ))) 127 127 128 128 144 + 129 129 === 1.5.3 Reset Button === 130 130 131 131 ... ... @@ -132,18 +132,20 @@ 132 132 Press to reboot the device. 133 133 134 134 151 + 135 135 === 1.5.4 LED === 136 136 137 137 138 138 It will flash: 139 139 140 -1. When boot the device in flash mode 157 +1. When boot the device in flash mode 158 +1. Send an uplink packet 141 141 142 -2. Send an uplink packet 143 143 144 144 145 145 = 2. Use N95S31B to communicate with IoT Server = 146 146 164 + 147 147 == 2.1 How it works == 148 148 149 149 ... ... @@ -166,8 +166,10 @@ 166 166 167 167 ))) 168 168 187 + 169 169 == 2.2 Configure the N95S31B == 170 170 190 + 171 171 === 2.2.1 Power On N95S31B === 172 172 173 173 ... ... @@ -174,9 +174,10 @@ 174 174 [[image:image-20220709150546-2.png]] 175 175 176 176 177 -=== 2.2.2 Test Requirement === 178 178 198 +=== 2.2.1 Test Requirement === 179 179 200 + 180 180 ((( 181 181 To use N95S31B in your city, make sure meet below requirements: 182 182 ))) ... ... @@ -223,6 +223,7 @@ 223 223 [[image:1657350625843-586.png]] 224 224 225 225 247 + 226 226 === 2.2.3 Insert SIM card === 227 227 228 228 ... ... @@ -238,6 +238,7 @@ 238 238 [[image:1657351240556-536.png]] 239 239 240 240 263 + 241 241 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 242 242 243 243 ... ... @@ -252,13 +252,13 @@ 252 252 [[image:1657351312545-300.png]] 253 253 254 254 255 - (% style="color:blue" %)**Connection:**278 +**Connection:** 256 256 257 - (% style="background-color:yellow" %) **USB TTL GND <~-~-~-~-> GND**280 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 258 258 259 - **~(% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**282 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 260 260 261 - **~(% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**284 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 262 262 263 263 264 264 In the PC, use below serial tool settings: ... ... @@ -281,6 +281,7 @@ 281 281 ))) 282 282 283 283 307 + 284 284 === 2.2.5 Use CoAP protocol to uplink data === 285 285 286 286 ... ... @@ -317,6 +317,7 @@ 317 317 [[image:1657352185396-303.png]] 318 318 319 319 344 + 320 320 === 2.2.6 Use UDP protocol to uplink data(Default protocol) === 321 321 322 322 ... ... @@ -330,18 +330,19 @@ 330 330 [[image:1657352403317-397.png]] 331 331 332 332 358 + 333 333 === 2.2.7 Use MQTT protocol to uplink data === 334 334 335 335 336 336 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 337 337 338 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ 339 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ 340 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ 341 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ 342 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ 343 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/ 344 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/ 364 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 365 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 366 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 367 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 368 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 369 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 370 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 345 345 346 346 [[image:1657352634421-276.png]] 347 347 ... ... @@ -353,11 +353,13 @@ 353 353 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. 354 354 ))) 355 355 382 + 356 356 ((( 357 357 MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 358 358 ))) 359 359 360 360 388 + 361 361 === 2.2.8 Use TCP protocol to uplink data === 362 362 363 363 ... ... @@ -372,6 +372,7 @@ 372 372 [[image:1657352914475-252.png]] 373 373 374 374 403 + 375 375 === 2.2.9 Change Update Interval === 376 376 377 377 ... ... @@ -392,6 +392,7 @@ 392 392 ))) 393 393 394 394 424 + 395 395 == 2.3 Uplink Payload == 396 396 397 397 ... ... @@ -405,7 +405,7 @@ 405 405 ))) 406 406 407 407 ((( 408 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/ 438 + (% 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. 409 409 ))) 410 410 411 411 ... ... @@ -434,18 +434,23 @@ 434 434 **By default, the device will send an uplink message every 1 hour.** 435 435 436 436 467 + 437 437 438 438 ))) 439 439 440 440 === 2.3.1 Payload Analyze === 441 441 473 + 442 442 ==== 2.3.1.1 Before Firmware v1.2 ==== 443 443 444 444 445 -N95S31B uplink payload includes in total 21 bytes .477 +N95S31B uplink payload includes in total 21 bytes 446 446 447 -(% border="1" style="background-color:#f2f2f2; width:520px" %) 448 -|=(% style="width: 50px;background-color:#D9E2F3" %)**Size(bytes)**|=(% style="width: 45px;background-color:#D9E2F3" %)**6**|=(% style="width: 25px;background-color:#D9E2F3" %)2|=(% style="width: 25px;background-color:#D9E2F3" %)**2**|=(% style="width: 65px;background-color:#D9E2F3" %)**1**|=(% style="width: 50px;background-color:#D9E2F3" %)1|=(% style="width: 120px;background-color:#D9E2F3" %)5|=(% style="width: 70px;background-color:#D9E2F3" %)**2**|=(% style="width: 70px;background-color:#D9E2F3" %)**2** 479 + 480 +(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:745px" %) 481 +|=(% style="width: 60px;" %)((( 482 +**Size(bytes)** 483 +)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 162px;" %)5|=(% style="width: 102px;" %)**2**|=(% style="width: 81px;" %)**2** 449 449 |(% 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" %)((( 450 450 ((( 451 451 Reserve/ Same as NBSN95 CFGMOD=1 ... ... @@ -484,7 +484,7 @@ 484 484 [[image:1657354294009-643.png]] 485 485 486 486 487 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**522 +The payload is ASCII string, representative same HEX: **0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186** 488 488 489 489 **where:** 490 490 ... ... @@ -507,6 +507,7 @@ 507 507 ((( 508 508 509 509 545 + 510 510 511 511 ))) 512 512 ... ... @@ -517,8 +517,9 @@ 517 517 518 518 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. 519 519 520 -(% border="1" style="background-color:#f2f2f2; width:520px" %) 521 -|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**Size(bytes)**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**8**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:30px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:55px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:35px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:30px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**4** 556 + 557 +(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %) 558 +|(% 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** 522 522 |(% 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 ..... 523 523 524 524 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. ... ... @@ -529,10 +529,8 @@ 529 529 530 530 The payload is ASCII string, representative same HEX: 531 531 532 -**0x (% style="color:red" %)__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__ ** 569 +**0x (% style="color:red" %)__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__ __0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 533 533 534 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 535 - 536 536 **where:** 537 537 538 538 * (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 ... ... @@ -539,7 +539,7 @@ 539 539 540 540 * (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 541 541 542 -* (% style="color:#037691" %)**BAT:** 577 +* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 543 543 544 544 * (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 545 545 ... ... @@ -562,6 +562,8 @@ 562 562 * (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 563 563 564 564 600 + 601 + 565 565 === 2.3.2 Device ID === 566 566 567 567 ... ... @@ -602,6 +602,7 @@ 602 602 AT+DEUI=868411056754138 603 603 604 604 642 + 605 605 === 2.3.3 Version Info === 606 606 607 607 ... ... @@ -610,11 +610,11 @@ 610 610 ))) 611 611 612 612 ((( 613 - **Higher byte:**Specify hardware version: always 0x00 for N95S31B651 +Higher byte: Specify hardware version: always 0x00 for N95S31B 614 614 ))) 615 615 616 616 ((( 617 - **Lower byte:**Specify the software version: 0x6E=110, means firmware version 110655 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 618 618 ))) 619 619 620 620 ((( ... ... @@ -629,6 +629,7 @@ 629 629 630 630 ))) 631 631 670 + 632 632 === 2.3.4 Battery Info === 633 633 634 634 ... ... @@ -641,6 +641,7 @@ 641 641 ))) 642 642 643 643 683 + 644 644 === 2.3.5 Signal Strength === 645 645 646 646 ... ... @@ -673,6 +673,7 @@ 673 673 ))) 674 674 675 675 716 + 676 676 === 2.3.6 Temperature & Humidity === 677 677 678 678 ... ... @@ -691,17 +691,15 @@ 691 691 Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 692 692 693 693 735 + 694 694 == 2.4 Downlink Payload == 695 695 696 696 697 697 By default, N95S31B prints the downlink payload to console port. 698 698 699 -(% border="1" style="background-color:#f2f2f2; width:520px" %) 700 -|(% style="background-color:#d9e2f3; color:#0070c0; width:200px" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:100px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; width:170px" %)**Downlink payload size(bytes)** 701 -|(% style="width:204px" %)TDC(Transmit Time Interval)|(% style="width:80px" %)Any|(% style="width:94px" %)01|(% style="width:150px" %)4 702 -|(% style="width:204px" %)RESET|(% style="width:80px" %)Any|(% style="width:94px" %)04|(% style="width:150px" %)2 703 -|(% style="width:204px" %)INTMOD|(% style="width:80px" %)Any|(% style="width:94px" %)06|(% style="width:150px" %)4 741 +[[image:image-20220709100028-1.png]] 704 704 743 + 705 705 ((( 706 706 (% style="color:blue" %)**Examples:** 707 707 ))) ... ... @@ -746,6 +746,7 @@ 746 746 ))) 747 747 748 748 788 + 749 749 == 2.5 Humidity and Temperature alarm function == 750 750 751 751 ... ... @@ -781,6 +781,7 @@ 781 781 AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 782 782 783 783 824 + 784 784 == 2.6 Set the number of data to be uploaded and the recording time == 785 785 786 786 ... ... @@ -794,6 +794,7 @@ 794 794 [[image:image-20221009001045-1.png||height="726" width="1009"]] 795 795 796 796 838 + 797 797 == 2.7 Read or Clear cached data == 798 798 799 799 ... ... @@ -805,14 +805,70 @@ 805 805 [[image:image-20220908163102-2.png]] 806 806 807 807 808 -== 2.8 Battery & Power Consumption == 809 809 851 +== 2.8 Battery Analysis == 810 810 811 -N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 812 812 813 - [[**BatteryInfo & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]].854 +=== 2.8.1 Battery Type === 814 814 815 815 857 +((( 858 +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. 859 +))) 860 + 861 +((( 862 +The battery is designed to last for several years depends on the actually use environment and update interval. 863 +))) 864 + 865 +((( 866 +The battery related documents as below: 867 +))) 868 + 869 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 870 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 871 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 872 + 873 +((( 874 +[[image:image-20220709101450-2.png]] 875 +))) 876 + 877 + 878 + 879 +=== 2.8.2 Power consumption Analyze === 880 + 881 + 882 +((( 883 +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. 884 +))) 885 + 886 +((( 887 + 888 +))) 889 + 890 + 891 +=== 2.8.3 Battery Note === 892 + 893 + 894 +((( 895 +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. 896 +))) 897 + 898 + 899 + 900 +=== 2.8.4 Replace the battery === 901 + 902 + 903 +((( 904 +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. 905 +))) 906 + 907 + 908 +((( 909 +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). 910 +))) 911 + 912 + 913 + 816 816 = 3. Access NB-IoT Module = 817 817 818 818 ... ... @@ -829,8 +829,10 @@ 829 829 [[image:1657333200519-600.png]] 830 830 831 831 930 + 832 832 = 4. Using the AT Commands = 833 833 933 + 834 834 == 4.1 Access AT Commands == 835 835 836 836 ... ... @@ -924,8 +924,10 @@ 924 924 AT+PWORD : Serial Access Password 925 925 926 926 1027 + 927 927 = 5. FAQ = 928 928 1030 + 929 929 == 5.1 How to Upgrade Firmware == 930 930 931 931 ... ... @@ -938,14 +938,18 @@ 938 938 ))) 939 939 940 940 ((( 941 - FirmwareDownload:[[https:~~/~~/www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0>>https://www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0]]1043 + 942 942 1045 +((( 943 943 (% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 944 944 ))) 1048 +))) 945 945 946 946 1051 + 947 947 = 6. Trouble Shooting = 948 948 1054 + 949 949 == 6.1 Connection problem when uploading firmware == 950 950 951 951 ... ... @@ -953,7 +953,12 @@ 953 953 **Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]] 954 954 ))) 955 955 1062 +(% class="wikigeneratedid" %) 1063 +((( 1064 + 1065 +))) 956 956 1067 + 957 957 == 6.2 AT Command input doesn't work == 958 958 959 959 ... ... @@ -963,12 +963,7 @@ 963 963 964 964 ))) 965 965 966 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 967 967 968 - 969 -This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**. 970 - 971 - 972 972 = 7. Order Info = 973 973 974 974 ... ... @@ -975,6 +975,11 @@ 975 975 Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 976 976 977 977 1084 +(% class="wikigeneratedid" %) 1085 +((( 1086 + 1087 +))) 1088 + 978 978 = 8. Packing Info = 979 979 980 980 ((( ... ... @@ -997,13 +997,15 @@ 997 997 * Weight / pcs : 180g 998 998 ))) 999 999 1111 +((( 1112 + 1000 1000 1001 1001 1115 + 1116 +))) 1117 + 1002 1002 = 9. Support = 1003 1003 1004 1004 1005 1005 * 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. 1006 - 1007 1007 * 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]] 1008 - 1009 -