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 ... ... @@ -66,7 +66,6 @@ 66 66 * Micro SIM card slot for NB-IoT SIM 67 67 * 8500mAh Battery for long term use 68 68 69 - 70 70 == 1.3 Specification == 71 71 72 72 ... ... @@ -92,9 +92,9 @@ 92 92 * Max continuously current: 130mA 93 93 * Max boost current: 2A, 1 second 94 94 95 - 96 96 == 1.4 Applications == 97 97 98 + 98 98 * Smart Buildings & Home Automation 99 99 * Logistics and Supply Chain Management 100 100 * Smart Metering ... ... @@ -106,15 +106,20 @@ 106 106 107 107 108 108 110 + 109 109 == 1.5 Pin Definitions & Switch == 110 110 113 + 111 111 N95S31B use the mother board from NBSN95 which as below. 112 112 116 + 113 113 [[image:image-20220709144723-1.png]] 114 114 115 115 120 + 116 116 === 1.5.1 Jumper JP2 === 117 117 123 + 118 118 Power on Device when put this jumper. 119 119 120 120 ... ... @@ -121,12 +121,13 @@ 121 121 122 122 === 1.5.2 BOOT MODE / SW1 === 123 123 130 + 124 124 ((( 125 -1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. 132 +**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. 126 126 ))) 127 127 128 128 ((( 129 -2) Flash: work mode, device starts to work and send out console output for further debug 136 +**2) Flash:** work mode, device starts to work and send out console output for further debug 130 130 ))) 131 131 132 132 ... ... @@ -133,6 +133,7 @@ 133 133 134 134 === 1.5.3 Reset Button === 135 135 143 + 136 136 Press to reboot the device. 137 137 138 138 ... ... @@ -139,14 +139,18 @@ 139 139 140 140 === 1.5.4 LED === 141 141 150 + 142 142 It will flash: 143 143 144 -1. When boot the device in flash mode 145 -1. Send an uplink packet 153 +1. When boot the device in flash mode 146 146 155 +2. Send an uplink packet 147 147 157 + 158 + 148 148 = 2. Use N95S31B to communicate with IoT Server = 149 149 161 + 150 150 == 2.1 How it works == 151 151 152 152 ... ... @@ -163,7 +163,7 @@ 163 163 164 164 ))) 165 165 166 -[[image:1657 350248151-650.png]]178 +[[image:1657520100595-569.png]] 167 167 168 168 ((( 169 169 ... ... @@ -179,6 +179,7 @@ 179 179 [[image:image-20220709150546-2.png]] 180 180 181 181 194 + 182 182 === 2.2.1 Test Requirement === 183 183 184 184 ... ... @@ -231,6 +231,7 @@ 231 231 232 232 === 2.2.3 Insert SIM card === 233 233 247 + 234 234 ((( 235 235 Insert the NB-IoT Card get from your provider. 236 236 ))) ... ... @@ -246,23 +246,27 @@ 246 246 247 247 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 248 248 263 + 249 249 ((( 250 250 ((( 251 251 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. 267 + 268 + 252 252 ))) 253 253 ))) 254 254 255 255 [[image:1657351312545-300.png]] 256 256 257 -**Connection:** 258 258 259 - background-color:yellow" %)USB TTL GND <~-~-~-~-> GND275 +(% style="color:blue" %)**Connection:** 260 260 261 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~->UART_RXD277 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 262 262 263 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD279 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 264 264 281 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 265 265 283 + 266 266 In the PC, use below serial tool settings: 267 267 268 268 * Baud: (% style="color:green" %)**9600** ... ... @@ -277,8 +277,9 @@ 277 277 278 278 [[image:1657329814315-101.png]] 279 279 298 + 280 280 ((( 281 -(% 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/]]300 +(% 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]]** 282 282 ))) 283 283 284 284 ... ... @@ -285,9 +285,10 @@ 285 285 286 286 === 2.2.5 Use CoAP protocol to uplink data === 287 287 288 -(% 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/]] 289 289 308 +(% 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/]]** 290 290 310 + 291 291 ((( 292 292 **Use below commands:** 293 293 ))) ... ... @@ -296,10 +296,10 @@ 296 296 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 297 297 ))) 298 298 * ((( 299 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 319 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 300 300 ))) 301 301 * ((( 302 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 322 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 303 303 ))) 304 304 305 305 ((( ... ... @@ -335,15 +335,16 @@ 335 335 336 336 === 2.2.7 Use MQTT protocol to uplink data === 337 337 358 + 338 338 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 339 339 340 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 341 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 342 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 343 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 344 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 345 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 346 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 361 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 362 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 363 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 364 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 365 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 366 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/ Set the sending topic of MQTT 367 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/ Set the subscription topic of MQTT 347 347 348 348 [[image:1657352634421-276.png]] 349 349 ... ... @@ -350,6 +350,7 @@ 350 350 351 351 [[image:1657352645687-385.png]] 352 352 374 + 353 353 ((( 354 354 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. 355 355 ))) ... ... @@ -363,6 +363,7 @@ 363 363 364 364 === 2.2.8 Use TCP protocol to uplink data === 365 365 388 + 366 366 This feature is supported since firmware version v110 367 367 368 368 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -377,6 +377,7 @@ 377 377 378 378 === 2.2.9 Change Update Interval === 379 379 403 + 380 380 User can use below command to change the (% style="color:green" %)**uplink interval**. 381 381 382 382 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -385,13 +385,21 @@ 385 385 386 386 ))) 387 387 412 +((( 413 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 414 +))) 388 388 416 +((( 417 +(% 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).** 418 +))) 389 389 420 + 421 + 390 390 == 2.3 Uplink Payload == 391 391 392 392 393 393 ((( 394 -N BSN95426 +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. 395 395 ))) 396 396 397 397 ... ... @@ -400,7 +400,7 @@ 400 400 ))) 401 401 402 402 ((( 403 - (% 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.435 + (% 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. 404 404 ))) 405 405 406 406 ... ... @@ -423,23 +423,30 @@ 423 423 424 424 (% style="color:red" %) 425 425 1. ((( 426 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 458 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 427 427 ))) 428 428 1. ((( 429 -By default, the device will send an uplink message every 1 hour. 430 -))) 461 +**By default, the device will send an uplink message every 1 hour.** 431 431 432 432 464 + 465 + 466 +))) 467 + 433 433 === 2.3.1 Payload Analyze === 434 434 470 + 471 +==== 2.3.1.1 Before Firmware v1.2 ==== 472 + 473 + 435 435 N95S31B uplink payload includes in total 21 bytes 436 436 437 437 438 -(% border="1" cellspacing=" 10" style="background-color:#ffffcc; color:green; width:520px" %)439 -|=(% style="width: 60px;" %)(((477 +(% border="1.5" cellspacing="0" style="background-color:#ffffcc; color:green; width:520px" %) 478 +|=(% scope="row" style="width: 50px;" %)((( 440 440 **Size(bytes)** 441 -)))|=(% 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**442 -|(% 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" %)(((480 +)))|=(% 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** 481 +|=(% 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" %)((( 443 443 ((( 444 444 Reserve/ Same as NBSN95 CFGMOD=1 445 445 ))) ... ... @@ -447,7 +447,7 @@ 447 447 ((( 448 448 No function here. 449 449 ))) 450 -)))|(% style="width: 77px" %)(((489 +)))|(% style="width:102px" %)((( 451 451 ((( 452 452 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 453 453 ))) ... ... @@ -455,7 +455,7 @@ 455 455 ((( 456 456 By SHT31 457 457 ))) 458 -)))|(% style="width:8 0px" %)(((497 +)))|(% style="width:81px" %)((( 459 459 ((( 460 460 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 461 461 ))) ... ... @@ -466,6 +466,8 @@ 466 466 ))) 467 467 468 468 ((( 508 + 509 + 469 469 ((( 470 470 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 471 471 ))) ... ... @@ -475,29 +475,88 @@ 475 475 [[image:1657354294009-643.png]] 476 476 477 477 478 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:519 +The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186** 479 479 480 -* Device ID: 0x724031607457 = 724031607457 481 -* Version: 0x006e=110=1.1.0 521 +**where:** 482 482 483 -* BAT: 0x0ccd = 3277 mV = 3.277V 484 -* Signal: 0x1b = 27 485 -* Model: 0x01 = 1 486 -* 0x00dc000ccc= reserve, ignore in N95S31B 487 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 488 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 523 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 489 489 525 +* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 526 + 527 +* (% style="color:#037691" %)**BAT:** (%%) 0x0ccd = 3277 mV = 3.277V 528 + 529 +* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 530 + 531 +* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 532 + 533 +* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 534 + 535 +* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 536 + 537 +* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 538 + 490 490 ((( 491 491 492 -))) 493 493 494 - (((542 + 495 495 496 496 ))) 497 497 546 +==== 2.3.1.2 Since Firmware v1.2 ==== 498 498 548 + 549 +In this mode, uplink payload includes 91 bytes in total by default. 550 + 551 +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. 552 + 553 + 554 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 555 +|=(% scope="row" 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** 556 +|=(% 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 ..... 557 + 558 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 559 + 560 + 561 +[[image:image-20220908154949-1.png]] 562 + 563 + 564 +The payload is ASCII string, representative same HEX: 565 + 566 +**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__ ** 567 + 568 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 569 + 570 +**where:** 571 + 572 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 573 + 574 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 575 + 576 +* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 577 + 578 +* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 579 + 580 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 581 + 582 +* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 583 + 584 +* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 585 + 586 +* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 587 + 588 +* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 589 + 590 +* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 591 + 592 +* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 593 + 594 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 595 + 596 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 597 + 499 499 === 2.3.2 Device ID === 500 500 600 + 501 501 ((( 502 502 By default, the Device ID equal to the last 6 bytes of IMEI. 503 503 ))) ... ... @@ -504,10 +504,12 @@ 504 504 505 505 ((( 506 506 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 607 + 608 + 507 507 ))) 508 508 509 509 ((( 510 -**Example:** 612 +(% style="color:blue" %)**Example:** 511 511 ))) 512 512 513 513 ((( ... ... @@ -515,13 +515,28 @@ 515 515 ))) 516 516 517 517 ((( 518 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 620 +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. 621 + 622 + 519 519 ))) 520 520 625 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 521 521 522 522 628 +By default, the Device ID equal to the last 15 bits of IMEI. 629 + 630 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 631 + 632 + 633 +(% style="color:blue" %)**Example:** 634 + 635 +AT+DEUI=868411056754138 636 + 637 + 638 + 523 523 === 2.3.3 Version Info === 524 524 641 + 525 525 ((( 526 526 These bytes include the hardware and software version. 527 527 ))) ... ... @@ -549,6 +549,7 @@ 549 549 550 550 === 2.3.4 Battery Info === 551 551 669 + 552 552 ((( 553 553 Ex1: 0x0B45 = 2885mV 554 554 ))) ... ... @@ -561,6 +561,7 @@ 561 561 562 562 === 2.3.5 Signal Strength === 563 563 682 + 564 564 ((( 565 565 NB-IoT Network signal Strength. 566 566 ))) ... ... @@ -593,6 +593,7 @@ 593 593 594 594 === 2.3.6 Temperature & Humidity === 595 595 715 + 596 596 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 597 597 598 598 [[image:image-20220709161741-3.png]] ... ... @@ -611,8 +611,9 @@ 611 611 612 612 == 2.4 Downlink Payload == 613 613 614 -By default, NDDS75 prints the downlink payload to console port. 615 615 735 +By default, N95S31B prints the downlink payload to console port. 736 + 616 616 [[image:image-20220709100028-1.png]] 617 617 618 618 ... ... @@ -649,7 +649,7 @@ 649 649 ))) 650 650 651 651 ((( 652 -If payload = 0x04FF, it will reset the DDS75773 +If payload = 0x04FF, it will reset the N95S31B 653 653 ))) 654 654 655 655 ... ... @@ -661,11 +661,74 @@ 661 661 662 662 663 663 664 -== 2.5 BatteryAnalysis==785 +== 2.5 Humidity and Temperature alarm function == 665 665 666 -=== 2.5.1 Battery Type === 667 667 788 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 668 668 790 + 791 +(% style="color:#037691" %)**AT+ SHHUM=min,max** 792 + 793 + 794 +² When min=0, and max≠0, Alarm higher than max 795 + 796 +² When min≠0, and max=0, Alarm lower than min 797 + 798 +² When min≠0 and max≠0, Alarm higher than max or lower than min 799 + 800 + 801 + (% style="color:blue" %)**Example:** 802 + 803 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 804 + 805 + 806 +(% style="color:#037691" %)**AT+ SHTEMP=min,max** 807 + 808 +² When min=0, and max≠0, Alarm higher than max 809 + 810 +² When min≠0, and max=0, Alarm lower than min 811 + 812 +² When min≠0 and max≠0, Alarm higher than max or lower than min 813 + 814 + 815 +**~ (% style="color:blue" %)Example:(%%)** 816 + 817 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 818 + 819 + 820 + 821 +== 2.6 Set the number of data to be uploaded and the recording time == 822 + 823 + 824 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 825 + 826 +* (% 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) 827 +* (% 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. 828 + 829 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 830 + 831 +[[image:image-20221009001045-1.png||height="726" width="1009"]] 832 + 833 + 834 + 835 +== 2.7 Read or Clear cached data == 836 + 837 + 838 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 839 + 840 +* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 841 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 842 + 843 +[[image:image-20220908163102-2.png]] 844 + 845 + 846 + 847 +== 2.8 Battery Analysis == 848 + 849 + 850 +=== 2.8.1 Battery Type === 851 + 852 + 669 669 ((( 670 670 The N95S31B battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter. 671 671 ))) ... ... @@ -688,10 +688,11 @@ 688 688 689 689 690 690 691 -=== 2. 5.2 Power consumption Analyze ===875 +=== 2.8.2 Power consumption Analyze === 692 692 877 + 693 693 ((( 694 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]879 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project. 695 695 ))) 696 696 697 697 ((( ... ... @@ -699,8 +699,9 @@ 699 699 ))) 700 700 701 701 702 -=== 2. 5.3 Battery Note ===887 +=== 2.8.3 Battery Note === 703 703 889 + 704 704 ((( 705 705 The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to uplink data, then the battery life may be decreased. 706 706 ))) ... ... @@ -707,7 +707,7 @@ 707 707 708 708 709 709 710 -=== 2. 5.4 Replace the battery ===896 +=== 2.8.4 Replace the battery === 711 711 712 712 713 713 ((( ... ... @@ -723,6 +723,7 @@ 723 723 724 724 = 3. Access NB-IoT Module = 725 725 912 + 726 726 ((( 727 727 Users can directly access the AT command set of the NB-IoT module. 728 728 ))) ... ... @@ -729,6 +729,8 @@ 729 729 730 730 ((( 731 731 The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 919 + 920 + 732 732 ))) 733 733 734 734 [[image:1657333200519-600.png]] ... ... @@ -737,11 +737,13 @@ 737 737 738 738 = 4. Using the AT Commands = 739 739 929 + 740 740 == 4.1 Access AT Commands == 741 741 742 -See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]] 743 743 933 +See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]] 744 744 935 + 745 745 AT+<CMD>? : Help on <CMD> 746 746 747 747 AT+<CMD> : Run <CMD> ... ... @@ -781,7 +781,24 @@ 781 781 782 782 AT+SERVADDR : Server Address 783 783 975 +AT+TR : Get or Set record time 784 784 977 +AT+APN : Get or set the APN 978 + 979 +AT+FBAND : Get or Set whether to automatically modify the frequency band 980 + 981 +AT+DNSCFG : Get or Set DNS Server 982 + 983 +AT+GETSENSORVALUE : Returns the current sensor measurement 984 + 985 +AT+NOUD : Get or Set the number of data to be uploaded 986 + 987 +AT+CDP : Read or Clear cached data 988 + 989 +AT+SHTEMP: Get or Set alarm of temp 990 + 991 +AT+SHHUM: Get or Set alarm of moisture 992 + 785 785 (% style="color:#037691" %)**COAP Management** 786 786 787 787 AT+URI : Resource parameters ... ... @@ -815,6 +815,7 @@ 815 815 816 816 = 5. FAQ = 817 817 1026 + 818 818 == 5.1 How to Upgrade Firmware == 819 819 820 820 ... ... @@ -830,7 +830,7 @@ 830 830 831 831 832 832 ((( 833 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 1042 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 834 834 ))) 835 835 ))) 836 836 ... ... @@ -838,6 +838,7 @@ 838 838 839 839 = 6. Trouble Shooting = 840 840 1050 + 841 841 == 6.1 Connection problem when uploading firmware == 842 842 843 843 ... ... @@ -853,6 +853,7 @@ 853 853 854 854 == 6.2 AT Command input doesn't work == 855 855 1066 + 856 856 ((( 857 857 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. 858 858 ... ... @@ -902,5 +902,6 @@ 902 902 903 903 = 9. Support = 904 904 1116 + 905 905 * 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. 906 906 * 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