MEMS (sensors)

Dear community,I am selecting an accelerometer to use in a project and I am looking for some advice.Essentially I am looking for the highest performance accelerometer (regarding noise) in the STM portfolio.The sensor requirements are: ~±2g scale support, I2C support (preferred), FIFO buffer, at least 1 (absolute) threshold interrupt. I am currently using the LSM303AGR in my design, which I am comparing to the LIS2DW12 and LSM6DSV16X as a potential replacement. For the comparison (see table), the most important factors are noise and active current consumption in high-performance mode. Note that the LSM303 and LSM6 are not pure accelerometers, since they offer additional functionalities (i.e., magnetometer & gyro). I am only interested in the performance of the accelerometer part.  Sensor

Hi everyone,I'm starting a project using the STEVAL-MKI109D motherboard with the following sensor adapter boards:STEVAL-MKI247A STEVAL-MKI240KA My main goal is to collect sensor data wirelessly for analysis, rather than being tethered to a PC with a USB cable. I'm trying to figure out the best approach and would appreciate some advice on the options I've considered.

Hi! I inherited a project and we're seeing strange accelerometer values and I'd like to get a sanity check on my configuration. when Idle and flat, I see 1g on Z, 0g on X and Y. When my device is moving I see peaks on many axes beyond 1g, eg 2.5 on X or Z, and it does not seem real. Here is downsampled data from a log file. X (brown) goes from +1.5g to -1.5g, Z (gray) is over 2.3g. I am not expecting such numbers during a short banked turn at ~15 mph This is my init. I'm expecting 104Hz data rate, 4g acc scale, 1000dps gyrp scale m_dev_ctx.write_reg = (stmdev_write_ptr) STWriteRegister; m_dev_ctx.

Hi ST guys,I played with the LIS3DH accelerometer options and don't really see difference in interrupts.Can you explain the differences between 6D and no 6D because as per my understanding of AN3308 the AOI + 6D option is position detection which is where I should get an interrupt when position of device is configured.ex : I put 0xF4 in INT1_CFG to enable AOI + 6D + ZHIE, ZLIE and YLIE and it doesn't seem to change when I put 0x34The documentation is also confusing regarding CTRL_REG6 (25h), can you explain  :I2_IA1 Enable interrupt 1 function on INT2 pin.  (is it configuration of INT1_XXX ?)I2_IA2 Enable interrupt 2 function on INT2 pin.  (is it configuration of INT2_XXX ?)I2_ACT Enable activity interrupt on INT2 pin. (What is thi

Hello All,We are adding the IIS2MDCTR magnetic sensor in our existing product.The concern we share is that this is a magnetic sensor and will it affect the MRI machine or its results when installed in the MRI Room.Our product is an Emergency Exit Light a manadatory product but as of now without the magnetic sensor. Please share your feedback. 

Hello!!I just started with the ASM330LHHX DIL24 module for the X-NUCLEO Boards, the module is listed as compatible with the IKS4A1 (sensors below):I have read some documents related to the procedure to make it work but it's an "old" document (see below), I look for general advice:Once the module is inserted do I need to configure any jumpers in the XNUCLEO board?If there is no need to modify jumper configuration on the board, does that mean that all configuration is done via software, correct?Once I gain access to the ASM330, the rest of the sensors onboard the IKS4A1 will be available? all of them + the ASM33

Hi,I am follow up on the query i am posted "https://community.st.com/t5/mems-sensors/integrating-the-sths34pf80-proximity-mems-sensor-using-the/td-p/823236".I am integrating the STHS34PF80 proximity MEMS sensor using the STMicroelectronics HAL from the following repository:https://github.com/STMicroelectronics/st-mems-android-linux-sensors-hal/tree/masterHowever, when I run the HAL binary, I encounter the following error:"root@imx8mp-lpddr4-evk:/st-mems-android-linux-sensors-hal/linux/build# ./stm-sensors-linuxfailed to open config file [/etc/stm-sensors-hal/config], using defa

Hi,I am integrating the STHS34PF80 proximity MEMS sensor using the STMicroelectronics HAL from the following repository:https://github.com/STMicroelectronics/st-mems-android-linux-sensors-hal/tree/masterHowever, when I run the HAL binary, I encounter the following error:"root@imx8mp-lpddr4-evk:/st-mems-android-linux-sensors-hal/linux/build# ./stm-sensors-linuxfailed to open config file [/etc/stm-sensors-hal/config], using defaultsfound 5 IIO devices available under /sys/bus/iio/devicessths34pf80_tmotion: IIO device not supported by sensorHALsths34pf80_tobject_comp: IIO device not supported by sensorHALsths34pf80_tpresence: IIO device not supported by sensorHALsths34pf80_tambshock: IIO device not supported by sensorHAL

Hi, I am using LSM6DSO as my I3C sensor. It works well with RSTDAA and ENTAA. But when I tried to get its PID using GETPID ccc command, it does not work.CCC commands: RSTDAA (CCC: 0x06): Previous assigned dynamic address is removed.ENTDAA (CCC: 0x07): 0x02 0x08 0x00 0x6C 0x10 0x1B 0x07 0x44 (matches the PID, BCR and DCR in the datasheet)GETPID (CCC: 0x8D): 0x03 0xFF 0xFF 0xFF 0xFF 0xFF or just 0x02GETBCR (CCC:0x8E): 0x07GETDCR (CCC:0x8F): 0x7FHere is how I connect LSM6DSO to my I3C host:I tried I2C communication (removing the INT1 connection and leave it unconnected) and I am able to query WHO_AM_I (0x0F)

Hi,  I'm struggling to monitor the debugging values on the MEMS studio. setup1. MEMS studio 2.1.1 (latest version)2. Sensor PRO Tile Box + STEVAL-MKI229A(LSM6DSO16IS)3. ST Official ispu-example GitHub, normhttps://github.com/STMicroelectronics/ispu-examples/blob/master/ism330is_lsm6dso16is/norm/output/norm.json4. ispu-examples/ism330is_lsm6dso16is/norm/output/norm.json    loading this json to the board through MEMS studio5. I can see the entire blank on the "Data Monitor" Page with checked "ISPU Output".6. Toggle the "ISPU Output" to the un-checked state, everything can back to the normal.

I'm new to the STEVAL-DRONE2 kit and would like to ask: Given that the STEVAL-FCU001V2 flight control unit includes basic sensors like the IMU and barometer, can it support the integration of additional external sensors, such as GPS modules, magnetometers, optical flow, LiDAR, or ultrasonic sensors, through STM32? And are there any specific hardware or firmware considerations I should be aware of when adding these to the system?

Hello wonderfull STM community,Really enjoying the experience with MotionFX so far, really easy to implement and get working, well done ST! Even on a G0 in CM0+ mode its working well! I'm just woudring three things:What precaution(s), if any, should be taken when pausing and later resuming the RTOS task that runs MotionFX_CM0P_update()?What is the refrence point for the quatenion in 6x mode? (to be fair I have not worked much with quatenions before so that might be an uneducated question. They are quite complex after all! (pun intended)) Is it normal for data_out.rotation_6x to be near 0 (e-16) during oppration in 6 axis mode? (other values, inlcuding inputs, are changing as expected) 

Hi,Like the post https://community.st.com/t5/mems-sensors/anyone-have-v1-3-1-mems-studio-for-download/m-p/745081 , I search the older version v.1.4.2 of MEMS-STUDIO for documenting my project. Does anyone have the installers of this version ?Thanks,lxaiia  

Hello, Is it possible to add the download links for the old versions of all your software's and resources, like it's the case on the web page of STM32CubeIDE ? In my case, I search to download the versions v1.4.1 and v.1.4.2 of MEMS-Studio for documenting my project. I asked to your support for this in the case 00239175 "How do I get an old version of MEMS-Studio ?", but your employee didn't find this. I think it is important to be able to get the older version of your resources for work on old projects and documenting the bugs and errors encountered. In my case, it's MEMS-Studio, but, in my feedback, I ask this for other of your resources which hasn't the same same system of the web page of STM32CubeIDE. Thanks for your time in the reading of my post. Best regards, lxaiia

Dear all,I am using SensorTile.box STEVAL-MKSBOX1V1 with St app.I made application with vibrometer and output to USB.but the problem when I receive this data with Python code.there is byte misaligned in x,y,z because I started to receive data after streaming.Is there any solution or another firmware to control thisBest regards 

dear all, i want to recoed acceleration date from LSM6DSOX . i made app on st app and made output rate 6666 and output stram to usb. the proplem is i use python to read date from port with serial but the bytes mismatch because the sensor starts streaming then code later and i cant control stream is there idea or solution.stream to sd isnt suitable becaues i nedd live date  best regards

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!

Edit by ST Moderator: This post has been translated from Chinese to comply with the ST Community Terms and Conditions (§10.2). 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.

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