MEMS (sensors)

Hi,Does ST have any plans to manufacture FLIR (Forward Looking InfraRed) MEMS sensors in future?Will 

I am currently trying to build a motion detector like application using a LSM6DSV80x and it's MLC in combination with MEMS Studio (fw 2.2.0). To do so, I use the standard DataLogExtended firmware on a NUCLEO-F401RE and can successfully log and visualise data in MEMS-Studio. The MLC training can also be done successfully, and I can flash the MLC from MEMS Studio as well as use the Decision Tree Output Viewer.But then, when I want to tweak the parameters or understand what is going on, I am missing the MLC Debug Tab in MEMS Studio (as referred to in UM3233 (MLC section) completely and cannot test on already recorded data (see picture attached).So where can I find the Debug MLC Tab in MEMS Studio 2.2.0? If it was removed, which is the last MEMS Studio version that supports it?(Tested both on Mac and Windows -> same issue)  

Hello,I'm working with the Vibration Monitor use case available in the Example Apps of Steval SensorTile.Box MKSBOX1V1. I'm quite happy with how it works, but I would like to modify some parameters and here comes the problems (both modifying the already available apps and creating new ones from the scratch in the expert mode). The app consists of two steps, one creating the vibration profile of the monitored object (Vibration Monitor - Training) and the second finding the differences between the current vibration profile and the reference one to identify anomalous vibrations.If we give a look to the settings of this example app, which is correctly working, we can see among the the parameters of the Vibrometer Accelerometer Sensor that the Output Data Rate (ODR) is set to 6666Hz and by default it can stream data over Bluetooth (otherwise it would not work with the Android app, lighting on the virtual lamp when the Sensortile.Box vibrates). However, when I click on "modify" in order

I recently purchased a mini drone set (Steval Drone 02 & Steval FCU001/V2) and encountered several issues after mounting and starting up the FCU.I would like to share these problems in the hope of finding a solution. Firstly, during indoor flight, after calibration and arming the drone, it only flies up to about 20 cm and cannot be controlled.I have ensured that the propellers are mounted correctly.I noticed on the forum that I am not the first to experience this issue. Secondly, regarding the Android app, there should be a take-off button on the screen as mentioned in the Help section, but it does not exist.Could you please guide me on where to find the log data? Lastly, concerning the gyroscope and accelerometer.I have installed the TM32CubIDE and loaded the FCU001V2 project.After making some changes as per the manual, the elf file was created without errors.I loaded it onto the FCU board, but the result remains unchanged. Upon debugging and evaluating the gyr

Greetings,we are working on to evaluate the data given in lsm6dsv datasheet ,we want to verify the sensitivity and rest of the parameters,could you please provide us the test setup/suitable test rig details with which we can test the sensor...Thank you

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.I attached a pic

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 0x62but according to the DCR table (details table in MIPI : https://www.mipi.org/MIPI_I3C_device_characteristics_register), all version1.0 device DCR is 0x00.I don't known what's the current I3C version included in LPS22HH sensor. Can anyone help me clarify it?Sorry to @Foued_KH again.

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 threshold includes this constant bias (which could be updated in

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 same document on page 57/107 in section 6.5 Sensor fusion functions I think the "the specific configuration b

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.../Drivers/BSP/STM32WBAxx_Nucleo/stm32wbaxx_nucleo.c: In function 'BSP_PB_Init': ../Drivers/BSP/STM32WBAxx_Nucleo/stm32wbaxx_nucleo.c:316:56: error: 'BSP_B1_IT_PRIORITY' undeclared (first use in this function) 316 | uint32_t BSP_BUTTON_IT_PRIO[BUTTONn] = {BSP_B1_IT_PRIORITY, | ^~~~~~~~~~~~~~~~~~ ../Drivers/BSP/STM32WBAxx_Nucleo/stm32wbaxx_

 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 sensors always report zero output (all axes = 0).Issue in Fusion HAL:The STM software fusion implementation (SWAccelMagnGyroFusion9X + STMSensorsFusion) contains only placeholder stubs for the main functions     int STMSensorsFusion::getQuaternion(...)int STMSensorsFusion::getEulerAngles(...)int STMSensorsFusion::getGravity

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_thresholds_set(&dev_ctx, &wu); /* Set Output Data Rate.*/ lsm6dsv16x

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.WHOAMI and STATUSOUT regs

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?