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)
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 ... ... @@ -68,6 +68,7 @@ 68 68 69 69 70 70 73 + 71 71 == 1.3 Specification == 72 72 73 73 ... ... @@ -76,6 +76,8 @@ 76 76 * Supply Voltage: 2.1v ~~ 3.6v 77 77 * Operating Temperature: -40 ~~ 85°C 78 78 82 + 83 + 79 79 (% style="color:#037691" %)**NB-IoT Spec:** 80 80 81 81 * - B1 @H-FDD: 2100MHz ... ... @@ -85,6 +85,8 @@ 85 85 * - B20 @H-FDD: 800MHz 86 86 * - B28 @H-FDD: 700MHz 87 87 93 + 94 + 88 88 (% style="color:#037691" %)**Battery:** 89 89 90 90 * Li/SOCI2 un-chargeable battery ... ... @@ -95,8 +95,10 @@ 95 95 96 96 97 97 105 + 98 98 == 1.4 Applications == 99 99 108 + 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 120 + 111 111 == 1.5 Pin Definitions & Switch == 112 112 123 + 113 113 N95S31B use the mother board from NBSN95 which as below. 114 114 126 + 115 115 [[image:image-20220709144723-1.png]] 116 116 117 117 130 + 118 118 === 1.5.1 Jumper JP2 === 119 119 133 + 120 120 Power on Device when put this jumper. 121 121 122 122 ... ... @@ -123,6 +123,7 @@ 123 123 124 124 === 1.5.2 BOOT MODE / SW1 === 125 125 140 + 126 126 ((( 127 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. 128 128 ))) ... ... @@ -135,6 +135,7 @@ 135 135 136 136 === 1.5.3 Reset Button === 137 137 153 + 138 138 Press to reboot the device. 139 139 140 140 ... ... @@ -141,6 +141,7 @@ 141 141 142 142 === 1.5.4 LED === 143 143 160 + 144 144 It will flash: 145 145 146 146 1. When boot the device in flash mode ... ... @@ -147,8 +147,11 @@ 147 147 1. Send an uplink packet 148 148 149 149 167 + 168 + 150 150 = 2. Use N95S31B to communicate with IoT Server = 151 151 171 + 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 204 + 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 257 + 236 236 ((( 237 237 Insert the NB-IoT Card get from your provider. 238 238 ))) ... ... @@ -248,14 +248,18 @@ 248 248 249 249 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 250 250 273 + 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. 277 + 278 + 254 254 ))) 255 255 ))) 256 256 257 257 [[image:1657351312545-300.png]] 258 258 284 + 259 259 **Connection:** 260 260 261 261 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -279,8 +279,9 @@ 279 279 280 280 [[image:1657329814315-101.png]] 281 281 308 + 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/]]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]]** 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 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/]]** 292 292 320 + 293 293 ((( 294 294 **Use below commands:** 295 295 ))) ... ... @@ -328,6 +328,8 @@ 328 328 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 329 329 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 330 330 359 + 360 + 331 331 [[image:1657352391268-297.png]] 332 332 333 333 ... ... @@ -337,6 +337,7 @@ 337 337 338 338 === 2.2.7 Use MQTT protocol to uplink data === 339 339 370 + 340 340 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 341 341 342 342 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink ... ... @@ -347,11 +347,14 @@ 347 347 * (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 348 348 * (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 349 349 381 + 382 + 350 350 [[image:1657352634421-276.png]] 351 351 352 352 353 353 [[image:1657352645687-385.png]] 354 354 388 + 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,11 +365,14 @@ 365 365 366 366 === 2.2.8 Use TCP protocol to uplink data === 367 367 402 + 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 371 371 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 372 372 408 + 409 + 373 373 [[image:1657352898400-901.png]] 374 374 375 375 ... ... @@ -379,6 +379,7 @@ 379 379 380 380 === 2.2.9 Change Update Interval === 381 381 419 + 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 ... ... @@ -393,7 +393,7 @@ 393 393 394 394 395 395 ((( 396 -N BSN95434 +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. 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.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. 406 406 ))) 407 407 408 408 ... ... @@ -425,14 +425,19 @@ 425 425 426 426 (% style="color:red" %) 427 427 1. ((( 428 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 466 +**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. 469 +**By default, the device will send an uplink message every 1 hour.** 470 + 471 + 472 + 473 + 432 432 ))) 433 433 434 434 === 2.3.1 Payload Analyze === 435 435 478 + 436 436 N95S31B uplink payload includes in total 21 bytes 437 437 438 438 ... ... @@ -467,6 +467,8 @@ 467 467 ))) 468 468 469 469 ((( 513 + 514 + 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 ))) ... ... @@ -499,6 +499,7 @@ 499 499 500 500 === 2.3.2 Device ID === 501 501 547 + 502 502 ((( 503 503 By default, the Device ID equal to the last 6 bytes of IMEI. 504 504 ))) ... ... @@ -523,6 +523,7 @@ 523 523 524 524 === 2.3.3 Version Info === 525 525 572 + 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 600 + 553 553 ((( 554 554 Ex1: 0x0B45 = 2885mV 555 555 ))) ... ... @@ -562,6 +562,7 @@ 562 562 563 563 === 2.3.5 Signal Strength === 564 564 613 + 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 646 + 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 666 +By default, N95S31B prints the downlink payload to console port. 667 + 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 DDS75704 +If payload = 0x04FF, it will reset the N95S31B 654 654 ))) 655 655 656 656 ... ... @@ -664,6 +664,7 @@ 664 664 665 665 == 2.5 Battery Analysis == 666 666 718 + 667 667 === 2.5.1 Battery Type === 668 668 669 669 ... ... @@ -691,8 +691,9 @@ 691 691 692 692 === 2.5.2 Power consumption Analyze === 693 693 746 + 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/]]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. 696 696 ))) 697 697 698 698 ((( ... ... @@ -702,6 +702,7 @@ 702 702 703 703 === 2.5.3 Battery Note === 704 704 758 + 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 ))) ... ... @@ -724,6 +724,7 @@ 724 724 725 725 = 3. Access NB-IoT Module = 726 726 781 + 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/]] 788 + 789 + 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 798 + 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 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]] 745 745 804 + 746 746 AT+<CMD>? : Help on <CMD> 747 747 748 748 AT+<CMD> : Run <CMD> ... ... @@ -816,6 +816,7 @@ 816 816 817 817 = 5. FAQ = 818 818 878 + 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. 894 +(% 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 902 + 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 918 + 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,9 @@ 903 903 904 904 = 9. Support = 905 905 968 + 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]] 971 + 972 + 973 +