MEMS (sensors)

During the SMT process, air may get blown into the pressure port from the pick-and-place nozzle, will the sensor inside be damaged? 

Did anyone have issue with freezing LPS22DFsensor?Have it connected using 4 wire SPI at 3.3 and 3.3  Volts. It successfully starts and reads temperature and air pressure once and than stays at the same value with no updates until I reset power on it. I can still read the Who_Am_I register which returns the correct valie (zeroed every time after it is read, so no doubt it reads every time) but the Air pressure and Temperature registers not updating. I use NoFIFO setting and sensor updating once per second. What I may be doing wrong?I do not use burst mode for reading and read individual bytes separately (not sure why but burst reading does not work for me)Using MikroC compiler.and PIC18F25K83 MCU

Dear all,We are using the LIS2DW12TR on a custom PCB and have observed significant offset errors on the Z-axis, reaching up to ±20% of full scale.The sensitivity appears to be correct; however, instead of measuring the expected values of +1 g and −1 g, we obtain readings such as +1.17 g and −0.83 g. This suggests a substantial offset while the sensitivity remains largely unaffected.The X- and Y-axes do not exhibit this behavior and remain within specification.The most unusual aspect is, that the offset is not stable. It changes very slowly over time, typically over a period of several days, without any intentional modification of the hardware or software configuration.Has anyone experienced similar behavior with the LIS2DW12TR or identified possible causes such as PCB stress, assembly process effects, flux contamination, humidity, temperature exposure, or aging effects?Any recommendations for further investigation would be greatly appreciated.Best regards,Reto 

Hi, We are using the ASM330LHHTR in our design and would like clarification regarding the INT1 pin configuration. We intend to configure INT1 as an active-low interrupt with the output driver set to open-drain.However, the datasheet seems to indicate that active-low operation requires a push-pull configuration.Kindly let me know the details.Thanks

When setting high pass filter mode to HPM=01, the values in the reference registers (3Ah-3Fh) need different scaling compared to the data output registers (28h-2Dh). I am following the algorithm specified on p.18 of AN4662 using the following C code:void accel_set_reference(void){ int16_t xyz[3]; lis2hh12_acceleration_raw_get(accel1, xyz); // extra dummy read lis2hh12_acceleration_raw_get(accel1, xyz); xyz[0] /= 8; xyz[1] /= 8; xyz[2] /= 8; lis2hh12_xl_filter_reference_set(accel1, xyz); lis2hh12_xl_filter_hp_bandwidth_set(accel1, LIS2HH12_HP_ODR_DIV_50_REF_MD); lis2hh12_xl_filter_out_path_set(accel1, LIS2HH12_FILT_HP);}For some reason, I need to divide the raw acceleration values by 8 before setting them as the reference values.  Observe the graphs of acceleration data I obtain (the step change occurs when this function is called). First, without scaling down by 8:Now when scaling down by 8:Why is this scaling necessary? It is not documented anywhere (as far

Hello Team, We are using a custom board based on QCS8550 processor with LE r90 release. This release has lsm6dsv driver available as part of the ssc framework of the qualcomm. Our custom board includes two LSM6DSVTR IMU sensors which are interfaced over SSC (sensor core based) I2Cs and we are able to get the data through see_workhorse (i.e. qualcomm's userspace utility for sensors) Use Case Requirements: There is a requirement from client regarding sampling the data from IMU sensors on the edge of the reference signal which needs to be provided on the INT2 pin of the LSM6DSVTR sensors. Same reference signal also work as sync signal for the camera as well. so we can consider like sampling the data of IMU and capturing the frame over camera should be somewhat simultaneously. Current Status:In the current driver implementation located at:source/adsp_proc/ssc_drivers/lsm6dsvFrom the driver code analysis, we observed that data is currently being received using a FIFO-based mechanism.Additio

Product https://www.st.com/en/mems-and-sensors/lsm6dsox.htmlAbout the below datasheet description, I want to confirm exact I2C Fast mode Plus timing. Should this SETDASA/ENTDAA follow all timing parameters as I2C Fm+? For NXP I3C, it’s not hard to set a suitable baud rate for this, but it’s impossible to meet all timing for a ENTDAA operation. Can ST I3C IP run ENTDAA with I2C timing to meet your sensor product?  

Hello,I am using the STWIN.box with the DATALOG2 firmware and would like to acquire data based on an external trigger signal from a speed sensor.My speed sensor provides an open-collector output, which is connected through appropriate signal conditioning to the STWIN.box.I would like to know:What is the recommended way to use an external GPIO as a trigger source in DATALOG2? Can a GPIO interrupt (EXTI) be used to start data acquisition or mark events in the recorded data? Are there existing examples in DATALOG2 that use external trigger inputs? Which GPIO pins are available for this purpose on the STWIN.box? For an open-collector speed sensor output, should I use an internal pull-up or an external pull-up resistor?My goal is to trigger or synchronize vibration measurements with the rotational speed signal.Thank you.

Hi ST community,Below is what I have setup for the sensorhub interface between LSM6DSO and H3LIS331DL Goal: Read H3LIS331DL WHO_AM_I (0x0F → expect 0x32) via LSM6DSO Mode 2 sensor hub (MCU ↔ LSM on main I²C; H3LIS on SCX/SDX).SetupH3LIS: CS→VDD (I²C), SA0→GND (addr 0x18), SCL/SDA→LSM SCX/SDX Hub: 1 slave, MASTER_CONFIG = 0x4C (WRITE_ONCE | SHUB_PU_EN | MASTER_ON), SLV0 read of 0x0F Trigger: internal (XL ODR ~104 Hz, START_CONFIG = 0) — not using INT2 / H3LIS_DRDY for this Readback from SENSOR_HUB_1 with embedded-page access (SHUB_REG_ACCESS=1)What we seeLSM6DSO itself is OK (WHO = 0x6C) After arming the hub: STATUS_MASTER ends as 0x09 → ENDOP=1, SLAVE0_NACK=1 SENSOR_HUB_1 = 0x00 (expected 0x32) Scope on SCX/SDX: lines go from low → high when hub pull-ups enable, then stay high — no visible I²C clock/data bursts Same result after resoldering / swapping H3LIS; also tried addr 0x19Question: With Mode 2 + internal XL trigger, why would we get SENSOR_HUB_1 =0x00 . It seems that the sensorhu

Hi ST team,We are using the LSM6DSV80X SFLP quaternion output for a smart racket project. The quaternion is used by the mobile APP to control the game character posture.During our test, we found that when the racket is powered on in a flat/horizontal position, the SFLP Yaw output can stay close to 0°, which is expected. However, when the racket is powered on or reset in a tilted position, the Yaw value is affected by the current Pitch/Roll posture and cannot remain at 0°.For example, when the racket is powered on in a tilted position, the output is:Roll = -0.58°Pitch = -37.61°Yaw = -9.40°For our racket game application, the expected behavior is:When the game starts or when the user performs posture reset, the current racket facing direction should be defined as the game coordinate system Yaw = 0°. At the same time, Roll and Pitch should still reflect the real physical tilt of the racket.So the requirement is not a full orientation reset. We only need a Yaw-only reset:Yaw should be rese

I’m trying to build a device that detects shaking using a LIS3DH, and then interrupts a Seeed XIAO RP2040 so that it can tell an OLED display to show numbers. I am using an LIS3DH in I²C mode. I want INT1 on the LIS3DH to wake a Seeed XIAO RP2040 from sleep when motion exceeds a threshold. Do I need to use INT1, SDA, and SCL, or could I just use INT1 to make this work? I’ve attached an electrical schematic of what I have right now, but I’m not quite sure if the connections between the LIS3DH and Seeed XIAO RP2040 are correct.  

Hi sir,I have a question regarding the hardware connection of Pin 3 (SCx) on the LSM6DSOW when operating in Mode 1.According to the datasheet, Pin 3 should be connected to VDDIO or GND in Mode 1. However, in our current design, this pin is connected to an MCU GPIO to maintain hardware compatibility with another project that utilizes the Sensor Hub (Mode 2) feature. Our intention is to drive this GPIO LOW to satisfy the Mode 1 requirement.We have a concern regarding the power-up sequence: In our system, the IMU and MCU are powered simultaneously. However, there is a short delay during the MCU's boot-up phase before the GPIO can be initialized and driven LOW. During this window, Pin 3 of the LSM6DSOW will be in a floating state (input without pull-up).Our proposed software flow is as follows:System power-up (IMU and MCU together).MCU drives the Pin 3 GPIO to output LOW as soon as its firmware initializes.MCU issues a Software Reset (SW_RESET in CTRL3_C, 12h) to the LSM6DSOW.Proceed with

Configuration:I2C address: 0x6A Bus speed: 100kHz (standard mode) ODR: 1920Hz for both XL and GY (ISM330BX_XL_ODR_AT_1920Hz, ISM330BX_GY_ODR_AT_1920Hz) Full scale: ±125dps gyro, ±4G accel Reading a 14-byte burst starting at register 0x20 (TEMP + GYRO + ACCEL) once every 10ms, from our control loop. The application currently checks the IMU every 10ms.My intention is:Every 10ms, determine whether a fresh IMU sample is available. If fresh data is available, start one interrupt-driven burst read (gyro + accel). When the transfer completes, update the application variables once. Ignore intermediate samples produced by the IMU between 10ms periods.Polling-based implementationInitially, we have implemented the IMU driver using a polling-based I²C implementation (partially based on an open-source GitHub driver). During long-duration testing, the application hung/resetting inside the blocking I²C loops. Code for this method is attached in attachment 1.Interrupt-based implementationTo overcome t

Hi Champs,the D/S of both LSM6DSV and LSM6DSV32X gives the same WHO_AM_I defaul value (01110000b = 0x70).is there a way to differentiate both IMUs?thanks in advance.Warm regards,Agnès

Hello,The self-test for the ISM330DHCX failed.What could be the cause?I performed the self-test following the procedure in application note AN5398.The test failed (NG) on the negative side of the Z-axis for the gyroscope function.When measuring the I2C waveforms, the data output by the IC at registers 26h and 27h showed values ​​consistent with a self-test failure.Incidentally, I am turning to this community because the distributor's support has been poor.Regards,  Japanese memoこんにちはISM330DHCXのセルフテストに失敗した。原因は何が考えられるか？アプリケーションノートAN5398の手順に沿ってセルフテストを行った。ジャイロセンサ機能のZ軸のネガティブでNGが出た。I2C波形を測定するとICが出力しているデータ26ｈ、27ｈのデータがセルフテストNGになるような数値を出力している。ちなみに商社の対応が悪いからこのコミュニティを頼っている。

The HTS221 is marked as Obsolete, and the only suggested alternative is SHT40-AD1B - a 3rd-party device. Has ST abandoned this product area?

Figure 14 - Operating modes transition diagram - does not show it: and neither does Table 16 - Operating modes transition criteria: The description of the “reset mechanism” doesn’t really relate to the above state diagram or table: 

I am using an LPS22DF over I2C with an STM32WB5MMG. The sensor is configured for continuous 1 Hz operation, AVG = 64, LPF1 = ODR/4, and continuous dynamic-stream FIFO mode. FIFO samples are retrieved as separate three-byte reads from registers 0x78–0x7A.The first FIFO read after every watermark interrupt is consistently corrupted by approximately +32 hPa. For example, the first value may be raw 4130956 (1008.534 hPa), while the following values are approximately raw 3999700 (976.49 hPa) and agree closely with the standard PRESS_OUT registers. The difference is close to 131072 counts, corresponding to bit 17 of the 24-bit pressure value. This occurs repeatedly for every FIFO batch, not only during startup or LPF settling.  Our operational workaround is to set the FIFO watermark to 11, read eleven three-byte data sets individually, discard the first result, and average the remaining ten. Is this first-read corruption a known LPS22DF behavior or erratum? Is there a required FIFO read sequ

Hello ST Community,We are using LIS2DW12 in single data conversion on-demand mode.Configuration:- MODE[1:0] = 10, single data conversion on-demand mode- SLP_MODE_SEL = 0, output data generation triggered by INT2 external signal- INT2 is used for Data update trigger- INT2 is driven by an MCU GPIOAccording to the LIS2DW12 datasheet, INT2 is described as a clock input when selected in single data conversion on-demand mode, and INT2 clock input supports up to 200 Hz.However, we could not find the AC timing specification for the INT2 input trigger.Could you please clarify the following points?1. What is the minimum HIGH pulse width required on INT2 to guarantee a trigger?2. What is the minimum LOW pulse width required before the next trigger?3. Is the trigger detected on the rising edge, falling edge, or by the HIGH level?4. Is it required to keep INT2 HIGH until DRDY is asserted, or is a one-shot pulse acceptable?5. Are these timing values guaranteed over process, voltage, and temperature?

HI,      It appears that the LSM6DSO32X has a higher shock/acceleration rating when compared to the automotive rated ASM330 IMU modules. 20’000g rating for the LSM6DSO32X and a 3’000g rating for the ASM330 modules.  Am I reading that right? The automotive modules have a lower shock rating than the consumer module?  thanks   

We are considering using IIS2ICLX for product development.I would like to know the following specifications for this product. ① “stability” of “bias” with respect to a fixed calibration value over a period of one year② “stability” of “scale factor” with respect to a fixed calibration value over a period of one year 

Regarding the behavior of temperature drift of the IIS2ICLX, I would like to ask for your guidance.- When the temperature increases, how does the zero-point temperature drift behave?- Does the amount of zero-point drift change depending on the rate of temperature increase?For example, after heating rapidly to 80°C and then allowing the temperature to stabilize sufficiently, compared with slowly heating to 80°C and allowing the temperature to stabilize sufficiently.

Hello,I am currently working with the IIS2ICLX MEMS inclinometer sensor, and I am unable to find the noise spectral density curve as a function of frequency.Would it be possible for you to provide it, in particular for the low-frequency range (0.1 Hz, 1 Hz, 10 Hz, etc.)?Thank you very much in advance for your help.Best regards,

Dear Community,I am currently following the official MEMS Studio tutorial "Module 5 - MLC Configuration and Visualization" available on YouTube.I am using the following hardware and software setup:MEMS Studio version: 2.4.0 Board: NUCLEO-F401RE with X-NUCLEO-IKS4A1I was able to successfully complete all tutorial steps up to the Automatic Filter & Feature Selection (AFS) stage. However, whenever I click "Run" in the AFS tool, MEMS Studio displays the following error message:"Unexpected error with code 104 occurred during AFS request processing."The issue occurs consistently, even though I am following the tutorial exactly as shown in the video.Additional information:The PC has internet access. I tested both my company network and a mobile hotspot, but the error persists in both cases. No firewall events indicating blocked connections were detected. The board is correctly recognized by MEMS Studio and all previous steps work as expected.Could you please help me identify the cause of

Hi, I'm seeing a consistent issue where every sensor connected via I²C (as far as I can tell) produces 0 bytes of streamed data over USB:HTS221 (temperature + humidity) LPS22HH (pressure + temperature) STTS751 (temperature) IIS2MDC (magnetometer)At the same time, all SPI-based sensors stream normally:IIS3DWB IIS2DH ISM330DHCX (accelerometer + gyroscope)Both microphones also work correctly.Execution details:Board: STEVAL-STWINKT1BFirmware package: FP-SNS-DATALOG1 v1.5.1 (Utilities/HSDPython_SDK included)Host SDK: HSDPython_SDK (st_hsdatalog 3.0.1, st_dtdl_gui 2.1.0, st_pnpl 2.1.0), Python 3.10, Windows 10Connection: USB (WinUSB), using hsdatalog_cli.pyResult (consistent across multiple runs and after a full USB power-cycle of the board):Name                  Length----                  ------AcquisitionInfo.json     226DeviceConfig.json      28090HTS221_HUM.dat             0HTS221_TEMP.dat            0IIS2DH_ACC.dat         76608IIS2MDC_MAG.dat            0IIS3DWB_ACC.dat      1542000IM