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
-
... ... @@ -9,6 +9,7 @@ 9 9 10 10 **Table of Contents:** 11 11 12 +{{toc/}} 12 12 13 13 14 14 ... ... @@ -16,21 +16,35 @@ 16 16 17 17 = 1. Introduction = 18 18 20 + 19 19 == 1.1 What is N95S31B NB-IoT Sensor Node == 20 20 21 21 ((( 22 22 23 23 26 +((( 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*. 28 +))) 25 25 30 +((( 26 26 The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use. 32 +))) 27 27 34 +((( 28 28 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 36 +))) 29 29 38 +((( 30 30 N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report). 40 +))) 31 31 42 +((( 43 + 44 +))) 32 32 46 +((( 33 33 ~* make sure you have NB-IoT coverage locally. 48 +))) 34 34 35 35 36 36 ))) ... ... @@ -41,6 +41,7 @@ 41 41 42 42 == 1.2 Features == 43 43 59 + 44 44 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 45 45 * Monitor Temperature & Humidity via SHT31 46 46 * AT Commands to change parameters ... ... @@ -52,9 +52,6 @@ 52 52 * Micro SIM card slot for NB-IoT SIM 53 53 * 8500mAh Battery for long term use 54 54 55 - 56 - 57 - 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -74,7 +74,6 @@ 74 74 75 75 (% style="color:#037691" %)**Battery:** 76 76 77 - 78 78 * Li/SOCI2 un-chargeable battery 79 79 * Capacity: 8500mAh 80 80 * Self Discharge: <1% / Year @ 25°C ... ... @@ -81,11 +81,9 @@ 81 81 * Max continuously current: 130mA 82 82 * Max boost current: 2A, 1 second 83 83 84 - 85 - 86 - 87 87 == 1.4 Applications == 88 88 98 + 89 89 * Smart Buildings & Home Automation 90 90 * Logistics and Supply Chain Management 91 91 * Smart Metering ... ... @@ -97,15 +97,20 @@ 97 97 98 98 99 99 100 -== 1.5 Pin Definitions == 101 101 111 +== 1.5 Pin Definitions & Switch == 112 + 113 + 102 102 N95S31B use the mother board from NBSN95 which as below. 103 103 116 + 104 104 [[image:image-20220709144723-1.png]] 105 105 106 106 120 + 107 107 === 1.5.1 Jumper JP2 === 108 108 123 + 109 109 Power on Device when put this jumper. 110 110 111 111 ... ... @@ -112,14 +112,20 @@ 112 112 113 113 === 1.5.2 BOOT MODE / SW1 === 114 114 130 + 131 +((( 115 115 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. 133 +))) 116 116 135 +((( 117 117 2) Flash: work mode, device starts to work and send out console output for further debug 137 +))) 118 118 119 119 120 120 121 121 === 1.5.3 Reset Button === 122 122 143 + 123 123 Press to reboot the device. 124 124 125 125 ... ... @@ -126,14 +126,15 @@ 126 126 127 127 === 1.5.4 LED === 128 128 150 + 129 129 It will flash: 130 130 131 131 1. When boot the device in flash mode 132 132 1. Send an uplink packet 133 133 134 - 135 135 = 2. Use N95S31B to communicate with IoT Server = 136 136 158 + 137 137 == 2.1 How it works == 138 138 139 139 ... ... @@ -150,7 +150,7 @@ 150 150 151 151 ))) 152 152 153 -[[image:1657 350248151-650.png]]175 +[[image:1657520100595-569.png]] 154 154 155 155 ((( 156 156 ... ... @@ -166,26 +166,49 @@ 166 166 [[image:image-20220709150546-2.png]] 167 167 168 168 191 + 169 169 === 2.2.1 Test Requirement === 170 170 171 171 195 +((( 172 172 To use N95S31B in your city, make sure meet below requirements: 197 +))) 173 173 174 -* Your local operator has already distributed a NB-IoT Network there. 175 -* The local NB-IoT network used the band that N95S31B supports. 176 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 199 +* ((( 200 +Your local operator has already distributed a NB-IoT Network there. 201 +))) 202 +* ((( 203 +The local NB-IoT network used the band that N95S31B supports. 204 +))) 205 +* ((( 206 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 207 +))) 177 177 209 +((( 178 178 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 211 +))) 179 179 213 +((( 180 180 N95S31B supports different communication protocol such as : 215 +))) 181 181 182 182 ((( 183 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 184 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 185 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 186 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 218 +* ((( 219 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 220 +))) 221 +* ((( 222 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 223 +))) 224 +* ((( 225 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 226 +))) 227 +* ((( 228 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 229 +))) 187 187 231 +((( 188 188 We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server. 233 +))) 189 189 190 190 191 191 ))) ... ... @@ -196,6 +196,7 @@ 196 196 197 197 === 2.2.3 Insert SIM card === 198 198 244 + 199 199 ((( 200 200 Insert the NB-IoT Card get from your provider. 201 201 ))) ... ... @@ -211,14 +211,18 @@ 211 211 212 212 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 213 213 260 + 214 214 ((( 215 215 ((( 216 216 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. 264 + 265 + 217 217 ))) 218 218 ))) 219 219 220 220 [[image:1657351312545-300.png]] 221 221 271 + 222 222 **Connection:** 223 223 224 224 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -242,8 +242,9 @@ 242 242 243 243 [[image:1657329814315-101.png]] 244 244 295 + 245 245 ((( 246 -(% 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/]]297 +(% 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]]** 247 247 ))) 248 248 249 249 ... ... @@ -250,9 +250,10 @@ 250 250 251 251 === 2.2.5 Use CoAP protocol to uplink data === 252 252 253 -(% 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/]] 254 254 305 +(% 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/]]** 255 255 307 + 256 256 ((( 257 257 **Use below commands:** 258 258 ))) ... ... @@ -300,6 +300,7 @@ 300 300 301 301 === 2.2.7 Use MQTT protocol to uplink data === 302 302 355 + 303 303 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 304 304 305 305 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink ... ... @@ -315,6 +315,7 @@ 315 315 316 316 [[image:1657352645687-385.png]] 317 317 371 + 318 318 ((( 319 319 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. 320 320 ))) ... ... @@ -328,6 +328,7 @@ 328 328 329 329 === 2.2.8 Use TCP protocol to uplink data === 330 330 385 + 331 331 This feature is supported since firmware version v110 332 332 333 333 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -342,6 +342,7 @@ 342 342 343 343 === 2.2.9 Change Update Interval === 344 344 400 + 345 345 User can use below command to change the (% style="color:green" %)**uplink interval**. 346 346 347 347 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -350,58 +350,98 @@ 350 350 351 351 ))) 352 352 409 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 353 353 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).** 354 354 413 + 355 355 == 2.3 Uplink Payload == 356 356 357 357 358 -NBSN95 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. 417 +((( 418 +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. 419 +))) 359 359 360 360 422 +((( 361 361 For example: 424 +))) 362 362 363 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 426 +((( 427 + (% 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. 428 +))) 364 364 365 365 431 +((( 366 366 The uplink payloads are composed in ASCII String. For example: 433 +))) 367 367 435 +((( 368 368 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 437 +))) 369 369 439 +((( 370 370 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 441 +))) 371 371 372 372 444 +((( 373 373 (% style="color:red" %)**NOTE:** 446 +))) 374 374 375 375 (% style="color:red" %) 376 -1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]]. 377 -1. By default, the device will send an uplink message every 1 hour. 449 +1. ((( 450 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 451 +))) 452 +1. ((( 453 +**By default, the device will send an uplink message every 1 hour.** 378 378 379 379 380 380 457 + 458 +))) 459 + 381 381 === 2.3.1 Payload Analyze === 382 382 462 + 463 +==== 2.3.1.1 Before Firmware v1.2 ==== 464 + 383 383 N95S31B uplink payload includes in total 21 bytes 384 384 385 385 386 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width: 440px" %)468 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 387 387 |=(% style="width: 60px;" %)((( 388 388 **Size(bytes)** 389 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1** 390 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)((( 471 +)))|=(% 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** 472 +|(% 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" %)((( 473 +((( 391 391 Reserve/ Same as NBSN95 CFGMOD=1 475 +))) 392 392 477 +((( 393 393 No function here. 479 +))) 394 394 )))|(% style="width:77px" %)((( 395 -[[Temperature >>||anchor="H2.4.5A0Distance"]] 481 +((( 482 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 483 +))) 396 396 485 +((( 397 397 By SHT31 487 +))) 398 398 )))|(% style="width:80px" %)((( 399 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 489 +((( 490 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 491 +))) 400 400 493 +((( 401 401 By SHT31 402 402 ))) 496 +))) 403 403 404 404 ((( 499 + 500 + 405 405 ((( 406 406 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 407 407 ))) ... ... @@ -427,13 +427,40 @@ 427 427 428 428 ))) 429 429 430 -((( 431 - 432 -))) 526 +==== 2.3.1.2 Since Firmware v1.2 ==== 433 433 528 +In this mode, uplink payload includes 91 bytes in total by default. 434 434 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 + 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 ..... 534 + 535 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 536 + 537 +[[image:image-20220908154949-1.png]] 538 + 539 +The payload is ASCII string, representative same HEX: 540 + 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: 542 + 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**//,....... 556 + 435 435 === 2.3.2 Device ID === 436 436 559 + 437 437 ((( 438 438 By default, the Device ID equal to the last 6 bytes of IMEI. 439 439 ))) ... ... @@ -452,21 +452,44 @@ 452 452 453 453 ((( 454 454 The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 578 + 579 + 455 455 ))) 456 456 582 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:** 457 457 458 458 585 +By default, the Device ID equal to the last 15 bits of IMEI. 586 + 587 +User can use **AT+DEUI** to set Device ID 588 + 589 +**Example:** 590 + 591 +AT+DEUI=868411056754138 592 + 593 + 459 459 === 2.3.3 Version Info === 460 460 461 461 597 +((( 462 462 These bytes include the hardware and software version. 599 +))) 463 463 601 +((( 464 464 Higher byte: Specify hardware version: always 0x00 for N95S31B 603 +))) 465 465 605 +((( 466 466 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 607 +))) 467 467 609 +((( 610 + 611 +))) 468 468 613 +((( 469 469 For example: 0x00 6E: this device is N95S31B with firmware version 110. 615 +))) 470 470 471 471 ((( 472 472 ... ... @@ -475,6 +475,7 @@ 475 475 476 476 === 2.3.4 Battery Info === 477 477 624 + 478 478 ((( 479 479 Ex1: 0x0B45 = 2885mV 480 480 ))) ... ... @@ -487,6 +487,7 @@ 487 487 488 488 === 2.3.5 Signal Strength === 489 489 637 + 490 490 ((( 491 491 NB-IoT Network signal Strength. 492 492 ))) ... ... @@ -519,6 +519,7 @@ 519 519 520 520 === 2.3.6 Temperature & Humidity === 521 521 670 + 522 522 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 523 523 524 524 [[image:image-20220709161741-3.png]] ... ... @@ -535,10 +535,11 @@ 535 535 536 536 537 537 538 -== 2. 5Downlink Payload ==687 +== 2.4 Downlink Payload == 539 539 540 -By default, NDDS75 prints the downlink payload to console port. 541 541 690 +By default, N95S31B prints the downlink payload to console port. 691 + 542 542 [[image:image-20220709100028-1.png]] 543 543 544 544 ... ... @@ -575,7 +575,7 @@ 575 575 ))) 576 576 577 577 ((( 578 -If payload = 0x04FF, it will reset the DDS75728 +If payload = 0x04FF, it will reset the N95S31B 579 579 ))) 580 580 581 581 ... ... @@ -586,12 +586,59 @@ 586 586 ))) 587 587 588 588 739 +== 2.5 Humidity and Temperature alarm function == 589 589 590 - ==2.5Battery Analysis ==741 +➢ AT Command: 591 591 592 - === 2.5.1 BatteryType===743 +AT+ SHHUM=min,max 593 593 745 +² When min=0, and max≠0, Alarm higher than max 594 594 747 +² When min≠0, and max=0, Alarm lower than min 748 + 749 +² When min≠0 and max≠0, Alarm higher than max or lower than min 750 + 751 +Example: 752 + 753 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 754 + 755 + 756 +AT+ SHTEMP=min,max 757 + 758 +² When min=0, and max≠0, Alarm higher than max 759 + 760 +² When min≠0, and max=0, Alarm lower than min 761 + 762 +² When min≠0 and max≠0, Alarm higher than max or lower than min 763 + 764 +Example: 765 + 766 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 767 + 768 +== 2.6 Set the number of data to be uploaded and the recording time == 769 + 770 +➢ AT Command: 771 + 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) 773 + 774 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 775 + 776 +== 2.7 Read or Clear cached data == 777 + 778 +➢ AT Command: 779 + 780 +AT+CDP ~/~/ Read cached data 781 + 782 +[[image:image-20220908163102-2.png]] 783 + 784 +AT+CDP=0 ~/~/ Clear cached data 785 + 786 +== 2.8 Battery Analysis == 787 + 788 + 789 +=== 2.8.1 Battery Type === 790 + 791 + 595 595 ((( 596 596 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. 597 597 ))) ... ... @@ -614,10 +614,11 @@ 614 614 615 615 616 616 617 -=== 2. 5.2 Power consumption Analyze ===814 +=== 2.8.2 Power consumption Analyze === 618 618 816 + 619 619 ((( 620 -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/]]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. 621 621 ))) 622 622 623 623 ((( ... ... @@ -625,8 +625,9 @@ 625 625 ))) 626 626 627 627 628 -=== 2. 5.3 Battery Note ===826 +=== 2.8.3 Battery Note === 629 629 828 + 630 630 ((( 631 631 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. 632 632 ))) ... ... @@ -633,7 +633,7 @@ 633 633 634 634 635 635 636 -=== 2. 5.4 Replace the battery ===835 +=== 2.8.4 Replace the battery === 637 637 638 638 639 639 ((( ... ... @@ -649,6 +649,7 @@ 649 649 650 650 = 3. Access NB-IoT Module = 651 651 851 + 652 652 ((( 653 653 Users can directly access the AT command set of the NB-IoT module. 654 654 ))) ... ... @@ -655,6 +655,8 @@ 655 655 656 656 ((( 657 657 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/]] 858 + 859 + 658 658 ))) 659 659 660 660 [[image:1657333200519-600.png]] ... ... @@ -663,11 +663,13 @@ 663 663 664 664 = 4. Using the AT Commands = 665 665 868 + 666 666 == 4.1 Access AT Commands == 667 667 668 -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/]] 669 669 872 +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]] 670 670 874 + 671 671 AT+<CMD>? : Help on <CMD> 672 672 673 673 AT+<CMD> : Run <CMD> ... ... @@ -707,7 +707,24 @@ 707 707 708 708 AT+SERVADDR : Server Address 709 709 914 +AT+TR : Get or Set record time 710 710 916 +AT+APN : Get or set the APN 917 + 918 +AT+FBAND : Get or Set whether to automatically modify the frequency band 919 + 920 +AT+DNSCFG : Get or Set DNS Server 921 + 922 +AT+GETSENSORVALUE : Returns the current sensor measurement 923 + 924 +AT+NOUD : Get or Set the number of data to be uploaded 925 + 926 +AT+CDP : Read or Clear cached data 927 + 928 +AT+SHTEMP: Get or Set alarm of temp 929 + 930 +AT+SHHUM: Get or Set alarm of moisture 931 + 711 711 (% style="color:#037691" %)**COAP Management** 712 712 713 713 AT+URI : Resource parameters ... ... @@ -741,6 +741,7 @@ 741 741 742 742 = 5. FAQ = 743 743 965 + 744 744 == 5.1 How to Upgrade Firmware == 745 745 746 746 ... ... @@ -755,13 +755,16 @@ 755 755 ((( 756 756 757 757 758 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 980 +((( 981 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 759 759 ))) 983 +))) 760 760 761 761 762 762 763 763 = 6. Trouble Shooting = 764 764 989 + 765 765 == 6.1 Connection problem when uploading firmware == 766 766 767 767 ... ... @@ -777,6 +777,7 @@ 777 777 778 778 == 6.2 AT Command input doesn't work == 779 779 1005 + 780 780 ((( 781 781 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. 782 782 ... ... @@ -787,7 +787,7 @@ 787 787 = 7. Order Info = 788 788 789 789 790 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B** 1016 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 791 791 792 792 793 793 (% class="wikigeneratedid" %) ... ... @@ -802,7 +802,7 @@ 802 802 803 803 (% style="color:#037691" %)**Package Includes**: 804 804 805 -* NS E01DistanceDetectSensorNode x 11031 +* N95S31B NB-IoT Temperature and Humidity Sensor 806 806 * External antenna x 1 807 807 ))) 808 808 ... ... @@ -811,11 +811,10 @@ 811 811 812 812 (% style="color:#037691" %)**Dimension and weight**: 813 813 814 - 815 815 * Device Size: 13.0 x 5 x 4.5 cm 816 816 * Device Weight: 150g 817 -* Package Size / pcs : 1 5x12x 5.5cm818 -* Weight / pcs : 220g1042 +* Package Size / pcs : 14.0 x 8x 5 cm 1043 +* Weight / pcs : 180g 819 819 ))) 820 820 821 821 ((( ... ... @@ -827,5 +827,6 @@ 827 827 828 828 = 9. Support = 829 829 1055 + 830 830 * 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. 831 831 * 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