MEMS (sensors)

Hi all,I need to integrate the driver for the iis2mdc magnetometer (Github: https://github.com/STMicroelectronics/stm32-iis2mdc/tree/main) into my own project for a custom board (with STM32H7A3 and i2c3).  The code from the driver requires an additional hardware driver so that the magnetometer can be read/written to. However this interface functions are not included in the driver on Github. int32_t __weak iis2mdc_read_reg( ...) and int32_t __weak iis2mdc_write_reg(stmdev_ctx_t *ctx, uint8_t reg,uint8_t *data,uint16_t len){int32_t ret;ret = ctx->write_reg(ctx->handle, reg, data, len);return ret;} Is there any sample code available, which can be simply adjusted for the specific i2c interface? or do I simply have to replace the call:ret = ctx->write_reg(ctx->handle, reg, data, len);    by  the corresponding    HAL_i2c... calls? Many thanks for any hints.BR GS    

We've implemented an example program based on UM2220 using an lsm6dsox IMU sensor on an STM32U575 microcontroller. We're trying to use MotionFX for orientation calculation from 6 axis measurement, configured with accelerometer and gyro. The IMU sensor is configured to sample at 12.5Hz. Pitch and roll are extracted and printed to a terminalWhat we're seeing is that the output data is stable for a short period of time, however after an indeterminate period of time, pitch and roll become corrupted, spewing (seemingly) random data outWe'd really appreciate any assistance on why this may be happening! We've already tried doubling the stack size of the thread, with no luck

Hello STM32 community,I'm relatively new to STM32 development and I'm currently working with the I3G4250D Gyro Sensor on the STM32F411e-Discovery board. I've been using the stm32f411e_discovery_gyroscope.c file (BSP Drivers) provided by STM32Cube to interface with the sensor.I've managed to retrieve data from the sensor using the provided code snippet:BSP_GYRO_GetXYZ(gyro_data); X_val = gyro_data[0]; Y_val = gyro_data[1]; Z_val = gyro_data[2]; However, whenever I observe the output, the values keep varying even if the system is at rest. Also the output I'm getting seems to be raw data, and I'm not quite sure how to interpret it correctly. My understanding is that these values represent the raw sensor readings, but I'm unsure how to convert them into meaningful X, Y, and Z values.Could someone please provide guidance on how to properly interpret and convert these raw values into meaningful data? Additionally, if there are any specific calibration steps or formulas that need to be

Hi,I have a i3g4250d sensor chip on our custom board with STM32G474 MCU.I have used the below driver github.com STMicroelectronics stm32-i3g4250dfor reading the sensor chip registers through SPI interfaceI am able to read "WHO_AM_I_ADDR" register without any issue that confirms my SPI interface is fine and communicating with sensor chip but when I read XYZ values I always get the same value irrespective of sensor position.My sensor init configurations areCTRL_REG1 = 0x3FCTRL_REG4 = 0x10When I read the STATUS_REG, the first read shows 0xFF and consecutive reads always shows 0x00What could be the problem.PS: I have a Accelero meter sensor chip lsm303agr on the same board configured with I2C interface which is working properly.Thank YouPrabhu M K

Hi,I'm working with the LIS2DW12 accelerometer in a low-power IoT application. The sensor is configured to wake the MCU via an interrupt on INT1, connected through a monostable multivibrator (Schmit trigger IC). The setup is designed so that a rising edge on INT1 triggers a reset of the MCU.Here’s the issue:When the MCU wakes from a previous interrupt (caused by actual motion), it starts reinitializing the LIS2DW12 — performing a soft reset and reconfiguring the registers into polling (standard) mode. Then, after some time in polling mode, if no motion is detected, the program switches the LIS2DW12 back into interrupt mode.At this point, the INT1 pin briefly goes high, creating a glitch pulse even though the system is stationary. This unexpected edge triggers the monostable multivibrator, which in turn resets the MCU — essentially creating a loop. This behavior is not acceptable for my use case.What I’ve tried:Delaying the CTRL4 write until after all other registers are configured (CTR

Hi.i am having a STEVAL-IDP005V1, STEVAL-UKI001V1, 10-pin-IDP005V1 Cable, M12female connector.i am referring this document ( https://www.st.com/resource/en/product_presentation/steval-bfa001v1b_quick_start_guide.pdf ) i am not able to connect the board to my PC.  please anyone suggest me to do the analysis of accelerometeris that any clear document? Thank you  

Hi all, I have installed the LPS22HHTR on my custom circuit to communicate with a STM32F4x via I2C. I have pulled up the SCL (pin 2), SDA (pin 4), SA0 (pin 5), and CS (pin 6) lines to 3.3V via 4.7k resistors, grounded the two ground pins (8 and 9) and RES (pin 3). I have also provided a 100nF decoupling capacitor for the VDD and Vdd_IO pins and left INT_DRDY floating. My issue right now is that when i try to call on the device using its address (0b1011101 << 1) and the HAL_I2C_IsDeviceReady() function, I am not getting a response and a NACK is thrown (I2C_FLAG_ADDR = RESET and I2C_FLAG_AF = SET). I have double checked the configuration of the circuit several times and voltages at pins but I'm still not getting a response.  I would appreciate any help as to why this is happening or if I'm doing something wrong.

HiI am trying to run the STEVAL-IDP005V1-GUI.Current setup:STEVAL-IDP005V1-GUI - > STEVAL-IDP004V1->STEVAL-IDP005V1:I am unable to connect to the IDP004V1 dev kit from the GUI, the comms just gives an error suggesting to restart the GUI. I have tried re flashing the firmware with the 485 and USB binaries provided in en.stsw-io-link (https://www.st.com/content/st_com/en/products/embedded-software/evaluation-tool-software/stsw-io-link.html)I have tried both 485 and USB connections but it does not work. Please advise on how to get the demo's up and runningRegards

Hi, I am using STM32CubeMX to configure STM32CubeIDE project. I have Nucleo-U385RG-Q with MEMS X-Nucleo-IKS01A3. I am trying to read pressure sensor LPS22HH. According the X-Nucleo documentation the I2C default addresses for LPS22HH are: BA and B8. But the C code for the sensor defines BA and B8.Using the STM32CubeIDE project generated by STM32CubeMX I am not able to read sensor ID. The following code gives me an error. In the code I first define: stmdev_ctx_t dev_ctx; dev_ctx.write_reg = platform_write; dev_ctx.read_reg = platform_read; dev_ctx.mdelay = platform_delay; dev_ctx.handle = &SENSOR_BUS;Then use it: whoamI = 0; lps22hh_device_id_get(&dev_ctx, &whoamI);In STM32CubeMX i configured PINs PB6 and PB7 for I2C1. The sensor files "lps22hh_reg.*" I got from GitHub.Can someone please point me to the right direction. Thank you in advance.

Hi all,Could you please tell me if the temperature sensor of the LIS2DW12 is used to correct the acceleration sensor?Thanks all,

Has anyone tested the LIS2DE12TR accelerometer using lower input capacitance? I am interested in trying it out and possibly using it in an intrinsically safe design and the recommended 10uF capacitor is a deal breaker. Alternatively, does ST have a similar low power model that has lower capacitive requirements? 

HelloI would like to get the lis2mdl magnetometer data using the lsm6dsv second i2c line using the sensor hub.so far I get the accelerometer and gyroscope data via SPI and I want to add the magnetometer data.The code I have to configure the sensor hub and retrieve the data doesn't work. The i2c line doesn't even move (I checked with an oscilloscope)I checked with the example here  https://github.com/STMicroelectronics/STMems_Standard_C_drivers/blob/master/lsm6dsv_STdC/examples/lsm6dsv_sensor_hub.c#L504 but I have trouble understanding the codeI have a nucleo board l476RG not the demo board given in the example but since my spi communication works it shouldn't be a problem. I also have several lsm6dsv connected to my MCU but right now I try to make it works for at least one.I use the lsm6dsv_reg and lis2mdl_reg libcan anyone tell me what is wrong and why I can't make this i2c line work?? I've been trying for 3 days alreadyI attached my project  

Hi I purchase a STEVAL MKBOXPro. It connects to phone and app fine but i'm having trouble to get the device connected to MEMS studio and Unicleo GUI  BLE Connection issue... 1. device manager detects STBOX but does not connect on MEMS studio and Unicleo GUI. I Problem with usbc connection.. 2. serial usbc sees COM9 with MEMBS studio but cannot connect to it when I hit connect button  Wondering what's causing the connection issue via bluetooth or via cable? I see a driver titled en.stsw-mkbox-bledk but i there is no exe button to install the driver.       

Hi,I'm developing a prototype based on an already existent product that contains an LSM303AGR, the goal is to install the device in a tower and detect when the tower is tilted or fallen, for this task the idea is to wake up the device via the interruption pin on the magnetometer as the device is battery powered and frequent checks on the status woud decrease the life span on the device too much. The main issue i'm facing is that my device seems too prone to false positives maybe caused by induced vibrations  by the wind on the tower, so far the best results are with the ODR to 1Hz, FS at 2g and adjusted the sensitivity acordingly but this is not an ideal sollution (each device has to be adjusted as the characteristics and eviroment of each tower is different and behaves differently), what is the right way to sense movement but filtering impacts? any sugetions about a good approach for detecting tilt and crash while being power efficient?

Hi all,Could you show me the temperature accuracy of LIS2DW12 ?Thanks all,

Hi,I’m encountering an issue with the LSM6DSOX IMU INT1 pin behavior during initialization. The expected behavior is for INT1 to remain LOW by default, including after a software reset. However, what I’m seeing is:After power-up or reset, the INT1 pin stays HIGH by default.It only transitions to the expected state (LOW) after the interrupt is configured and routed to INT1.I have checked the INT2, it is OK (default LOW)This is causing some unintended behavior during system startup, as other components relying on the INT1 state assume an interrupt has already occurred.Expected behavior:The INT1 pin should be LOW by default and remain LOW after a software reset, until a valid interrupt condition is met.Has anyone experienced similar behavior, or is there any recommended workaround or configuration to force INT1 to stay LOW until explicitly triggered?Appreciate any insights or guidance on this.Thanks

Hi,im currently working on interfacing the STM mems sensors with Beagle Vahead board, im using a kernel version of 6.13 and i tried patching the STM MEMS IIO drivers from link. Im aware that the STM has confirmed the testing of the driver with kernel 6.6.While patching i faced few errors ie mis match in the headders and i have successfully resolved them.im able to boot the device and able to get the device node in the /sys/bus/iio/device  when interfacing the lps22df sensor.when any other sensors (lsm6dsox, lisduxs12,lsm6dsv32) are interfaced on the same bus, im not able to detect the device. i have the same hardware set for lps22df  also. but in that case i was able to get the raw pressure and temperature data.I want to understand the issue why it happens so.i have mentioned the mininal properties on the i2c bus node in DTS file. and have omitted all the optional parameters.have a look at the STM driver booting errors[ 1.143802] st_lsm6dsox_i2c 2-006b: supply vdd not fo

Hi ST Community,I’m trying to use the LSM6DSO32XTR in Mode 2 (SensorHub) to stream data from two accelerometers, two gyroscopes, and a magnetometer into the 9-kbyte Smart FIFO for motion tracking over 10–30 minutes, aiming for low MCU interrupts and power usage.What I’ve Tried:I’ve set up one LSM6DSO32XTR as the master (using its internal accelerometer and gyroscope) and planned to connect a second accelerometer (e.g., LIS2DH12), a second gyroscope (e.g., L3GD20H), and a magnetometer (e.g., LIS3MDL) on the secondary I²C bus (SCx/SDx).I’m using Zephyr RTOS, referring to the datasheet (Section 7.2, 5.4), but learned I can’t connect another LSM6DSO32XTR as a slave on the secondary bus.Questions:1. Has anyone done a similar Mode 2 setup with these sensors? How did you handle I²C addressing?2. Any pitfalls in the Mode 2 config to ensure FIFO streaming works?3. Tips for power optimisation and avoiding data loss over long periods?4. Any alternative methods for this multi-sensor setup?I’d appr

Hello everyone, I'm stuck and I need some help. I have the LIS2HH12 accelerometer connected to my raspberry pi via SPI. So far, I have been able to collect real-time accelerometer data . But my goal is to only get data once the accelerometer is titled or moved(I've noticed that z goes to less than 0.7g when tilted). I'm trying to program the INT1 pin to send a high or low signal to my gpio once movement is detected. But so far, I've failed.   Here's my code, if anyone can please look at it and help a desperate PhD student I would be very thankful! import spidevimport RPi.GPIO as GPIOimport time # SPI Configurationspi = spidev.SpiDev()spi.open(0, 0) # Bus 0, Device 0spi.max_speed_hz = 10000000 # 10 MHzspi.mode = 0b11 # GPIO ConfigurationINT_PIN = 22GPIO.setmode(GPIO.BCM)GPIO.setup(INT_PIN, GPIO.IN, pull_up_down=GPIO.PUD_UP) # Register addressesCTRL1 = 0x20CTRL2 = 0x21CTRL3 = 0x22CTRL4 = 0x23CTRL5 = 0x24CTRL7 = 0x26IG_THS_X1 = 0x32IG_THS_Y1 = 0x33IG_THS_Z1 = 0x34IG_DUR1 = 0x35IG_CFG

Hi, Is it possible to obtain more information regarding the typical performance characteristics of MEMS accelerometers? We are currently evaluating the LSM6DSO32 sensor, and the datasheet is mostly just +/- in terms of accuracy. We would like to see the performance graphs over a range of frequency / temperature / etc.  

Hello,Please , can i use the module STEVAL-MKI228KA (ILPS22QS) with arduino ?Thanks

Hello, I am trying to use the output of the LSM6DSL (accelerometer + gyroscope) to feed an orientation filter. While the accelerometer part is easy to interpret, I am having some trouble with the gyroscope. Apologies if my question is trivial, I have not found any clear answer on the subject so I must have missed something very obvious.   The LSM6DSL returns the angular velocity of the device as a vector of 3 Euler angles, one per axis. With this sort of representation this usually means that the underlying rotation R is a composition of 3 axial rotations, either intrinsic or extrinsic, such as R = R_x * R_y * R_z or any of the permutations. The actual order of the permutation being crucial. The documentation is not 100% clear to me in what order I should apply the axial rotations to describe R. There is no textual mention of this in the Application Note but on page 2 there is a diagram showing: The axis of the accelerometer The rotation Omega_Y, Omega_P, Omega_R Where I guess t

Hi Team,I came across the LSM6DSV16BX, which seems suitable for sports earbuds. Are there any compact earbud-style development boards or hearable devices available on the market?

Hello,I am looking for MEMS accelerometer for seismic application.We need low noise, up to 100Hz bandwidth, full scale +-2g range.I consider IIS3DHHC as a candidate, which has features as below:3-axis, ±2.5 g full-scaleUltra-low noise performance: 45 µg/√Hz16-bit data outputI would like to clarify what is the effective number of bits for 16bit output?How does the Sensitivity 0.076mg/LSB relates to the noise performance?Is there any other products with lower noise?Best regards,Lhagva

Hi based on the quaternion/Sensor fusion of LSM6DSV example I developed an application where I display the direction of a cube. Everything works fine, no drift, but: when I take the device move and turn it around, then put it back in the same exact position, the drawing on the PC is not back to the same direction as when I started.What is going wrong?Thx