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, 11 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 ... ... @@ -21,16 +21,29 @@ 21 21 ((( 22 22 23 23 25 +((( 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*. 27 +))) 25 25 29 +((( 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. 31 +))) 27 27 33 +((( 28 28 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 35 +))) 29 29 37 +((( 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). 39 +))) 31 31 41 +((( 42 + 43 +))) 32 32 45 +((( 33 33 ~* make sure you have NB-IoT coverage locally. 47 +))) 34 34 35 35 36 36 ))) ... ... @@ -41,7 +41,6 @@ 41 41 42 42 == 1.2 Features == 43 43 44 - 45 45 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 46 46 * Monitor Temperature & Humidity via SHT31 47 47 * AT Commands to change parameters ... ... @@ -55,6 +55,7 @@ 55 55 56 56 57 57 71 + 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -63,6 +63,7 @@ 63 63 * Supply Voltage: 2.1v ~~ 3.6v 64 64 * Operating Temperature: -40 ~~ 85°C 65 65 80 + 66 66 (% style="color:#037691" %)**NB-IoT Spec:** 67 67 68 68 * - B1 @H-FDD: 2100MHz ... ... @@ -72,9 +72,9 @@ 72 72 * - B20 @H-FDD: 800MHz 73 73 * - B28 @H-FDD: 700MHz 74 74 90 + 75 75 (% style="color:#037691" %)**Battery:** 76 76 77 - 78 78 * Li/SOCI2 un-chargeable battery 79 79 * Capacity: 8500mAh 80 80 * Self Discharge: <1% / Year @ 25°C ... ... @@ -83,6 +83,7 @@ 83 83 84 84 85 85 101 + 86 86 == 1.4 Applications == 87 87 88 88 * Smart Buildings & Home Automation ... ... @@ -111,9 +111,13 @@ 111 111 112 112 === 1.5.2 BOOT MODE / SW1 === 113 113 130 +((( 114 114 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 +))) 115 115 134 +((( 116 116 2) Flash: work mode, device starts to work and send out console output for further debug 136 +))) 117 117 118 118 119 119 ... ... @@ -170,24 +170,45 @@ 170 170 === 2.2.1 Test Requirement === 171 171 172 172 193 +((( 173 173 To use N95S31B in your city, make sure meet below requirements: 195 +))) 174 174 175 -* Your local operator has already distributed a NB-IoT Network there. 176 -* The local NB-IoT network used the band that N95S31B supports. 177 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 197 +* ((( 198 +Your local operator has already distributed a NB-IoT Network there. 199 +))) 200 +* ((( 201 +The local NB-IoT network used the band that N95S31B supports. 202 +))) 203 +* ((( 204 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 205 +))) 178 178 179 - 207 +((( 180 180 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 209 +))) 181 181 211 +((( 182 182 N95S31B supports different communication protocol such as : 213 +))) 183 183 184 184 ((( 185 -* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 186 -* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 187 -* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 188 -* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 216 +* ((( 217 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 218 +))) 219 +* ((( 220 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 221 +))) 222 +* ((( 223 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 224 +))) 225 +* ((( 226 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 227 +))) 189 189 229 +((( 190 190 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. 231 +))) 191 191 192 192 193 193 ))) ... ... @@ -211,15 +211,15 @@ 211 211 212 212 213 213 214 -=== 2.2. 3DDS75 to configure it ===255 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 215 215 216 216 ((( 217 217 ((( 218 -User need to configure DDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect toDDS75 and use AT Commands to configure it, as below.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. 219 219 ))) 220 220 ))) 221 221 222 -[[image: image-20220709092052-2.png]]263 +[[image:1657351312545-300.png]] 223 223 224 224 **Connection:** 225 225 ... ... @@ -239,18 +239,18 @@ 239 239 * Flow Control: (% style="color:green" %)**None** 240 240 241 241 ((( 242 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N DDS75.DDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.283 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input. 243 243 ))) 244 244 245 245 [[image:1657329814315-101.png]] 246 246 247 247 ((( 248 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N DDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]289 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] 249 249 ))) 250 250 251 251 252 252 253 -=== 2.2. 4294 +=== 2.2.5 Use CoAP protocol to uplink data === 254 254 255 255 (% 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/]] 256 256 ... ... @@ -270,10 +270,12 @@ 270 270 ))) 271 271 272 272 ((( 314 + 315 + 273 273 For parameter description, please refer to AT command set 274 274 ))) 275 275 276 -[[image:16573 30452568-615.png]]319 +[[image:1657352146020-183.png]] 277 277 278 278 279 279 ((( ... ... @@ -280,11 +280,11 @@ 280 280 After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server. 281 281 ))) 282 282 283 -[[image:16573 30472797-498.png]]326 +[[image:1657352185396-303.png]] 284 284 285 285 286 286 287 -=== 2.2. 5330 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 288 288 289 289 290 290 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -291,15 +291,16 @@ 291 291 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 292 292 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 293 293 294 -[[image:16573 30501006-241.png]]337 +[[image:1657352391268-297.png]] 295 295 296 296 297 -[[image:16573 30533775-472.png]]340 +[[image:1657352403317-397.png]] 298 298 299 299 300 300 301 -=== 2.2. 6344 +=== 2.2.7 Use MQTT protocol to uplink data === 302 302 346 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 303 303 304 304 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 305 305 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -306,35 +306,40 @@ 306 306 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 307 307 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 308 308 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 309 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB**(%%)~/~/Set the sending topic of MQTT310 -* (% style="color:blue" %)**AT+SUBTOPIC=N DDS75_SUB**(%%) ~/~/Set the subscription topic of MQTT353 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 354 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 311 311 312 -[[image:165724 9978444-674.png]]356 +[[image:1657352634421-276.png]] 313 313 314 314 315 -[[image:16573 30723006-866.png]]359 +[[image:1657352645687-385.png]] 316 316 361 +((( 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 +))) 317 317 365 + 318 318 ((( 319 -MQTT protocol has a much high erpower consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.367 +MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 320 320 ))) 321 321 322 322 323 323 324 -=== 2.2. 7372 +=== 2.2.8 Use TCP protocol to uplink data === 325 325 374 +This feature is supported since firmware version v110 326 326 327 327 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 328 328 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 329 329 330 -[[image: image-20220709093918-1.png]]379 +[[image:1657352898400-901.png]] 331 331 332 332 333 -[[image: image-20220709093918-2.png]]382 +[[image:1657352914475-252.png]] 334 334 335 335 336 336 337 -=== 2.2. 8386 +=== 2.2.9 Change Update Interval === 338 338 339 339 User can use below command to change the (% style="color:green" %)**uplink interval**. 340 340 ... ... @@ -341,227 +341,207 @@ 341 341 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 342 342 343 343 ((( 344 - (%style="color:red" %)**NOTE:**393 + 345 345 ))) 346 346 347 -((( 348 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 349 -))) 350 350 351 351 352 - 353 353 == 2.3 Uplink Payload == 354 354 355 -In this mode, uplink payload includes in total 14 bytes 356 356 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. 357 357 358 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 359 -|=(% style="width: 60px;" %)((( 360 -**Size(bytes)** 361 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 362 -|(% 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:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]] 363 363 364 -((( 365 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 366 -))) 404 +For example: 367 367 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. 368 368 369 -[[image:1657331036973-987.png]] 370 370 371 -((( 372 -The payload is ASCII string, representative same HEX: 373 -))) 409 +The uplink payloads are composed in ASCII String. For example: 374 374 375 -((( 376 -0x72403155615900640c6c19029200 where: 377 -))) 411 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 378 378 379 -* ((( 380 -Device ID: 0x724031556159 = 724031556159 381 -))) 382 -* ((( 383 -Version: 0x0064=100=1.0.0 384 -))) 413 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 385 385 386 -* ((( 387 -BAT: 0x0c6c = 3180 mV = 3.180V 388 -))) 389 -* ((( 390 -Signal: 0x19 = 25 391 -))) 392 -* ((( 393 -Distance: 0x0292= 658 mm 394 -))) 395 -* ((( 396 -Interrupt: 0x00 = 0 397 397 416 +(% style="color:red" %)**NOTE:** 398 398 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. 399 399 400 - 401 -))) 402 402 403 -== 2. 4PayloadExplanation and SensorInterface==423 +=== 2.3.1 Payload Analyze === 404 404 425 +N95S31B uplink payload includes in total 21 bytes 405 405 406 -=== 2.4.1 Device ID === 407 407 428 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 429 +|=(% style="width: 60px;" %)((( 430 +**Size(bytes)** 431 +)))|=(% 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** 432 +|(% 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" %)((( 408 408 ((( 409 - By default, theDeviceID equal to thelast6bytes of IMEI.434 +Reserve/ Same as NBSN95 CFGMOD=1 410 410 ))) 411 411 412 412 ((( 413 - Usercanuse (% style="color:blue" %)**AT+DEUI**(%%)toset Device ID438 +No function here. 414 414 ))) 415 - 440 +)))|(% style="width:77px" %)((( 416 416 ((( 417 - **Example:**442 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 418 418 ))) 419 419 420 420 ((( 421 - AT+DEUI=A84041F15612446 +By SHT31 422 422 ))) 423 - 448 +)))|(% style="width:80px" %)((( 424 424 ((( 425 - The Device ID is storednane-erasearea, Upgradethe firmwareor run **AT+FDR** won'terase Device ID.450 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 426 426 ))) 427 427 428 - 429 - 430 -=== 2.4.2 Version Info === 431 - 432 432 ((( 433 - Specifythe software version: 0x64=100, means firmware version 1.00.454 +By SHT31 434 434 ))) 456 +))) 435 435 436 436 ((( 437 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 459 +((( 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. 438 438 ))) 462 +))) 439 439 440 440 465 +[[image:1657354294009-643.png]] 441 441 442 -=== 2.4.3 Battery Info === 443 443 468 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 469 + 470 +* Device ID: 0x724031607457 = 724031607457 471 +* Version: 0x006e=110=1.1.0 472 + 473 +* BAT: 0x0ccd = 3277 mV = 3.277V 474 +* Signal: 0x1b = 27 475 +* Model: 0x01 = 1 476 +* 0x00dc000ccc= reserve, ignore in N95S31B 477 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 478 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 479 + 444 444 ((( 445 - Ex1:0x0B45 = 2885mV481 + 446 446 ))) 447 447 448 448 ((( 449 - Ex2:0x0B49 = 2889mV485 + 450 450 ))) 451 451 452 452 489 +=== 2.3.2 Device ID === 453 453 454 -=== 2.4.4 Signal Strength === 455 - 456 456 ((( 457 - NB-IoTNetworksignalStrength.492 +By default, the Device ID equal to the last 6 bytes of IMEI. 458 458 ))) 459 459 460 460 ((( 461 - **Ex1:0x1d=29**496 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 462 462 ))) 463 463 464 464 ((( 465 - (% style="color:blue" %)**0**(%%) -113dBmorless500 +**Example:** 466 466 ))) 467 467 468 468 ((( 469 - (% style="color:blue" %)**1**(%%) -111dBm504 +AT+DEUI=A84041F15612 470 470 ))) 471 471 472 472 ((( 473 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm508 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 474 474 ))) 475 475 476 -((( 477 -(% style="color:blue" %)**31** (%%) -51dBm or greater 478 -))) 479 479 480 -((( 481 -(% style="color:blue" %)**99** (%%) Not known or not detectable 482 -))) 483 483 513 +=== 2.3.3 Version Info === 484 484 485 485 486 - ===2.4.5Distance===516 +These bytes include the hardware and software version. 487 487 488 - Get thedistance.Flat objectrange280mm-7500mm.518 +Higher byte: Specify hardware version: always 0x00 for N95S31B 489 489 490 -((( 491 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 492 -))) 520 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 493 493 522 + 523 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 524 + 494 494 ((( 495 -((( 496 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 526 + 497 497 ))) 498 -))) 499 499 529 + 530 +=== 2.3.4 Battery Info === 531 + 500 500 ((( 501 - 533 +Ex1: 0x0B45 = 2885mV 502 502 ))) 503 503 504 504 ((( 505 - 537 +Ex2: 0x0B49 = 2889mV 506 506 ))) 507 507 508 -=== 2.4.6 Digital Interrupt === 509 509 541 + 542 +=== 2.3.5 Signal Strength === 543 + 510 510 ((( 511 - DigitalInterrupt refers topin (% style="color:blue" %)**GPIO_EXTI**(%%),and there are differenttrigger methods. When thereisa trigger, the NDDS75 will sendapacketto the server.545 +NB-IoT Network signal Strength. 512 512 ))) 513 513 514 514 ((( 515 - Thecommandis:549 +**Ex1: 0x1d = 29** 516 516 ))) 517 517 518 518 ((( 519 -(% style="color:blue" %)** AT+INTMOD=3**(%%)~/~/(moreinfoaboutINMODpleaserefer[[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**553 +(% style="color:blue" %)**0**(%%) -113dBm or less 520 520 ))) 521 521 522 - 523 523 ((( 524 - Thelower four bitsofthis data field shows if this packet is generatedby interruptornot.Clickhereforthehardwareandsoftware set up.557 +(% style="color:blue" %)**1**(%%) -111dBm 525 525 ))) 526 526 527 - 528 528 ((( 529 - Example:561 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 530 530 ))) 531 531 532 532 ((( 533 - 0x(00):Normalplinkpacket.565 +(% style="color:blue" %)**31** (%%) -51dBm or greater 534 534 ))) 535 535 536 536 ((( 537 - 0x(01):InterruptUplinkPacket.569 +(% style="color:blue" %)**99** (%%) Not known or not detectable 538 538 ))) 539 539 540 540 541 541 542 -=== 2. 4.7+5VOutput===574 +=== 2.3.6 Temperature & Humidity === 543 543 544 -((( 545 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 546 -))) 576 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 547 547 578 +[[image:image-20220709161741-3.png]] 548 548 549 -((( 550 -The 5V output time can be controlled by AT Command. 551 -))) 552 552 553 -((( 554 -(% style="color:blue" %)**AT+5VT=1000** 555 -))) 581 +Convert the read byte to decimal and divide it by ten. 556 556 557 -((( 558 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 559 -))) 560 560 584 +**Example:** 561 561 586 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 562 562 563 - ==2.5Downlink Payload==588 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 564 564 590 + 591 + 592 +== 2.4 Downlink Payload == 593 + 565 565 By default, NDDS75 prints the downlink payload to console port. 566 566 567 567 [[image:image-20220709100028-1.png]] ... ... @@ -612,51 +612,16 @@ 612 612 613 613 614 614 615 -== 2. 6LED Indicator ==644 +== 2.5 Battery Analysis == 616 616 646 +=== 2.5.1 Battery Type === 617 617 618 -The NDDS75 has an internal LED which is to show the status of different state. 619 619 620 - 621 -* 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) 622 -* Then the LED will be on for 1 second means device is boot normally. 623 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 624 -* For each uplink probe, LED will be on for 500ms. 625 - 626 626 ((( 627 - 650 +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. 628 628 ))) 629 629 630 - 631 - 632 -== 2.7 Firmware Change Log == 633 - 634 - 635 635 ((( 636 -Download URL & Firmware Change log 637 -))) 638 - 639 -((( 640 -[[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/]] 641 -))) 642 - 643 - 644 -((( 645 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 646 -))) 647 - 648 - 649 - 650 -== 2.8 Battery Analysis == 651 - 652 -=== 2.8.1 Battery Type === 653 - 654 - 655 -((( 656 -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. 657 -))) 658 - 659 -((( 660 660 The battery is designed to last for several years depends on the actually use environment and update interval. 661 661 ))) 662 662 ... ... @@ -674,56 +674,35 @@ 674 674 675 675 676 676 677 -=== 2. 8.2 Power consumption Analyze ===671 +=== 2.5.2 Power consumption Analyze === 678 678 679 679 ((( 680 - Draginobatterypoweredproductareall runsinLow Powermode.Wehave an update battery calculatorwhichbaseonthe measurement oftherealdevice. User can usethis calculatortocheck the batterylifeandcalculatethe batterylifeifwant tousedifferenttransmit interval.674 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project. 681 681 ))) 682 682 683 - 684 684 ((( 685 - Instructionto use as below:678 + 686 686 ))) 687 687 688 -((( 689 -(% 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/]] 690 -))) 691 691 682 +=== 2.5.3 Battery Note === 692 692 693 693 ((( 694 - (%style="color:blue"%)**Step2:**(%%)Open it andchoose685 +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. 695 695 ))) 696 696 697 -* ((( 698 -Product Model 699 -))) 700 -* ((( 701 -Uplink Interval 702 -))) 703 -* ((( 704 -Working Mode 705 -))) 706 706 707 -((( 708 -And the Life expectation in difference case will be shown on the right. 709 -))) 710 710 711 - [[image:image-20220709110451-3.png]]690 +=== 2.5.4 Replace the battery === 712 712 713 713 714 - 715 -=== 2.8.3 Battery Note === 716 - 717 717 ((( 718 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.694 +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. 719 719 ))) 720 720 721 721 722 - 723 -=== 2.8.4 Replace the battery === 724 - 725 725 ((( 726 -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).699 +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). 727 727 ))) 728 728 729 729 ... ... @@ -746,7 +746,7 @@ 746 746 747 747 == 4.1 Access AT Commands == 748 748 749 -See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N DDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]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/]] 750 750 751 751 752 752 AT+<CMD>? : Help on <CMD> ... ... @@ -834,7 +834,9 @@ 834 834 ))) 835 835 836 836 ((( 837 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 810 + 811 + 812 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 838 838 ))) 839 839 840 840 ... ... @@ -866,7 +866,7 @@ 866 866 = 7. Order Info = 867 867 868 868 869 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**844 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 870 870 871 871 872 872 (% class="wikigeneratedid" %) ... ... @@ -881,7 +881,7 @@ 881 881 882 882 (% style="color:#037691" %)**Package Includes**: 883 883 884 -* NS E01DistanceDetectSensorNode x 1859 +* N95S31B NB-IoT Temperature and Humidity Sensor 885 885 * External antenna x 1 886 886 ))) 887 887 ... ... @@ -890,11 +890,10 @@ 890 890 891 891 (% style="color:#037691" %)**Dimension and weight**: 892 892 893 - 894 894 * Device Size: 13.0 x 5 x 4.5 cm 895 895 * Device Weight: 150g 896 -* Package Size / pcs : 1 5x12x 5.5cm897 -* Weight / pcs : 220g870 +* Package Size / pcs : 14.0 x 8x 5 cm 871 +* Weight / pcs : 180g 898 898 ))) 899 899 900 900 (((
- 1657351312545-300.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +675.8 KB - Content
- 1657352146020-183.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +264.0 KB - Content
- 1657352185396-303.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +98.3 KB - Content
- 1657352391268-297.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +238.0 KB - Content
- 1657352403317-397.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +547.7 KB - Content
- 1657352634421-276.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +163.6 KB - Content
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +144.8 KB - Content
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +157.0 KB - Content
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +214.7 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +111.2 KB - Content