MEMS (sensors)

We need ~50k 6-axis IMUs for an application that will experience > 2000dps yaw rate and highly dynamic motion. The spec sheets for the ISM330BX and LSM6DSV32X seem to not paint a complete picture regarding the angular zero-rate at different G_FS angular rate measurement range.We're looking for an ST engineer to make a recommendation for the highest-quality IMU with respect to angular drift and accuracy while in highly dynamic motion. We are interested in IMUs with on-board sensor fusion. Other questions:The ISM330BX seems to be better than the ISM330DHCX in several dimensions, but appears to use a different accelerometer that is not strictly better than what is found in the ISM330DHCX. Is this correct?Is there an IMU that can be classified as "strictly the best" IMU under highly dynamic motion & vibration for mobile vehicle and robotics applications?

 We are currently working on integrating the LSM6DSV16X (IMU) and IIS2MDC (Magnetometer) sensors into our platform based on NXP’s i.MX8MM SoC running Android 10. As Android 10 uses the legacy HAL, we’ve followed the integration steps as per the README documentation.Below are the key configurations and issues we are encountering:Platform & Sensor InfoAndroid Version: 10 (AOSP)SoC: NXP i.MX8MMSensor Drivers: LSM6DSV16X and IIS2MDCHAL Version: 1.0 (Legacy)What We've DoneIntegrated device nodes into DTS as follows: dts

Hello everyone,I'm currently in the process of integrating the ISM330BX IMU to a sensor i'm developping.So far, I have been able to implement this component to my design, communicate with it and read acceleration/gyroscope data.However, the reason that made me choose this component was for its embedded sensor fusion capabilites... And this is where problems start.Enabling the sensor fusion was a pretty straighforward process thanks to the ISM330BX's documentation and examples on Github. But i find the rotations it gives very strange.I noticed a huge amount of drift on the pitch and roll axes (i didn't expect the yaw to be robust and stable without the addition of a magnetometer, which is planned). It also often take way more than the state 0.7 seconds to stabilize its rotation.Currently, my configuration is as follow :- Accelerometer and Gyroscope ODR at 480Hz- Accelerometer, Gyroscope and SFLP game vector (the rotation qu

We have procured STEVAL-MKI197V1 I3C device to validate I3C on the AMD platform, and we have found the slave driver support from the st website and below is the link shared for the same.https://github.com/STMicroelectronics/st-mems-android-linux-drivers-iio/tree/master When we connect the same device to the i2c controller it's getting the address as 6a but when we connect to i3c controller device is not even detectingwhen we checked the in the source code 6a address we couldn't find and tried by adding prints in the beginning of the st_lsm6dsox_i3c_probe function but didn't get the prints too can anyone help it on the issue.

I am using the kernel driver for accelerometer i need to find the accurate step count.Below are the reading for accelerometer from the driver from sysfs parameters and how can i find the step count,root@antler_xedge:/sys/bus/iio/devices/iio:device2#lscurrent_timestamp_clock dev events in_accel_scale in_accel_scale_available in_accel_x_raw in_accel_y_raw in_accel_z_raw mount_matrix name of_node power sampling_frequency sampling_frequency_available subsystem ueventroot@antler_xedge:/sys/bus/iio/devices/iio:device2#cat namelsm6dsl_accelroot@antler_xedge:/sys/bus/iio/devices/iio:device2#cat incat: in: No such file or directoryroot@antler_xedge:/sys/bus/iio/devices/iio:device2#cat in_accel_scale0.000598205root@antler_xedge:/sys/bus/iio/devices/iio:device2#cat in_accel_scale_available0.000598205 0.0

Dear All,We are using the IIS3DWB MEMS accelerometer in one of our products and have encountered an issue with a single unit that we would like your input on. Issue description:On this specific device, the X-axis always reports the maximum negative value (−32768 in 2’s complement), regardless of the selected full-scale range or output data rate. The Y and Z axes function correctly. The issue persists across power cycles and register resets and started after using it for 6-8 months. We have verified the following:• The offset registers are set to 0.• No filters or self-test modes are enabled.• The axis is properly enabled.• The unit was removed from its casing to exclude mechanical stress.• This appears to be a one-off issue; all other units from the same batch are functioning normally. We would appreciate your insights on what might cause this axis-specific satu

Hi,I saw in the datasheet of ISM330DLC that the sensitivity of accelerometer and gyrsocope can deviate at a maximum of 3%. What would be the typical deviation of the senitivity of accelerometer and gyroscope?Thank you!

LSM303AGRTR  The chip is used to calibrate the orientation of the compass, but it is very easy to be interfered with and has the following two problems 1 Calibration is very difficult to calibrate, you need to shake the sensor many times 2. After calibration is done it is very susceptible to interference, resulting in inaccurate compass data Below is the circuit diagram, if you have a mature circuit please send me to see if there are other solutions to the problem. Edit by ST Moderator: This post has been translated from Chinese to comply with the

Tools/Software/etc:SensorTile.box PRO with DATALOG2_Release firmwareSTBLE Sensor app (to trigger data collection)hsdatalog_to_unico.pyMEMS Studio v1.4.1Ubuntu Linux 24.04I watched a handful of webinars and read through tutorials related to the LSM6DSV16X's machine learning core. Most of these covered the basics, but only the basics (as in, they only show the most barebones demonstration with a single sample of a single simple movement). When attempting to generate a decision tree on my own using custom data, I ran into several problems.First, I collected 4 samples of a basic jab motion and labeled the data "strike" and "retract" for each. Everything worked up to the point where I generated the decision tree and got a confidence value of 0%. Then, I attempted to simplify the data and only use one sample of one movement (just the strike component). At this point, I began to see the error below when running the AFS too

Hello ST Team,We are currently building an AI-powered digital pen using ST MEMS sensors (accelerometer, gyroscope, magnetometer) and the STM32WB05KZ MCU. We’ve reviewed the st-mems-finite-state-machine repository and are exploring how the embedded FSM core in sensors like LSM6DSO32XTR can help detect gestures such as:Double tapSwipe gesturesRepetitive handwriting-like motion (“double write”)Tilt-based mode switchingWe are aiming for a low-power design, where motion recognition is offloaded to the sensor and only specific events are passed to the MCU for further processing.Could you clarify:Can the FSM core be extended to detect custom gesture patterns (e.g., two similar ha

I am trying to build a project to detect vibration using STEVAL PROTEUS 1 (STM32WB5MMG, ISM330DHCX and BLE SENSOR). Unfortunately my sensor and BLE does not initialize despite 0 errors.I have used custom BLE Template. I have initialized sensor code in custom_app.c. My inference:Below is the main.c function MX_APPE_Init(); Custom_APP_Init();////  UTIL_SEQ_RegTask(1 << CFG_TASK_BLINK_LED_ID,while (1){   /* USER CODE END WHILE */MX_APPE_Process();   /* USER CODE BEGIN 3 */// HAL_GPIO_TogglePin(GPIOD, GPIO_PIN_2);HAL_GPIO_WritePin(GPIOD, GPIO_PIN_2, SET);

 I am trying to collect accelerometer, gyroscope, and temperature data from the ASM330LHH IMU sensor via SPI by timestamping the exact moment the data is generated. I have connected the INT1 pin of the sensor to the STM32H735RGV6 microcontroller’s PB0 pin and configured it as an external interrupt input. I enabled both the data-ready (DRDY) interrupt and the FIFO threshold interrupt by setting the appropriate registers (CTRL3_C, INT1_CTRL, MD1_CFG, FIFO_CTRL1, FIFO_CTRL3, FIFO_CTRL5, etc.). I verified that SPI communication is working correctly — I can read raw sensor data via polling mode, and the WHO_AM_I register returns the correct device ID. However, the INT1 pin does not toggle or pulse when configured for interrupt generation. I checked the INT1 pin using an oscilloscope and confirmed that it remains static.  Additionally, DWT->CYCCNT is initialized and functional for timestamping.Despite these checks, the interrupt callback (HAL_GPIO_EXTI_Callback(

Hi everyone,I’m developing an application that tracks the path of a device using the ISM330BX IMU and sensor fusion. I’ve based my implementation on ST’s GitHub example for sensor fusion, and the rotation outputs appear to respond correctly when I move the sensor. Pitch and roll are stable, and the orientation updates as expected.However, I’m seeing significant drift in the yaw when the device is stationary. I understand that yaw is difficult to estimate accurately with only a 6-axis sensor (no magnetometer), but I’ve observed a big difference between my application and the ISM330BX demo board (STEVAL-MKI245KA) running in MEMS Studio.For example:On my custom board, I’ve observed drift of nearly 2° per minute at a 3.84 kHz data rate.Lowering the data rate to 30 Hz helps — I now see around 0.5° per minute.In contrast, with the demo board in MEMS Studio (also at 3.84 kHz), the drift is only about 0.1° per minute.I’m t

Hi, I have a compulab SBC (UCMiMX8Mplus sbev) it is a dev kit. I am connecting the STEVAL-55GMBI to the board with the edge connector with our custom board. It is connected to the MIPI-CSI2 connection. I have build the vd55g1 driver with the kernel and the driver is being loaded. Although it does not create the subdevice nodes in the v4l2-ctl --list-devices. I do see errors regarding the setup : [ 10.219820] mx8-img-md: Registered sensor subdevice: vd55g1 4-0010 (1)[ 10.219837] mx8-img-md: subdev_notifier_complete error exit[ 10.219847] mxc-md 32c00000.bus:camera: Sensor register failed[ 10.219853] mx8-img-md: Unregistered all entities[ 10.219857] mxc-md: probe of 32c00000.bus:camera failed with error -515 I have attached the schematics of the adapter board that we have created to connect the SBC to the ST camera board. 

Hello,What is the maximum sustained long term acceleration that the ISM330 can handle before ruining the sensor?I see in the datasheet that the maximum acceleration for 0.2ms is 20,000 G, but I would like to know if it can handle a sustained 100G acceleration for an extended period of time.Thank you!

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 bas

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:

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 variationsIss

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 i

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