Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 118.9 >
edited by Xiaoling
on 2022/07/12 17:37
To version < 111.2 >
edited by Xiaoling
on 2022/07/09 15:45
>
Change comment: There is no comment for this version

Summary

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  
... ... @@ -22,29 +22,16 @@
22 22  (((
23 23  
24 24  
25 -(((
26 26  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 -)))
28 28  
29 -(((
30 30  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 -)))
32 32  
33 -(((
34 34  N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
35 -)))
36 36  
37 -(((
38 38  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 -)))
40 40  
41 -(((
42 -
43 -)))
44 44  
45 -(((
46 46  ~* make sure you have NB-IoT coverage locally.
47 -)))
48 48  
49 49  
50 50  )))
... ... @@ -55,6 +55,7 @@
55 55  
56 56  == 1.2 ​ Features ==
57 57  
44 +
58 58  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
59 59  * Monitor Temperature & Humidity via SHT31
60 60  * AT Commands to change parameters
... ... @@ -87,6 +87,7 @@
87 87  
88 88  (% style="color:#037691" %)**Battery:**
89 89  
77 +
90 90  * Li/SOCI2 un-chargeable battery
91 91  * Capacity: 8500mAh
92 92  * Self Discharge: <1% / Year @ 25°C
... ... @@ -108,7 +108,7 @@
108 108  ​
109 109  
110 110  
111 -== 1.5  Pin Definitions & Switch ==
99 +== 1.5  Pin Definitions ==
112 112  
113 113  N95S31B use the mother board from NBSN95 which as below.
114 114  
... ... @@ -123,13 +123,9 @@
123 123  
124 124  === 1.5.2 BOOT MODE / SW1 ===
125 125  
126 -(((
127 127  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.
128 -)))
129 129  
130 -(((
131 131  2) Flash: work mode, device starts to work and send out console output for further debug
132 -)))
133 133  
134 134  
135 135  
... ... @@ -148,6 +148,7 @@
148 148  
149 149  
150 150  
135 +
151 151  = 2.  Use N95S31B to communicate with IoT Server =
152 152  
153 153  == 2.1  How it works ==
... ... @@ -166,7 +166,7 @@
166 166  
167 167  )))
168 168  
169 -[[image:1657520100595-569.png]]
154 +[[image:1657350248151-650.png]]
170 170  
171 171  (((
172 172  
... ... @@ -185,45 +185,24 @@
185 185  === 2.2.1 Test Requirement ===
186 186  
187 187  
188 -(((
189 189  To use N95S31B in your city, make sure meet below requirements:
190 -)))
191 191  
192 -* (((
193 -Your local operator has already distributed a NB-IoT Network there.
194 -)))
195 -* (((
196 -The local NB-IoT network used the band that N95S31B supports.
197 -)))
198 -* (((
199 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
200 -)))
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.
201 201  
202 -(((
179 +
203 203  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
204 -)))
205 205  
206 -(((
207 207  N95S31B supports different communication protocol such as :
208 -)))
209 209  
210 210  (((
211 -* (((
212 -CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
213 -)))
214 -* (((
215 -raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
216 -)))
217 -* (((
218 -MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
219 -)))
220 -* (((
221 -TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
222 -)))
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(%%))
223 223  
224 -(((
225 225  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.
226 -)))
227 227  
228 228  
229 229  )))
... ... @@ -338,7 +338,7 @@
338 338  
339 339  === 2.2.7  Use MQTT protocol to uplink data ===
340 340  
341 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
305 +N95S31B supports only plain MQTT now it doesn’t support TLS and other related encryption.
342 342  
343 343  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
344 344  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
... ... @@ -345,8 +345,8 @@
345 345  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
346 346  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
347 347  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
348 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
349 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
312 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527  **(%%)~/~/Set the sending topic of MQTT
313 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527  **(%%) ~/~/Set the subscription topic of MQTT
350 350  
351 351  [[image:1657352634421-276.png]]
352 352  
... ... @@ -364,21 +364,20 @@
364 364  
365 365  
366 366  
367 -=== 2.2.8  Use TCP protocol to uplink data ===
331 +=== 2.2.7 Use TCP protocol to uplink data ===
368 368  
369 -This feature is supported since firmware version v110
370 370  
371 371  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
372 372  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
373 373  
374 -[[image:1657352898400-901.png]]
337 +[[image:image-20220709093918-1.png]]
375 375  
376 376  
377 -[[image:1657352914475-252.png]]
340 +[[image:image-20220709093918-2.png]]
378 378  
379 379  
380 380  
381 -=== 2.2.9  Change Update Interval ===
344 +=== 2.2.8 Change Update Interval ===
382 382  
383 383  User can use below command to change the (% style="color:green" %)**uplink interval**.
384 384  
... ... @@ -385,51 +385,59 @@
385 385  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
386 386  
387 387  (((
388 -
351 +(% style="color:red" %)**NOTE:**
389 389  )))
390 390  
354 +(((
355 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
356 +)))
391 391  
392 392  
359 +
393 393  == 2.3  Uplink Payload ==
394 394  
362 +In this mode, uplink payload includes in total 14 bytes
395 395  
396 -(((
397 -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.
398 -)))
399 399  
365 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
366 +|=(% style="width: 60px;" %)(((
367 +**Size(bytes)**
368 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
369 +|(% 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"]]
400 400  
401 401  (((
402 -For example:
372 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
403 403  )))
404 404  
405 -(((
406 - (% 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.
407 -)))
408 408  
376 +[[image:1657331036973-987.png]]
409 409  
410 410  (((
411 -The uplink payloads are composed in  ASCII String. For example:
379 +The payload is ASCII string, representative same HEX:
412 412  )))
413 413  
414 414  (((
415 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
383 +0x72403155615900640c6c19029200 where:
416 416  )))
417 417  
418 -(((
419 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
386 +* (((
387 +Device ID: 0x724031556159 = 724031556159
420 420  )))
421 -
422 -
423 -(((
424 -(% style="color:red" %)**NOTE:**
389 +* (((
390 +Version: 0x0064=100=1.0.0
425 425  )))
426 426  
427 -(% style="color:red" %)
428 -1. (((
429 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
393 +* (((
394 +BAT: 0x0c6c = 3180 mV = 3.180V
430 430  )))
431 -1. (((
432 -By default, the device will send an uplink message every 1 hour.
396 +* (((
397 +Signal: 0x19 = 25
398 +)))
399 +* (((
400 +Distance: 0x0292= 658 mm
401 +)))
402 +* (((
403 +Interrupt: 0x00 = 0
433 433  
434 434  
435 435  
... ... @@ -436,108 +436,105 @@
436 436  
437 437  )))
438 438  
439 -=== 2.3.1  Payload Analyze ===
410 +== 2.4  Payload Explanation and Sensor Interface ==
440 440  
441 -N95S31B uplink payload includes in total 21 bytes
442 442  
413 +=== 2.4.1  Device ID ===
443 443  
444 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
445 -|=(% style="width: 60px;" %)(((
446 -**Size(bytes)**
447 -)))|=(% 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**
448 -|(% 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" %)(((
449 449  (((
450 -Reserve/ Same as NBSN95 CFGMOD=1
416 +By default, the Device ID equal to the last 6 bytes of IMEI.
451 451  )))
452 452  
453 453  (((
454 -No function here.
420 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
455 455  )))
456 -)))|(% style="width:77px" %)(((
422 +
457 457  (((
458 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
424 +**Example:**
459 459  )))
460 460  
461 461  (((
462 -By SHT31
428 +AT+DEUI=A84041F15612
463 463  )))
464 -)))|(% style="width:80px" %)(((
430 +
465 465  (((
466 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
432 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
467 467  )))
468 468  
435 +
436 +
437 +=== 2.4.2  Version Info ===
438 +
469 469  (((
470 -By SHT31
440 +Specify the software version: 0x64=100, means firmware version 1.00.
471 471  )))
472 -)))
473 473  
474 474  (((
475 -(((
476 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
444 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
477 477  )))
478 -)))
479 479  
480 480  
481 -[[image:1657354294009-643.png]]
482 482  
449 +=== 2.4.3  Battery Info ===
483 483  
484 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
451 +(((
452 +Ex1: 0x0B45 = 2885mV
453 +)))
485 485  
486 -* Device ID: 0x724031607457 = 724031607457
487 -* Version: 0x006e=110=1.1.0
455 +(((
456 +Ex2: 0x0B49 = 2889mV
457 +)))
488 488  
489 -* BAT: 0x0ccd = 3277 mV = 3.277V
490 -* Signal: 0x1b = 27
491 -* Model: 0x01 = 1
492 -* 0x00dc000ccc= reserve, ignore in N95S31B
493 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
494 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
495 495  
460 +
461 +=== 2.4.4  Signal Strength ===
462 +
496 496  (((
497 -
464 +NB-IoT Network signal Strength.
498 498  )))
499 499  
500 500  (((
501 -
468 +**Ex1: 0x1d = 29**
502 502  )))
503 503  
504 -
505 -=== 2.3.2  Device ID ===
506 -
507 507  (((
508 -By default, the Device ID equal to the last 6 bytes of IMEI.
472 +(% style="color:blue" %)**0**(%%)  -113dBm or less
509 509  )))
510 510  
511 511  (((
512 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
476 +(% style="color:blue" %)**1**(%%)  -111dBm
513 513  )))
514 514  
515 515  (((
516 -**Example:**
480 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
517 517  )))
518 518  
519 519  (((
520 -AT+DEUI=A84041F15612
484 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
521 521  )))
522 522  
523 523  (((
524 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
488 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
525 525  )))
526 526  
527 527  
528 528  
529 -=== 2.3.3  Version Info ===
493 +=== 2.4.5  Distance ===
530 530  
495 +Get the distance. Flat object range 280mm - 7500mm.
496 +
531 531  (((
532 -These bytes include the hardware and software version.
498 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
533 533  )))
534 534  
535 535  (((
536 -Higher byte: Specify hardware version: always 0x00 for N95S31B
502 +(((
503 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
537 537  )))
505 +)))
538 538  
539 539  (((
540 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110
508 +
541 541  )))
542 542  
543 543  (((
... ... @@ -544,81 +544,65 @@
544 544  
545 545  )))
546 546  
515 +=== 2.4.6  Digital Interrupt ===
516 +
547 547  (((
548 -For example: 0x00 6E: this device is N95S31B with firmware version 110.
518 +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.
549 549  )))
550 550  
551 551  (((
552 -
522 +The command is:
553 553  )))
554 554  
555 -
556 -=== 2.3.4  Battery Info ===
557 -
558 558  (((
559 -Ex1: 0x0B45 = 2885mV
526 +(% 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]])**.**
560 560  )))
561 561  
529 +
562 562  (((
563 -Ex2: 0x0B49 = 2889mV
531 +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.
564 564  )))
565 565  
566 566  
567 -
568 -=== 2.3.5  Signal Strength ===
569 -
570 570  (((
571 -NB-IoT Network signal Strength.
536 +Example:
572 572  )))
573 573  
574 574  (((
575 -**Ex1: 0x1d = 29**
540 +0x(00): Normal uplink packet.
576 576  )))
577 577  
578 578  (((
579 -(% style="color:blue" %)**0**(%%)  -113dBm or less
544 +0x(01): Interrupt Uplink Packet.
580 580  )))
581 581  
547 +
548 +
549 +=== 2.4.7  ​+5V Output ===
550 +
582 582  (((
583 -(% style="color:blue" %)**1**(%%)  -111dBm
552 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
584 584  )))
585 585  
555 +
586 586  (((
587 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
557 +The 5V output time can be controlled by AT Command.
588 588  )))
589 589  
590 590  (((
591 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
561 +(% style="color:blue" %)**AT+5VT=1000**
592 592  )))
593 593  
594 594  (((
595 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
565 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
596 596  )))
597 597  
598 598  
599 599  
600 -=== 2.3.6  Temperature & Humidity ===
570 +== 2.5  Downlink Payload ==
601 601  
602 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
572 +By default, NDDS75 prints the downlink payload to console port.
603 603  
604 -[[image:image-20220709161741-3.png]]
605 -
606 -
607 -Convert the read byte to decimal and divide it by ten.
608 -
609 -
610 -**Example:**
611 -
612 -Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
613 -
614 -Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
615 -
616 -
617 -
618 -== 2.4  Downlink Payload ==
619 -
620 -By default, N95S31B prints the downlink payload to console port.
621 -
622 622  [[image:image-20220709100028-1.png]]
623 623  
624 624  
... ... @@ -655,7 +655,7 @@
655 655  )))
656 656  
657 657  (((
658 -If payload = 0x04FF, it will reset the N95S31B
610 +If payload = 0x04FF, it will reset the NDDS75
659 659  )))
660 660  
661 661  
... ... @@ -667,16 +667,51 @@
667 667  
668 668  
669 669  
670 -== 2.5  ​Battery Analysis ==
622 +== 2.6  ​LED Indicator ==
671 671  
672 -=== 2.5.1  ​Battery Type ===
673 673  
625 +The NDDS75 has an internal LED which is to show the status of different state.
674 674  
627 +
628 +* 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)
629 +* Then the LED will be on for 1 second means device is boot normally.
630 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
631 +* For each uplink probe, LED will be on for 500ms.
632 +
675 675  (((
676 -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.
634 +
677 677  )))
678 678  
637 +
638 +
639 +== 2.7  ​Firmware Change Log ==
640 +
641 +
679 679  (((
643 +Download URL & Firmware Change log
644 +)))
645 +
646 +(((
647 +[[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/]]
648 +)))
649 +
650 +
651 +(((
652 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
653 +)))
654 +
655 +
656 +
657 +== 2.8  ​Battery Analysis ==
658 +
659 +=== 2.8.1  ​Battery Type ===
660 +
661 +
662 +(((
663 +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.
664 +)))
665 +
666 +(((
680 680  The battery is designed to last for several years depends on the actually use environment and update interval. 
681 681  )))
682 682  
... ... @@ -694,35 +694,56 @@
694 694  
695 695  
696 696  
697 -=== 2.5.2  Power consumption Analyze ===
684 +=== 2.8.2  Power consumption Analyze ===
698 698  
699 699  (((
700 -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.
687 +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.
701 701  )))
702 702  
690 +
703 703  (((
704 -
692 +Instruction to use as below:
705 705  )))
706 706  
695 +(((
696 +(% 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/]]
697 +)))
707 707  
708 -=== 2.5.3  ​Battery Note ===
709 709  
710 710  (((
711 -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.
701 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
712 712  )))
713 713  
704 +* (((
705 +Product Model
706 +)))
707 +* (((
708 +Uplink Interval
709 +)))
710 +* (((
711 +Working Mode
712 +)))
714 714  
714 +(((
715 +And the Life expectation in difference case will be shown on the right.
716 +)))
715 715  
716 -=== 2.5.4  Replace the battery ===
718 +[[image:image-20220709110451-3.png]]
717 717  
718 718  
721 +
722 +=== 2.8.3  ​Battery Note ===
723 +
719 719  (((
720 -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.
725 +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.
721 721  )))
722 722  
723 723  
729 +
730 +=== 2.8.4  Replace the battery ===
731 +
724 724  (((
725 -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).
733 +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).
726 726  )))
727 727  
728 728  
... ... @@ -745,7 +745,7 @@
745 745  
746 746  == 4.1  Access AT Commands ==
747 747  
748 -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/]]
756 +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/]]
749 749  
750 750  
751 751  AT+<CMD>?  : Help on <CMD>
... ... @@ -833,12 +833,8 @@
833 833  )))
834 834  
835 835  (((
836 -
837 -
838 -(((
839 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
844 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
840 840  )))
841 -)))
842 842  
843 843  
844 844  
... ... @@ -869,7 +869,7 @@
869 869  = 7. ​ Order Info =
870 870  
871 871  
872 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
876 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
873 873  
874 874  
875 875  (% class="wikigeneratedid" %)
... ... @@ -884,7 +884,7 @@
884 884  
885 885  (% style="color:#037691" %)**Package Includes**:
886 886  
887 -* N95S31B NB-IoT Temperature and Humidity Sensor
891 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
888 888  * External antenna x 1
889 889  )))
890 890  
... ... @@ -893,10 +893,11 @@
893 893  
894 894  (% style="color:#037691" %)**Dimension and weight**:
895 895  
900 +
896 896  * Device Size: 13.0 x 5 x 4.5 cm
897 897  * Device Weight: 150g
898 -* Package Size / pcs : 14.0 x 8x 5 cm
899 -* Weight / pcs : 180g
903 +* Package Size / pcs : 15 x 12x 5.5 cm
904 +* Weight / pcs : 220g
900 900  )))
901 901  
902 902  (((
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
1657520100595-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
image-20220709161741-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -111.2 KB
Content

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0