MEMS (sensors)

I'm using an IMU ISM330BX on my electric bicycle, and I want to detect while I'm cycling, if I'm ascending or descending a climb, and then calculate which is the angle in degrees or percentage of the slope. For this I'm using Sensor Fusion Function SFLP, which combines accelerometer and gyroscope data, and using the Gravity Vector to calculate the Pitch.When I'm static, not moving the bicycle forward or backward, just lift the front wheel while the rear wheel touches the ground, simulating pedaling uphill. The results are quite good and I can calculate the pitch and transform to degrees.The problem rise when I'm pedalling, then exists acceleration and decelerations, in this situation I can not distinguish if there is a slope (positive or negative) because these accelerations forces are masking the pitch. I tested different filter options trying to acquire the best results, but It doesn't matter which filter option I choose that always I found the same problem

Hello,Will support be added to MEMS Studio for the B-U585I-IOT02A demo board?Thanks.Bruce

I am using STEVAL-MKI142V1 to read the barometric pressure by the LPS25HB MEMS sensor via SPI.The reading pressure always has a 3-4 hpa deviation or offset from the real value. (read by reference device)The RPDS registers already have values and not 0, as the datasheet states. The datasheet states that the accuracy of this sensor is +/- 0.2 hPa guaranteed without further recalibration or temperature compensation.I have also manufactured my own PCB equipped with LPS25HB, and I get the same offset and even larger offset.So, it is not accurate at all and has a large deviation and must have recalibration.The question is:  if I did something wrong while  PCB design, or during assembly, or it's a software issue.  How to get datasheet accuracy without further actions after getting a working sensor PCB ,  just reading pressure ? 

I got the DCR form LPS22HH value is 0x00, but the BCR and TPID value all matched the datasheet except the DCR, and the waveforms as follow: Based on the feature showed in LPS22HH datasheet, the DCR should be 0x62

Hi :We are using lsm6dsl chip on i2c bus.   Our customer request to implement a api interface similar as int setIMUPowerMode(int powerMode, int sensorType);  Noted that in "table 5/6"  the powemode is not a one-to-one correspondence with some registers.  In my unstanding the power mode can't be set directly. Is there anyway to implement the interface?  

Hi,   This webpage suggests that STM can offer ceramic packages for their IMU modules. How would I go about requesting or getting a quote for a ceramic package version of any particular IMU module? thanks   

Hello, I am trying to figure out if disabling the Offset Cancellation on the LSM303AGR would impact the wake up trigger mechanism. From what I could find, the LSM303AGR is an AMR sensor that uses the magneto-resistant property of a film to change its resistance based on the value of an external field. However, a constant bias is present due to imperfections of the sensor and to remove those, a set and reset of the film is performed to create a uniform direction of the resistive elements. When the set and reset functionality is disabled, the film particles will point to arbitrary directions.This bias is similar to a hard-iron offset that will shift the center of the magnetic sphere, however the sensor imperfections bias can drift with time and temperature. The trigger mechanism that we are aiming for needs to wake up the MCU when the relative change in the magnetic field exceeds a threshold. So when the

anyone know who to contact about an error in the datasheets? In the AN6109 (device application note) of the ISM330BX datasheet on page 65/107 in section 8.2 FIFO registers there are three line I believe have errors: – SFLP_GBIAS_FIFO_EN bit of the EMB_FUNC_FIFO_EN_B register in order to enable batching the gyroscope bias data in FIFO (the SFLP embedded function must be enabled)– SFLP_GRAVITY_FIFO_EN bit of the EMB_FUNC_FIFO_EN_B register in order to enable batching the gravity vector data in FIFO (the SFLP embedded function must be enabled)– SFLP_GAME_FIFO_EN bit of the EMB_FUNC_FIFO_EN_B register in order to enable batching the game rotation vector data in FIFO (the SFLP embedded function must be enabled)  these three lines should say EMB_FUNC_FIFO_EN_A register not EMB_FUNC_FIFO_EN_B register.  also, and this part I'm less sure about, on the sam

Hello,I have been working with a NUCLEO-WBA55CG board and the X-NUCLEO-IKS02A1 expansion board. I am running into an issue where the project fails to build after I enable the X-CUBE-MEMS software pack.Here are the steps to reproduce the problem:In STM32CubeIDE, create a new STM32 project using the "Board Selector" for the NUCLEO-WBA55CG.In the Pinout & Configuration view, enable the I2C1 peripheral and assign it to pins PB1 and PB2.Under "Software Packs," enable X-CUBE-MEMS1 for the IKS02A1 and select I2C1 as the communication interface.Generate the code and build the project.After building, I receive the following error messages in the console.

 We have integrated LSM6DSV16X (IMU) and ISM303DAC (magnetometer) on Android 10 running on the NXP i.MX8MM EVK.The magnetometer and accelerometer, gryoscope drivers are working correctly, and raw values are verified using sysfs and logcat.However, the compass heading is always 0°, and the GEOMAGNETIC_ROTATION_VECTOR output from the STM fusion HAL remains constant, even though the raw sensor data is correct.Observed Behavior:Raw ACC, GYRO, MAG readings are valid and updating.Android framework registers all sensors correctly.But heading never changes in any compass or mapping application.Rotation Vector, Geomagnetic Rotation Vector, and Orientation

So i'm trying to install X-CUBE-MEMS1 in the IOC file of a STM32N6-DK board.  The problem i can't seem to install it?  All the tabs are greyed out and have little red cpu marks by them.  Is X-CUBE-MEMS1 supported on STM32N6 processors?   When i go to the github page it also doesn't like there there's drivers for to many chips inside of it?* https://github.com/STMicroelectronics/X-CUBE-MEMS1/tree/main/Drivers 

Hi,It's mentioned in the datasheet that the sensor will convert the FIFO from streaming (reading data all the time) into FIFO (holding the data until it's read) If i am getting it right, then my question isWhen exactly will the sensor read ? Will it read 32 samples after the interrupt and then stops ?Or will it just turn into FIFO immediately after the interrupt ? and discard the samples after the interrupt holding the data before the interrupt ? Thanks 

I was asking can I sense (generate interrupt) over the overall acceleration ?Because in the datasheet it was mentioned that I can manipulate the interrupt between X, Y, Z high and low.But it'd be helpful for me if I can generate an interrupt based on the total acceleration in LIS2DH12 Thanks in advance

Parts i'm looking to connect * STM32N6 - microcontroller * LSM6DSV320X -  Master Sensor IMU * LIS2MDL - On sensor hub Magnetometer     Question - is there any benefit to connecting the IMU master sensor to the LIS2MDL on the sensor hub vs connecting it directly to the microcontroller.     One of the features of this IMU is to generate quaternions but i don't think i can add the LIS2MDL into that equation.  

I tried to connect one MP34DT01 mic to NUCLEO-N657X0Q via SAI peripheral's PDM interface. I included my project's clk configuration, peripheral configuration and main code below.Debugged and when i only touch the mic, value is changing. HELP

Hello.I am using an STM32H562VI board with an LSM6DSV16X sensor,and when I read the whoami value, it reads as 71.I configured the register as follows to check the interrupt on INT1./* Enable Block Data Update */ lsm6dsv16x_block_data_update_set(&dev_ctx, PROPERTY_ENABLE); pin_int.wakeup = PROPERTY_ENABLE; lsm6dsv16x_pin_int1_route_set(&dev_ctx, &pin_int); //lsm6dsv16x_pin_int2_route_set(&dev_ctx, &pin_int); irq.enable = 1; irq.lir = 1; lsm6dsv16x_interrupt_enable_set(&dev_ctx, irq); lsm6dsv16x_filt_xl_fast_settling_set(&dev_ctx, 1); lsm6dsv16x_mask_trigger_xl_settl_set(&dev_ctx, 1); lsm6dsv16x_filt_wkup_act_feed_set(&dev_ctx, LSM6DSV16X_WK_FEED_HIGH_PASS); wu.inactivity_cfg.inact_dur = 0; wu.inactivity_cfg.xl_inact_odr = 1; wu.inactivity_cfg.wu_inact_ths_w = 3; /* threshold resolution to 62.5 mg */ wu.inactivity_ths = 0; wu.threshold = 1; wu.duration = 0; lsm6dsv16x_act_thr

In application note TN1571 "Reference design based on the ST1VAFE6AX and ST1VAFE3BX biosensors..." Table 2 mentions that ST1VAFE3BX has a selectable 50/60Hz notch filter. However, there's no further reference to this filter or how to enable it in the datasheet.Is this an error in TN1571, or something I'm missing.Thank you.  

Hello,I have the LIS2HH12 chip in two separate boards, same board, same firmware.  These devices have been working well, producing X,Y,Z data.  Until today, that is, after a firmware update.This device is the only thing on the I2C bus, 100KHz, 5.1K pullups, 3.3V, connected to an ESP32 S3.  Waveforms on the oscilloscope look clean.The CTRL1 register gets 0x3F and CTRL4 register gets 0x04 which I believe should provide initial functionality.WHOAMI returns 0x41, but STATUS returns 0x00 and all six OUT_ registers return 0, as illustrated below.I have a feeling I've overlooked something really simple.  I've read both datasheet and appnote, and looked through this community for hits on the LIS2HH12.  Thanks for any thoughts or ideas.

Hi,I would like to know what is the stop band attenuation of LPF1 and LPF2 for the sensors ISM330DLC & IIS2DLPC. Thank you!

AN5296Application noteASM330LHH: automotive inertial module digital 3-axis accelerometer and digital 3-axis gyroscope3 Operating modes”To guarantee proper power-off of the device, it is recommended to maintain the duration of the VDD line to GND for at least 100μs."About the statement:If the power is turned on before reaching the GND level, what will be the effect?

Hi, I am working on the LIS2DH12,  I have a problem to the appearance of acceleration data.  I'm using full scale of +/- 2g and ODR of 400Hz.  When the resolution is either 10-bit or 12-bit, only even number acceleration data is read(all x/y/z axis).  The acceleration data is generally correct(but only even number).  When resolution of 8-bit is selected, now both even and odd number acceleration data can be read.  It shows the same appearance for ODR from 1Hz to 400Hz.

Hello,I have a requirement to log the data from evaluation board STEVAL-STWINBX1 to cloud. I have created Azure IOT hub and while initiating the cloud logging from the app i was unable to successfully connect to the created IOT Device created in azure even though the connection string was pasted correctly. the application ST BLE Sensor classic automatically disconnects from the sensor once the cloud logging is enabled. do i need to install the SD card and log the data from card to cloud ? I got struck at this point, is there any specific firmware to be loaded, for now I'm just testing with the basic firmware that provides data from all the sensors to the app

I am looking for information about iNemoEngine sensors in the latest STMicroelectronics HAL for Android.I successfully integrated the STMicroelectronics HAL framework into Android 11. I am using the LSM6DSOTR gyroscope/accelerometer and the LIS3MDLTR magnetometer. These sensors are correctly detected and can be accessed from an Android application. However, the STMicroelectronics HAL also creates iNemoEngine sensors, which do not return any values.The previous STMems_Android_Sensor_HAL_IIO framework used several proprietary STM libraries, including SENSOR_FUSION, GEOMAG_FUSION, GBIAS, MAGCALIB, and ACC_CALIB, to generate the game_rotation_vector, orientation, and rotation_vector sensors. Are these libraries

Hello ST Community,I am currently working on integrating the LSM6DSV16X accelerometer with an STM32H7 series MCU over I²C. Our main goal is to detect the tilt angle of the system. Hardware SetupMCU: STM32H7Sensor: LSM6DSV16X (mounted on a custom board)Interface: I²CSA0 Pin: Pulled high → I²C address = 0x6BPower Supply: 3.3 VPull-ups: 4.7 kΩ on SDA and SCL linesI²C Speed: Tested at both 100 kHz and 400 kHz The setup is straightforward — the sensor is connected to the STM32H7’s I²C1 bus, and it can be successfully detected using an I²C scanner. I’m using the official STMicroelectroni

hello , i am using lsmds0 sensor with nxp board below is the section of my code int main(void) { /* Write your code here */ Clock_Ip_StatusType clockStatus; clockStatus = Clock_Ip_Init(&Clock_Ip_aClockConfig[0]); Siul2_Port_Ip_Init(NUM_OF_CONFIGURED_PINS0, g_pin_mux_InitConfigArr0); Siul2_Dio_Ip_WritePin(MEMS_CS_DRIVE_ENABLE_PORT ,MEMS_CS_DRIVE_ENABLE_PIN,1); i2c_int(); //i2c_scan_bus(); i2c_bustest(); // I2C_ManualBusRecovery(); dev_ctx.write_reg = accelero_write;//assigning read and write pointers to ST driver context dev_ctx.read_reg = accelero_read; dev_ctx.handle = NULL; uint8_t who_am_i = 0; uint8_t ctrl1; int16_t raw_accel_data[3];// variable to store raw 16 bit accelerometer value volatile float acceleration_mg[3];// converted acceleration in milli-g lsm6dso_status_reg_t reg_status; // structure store the register flags lsm6dso_device_id_get(&dev_ctx, &who_am_i); lsm6dso_reset_set(&dev_ctx, PROPERTY_EN