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, 2 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -9,6 +9,7 @@ 9 9 10 10 **Table of Contents:** 11 11 12 +{{toc/}} 12 12 13 13 14 14 ... ... @@ -16,21 +16,35 @@ 16 16 17 17 = 1. Introduction = 18 18 20 + 19 19 == 1.1 What is N95S31B NB-IoT Sensor Node == 20 20 21 21 ((( 22 22 23 23 26 +((( 24 24 The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*. 28 +))) 25 25 30 +((( 26 26 The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use. 32 +))) 27 27 34 +((( 28 28 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 36 +))) 29 29 38 +((( 30 30 N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report). 40 +))) 31 31 42 +((( 43 + 44 +))) 32 32 46 +((( 33 33 ~* make sure you have NB-IoT coverage locally. 48 +))) 34 34 35 35 36 36 ))) ... ... @@ -54,6 +54,8 @@ 54 54 * 8500mAh Battery for long term use 55 55 56 56 72 + 73 + 57 57 == 1.3 Specification == 58 58 59 59 ... ... @@ -62,6 +62,8 @@ 62 62 * Supply Voltage: 2.1v ~~ 3.6v 63 63 * Operating Temperature: -40 ~~ 85°C 64 64 82 + 83 + 65 65 (% style="color:#037691" %)**NB-IoT Spec:** 66 66 67 67 * - B1 @H-FDD: 2100MHz ... ... @@ -71,9 +71,10 @@ 71 71 * - B20 @H-FDD: 800MHz 72 72 * - B28 @H-FDD: 700MHz 73 73 74 -(% style="color:#037691" %)**Battery:** 75 75 76 76 95 +(% style="color:#037691" %)**Battery:** 96 + 77 77 * Li/SOCI2 un-chargeable battery 78 78 * Capacity: 8500mAh 79 79 * Self Discharge: <1% / Year @ 25°C ... ... @@ -81,8 +81,11 @@ 81 81 * Max boost current: 2A, 1 second 82 82 83 83 104 + 105 + 84 84 == 1.4 Applications == 85 85 108 + 86 86 * Smart Buildings & Home Automation 87 87 * Logistics and Supply Chain Management 88 88 * Smart Metering ... ... @@ -94,15 +94,20 @@ 94 94 95 95 96 96 97 -== 1.5 Pin Definitions == 98 98 121 +== 1.5 Pin Definitions & Switch == 122 + 123 + 99 99 N95S31B use the mother board from NBSN95 which as below. 100 100 126 + 101 101 [[image:image-20220709144723-1.png]] 102 102 103 103 130 + 104 104 === 1.5.1 Jumper JP2 === 105 105 133 + 106 106 Power on Device when put this jumper. 107 107 108 108 ... ... @@ -109,14 +109,20 @@ 109 109 110 110 === 1.5.2 BOOT MODE / SW1 === 111 111 140 + 141 +((( 112 112 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. 143 +))) 113 113 145 +((( 114 114 2) Flash: work mode, device starts to work and send out console output for further debug 147 +))) 115 115 116 116 117 117 118 118 === 1.5.3 Reset Button === 119 119 153 + 120 120 Press to reboot the device. 121 121 122 122 ... ... @@ -123,6 +123,7 @@ 123 123 124 124 === 1.5.4 LED === 125 125 160 + 126 126 It will flash: 127 127 128 128 1. When boot the device in flash mode ... ... @@ -130,8 +130,10 @@ 130 130 131 131 132 132 168 + 133 133 = 2. Use N95S31B to communicate with IoT Server = 134 134 171 + 135 135 == 2.1 How it works == 136 136 137 137 ... ... @@ -148,7 +148,7 @@ 148 148 149 149 ))) 150 150 151 -[[image:1657 350248151-650.png]]188 +[[image:1657520100595-569.png]] 152 152 153 153 ((( 154 154 ... ... @@ -164,26 +164,49 @@ 164 164 [[image:image-20220709150546-2.png]] 165 165 166 166 204 + 167 167 === 2.2.1 Test Requirement === 168 168 169 169 208 +((( 170 170 To use N95S31B in your city, make sure meet below requirements: 210 +))) 171 171 172 -* Your local operator has already distributed a NB-IoT Network there. 173 -* The local NB-IoT network used the band that N95S31B supports. 174 -* 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 +))) 175 175 222 +((( 176 176 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 224 +))) 177 177 226 +((( 178 178 N95S31B supports different communication protocol such as : 228 +))) 179 179 180 180 ((( 181 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 182 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 183 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 184 -* 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 +))) 185 185 244 +((( 186 186 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 +))) 187 187 188 188 189 189 ))) ... ... @@ -194,6 +194,7 @@ 194 194 195 195 === 2.2.3 Insert SIM card === 196 196 257 + 197 197 ((( 198 198 Insert the NB-IoT Card get from your provider. 199 199 ))) ... ... @@ -209,14 +209,18 @@ 209 209 210 210 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 211 211 273 + 212 212 ((( 213 213 ((( 214 214 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 + 215 215 ))) 216 216 ))) 217 217 218 218 [[image:1657351312545-300.png]] 219 219 284 + 220 220 **Connection:** 221 221 222 222 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -240,8 +240,9 @@ 240 240 241 241 [[image:1657329814315-101.png]] 242 242 308 + 243 243 ((( 244 -(% 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]]** 245 245 ))) 246 246 247 247 ... ... @@ -248,9 +248,10 @@ 248 248 249 249 === 2.2.5 Use CoAP protocol to uplink data === 250 250 251 -(% 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/]] 252 252 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/]]** 253 253 320 + 254 254 ((( 255 255 **Use below commands:** 256 256 ))) ... ... @@ -289,6 +289,8 @@ 289 289 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 290 290 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 291 291 359 + 360 + 292 292 [[image:1657352391268-297.png]] 293 293 294 294 ... ... @@ -298,6 +298,7 @@ 298 298 299 299 === 2.2.7 Use MQTT protocol to uplink data === 300 300 370 + 301 301 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 302 302 303 303 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink ... ... @@ -308,11 +308,14 @@ 308 308 * (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 309 309 * (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 310 310 381 + 382 + 311 311 [[image:1657352634421-276.png]] 312 312 313 313 314 314 [[image:1657352645687-385.png]] 315 315 388 + 316 316 ((( 317 317 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. 318 318 ))) ... ... @@ -326,11 +326,14 @@ 326 326 327 327 === 2.2.8 Use TCP protocol to uplink data === 328 328 402 + 329 329 This feature is supported since firmware version v110 330 330 331 331 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 332 332 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 333 333 408 + 409 + 334 334 [[image:1657352898400-901.png]] 335 335 336 336 ... ... @@ -340,6 +340,7 @@ 340 340 341 341 === 2.2.9 Change Update Interval === 342 342 419 + 343 343 User can use below command to change the (% style="color:green" %)**uplink interval**. 344 344 345 345 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -353,54 +353,88 @@ 353 353 == 2.3 Uplink Payload == 354 354 355 355 356 -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 +))) 357 357 358 358 438 +((( 359 359 For example: 440 +))) 360 360 361 - (% 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 +))) 362 362 363 363 447 +((( 364 364 The uplink payloads are composed in ASCII String. For example: 449 +))) 365 365 451 +((( 366 366 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 453 +))) 367 367 455 +((( 368 368 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 457 +))) 369 369 370 370 460 +((( 371 371 (% style="color:red" %)**NOTE:** 462 +))) 372 372 373 373 (% style="color:red" %) 374 -1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]]. 375 -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.** 376 376 377 377 378 378 473 + 474 +))) 379 379 380 380 === 2.3.1 Payload Analyze === 381 381 478 + 382 382 N95S31B uplink payload includes in total 21 bytes 383 383 384 384 385 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width: 440px" %)482 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 386 386 |=(% style="width: 60px;" %)((( 387 387 **Size(bytes)** 388 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1** 389 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)((( 485 +)))|=(% 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** 486 +|(% 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" %)((( 487 +((( 390 390 Reserve/ Same as NBSN95 CFGMOD=1 489 +))) 391 391 491 +((( 392 392 No function here. 493 +))) 393 393 )))|(% style="width:77px" %)((( 394 -[[Temperature >>||anchor="H2.4.5A0Distance"]] 495 +((( 496 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 497 +))) 395 395 499 +((( 396 396 By SHT31 501 +))) 397 397 )))|(% style="width:80px" %)((( 398 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 503 +((( 504 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 505 +))) 399 399 507 +((( 400 400 By SHT31 401 401 ))) 510 +))) 402 402 403 403 ((( 513 + 514 + 404 404 ((( 405 405 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 406 406 ))) ... ... @@ -409,42 +409,30 @@ 409 409 410 410 [[image:1657354294009-643.png]] 411 411 412 -((( 413 -The payload is ASCII string, representative same HEX: 414 -))) 415 415 416 -((( 417 -0x72403155615900640c6c19029200 where: 418 -))) 524 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 419 419 420 -* ((( 421 -Device ID: 0x724031556159 = 724031556159 422 -))) 423 -* ((( 424 -Version: 0x0064=100=1.0.0 425 -))) 526 +* Device ID: 0x724031607457 = 724031607457 527 +* Version: 0x006e=110=1.1.0 426 426 427 -* ((( 428 -BAT: 0x0c6c = 3180 mV = 3.180V 529 +* BAT: 0x0ccd = 3277 mV = 3.277V 530 +* Signal: 0x1b = 27 531 +* Model: 0x01 = 1 532 +* 0x00dc000ccc= reserve, ignore in N95S31B 533 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 534 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 535 + 536 +((( 537 + 429 429 ))) 430 -* ((( 431 -Signal: 0x19 = 25 432 -))) 433 -* ((( 434 -Distance: 0x0292= 658 mm 435 -))) 436 -* ((( 437 -Interrupt: 0x00 = 0 438 438 439 - 440 - 540 +((( 441 441 442 442 ))) 443 443 444 -== 2.4 Payload Explanation and Sensor Interface == 445 445 545 +=== 2.3.2 Device ID === 446 446 447 -=== 2.4.1 Device ID === 448 448 449 449 ((( 450 450 By default, the Device ID equal to the last 6 bytes of IMEI. ... ... @@ -468,143 +468,104 @@ 468 468 469 469 470 470 471 -=== 2. 4.2Version Info ===570 +=== 2.3.3 Version Info === 472 472 473 -((( 474 -Specify the software version: 0x64=100, means firmware version 1.00. 475 -))) 476 476 477 477 ((( 478 - Forexample:0x00 64 :thisdeviceis NDDS75 withfirmware version1.0.0.574 +These bytes include the hardware and software version. 479 479 ))) 480 480 481 - 482 - 483 -=== 2.4.3 Battery Info === 484 - 485 485 ((( 486 - Ex1: 0x0B45=2885mV578 +Higher byte: Specify hardware version: always 0x00 for N95S31B 487 487 ))) 488 488 489 489 ((( 490 - Ex2: 0x0B49=2889mV582 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 491 491 ))) 492 492 493 - 494 - 495 -=== 2.4.4 Signal Strength === 496 - 497 497 ((( 498 - NB-IoTNetwork signal Strength.586 + 499 499 ))) 500 500 501 501 ((( 502 - **Ex1: 0x1d=29**590 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 503 503 ))) 504 504 505 505 ((( 506 - (%style="color:blue" %)**0**(%%) -113dBm or less594 + 507 507 ))) 508 508 509 -((( 510 -(% style="color:blue" %)**1**(%%) -111dBm 511 -))) 512 512 513 -((( 514 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 515 -))) 598 +=== 2.3.4 Battery Info === 516 516 600 + 517 517 ((( 518 - (% style="color:blue"%)**31**(%%)-51dBmor greater602 +Ex1: 0x0B45 = 2885mV 519 519 ))) 520 520 521 521 ((( 522 - (% style="color:blue"%)**99**(%%)Not known or not detectable606 +Ex2: 0x0B49 = 2889mV 523 523 ))) 524 524 525 525 526 526 527 -=== 2. 4.5Distance ===611 +=== 2.3.5 Signal Strength === 528 528 529 -Get the distance. Flat object range 280mm - 7500mm. 530 530 531 531 ((( 532 - Forexample, ifthe data you get fromthe registeris **__0x0B 0x05__**, the distance between the sensorandthe measured objectis615 +NB-IoT Network signal Strength. 533 533 ))) 534 534 535 535 ((( 536 -((( 537 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 619 +**Ex1: 0x1d = 29** 538 538 ))) 539 -))) 540 540 541 541 ((( 542 - 623 +(% style="color:blue" %)**0**(%%) -113dBm or less 543 543 ))) 544 544 545 545 ((( 546 - 627 +(% style="color:blue" %)**1**(%%) -111dBm 547 547 ))) 548 548 549 -=== 2.4.6 Digital Interrupt === 550 - 551 551 ((( 552 - Digital Interrupt refers to pin(% style="color:blue" %)**GPIO_EXTI**(%%),andthere are different triggermethods.When there is a trigger, the NDDS75will senda packet to the server.631 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 553 553 ))) 554 554 555 555 ((( 556 - Thecommandis:635 +(% style="color:blue" %)**31** (%%) -51dBm or greater 557 557 ))) 558 558 559 559 ((( 560 -(% style="color:blue" %)** AT+INTMOD=3**(%%)~/~/(moreinfoabout INMOD pleaserefer[[**AT CommandManual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**639 +(% style="color:blue" %)**99** (%%) Not known or not detectable 561 561 ))) 562 562 563 563 564 -((( 565 -The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up. 566 -))) 567 567 644 +=== 2.3.6 Temperature & Humidity === 568 568 569 -((( 570 -Example: 571 -))) 572 572 573 -((( 574 -0x(00): Normal uplink packet. 575 -))) 647 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 576 576 577 -((( 578 -0x(01): Interrupt Uplink Packet. 579 -))) 649 +[[image:image-20220709161741-3.png]] 580 580 581 581 652 +Convert the read byte to decimal and divide it by ten. 582 582 583 -=== 2.4.7 +5V Output === 584 584 585 -((( 586 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 587 -))) 655 +**Example:** 588 588 657 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 589 589 590 -((( 591 -The 5V output time can be controlled by AT Command. 592 -))) 659 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 593 593 594 -((( 595 -(% style="color:blue" %)**AT+5VT=1000** 596 -))) 597 597 598 -((( 599 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 600 -))) 601 601 663 +== 2.4 Downlink Payload == 602 602 603 603 604 - ==2.5DownlinkPayload==666 +By default, N95S31B prints the downlink payload to console port. 605 605 606 -By default, NDDS75 prints the downlink payload to console port. 607 - 608 608 [[image:image-20220709100028-1.png]] 609 609 610 610 ... ... @@ -641,7 +641,7 @@ 641 641 ))) 642 642 643 643 ((( 644 -If payload = 0x04FF, it will reset the DDS75704 +If payload = 0x04FF, it will reset the N95S31B 645 645 ))) 646 646 647 647 ... ... @@ -653,51 +653,17 @@ 653 653 654 654 655 655 656 -== 2. 6LED Indicator ==716 +== 2.5 Battery Analysis == 657 657 658 658 659 - TheNDDS75has an internal LED which isto show thestatus of differentstate.719 +=== 2.5.1 Battery Type === 660 660 661 661 662 -* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 663 -* Then the LED will be on for 1 second means device is boot normally. 664 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 665 -* For each uplink probe, LED will be on for 500ms. 666 - 667 667 ((( 668 - 723 +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. 669 669 ))) 670 670 671 - 672 - 673 -== 2.7 Firmware Change Log == 674 - 675 - 676 676 ((( 677 -Download URL & Firmware Change log 678 -))) 679 - 680 -((( 681 -[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]] 682 -))) 683 - 684 - 685 -((( 686 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 687 -))) 688 - 689 - 690 - 691 -== 2.8 Battery Analysis == 692 - 693 -=== 2.8.1 Battery Type === 694 - 695 - 696 -((( 697 -The NDDS75 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. 698 -))) 699 - 700 -((( 701 701 The battery is designed to last for several years depends on the actually use environment and update interval. 702 702 ))) 703 703 ... ... @@ -715,56 +715,37 @@ 715 715 716 716 717 717 718 -=== 2. 8.2 Power consumption Analyze ===744 +=== 2.5.2 Power consumption Analyze === 719 719 720 -((( 721 -Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval. 722 -))) 723 723 724 - 725 725 ((( 726 -Instruction to use as below: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. 727 727 ))) 728 728 729 729 ((( 730 - (%style="color:blue" %)**Step 1: **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]752 + 731 731 ))) 732 732 733 733 734 -((( 735 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose 736 -))) 756 +=== 2.5.3 Battery Note === 737 737 738 -* ((( 739 -Product Model 740 -))) 741 -* ((( 742 -Uplink Interval 743 -))) 744 -* ((( 745 -Working Mode 746 -))) 747 747 748 748 ((( 749 - And the Life expectation in difference casewillbe shownon theright.760 +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. 750 750 ))) 751 751 752 -[[image:image-20220709110451-3.png]] 753 753 754 754 765 +=== 2.5.4 Replace the battery === 755 755 756 -=== 2.8.3 Battery Note === 757 757 758 758 ((( 759 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.769 +You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board. 760 760 ))) 761 761 762 762 763 - 764 -=== 2.8.4 Replace the battery === 765 - 766 766 ((( 767 -The default battery pack of N DDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).774 +The default battery pack of N95S31B includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes). 768 768 ))) 769 769 770 770 ... ... @@ -771,6 +771,7 @@ 771 771 772 772 = 3. Access NB-IoT Module = 773 773 781 + 774 774 ((( 775 775 Users can directly access the AT command set of the NB-IoT module. 776 776 ))) ... ... @@ -777,6 +777,8 @@ 777 777 778 778 ((( 779 779 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 + 780 780 ))) 781 781 782 782 [[image:1657333200519-600.png]] ... ... @@ -785,11 +785,13 @@ 785 785 786 786 = 4. Using the AT Commands = 787 787 798 + 788 788 == 4.1 Access AT Commands == 789 789 790 -See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 791 791 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]] 792 792 804 + 793 793 AT+<CMD>? : Help on <CMD> 794 794 795 795 AT+<CMD> : Run <CMD> ... ... @@ -863,6 +863,7 @@ 863 863 864 864 = 5. FAQ = 865 865 878 + 866 866 == 5.1 How to Upgrade Firmware == 867 867 868 868 ... ... @@ -875,13 +875,18 @@ 875 875 ))) 876 876 877 877 ((( 878 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 891 + 892 + 893 +((( 894 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 879 879 ))) 896 +))) 880 880 881 881 882 882 883 883 = 6. Trouble Shooting = 884 884 902 + 885 885 == 6.1 Connection problem when uploading firmware == 886 886 887 887 ... ... @@ -897,6 +897,7 @@ 897 897 898 898 == 6.2 AT Command input doesn't work == 899 899 918 + 900 900 ((( 901 901 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. 902 902 ... ... @@ -907,7 +907,7 @@ 907 907 = 7. Order Info = 908 908 909 909 910 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**929 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 911 911 912 912 913 913 (% class="wikigeneratedid" %) ... ... @@ -922,7 +922,7 @@ 922 922 923 923 (% style="color:#037691" %)**Package Includes**: 924 924 925 -* NS E01DistanceDetectSensorNode x 1944 +* N95S31B NB-IoT Temperature and Humidity Sensor 926 926 * External antenna x 1 927 927 ))) 928 928 ... ... @@ -931,11 +931,10 @@ 931 931 932 932 (% style="color:#037691" %)**Dimension and weight**: 933 933 934 - 935 935 * Device Size: 13.0 x 5 x 4.5 cm 936 936 * Device Weight: 150g 937 -* Package Size / pcs : 1 5x12x 5.5cm938 -* Weight / pcs : 220g955 +* Package Size / pcs : 14.0 x 8x 5 cm 956 +* Weight / pcs : 180g 939 939 ))) 940 940 941 941 ((( ... ... @@ -947,5 +947,9 @@ 947 947 948 948 = 9. Support = 949 949 968 + 950 950 * 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. 951 951 * 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-20220709161741-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +111.2 KB - Content