MEMS (sensors)

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 all,I am trying to get started with a LSM6DSV320X accelerometer, using a STEVAL-MKI251A and a Raspberry Pi 4. I can get raw Accelerometer and Gyroscope data from their dedicated output registers (0x22h to 0x2D), but when I try to use the FIFO, I can't get it to work - I get data with tags that are not enabled, with tags that don't exist, and when there's a tag with Accelerometer data, it's incorrect. I've also tried writing the special functions registers to make sure the special functions are disabled and there's nothing of that batched into the FIFO, just to make sure, but that didn't make any change. Currently I've reduced it to as simple a configuration as possible and removed all other code from the test program, and I'm using the following configuration:Read WHO_AM_I register - get 0x73Configure FIFO:Write 0x01 to CTRL3 (software reset)Write 0x44 to CTRL3 (Enable BDU, auto-increment)Write 0x04 to CTRL1 (Acc high performance

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:Please support.

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

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 = lsm6dso3

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