Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual

Last modified by Mengting Qiu on 2024/04/02 16:44

From version < 115.31 >

edited by Xiaoling
on 2022/07/11 08:42

To version < 113.2 >

edited by Xiaoling
on 2022/07/09 15:50

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 2 removed)
- 1657354294009-643.png
- image-20220709161741-3.png

Details

Page properties

Content

@@ -9,7 +9,6 @@
  **Table of Contents:**
--{{toc/}}
@@ -22,29 +22,16 @@
  (((
--(((
  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*.
--)))
--(((
  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.
--)))
--(((
  N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
--)))
--(((
  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).
--)))
--(((
--
--)))
--(((
  ~* make sure you have NB-IoT coverage locally.
--)))
  )))
@@ -55,6 +55,7 @@
  == 1.2  Features ==
++
  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
  * Monitor Temperature & Humidity via SHT31
  * AT Commands to change parameters
@@ -68,7 +68,6 @@
--
  == 1.3  Specification ==
@@ -77,7 +77,6 @@
  * Supply Voltage: 2.1v ~~ 3.6v
  * Operating Temperature: -40 ~~ 85°C
--
  (% style="color:#037691" %)**NB-IoT Spec:**
  * - B1 @H-FDD: 2100MHz
@@ -87,9 +87,9 @@
  * - B20 @H-FDD: 800MHz
  * - B28 @H-FDD: 700MHz
--
  (% style="color:#037691" %)**Battery:**
++
  * Li/SOCI2 un-chargeable battery
  * Capacity: 8500mAh
  * Self Discharge: <1% / Year @ 25°C
@@ -98,7 +98,6 @@
--
  == 1.4  Applications ==
  * Smart Buildings & Home Automation
@@ -127,13 +127,9 @@
  === 1.5.2  BOOT MODE / SW1 ===
--(((
 ) 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.
--)))
--(((
 ) Flash: work mode, device starts to work and send out console output for further debug
--)))
@@ -190,45 +190,24 @@
  === 2.2.1  Test Requirement ===
--(((
  To use N95S31B in your city, make sure meet below requirements:
--)))
--* (((
--Your local operator has already distributed a NB-IoT Network there.
--)))
--* (((
--The local NB-IoT network used the band that N95S31B supports.
--)))
--* (((
--Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
--)))
++* Your local operator has already distributed a NB-IoT Network there.
++* The local NB-IoT network used the band that N95S31B supports.
++* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
--(((
++
  Below figure shows our testing structure.   Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
--)))
--(((
  N95S31B supports different communication protocol such as :
--)))
  (((
--* (((
--CoAP       ((% style="color:red" %)120.24.4.116:5683(%%))
--)))
--* (((
--raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
--)))
--* (((
--MQTT      ((% style="color:red" %)120.24.4.116:1883(%%))
--)))
--* (((
--TCP          ((% style="color:red" %)120.24.4.116:5600(%%))
--)))
++* CoAP       ((% style="color:red" %)120.24.4.116:5683(%%))
++* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
++* MQTT      ((% style="color:red" %)120.24.4.116:1883(%%))
++* TCP          ((% style="color:red" %)120.24.4.116:5600(%%))
--(((
  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.
--)))
  )))
@@ -350,8 +350,8 @@
  * (% style="color:blue" %)**AT+CLIENT=CLIENT       **                            (%%)~/~/Set up the CLIENT of MQTT
  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
--* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
--* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%)                  ~/~/Set the subscription topic of MQTT
++* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
++* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%)                  ~/~/Set the subscription topic of MQTT
  [[image:1657352634421-276.png]]
@@ -397,200 +397,216 @@
  == 2.3  Uplink Payload ==
++In this mode, uplink payload includes in total 14 bytes
--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.
++(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
++|=(% style="width: 60px;" %)(((
++**Size(bytes)**
++)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
++|(% 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"]]
--For example:
++(((
++If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
++)))
-- (% 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.
++[[image:1657331036973-987.png]]
--The uplink payloads are composed in  ASCII String. For example:
++(((
++The payload is ASCII string, representative same HEX:
++)))
--0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
++(((
++0x72403155615900640c6c19029200 where:
++)))
--0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d  Total 12 bytes
++* (((
++Device ID: 0x724031556159 = 724031556159
++)))
++* (((
++Version: 0x0064=100=1.0.0
++)))
++* (((
++BAT: 0x0c6c = 3180 mV = 3.180V
++)))
++* (((
++Signal: 0x19 = 25
++)))
++* (((
++Distance: 0x0292= 658 mm
++)))
++* (((
++Interrupt: 0x00 = 0
--(% style="color:red" %)**NOTE:**
--(% style="color:red" %)
--1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
--1. By default, the device will send an uplink message every 1 hour.
++
++)))
--=== 2.3.1  Payload Analyze ===
++== 2.4  Payload Explanation and Sensor Interface ==
--N95S31B uplink payload includes in total 21 bytes
++=== 2.4.1  Device ID ===
--(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
--|=(% style="width: 60px;" %)(((
--**Size(bytes)**
--)))|=(% 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**
--|(% 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" %)(((
  (((
--Reserve/ Same as NBSN95 CFGMOD=1
++By default, the Device ID equal to the last 6 bytes of IMEI.
  )))
  (((
--No function here.
++User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
  )))
--)))|(% style="width:77px" %)(((
++
  (((
--[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
++**Example:**
  )))
  (((
--By SHT31
++AT+DEUI=A84041F15612
  )))
--)))|(% style="width:80px" %)(((
++
  (((
--[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
++The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
  )))
++
++
++=== 2.4.2  Version Info ===
++
  (((
--By SHT31
++Specify the software version: 0x64=100, means firmware version 1.00.
  )))
--)))
  (((
--(((
--If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
++For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
  )))
--)))
--[[image:1657354294009-643.png]]
++=== 2.4.3  Battery Info ===
--The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
--
--* Device ID: 0x724031607457 = 724031607457
--* Version: 0x006e=110=1.1.0
--
--* BAT: 0x0ccd = 3277 mV = 3.277V
--* Signal: 0x1b = 27
--* Model: 0x01 = 1
--* 0x00dc000ccc= reserve, ignore in N95S31B
--* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
--* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
--
  (((
--
++Ex1: 0x0B45 = 2885mV
  )))
  (((
--
++Ex2: 0x0B49 = 2889mV
  )))
--=== 2.3.2  Device ID ===
++=== 2.4.4  Signal Strength ===
++
  (((
--By default, the Device ID equal to the last 6 bytes of IMEI.
++NB-IoT Network signal Strength.
  )))
  (((
--User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
++**Ex1: 0x1d = 29**
  )))
  (((
--**Example:**
++(% style="color:blue" %)**0**(%%)        -113dBm or less
  )))
  (((
--AT+DEUI=A84041F15612
++(% style="color:blue" %)**1**(%%)        -111dBm
  )))
  (((
--The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
++(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
  )))
++(((
++(% style="color:blue" %)**31**  (%%)    -51dBm or greater
++)))
++(((
++(% style="color:blue" %)**99**   (%%)   Not known or not detectable
++)))
--=== 2.3.3  Version Info ===
--These bytes include the hardware and software version.
++=== 2.4.5  Distance ===
--Higher byte: Specify hardware version: always 0x00 for N95S31B
++Get the distance. Flat object range 280mm - 7500mm.
--Lower byte: Specify the software version: 0x6E=110, means firmware version 110
++(((
++For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
++)))
--
--For example: 0x00 6E: this device is N95S31B with firmware version 110.
--
  (((
--
++(((
++(% style="color:blue" %)**                                                        0B05(H) = 2821(D) = 2821mm.**
  )))
++)))
--
--=== 2.3.4  Battery Info ===
--
  (((
--Ex1: 0x0B45 = 2885mV
++
  )))
  (((
--Ex2: 0x0B49 = 2889mV
++
  )))
++=== 2.4.6  Digital Interrupt ===
--
--=== 2.3.5  Signal Strength ===
--
  (((
--NB-IoT Network signal Strength.
++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.
  )))
  (((
--**Ex1: 0x1d = 29**
++The command is:
  )))
  (((
--(% style="color:blue" %)**0**(%%)        -113dBm or less
++(% 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]])**.**
  )))
++
  (((
--(% style="color:blue" %)**1**(%%)        -111dBm
++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.
  )))
++
  (((
--(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
++Example:
  )))
  (((
--(% style="color:blue" %)**31**  (%%)    -51dBm or greater
++0x(00): Normal uplink packet.
  )))
  (((
--(% style="color:blue" %)**99**   (%%)   Not known or not detectable
++0x(01): Interrupt Uplink Packet.
  )))
--=== 2.3.6  Temperature & Humidity ===
++=== 2.4.7  +5V Output ===
--The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
++(((
++NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
++)))
--[[image:image-20220709161741-3.png]]
++(((
++The 5V output time can be controlled by AT Command.
++)))
--Convert the read byte to decimal and divide it by ten.
++(((
++(% style="color:blue" %)**AT+5VT=1000**
++)))
++(((
++Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
++)))
--**Example:**
--Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
--Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
++== 2.5  Downlink Payload ==
--
--
--== 2.4  Downlink Payload ==
--
  By default, NDDS75 prints the downlink payload to console port.
  [[image:image-20220709100028-1.png]]
@@ -641,16 +641,51 @@
--== 2.5  Battery Analysis ==
++== 2.6  LED Indicator ==
--=== 2.5.1  Battery Type ===
++The NDDS75 has an internal LED which is to show the status of different state.
++
++* 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)
++* Then the LED will be on for 1 second means device is boot normally.
++* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
++* For each uplink probe, LED will be on for 500ms.
++
  (((
--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.
++
  )))
++
++
++== 2.7  Firmware Change Log ==
++
++
  (((
++Download URL & Firmware Change log
++)))
++
++(((
++[[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/]]
++)))
++
++
++(((
++Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
++)))
++
++
++
++== 2.8  Battery Analysis ==
++
++=== 2.8.1  Battery Type ===
++
++
++(((
++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.
++)))
++
++(((
  The battery is designed to last for several years depends on the actually use environment and update interval.
  )))
@@ -668,35 +668,56 @@
--=== 2.5.2  Power consumption Analyze ===
++=== 2.8.2  Power consumption Analyze ===
  (((
--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.
++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.
  )))
++
  (((
--
++Instruction to use as below:
  )))
++(((
++(% 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/]]
++)))
--=== 2.5.3  Battery Note ===
  (((
--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.
++(% style="color:blue" %)**Step 2: **(%%) Open it and choose
  )))
++* (((
++Product Model
++)))
++* (((
++Uplink Interval
++)))
++* (((
++Working Mode
++)))
++(((
++And the Life expectation in difference case will be shown on the right.
++)))
--=== 2.5.4  Replace the battery ===
++[[image:image-20220709110451-3.png]]
++
++=== 2.8.3  Battery Note ===
++
  (((
--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.
++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.
  )))
++
++=== 2.8.4  Replace the battery ===
++
  (((
--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).
++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).
  )))
@@ -719,7 +719,7 @@
  == 4.1  Access AT Commands ==
--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/]]
++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/]]
  AT+<CMD>?                    : Help on <CMD>
@@ -807,9 +807,7 @@
  )))
  (((
--
--
--(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
++(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
  )))
@@ -841,7 +841,7 @@
  = 7.  Order Info =
--Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
++Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
  (% class="wikigeneratedid" %)
@@ -856,7 +856,7 @@
  (% style="color:#037691" %)**Package Includes**:
--* N95S31B NB-IoT Temperature and Humidity Sensor
++* NSE01 NB-IoT Distance Detect Sensor Node x 1
  * External antenna x 1
  )))
@@ -865,10 +865,11 @@
  (% style="color:#037691" %)**Dimension and weight**:
++
  * Device Size: 13.0 x 5 x 4.5 cm
  * Device Weight: 150g
--* Package Size / pcs : 14.0 x 8x 5 cm
--* Weight / pcs : 180g
++* Package Size / pcs : 15 x 12x 5.5 cm
++* Weight / pcs : 220g
  )))
  (((

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

Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual

Summary

Details

Applications

Navigation