MEMS (sensors)

Hello,I have a case where my IMU (ISM330) can see peak accelerations above the 16G limit.How does this effect the output of the sensor?Could this cause aliasing of my data or would it just cause me to see a lower amplitude?Thank you! 

 Can someone please provide a working download file for "STM32Cube function pack for STEVAL-PROTEUS1 sensor datalog and file transfer over BLE and USB"?The ZIP-File Version is corrupt.It cannot be extracted neither on Windows, Linux or Mac.Thank you.@

Hello fellow users! I'm trying to implement the Fusion MOTIONFX library with the board X-NUCLEO-IKS02A1 and the nucleo board NUCLEO-U575ZI-Q so I can output via terminal all the values. So far I can output the fusion values but they are wrong as I need to define the sensors orientation on the PCB board (real world) and there is no documentation that indicates this for the IKS02A1 (I also have the IKS4A1 and such info also is not avilable) So will be nice of ST to have a:1)definitive guide or schematic showing the physical orientation of the sensor axes (ISM330DHCX, IIS2MDC and IIS2DLPC) on the X-NUCLEO-IKS02A1.2) The recommended orientation strings (acc_orientation, gyro_orientation, mag_orientation) for this specific board.3) Clarification: Does the user need to remap the sensor axes manually in code to match the declared orientation strings? Or does MotionFX internally handle axis rotation based on the strings?4) Ideally: an official reference example with working

Hi,I am currently working on a project using the STHS34PF80 proximity sensor from STMicroelectronics. The platform is running Android 14.0.0_1.0.0 (L6.1.55_2.2.0 BSP). I would like to know if there is a dedicated Android driver or SDK available to directly interface with the STHS34PF80 sensor—either from STMicroelectronics or open-source contributors. I have the datasheet and application notes for the sensor, and I understand its I²C communication protocol. However, before starting from scratch, I’d like to ask: 1) Any existing Android libraries or HAL implementations 2) Sensor integration examples in Android (preferably for NXP i.MX8M Plus - based platforms) Any examples or references would be greatly appreciated. Thanks in advance for your support!

Hello.I am working with the STM32U083 and LIS2HH12TR communication via SPI. Did the SPI settings configuration in mode 3 and build a simple project in cube ide to identify and read the accelerometer data.The project also does the conversion in mg of the acceleration for all axis. When I move the axis I was expecting the values to change but there is no change as in picture below: (Debug data via uart ). Does anyone come out with this kind of problem ? Could it be sensor (accelerometer) damage, a soldering problem, or something else?Following the terminal log:Please support.Thankyou

Hi,We are implementing a compass application using the LIS2MDL magnetometer sensor and experiencing incorrect direction readings due to the sensor's left-handed coordinate system. The raw sensor data is functioning correctly, but standard compass calculation algorithms designed for right-handed coordinate systems produce inaccurate results.Issue Summary:Sensor: LIS2MDL 3-axis magnetometerProblem: Compass calculations yield incorrect directions (primarily showing North/East instead of full 360° range)Root Cause: LIS2MDL uses left-handed coordinate system (confirmed from ST Community forum discussion)Impact: Standard compass algorithms fail to provide accurate bearingsTechnical Details:Raw sensor readings are stable and changing correctlySensor communication and initialization working properly (WHO_AM_I = 0x40)Sample raw data shows expected magnetic field variationsIssue occurs during coordinate system conversion for compass heading calculationsCurrent Environment:Platform: Embedded Linu

Hi,We are using 4 ASM330LHB in our application. We have placed 4IMU's on PCB. We put the PCB in temperature chamber to observe the sensor behaviour during the temperature variation(cooling) with 1deg/min from 30 to 60 to -20.During this test all sensors in static only. During cooling, the sensor bias or readings changed significantly as shown in attached file. Why sensors readings changed significantly?.Each plot has 4gyroscope readings. In attached file The last 3Plots are zoomed version of first 3plots respectively.

Hello ST Community,I’m currently working on a project using the LIS2DW12 accelerometer sensor connected to a Nordic nRF9151 module. The firmware is based on Zephyr RTOS from the Nordic Connect SDK v2.9.0.For our use case, we need to configure the LIS2DW12 to generate two separate interrupts, for example:One interrupt for activity/inactivity detection.Another interrupt for free-fall or motion detection.I would like to know:Is it possible to configure and use two independent interrupts from the LIS2DW12 sensor?If yes, which registers need to be configured and what is the recommended configuration for enabling and mapping two different interrupts (e.g., INT1 and INT2)?Are there any best practices or constraints to consider when working with dual interrupts on this sensor?Any guidance, register-level documentation, or example configurations would be greatly appreciated.Thank you,Manoj

Hello everyoneI would like to generate two different interrupts (INT1 and INT2) to detect free fall and tap.I am using MEMS studio to verify the configuration of the registers.I am using a F401RE development board with an IKS4A1 expansion that integrates the LIS2DUXS12 sensor.Question 1) why is the Sensor evaluation->Interrupt->Acc interrupt page not showing the signal for interrupt 2?Question 2) why are the options to enable INT2 interrupts not made available?Question 3) I have done many tests but INT2 seems to be unmanaged. I have simplified everything to a very simple test: in the interrupt config I select Free Fall [INT1] (which works and is represented) and then manually edit the MD2_CFG register setting it to 0x10 (so that I can be sure that the configuration for free fall is correct and then I enable the FF route on INT2 as well)I would expect that by exporting the data via the save to file page to see an output where two interrupts change together. Instead, what I get is

We observe mutually exclusive behavior in the LSM6DSVX driver:With interrupts DISABLED:Can successfully read raw values via sysfs: cat /sys/bus/iio/devices/iio:deviceX/in_accel_x_raw # Returns valid dataWith interrupts ENABLED:Sysfs reads return 0:  cat /sys/bus/iio/devices/iio:deviceX/in_accel_x_raw # Returns 0Kernel driver appears functional (interrupts fire in dmesg)HAL receives flush events but no sensor dataDebugging Performed:Confirmed IIO buffer configuration:  echo 1 > /sys/bus/iio/devices/iio:deviceX/buffer/enableVerified no resource conflicts (lsof /dev/iio:device*)Tested with/without FIFO mode - same behaviorSuspected Root Cause:Driver may be locking out sysfs reads when interrupts are active, or buffer ownership isn't properly shared between interrupt and sysfs access modes.Request:Could you clarify:Is this expected behavior in the LSM6DSVX driver?Recommended workaround to allow both interrupt-driven AND sysfs access?Any known patches o

If the electrode is embedded in an insulator, isn't the sensing process dielectric polarization rather than electrostatic induction?The following text is quoted from 「Application Note "Qvar sensing" (AN5755) p2.「 A signal is derived from the electronic circuit due to the fluctuations in the electric field resulting from the passage of the charged particles. If the electrode is embedded in an insulator or there is no direct contact between the electrode and the particles, the sensing process is achieved through electrostatic induction. 」

Hello Everyone, Have anyone measured the latency from sensing the physical motion to the output of the sensor? I couldn't find in the datasheet how much time the filters takes. Thanks

Hi There, I've designed a board which uses a LSM6DSO32 sensor over i2c for accelerometer, gyro and it's embedded pedometer function. I've been able to reliably get data from the sensors accelerometer and gyro registers however I've not been able to get it to return pedometer data. I'm aware of AN5473 and have followed this in my own application and have also implemented the public C driver for this IC found on github. I'm initialising the pedometer as follows```int lsm6dso32_init(void) { int32_t ret; uint8_t rst; if (!lsm6dso32_is_available()) { LOG_ERR("I2C device not ready"); return -ENODEV; } /* Initialize STM driver interface */ dev_ctx.write_reg = platform_write; dev_ctx.read_reg = platform_read; dev_ctx.mdelay = platform_delay; dev_ctx.handle = (void *)&dev_i2c; /* Wait sensor boot time */ platform_delay(10); /* Check device ID */ ret = lsm6dso32_device_id_get(&dev_ctx, &whoami_value); // if (ret != 0 || whoami_value != LSM6DSO32

Hello, I’m using the LIS2DU12 accelerometer and trying to perform the positive self-test exactly as described in the official application note. However, I’m consistently seeing results that do not meet the expected deviation thresholds, and the self-test fails on all axes. I’ve double-checked the register writes and delays and followed the datasheet carefully. If anyone has a known working configuration or insights on what might be going wrong, I’d appreciate your help. Thanks!

Hi,Where can I find inforamtion on Moisture sensitivity level for each sensors? I checked datasheets and few other documents in the product page but couldn't find it. I want to know the MSL of IIS3DWB.Best regards,Kev

Two LSM6DSVQ IMU sensors have been interfaced on the same I3C IBI bus. In normal working scenario all the transfers be it from master or slave side are working fine.In the problematic case while generating an IBI, from the waveform capture the SCL is being driven to low before SCL (incorrect start condition) and thereafter the SDA line is continuously held to low.Which amongst the master and slave can be the reason for incorrect start condition and can this cause the slave to go in bad state leading to holding the SDA line to low?  

Dear all,I would be interested to use a MKI109D dev board (with USB C connector) to stream data from a MKI178V2 board fitted with a SM6DSL IMU sensor to a preferably a python or cpp based script using something like a pyserial library. I have tested the board and the IMU with the MEMS Studio software and flashed it with the correct firmware , and therefore can see the IMU output as intended. However when trying to connect  to the dev board using pyserial, after opening the COM port , and transmitting the *dev command, I receive an error that the device is not supported. I would appreciate some help on some direction as to what the problem here might be and if possible a minimal set of python (or cpp) command to read out the IMU data. Many thanks in adveance.  

Hi, i have a question, is it possible to use the embedded STLINK on the nucleo-f446re for programming the sensortile.box (steval-mksbox1v1) ? If so, how do i have to connects the pin? I have a JTAG Adapter v1.0 (included in the sensortile box), so i'm thinking about connecting it to the sensortile using the STDC14 connector, but how do i connect the adapter to the nucleo board? Do i only have to connect the CN4 pins (SWD) from the nucleo to the adapter?Thanks for the help

I've had this problem with an ILPS22QS and now I'm having it with an LPS22HH. It has me completely mystified. The issue is like this: The pressure sensor works as normal for a week or even multiple weeks and then all of a sudden it enters a mode where it no longer reacts to pressure changes properly. Instead it looks more like a capacitor where pressure peaks increase the value of the sensor and if there are multiple in quick succession they add up. Once the pressure goes back to environmental pressure the value slowly goes down. A picture illustrates this better. The picture is a recording of pressure values from 2 sensors of type LPS22HH on the same PCB. They've both been working fine for about a week now. Today one of them entered the weird-mode. Power-cycling does nothing. I've unplugged and replugged the PCB multiple times. The firmware of the PCB has not been changed, nor does it have non-volatile memory that could change its behavior. For both pressure sensors I take a drinking

I am leading a project in the automotive sector where we are using the ASM330LHH for mass production (we have assembled more than 2000 units). Our reading method involves not using the DATA-READY or interrupt; instead, we read at a rate of 417 Hz with our microcontroller's clock. To verify that the temperature compensation meets our quality standards, we conduct a temperature test ranging from -30 to 95 degrees on all units. During testing, we've observed that approximately 40% of the units exhibit spurious measurements at a specific temperatures. This issue is reproducible over time; repeating the test with the same unit consistently shows problems around the same temperature. These anomalies are spikes, consistently appearing in the X and Y-axis gyroscopes but never in the Z-axis gyroscopes or accelerometers. The BDU register is activated. I would like to understand why these issues might be occurring, as they significantly impact production. Thank you

I'm currently working with the LSM6DSV16X IMU and would like to connect an external sensor—specifically the SHT40 (a humidity and temperature sensor from Sensirion)—via the Sensor Hub feature.My hardware setup uses SPI for communication between the microcontroller (master) and the LSM6DSV16X. The SHT40 is connected to the LSM6DSV16X via the I²C interface (Sensor Hub port). Already got the other two sensors(LIS2 and LPS22) working.Here’s what I’m trying to accomplish:Trigger a measurement on the SHT40 through the Sensor Hub (Slave 0 write)Read the result using Slave3 (external sensor read)Eventually collect the data via FIFO or directly through Sensor Hub registersQuestions:Is it possible to interface the SHT40 as an external sensor through the LSM6DSV16X Sensor Hub while using SPI as the main interface to the host?The SHT40 does not use register addressing (i.e., it does not support a subaddress). Does the LSM6DSV16X Sensor Hub support communication with devices like this?Are there any

Hello, I’m working with the LIS2DW12 vibration sensor for single-tap detection. I have configured the sensor registers according to the application note for enabling single tap. When I continuously read the TAP_SRC register in polling mode, I’m able to detect single taps successfully. However, I want to use interrupts instead of polling. I have connected the LIS2DW12’s INT1 pin to the PE7 GPIO pin of my STM32L496 controller. Despite this, I am not receiving any interrupt signal on PE7 when I tap the sensor. please check the single tap init function : void LIS2DW12_Init_Single_TAP(void) { message[0] = 0x74; if(HAL_I2C_Mem_Write(&hi2c3, LIS2DW12_Adrr, CTRL1, 1, message, 1, 1000)==HAL_OK) { message[0] = 0x0C; if(HAL_I2C_Mem_Write(&hi2c3, LIS2DW12_Adrr, CTRL6, 1, message, 1, 1000)==HAL_OK) { message[0] = 0x09; if(HAL_I2C_Mem_Write(&hi2c3, LIS2DW12_Adrr, TAP_THS_X, 1, message, 1, 1000)==HAL_OK) { message[0] = 0xE9; if(HAL_I2C_Mem_Write(&hi2c3, LIS2DW12_Ad

volatile UB__8 ubAisRxData; volatile UB__8 ubSpiStatus = 0; void SPI_vInit(void) { disable_interrupts(); configure_D_OUT_SPI_MOSI_Pin(); // PTBDD_PTBDD5 = 1; // MOSI configure_D_IN_SPI_MISO_Pin(); //PTBDD_PTBDD4 = 0; // MISO configure_D_OUT_SPI_CLK_Pin(); // PTBDD_PTBDD6 = 1; // SCK set_CS1_high(); // Sensor 1 disable set_CS2_high(); // Sensor 2 disable // SPI Control Register 1 SPIC1 = 0xD4; // SPE=1, MSTR=1, SSOE=0, CPOL=0, CPHA=0, SPIE=1 //SPIC1 = 0xF0; // SPE=1, MSTR=1, SSOE=0, CPOL=0, CPHA=0, SPIE=1 // SPI Control Register 2 SPIC2 = 0x00; // SPI Baud Rate Register (set to suitable speed) //SPIBR = 0x10; // Divide bus clock 16 Mhz, spi clock 5,33Mhz SPIBR = 0x11; // Divide bus clock 16 Mhz, spi clock 4 Mhz // Clear status flags by reading SPIS and SPID (void)SPIS; (void)SPID; enable_interrupts(); } void SPI_vSendByte(UB__8 ubSpiTransfer, UB__8 ubSpiChannel) { volatile UB__8 ubAisStatus; volatile UB__8 ubAisRx; while (!(SPIS)); // Wait until transmi

Hi all, I’m working on a project using the STEVAL-STWINBX1, and my main goal is to use the IIS3DWB vibration sensor as a high-speed vibrometer. I’m still pretty new to embedded programming (about 2 months in), so please bear with me! Project setup so far: Board: STEVAL-STWINBX1 (STM32U585AI MCU) Using: Only the IIS3DWB vibration sensor (not the other sensors for now) Peripherals: SPI2 (for IIS3DWB), UART2 (for debug/streaming), FreeRTOS Goal: Read high-frequency vibration data, and eventually store it for later analysis What I’ve tried: I set up IIS3DWB via SPI2 and am running it at the full 26.7 kHz ODR (output data rate). Because the data rate is so high, using an interrupt for every data-ready signal floods the CPU. To handle this, I enabled the IIS3DWB internal FIFO (3KB, ~200 samples), set a watermark/threshold, and use the FIFO threshold interrupt to trigger reading. My ISR releases a semaphore, which a FreeRTOS task then picks up to read out the FIFO using: &n

Hi,I am working on an accelerometer interrupt using the LSM6DSM. In AN4987 I found that I can configure the slope filter to use a window of WK_DUR samples that consecutively exceed WK_THS based on the given formula. I found good threshold settings for the slope filter, but that required me to filter out unwanted interrupts using the WAKE_UP_SRC (if X_WU or Y_WY and not Z_WU) after an interrupt. Is there a way to use a binary operator to filter out interrupts on an hardware level?That lead me to believe that I would need to use the high-pass filter. However, it is not explicitly stated how exactly the wake-up interrupt behaves, the only clue that I found was the following statement:"The wake-up interrupt signal is generated if a certain number of consecutive filtered data exceed the configured threshold". Would that be for a given window (WK_DUR) that every sample should exceed WK_THS compared against the previous sample?Thanks,Bart