Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 116.2 >
edited by Xiaoling
on 2022/07/11 09:42
To version < 110.1 >
edited by Xiaoling
on 2022/07/09 15:43
>
Change comment: Uploaded new attachment "1657352634421-276.png", version {1}

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
... ... @@ -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 ==
... ... @@ -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  )))
... ... @@ -329,16 +329,15 @@
329 329  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
330 330  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
331 331  
332 -[[image:1657352391268-297.png]]
296 +[[image:1657330501006-241.png]]
333 333  
334 334  
335 -[[image:1657352403317-397.png]]
299 +[[image:1657330533775-472.png]]
336 336  
337 337  
338 338  
339 -=== 2.2.7  Use MQTT protocol to uplink data ===
303 +=== 2.2.6 Use MQTT protocol to uplink data ===
340 340  
341 -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,40 +345,35 @@
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
311 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
312 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
350 350  
351 -[[image:1657352634421-276.png]]
314 +[[image:1657249978444-674.png]]
352 352  
353 353  
354 -[[image:1657352645687-385.png]]
317 +[[image:1657330723006-866.png]]
355 355  
356 -(((
357 -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.
358 -)))
359 359  
360 -
361 361  (((
362 -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.
321 +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.
363 363  )))
364 364  
365 365  
366 366  
367 -=== 2.2.8  Use TCP protocol to uplink data ===
326 +=== 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]]
332 +[[image:image-20220709093918-1.png]]
375 375  
376 376  
377 -[[image:1657352914475-252.png]]
335 +[[image:image-20220709093918-2.png]]
378 378  
379 379  
380 380  
381 -=== 2.2.9  Change Update Interval ===
339 +=== 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,158 +385,164 @@
385 385  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
386 386  
387 387  (((
388 -
346 +(% style="color:red" %)**NOTE:**
389 389  )))
390 390  
349 +(((
350 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
351 +)))
391 391  
392 392  
354 +
393 393  == 2.3  Uplink Payload ==
394 394  
357 +In this mode, uplink payload includes in total 14 bytes
395 395  
396 -(((
397 -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.
398 -)))
399 399  
360 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
361 +|=(% style="width: 60px;" %)(((
362 +**Size(bytes)**
363 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
364 +|(% 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:
367 +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 NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
407 -)))
408 408  
371 +[[image:1657331036973-987.png]]
409 409  
410 410  (((
411 -The uplink payloads are composed in  ASCII String. For example:
374 +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:
378 +0x72403155615900640c6c19029200 where:
416 416  )))
417 417  
418 -(((
419 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
381 +* (((
382 +Device ID: 0x724031556159 = 724031556159
420 420  )))
421 -
422 -
423 -(((
424 -(% style="color:red" %)**NOTE:**
384 +* (((
385 +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"]].
388 +* (((
389 +BAT: 0x0c6c = 3180 mV = 3.180V
430 430  )))
431 -1. (((
432 -By default, the device will send an uplink message every 1 hour.
391 +* (((
392 +Signal: 0x19 = 25
433 433  )))
394 +* (((
395 +Distance: 0x0292= 658 mm
396 +)))
397 +* (((
398 +Interrupt: 0x00 = 0
434 434  
435 435  
436 436  
437 -=== 2.3.1  Payload Analyze ===
402 +
403 +)))
438 438  
439 -N95S31B uplink payload includes in total 21 bytes
405 +== 2.4  Payload Explanation and Sensor Interface ==
440 440  
441 441  
442 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
443 -|=(% style="width: 60px;" %)(((
444 -**Size(bytes)**
445 -)))|=(% 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**
446 -|(% 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 +=== 2.4.1  Device ID ===
409 +
447 447  (((
448 -Reserve/ Same as NBSN95 CFGMOD=1
411 +By default, the Device ID equal to the last 6 bytes of IMEI.
449 449  )))
450 450  
451 451  (((
452 -No function here.
415 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
453 453  )))
454 -)))|(% style="width:77px" %)(((
417 +
455 455  (((
456 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
419 +**Example:**
457 457  )))
458 458  
459 459  (((
460 -By SHT31
423 +AT+DEUI=A84041F15612
461 461  )))
462 -)))|(% style="width:80px" %)(((
425 +
463 463  (((
464 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
427 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
465 465  )))
466 466  
430 +
431 +
432 +=== 2.4.2  Version Info ===
433 +
467 467  (((
468 -By SHT31
435 +Specify the software version: 0x64=100, means firmware version 1.00.
469 469  )))
470 -)))
471 471  
472 472  (((
473 -(((
474 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
439 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
475 475  )))
476 -)))
477 477  
478 478  
479 -[[image:1657354294009-643.png]]
480 480  
444 +=== 2.4.3  Battery Info ===
481 481  
482 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
446 +(((
447 +Ex1: 0x0B45 = 2885mV
448 +)))
483 483  
484 -* Device ID: 0x724031607457 = 724031607457
485 -* Version: 0x006e=110=1.1.0
450 +(((
451 +Ex2: 0x0B49 = 2889mV
452 +)))
486 486  
487 -* BAT: 0x0ccd = 3277 mV = 3.277V
488 -* Signal: 0x1b = 27
489 -* Model: 0x01 = 1
490 -* 0x00dc000ccc= reserve, ignore in N95S31B
491 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
492 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
493 493  
455 +
456 +=== 2.4.4  Signal Strength ===
457 +
494 494  (((
495 -
459 +NB-IoT Network signal Strength.
496 496  )))
497 497  
498 498  (((
499 -
463 +**Ex1: 0x1d = 29**
500 500  )))
501 501  
502 -
503 -=== 2.3.2  Device ID ===
504 -
505 505  (((
506 -By default, the Device ID equal to the last 6 bytes of IMEI.
467 +(% style="color:blue" %)**0**(%%)  -113dBm or less
507 507  )))
508 508  
509 509  (((
510 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
471 +(% style="color:blue" %)**1**(%%)  -111dBm
511 511  )))
512 512  
513 513  (((
514 -**Example:**
475 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
515 515  )))
516 516  
517 517  (((
518 -AT+DEUI=A84041F15612
479 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
519 519  )))
520 520  
521 521  (((
522 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
483 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
523 523  )))
524 524  
525 525  
526 526  
527 -=== 2.3.3  Version Info ===
488 +=== 2.4.5  Distance ===
528 528  
490 +Get the distance. Flat object range 280mm - 7500mm.
529 529  
530 530  (((
531 -These bytes include the hardware and software version.
493 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
532 532  )))
533 533  
534 534  (((
535 -Higher byte: Specify hardware version: always 0x00 for N95S31B
497 +(((
498 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
536 536  )))
500 +)))
537 537  
538 538  (((
539 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110
503 +
540 540  )))
541 541  
542 542  (((
... ... @@ -543,79 +543,63 @@
543 543  
544 544  )))
545 545  
510 +=== 2.4.6  Digital Interrupt ===
511 +
546 546  (((
547 -For example: 0x00 6E: this device is N95S31B with firmware version 110.
513 +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.
548 548  )))
549 549  
550 550  (((
551 -
517 +The command is:
552 552  )))
553 553  
554 -
555 -=== 2.3.4  Battery Info ===
556 -
557 557  (((
558 -Ex1: 0x0B45 = 2885mV
521 +(% 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]])**.**
559 559  )))
560 560  
524 +
561 561  (((
562 -Ex2: 0x0B49 = 2889mV
526 +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.
563 563  )))
564 564  
565 565  
566 -
567 -=== 2.3.5  Signal Strength ===
568 -
569 569  (((
570 -NB-IoT Network signal Strength.
531 +Example:
571 571  )))
572 572  
573 573  (((
574 -**Ex1: 0x1d = 29**
535 +0x(00): Normal uplink packet.
575 575  )))
576 576  
577 577  (((
578 -(% style="color:blue" %)**0**(%%)  -113dBm or less
539 +0x(01): Interrupt Uplink Packet.
579 579  )))
580 580  
542 +
543 +
544 +=== 2.4.7  ​+5V Output ===
545 +
581 581  (((
582 -(% style="color:blue" %)**1**(%%)  -111dBm
547 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
583 583  )))
584 584  
550 +
585 585  (((
586 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
552 +The 5V output time can be controlled by AT Command.
587 587  )))
588 588  
589 589  (((
590 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
556 +(% style="color:blue" %)**AT+5VT=1000**
591 591  )))
592 592  
593 593  (((
594 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
560 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
595 595  )))
596 596  
597 597  
598 598  
599 -=== 2.3.6  Temperature & Humidity ===
565 +== 2.5  Downlink Payload ==
600 600  
601 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
602 -
603 -[[image:image-20220709161741-3.png]]
604 -
605 -
606 -Convert the read byte to decimal and divide it by ten.
607 -
608 -
609 -**Example:**
610 -
611 -Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
612 -
613 -Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
614 -
615 -
616 -
617 -== 2.4  Downlink Payload ==
618 -
619 619  By default, NDDS75 prints the downlink payload to console port.
620 620  
621 621  [[image:image-20220709100028-1.png]]
... ... @@ -666,16 +666,51 @@
666 666  
667 667  
668 668  
669 -== 2.5  ​Battery Analysis ==
617 +== 2.6  ​LED Indicator ==
670 670  
671 -=== 2.5.1  ​Battery Type ===
672 672  
620 +The NDDS75 has an internal LED which is to show the status of different state.
673 673  
622 +
623 +* 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)
624 +* Then the LED will be on for 1 second means device is boot normally.
625 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
626 +* For each uplink probe, LED will be on for 500ms.
627 +
674 674  (((
675 -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.
629 +
676 676  )))
677 677  
632 +
633 +
634 +== 2.7  ​Firmware Change Log ==
635 +
636 +
678 678  (((
638 +Download URL & Firmware Change log
639 +)))
640 +
641 +(((
642 +[[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/]]
643 +)))
644 +
645 +
646 +(((
647 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
648 +)))
649 +
650 +
651 +
652 +== 2.8  ​Battery Analysis ==
653 +
654 +=== 2.8.1  ​Battery Type ===
655 +
656 +
657 +(((
658 +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.
659 +)))
660 +
661 +(((
679 679  The battery is designed to last for several years depends on the actually use environment and update interval. 
680 680  )))
681 681  
... ... @@ -693,35 +693,56 @@
693 693  
694 694  
695 695  
696 -=== 2.5.2  Power consumption Analyze ===
679 +=== 2.8.2  Power consumption Analyze ===
697 697  
698 698  (((
699 -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.
682 +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.
700 700  )))
701 701  
685 +
702 702  (((
703 -
687 +Instruction to use as below:
704 704  )))
705 705  
690 +(((
691 +(% 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/]]
692 +)))
706 706  
707 -=== 2.5.3  ​Battery Note ===
708 708  
709 709  (((
710 -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.
696 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
711 711  )))
712 712  
699 +* (((
700 +Product Model
701 +)))
702 +* (((
703 +Uplink Interval
704 +)))
705 +* (((
706 +Working Mode
707 +)))
713 713  
709 +(((
710 +And the Life expectation in difference case will be shown on the right.
711 +)))
714 714  
715 -=== 2.5.4  Replace the battery ===
713 +[[image:image-20220709110451-3.png]]
716 716  
717 717  
716 +
717 +=== 2.8.3  ​Battery Note ===
718 +
718 718  (((
719 -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.
720 +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.
720 720  )))
721 721  
722 722  
724 +
725 +=== 2.8.4  Replace the battery ===
726 +
723 723  (((
724 -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).
728 +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).
725 725  )))
726 726  
727 727  
... ... @@ -744,7 +744,7 @@
744 744  
745 745  == 4.1  Access AT Commands ==
746 746  
747 -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/]]
751 +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/]]
748 748  
749 749  
750 750  AT+<CMD>?  : Help on <CMD>
... ... @@ -832,12 +832,8 @@
832 832  )))
833 833  
834 834  (((
835 -
836 -
837 -(((
838 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
839 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
839 839  )))
840 -)))
841 841  
842 842  
843 843  
... ... @@ -868,7 +868,7 @@
868 868  = 7. ​ Order Info =
869 869  
870 870  
871 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
871 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
872 872  
873 873  
874 874  (% class="wikigeneratedid" %)
... ... @@ -883,7 +883,7 @@
883 883  
884 884  (% style="color:#037691" %)**Package Includes**:
885 885  
886 -* N95S31B NB-IoT Temperature and Humidity Sensor
886 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
887 887  * External antenna x 1
888 888  )))
889 889  
... ... @@ -892,10 +892,11 @@
892 892  
893 893  (% style="color:#037691" %)**Dimension and weight**:
894 894  
895 +
895 895  * Device Size: 13.0 x 5 x 4.5 cm
896 896  * Device Weight: 150g
897 -* Package Size / pcs : 14.0 x 8x 5 cm
898 -* Weight / pcs : 180g
898 +* Package Size / pcs : 15 x 12x 5.5 cm
899 +* Weight / pcs : 220g
899 899  )))
900 900  
901 901  (((
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

Applications

Navigation

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