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,7 +67,6 @@ 67 67 * 8500mAh Battery for long term use 68 68 69 69 70 - 71 71 == 1.3 Specification == 72 72 73 73 ... ... @@ -94,9 +94,9 @@ 94 94 * Max boost current: 2A, 1 second 95 95 96 96 97 - 98 98 == 1.4 Applications == 99 99 100 + 100 100 * Smart Buildings & Home Automation 101 101 * Logistics and Supply Chain Management 102 102 * Smart Metering ... ... @@ -108,15 +108,20 @@ 108 108 109 109 110 110 112 + 111 111 == 1.5 Pin Definitions & Switch == 112 112 115 + 113 113 N95S31B use the mother board from NBSN95 which as below. 114 114 118 + 115 115 [[image:image-20220709144723-1.png]] 116 116 117 117 122 + 118 118 === 1.5.1 Jumper JP2 === 119 119 125 + 120 120 Power on Device when put this jumper. 121 121 122 122 ... ... @@ -123,12 +123,13 @@ 123 123 124 124 === 1.5.2 BOOT MODE / SW1 === 125 125 132 + 126 126 ((( 127 -1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. 134 +**1) ISP: ** upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. 128 128 ))) 129 129 130 130 ((( 131 -2) Flash: work mode, device starts to work and send out console output for further debug 138 +**2) Flash:** work mode, device starts to work and send out console output for further debug 132 132 ))) 133 133 134 134 ... ... @@ -135,6 +135,7 @@ 135 135 136 136 === 1.5.3 Reset Button === 137 137 145 + 138 138 Press to reboot the device. 139 139 140 140 ... ... @@ -141,14 +141,18 @@ 141 141 142 142 === 1.5.4 LED === 143 143 152 + 144 144 It will flash: 145 145 146 -1. When boot the device in flash mode 147 -1. Send an uplink packet 155 +1. When boot the device in flash mode 148 148 157 +2. Send an uplink packet 149 149 159 + 160 + 150 150 = 2. Use N95S31B to communicate with IoT Server = 151 151 163 + 152 152 == 2.1 How it works == 153 153 154 154 ... ... @@ -181,6 +181,7 @@ 181 181 [[image:image-20220709150546-2.png]] 182 182 183 183 196 + 184 184 === 2.2.1 Test Requirement === 185 185 186 186 ... ... @@ -233,6 +233,7 @@ 233 233 234 234 === 2.2.3 Insert SIM card === 235 235 249 + 236 236 ((( 237 237 Insert the NB-IoT Card get from your provider. 238 238 ))) ... ... @@ -248,23 +248,27 @@ 248 248 249 249 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 250 250 265 + 251 251 ((( 252 252 ((( 253 253 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. 269 + 270 + 254 254 ))) 255 255 ))) 256 256 257 257 [[image:1657351312545-300.png]] 258 258 259 -**Connection:** 260 260 261 - background-color:yellow" %)USB TTL GND <~-~-~-~-> GND277 +**(% style="color:blue" %)Connection:** 262 262 263 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~->UART_RXD279 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 264 264 265 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD281 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 266 266 283 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 267 267 285 + 268 268 In the PC, use below serial tool settings: 269 269 270 270 * Baud: (% style="color:green" %)**9600** ... ... @@ -279,8 +279,9 @@ 279 279 280 280 [[image:1657329814315-101.png]] 281 281 300 + 282 282 ((( 283 -(% 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/]]302 +(% 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]]** 284 284 ))) 285 285 286 286 ... ... @@ -287,9 +287,10 @@ 287 287 288 288 === 2.2.5 Use CoAP protocol to uplink data === 289 289 290 -(% 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/]] 291 291 310 +(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]** 292 292 312 + 293 293 ((( 294 294 **Use below commands:** 295 295 ))) ... ... @@ -298,10 +298,10 @@ 298 298 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 299 299 ))) 300 300 * ((( 301 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 321 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 302 302 ))) 303 303 * ((( 304 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 324 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 305 305 ))) 306 306 307 307 ((( ... ... @@ -337,15 +337,16 @@ 337 337 338 338 === 2.2.7 Use MQTT protocol to uplink data === 339 339 360 + 340 340 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 341 341 342 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 343 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 344 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 345 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 346 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 347 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 348 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 363 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 364 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 365 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 366 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 367 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 368 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/ Set the sending topic of MQTT 369 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/ Set the subscription topic of MQTT 349 349 350 350 [[image:1657352634421-276.png]] 351 351 ... ... @@ -352,6 +352,7 @@ 352 352 353 353 [[image:1657352645687-385.png]] 354 354 376 + 355 355 ((( 356 356 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. 357 357 ))) ... ... @@ -365,6 +365,7 @@ 365 365 366 366 === 2.2.8 Use TCP protocol to uplink data === 367 367 390 + 368 368 This feature is supported since firmware version v110 369 369 370 370 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -379,6 +379,7 @@ 379 379 380 380 === 2.2.9 Change Update Interval === 381 381 405 + 382 382 User can use below command to change the (% style="color:green" %)**uplink interval**. 383 383 384 384 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -387,13 +387,21 @@ 387 387 388 388 ))) 389 389 414 +((( 415 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 416 +))) 390 390 418 +((( 419 +(% 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).** 420 +))) 391 391 422 + 423 + 392 392 == 2.3 Uplink Payload == 393 393 394 394 395 395 ((( 396 -N BSN95428 +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. 397 397 ))) 398 398 399 399 ... ... @@ -402,7 +402,7 @@ 402 402 ))) 403 403 404 404 ((( 405 - (% 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.437 + (% 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. 406 406 ))) 407 407 408 408 ... ... @@ -425,22 +425,30 @@ 425 425 426 426 (% style="color:red" %) 427 427 1. ((( 428 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 460 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 429 429 ))) 430 430 1. ((( 431 -By default, the device will send an uplink message every 1 hour. 463 +**By default, the device will send an uplink message every 1 hour.** 464 + 465 + 466 + 467 + 432 432 ))) 433 433 434 434 === 2.3.1 Payload Analyze === 435 435 472 + 473 +==== 2.3.1.1 Before Firmware v1.2 ==== 474 + 475 + 436 436 N95S31B uplink payload includes in total 21 bytes 437 437 438 438 439 -(% border=" 1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)440 -|=(% style="width: 60px;" %)(((479 +(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 480 +|=(% style="width: 50px;" %)((( 441 441 **Size(bytes)** 442 -)))|=(% 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**443 -|(% 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" %)(((482 +)))|=(% style="width: 40px;" %)**6**|=(% style="width: 20px;" %)2|=(% style="width: 20px;" %)**2**|=(% style="width: 60px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 100px;" %)5|=(% style="width: 102px;" %)**2**|=(% style="width: 81px;" %)**2** 483 +|(% 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" %)((( 444 444 ((( 445 445 Reserve/ Same as NBSN95 CFGMOD=1 446 446 ))) ... ... @@ -448,7 +448,7 @@ 448 448 ((( 449 449 No function here. 450 450 ))) 451 -)))|(% style="width: 77px" %)(((491 +)))|(% style="width:102px" %)((( 452 452 ((( 453 453 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 454 454 ))) ... ... @@ -456,7 +456,7 @@ 456 456 ((( 457 457 By SHT31 458 458 ))) 459 -)))|(% style="width:8 0px" %)(((499 +)))|(% style="width:81px" %)((( 460 460 ((( 461 461 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 462 462 ))) ... ... @@ -467,6 +467,8 @@ 467 467 ))) 468 468 469 469 ((( 510 + 511 + 470 470 ((( 471 471 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 472 472 ))) ... ... @@ -476,29 +476,89 @@ 476 476 [[image:1657354294009-643.png]] 477 477 478 478 479 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:521 +The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186** 480 480 481 -* Device ID: 0x724031607457 = 724031607457 482 -* Version: 0x006e=110=1.1.0 523 +**where:** 483 483 484 -* BAT: 0x0ccd = 3277 mV = 3.277V 485 -* Signal: 0x1b = 27 486 -* Model: 0x01 = 1 487 -* 0x00dc000ccc= reserve, ignore in N95S31B 488 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 489 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 525 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 490 490 527 +* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 528 + 529 +* (% style="color:#037691" %)**BAT:** (%%) 0x0ccd = 3277 mV = 3.277V 530 + 531 +* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 532 + 533 +* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 534 + 535 +* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 536 + 537 +* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 538 + 539 +* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 540 + 491 491 ((( 492 492 493 -))) 494 494 495 - (((544 + 496 496 497 497 ))) 498 498 548 +==== 2.3.1.2 Since Firmware v1.2 ==== 499 499 550 + 551 +In this mode, uplink payload includes 91 bytes in total by default. 552 + 553 +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. 554 + 555 + 556 +(% border="2" style="background-color:#ffffcc; color:green; width:520px" %) 557 +|(% style="width:50px" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**2**|(% style="width:50px" %)**1**|(% style="width:30px" %)**2**|(% style="width:50px" %)**2**|(% style="width:50px" %)**2**|(% style="width:50px" %)**4**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:50px" %)**4** 558 +|(% 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 ..... 559 + 560 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 561 + 562 + 563 +[[image:image-20220908154949-1.png]] 564 + 565 + 566 +The payload is ASCII string, representative same HEX: 567 + 568 +**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 + 570 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 571 + 572 +**where:** 573 + 574 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 575 + 576 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 577 + 578 +* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 579 + 580 +* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 581 + 582 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 583 + 584 +* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 585 + 586 +* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 587 + 588 +* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 589 + 590 +* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 591 + 592 +* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 593 + 594 +* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 595 + 596 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 597 + 598 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 599 + 600 + 500 500 === 2.3.2 Device ID === 501 501 603 + 502 502 ((( 503 503 By default, the Device ID equal to the last 6 bytes of IMEI. 504 504 ))) ... ... @@ -505,10 +505,12 @@ 505 505 506 506 ((( 507 507 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 610 + 611 + 508 508 ))) 509 509 510 510 ((( 511 -**Example:** 615 +(% style="color:blue" %)**Example:** 512 512 ))) 513 513 514 514 ((( ... ... @@ -516,13 +516,28 @@ 516 516 ))) 517 517 518 518 ((( 519 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 623 +The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID. 624 + 625 + 520 520 ))) 521 521 628 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 522 522 523 523 631 +By default, the Device ID equal to the last 15 bits of IMEI. 632 + 633 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 634 + 635 + 636 +(% style="color:blue" %)**Example:** 637 + 638 +AT+DEUI=868411056754138 639 + 640 + 641 + 524 524 === 2.3.3 Version Info === 525 525 644 + 526 526 ((( 527 527 These bytes include the hardware and software version. 528 528 ))) ... ... @@ -550,6 +550,7 @@ 550 550 551 551 === 2.3.4 Battery Info === 552 552 672 + 553 553 ((( 554 554 Ex1: 0x0B45 = 2885mV 555 555 ))) ... ... @@ -562,6 +562,7 @@ 562 562 563 563 === 2.3.5 Signal Strength === 564 564 685 + 565 565 ((( 566 566 NB-IoT Network signal Strength. 567 567 ))) ... ... @@ -594,6 +594,7 @@ 594 594 595 595 === 2.3.6 Temperature & Humidity === 596 596 718 + 597 597 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 598 598 599 599 [[image:image-20220709161741-3.png]] ... ... @@ -612,8 +612,9 @@ 612 612 613 613 == 2.4 Downlink Payload == 614 614 615 -By default, NDDS75 prints the downlink payload to console port. 616 616 738 +By default, N95S31B prints the downlink payload to console port. 739 + 617 617 [[image:image-20220709100028-1.png]] 618 618 619 619 ... ... @@ -650,7 +650,7 @@ 650 650 ))) 651 651 652 652 ((( 653 -If payload = 0x04FF, it will reset the DDS75776 +If payload = 0x04FF, it will reset the N95S31B 654 654 ))) 655 655 656 656 ... ... @@ -662,11 +662,74 @@ 662 662 663 663 664 664 665 -== 2.5 BatteryAnalysis==788 +== 2.5 Humidity and Temperature alarm function == 666 666 667 -=== 2.5.1 Battery Type === 668 668 791 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 669 669 793 + 794 +(% style="color:#037691" %)**AT+ SHHUM=min,max** 795 + 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 + 804 + (% style="color:blue" %)**Example:** 805 + 806 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 807 + 808 + 809 +(% style="color:#037691" %)**AT+ SHTEMP=min,max** 810 + 811 +² When min=0, and max≠0, Alarm higher than max 812 + 813 +² When min≠0, and max=0, Alarm lower than min 814 + 815 +² When min≠0 and max≠0, Alarm higher than max or lower than min 816 + 817 + 818 +**~ (% style="color:blue" %)Example:(%%)** 819 + 820 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 821 + 822 + 823 + 824 +== 2.6 Set the number of data to be uploaded and the recording time == 825 + 826 + 827 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 828 + 829 +* (% style="color:#037691" %)**AT+TR=900** (%%)~/~/ The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds) 830 +* (% style="color:#037691" %)**AT+NOUD=8** (%%)~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 831 + 832 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 833 + 834 +[[image:image-20221009001045-1.png||height="726" width="1009"]] 835 + 836 + 837 + 838 +== 2.7 Read or Clear cached data == 839 + 840 + 841 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 842 + 843 +* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 844 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 845 + 846 +[[image:image-20220908163102-2.png]] 847 + 848 + 849 + 850 +== 2.8 Battery Analysis == 851 + 852 + 853 +=== 2.8.1 Battery Type === 854 + 855 + 670 670 ((( 671 671 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. 672 672 ))) ... ... @@ -689,10 +689,11 @@ 689 689 690 690 691 691 692 -=== 2. 5.2 Power consumption Analyze ===878 +=== 2.8.2 Power consumption Analyze === 693 693 880 + 694 694 ((( 695 -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/]]882 +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. 696 696 ))) 697 697 698 698 ((( ... ... @@ -700,8 +700,9 @@ 700 700 ))) 701 701 702 702 703 -=== 2. 5.3 Battery Note ===890 +=== 2.8.3 Battery Note === 704 704 892 + 705 705 ((( 706 706 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. 707 707 ))) ... ... @@ -708,7 +708,7 @@ 708 708 709 709 710 710 711 -=== 2. 5.4 Replace the battery ===899 +=== 2.8.4 Replace the battery === 712 712 713 713 714 714 ((( ... ... @@ -724,6 +724,7 @@ 724 724 725 725 = 3. Access NB-IoT Module = 726 726 915 + 727 727 ((( 728 728 Users can directly access the AT command set of the NB-IoT module. 729 729 ))) ... ... @@ -730,6 +730,8 @@ 730 730 731 731 ((( 732 732 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/]] 922 + 923 + 733 733 ))) 734 734 735 735 [[image:1657333200519-600.png]] ... ... @@ -738,11 +738,13 @@ 738 738 739 739 = 4. Using the AT Commands = 740 740 932 + 741 741 == 4.1 Access AT Commands == 742 742 743 -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/]] 744 744 936 +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]] 745 745 938 + 746 746 AT+<CMD>? : Help on <CMD> 747 747 748 748 AT+<CMD> : Run <CMD> ... ... @@ -782,7 +782,24 @@ 782 782 783 783 AT+SERVADDR : Server Address 784 784 978 +AT+TR : Get or Set record time 785 785 980 +AT+APN : Get or set the APN 981 + 982 +AT+FBAND : Get or Set whether to automatically modify the frequency band 983 + 984 +AT+DNSCFG : Get or Set DNS Server 985 + 986 +AT+GETSENSORVALUE : Returns the current sensor measurement 987 + 988 +AT+NOUD : Get or Set the number of data to be uploaded 989 + 990 +AT+CDP : Read or Clear cached data 991 + 992 +AT+SHTEMP: Get or Set alarm of temp 993 + 994 +AT+SHHUM: Get or Set alarm of moisture 995 + 786 786 (% style="color:#037691" %)**COAP Management** 787 787 788 788 AT+URI : Resource parameters ... ... @@ -816,6 +816,7 @@ 816 816 817 817 = 5. FAQ = 818 818 1029 + 819 819 == 5.1 How to Upgrade Firmware == 820 820 821 821 ... ... @@ -831,7 +831,7 @@ 831 831 832 832 833 833 ((( 834 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 1045 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 835 835 ))) 836 836 ))) 837 837 ... ... @@ -839,6 +839,7 @@ 839 839 840 840 = 6. Trouble Shooting = 841 841 1053 + 842 842 == 6.1 Connection problem when uploading firmware == 843 843 844 844 ... ... @@ -854,6 +854,7 @@ 854 854 855 855 == 6.2 AT Command input doesn't work == 856 856 1069 + 857 857 ((( 858 858 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. 859 859 ... ... @@ -903,5 +903,6 @@ 903 903 904 904 = 9. Support = 905 905 1119 + 906 906 * 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. 907 907 * 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]]
- 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
- image-20221009001045-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +282.9 KB - Content