<
From version < 114.2 >
edited by Xiaoling
on 2022/07/09 16:12
To version < 118.2 >
edited by Xiaoling
on 2022/07/11 14:15
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -9,6 +9,7 @@
9 9  
10 10  **Table of Contents:**
11 11  
12 +{{toc/}}
12 12  
13 13  
14 14  
... ... @@ -21,16 +21,29 @@
21 21  (((
22 22  
23 23  
25 +(((
24 24  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 +)))
25 25  
29 +(((
26 26  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 +)))
27 27  
33 +(((
28 28  N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
35 +)))
29 29  
37 +(((
30 30  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 +)))
31 31  
41 +(((
42 +
43 +)))
32 32  
45 +(((
33 33  ~* make sure you have NB-IoT coverage locally.
47 +)))
34 34  
35 35  
36 36  )))
... ... @@ -41,7 +41,6 @@
41 41  
42 42  == 1.2 ​ Features ==
43 43  
44 -
45 45  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
46 46  * Monitor Temperature & Humidity via SHT31
47 47  * AT Commands to change parameters
... ... @@ -54,6 +54,7 @@
54 54  * 8500mAh Battery for long term use
55 55  
56 56  
70 +
57 57  == 1.3  Specification ==
58 58  
59 59  
... ... @@ -73,7 +73,6 @@
73 73  
74 74  (% style="color:#037691" %)**Battery:**
75 75  
76 -
77 77  * Li/SOCI2 un-chargeable battery
78 78  * Capacity: 8500mAh
79 79  * Self Discharge: <1% / Year @ 25°C
... ... @@ -81,6 +81,7 @@
81 81  * Max boost current: 2A, 1 second
82 82  
83 83  
97 +
84 84  == ​1.4  Applications ==
85 85  
86 86  * Smart Buildings & Home Automation
... ... @@ -94,7 +94,7 @@
94 94  ​
95 95  
96 96  
97 -== 1.5  Pin Definitions ==
111 +== 1.5  Pin Definitions & Switch ==
98 98  
99 99  N95S31B use the mother board from NBSN95 which as below.
100 100  
... ... @@ -109,9 +109,13 @@
109 109  
110 110  === 1.5.2 BOOT MODE / SW1 ===
111 111  
126 +(((
112 112  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 +)))
113 113  
130 +(((
114 114  2) Flash: work mode, device starts to work and send out console output for further debug
132 +)))
115 115  
116 116  
117 117  
... ... @@ -148,7 +148,7 @@
148 148  
149 149  )))
150 150  
151 -[[image:1657350248151-650.png]]
169 +[[image:1657520100595-569.png]]
152 152  
153 153  (((
154 154  
... ... @@ -167,23 +167,45 @@
167 167  === 2.2.1 Test Requirement ===
168 168  
169 169  
188 +(((
170 170  To use N95S31B in your city, make sure meet below requirements:
190 +)))
171 171  
172 -* Your local operator has already distributed a NB-IoT Network there.
173 -* The local NB-IoT network used the band that N95S31B supports.
174 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
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 175  
202 +(((
176 176  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
204 +)))
177 177  
206 +(((
178 178  N95S31B supports different communication protocol such as :
208 +)))
179 179  
180 180  (((
181 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
182 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
183 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
184 -* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
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 185  
224 +(((
186 186  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 +)))
187 187  
188 188  
189 189  )))
... ... @@ -353,52 +353,79 @@
353 353  == 2.3  Uplink Payload ==
354 354  
355 355  
396 +(((
356 356  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 +)))
357 357  
358 358  
401 +(((
359 359  For example:
403 +)))
360 360  
405 +(((
361 361   (% 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 +)))
362 362  
363 363  
410 +(((
364 364  The uplink payloads are composed in  ASCII String. For example:
412 +)))
365 365  
414 +(((
366 366  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
416 +)))
367 367  
418 +(((
368 368  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
420 +)))
369 369  
370 370  
423 +(((
371 371  (% style="color:red" %)**NOTE:**
425 +)))
372 372  
373 373  (% style="color:red" %)
374 -1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
375 -1. By default, the device will send an uplink message every 1 hour.
428 +1. (((
429 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
430 +)))
431 +1. (((
432 +By default, the device will send an uplink message every 1 hour.
433 +)))
376 376  
377 -
378 -
379 -
380 380  === 2.3.1  Payload Analyze ===
381 381  
382 382  N95S31B uplink payload includes in total 21 bytes
383 383  
384 384  
385 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
440 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
386 386  |=(% style="width: 60px;" %)(((
387 387  **Size(bytes)**
388 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1**
389 -|(% 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:123px" %)MOD 0X01|(% style="width:99px" %)(((
443 +)))|=(% 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**
444 +|(% 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" %)(((
445 +(((
390 390  Reserve/ Same as NBSN95 CFGMOD=1
447 +)))
391 391  
449 +(((
392 392  No function here.
451 +)))
393 393  )))|(% style="width:77px" %)(((
394 -[[Temperature >>||anchor="H2.4.5A0Distance"]]
453 +(((
454 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
455 +)))
395 395  
457 +(((
396 396  By SHT31
459 +)))
397 397  )))|(% style="width:80px" %)(((
398 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
461 +(((
462 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
463 +)))
399 399  
465 +(((
400 400  By SHT31
401 401  )))
468 +)))
402 402  
403 403  (((
404 404  (((
... ... @@ -409,43 +409,30 @@
409 409  
410 410  [[image:1657354294009-643.png]]
411 411  
412 -(((
413 -The payload is ASCII string, representative same HEX:
414 -)))
415 415  
416 -(((
417 -0x72403155615900640c6c19029200 where:
418 -)))
480 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
419 419  
420 -* (((
421 -Device ID: 0x724031556159 = 724031556159
422 -)))
423 -* (((
424 -Version: 0x0064=100=1.0.0
425 -)))
482 +* Device ID: 0x724031607457 = 724031607457
483 +* Version: 0x006e=110=1.1.0
426 426  
427 -* (((
428 -BAT: 0x0c6c = 3180 mV = 3.180V
485 +* BAT: 0x0ccd = 3277 mV = 3.277V
486 +* Signal: 0x1b = 27
487 +* Model: 0x01 = 1
488 +* 0x00dc000ccc= reserve, ignore in N95S31B
489 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
490 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
491 +
492 +(((
493 +
429 429  )))
430 -* (((
431 -Signal: 0x19 = 25
432 -)))
433 -* (((
434 -Distance: 0x0292= 658 mm
435 -)))
436 -* (((
437 -Interrupt: 0x00 = 0
438 438  
439 -
440 -
496 +(((
441 441  
442 442  )))
443 443  
444 -== 2.4  Payload Explanation and Sensor Interface ==
445 445  
501 +=== 2.3.2  Device ID ===
446 446  
447 -=== 2.4.1  Device ID ===
448 -
449 449  (((
450 450  By default, the Device ID equal to the last 6 bytes of IMEI.
451 451  )))
... ... @@ -468,141 +468,97 @@
468 468  
469 469  
470 470  
471 -=== 2.4.2  Version Info ===
525 +=== 2.3.3  Version Info ===
472 472  
473 473  (((
474 -Specify the software version: 0x64=100, means firmware version 1.00.
528 +These bytes include the hardware and software version.
475 475  )))
476 476  
477 477  (((
478 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
532 +Higher byte: Specify hardware version: always 0x00 for N95S31B
479 479  )))
480 480  
481 -
482 -
483 -=== 2.4.3  Battery Info ===
484 -
485 485  (((
486 -Ex1: 0x0B45 = 2885mV
536 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
487 487  )))
488 488  
489 489  (((
490 -Ex2: 0x0B49 = 2889mV
540 +
491 491  )))
492 492  
493 -
494 -
495 -=== 2.4.4  Signal Strength ===
496 -
497 497  (((
498 -NB-IoT Network signal Strength.
544 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
499 499  )))
500 500  
501 501  (((
502 -**Ex1: 0x1d = 29**
548 +
503 503  )))
504 504  
505 -(((
506 -(% style="color:blue" %)**0**(%%)  -113dBm or less
507 -)))
508 508  
509 -(((
510 -(% style="color:blue" %)**1**(%%)  -111dBm
511 -)))
552 +=== 2.3.4  Battery Info ===
512 512  
513 513  (((
514 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
555 +Ex1: 0x0B45 = 2885mV
515 515  )))
516 516  
517 517  (((
518 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
559 +Ex2: 0x0B49 = 2889mV
519 519  )))
520 520  
521 -(((
522 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
523 -)))
524 524  
525 525  
564 +=== 2.3.5  Signal Strength ===
526 526  
527 -=== 2.4.5  Distance ===
528 -
529 -Get the distance. Flat object range 280mm - 7500mm.
530 -
531 531  (((
532 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
567 +NB-IoT Network signal Strength.
533 533  )))
534 534  
535 535  (((
536 -(((
537 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
571 +**Ex1: 0x1d = 29**
538 538  )))
539 -)))
540 540  
541 541  (((
542 -
575 +(% style="color:blue" %)**0**(%%)  -113dBm or less
543 543  )))
544 544  
545 545  (((
546 -
579 +(% style="color:blue" %)**1**(%%)  -111dBm
547 547  )))
548 548  
549 -=== 2.4.6  Digital Interrupt ===
550 -
551 551  (((
552 -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.
583 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
553 553  )))
554 554  
555 555  (((
556 -The command is:
587 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
557 557  )))
558 558  
559 559  (((
560 -(% 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]])**.**
591 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
561 561  )))
562 562  
563 563  
564 -(((
565 -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.
566 -)))
567 567  
596 +=== 2.3.6  Temperature & Humidity ===
568 568  
569 -(((
570 -Example:
571 -)))
598 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
572 572  
573 -(((
574 -0x(00): Normal uplink packet.
575 -)))
600 +[[image:image-20220709161741-3.png]]
576 576  
577 -(((
578 -0x(01): Interrupt Uplink Packet.
579 -)))
580 580  
603 +Convert the read byte to decimal and divide it by ten.
581 581  
582 582  
583 -=== 2.4.7  ​+5V Output ===
606 +**Example:**
584 584  
585 -(((
586 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
587 -)))
608 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
588 588  
610 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
589 589  
590 -(((
591 -The 5V output time can be controlled by AT Command.
592 -)))
593 593  
594 -(((
595 -(% style="color:blue" %)**AT+5VT=1000**
596 -)))
597 597  
598 -(((
599 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
600 -)))
614 +== 2.4  Downlink Payload ==
601 601  
602 -
603 -
604 -== 2.5  Downlink Payload ==
605 -
606 606  By default, NDDS75 prints the downlink payload to console port.
607 607  
608 608  [[image:image-20220709100028-1.png]]
... ... @@ -653,51 +653,16 @@
653 653  
654 654  
655 655  
656 -== 2.6  ​LED Indicator ==
666 +== 2.5  ​Battery Analysis ==
657 657  
668 +=== 2.5.1  ​Battery Type ===
658 658  
659 -The NDDS75 has an internal LED which is to show the status of different state.
660 660  
661 -
662 -* 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)
663 -* Then the LED will be on for 1 second means device is boot normally.
664 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
665 -* For each uplink probe, LED will be on for 500ms.
666 -
667 667  (((
668 -
672 +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.
669 669  )))
670 670  
671 -
672 -
673 -== 2.7  ​Firmware Change Log ==
674 -
675 -
676 676  (((
677 -Download URL & Firmware Change log
678 -)))
679 -
680 -(((
681 -[[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/]]
682 -)))
683 -
684 -
685 -(((
686 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
687 -)))
688 -
689 -
690 -
691 -== 2.8  ​Battery Analysis ==
692 -
693 -=== 2.8.1  ​Battery Type ===
694 -
695 -
696 -(((
697 -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.
698 -)))
699 -
700 -(((
701 701  The battery is designed to last for several years depends on the actually use environment and update interval. 
702 702  )))
703 703  
... ... @@ -715,56 +715,35 @@
715 715  
716 716  
717 717  
718 -=== 2.8.2  Power consumption Analyze ===
693 +=== 2.5.2  Power consumption Analyze ===
719 719  
720 720  (((
721 -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.
696 +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.
722 722  )))
723 723  
724 -
725 725  (((
726 -Instruction to use as below:
700 +
727 727  )))
728 728  
729 -(((
730 -(% 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/]]
731 -)))
732 732  
704 +=== 2.5.3  ​Battery Note ===
733 733  
734 734  (((
735 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
707 +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.
736 736  )))
737 737  
738 -* (((
739 -Product Model
740 -)))
741 -* (((
742 -Uplink Interval
743 -)))
744 -* (((
745 -Working Mode
746 -)))
747 747  
748 -(((
749 -And the Life expectation in difference case will be shown on the right.
750 -)))
751 751  
752 -[[image:image-20220709110451-3.png]]
712 +=== 2.5.4  Replace the battery ===
753 753  
754 754  
755 -
756 -=== 2.8.3  ​Battery Note ===
757 -
758 758  (((
759 -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.
716 +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.
760 760  )))
761 761  
762 762  
763 -
764 -=== 2.8.4  Replace the battery ===
765 -
766 766  (((
767 -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).
721 +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).
768 768  )))
769 769  
770 770  
... ... @@ -787,7 +787,7 @@
787 787  
788 788  == 4.1  Access AT Commands ==
789 789  
790 -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/]]
744 +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/]]
791 791  
792 792  
793 793  AT+<CMD>?  : Help on <CMD>
... ... @@ -875,8 +875,12 @@
875 875  )))
876 876  
877 877  (((
878 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
832 +
833 +
834 +(((
835 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
879 879  )))
837 +)))
880 880  
881 881  
882 882  
... ... @@ -907,7 +907,7 @@
907 907  = 7. ​ Order Info =
908 908  
909 909  
910 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
868 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
911 911  
912 912  
913 913  (% class="wikigeneratedid" %)
... ... @@ -922,7 +922,7 @@
922 922  
923 923  (% style="color:#037691" %)**Package Includes**:
924 924  
925 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
883 +* N95S31B NB-IoT Temperature and Humidity Sensor
926 926  * External antenna x 1
927 927  )))
928 928  
... ... @@ -931,11 +931,10 @@
931 931  
932 932  (% style="color:#037691" %)**Dimension and weight**:
933 933  
934 -
935 935  * Device Size: 13.0 x 5 x 4.5 cm
936 936  * Device Weight: 150g
937 -* Package Size / pcs : 15 x 12x 5.5 cm
938 -* Weight / pcs : 220g
894 +* Package Size / pcs : 14.0 x 8x 5 cm
895 +* Weight / pcs : 180g
939 939  )))
940 940  
941 941  (((
1657520100595-569.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
image-20220709161741-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +111.2 KB
Content
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0