Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.29 >
edited by Xiaoling
on 2022/07/11 08:38
To version < 112.1 >
edited by Xiaoling
on 2022/07/09 15:48
>
Change comment: Uploaded new attachment "1657352898400-901.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
... ... @@ -68,7 +68,6 @@
68 68  
69 69  
70 70  
71 -
72 72  == 1.3  Specification ==
73 73  
74 74  
... ... @@ -77,7 +77,6 @@
77 77  * Supply Voltage: 2.1v ~~ 3.6v
78 78  * Operating Temperature: -40 ~~ 85°C
79 79  
80 -
81 81  (% style="color:#037691" %)**NB-IoT Spec:**
82 82  
83 83  * - B1 @H-FDD: 2100MHz
... ... @@ -87,9 +87,9 @@
87 87  * - B20 @H-FDD: 800MHz
88 88  * - B28 @H-FDD: 700MHz
89 89  
90 -
91 91  (% style="color:#037691" %)**Battery:**
92 92  
77 +
93 93  * Li/SOCI2 un-chargeable battery
94 94  * Capacity: 8500mAh
95 95  * Self Discharge: <1% / Year @ 25°C
... ... @@ -98,7 +98,6 @@
98 98  
99 99  
100 100  
101 -
102 102  == ​1.4  Applications ==
103 103  
104 104  * Smart Buildings & Home Automation
... ... @@ -127,13 +127,9 @@
127 127  
128 128  === 1.5.2 BOOT MODE / SW1 ===
129 129  
130 -(((
131 131  1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
132 -)))
133 133  
134 -(((
135 135  2) Flash: work mode, device starts to work and send out console output for further debug
136 -)))
137 137  
138 138  
139 139  
... ... @@ -150,6 +150,9 @@
150 150  1. When boot the device in flash mode
151 151  1. Send an uplink packet
152 152  
133 +
134 +
135 +
153 153  = 2.  Use N95S31B to communicate with IoT Server =
154 154  
155 155  == 2.1  How it works ==
... ... @@ -193,6 +193,7 @@
193 193  * The local NB-IoT network used the band that N95S31B supports.
194 194  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
195 195  
179 +
196 196  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
197 197  
198 198  N95S31B supports different communication protocol such as :
... ... @@ -318,7 +318,7 @@
318 318  
319 319  === 2.2.7  Use MQTT protocol to uplink data ===
320 320  
321 -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.
322 322  
323 323  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
324 324  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
... ... @@ -325,8 +325,8 @@
325 325  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
326 326  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
327 327  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
328 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
329 -* (% 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
330 330  
331 331  [[image:1657352634421-276.png]]
332 332  
... ... @@ -344,21 +344,20 @@
344 344  
345 345  
346 346  
347 -=== 2.2.8  Use TCP protocol to uplink data ===
331 +=== 2.2.7 Use TCP protocol to uplink data ===
348 348  
349 -This feature is supported since firmware version v110
350 350  
351 351  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
352 352  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
353 353  
354 -[[image:1657352898400-901.png]]
337 +[[image:image-20220709093918-1.png]]
355 355  
356 356  
357 -[[image:1657352914475-252.png]]
340 +[[image:image-20220709093918-2.png]]
358 358  
359 359  
360 360  
361 -=== 2.2.9  Change Update Interval ===
344 +=== 2.2.8 Change Update Interval ===
362 362  
363 363  User can use below command to change the (% style="color:green" %)**uplink interval**.
364 364  
... ... @@ -365,207 +365,227 @@
365 365  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
366 366  
367 367  (((
368 -
351 +(% style="color:red" %)**NOTE:**
369 369  )))
370 370  
354 +(((
355 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
356 +)))
371 371  
372 372  
359 +
373 373  == 2.3  Uplink Payload ==
374 374  
362 +In this mode, uplink payload includes in total 14 bytes
375 375  
376 -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.
377 377  
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"]]
378 378  
379 -For example:
371 +(((
372 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
373 +)))
380 380  
381 - (% 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.
382 382  
376 +[[image:1657331036973-987.png]]
383 383  
384 -The uplink payloads are composed in  ASCII String. For example:
378 +(((
379 +The payload is ASCII string, representative same HEX:
380 +)))
385 385  
386 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
382 +(((
383 +0x72403155615900640c6c19029200 where:
384 +)))
387 387  
388 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
386 +* (((
387 +Device ID: 0x724031556159 = 724031556159
388 +)))
389 +* (((
390 +Version: 0x0064=100=1.0.0
391 +)))
389 389  
393 +* (((
394 +BAT: 0x0c6c = 3180 mV = 3.180V
395 +)))
396 +* (((
397 +Signal: 0x19 = 25
398 +)))
399 +* (((
400 +Distance: 0x0292= 658 mm
401 +)))
402 +* (((
403 +Interrupt: 0x00 = 0
390 390  
391 -(% style="color:red" %)**NOTE:**
392 392  
393 -(% style="color:red" %)
394 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
395 -1. By default, the device will send an uplink message every 1 hour.
396 396  
407 +
408 +)))
397 397  
398 -=== 2.3.1  Payload Analyze ===
410 +== 2.4  Payload Explanation and Sensor Interface ==
399 399  
400 -N95S31B uplink payload includes in total 21 bytes
401 401  
413 +=== 2.4.1  Device ID ===
402 402  
403 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
404 -|=(% style="width: 60px;" %)(((
405 -**Size(bytes)**
406 -)))|=(% 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**
407 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
408 408  (((
409 -Reserve/ Same as NBSN95 CFGMOD=1
416 +By default, the Device ID equal to the last 6 bytes of IMEI.
410 410  )))
411 411  
412 412  (((
413 -No function here.
420 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
414 414  )))
415 -)))|(% style="width:77px" %)(((
422 +
416 416  (((
417 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
424 +**Example:**
418 418  )))
419 419  
420 420  (((
421 -By SHT31
428 +AT+DEUI=A84041F15612
422 422  )))
423 -)))|(% style="width:80px" %)(((
430 +
424 424  (((
425 -[[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.
426 426  )))
427 427  
435 +
436 +
437 +=== 2.4.2  Version Info ===
438 +
428 428  (((
429 -By SHT31
440 +Specify the software version: 0x64=100, means firmware version 1.00.
430 430  )))
431 -)))
432 432  
433 433  (((
434 -(((
435 -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.
436 436  )))
437 -)))
438 438  
439 439  
440 -[[image:1657354294009-643.png]]
441 441  
449 +=== 2.4.3  Battery Info ===
442 442  
443 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
444 -
445 -* Device ID: 0x724031607457 = 724031607457
446 -* Version: 0x006e=110=1.1.0
447 -
448 -* BAT: 0x0ccd = 3277 mV = 3.277V
449 -* Signal: 0x1b = 27
450 -* Model: 0x01 = 1
451 -* 0x00dc000ccc= reserve, ignore in N95S31B
452 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
453 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
454 -
455 455  (((
456 -
452 +Ex1: 0x0B45 = 2885mV
457 457  )))
458 458  
459 459  (((
460 -
456 +Ex2: 0x0B49 = 2889mV
461 461  )))
462 462  
463 463  
464 -=== 2.3.2  Device ID ===
465 465  
461 +=== 2.4.4  Signal Strength ===
462 +
466 466  (((
467 -By default, the Device ID equal to the last 6 bytes of IMEI.
464 +NB-IoT Network signal Strength.
468 468  )))
469 469  
470 470  (((
471 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
468 +**Ex1: 0x1d = 29**
472 472  )))
473 473  
474 474  (((
475 -**Example:**
472 +(% style="color:blue" %)**0**(%%)  -113dBm or less
476 476  )))
477 477  
478 478  (((
479 -AT+DEUI=A84041F15612
476 +(% style="color:blue" %)**1**(%%)  -111dBm
480 480  )))
481 481  
482 482  (((
483 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
480 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
484 484  )))
485 485  
483 +(((
484 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
485 +)))
486 486  
487 +(((
488 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
489 +)))
487 487  
488 -=== 2.3.3  Version Info ===
489 489  
490 490  
491 -These bytes include the hardware and software version.
493 +=== 2.4.5  Distance ===
492 492  
493 -Higher byte: Specify hardware version: always 0x00 for N95S31B
495 +Get the distance. Flat object range 280mm - 7500mm.
494 494  
495 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110
497 +(((
498 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
499 +)))
496 496  
497 -
498 -For example: 0x00 6E: this device is N95S31B with firmware version 110.
499 -
500 500  (((
501 -
502 +(((
503 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
502 502  )))
505 +)))
503 503  
504 -
505 -=== 2.3.4  Battery Info ===
506 -
507 507  (((
508 -Ex1: 0x0B45 = 2885mV
508 +
509 509  )))
510 510  
511 511  (((
512 -Ex2: 0x0B49 = 2889mV
512 +
513 513  )))
514 514  
515 +=== 2.4.6  Digital Interrupt ===
515 515  
516 -
517 -=== 2.3.5  Signal Strength ===
518 -
519 519  (((
520 -NB-IoT Network signal Strength.
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.
521 521  )))
522 522  
523 523  (((
524 -**Ex1: 0x1d = 29**
522 +The command is:
525 525  )))
526 526  
527 527  (((
528 -(% style="color:blue" %)**0**(%%)  -113dBm or less
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]])**.**
529 529  )))
530 530  
529 +
531 531  (((
532 -(% style="color:blue" %)**1**(%%)  -111dBm
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.
533 533  )))
534 534  
534 +
535 535  (((
536 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
536 +Example:
537 537  )))
538 538  
539 539  (((
540 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
540 +0x(00): Normal uplink packet.
541 541  )))
542 542  
543 543  (((
544 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
544 +0x(01): Interrupt Uplink Packet.
545 545  )))
546 546  
547 547  
548 548  
549 -=== 2.3.6  Temperature & Humidity ===
549 +=== 2.4.7  ​+5V Output ===
550 550  
551 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
551 +(((
552 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
553 +)))
552 552  
553 -[[image:image-20220709161741-3.png]]
554 554  
556 +(((
557 +The 5V output time can be controlled by AT Command.
558 +)))
555 555  
556 -Convert the read byte to decimal and divide it by ten.
560 +(((
561 +(% style="color:blue" %)**AT+5VT=1000**
562 +)))
557 557  
564 +(((
565 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
566 +)))
558 558  
559 -**Example:**
560 560  
561 -Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
562 562  
563 -Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
570 +== 2.5  Downlink Payload ==
564 564  
565 -
566 -
567 -== 2.4  Downlink Payload ==
568 -
569 569  By default, NDDS75 prints the downlink payload to console port.
570 570  
571 571  [[image:image-20220709100028-1.png]]
... ... @@ -616,16 +616,51 @@
616 616  
617 617  
618 618  
619 -== 2.5  ​Battery Analysis ==
622 +== 2.6  ​LED Indicator ==
620 620  
621 -=== 2.5.1  ​Battery Type ===
622 622  
625 +The NDDS75 has an internal LED which is to show the status of different state.
623 623  
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 +
624 624  (((
625 -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 +
626 626  )))
627 627  
637 +
638 +
639 +== 2.7  ​Firmware Change Log ==
640 +
641 +
628 628  (((
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 +(((
629 629  The battery is designed to last for several years depends on the actually use environment and update interval. 
630 630  )))
631 631  
... ... @@ -643,35 +643,56 @@
643 643  
644 644  
645 645  
646 -=== 2.5.2  Power consumption Analyze ===
684 +=== 2.8.2  Power consumption Analyze ===
647 647  
648 648  (((
649 -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.
650 650  )))
651 651  
690 +
652 652  (((
653 -
692 +Instruction to use as below:
654 654  )))
655 655  
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 +)))
656 656  
657 -=== 2.5.3  ​Battery Note ===
658 658  
659 659  (((
660 -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
661 661  )))
662 662  
704 +* (((
705 +Product Model
706 +)))
707 +* (((
708 +Uplink Interval
709 +)))
710 +* (((
711 +Working Mode
712 +)))
663 663  
714 +(((
715 +And the Life expectation in difference case will be shown on the right.
716 +)))
664 664  
665 -=== 2.5.4  Replace the battery ===
718 +[[image:image-20220709110451-3.png]]
666 666  
667 667  
721 +
722 +=== 2.8.3  ​Battery Note ===
723 +
668 668  (((
669 -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.
670 670  )))
671 671  
672 672  
729 +
730 +=== 2.8.4  Replace the battery ===
731 +
673 673  (((
674 -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).
675 675  )))
676 676  
677 677  
... ... @@ -694,7 +694,7 @@
694 694  
695 695  == 4.1  Access AT Commands ==
696 696  
697 -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/]]
698 698  
699 699  
700 700  AT+<CMD>?  : Help on <CMD>
... ... @@ -782,9 +782,7 @@
782 782  )))
783 783  
784 784  (((
785 -
786 -
787 -(% 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.
788 788  )))
789 789  
790 790  
... ... @@ -816,7 +816,7 @@
816 816  = 7. ​ Order Info =
817 817  
818 818  
819 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
876 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
820 820  
821 821  
822 822  (% class="wikigeneratedid" %)
... ... @@ -831,7 +831,7 @@
831 831  
832 832  (% style="color:#037691" %)**Package Includes**:
833 833  
834 -* N95S31B NB-IoT Temperature and Humidity Sensor
891 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
835 835  * External antenna x 1
836 836  )))
837 837  
... ... @@ -840,10 +840,11 @@
840 840  
841 841  (% style="color:#037691" %)**Dimension and weight**:
842 842  
900 +
843 843  * Device Size: 13.0 x 5 x 4.5 cm
844 844  * Device Weight: 150g
845 -* Package Size / pcs : 14.0 x 8x 5 cm
846 -* Weight / pcs : 180g
903 +* Package Size / pcs : 15 x 12x 5.5 cm
904 +* Weight / pcs : 220g
847 847  )))
848 848  
849 849  (((
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