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, 0 added, 9 removed)
Details
- Page properties
-
- Content
-
... ... @@ -9,7 +9,6 @@ 9 9 10 10 **Table of Contents:** 11 11 12 -{{toc/}} 13 13 14 14 15 15 ... ... @@ -42,6 +42,7 @@ 42 42 43 43 == 1.2 Features == 44 44 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 ... ... @@ -53,6 +53,8 @@ 53 53 * Micro SIM card slot for NB-IoT SIM 54 54 * 8500mAh Battery for long term use 55 55 56 + 57 + 56 56 == 1.3 Specification == 57 57 58 58 ... ... @@ -79,6 +79,8 @@ 79 79 * Max continuously current: 130mA 80 80 * Max boost current: 2A, 1 second 81 81 84 + 85 + 82 82 == 1.4 Applications == 83 83 84 84 * Smart Buildings & Home Automation ... ... @@ -126,6 +126,9 @@ 126 126 1. When boot the device in flash mode 127 127 1. Send an uplink packet 128 128 133 + 134 + 135 + 129 129 = 2. Use N95S31B to communicate with IoT Server = 130 130 131 131 == 2.1 How it works == ... ... @@ -169,6 +169,7 @@ 169 169 * The local NB-IoT network used the band that N95S31B supports. 170 170 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 171 171 179 + 172 172 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 173 173 174 174 N95S31B supports different communication protocol such as : ... ... @@ -203,7 +203,7 @@ 203 203 204 204 205 205 206 -=== 2.2. 4Connect USB – TTL to N95S31B to configure it ===214 +=== 2.2.3 Connect USB – TTL to N95S31B to configure it === 207 207 208 208 ((( 209 209 ((( ... ... @@ -242,7 +242,7 @@ 242 242 243 243 244 244 245 -=== 2.2. 5Use CoAP protocol to uplink data ===253 +=== 2.2.4 Use CoAP protocol to uplink data === 246 246 247 247 (% 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/]] 248 248 ... ... @@ -262,12 +262,10 @@ 262 262 ))) 263 263 264 264 ((( 265 - 266 - 267 267 For parameter description, please refer to AT command set 268 268 ))) 269 269 270 -[[image:1657352 146020-183.png]]276 +[[image:1657330452568-615.png]] 271 271 272 272 273 273 ((( ... ... @@ -274,11 +274,11 @@ 274 274 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. 275 275 ))) 276 276 277 -[[image:16573 52185396-303.png]]283 +[[image:1657330472797-498.png]] 278 278 279 279 280 280 281 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===287 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 282 282 283 283 284 284 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -285,16 +285,15 @@ 285 285 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 286 286 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 287 287 288 -[[image:16573 52391268-297.png]]294 +[[image:1657330501006-241.png]] 289 289 290 290 291 -[[image:16573 52403317-397.png]]297 +[[image:1657330533775-472.png]] 292 292 293 293 294 294 295 -=== 2.2. 7Use MQTT protocol to uplink data ===301 +=== 2.2.6 Use MQTT protocol to uplink data === 296 296 297 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 298 298 299 299 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 300 300 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -301,40 +301,35 @@ 301 301 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 302 302 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 303 303 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 304 -* (% style="color:blue" %)**AT+PUBTOPIC= f9527305 -* (% style="color:blue" %)**AT+SUBTOPIC=N s9527 **(%%)309 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 310 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 306 306 307 -[[image:1657 352634421-276.png]]312 +[[image:1657249978444-674.png]] 308 308 309 309 310 -[[image:16573 52645687-385.png]]315 +[[image:1657330723006-866.png]] 311 311 312 -((( 313 -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. 314 -))) 315 315 316 - 317 317 ((( 318 -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.319 +MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 319 319 ))) 320 320 321 321 322 322 323 -=== 2.2. 8Use TCP protocol to uplink data ===324 +=== 2.2.7 Use TCP protocol to uplink data === 324 324 325 -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: 1657352898400-901.png]]330 +[[image:image-20220709093918-1.png]] 331 331 332 332 333 -[[image: 1657352914475-252.png]]333 +[[image:image-20220709093918-2.png]] 334 334 335 335 336 336 337 -=== 2.2. 9Change Update Interval ===337 +=== 2.2.8 Change Update Interval === 338 338 339 339 User can use below command to change the (% style="color:green" %)**uplink interval**. 340 340 ... ... @@ -341,209 +341,227 @@ 341 341 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 342 342 343 343 ((( 344 - 344 +(% style="color:red" %)**NOTE:** 345 345 ))) 346 346 347 +((( 348 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 349 +))) 347 347 348 348 352 + 349 349 == 2.3 Uplink Payload == 350 350 355 +In this mode, uplink payload includes in total 14 bytes 351 351 352 -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. 353 353 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"]] 354 354 355 -For example: 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 +))) 356 356 357 - (% 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. 358 358 369 +[[image:1657331036973-987.png]] 359 359 360 -The uplink payloads are composed in ASCII String. For example: 371 +((( 372 +The payload is ASCII string, representative same HEX: 373 +))) 361 361 362 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 375 +((( 376 +0x72403155615900640c6c19029200 where: 377 +))) 363 363 364 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 379 +* ((( 380 +Device ID: 0x724031556159 = 724031556159 381 +))) 382 +* ((( 383 +Version: 0x0064=100=1.0.0 384 +))) 365 365 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 366 366 367 -(% style="color:red" %)**NOTE:** 368 368 369 -(% style="color:red" %) 370 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 371 -1. By default, the device will send an uplink message every 1 hour. 372 372 400 + 401 +))) 373 373 403 +== 2.4 Payload Explanation and Sensor Interface == 374 374 375 375 376 -=== 2. 3.1Payload Analyze ===406 +=== 2.4.1 Device ID === 377 377 378 -N95S31B uplink payload includes in total 21 bytes 379 - 380 - 381 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 382 -|=(% style="width: 60px;" %)((( 383 -**Size(bytes)** 384 -)))|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2** 385 -|(% 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" %)((( 386 386 ((( 387 - Reserve/Same asNBSN95CFGMOD=1409 +By default, the Device ID equal to the last 6 bytes of IMEI. 388 388 ))) 389 389 390 390 ((( 391 - Nofunctionhere.413 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 392 392 ))) 393 - )))|(% style="width:77px" %)(((415 + 394 394 ((( 395 - [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]417 +**Example:** 396 396 ))) 397 397 398 398 ((( 399 - By SHT31421 +AT+DEUI=A84041F15612 400 400 ))) 401 - )))|(% style="width:80px" %)(((423 + 402 402 ((( 403 - [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]425 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 404 404 ))) 405 405 428 + 429 + 430 +=== 2.4.2 Version Info === 431 + 406 406 ((( 407 - BySHT31433 +Specify the software version: 0x64=100, means firmware version 1.00. 408 408 ))) 409 -))) 410 410 411 411 ((( 412 -((( 413 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 437 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 414 414 ))) 415 -))) 416 416 417 417 418 -[[image:1657354294009-643.png]] 419 419 442 +=== 2.4.3 Battery Info === 420 420 421 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 422 - 423 -* Device ID: 0x724031607457 = 724031607457 424 -* Version: 0x006e=110=1.1.0 425 - 426 -* BAT: 0x0ccd = 3277 mV = 3.277V 427 -* Signal: 0x1b = 27 428 -* Model: 0x01 = 1 429 -* 0x00dc000ccc= reserve, ignore in N95S31B 430 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 431 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 432 - 433 433 ((( 434 - 445 +Ex1: 0x0B45 = 2885mV 435 435 ))) 436 436 437 437 ((( 438 - 449 +Ex2: 0x0B49 = 2889mV 439 439 ))) 440 440 441 441 442 -=== 2.3.2 Device ID === 443 443 454 +=== 2.4.4 Signal Strength === 455 + 444 444 ((( 445 -B ydefault,the Device ID equal to thelast6 bytes of IMEI.457 +NB-IoT Network signal Strength. 446 446 ))) 447 447 448 448 ((( 449 - User can use (% style="color:blue" %)**AT+DEUI**(%%)tosetDevice ID461 +**Ex1: 0x1d = 29** 450 450 ))) 451 451 452 452 ((( 453 - **Example:**465 +(% style="color:blue" %)**0**(%%) -113dBm or less 454 454 ))) 455 455 456 456 ((( 457 - AT+DEUI=A84041F15612469 +(% style="color:blue" %)**1**(%%) -111dBm 458 458 ))) 459 459 460 460 ((( 461 - TheDevice ID isstored in a none-erase area, Upgrade the firmwareorrun**AT+FDR**won't erase Device ID.473 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 462 462 ))) 463 463 476 +((( 477 +(% style="color:blue" %)**31** (%%) -51dBm or greater 478 +))) 464 464 480 +((( 481 +(% style="color:blue" %)**99** (%%) Not known or not detectable 482 +))) 465 465 466 -=== 2.3.3 Version Info === 467 467 468 468 469 - Thesebytesinclude the hardware andsoftwareversion.486 +=== 2.4.5 Distance === 470 470 471 - Higherbyte:Specifyhardwareversion: always0x00forN95S31B488 +Get the distance. Flat object range 280mm - 7500mm. 472 472 473 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110 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 +))) 474 474 475 - 476 -For example: 0x00 6E: this device is N95S31B with firmware version 110. 477 - 478 478 ((( 479 - 495 +((( 496 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 480 480 ))) 498 +))) 481 481 482 - 483 -=== 2.3.4 Battery Info === 484 - 485 485 ((( 486 - Ex1:0x0B45 = 2885mV501 + 487 487 ))) 488 488 489 489 ((( 490 - Ex2:0x0B49 = 2889mV505 + 491 491 ))) 492 492 508 +=== 2.4.6 Digital Interrupt === 493 493 494 - 495 -=== 2.3.5 Signal Strength === 496 - 497 497 ((( 498 - NB-IoTNetworksignalStrength.511 +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. 499 499 ))) 500 500 501 501 ((( 502 - **Ex1:0x1d= 29**515 +The command is: 503 503 ))) 504 504 505 505 ((( 506 -(% style="color:blue" %)** 0**(%%)-113dBmor less519 +(% 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]])**.** 507 507 ))) 508 508 522 + 509 509 ((( 510 - (%style="color:blue"%)**1**(%%)-111dBm524 +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. 511 511 ))) 512 512 527 + 513 513 ((( 514 - (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm529 +Example: 515 515 ))) 516 516 517 517 ((( 518 -( %style="color:blue"%)**31** (%%) -51dBm or greater533 +0x(00): Normal uplink packet. 519 519 ))) 520 520 521 521 ((( 522 -( %style="color:blue" %)**99** (%%) Notknownor not detectable537 +0x(01): Interrupt Uplink Packet. 523 523 ))) 524 524 525 525 526 526 527 -=== 2. 3.6Temperature& Humidity===542 +=== 2.4.7 +5V Output === 528 528 529 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 544 +((( 545 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 546 +))) 530 530 531 -[[image:image-20220709161741-3.png]] 532 532 549 +((( 550 +The 5V output time can be controlled by AT Command. 551 +))) 533 533 534 -Convert the read byte to decimal and divide it by ten. 553 +((( 554 +(% style="color:blue" %)**AT+5VT=1000** 555 +))) 535 535 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 +))) 536 536 537 -**Example:** 538 538 539 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 540 540 541 - Humidity:Read:0295(H)=661(D)Value:661 / 10=66.1, So66.1%563 +== 2.5 Downlink Payload == 542 542 543 - 544 - 545 -== 2.4 Downlink Payload == 546 - 547 547 By default, NDDS75 prints the downlink payload to console port. 548 548 549 549 [[image:image-20220709100028-1.png]] ... ... @@ -594,16 +594,51 @@ 594 594 595 595 596 596 597 -== 2. 5BatteryAnalysis==615 +== 2.6 LED Indicator == 598 598 599 -=== 2.5.1 Battery Type === 600 600 618 +The NDDS75 has an internal LED which is to show the status of different state. 601 601 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 + 602 602 ((( 603 - TheN95S31B 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.627 + 604 604 ))) 605 605 630 + 631 + 632 +== 2.7 Firmware Change Log == 633 + 634 + 606 606 ((( 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 +((( 607 607 The battery is designed to last for several years depends on the actually use environment and update interval. 608 608 ))) 609 609 ... ... @@ -621,35 +621,56 @@ 621 621 622 622 623 623 624 -=== 2. 5.2 Power consumption Analyze ===677 +=== 2.8.2 Power consumption Analyze === 625 625 626 626 ((( 627 - 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/]] describesadetailmeasurementtoanalyzethepowerconsumption indifferentcase. User can useitfordesignguideline fortheirproject.680 +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. 628 628 ))) 629 629 683 + 630 630 ((( 631 - 685 +Instruction to use as below: 632 632 ))) 633 633 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 +))) 634 634 635 -=== 2.5.3 Battery Note === 636 636 637 637 ((( 638 - TheLi-SICO batteryis designed for small current / long period application. It is not good tousea high current, short periodtransmitmethod.Therecommendedminimum period for use ofthisbattery is 5 minutes.If you use a shorter period time to uplink data, then the battery life may be decreased.694 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 639 639 ))) 640 640 697 +* ((( 698 +Product Model 699 +))) 700 +* ((( 701 +Uplink Interval 702 +))) 703 +* ((( 704 +Working Mode 705 +))) 641 641 707 +((( 708 +And the Life expectation in difference case will be shown on the right. 709 +))) 642 642 643 - === 2.5.4 Replacethe battery ===711 +[[image:image-20220709110451-3.png]] 644 644 645 645 714 + 715 +=== 2.8.3 Battery Note === 716 + 646 646 ((( 647 - You can changethebattery intheN95S31B.Thetype ofbatteryis notlimitedaslongas theutput isbetween3vto3.6v.Onthemainboard,there isa diode(D1)betweenthebatteryandthemaincircuit. If youneed touse abatterywith less than 3.3v,pleaseremove the D1 andshortcut the twopadsofitso there won'tbe voltagedropbetween batteryandmainboard.718 +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 transmit LoRa, then the battery life may be decreased. 648 648 ))) 649 649 650 650 722 + 723 +=== 2.8.4 Replace the battery === 724 + 651 651 ((( 652 -The default battery pack of N 95S31Bincludes 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).726 +The default battery pack of NDDS75 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). 653 653 ))) 654 654 655 655 ... ... @@ -672,7 +672,7 @@ 672 672 673 673 == 4.1 Access AT Commands == 674 674 675 -See NBSN95 AT Command inthis link for detail:BSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]749 +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/]] 676 676 677 677 678 678 AT+<CMD>? : Help on <CMD> ... ... @@ -760,9 +760,7 @@ 760 760 ))) 761 761 762 762 ((( 763 - 764 - 765 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 837 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 766 766 ))) 767 767 768 768 ... ... @@ -794,7 +794,7 @@ 794 794 = 7. Order Info = 795 795 796 796 797 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**869 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 798 798 799 799 800 800 (% class="wikigeneratedid" %) ... ... @@ -809,7 +809,7 @@ 809 809 810 810 (% style="color:#037691" %)**Package Includes**: 811 811 812 -* N 95S31BNB-IoTTemperatureandHumiditySensor884 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 813 813 * External antenna x 1 814 814 ))) 815 815 ... ... @@ -818,10 +818,11 @@ 818 818 819 819 (% style="color:#037691" %)**Dimension and weight**: 820 820 893 + 821 821 * Device Size: 13.0 x 5 x 4.5 cm 822 822 * Device Weight: 150g 823 -* Package Size / pcs : 1 4.0x8x 5 cm824 -* Weight / pcs : 180g896 +* Package Size / pcs : 15 x 12x 5.5 cm 897 +* Weight / pcs : 220g 825 825 ))) 826 826 827 827 (((
- 1657352185396-303.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -98.3 KB - Content
- 1657352391268-297.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -238.0 KB - Content
- 1657352403317-397.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -547.7 KB - Content
- 1657352634421-276.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -163.6 KB - Content
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -144.8 KB - Content
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -157.0 KB - Content
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.2 KB - Content