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, 15 added, 0 removed)
- 1657350248151-650.png
- 1657350625843-586.png
- 1657351240556-536.png
- 1657351312545-300.png
- 1657352146020-183.png
- 1657352185396-303.png
- 1657352391268-297.png
- 1657352403317-397.png
- 1657352634421-276.png
- 1657352645687-385.png
- 1657352898400-901.png
- 1657352914475-252.png
- 1657354294009-643.png
- image-20220709150546-2.png
- image-20220709161741-3.png
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 ... ... @@ -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 ... ... @@ -54,7 +54,6 @@ 54 54 * 8500mAh Battery for long term use 55 55 56 56 57 - 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -82,7 +82,6 @@ 82 82 * Max boost current: 2A, 1 second 83 83 84 84 85 - 86 86 == 1.4 Applications == 87 87 88 88 * Smart Buildings & Home Automation ... ... @@ -130,20 +130,18 @@ 130 130 1. When boot the device in flash mode 131 131 1. Send an uplink packet 132 132 133 - 134 - 135 - 136 136 = 2. Use N95S31B to communicate with IoT Server = 137 137 138 138 == 2.1 How it works == 139 139 135 + 140 140 ((( 141 -The N DDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.137 +The N95S31B is equipped with a NB-IoT module, the pre-loaded firmware in N95S31B will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by N95S31B. 142 142 ))) 143 143 144 144 145 145 ((( 146 -The diagram below shows the working flow in default firmware of N DDS75:142 +The diagram below shows the working flow in default firmware of N95S31B: 147 147 ))) 148 148 149 149 ((( ... ... @@ -150,7 +150,7 @@ 150 150 151 151 ))) 152 152 153 -[[image:1657328 659945-416.png]]149 +[[image:1657350248151-650.png]] 154 154 155 155 ((( 156 156 ... ... @@ -157,30 +157,45 @@ 157 157 ))) 158 158 159 159 160 -== 2.2 Configure the N DDS75 ==156 +== 2.2 Configure the N95S31B == 161 161 162 162 159 +=== 2.2.1 Power On N95S31B === 160 + 161 + 162 +[[image:image-20220709150546-2.png]] 163 + 164 + 163 163 === 2.2.1 Test Requirement === 164 164 165 -((( 166 -To use NDDS75 in your city, make sure meet below requirements: 167 -))) 168 168 168 +To use N95S31B in your city, make sure meet below requirements: 169 + 169 169 * Your local operator has already distributed a NB-IoT Network there. 170 -* The local NB-IoT network used the band that NS E01 supports.171 +* The local NB-IoT network used the band that N95S31B supports. 171 171 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 172 172 174 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 175 + 176 +N95S31B supports different communication protocol such as : 177 + 173 173 ((( 174 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server 175 -))) 179 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 180 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 181 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 182 +* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 176 176 184 +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. 177 177 178 -[[image:1657328756309-230.png]] 186 + 187 +))) 179 179 189 +[[image:1657350625843-586.png]] 180 180 181 181 182 -=== 2.2.2 Insert SIM card === 183 183 193 +=== 2.2.3 Insert SIM card === 194 + 184 184 ((( 185 185 Insert the NB-IoT Card get from your provider. 186 186 ))) ... ... @@ -190,19 +190,19 @@ 190 190 ))) 191 191 192 192 193 -[[image:165732 8884227-504.png]]204 +[[image:1657351240556-536.png]] 194 194 195 195 196 196 197 -=== 2.2. 3DDS75 to configure it ===208 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 198 198 199 199 ((( 200 200 ((( 201 -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.212 +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. 202 202 ))) 203 203 ))) 204 204 205 -[[image: image-20220709092052-2.png]]216 +[[image:1657351312545-300.png]] 206 206 207 207 **Connection:** 208 208 ... ... @@ -222,18 +222,18 @@ 222 222 * Flow Control: (% style="color:green" %)**None** 223 223 224 224 ((( 225 -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.236 +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. 226 226 ))) 227 227 228 228 [[image:1657329814315-101.png]] 229 229 230 230 ((( 231 -(% 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/]]242 +(% 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/]] 232 232 ))) 233 233 234 234 235 235 236 -=== 2.2. 4247 +=== 2.2.5 Use CoAP protocol to uplink data === 237 237 238 238 (% 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/]] 239 239 ... ... @@ -253,10 +253,12 @@ 253 253 ))) 254 254 255 255 ((( 267 + 268 + 256 256 For parameter description, please refer to AT command set 257 257 ))) 258 258 259 -[[image:16573 30452568-615.png]]272 +[[image:1657352146020-183.png]] 260 260 261 261 262 262 ((( ... ... @@ -263,11 +263,11 @@ 263 263 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. 264 264 ))) 265 265 266 -[[image:16573 30472797-498.png]]279 +[[image:1657352185396-303.png]] 267 267 268 268 269 269 270 -=== 2.2. 5283 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 271 271 272 272 273 273 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -274,15 +274,16 @@ 274 274 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 275 275 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 276 276 277 -[[image:16573 30501006-241.png]]290 +[[image:1657352391268-297.png]] 278 278 279 279 280 -[[image:16573 30533775-472.png]]293 +[[image:1657352403317-397.png]] 281 281 282 282 283 283 284 -=== 2.2. 6297 +=== 2.2.7 Use MQTT protocol to uplink data === 285 285 299 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 286 286 287 287 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 288 288 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -289,35 +289,40 @@ 289 289 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 290 290 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 291 291 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 292 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB**(%%)~/~/Set the sending topic of MQTT293 -* (% style="color:blue" %)**AT+SUBTOPIC=N DDS75_SUB**(%%) ~/~/Set the subscription topic of MQTT306 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 307 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 294 294 295 -[[image:165724 9978444-674.png]]309 +[[image:1657352634421-276.png]] 296 296 297 297 298 -[[image:16573 30723006-866.png]]312 +[[image:1657352645687-385.png]] 299 299 314 +((( 315 +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. 316 +))) 300 300 318 + 301 301 ((( 302 -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.320 +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. 303 303 ))) 304 304 305 305 306 306 307 -=== 2.2. 7325 +=== 2.2.8 Use TCP protocol to uplink data === 308 308 327 +This feature is supported since firmware version v110 309 309 310 310 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 311 311 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 312 312 313 -[[image: image-20220709093918-1.png]]332 +[[image:1657352898400-901.png]] 314 314 315 315 316 -[[image: image-20220709093918-2.png]]335 +[[image:1657352914475-252.png]] 317 317 318 318 319 319 320 -=== 2.2. 8339 +=== 2.2.9 Change Update Interval === 321 321 322 322 User can use below command to change the (% style="color:green" %)**uplink interval**. 323 323 ... ... @@ -324,69 +324,90 @@ 324 324 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 325 325 326 326 ((( 327 - (%style="color:red" %)**NOTE:**346 + 328 328 ))) 329 329 330 -((( 331 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 332 -))) 333 333 334 334 335 - 336 336 == 2.3 Uplink Payload == 337 337 338 -In this mode, uplink payload includes in total 14 bytes 339 339 354 +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. 340 340 341 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 356 + 357 +For example: 358 + 359 + (% 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. 360 + 361 + 362 +The uplink payloads are composed in ASCII String. For example: 363 + 364 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 365 + 366 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 367 + 368 + 369 +(% style="color:red" %)**NOTE:** 370 + 371 +(% style="color:red" %) 372 +1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 373 +1. By default, the device will send an uplink message every 1 hour. 374 + 375 +=== 2.3.1 Payload Analyze === 376 + 377 +N95S31B uplink payload includes in total 21 bytes 378 + 379 + 380 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 342 342 |=(% style="width: 60px;" %)((( 343 343 **Size(bytes)** 344 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 345 -|(% 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"]] 383 +)))|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2** 384 +|(% 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" %)((( 385 +Reserve/ Same as NBSN95 CFGMOD=1 346 346 347 - (((348 - Ifwe usethe MQTT client to subscribe to this MQTT topic,we can see the following information when the NDDS751 uplinkdata.349 - )))387 +No function here. 388 +)))|(% style="width:77px" %)((( 389 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 350 350 391 +By SHT31 392 +)))|(% style="width:80px" %)((( 393 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 351 351 352 -[[image:1657331036973-987.png]] 353 - 354 -((( 355 -The payload is ASCII string, representative same HEX: 395 +By SHT31 356 356 ))) 357 357 358 358 ((( 359 -0x72403155615900640c6c19029200 where: 399 +((( 400 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 360 360 ))) 361 - 362 -* ((( 363 -Device ID: 0x724031556159 = 724031556159 364 364 ))) 365 -* ((( 366 -Version: 0x0064=100=1.0.0 367 -))) 368 368 369 -* ((( 370 -BAT: 0x0c6c = 3180 mV = 3.180V 371 -))) 372 -* ((( 373 -Signal: 0x19 = 25 374 -))) 375 -* ((( 376 -Distance: 0x0292= 658 mm 377 -))) 378 -* ((( 379 -Interrupt: 0x00 = 0 380 380 405 +[[image:1657354294009-643.png]] 381 381 382 382 408 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 409 + 410 +* Device ID: 0x724031607457 = 724031607457 411 +* Version: 0x006e=110=1.1.0 412 + 413 +* BAT: 0x0ccd = 3277 mV = 3.277V 414 +* Signal: 0x1b = 27 415 +* Model: 0x01 = 1 416 +* 0x00dc000ccc= reserve, ignore in N95S31B 417 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 418 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 419 + 420 +((( 383 383 384 384 ))) 385 385 386 -== 2.4 Payload Explanation and Sensor Interface == 424 +((( 425 + 426 +))) 387 387 388 388 389 -=== 2. 4.1429 +=== 2.3.2 Device ID === 390 390 391 391 ((( 392 392 By default, the Device ID equal to the last 6 bytes of IMEI. ... ... @@ -410,20 +410,25 @@ 410 410 411 411 412 412 413 -=== 2. 4.2Version Info ===453 +=== 2.3.3 Version Info === 414 414 415 -((( 416 -Specify the software version: 0x64=100, means firmware version 1.00. 417 -))) 418 418 456 +These bytes include the hardware and software version. 457 + 458 +Higher byte: Specify hardware version: always 0x00 for N95S31B 459 + 460 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 461 + 462 + 463 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 464 + 419 419 ((( 420 - Forexample: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.466 + 421 421 ))) 422 422 423 423 470 +=== 2.3.4 Battery Info === 424 424 425 -=== 2.4.3 Battery Info === 426 - 427 427 ((( 428 428 Ex1: 0x0B45 = 2885mV 429 429 ))) ... ... @@ -434,7 +434,7 @@ 434 434 435 435 436 436 437 -=== 2. 4.4Signal Strength ===482 +=== 2.3.5 Signal Strength === 438 438 439 439 ((( 440 440 NB-IoT Network signal Strength. ... ... @@ -466,85 +466,26 @@ 466 466 467 467 468 468 469 -=== 2. 4.5Distance ===514 +=== 2.3.6 Temperature & Humidity === 470 470 471 - Get the distance.Flatobject range280mm-7500mm.516 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 472 472 473 -((( 474 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 475 -))) 518 +[[image:image-20220709161741-3.png]] 476 476 477 -((( 478 -((( 479 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 480 -))) 481 -))) 482 482 483 -((( 484 - 485 -))) 521 +Convert the read byte to decimal and divide it by ten. 486 486 487 -((( 488 - 489 -))) 490 490 491 - === 2.4.6 DigitalInterrupt ===524 +**Example:** 492 492 493 -((( 494 -Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server. 495 -))) 526 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 496 496 497 -((( 498 -The command is: 499 -))) 528 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 500 500 501 -((( 502 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.** 503 -))) 504 504 505 505 506 -((( 507 -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. 508 -))) 532 +== 2.4 Downlink Payload == 509 509 510 - 511 -((( 512 -Example: 513 -))) 514 - 515 -((( 516 -0x(00): Normal uplink packet. 517 -))) 518 - 519 -((( 520 -0x(01): Interrupt Uplink Packet. 521 -))) 522 - 523 - 524 - 525 -=== 2.4.7 +5V Output === 526 - 527 -((( 528 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 529 -))) 530 - 531 - 532 -((( 533 -The 5V output time can be controlled by AT Command. 534 -))) 535 - 536 -((( 537 -(% style="color:blue" %)**AT+5VT=1000** 538 -))) 539 - 540 -((( 541 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 542 -))) 543 - 544 - 545 - 546 -== 2.5 Downlink Payload == 547 - 548 548 By default, NDDS75 prints the downlink payload to console port. 549 549 550 550 [[image:image-20220709100028-1.png]] ... ... @@ -595,51 +595,16 @@ 595 595 596 596 597 597 598 -== 2. 6LED Indicator ==584 +== 2.5 Battery Analysis == 599 599 586 +=== 2.5.1 Battery Type === 600 600 601 -The NDDS75 has an internal LED which is to show the status of different state. 602 602 603 - 604 -* 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) 605 -* Then the LED will be on for 1 second means device is boot normally. 606 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 607 -* For each uplink probe, LED will be on for 500ms. 608 - 609 609 ((( 610 - 590 +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. 611 611 ))) 612 612 613 - 614 - 615 -== 2.7 Firmware Change Log == 616 - 617 - 618 618 ((( 619 -Download URL & Firmware Change log 620 -))) 621 - 622 -((( 623 -[[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/]] 624 -))) 625 - 626 - 627 -((( 628 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 629 -))) 630 - 631 - 632 - 633 -== 2.8 Battery Analysis == 634 - 635 -=== 2.8.1 Battery Type === 636 - 637 - 638 -((( 639 -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. 640 -))) 641 - 642 -((( 643 643 The battery is designed to last for several years depends on the actually use environment and update interval. 644 644 ))) 645 645 ... ... @@ -657,56 +657,35 @@ 657 657 658 658 659 659 660 -=== 2. 8.2 Power consumption Analyze ===611 +=== 2.5.2 Power consumption Analyze === 661 661 662 662 ((( 663 - Draginobatterypoweredproductareall runsinLow Powermode.Wehave an update battery calculatorwhichbaseonthe measurement oftherealdevice. User can usethis calculatortocheck the batterylifeandcalculatethe batterylifeifwant tousedifferenttransmit interval.614 +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. 664 664 ))) 665 665 666 - 667 667 ((( 668 - Instructionto use as below:618 + 669 669 ))) 670 670 671 -((( 672 -(% 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/]] 673 -))) 674 674 622 +=== 2.5.3 Battery Note === 675 675 676 676 ((( 677 - (%style="color:blue"%)**Step2:**(%%)Open it andchoose625 +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. 678 678 ))) 679 679 680 -* ((( 681 -Product Model 682 -))) 683 -* ((( 684 -Uplink Interval 685 -))) 686 -* ((( 687 -Working Mode 688 -))) 689 689 690 -((( 691 -And the Life expectation in difference case will be shown on the right. 692 -))) 693 693 694 - [[image:image-20220709110451-3.png]]630 +=== 2.5.4 Replace the battery === 695 695 696 696 697 - 698 -=== 2.8.3 Battery Note === 699 - 700 700 ((( 701 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.634 +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. 702 702 ))) 703 703 704 704 705 - 706 -=== 2.8.4 Replace the battery === 707 - 708 708 ((( 709 -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).639 +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). 710 710 ))) 711 711 712 712 ... ... @@ -729,7 +729,7 @@ 729 729 730 730 == 4.1 Access AT Commands == 731 731 732 -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/]]662 +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/]] 733 733 734 734 735 735 AT+<CMD>? : Help on <CMD> ... ... @@ -817,7 +817,9 @@ 817 817 ))) 818 818 819 819 ((( 820 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 750 + 751 + 752 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 821 821 ))) 822 822 823 823 ... ... @@ -849,7 +849,7 @@ 849 849 = 7. Order Info = 850 850 851 851 852 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**784 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 853 853 854 854 855 855 (% class="wikigeneratedid" %) ... ... @@ -864,7 +864,7 @@ 864 864 865 865 (% style="color:#037691" %)**Package Includes**: 866 866 867 -* NS E01DistanceDetectSensorNode x 1799 +* N95S31B NB-IoT Temperature and Humidity Sensor 868 868 * External antenna x 1 869 869 ))) 870 870 ... ... @@ -873,11 +873,10 @@ 873 873 874 874 (% style="color:#037691" %)**Dimension and weight**: 875 875 876 - 877 877 * Device Size: 13.0 x 5 x 4.5 cm 878 878 * Device Weight: 150g 879 -* Package Size / pcs : 1 5x12x 5.5cm880 -* Weight / pcs : 220g810 +* Package Size / pcs : 14.0 x 8x 5 cm 811 +* Weight / pcs : 180g 881 881 ))) 882 882 883 883 (((
- 1657350248151-650.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content
- 1657350625843-586.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +93.3 KB - Content
- 1657351240556-536.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +483.6 KB - Content
- 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-20220709150546-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +333.5 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +111.2 KB - Content