MEMS (sensors)

Hello,I can't find reference to the expected chip markings for the ISM330DLC and IIS2MDC in their respective datasheets. My PCB assembler is requesting this information to validate the components.Are these the correct markings?ISM330DLC: SY 203IIS2MDC: M Thank you in advance for your time and kind regards,

Hi,We are evaluating the LSM6DSR's noise floor for a specific use case. Based from the datasheet the noise is 60ug/sqrt(hz). So calculating the RMS noise at 208Hz should result to 0.00062 m/s^2 right? However, we are getting measured RMS values around 0.002 to 0.004 m/s^2. Here are some configurations setFS: +-2GODR: 208HzData acquired using FIFO reading every 500 samplesNo onboard filtering enabled. I have attached a sample dataset for your analysis as well.

Hi,We are using LSM6DSV320X for our product and want to generate interrupt when high-g is detected. In which register do we need to set the threshold so that the interrupt is generated at or above that value.

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) 

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 on

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

Hello all,I am developing a vibration measurement device using LSM6DS3TR-C. Most of the time the data were in good shape (99%).  However, I noticed some spike in my vibration intensity reading randomly. After checking the raw data I saw some step change at the same time point, indicating the data reading of the three axis are confounding.My configuration only requires the accelometer readings to be cached in FIFO:1. enable block update 2. set fifo accelometer decimation register to 1 (no decimation) 3. set fifo accelometer data rate to 3333Hz 4. set accelometer data rate to 3333Hz, bandwidth 1.5khz, LPF_BW_SEL to 1 5. set FIFO mode to bypass, then set to FIFO mode (clear and restart FIFO) 6. polling FIFO_STATUS2(0x3B) register for FIFO_FULL_SMART. 7. I2C bulk read the FIFO for 682(sample count) * 3(axis) * 2(16bit-axes) = 4092 bytes from buffer 8. repeat from 5.To identify the

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 ? 

Hi everyone,I'm using 2 LIS2DU12 on one object.The first one is configured in continuous mode. I forward the samples directly to a computer. I use it to check the wake up triggering configuration of the second one.The second one is configured in continuous-to-FIFO mode. And I'm trying to get it to wake up when the acceleration on one axis is over 2g for at least 8.75ms. ODR is 800Hz, FS=16g, so I set :WK_THS=8WAKE_THS_W=0=> threshold = 2g x 2⁶ / 16g = 8WAKE_DUR=01 (7 ODR_time)WU_DUR_X4=1=> Wake-up duration = 7 / 800 = 8.75msThe first LIS2DU12 configured in continuous mode shows that during my tests I get 4g for over 20ms, yet the second LIS2DU12 does not wake up. But if I set the threshold to 4 (i.e. 1g according to my calculations) it does wake up, and I recover 2 very similar acquisitions.What did I misunderstand ?Here is a code snippet of the configuration of the LIS2DU12 in continuous-to-FIFO m

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