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-20220908163102-2.png", version {1}
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.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,13 +145,18 @@ 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 151 151 1. Send an uplink packet 152 152 166 + 167 + 168 + 153 153 = 2. Use N95S31B to communicate with IoT Server = 154 154 171 + 155 155 == 2.1 How it works == 156 156 157 157 ... ... @@ -168,7 +168,7 @@ 168 168 169 169 ))) 170 170 171 -[[image:1657 350248151-650.png]]188 +[[image:1657520100595-569.png]] 172 172 173 173 ((( 174 174 ... ... @@ -184,26 +184,49 @@ 184 184 [[image:image-20220709150546-2.png]] 185 185 186 186 204 + 187 187 === 2.2.1 Test Requirement === 188 188 189 189 208 +((( 190 190 To use N95S31B in your city, make sure meet below requirements: 210 +))) 191 191 192 -* Your local operator has already distributed a NB-IoT Network there. 193 -* The local NB-IoT network used the band that N95S31B supports. 194 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 212 +* ((( 213 +Your local operator has already distributed a NB-IoT Network there. 214 +))) 215 +* ((( 216 +The local NB-IoT network used the band that N95S31B supports. 217 +))) 218 +* ((( 219 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 220 +))) 195 195 222 +((( 196 196 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 224 +))) 197 197 226 +((( 198 198 N95S31B supports different communication protocol such as : 228 +))) 199 199 200 200 ((( 201 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 202 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 203 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 204 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 231 +* ((( 232 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 233 +))) 234 +* ((( 235 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 236 +))) 237 +* ((( 238 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 239 +))) 240 +* ((( 241 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 242 +))) 205 205 244 +((( 206 206 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. 246 +))) 207 207 208 208 209 209 ))) ... ... @@ -214,6 +214,7 @@ 214 214 215 215 === 2.2.3 Insert SIM card === 216 216 257 + 217 217 ((( 218 218 Insert the NB-IoT Card get from your provider. 219 219 ))) ... ... @@ -229,14 +229,18 @@ 229 229 230 230 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 231 231 273 + 232 232 ((( 233 233 ((( 234 234 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 + 235 235 ))) 236 236 ))) 237 237 238 238 [[image:1657351312545-300.png]] 239 239 284 + 240 240 **Connection:** 241 241 242 242 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -260,8 +260,9 @@ 260 260 261 261 [[image:1657329814315-101.png]] 262 262 308 + 263 263 ((( 264 -(% 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]]** 265 265 ))) 266 266 267 267 ... ... @@ -268,9 +268,10 @@ 268 268 269 269 === 2.2.5 Use CoAP protocol to uplink data === 270 270 271 -(% 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/]] 272 272 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/]]** 273 273 320 + 274 274 ((( 275 275 **Use below commands:** 276 276 ))) ... ... @@ -309,6 +309,8 @@ 309 309 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 310 310 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 311 311 359 + 360 + 312 312 [[image:1657352391268-297.png]] 313 313 314 314 ... ... @@ -318,6 +318,7 @@ 318 318 319 319 === 2.2.7 Use MQTT protocol to uplink data === 320 320 370 + 321 321 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 322 322 323 323 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink ... ... @@ -328,11 +328,14 @@ 328 328 * (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 329 329 * (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 330 330 381 + 382 + 331 331 [[image:1657352634421-276.png]] 332 332 333 333 334 334 [[image:1657352645687-385.png]] 335 335 388 + 336 336 ((( 337 337 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. 338 338 ))) ... ... @@ -346,11 +346,14 @@ 346 346 347 347 === 2.2.8 Use TCP protocol to uplink data === 348 348 402 + 349 349 This feature is supported since firmware version v110 350 350 351 351 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 352 352 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 353 353 408 + 409 + 354 354 [[image:1657352898400-901.png]] 355 355 356 356 ... ... @@ -360,6 +360,7 @@ 360 360 361 361 === 2.2.9 Change Update Interval === 362 362 419 + 363 363 User can use below command to change the (% style="color:green" %)**uplink interval**. 364 364 365 365 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -373,30 +373,52 @@ 373 373 == 2.3 Uplink Payload == 374 374 375 375 376 -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 +))) 377 377 378 378 438 +((( 379 379 For example: 440 +))) 380 380 381 - (% 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 +))) 382 382 383 383 447 +((( 384 384 The uplink payloads are composed in ASCII String. For example: 449 +))) 385 385 451 +((( 386 386 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 453 +))) 387 387 455 +((( 388 388 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 457 +))) 389 389 390 390 460 +((( 391 391 (% style="color:red" %)**NOTE:** 462 +))) 392 392 393 393 (% style="color:red" %) 394 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 395 -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.** 396 396 397 397 472 + 473 + 474 +))) 475 + 398 398 === 2.3.1 Payload Analyze === 399 399 478 + 400 400 N95S31B uplink payload includes in total 21 bytes 401 401 402 402 ... ... @@ -431,6 +431,8 @@ 431 431 ))) 432 432 433 433 ((( 513 + 514 + 434 434 ((( 435 435 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 436 436 ))) ... ... @@ -463,6 +463,7 @@ 463 463 464 464 === 2.3.2 Device ID === 465 465 547 + 466 466 ((( 467 467 By default, the Device ID equal to the last 6 bytes of IMEI. 468 468 ))) ... ... @@ -488,14 +488,25 @@ 488 488 === 2.3.3 Version Info === 489 489 490 490 573 +((( 491 491 These bytes include the hardware and software version. 575 +))) 492 492 577 +((( 493 493 Higher byte: Specify hardware version: always 0x00 for N95S31B 579 +))) 494 494 581 +((( 495 495 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 583 +))) 496 496 585 +((( 586 + 587 +))) 497 497 589 +((( 498 498 For example: 0x00 6E: this device is N95S31B with firmware version 110. 591 +))) 499 499 500 500 ((( 501 501 ... ... @@ -504,6 +504,7 @@ 504 504 505 505 === 2.3.4 Battery Info === 506 506 600 + 507 507 ((( 508 508 Ex1: 0x0B45 = 2885mV 509 509 ))) ... ... @@ -516,6 +516,7 @@ 516 516 517 517 === 2.3.5 Signal Strength === 518 518 613 + 519 519 ((( 520 520 NB-IoT Network signal Strength. 521 521 ))) ... ... @@ -548,6 +548,7 @@ 548 548 549 549 === 2.3.6 Temperature & Humidity === 550 550 646 + 551 551 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 552 552 553 553 [[image:image-20220709161741-3.png]] ... ... @@ -566,8 +566,9 @@ 566 566 567 567 == 2.4 Downlink Payload == 568 568 569 -By default, NDDS75 prints the downlink payload to console port. 570 570 666 +By default, N95S31B prints the downlink payload to console port. 667 + 571 571 [[image:image-20220709100028-1.png]] 572 572 573 573 ... ... @@ -604,7 +604,7 @@ 604 604 ))) 605 605 606 606 ((( 607 -If payload = 0x04FF, it will reset the DDS75704 +If payload = 0x04FF, it will reset the N95S31B 608 608 ))) 609 609 610 610 ... ... @@ -618,6 +618,7 @@ 618 618 619 619 == 2.5 Battery Analysis == 620 620 718 + 621 621 === 2.5.1 Battery Type === 622 622 623 623 ... ... @@ -645,8 +645,9 @@ 645 645 646 646 === 2.5.2 Power consumption Analyze === 647 647 746 + 648 648 ((( 649 -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. 650 650 ))) 651 651 652 652 ((( ... ... @@ -656,6 +656,7 @@ 656 656 657 657 === 2.5.3 Battery Note === 658 658 758 + 659 659 ((( 660 660 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. 661 661 ))) ... ... @@ -678,6 +678,7 @@ 678 678 679 679 = 3. Access NB-IoT Module = 680 680 781 + 681 681 ((( 682 682 Users can directly access the AT command set of the NB-IoT module. 683 683 ))) ... ... @@ -684,6 +684,8 @@ 684 684 685 685 ((( 686 686 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 + 687 687 ))) 688 688 689 689 [[image:1657333200519-600.png]] ... ... @@ -692,11 +692,13 @@ 692 692 693 693 = 4. Using the AT Commands = 694 694 798 + 695 695 == 4.1 Access AT Commands == 696 696 697 -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/]] 698 698 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]] 699 699 804 + 700 700 AT+<CMD>? : Help on <CMD> 701 701 702 702 AT+<CMD> : Run <CMD> ... ... @@ -770,6 +770,7 @@ 770 770 771 771 = 5. FAQ = 772 772 878 + 773 773 == 5.1 How to Upgrade Firmware == 774 774 775 775 ... ... @@ -784,13 +784,16 @@ 784 784 ((( 785 785 786 786 787 -(% 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.** 788 788 ))) 896 +))) 789 789 790 790 791 791 792 792 = 6. Trouble Shooting = 793 793 902 + 794 794 == 6.1 Connection problem when uploading firmware == 795 795 796 796 ... ... @@ -806,6 +806,7 @@ 806 806 807 807 == 6.2 AT Command input doesn't work == 808 808 918 + 809 809 ((( 810 810 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. 811 811 ... ... @@ -855,5 +855,9 @@ 855 855 856 856 = 9. Support = 857 857 968 + 858 858 * 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. 859 859 * 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
- image-20220908163102-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.David - Size
-
... ... @@ -1,0 +1,1 @@ 1 +29.7 KB - Content