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,21 +17,35 @@ 17 17 18 18 = 1. Introduction = 19 19 20 + 20 20 == 1.1 What is N95S31B NB-IoT Sensor Node == 21 21 22 22 ((( 23 23 24 24 26 +((( 25 25 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 +))) 26 26 30 +((( 27 27 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 +))) 28 28 34 +((( 29 29 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 36 +))) 30 30 38 +((( 31 31 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 +))) 32 32 42 +((( 43 + 44 +))) 33 33 46 +((( 34 34 ~* make sure you have NB-IoT coverage locally. 48 +))) 35 35 36 36 37 37 ))) ... ... @@ -42,6 +42,7 @@ 42 42 43 43 == 1.2 Features == 44 44 59 + 45 45 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 46 46 * Monitor Temperature & Humidity via SHT31 47 47 * AT Commands to change parameters ... ... @@ -53,9 +53,6 @@ 53 53 * Micro SIM card slot for NB-IoT SIM 54 54 * 8500mAh Battery for long term use 55 55 56 - 57 - 58 - 59 59 == 1.3 Specification == 60 60 61 61 ... ... @@ -75,7 +75,6 @@ 75 75 76 76 (% style="color:#037691" %)**Battery:** 77 77 78 - 79 79 * Li/SOCI2 un-chargeable battery 80 80 * Capacity: 8500mAh 81 81 * Self Discharge: <1% / Year @ 25°C ... ... @@ -82,11 +82,9 @@ 82 82 * Max continuously current: 130mA 83 83 * Max boost current: 2A, 1 second 84 84 85 - 86 - 87 - 88 88 == 1.4 Applications == 89 89 98 + 90 90 * Smart Buildings & Home Automation 91 91 * Logistics and Supply Chain Management 92 92 * Smart Metering ... ... @@ -98,15 +98,20 @@ 98 98 99 99 100 100 101 -== 1.5 Pin Definitions == 102 102 111 +== 1.5 Pin Definitions & Switch == 112 + 113 + 103 103 N95S31B use the mother board from NBSN95 which as below. 104 104 116 + 105 105 [[image:image-20220709144723-1.png]] 106 106 107 107 120 + 108 108 === 1.5.1 Jumper JP2 === 109 109 123 + 110 110 Power on Device when put this jumper. 111 111 112 112 ... ... @@ -113,14 +113,20 @@ 113 113 114 114 === 1.5.2 BOOT MODE / SW1 === 115 115 130 + 131 +((( 116 116 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 +))) 117 117 135 +((( 118 118 2) Flash: work mode, device starts to work and send out console output for further debug 137 +))) 119 119 120 120 121 121 122 122 === 1.5.3 Reset Button === 123 123 143 + 124 124 Press to reboot the device. 125 125 126 126 ... ... @@ -127,14 +127,15 @@ 127 127 128 128 === 1.5.4 LED === 129 129 150 + 130 130 It will flash: 131 131 132 132 1. When boot the device in flash mode 133 133 1. Send an uplink packet 134 134 135 - 136 136 = 2. Use N95S31B to communicate with IoT Server = 137 137 158 + 138 138 == 2.1 How it works == 139 139 140 140 ... ... @@ -151,7 +151,7 @@ 151 151 152 152 ))) 153 153 154 -[[image:1657 350248151-650.png]]175 +[[image:1657520100595-569.png]] 155 155 156 156 ((( 157 157 ... ... @@ -167,26 +167,49 @@ 167 167 [[image:image-20220709150546-2.png]] 168 168 169 169 191 + 170 170 === 2.2.1 Test Requirement === 171 171 172 172 195 +((( 173 173 To use N95S31B in your city, make sure meet below requirements: 197 +))) 174 174 175 -* Your local operator has already distributed a NB-IoT Network there. 176 -* The local NB-IoT network used the band that N95S31B supports. 177 -* 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 +))) 178 178 209 +((( 179 179 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 211 +))) 180 180 213 +((( 181 181 N95S31B supports different communication protocol such as : 215 +))) 182 182 183 183 ((( 184 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 185 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 186 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 187 -* 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 +))) 188 188 231 +((( 189 189 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 +))) 190 190 191 191 192 192 ))) ... ... @@ -197,6 +197,7 @@ 197 197 198 198 === 2.2.3 Insert SIM card === 199 199 244 + 200 200 ((( 201 201 Insert the NB-IoT Card get from your provider. 202 202 ))) ... ... @@ -212,14 +212,18 @@ 212 212 213 213 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 214 214 260 + 215 215 ((( 216 216 ((( 217 217 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 + 218 218 ))) 219 219 ))) 220 220 221 221 [[image:1657351312545-300.png]] 222 222 271 + 223 223 **Connection:** 224 224 225 225 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -243,8 +243,9 @@ 243 243 244 244 [[image:1657329814315-101.png]] 245 245 295 + 246 246 ((( 247 -(% 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]]** 248 248 ))) 249 249 250 250 ... ... @@ -251,9 +251,10 @@ 251 251 252 252 === 2.2.5 Use CoAP protocol to uplink data === 253 253 254 -(% 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 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/]]** 256 256 307 + 257 257 ((( 258 258 **Use below commands:** 259 259 ))) ... ... @@ -301,6 +301,7 @@ 301 301 302 302 === 2.2.7 Use MQTT protocol to uplink data === 303 303 355 + 304 304 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 305 305 306 306 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink ... ... @@ -316,6 +316,7 @@ 316 316 317 317 [[image:1657352645687-385.png]] 318 318 371 + 319 319 ((( 320 320 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. 321 321 ))) ... ... @@ -329,6 +329,7 @@ 329 329 330 330 === 2.2.8 Use TCP protocol to uplink data === 331 331 385 + 332 332 This feature is supported since firmware version v110 333 333 334 334 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -343,6 +343,7 @@ 343 343 344 344 === 2.2.9 Change Update Interval === 345 345 400 + 346 346 User can use below command to change the (% style="color:green" %)**uplink interval**. 347 347 348 348 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -351,58 +351,98 @@ 351 351 352 352 ))) 353 353 409 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 354 354 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).** 355 355 413 + 356 356 == 2.3 Uplink Payload == 357 357 358 358 359 -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 +))) 360 360 361 361 422 +((( 362 362 For example: 424 +))) 363 363 364 - (% 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 +))) 365 365 366 366 431 +((( 367 367 The uplink payloads are composed in ASCII String. For example: 433 +))) 368 368 435 +((( 369 369 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 437 +))) 370 370 439 +((( 371 371 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 441 +))) 372 372 373 373 444 +((( 374 374 (% style="color:red" %)**NOTE:** 446 +))) 375 375 376 376 (% style="color:red" %) 377 -1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]]. 378 -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.** 379 379 380 380 381 381 457 + 458 +))) 459 + 382 382 === 2.3.1 Payload Analyze === 383 383 462 + 463 +==== 2.3.1.1 Before Firmware v1.2 ==== 464 + 384 384 N95S31B uplink payload includes in total 21 bytes 385 385 386 386 387 -(% 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" %) 388 388 |=(% style="width: 60px;" %)((( 389 389 **Size(bytes)** 390 -)))|=(% 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** 391 -|(% 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 +((( 392 392 Reserve/ Same as NBSN95 CFGMOD=1 475 +))) 393 393 477 +((( 394 394 No function here. 479 +))) 395 395 )))|(% style="width:77px" %)((( 396 -[[Temperature >>||anchor="H2.4.5A0Distance"]] 481 +((( 482 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 483 +))) 397 397 485 +((( 398 398 By SHT31 487 +))) 399 399 )))|(% style="width:80px" %)((( 400 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 489 +((( 490 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 491 +))) 401 401 493 +((( 402 402 By SHT31 403 403 ))) 496 +))) 404 404 405 405 ((( 499 + 500 + 406 406 ((( 407 407 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 408 408 ))) ... ... @@ -428,13 +428,40 @@ 428 428 429 429 ))) 430 430 431 -((( 432 - 433 -))) 526 +==== 2.3.1.2 Since Firmware v1.2 ==== 434 434 528 +In this mode, uplink payload includes 91 bytes in total by default. 435 435 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 + 436 436 === 2.3.2 Device ID === 437 437 559 + 438 438 ((( 439 439 By default, the Device ID equal to the last 6 bytes of IMEI. 440 440 ))) ... ... @@ -453,21 +453,44 @@ 453 453 454 454 ((( 455 455 The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 578 + 579 + 456 456 ))) 457 457 582 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:** 458 458 459 459 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 + 460 460 === 2.3.3 Version Info === 461 461 462 462 597 +((( 463 463 These bytes include the hardware and software version. 599 +))) 464 464 601 +((( 465 465 Higher byte: Specify hardware version: always 0x00 for N95S31B 603 +))) 466 466 605 +((( 467 467 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 607 +))) 468 468 609 +((( 610 + 611 +))) 469 469 613 +((( 470 470 For example: 0x00 6E: this device is N95S31B with firmware version 110. 615 +))) 471 471 472 472 ((( 473 473 ... ... @@ -476,6 +476,7 @@ 476 476 477 477 === 2.3.4 Battery Info === 478 478 624 + 479 479 ((( 480 480 Ex1: 0x0B45 = 2885mV 481 481 ))) ... ... @@ -488,6 +488,7 @@ 488 488 489 489 === 2.3.5 Signal Strength === 490 490 637 + 491 491 ((( 492 492 NB-IoT Network signal Strength. 493 493 ))) ... ... @@ -520,6 +520,7 @@ 520 520 521 521 === 2.3.6 Temperature & Humidity === 522 522 670 + 523 523 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 524 524 525 525 [[image:image-20220709161741-3.png]] ... ... @@ -538,8 +538,9 @@ 538 538 539 539 == 2.4 Downlink Payload == 540 540 541 -By default, NDDS75 prints the downlink payload to console port. 542 542 690 +By default, N95S31B prints the downlink payload to console port. 691 + 543 543 [[image:image-20220709100028-1.png]] 544 544 545 545 ... ... @@ -576,7 +576,7 @@ 576 576 ))) 577 577 578 578 ((( 579 -If payload = 0x04FF, it will reset the DDS75728 +If payload = 0x04FF, it will reset the N95S31B 580 580 ))) 581 581 582 582 ... ... @@ -587,12 +587,59 @@ 587 587 ))) 588 588 589 589 739 +== 2.5 Humidity and Temperature alarm function == 590 590 591 - ==2.5Battery Analysis ==741 +➢ AT Command: 592 592 593 - === 2.5.1 BatteryType===743 +AT+ SHHUM=min,max 594 594 745 +² When min=0, and max≠0, Alarm higher than max 595 595 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 + 596 596 ((( 597 597 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. 598 598 ))) ... ... @@ -615,10 +615,11 @@ 615 615 616 616 617 617 618 -=== 2. 5.2 Power consumption Analyze ===814 +=== 2.8.2 Power consumption Analyze === 619 619 816 + 620 620 ((( 621 -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. 622 622 ))) 623 623 624 624 ((( ... ... @@ -626,8 +626,9 @@ 626 626 ))) 627 627 628 628 629 -=== 2. 5.3 Battery Note ===826 +=== 2.8.3 Battery Note === 630 630 828 + 631 631 ((( 632 632 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. 633 633 ))) ... ... @@ -634,7 +634,7 @@ 634 634 635 635 636 636 637 -=== 2. 5.4 Replace the battery ===835 +=== 2.8.4 Replace the battery === 638 638 639 639 640 640 ((( ... ... @@ -650,6 +650,7 @@ 650 650 651 651 = 3. Access NB-IoT Module = 652 652 851 + 653 653 ((( 654 654 Users can directly access the AT command set of the NB-IoT module. 655 655 ))) ... ... @@ -656,6 +656,8 @@ 656 656 657 657 ((( 658 658 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 + 659 659 ))) 660 660 661 661 [[image:1657333200519-600.png]] ... ... @@ -664,11 +664,13 @@ 664 664 665 665 = 4. Using the AT Commands = 666 666 868 + 667 667 == 4.1 Access AT Commands == 668 668 669 -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/]] 670 670 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]] 671 671 874 + 672 672 AT+<CMD>? : Help on <CMD> 673 673 674 674 AT+<CMD> : Run <CMD> ... ... @@ -708,7 +708,24 @@ 708 708 709 709 AT+SERVADDR : Server Address 710 710 914 +AT+TR : Get or Set record time 711 711 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 + 712 712 (% style="color:#037691" %)**COAP Management** 713 713 714 714 AT+URI : Resource parameters ... ... @@ -742,6 +742,7 @@ 742 742 743 743 = 5. FAQ = 744 744 965 + 745 745 == 5.1 How to Upgrade Firmware == 746 746 747 747 ... ... @@ -756,13 +756,16 @@ 756 756 ((( 757 757 758 758 759 -(% 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.** 760 760 ))) 983 +))) 761 761 762 762 763 763 764 764 = 6. Trouble Shooting = 765 765 989 + 766 766 == 6.1 Connection problem when uploading firmware == 767 767 768 768 ... ... @@ -778,6 +778,7 @@ 778 778 779 779 == 6.2 AT Command input doesn't work == 780 780 1005 + 781 781 ((( 782 782 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. 783 783 ... ... @@ -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