Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Change comment:
Uploaded new attachment "image-20220908154949-1.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 2 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.David - 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 ... ... @@ -78,6 +78,7 @@ 78 78 * Operating Temperature: -40 ~~ 85°C 79 79 80 80 83 + 81 81 (% style="color:#037691" %)**NB-IoT Spec:** 82 82 83 83 * - B1 @H-FDD: 2100MHz ... ... @@ -88,6 +88,7 @@ 88 88 * - B28 @H-FDD: 700MHz 89 89 90 90 94 + 91 91 (% style="color:#037691" %)**Battery:** 92 92 93 93 * Li/SOCI2 un-chargeable battery ... ... @@ -101,6 +101,7 @@ 101 101 102 102 == 1.4 Applications == 103 103 108 + 104 104 * Smart Buildings & Home Automation 105 105 * Logistics and Supply Chain Management 106 106 * Smart Metering ... ... @@ -112,15 +112,20 @@ 112 112 113 113 114 114 115 -== 1.5 Pin Definitions == 116 116 121 +== 1.5 Pin Definitions & Switch == 122 + 123 + 117 117 N95S31B use the mother board from NBSN95 which as below. 118 118 126 + 119 119 [[image:image-20220709144723-1.png]] 120 120 121 121 130 + 122 122 === 1.5.1 Jumper JP2 === 123 123 133 + 124 124 Power on Device when put this jumper. 125 125 126 126 ... ... @@ -127,6 +127,7 @@ 127 127 128 128 === 1.5.2 BOOT MODE / SW1 === 129 129 140 + 130 130 ((( 131 131 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 132 ))) ... ... @@ -139,6 +139,7 @@ 139 139 140 140 === 1.5.3 Reset Button === 141 141 153 + 142 142 Press to reboot the device. 143 143 144 144 ... ... @@ -145,6 +145,7 @@ 145 145 146 146 === 1.5.4 LED === 147 147 160 + 148 148 It will flash: 149 149 150 150 1. When boot the device in flash mode ... ... @@ -155,6 +155,7 @@ 155 155 156 156 = 2. Use N95S31B to communicate with IoT Server = 157 157 171 + 158 158 == 2.1 How it works == 159 159 160 160 ... ... @@ -171,7 +171,7 @@ 171 171 172 172 ))) 173 173 174 -[[image:1657 350248151-650.png]]188 +[[image:1657520100595-569.png]] 175 175 176 176 ((( 177 177 ... ... @@ -187,6 +187,7 @@ 187 187 [[image:image-20220709150546-2.png]] 188 188 189 189 204 + 190 190 === 2.2.1 Test Requirement === 191 191 192 192 ... ... @@ -239,6 +239,7 @@ 239 239 240 240 === 2.2.3 Insert SIM card === 241 241 257 + 242 242 ((( 243 243 Insert the NB-IoT Card get from your provider. 244 244 ))) ... ... @@ -254,14 +254,18 @@ 254 254 255 255 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 256 256 273 + 257 257 ((( 258 258 ((( 259 259 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. 277 + 278 + 260 260 ))) 261 261 ))) 262 262 263 263 [[image:1657351312545-300.png]] 264 264 284 + 265 265 **Connection:** 266 266 267 267 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -285,8 +285,9 @@ 285 285 286 286 [[image:1657329814315-101.png]] 287 287 308 + 288 288 ((( 289 -(% 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/]]310 +(% 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]]** 290 290 ))) 291 291 292 292 ... ... @@ -293,9 +293,10 @@ 293 293 294 294 === 2.2.5 Use CoAP protocol to uplink data === 295 295 296 -(% 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/]] 297 297 318 +(% 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/]]** 298 298 320 + 299 299 ((( 300 300 **Use below commands:** 301 301 ))) ... ... @@ -334,6 +334,8 @@ 334 334 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 335 335 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 336 336 359 + 360 + 337 337 [[image:1657352391268-297.png]] 338 338 339 339 ... ... @@ -343,6 +343,7 @@ 343 343 344 344 === 2.2.7 Use MQTT protocol to uplink data === 345 345 370 + 346 346 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 347 347 348 348 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink ... ... @@ -353,11 +353,14 @@ 353 353 * (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 354 354 * (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 355 355 381 + 382 + 356 356 [[image:1657352634421-276.png]] 357 357 358 358 359 359 [[image:1657352645687-385.png]] 360 360 388 + 361 361 ((( 362 362 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. 363 363 ))) ... ... @@ -371,11 +371,14 @@ 371 371 372 372 === 2.2.8 Use TCP protocol to uplink data === 373 373 402 + 374 374 This feature is supported since firmware version v110 375 375 376 376 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 377 377 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 378 378 408 + 409 + 379 379 [[image:1657352898400-901.png]] 380 380 381 381 ... ... @@ -385,6 +385,7 @@ 385 385 386 386 === 2.2.9 Change Update Interval === 387 387 419 + 388 388 User can use below command to change the (% style="color:green" %)**uplink interval**. 389 389 390 390 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -398,30 +398,52 @@ 398 398 == 2.3 Uplink Payload == 399 399 400 400 401 -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. 433 +((( 434 +N95S31B 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. 435 +))) 402 402 403 403 438 +((( 404 404 For example: 440 +))) 405 405 406 - (% 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. 442 +((( 443 + (% 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. 444 +))) 407 407 408 408 447 +((( 409 409 The uplink payloads are composed in ASCII String. For example: 449 +))) 410 410 451 +((( 411 411 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 453 +))) 412 412 455 +((( 413 413 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 457 +))) 414 414 415 415 460 +((( 416 416 (% style="color:red" %)**NOTE:** 462 +))) 417 417 418 418 (% style="color:red" %) 419 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 420 -1. By default, the device will send an uplink message every 1 hour. 465 +1. ((( 466 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 467 +))) 468 +1. ((( 469 +**By default, the device will send an uplink message every 1 hour.** 421 421 422 422 472 + 473 + 474 +))) 475 + 423 423 === 2.3.1 Payload Analyze === 424 424 478 + 425 425 N95S31B uplink payload includes in total 21 bytes 426 426 427 427 ... ... @@ -456,6 +456,8 @@ 456 456 ))) 457 457 458 458 ((( 513 + 514 + 459 459 ((( 460 460 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 461 461 ))) ... ... @@ -488,6 +488,7 @@ 488 488 489 489 === 2.3.2 Device ID === 490 490 547 + 491 491 ((( 492 492 By default, the Device ID equal to the last 6 bytes of IMEI. 493 493 ))) ... ... @@ -513,14 +513,25 @@ 513 513 === 2.3.3 Version Info === 514 514 515 515 573 +((( 516 516 These bytes include the hardware and software version. 575 +))) 517 517 577 +((( 518 518 Higher byte: Specify hardware version: always 0x00 for N95S31B 579 +))) 519 519 581 +((( 520 520 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 583 +))) 521 521 585 +((( 586 + 587 +))) 522 522 589 +((( 523 523 For example: 0x00 6E: this device is N95S31B with firmware version 110. 591 +))) 524 524 525 525 ((( 526 526 ... ... @@ -529,6 +529,7 @@ 529 529 530 530 === 2.3.4 Battery Info === 531 531 600 + 532 532 ((( 533 533 Ex1: 0x0B45 = 2885mV 534 534 ))) ... ... @@ -541,6 +541,7 @@ 541 541 542 542 === 2.3.5 Signal Strength === 543 543 613 + 544 544 ((( 545 545 NB-IoT Network signal Strength. 546 546 ))) ... ... @@ -573,6 +573,7 @@ 573 573 574 574 === 2.3.6 Temperature & Humidity === 575 575 646 + 576 576 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 577 577 578 578 [[image:image-20220709161741-3.png]] ... ... @@ -591,8 +591,9 @@ 591 591 592 592 == 2.4 Downlink Payload == 593 593 594 -By default, NDDS75 prints the downlink payload to console port. 595 595 666 +By default, N95S31B prints the downlink payload to console port. 667 + 596 596 [[image:image-20220709100028-1.png]] 597 597 598 598 ... ... @@ -629,7 +629,7 @@ 629 629 ))) 630 630 631 631 ((( 632 -If payload = 0x04FF, it will reset the DDS75704 +If payload = 0x04FF, it will reset the N95S31B 633 633 ))) 634 634 635 635 ... ... @@ -643,6 +643,7 @@ 643 643 644 644 == 2.5 Battery Analysis == 645 645 718 + 646 646 === 2.5.1 Battery Type === 647 647 648 648 ... ... @@ -670,8 +670,9 @@ 670 670 671 671 === 2.5.2 Power consumption Analyze === 672 672 746 + 673 673 ((( 674 -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/]]748 +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. 675 675 ))) 676 676 677 677 ((( ... ... @@ -681,6 +681,7 @@ 681 681 682 682 === 2.5.3 Battery Note === 683 683 758 + 684 684 ((( 685 685 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. 686 686 ))) ... ... @@ -703,6 +703,7 @@ 703 703 704 704 = 3. Access NB-IoT Module = 705 705 781 + 706 706 ((( 707 707 Users can directly access the AT command set of the NB-IoT module. 708 708 ))) ... ... @@ -709,6 +709,8 @@ 709 709 710 710 ((( 711 711 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/]] 788 + 789 + 712 712 ))) 713 713 714 714 [[image:1657333200519-600.png]] ... ... @@ -717,11 +717,13 @@ 717 717 718 718 = 4. Using the AT Commands = 719 719 798 + 720 720 == 4.1 Access AT Commands == 721 721 722 -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/]] 723 723 802 +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]] 724 724 804 + 725 725 AT+<CMD>? : Help on <CMD> 726 726 727 727 AT+<CMD> : Run <CMD> ... ... @@ -795,6 +795,7 @@ 795 795 796 796 = 5. FAQ = 797 797 878 + 798 798 == 5.1 How to Upgrade Firmware == 799 799 800 800 ... ... @@ -809,13 +809,16 @@ 809 809 ((( 810 810 811 811 812 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 893 +((( 894 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 813 813 ))) 896 +))) 814 814 815 815 816 816 817 817 = 6. Trouble Shooting = 818 818 902 + 819 819 == 6.1 Connection problem when uploading firmware == 820 820 821 821 ... ... @@ -831,6 +831,7 @@ 831 831 832 832 == 6.2 AT Command input doesn't work == 833 833 918 + 834 834 ((( 835 835 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. 836 836 ... ... @@ -880,5 +880,9 @@ 880 880 881 881 = 9. Support = 882 882 968 + 883 883 * 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. 884 884 * 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]] 971 + 972 + 973 +
- 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