The humidity sensor is a 16-bit digital ultra-low-power and high-performance sensor with
digital output interface. It measures relative humidity from 0 to 100% rH with an output data
rate of 1 Hz, 7 Hz and 12.5 Hz. It is embedded with a temperature sensor for ambient temperature measurement. The sensor is fully calibrated and no further calibration is required.
The dimension of the sensor is 2.0 mm×2.0 mm×0.9 mm. It is available in land grid array
package (LGA).
1.2 Applications
• HVAC systems
• Home and building automation
• Goods and asset tracking
• Air conditioners
• Refrigerators
1.3 Sensor features
•Humidity measurement range :
•Humidity noise :
•Temperature measurement range :
•Temperature noise :
•Output data rate :
•Operating modes :
•Current consumption :
•Communication interface :
0 to 100 % rH
0.35 rH % RMS
-40 to +120 °C
0.03 °C RMS
1 Hz, 7 Hz and 12.5 Hz
Continuous mode and one-shot mode
The sensor is a MEMS based capacitive humidity sensor with an integrated ASIC. MEMS
sensing element is a planar fringed capacitor with a dielectric polymer which absorbs or releases water with proportional to the relative humidity in the environment. A silicon based
temperature sensor is integrated in the same package. ASIC comprises of multiplier, operational amplifier, analog-to-digital converter and other signal conditioning blocks like controller
logics and interrupts. ASIC converts the analog signal from the both humidity and temperature sensing element into a 16-bit digital humidity and temperature values. The sensor is
factory calibrated for both humidity and temperature measurements. The trimming parameters are stored in on-chip flash memory. When the sensor is powered on, these trimming
parameters are loaded from the flash memory to the registers. Hence, no further calibration
is required for humidity and temperature values.
The device is susceptible to damage by electrostatic discharge (ESD). Always
use proper ESD precautions when handling. Improper handling of the device
can cause performance degradation or permanent damage to the part
Table 6: General information
For better performance, the recommended storage condition for the humidity
sensor is 10°C to 40°C with 20% rH to 60% rH
A positive supply voltage is applied to the sensor through VDD pin and negative voltage to
GND. The decoupling capacitor of 100 nF in parallel is highly recommended to prevent the
voltage ripples on the VDD line. It should be placed as close as possible to the VDD pin.
The CS pin shall be connected to VDD_IO in order to enable the I2C communication interface. For SPI communication, the CS pin shall be connected to master side CS pin for active
start and stop SPI communication. The pull up resistors Rpfor I2C communication interface
should be connected parallel between supply voltage VDD and SCL and SDA pins.
Depending on the internal resistance of I2C pins at the master side, the pull up resistors
Rpcan be selected for proper rise and fall time of the digital signals. The 3-pin to 4-pin SPI
configuration can be configured as mentioned in the figure 3.
The humidity sensor supports standard I2C (Inter-IC) bus protocol. Further information of
the I2C interface can be found at https://www.nxp.com/docs/en/user-guide/UM10204.pdf .
I2C is a serial 8-bit protocol with two-wire interface, which supports communication between
different ICs. For example, between the microcontroller and other peripheral devices.
5.1 General characteristics
A serial data line (SDA) and a serial clock line (SCL) are required for the communication
between the devices connected via I2C bus. Both SDA and SCL lines are bidirectional. The
output stages of devices connected to the bus must have an open-drain or open-collector.
Hence, the SDA and SCL lines are connected to a positive supply voltage via pull-up resistors. In I2C protocol, the communication is realized through master-slave principle. The
master device generates the clock pulse, a start command and a stop command for the data
transfer. Each connected device on the bus is addressable via a unique address. Master
and slave can act as a transmitter or a receiver depending upon whether the data needs to
be transmitted or received.
The sensor behaves like a slave device on the I2C bus
The positive supply voltage to which SDA and SCL lines are pulled up (through pull-up
resistors), in turn determines the high level input for the slave devices. The sensor has
separate supply voltage VDD_IO for the SDA and SCL lines. The logic high ’1’ and logic low
’0’ levels for the SDA and SCL lines then depend on the VDD.
5.3 Communication phase
5.3.1 Idle state
During the idle state, the bus is free and both SDA and SCL lines are in logic high ’1’ state.
5.3.2 START(S) and STOP(P) condition
Data transfer on the bus starts with a START command, which is generated by the master.
A start condition is defined as a high-to-low transition on the SDA line while the SCL line is
held high. The bus is considered busy after the start condition.
Data transfer on the bus is terminated with a STOP command, which is also generated by
the master. A low-to-high transition on the SDA line, while the SCL line being high is defined
as a STOP condition. After the stop condition, the bus is again considered free and is in idle
state. Figure 5 shows the I2C bus START and STOP conditions.
Master can also send a REPEATED START (SR) command instead of STOP command.
REPEATED START condition is same as the START condition.
5.3.3 Data validity
After the start condition, one data bit is transmitted with each clock pulse. The transmitted
data is only valid when the SDA line data is stable (high or low) during the high period of the
clock pulse. High or low state of the data line can only change when the clock pulse is in low
state.
Data transmission on the SDA line is always done in bytes, with each byte being 8-bits long.
Data is transmitted with the most significant bit (MSB) followed by other bits.
If the slave cannot receive or transmit another complete byte of data, it can force the master
into a wait state by holding SCL LOW. Data transfer continues when the slave is ready which
is indicated by releasing the SCL pin.
5.3.5 Acknowledge (ACK) and No-Acknowledge (NAACK)
Each byte transmitted on the data line must follow an Acknowledge bit. The receiver (master or slave) generates an Acknowledge signal to indicate that the data byte was received
successfully and ready to receive next data byte.
After one byte is transmitted, the master generates an additional Acknowledge clock pulse
to continue the data transfer. The transmitter releases the SDA line during this clock pulse
so that the receiver can pull the SDA line to low state in such a way that the SDA line
remains stable low during the entire high period of the clock pulse. It is considered as an
Acknowledge signal.
If the receiver does not want to receive any further byte, it will not pull down the SDA line
and it remains in stable high state during the entire clock pulse. It is considered as a NoAcknowledge signal and the master can generate either a stop condition to terminate the
data transfer or a repeated start condition to initiate a new data transfer.
5.3.6 Slave address for the sensor
The slave address is transmitted after sending the start condition. Each device on the I2C
bus has a unique address. Master selects the slave by sending corresponding slave address
after the start condition. A slave address is a 7 bits long followed by a Read/Write bit.
Figure 6: Slave address format
The 7-bit slave address of the humidity sensor is 1011111b. The R/W bit determines the
data direction. ’0’ indicates a write operation (transmission from master to slave) and a ’1’
indicates a read operation (data request from slave).
Once the slave-address and data direction bit is transmitted, the slave acknowledges the
master. The master transmits the next byte, which must be a register-address of the sensor.
It indicates the address of the register where data needs to be written to or read from.
After receiving the register address, the slave sends an Acknowledgement (ACK). If the
master is still writing to the slave (R/W bit = 0), it will transmit the data to slave in the same
direction. If the master wants to read from the addressed register (R/W bit =1), a repeated
start (SR) condition must be transmitted to the slave. Master acknowledges the slave after
receiving each data byte. If the master no longer wants to receive further data from the slave,
it would send No-Acknowledge (NACK). Afterwards, master can send a STOP condition to
terminate the data transfer. Figure 8 shows the writing and reading procedures between the
master and the slave device (sensor).
5.4I2C Multiple bytes read operation
In order to read multiple bytes incrementing the register address, it is necessary to assert
the most significant bit of the sub-address field (output register address). The bit [7] must
be equal to 1 while bit [6-0] represents the address of the first register to be read. Here is
an example of how to read 4 bytes of data from output registers by requesting the data only
from 0x28.
• To read multiple bytes from the output registers 0x28 to 0x2B, the first register address
must be changed from 0x28 (b0010 1000) to 0xA8(b1010 1000 (MSB is changed from
’0’ to ’1’).
• After sending I2C address, start with reading from the register 0xA8 and request 4
bytes to read.
• The received 4 bytes gives the content from registers 0x28 to 0x2B.
There is no auto increment bit (enable/disable) implemented in the control register for multiple bytes of read.
Serial Peripheral Interface (SPI) is a synchronous serial communication bus system for the
communication between host microcontroller and other peripheral ICs such as ADCs, EEPROMs, sensors, etc. SPI is a full-duplex master-slave based interface allowing the communication to happen in both directions simultaneously. The data from the master or the slave
is synchronized either on the rising or falling edge of clock pulse. SPI can be either 4-wire or
3-wire interface. 4-wire interface consists of two signal lines and two data lines. All of these
bus lines are unidirectional.
1. Clock (SCL)
2. Chip select (CS)
3. Master out, slave in (MOSI)
4. Master in, slave out (MISO)
Figure 9: SPI Interface
Master generates the clock signal and is connected to all slave devices. Data transmission
between the master and salves is synchronized to the clock signal generated by the master.
One master can be connected to one or more slave devices. Each slave device is addressed
and controlled by the master via individual chip select (CS) signals. CS is controlled by the
master and is normally an active low signal.
MOSI and MISO are data lines. MOSI transmits data from the master to the slave. MISO
transmits data from the slave to the master.
The humidity sensor supports only 3-wire SPI communication.
Communication begins when the master selects a slave device by pulling the CS line to
LOW. The clock and data lines (MOSI/MISO) are available for the selected slave device.
Data stored in the specific shift registers are exchanged synchronously between master and
the slave through MISO and MOSI lines. The data transmission is over when the chip select
line is pulled up to the HIGH state. 4-wire SPI uses both data lines for the synchronous data
exchange in both the direction. 3-wire SPI shares a single data line for the data transfer,
where the master and slave alternate their transmitter and receiver roles synchronously.
6.2 Communication modes
In SPI, the master can select the clock polarity (CPOL) and clock phase (CPHA). The CPOL
bit sets the polarity of the clock signal during the idle state. The CPHA bit selects the clock
phase. Depending on the CPHA bit, the rising or falling clock edge is used to sample and
shift the data. Depending on the CPOL and CPHA bit selection in the SPI control registers,
four SPI modes are available as per table9. In order to ensure proper communication,
master and the slave must be set to same communication modes.
CPOLCPHADescription
00Clock polarity LOW in idle state; Data sampled on the rising clock edge
01Clock polarity LOW in idle state; Data sampled on the falling clock edge
11Clock polarity HIGH in idle state; Data sampled on the falling clock edge
10Clock polarity HIGH in idle state; Data sampled on the rising clock edge
3-Wire SPI of this sensor uses following lines: SDA (data input, MOSI), SCL (serial clock)
and CS (chip select). For more information, please refer to pin description in the section 3.
CS is pulled LOW by the master at the start of communication. The SCL polarity is HIGH in
the idle state (CPOL = 1). The data lines (SDA & SAO) are sampled at the falling clock edge
and latched at the rising clock edge (CPHA = 1). Data is transmitted with MSB first and the
LSB last.
SPI read and write operations are completed in 2 or more bytes (multiple of 16 or more clock
pulses). Each block consists of a register address byte and a data byte. The first byte is the
register address. In the SPI communication, the register address is specified in the 7-bits
and the MSB of the register address is used as an SPI read/write bit (Figure10). When R/W
is ’0’, the data is written on to the sensor. When ’1’, the data is read from the sensor.
Figure 10: SPI register address
The next bytes of data, depending on the R/W bit, is either written to or read from the indexed
register. Figure11shows the complete SPI data transfer protocol.
The sensor supports 3-wire SPI communication uses SDA pin for both data
read and write operations. Communication protocol remains the same.
Figure 11: 4-wire SPI data transfer (CPOL = 1, CPHA = 1)
The write operation starts with the CS = LOW and sending the 7-bit register address with
R/W bit = ’0’ (write command). Next byte is the data byte that is the data to be written to the
indexed register. Several write command pairs can be sent without raising the CS back to
HIGH. The operation is ended with CS = HIGH. The SPI write protocol is shown in the figure
12
.
Figure 12: SPI write protocol
6.3.2 SPI read operation
The read operation starts with the CS = LOW and sending the 7-bit register address with
R/W bit = ’1’ (read command). Data is sent out from the sensor through the SDA line. The
SPI read protocol is shown in the figure13.
This chapter describes the sensor communication check and operation sequence of the
humidity sensor.
7.1 Communication check
After proper powering of the sensor, the first step is to check the communication of the sensor with an I2C or SPI digital interface. It can be verified by reading the DEVICE_ID register
(0x0F). If the value from the DEVICE_ID register (0x0F) is 0xBC, then communication from
master to sensor is successful.
Humidity sensor with integrated temperature sensor, Part Nr. 2525020210001
7.2 Sensor in operation
Sensorinpowerdown
mode
Enable continuousoperationmode
Enable BDUbit
Selectoutputdatarate: 1 Hz
CTRL_1(0x20)
If
DRDYsignalis
available?
Enable DRDY_ENbit
Readdatafromoutputregister
Computethedata
withcalibration
registers
Compute the datausinggiven
formula(Refertochapter9)
Yes
No
Nodatainoutputregister
CTRL_3(0x22)
Outputregisters0x28, 0x29, 0x2A,
0x2B
Outputregisters0x28, 0x29, 0x2A,
0x2B
Readcalibrationregisters
(Onlyonce)
Fromregisters0x30 to0x3F
Humidityvaluein%rH
Temperaturevaluein°C
Outputvalue
Stepscan
be
performed
once
Stepscan
be
performed
in loops
The following flow chart is an initialization example to operate the sensor in continuous mode
with output data rate of 1 Hz.
The initialization of the sensor can be performed by selecting the operation mode and output
data rate. After initialization of the sensor, it is recommended to check the availability of data
samples using DRDY signal at INT pin.
The humidity sensor can be operated in two different modes. Operating modes can be selected by PD bit and ODR[1:0] bits in the CTRL_1 register(0x20) and ONE SHOT bit in the
CTRL_2 register(0x21).
By default after powering up, the sensor goes to power down mode. In power down mode,
all internal blocks are turned off to minimize the power consumption. After selecting one of
the two operating mode, the sensor is in active measurement state depending on the output
data rate.
8.1 Continuous mode
In the continuous mode, the sensor is in active measurement state for humidity and temperature values. The humidity and temperature values are available at a rate of selected output
data rate in the table 11.
Three possible output data rates in the continuous mode are mentioned in table 11.
ODR[1:0]Output data rate
00One shot mode
011 Hz
107 Hz
1112.5 Hz
Table 11: Output data rate
8.2 One shot mode
One shot mode can be used only when the humidity and temperature values are necessary
instead of continuous measurement value. ONE SHOT bit in the CTRL_2 register(0x21) is
used to start a new measurement. The humidity and temperature output values are acquired
and it is available in the output registers when the ONE SHOT bit is set to ’1’. After completion of a new measurement for humidity and temperature values, the ONE SHOT bit is set
to ’0’ automatically by the sensor.
The humidity sensor values are obtained from two 8-bit output registers H_OUT_L (0x28)
and H_OUT_H (0x29). These two 8-bit values are concatenated to form a 16-bit word, which
is represented in 2’s complement. The relative humidity value is calculated by linear interpolation method using values from humidity output registers H_OUT_L (0x28) and H_OUT_H
(0x29) along with calibration registers.
9.2 Steps to calculate humidity output value
Step 1 to step 6 can be performed only once
1. Read the coefficient values from the registers H0_rH_x2 (0x30) and H1_rH_x2 and
(0x31)
2. Divide the coefficients by 2 to get H0_rH and H1_rH:
(H0_rh_x2)/2 and (H1_rh_x2)/2
3. Read the values from register 0x36 and 0x37.
4. Concatenate 0x37 & 0x36 to obtain signed 16-bit value of H0_T0_OUT.
5. Read the values from register 0x3A and 0x3B.
6. Concatenate 0x3B & 0x3A to obtain signed 16-bit value of H1_T0_OUT.
7. Read the raw values from humidity output register 0x28 and 0x29.
8. Concatenate 0x29 & 0x28 to obtain 16-bit word of H_T_OUT.
9. Calculate the relative humidity value in rH % using below formula:
WSEN_HIDS humidity sensor SDK is implemented with the above steps. It is
available in our website to download for free.
9.3 Temperature sensor
The temperature sensor values are obtained from two 8-bit output registers T_OUT_L (0x2A)
and T_OUT_H (0x2B). These two 8-bit values are concatenated to form a 16-bit word, which
is represented in 2’s complement.
The most significant bit (MSB) of the T_OUT_H register indicates the polarity of the temperature output value.
• If the sign bit is ’0’, then the value read is positive.
• If the sign bit is ’1’, then the value read is negative. In this case, take 2’s complement
of the entire word.
The temperature value is calculated by linear interpolation method using values from the
temperature output registers T_OUT_L (0x2A) and T_OUT_H (0x2B) along with calibration
registers.
9.4 Steps to compute temperature output value
Step 1 to step 13 can be performed only once
1. Read the coefficient value from the register T1_T0 (0x35) and store it in a variable
’tmp’.
2. Read the coefficient value from the registers T0_degC_x8 (0x32) and store it in a
variable ’buffer’.
3. Perform logic AND operation between ’tmp’ and 0x03 and left shift by 8 bits.
x = ((tmp & 0x03)<<8)
4. Perform logic OR operation between x and ’buffer’ to get T0_degC_x8.
T0_degC_x8 = x | buffer
5. Divide the coefficient by 8 to get T0_degC.
T0_degC = (T0_degC_x8)/8
6. Read the coefficient value from the registers T1_degC_x8 (0x33) and store it in a
variable ’buffer’.
• 10-bit T0 Temperature calibration value: 8-bit T_degC_0[7:0] from the register (0x32) and 2 bit T_0[1:0] from the register (0x35)
• 10-bit T1 Temperature calibration value: 8-bit T_degC_1[7:0] from the register (0x33) and 2 bit T_1[1:0] from the register (0x35)
1
The registers contents are loaded at boot procedure should not be changed. They contain
the factory calibration values and their content is automatically restored when the device is
powered up.
Writing to Reserved marked in the registers is not allowed. Writing to those
reserved marked bits may cause permanent damage to the sensor.
The content of the calibration registers should not be changed.
11 Register description
11.1 Device_ID (0x0F)
The value of this register gives the device ID: 0xBC (b10111100)
Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0Type
10111100R
Table 12: Device_ID register
11.2 Average (0x10)
Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0Type
ReservedAVG_T[2:0]AVG_H[2:0]
Table 13: Average register
bitsDescription
R/W
AVG_T[2:0]Internal averaging of the samples for temperature output values
AVG_H[2:0]Internal averaging of the samples for humidity output values
Power down. By default, PD: 0 which is power down mode. PD: 1
Continuous mode for active measurement
Block data update. 0: Continuous update, 1: Output registers are not
updated until MSB and LSB is read
ODR[1:0]Output data rate of the humidity and temperature value
Table 17: CTRL_1 register description
11.3.1 Block data update (BDU)
ODR[1:0]
R/W
It is strongly recommended to set the BDU bit to ’1’ in the CTRL_1 register. By default the
BDU bit is ’0’ and the output registers are continuously updated. When the BDU bit is set
to ’1’ the content of the output registers is not updated until both MSB and LSB are read.
It avoids reading values related to different samples. As soon as the BDU is activated, the
output registers always contain the most recent output data produced by the sensor. If the
processor initiate the read function of the output registers T_OUT_L, T_OUT_H, H_OUT_L
and H_OUT_H, the update for that pair is blocked until both MSB and LSB of the data is read.
BOOTReboot memory content. 0: normal mode, 1: reboot memory content
HeaterHeater enable/disable. By default 0: disable, 1: enable
ONE SHOT
11.4.1 BOOT
The content of the internal registers stored in the flash memory block can be refreshed using
BOOT bit. After proper powering of the sensor, content of the flash memory is loaded to the
internal registers. When the BOOT bit is set to ’1’ the content of the internal flash memory
block is copied to the internal registers and also calibrates the sensor. Each sensor has
different factory trimmed values stored in the internal flash memory. The content in the flash
memory copied to internal registers permit good performance of the sensor. Therefore the
content of the internal registers should not be modified.
One shot mode enable. By default 0: conversion done, 1: start of new
Reserved
Table 19: CTRL_2 register
conversion
Table 20: CTRL_2 register description
HeaterONE SHOTR/W
11.4.2 Heater
In case of condensation on the sensor, heater can be turned on using Heater bit. The heating
of the sensor element will speed up the recovery time of the sensor after condensation. During active heating, the humidity and temperature output values should not be read. It is also
recommended that output values should not be read immediately after turning off the heater.
The value of the humidity output registers H_OUT_L(0x28) and H_OUT_H(0x29) is expressed in 16-bit resolution. Please refer chapter 9.1 to obtain the humidity value from
16-bit values of the output registers.
Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0Type
HUMIDITY[7:0]
Table 26: H_OUT_L register
bitsDescription
HUMIDITY[7:0]8 least significant bits (LSB) of the humidity sensor output
Table 27: H_OUT_L register description
11.8 H_OUT_H (0x29)
Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0Type
HUMIDITY[7:0]
Table 28: H_OUT_H register
R
R
bitsDescription
HUMIDITY[7:0]8 most significant bits (MSB) of the humidity sensor output
Table 29: H_OUT_H register description
The software drivers must clip output values exceeding the measurement range of the humidity sensor.
11.9 T_OUT_L (0x2A)
The value of the temperature output registers T_OUT_L(0x2A) and T_OUT_H(0x0E) is expressed in 16-bit resolution. Please refer chapter 9.3 to obtain the temperature value from
16-bit values of the output registers.
• It is important to understand that a humidity sensor is not a normal electronic component and needs to be handled with care.
• Chemical vapours at high concentration in combination with long exposure time may
offset the sensor reading.
• Furthermore it is recommended to store the sensors with temperature range of 10°C
and 40°C and humidity with a range of 20 rH% and 60 rH%.
• Long-term exposure to conditions outside normal humidity and temperature range,
especially at higher humidity range, may temporarily offset the output signal of humidity
sensor.
• After returning to the normal exposure conditions, the humidity output value will slowly
return to the calibration state by itself.
• If such cases happen, to recover the sensor accuracy to the normal state, it has to be
reconditioned to the following procedure :
The sensor product is categorized as JEDEC Moisture Sensitivity Level 3 (MSL3), which requires special handling.
More information regarding the MSL requirements can be found in the IPC/JEDEC J-STD-020
standard on www.jedec.org. More information about the handling, picking, shipping and the
usage of moisture/re-flow and/or process sensitive products can be found in the IPC/JEDEC
J-STD-033 standard on www.jedec.org.
14.2 Soldering
14.2.1 Reflow soldering
Attention must be paid on the thickness of the solder resist between the host PCB top
side and the modules bottom side. Only lead-free assembly is recommended according
to JEDEC J-STD020.
It is recommended to solder the sensor on the last re-flow cycle of the PCB. For solder paste
use a LFM-48W or Indium based SAC 305 alloy (Sn 96.5 / Ag 3.0 / Cu 0.5 / Indium 8.9HF /
Type 3 / 89%) type 3 or higher.
The reflow profile must be adjusted based on the thermal mass of the entire populated PCB,
heat transfer efficiency of the re-flow oven and the specific type of solder paste used. Based
on the specific process and PCB layout the optimal soldering profile must be adjusted and
verified. Other soldering methods (e.g. vapor phase) have not been verified and have to be
validated by the customer at their own risk. Rework is not recommended.
Figure 19: Reflow soldering profile
After reflow soldering, visually inspect the board to confirm proper alignment
Do not clean the product. Any residue cannot be easily removed by washing. Use a "no
clean" soldering paste and do not clean the board after soldering.
• Washing agents used during the production to clean the customer application might
damage or change the characteristics of the component. Washing agents may have a
negative effect on the long-term functionality of the product.
• Using a brush during the cleaning process may damage the component. Therefore,
we do not recommend using a brush during the PCB cleaning process
14.2.3 Potting and coating
• Potting material might shrink or expand during and after hardening. This might apply mechanical stress on the components, which can influence the characteristics of
the transfer function. In addition, potting material can close existing openings in the
housing. This can lead to a malfunction of the component. Thus, potting is not recommended.
• Conformal coating may affect the product performance. We do not recommend coating
the components.
14.2.4 Storage conditions
• A storage of Würth Elektronik eiSos products for longer than 12 months is not recommended. Within other effects, the terminals may suffer degradation, resulting in
bad solderability. Therefore, all products shall be used within the period of 12 months
based on the day of shipment.
• Do not expose the components to direct sunlight.
• The storage conditions in the original packaging are defined according to
DIN EN 61760 - 2.
• For a moisture sensitive component, the storage condition in the original packaging
is defined according to IPC/JEDEC-J-STD-033. It is also recommended to return the
component to the original moisture proof bag and reseal the moisture proof bag again.
14.2.5 Handling
• Violation of the technical product specifications such as exceeding the nominal rated
supply voltage, will void the warranty.
• Violation of the technical product specifications such as but not limited to exceeding
the absolute maximum ratings will void the conformance to regulatory requirements.
• ESD prevention methods need to be followed for manual handling and processing by
machinery.
• The edge castellation is designed and made for prototyping, i.e. hand soldering purposes only.
The following conditions apply to all goods within the sensors product range of Würth Elektronik eiSos GmbH & Co. KG:
15.1 General customer responsibility
Some goods within the product range of Würth Elektronik eiSos GmbH & Co. KG contain
statements regarding general suitability for certain application areas. These statements
about suitability are based on our knowledge and experience of typical requirements concerning the areas, serve as general guidance and cannot be estimated as binding statements
about the suitability for a customer application. The responsibility for the applicability and use
in a particular customer design is always solely within the authority of the customer. Due to
this fact, it is up to the customer to evaluate, where appropriate to investigate and to decide
whether the device with the specific product characteristics described in the product specification is valid and suitable for the respective customer application or not. Accordingly, the
customer is cautioned to verify that the documentation is current before placing orders.
15.2 Customer responsibility related to specific, in particular
safety-relevant applications
It has to be clearly pointed out that the possibility of a malfunction of electronic components
or failure before the end of the usual lifetime cannot be completely eliminated in the current
state of the art, even if the products are operated within the range of the specifications.
The same statement is valid for all software and software parts contained in or used with
or for products in the sensor product range of Würth Elektronik eiSos GmbH & Co. KG.
In certain customer applications requiring a high level of safety and especially in customer
applications in which the malfunction or failure of an electronic component could endanger
human life or health, it must be ensured by most advanced technological aid of suitable
design of the customer application that no injury or damage is caused to third parties in the
event of malfunction or failure of an electronic component.
15.3 Best care and attention
Any product-specific data sheets, manuals, application notes, PCN’s, warnings and cautions must be strictly observed in the most recent versions and matching to the products
revisions. This documents can be downloaded from the product specific sections on the
wireless connectivity and sensors homepage.
15.4 Customer support for product specifications
Some products within the product range may contain substances, which are subject to restrictions in certain jurisdictions in order to serve specific technical requirements. Necessary
information is available on request. In this case, the field sales engineer or the internal sales
person in charge should be contacted who will be happy to support in this matter.
Due to constant product improvement, product specifications may change from time to time.
As a standard reporting procedure of the Product Change Notification (PCN) according to
the JEDEC-Standard, we inform about major changes. In case of further queries regarding
the PCN, the field sales engineer, the internal sales person or the technical support team in
charge should be contacted. The basic responsibility of the customer as per section
and
15.2
remains unaffected.
The sensor driver software ¨Sensor SDK¨ and it’s source codes are not subject to the Product Change Notification information process.
15.1
15.6 Product life cycle
Due to technical progress and economical evaluation we also reserve the right to discontinue production and delivery of products. As a standard reporting procedure of the Product
Termination Notification (PTN) according to the JEDEC-Standard we will inform at an early
stage about inevitable product discontinuance. According to this, we cannot ensure that all
products within our product range will always be available. Therefore, it needs to be verified
with the field sales engineer or the internal sales person in charge about the current product
availability expectancy before or when the product for application design-in disposal is considered. The approach named above does not apply in the case of individual agreements
deviating from the foregoing for customer-specific products.
15.7 Property rights
All the rights for contractual products produced by Würth Elektronik eiSos GmbH & Co. KG
on the basis of ideas, development contracts as well as models or templates that are subject
to copyright, patent or commercial protection supplied to the customer will remain with Würth
Elektronik eiSos GmbH & Co. KG. Würth Elektronik eiSos GmbH & Co. KG does not warrant
or represent that any license, either expressed or implied, is granted under any patent right,
copyright, mask work right, or other intellectual property right relating to any combination,
application, or process in which Würth Elektronik eiSos GmbH & Co. KG components or
services are used.
15.8 General terms and conditions
Unless otherwise agreed in individual contracts, all orders are subject to the current version of the "General Terms and Conditions of Würth Elektronik eiSos Group", last version
available at www.we-online.com.
Würth Elektronik eiSos GmbH & Co. KG considers the information in this document to be
correct at the time of publication. However, Würth Elektronik eiSos GmbH & Co. KG reserves the right to modify the information such as technical specifications or functions of
its products or discontinue the production of these products or the support of one of these
products without any written announcement or notification to customers. The customer must
make sure that the information used corresponds to the latest published information. Würth
Elektronik eiSos GmbH & Co. KG does not assume any liability for the use of its products.
Würth Elektronik eiSos GmbH & Co. KG does not grant licenses for its patent rights or for
any other of its intellectual property rights or third-party rights.
Notwithstanding anything above, Würth Elektronik eiSos GmbH & Co. KG makes no representations and/or warranties of any kind for the provided information related to their accuracy,
correctness, completeness, usage of the products and/or usability for customer applications.
Information published by Würth Elektronik eiSos GmbH & Co. KG regarding third-party products or services does not constitute a license to use such products or services or a warranty
or endorsement thereof.
16.2 Suitability in customer applications
The customer bears the responsibility for compliance of systems or units, in which Würth
Elektronik eiSos GmbH & Co. KG products are integrated, with applicable legal regulations.
Customer acknowledges and agrees that it is solely responsible for compliance with all legal, regulatory and safety-related requirements concerning its products, and any use of
Würth Elektronik eiSos GmbH & Co. KG components in its applications, notwithstanding
any applications-related in-formation or support that may be provided by Würth Elektronik eiSos GmbH & Co. KG. Customer represents and agrees that it has all the necessary
expertise to create and implement safeguards which anticipate dangerous consequences of
failures, monitor failures and their consequences lessen the likelihood of failures that might
cause harm and take appropriate remedial actions. The customer will fully indemnify Würth
Elektronik eiSos GmbH & Co. KG and its representatives against any damages arising out
of the use of any Würth Elektronik eiSos GmbH & Co. KG components in safety-critical
applications.
16.3 Usage restriction
Würth Elektronik eiSos GmbH & Co. KG products have been designed and developed for
usage in general electronic equipment only. This product is not authorized for use in equipment where a higher safety standard and reliability standard is especially required or where
a failure of the product is reasonably expected to cause severe personal injury or death,
unless the parties have executed an agreement specifically governing such use. Moreover,
Würth Elektronik eiSos GmbH & Co. KG products are neither designed nor intended for use
in areas such as military, aerospace, aviation, nuclear control, submarine, transportation
(automotive control, train control, ship control), transportation signal, disaster prevention,
medical, public information network etc. Würth Elektronik eiSos GmbH & Co. KG must be
informed about the intent of such usage before the design-in stage. In addition, sufficient
reliability evaluation checks for safety must be performed on every electronic component,
which is used in electrical circuits that require high safety and reliability function or performance. By using Würth Elektronik eiSos GmbH & Co. KG products, the customer agrees to
these terms and conditions.
GmbH & Co. KG sensor product software and source
code
This License terms will take effect upon the purchase and usage of the Würth Elektronik
eiSos GmbH & Co. KG sensor products. You hereby agree that this license terms are applicable to the product and the incorporated software, firmware and source codes (collectively,
"Software") made available by Würth Elektronik eiSos in any form, including but not limited
to binary, executable or source code form.
The software included in any Würth Elektronik eiSos sensor product is purchased to you on
the condition that you accept the terms and conditions of this license terms. You agree to
comply with all provisions under this license terms.
17.1 Limited license
Würth Elektronik eiSos hereby grants you a limited, non-exclusive, non-transferable and
royalty-free license to use the software and under the conditions that will be set forth in this
license terms. You are free to use the provided software only in connection with one of the
products from Würth Elektronik eiSos to the extent described in this license terms.
You are entitled to change or alter the source code for the sole purpose of creating an application embedding the Würth Elektronik eiSos sensor product. The transfer of the source
code to third parties is allowed to the sole extent that the source code is used by such third
parties in connection with our product or another hardware provided by Würth Elektronik
eiSos under strict adherence of this license terms. Würth Elektronik eiSos will not assume
any liability for the usage of the incorporated software and the source code.
You are not entitled to transfer the source code in any form to third parties without prior written consent of Würth Elektronik eiSos.
You are not allowed to reproduce, translate, reverse engineer, decompile, disassemble or
create derivative works of the incorporated software and the source code in whole or in part.
No more extensive rights to use and exploit the products are granted to you.
17.2 Usage and obligations
The responsibility for the applicability and use of the Würth Elektronik eiSos sensor product
with the incorporated software in a particular customer design is always solely within the
authority of the customer. Due to this fact, it is up to you to evaluate and investigate, where
appropriate, and to decide whether the device with the specific product characteristics described in the product specification is valid and suitable for your respective application or
not.
You are responsible for using the Würth Elektronik eiSos sensor product with the incorporated software in compliance with all applicable product liability and product safety laws. You
acknowledge to minimize the risk of loss and harm to individuals and bear the risk for failure
leading to personal injury or death due to your usage of the product.
Würth Elektronik eiSos’ products are not authorized for use in safety-critical applications,
or where a failure of the product is reasonably expected to cause severe personal injury
or death. Moreover, Würth Elektronik eiSos’ products are neither designed nor intended for
use in areas such as military, aerospace, aviation, nuclear control, submarine, transportation
(automotive control, train control, ship control), transportation signal, disaster prevention,
medical, public information network etc. You shall inform Würth Elektronik eiSos about the
intent of such usage before design-in stage. In certain customer applications requiring a very
high level of safety and in which the malfunction or failure of an electronic component could
endanger human life or health, you must ensure to have all necessary expertise in the safety
and regulatory ramifications of your applications. You acknowledge and agree that you are
solely responsible for all legal, regulatory and safety-related requirements concerning your
products and any use of Würth Elektronik eiSos’ products in such safety-critical applications, notwithstanding any applications-related information or support that may be provided by
Würth Elektronik eiSos. YOU SHALL INDEMNIFY WÜRTH ELEKTRONIK EISOS AGAINST
ANY DAMAGES ARISING OUT OF THE USE OF WÜRTH ELEKTRONIK EISOS’ PRODUCTS IN SUCH SAFETY-CRITICAL APPLICATIONS.
17.3 Ownership
The incorporated Software created by Würth Elektronik eiSos is and will remain the exclusive
property of Würth Elektronik eiSos.
17.4 Disclaimer of warranty
THE SOFTWARE AND IT’S SOURCE CODE IS PROVIDED "AS IS". YOU ACKNOWLEDGE THAT WÜRTH ELEKTRONIK EISOS MAKES NO REPRESENTATIONS AND WARRANTIES OF ANY KIND RELATED TO, BUT NOT LIMITED TO THE NON-INFRINGEMENT
OF THIRD PARTIES’ INTELLECTUAL PROPERTY RIGHTS OR THE MERCHANTABILITY OR FITNESS FOR YOUR INTENDED PURPOSE OR USAGE. WÜRTH ELEKTRONIK
EISOS DOES NOT WARRANT OR REPRESENT THAT ANY LICENSE, EITHER EXPRESS
OR IMPLIED, IS GRANTED UNDER ANY PATENT RIGHT, COPYRIGHT, MASK WORK
RIGHT, OR OTHER INTELLECTUAL PROPERTY RIGHT RELATING TO ANY COMBINATION, MACHINE, OR PROCESS IN WHICH THE WÜRTH ELEKTRONIK EISOS’ PRODUCT WITH THE INCORPORATED SOFTWARE IS USED. INFORMATION PUBLISHED BY
WÜRTH ELEKTRONIK EISOS REGARDING THIRD-PARTY PRODUCTS OR SERVICES
DOES NOT CONSTITUTE A LICENSE FROM WÜRTH ELEKTRONIK EISOS TO USE
SUCH PRODUCTS OR SERVICES OR A WARRANTY OR ENDORSEMENT THEREOF.
17.5 Limitation of liability
Any liability not expressly provided by Würth Elektronik eiSos shall be disclaimed.
You agree to hold us harmless from any third-party claims related to your usage of the Würth
Elektronik eiSos’ products with the incorporated software and source code. Würth Elektronik
eiSos disclaims any liability for any alteration, development created by you or your customers
as well as for any combination with other products.
17.6 Applicable law and jurisdiction
Applicable law to this license terms shall be the laws of the Federal Republic of Germany.
Any dispute, claim or controversy arising out of or relating to this license terms shall be
resolved and finally settled by the court competent for the location of Würth Elektronik eiSos
registered office.
17.7 Severability clause
If a provision of this license terms are or becomes invalid, unenforceable or null and void,
this shall not affect the remaining provisions of the terms. The parties shall replace any such
provisions with new valid provisions that most closely approximate the purpose of the terms.
17.8 Miscellaneous
Würth Elektronik eiSos reserves the right at any time to change this terms at its own discretion. It is your responsibility to check at Würth Elektronik eiSos homepage for any updates.
Your continued usage of the products will be deemed as the acceptance of the change.
We recommend you to be updated about the status of new software, which is available on
our website or in our data sheet, and to implement new software in your device where appropriate.
By ordering a sensor product, you accept this license terms in all terms.