MEMS and sensors

Hi all,I am trying to get started with a LSM6DSV320X accelerometer, using a STEVAL-MKI251A and a Raspberry Pi 4. I can get raw Accelerometer and Gyroscope data from their dedicated output registers (0x22h to 0x2D), but when I try to use the FIFO, I can't get it to work - I get data with tags that are not enabled, with tags that don't exist, and when there's a tag with Accelerometer data, it's incorrect. I've also tried writing the special functions registers to make sure the special functions are disabled and there's nothing of that batched into the FIFO, just to make sure, but that didn't make any change. Currently I've reduced it to as simple a configuration as possible and removed all other code from the test program, and I'm using the following configuration:Read WHO_AM_I register - get 0x73Configure FIFO:Write 0x01 to CTRL3 (software reset)Write 0x44 to CTRL3 (Enable BDU, auto-increment)Write 0x04 to CTRL1 (Acc high performance mode, 30HZ)Write 0x10 to FIFO_CTRL1 (watermark at 16

Hello,I'm using MEMS Studio to log data from a multi-sensor glasses platform for biomarker extraction research. My sensor configuration includes:ST1VAFE6AX (Accelerometer @ 240 Hz, Gyroscope @ 240 Hz, vAFE enabled)LIS2MDL (Magnetometer)LPS22DF (Pressure)STTS22H (Temperature)The CSV export includes a new_data column containing hex values (e.g., 0x08, 0x10, 0x18, 0x20, 0x400). I understand this is a bitmask indicating which sensor(s) have new data in each row, but I cannot find official documentation for the bit assignments.Through empirical analysis (checking which sensor columns actually change when each bit is set), I determined:Bit Mask Sensor CorrelationBit 30x08Accelerometer96.6%Bit 40x10Gyroscope96.6%Bit 50x20Magnetometer99.9%Bit 60x40Pressure—Bit 100x400vAFE—Questions:Is there official documentation for the new_data bitmask format in MEMS Studio CSV exports?Are these bit assignments consistent across different sensor configurations, or are they dynamically assigned based on which

Hello, I have a question about the temperature calibration for the VL53L0X Time-of-Flight sensor.The UM2039 manual states the following:> [Temperature calibration] has only to be done before offset and cross-talk calibrations, after Reference SPADs  management and before the first ranging is performed.During assembly of our product, those calibration steps (SPADs, Temperature, Offset, XTalk) are performed in order.To account for possible temperature changes when the device is in use, we call both  `VL53L0X_PerformRefSPADManagement` and `VL53L0X_PerformRefCalibration` on device boot to ensure the sensor is ready for use for the current temperature.My question is if this would affect the offset and xtalk calibrations, since the docs state that temperature calibration must be perfomed before those. Or is that sequence merely to ensure the offset and xtalk calibrations are done with the correct temperature calibration.Thank you for your time.

Hi,We've been working on a project using v1.3.1 of MEMS Studio, but I've had to use a new laptop and it doesn't have this installed. Unfortunately, when I go to the downloads page I can only see v1.4.1 of MEMS Studio and it's forcing me to upgrade the firmware, which I don't want to do as all our testing & benchmarking has been based on a specific configuration.Does anyone have, or can you point me to, the older version of the application? ST don't seem to have an archive of older builds anywhere and their support team has been unable to help.Thanks,Simon

Hi,I can't find a way to select in MEMS Studio which MLC filters are passed FIFO and how to enalbe MLC result in FIFO.Configuration created by MEMS studio enabled MLC_FILTER_FEATURE_FIFO_EN in EMB_FUNC_FIFO_EN so I see selected MLC features in FIFO but nothing more - no filters, no results.I manually enabled MLC_FIFO_EN but MLC results didn't appear in FIFO.I tried to enable filters manually in mlc.json by adding "fifo": "true" to filters in json file, but it didn't help.  I've attached MLC files. Best regardsTomasz 

Hello, I am trying to record audio with external digital PDM microphones using the MEMSMIC1 example but it is not so straightforward without the nucleo expansion board. Because the CCA02M1 has a direct connection to the pc it is able to be detected as a microphone in the device manager, it is easily used through audacity. How can I implement this project and use audacity with my microphone setup if they are directly connected only to the development board (I am using nucleo-wb55rg)?

I have previously used a large quantity of LSM6DSV16XTR products from batch 426, and their data was completely normal. My device utilizes 16 gyroscopes simultaneously. Recently, I started using products from batch 509, and they have exhibited a peculiar phenomenon. Specifically, it includes two parts: (1) When the temperature slowly increases from -40°C to 85°C, observing the data of a gyroscope at rest, some gyroscopes show data jumps at certain temperature points (the jump temperature point varies for each gyroscope). For example, the data may jump from -0.98°/s to -0.08°/s. (2) For the same gyroscope, at the same temperature, the bias data varies significantly at different times. This phenomenon does not occur in every gyroscope, but it greatly troubles me because I cannot record and compensate for the bias data in the temperature chamber, as these biases have become highly irregular. This phenomenon did not occur in batch 426. Does anyone know why this is happening?

This is a continuation from this post, where I erroneously marked the post as solved: https://community.st.com/t5/imaging-sensors/vl53l7cx-distance-data-stratification/td-p/866073Unfortunately I'm still experiencing the issue where range data continue to be unstable, and appear to stratify or cluster into discrete magnitudes.Test setup:2x VL53L7CX sensors on one I2C busCover glass installed on both sensorsRanging enabled on both sensorsThe video is showing data from a single sensorI have a test setup with a sensor looking at the back of a notebook at a fixed distance as shown in this picture. The range data returned from the sensor varies between actual the distance, and shorter distances. You can see this in the video below. In addition, in the video I'm also printing the `target_status` for all 64 zones on the terminal output to the right. Would anyone have insight, or perhaps offer troubleshooting steps?  Thank you EDIT: Added test setup details

HeyI've got great success with the VL53L4CX at sorter ranges, but at longer ranges i seem to get two objects. One closeby between 10 and 30mm away, and one at the distance that it should be.I've done calibration and i cant' get this to go away. I'm assuming it's crosstalk but i've done the crosstalk calibration and so on. What could this be?Example of some of my log output, where you can see the two outputs and some other values from the same measurements.[995156] PerformMeasurement(offset=0, maxdepth=2000, ignoreBelow=10)[995162] Read 388 bytes...[995163] VL53L4CX_SetCalibrationData status: VL53L4CX_ERROR_NONE[995166] VL53L4CX_SetXTalkCompensationEnable status: VL53L4CX_ERROR_NONE[995166] VL53L4CX_SetMeasurementTimingBudgetMicroSeconds status: VL53L4CX_ERROR_NONE[995166] VL53L4CX_SetDistanceMode status: VL53L4CX_ERROR_NONE[995166] VL53L4CX_SetOffsetCorrectionMode status: VL53L4CX_ERROR_NONE[995166] VL53L4CX_SmudgeCorrectionEnable status: VL53L4CX_ERROR_NONE[995166] VL53L4CX_SetUserROI

Dear all,I'm looking for the driver for the VD55G0 camera sensor compatible with the STM32N657 MCU. According to the camera sensor's driver product page (STSW-IMG505) a driver should be available for the N6 (the N6 is mentioned several times as being supported) but I can only find drivers for Raspberry Pi and V4L2. Could you please let me know where I can obtain the driver?Thank you very much for your support!Michael

Hi,I've tried to use high-pass filter in MLC in MEMS Studio, but the results are incorrect for first windows in each data file. I found that result is different from the one from Unico, but probably because Unico just drops first 2 windows from each file (which is an error itself). Signal is a quite constant noise (sample data and project is attached). These are F2_MEAN_ACC_Z_FILTER_1 & F3_MEAN_ACC_V_FILTER_2 from MEMS Studio and Unico. Decision tree generated based on these filters makes no sense. Values of these features read from FIFO looks ok. Looks like a bug in the app. Best regardsTomasz  

HI,I'm using the VL53L4CX and in an enclosure and thus have a cover glass over the sensor.i've been doing some simple calibration, but have noticed that this requires a strict procedure and preferably a good setup to perform the calibration.I therefor want to make a box to perform the calibration in. This should remove any variables and make sure that calibration is handled the same every time.I know i should be able to copy the calibration data from one device to the other, but due to it being a lorawan device, and my current provisioning/flashing steps, it's easier for me to calibrate the sensor afterwards.I posted the same question here: https://community.st.com/t5/imaging-sensors/vl53l4cx-refspad-caliberation-no-target/m-p/869701/highlight/true#M6277 but that's a fairly old topic, so i'm starting a new one. My current idea for a wooden calibration box is:Wooden (probably MDF) box with an internal height from sensor to top of 60cm, probably 40cm wide.Matt black paint

I need to save power in a project; the system will turn on when shaken. I need to configure INT1 pin to leave the LDO open for 15-20 seconds. Conditions:1- Did the device move? (acceleration)2- Are the x, y, and z axes in the correct position?If conditions 1 and 2 are met, set INT1 high for 15 seconds.Is this possible? Are there any documents available on how to use int1 and int2?

Hello ST Community,Based on a photo found on the internet of the LIS3DH chip and a comparison with the package information in the datasheet, I found a discrepancy in the footprint.The datasheet appears to show the pin-1 mark on the opposite side compared to the photo. I also found differences between two different online libraries that you recommend on your website.I am pretty sure that the correct position is as shown in the photo or in the Ultra Librarian library, but could you please clarify the correct location of the pin-1 mark, both on the top of the IC and on the bottom of the IC?Many thanks.Internet Photo:Datasheet page 50 (LGA-16 package information)SymacSys library ( https://componentsearchengine.com/ )Ultra Librarian 3D model (TOP, Opacity 25%)What do you think @Federica Bossi ? ;)   

Hi Sir,1. Regarding Initialization (Absolute Orientation)In my application, I need to obtain an absolute orientation (Roll, Pitch, and Yaw) relative to the Earth's frame. Is my understanding correct that the Initial Quaternion must be computed using both Accelerometer and Magnetometer data (as per DT0058 Step 4) to establish the starting reference?Since the gyroscope only measures angular rates, is it true that a 6-axis (Acc+Gyro) initialization alone cannot provide an absolute Yaw/Heading reference?2. Regarding DT0060 Step 2 I would like to confirm the definitions and implementation of the mixing process:Q1 Definition: Is Q1 the "dynamic quaternion" that is updated via gyroscope integration in Step 1?Q2 Definition: Is Q2 the "reference quaternion" calculated from the accelerometer and magnetometer data, used to correct the drift of Q1?Weighting Parameter (alpha): For a handheld device, what is the recommended range for the alpha parameter in the formula Q = Q1*alpha + Q2*(1-alpha) to

Hello, I'm trying to use ODR-triggered to get data aligned with my clock. I'm sending a square wave 50% duty cycle period 2000ms over INT2 pin, yet when I poll the IMU every 50 ms the accel and gyro data changes, even though it should be aligned to the edges every 1000 ms.I've double checked the registers to confirm they are correct and have an analyzer attached to verify INT2 pin is being sent signals. // init.c lsm6dsv320x_block_data_update_set(&data->ctx, PROPERTY_ENABLE); lsm6dsv320x_xl_data_rate_set(&data->ctx, LSM6DSV320X_ODR_OFF); lsm6dsv320x_gy_data_rate_set(&data->ctx, LSM6DSV320X_ODR_OFF); lsm6dsv320x_xl_mode_set(&data->ctx, LSM6DSV320X_XL_ODR_TRIGGERED_MD); lsm6dsv320x_gy_mode_set(&data->ctx, LSM6DSV320X_GY_ODR_TRIGGERED_MD); lsm6dsv320x_xl_full_scale_set(&data->ctx, LSM6DSV320X_2g); lsm6dsv320x_gy_full_scale_set(&data->ctx, LSM6DSV320X_2000dps); lsm6dsv320x_xl_data_rate_set(&data->ctx, LSM6DSV320X_ODR_AT_240Hz); l

I am trying to use some machine vibration data to identify running condition. In my use case, i was able to create decision tree and configuration file in sensor with MEMS studio 2.2.0, but the sensor is not detecting any decision tree information.the decision tree information is stuck at 0x00.my decision tree label value:      1 ---> not running ( no accel vibration detection)     4 ---> running What could cause the LSM6DSV16X sensor to provide no data in the decision tree?feature.arff file few lines: using acc_v and gyr_v information.@relation 'MLC'@attribute F1_VARIANCE_ACC_V numeric@attribute F2_VARIANCE_GYR_V numeric  

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 mode:  lis2du12_pin_int_route_t int_route; lis2du12_status_t status; lis2du12

Hello Team,We are using SensorTile.box Pro with the STEVAL-MKI251A (LSM6DSV320X) adapter board and MEMS Studio version 2.2.0. Flashed the sensor tile box pro with the DataLogExtended.bin firmware which is available in the MEMS StudioWe have logged accelerometer Low-G and High-G data at 1.9 kHz. Additionally, we enabled and monitored interrupts from INT1 to INT10 during the test.We observed that only INT10 shows an output value of 1, while all other interrupts remain inactive.Could you please confirm from your side whether INT10 = 1 corresponds to the Free-Fall interrupt for this sensor configuration? Also, kindly let us know if this behavior is expected when using MEMS Studio 2.2.0 with SensorTile.box Pro and the STEVAL-MKI251A.Thank you for your support.Best regards,Ahilesh

Do you consider this as aDo you consider this a crack?

Problem description:We are seeing a hard I2C bus lockup involving an ISM330 IMU and an IIS2MDC magnetometer on the same bus. The failure mode is that SDA is driven low permanently, and the bus cannot be recovered by standard I2C recovery procedures (9–20 SCL pulses with SDA released). This occurs both immediately after MCU firmware is flashed and during nominal runtime, seemingly at random. Once the condition occurs, a full MCU reset does not recover the bus. On a bench setup we confirmed by probing that SDA is physically held low. Hardware configuration:MCU: STM32 acting as I2C masterDevices on bus:ISM330 (IMU)IIS2MDC (magnetometer)These are the only slaves on the bus.Standard I2C pull-ups are used, with no level shifting. I've done additional testing to try to find the problematic device by removing devices and reconfiguring connections (auxiliary I2C), see results below. Observed behavior by configuration:ISM330 only on I2C: no issuesISM330 and IIS2MDC

Hi Everyone,I'm currently migrating from LSM6DSM to LSM6DSO in my application and facing some issues with accelerometer accuracy in stable conditions.System Overview:MCU: STM32L4Sensor Interface: SPI (3-wire)Purpose: Reading raw accelerometer and gyroscope data, converting to physical units, and estimating roll/pitch/yaw using MotionFX.Configuration Details:   Parameter Value Acc/Gyro ODR1.6 kHzFIFO Output Rate400 HzMain Loop Rate100 HzAveraging4 samples/frame What’s Working:I can successfully communicate with LSM6DSO via 3-wire SPI.I’m able to read raw data from the accelerometer and gyroscope.Sensor fusion (MotionFX) works and outputs roll, pitch, and yaw.With LSM6DSM, I was getting clean and accurate data as expected.Problem:I'm trying to measure raw linear acceleration (after converting to g).The requirement is that the noise level (in a static, stable condition) should be less than ±0.005g in all directions.With LSM6DSO, the data seems noisier and less accurate, eve

Hi community,I am working with STM32H747I-DISCO Board(Dual cortex M7+M4)MP34DT05-A digital MEMS microphone is integrated on the board and issues are facing while bringup.Issues follows:As per the schematic there is one digital microphone connected to the MCU using SAI Interface with default connectionsI am trying to bringup it with the help of refernce document(Ref AN5027).When i am understnading this document a few questions have been raised. Those question as follows.1.There are two types of mode  mono modestereo mode       stereo modeIf we see the schematic:One digital microphone is connected to stm32 MCU and it looks like mono mode configuration But when I am following mono mode configuration process to bring up it then pins which are enabling while configuring is mismatching with pins which are connected to this digital microphone as per the schematic.Connection pins – (SAI4_CK1) PE2, (SAI4_D1) PC1 (as per the schematic)Enabling Pins :In stereo mode config

I'm using a STEVAL-MKI109D with the IR sensor STHS34PF80 and I need to fine tune it to detect objects with low IR emissivity, but everytime I want to load the log file into the IR Algorithm Tuning, the same error appears "Failed to parse log file". I've tried modifiying different things from the log, but everytime, I get the same error. Here is an example of a log file:# STEVAL-MKI231KA (STHS34PF80)time[us],t_object[LSB],t_object_comp[LSB],t_ambient[C],t_ambient_shock[LSB],t_ambient[LSB],t_ambient_shock_flag,motion[LSB],presence[LSB],presence_flag,int_1638,-614,-614,23.470,0,2347,0,0,0,0,0638,-671,-671,23.540,0,2354,0,0,0,0,0729188,-641,-641,23.490,5,2349,0,0,0,0,01736289,-659,-659,23.440,9,2344,0,15,15,0,02742002,-642,-642,23.450,7,2345,0,12,12,0,03748506,-626,-626,23.490,2,2349,0,19,19,0,04754121,-617,-617,23.510,0,2351,0,30,30,0,0Any idea on what could be happening?

Hello, I have bought an ISM330BX | Product - STMicroelectronics and a STEVAL-MKI109D | Product - STMicroelectronics. I can get it to stream data by using: *setdb245ka *zoff *gw1009 *gw1109 *startOR*debug For debug this streams something like:AX = -7303 AY = -4734 AZ =-13823GX = -429 GY = +271 GZ = +358QVAR =  +0 QVAR_FILTERED =  +0 For start, it is binary and i can convert it. According to page 21 of this manual, STEVAL-MKI109D Professional MEMS Tool motherboard for MEMS adapter boards - User manual , this is the returned value of *start: UIstring: s t A_XH A_XL A_YH A_YL A_ZH A_ZL G_XH G_XL G_YH G_YL G_ZH G_ZL QH QL Q_FH Q_FL A_Int1 A_Int2 FSMLC_INT FSM1 StpL StpH DT1 DT2 DT3 DT4 TL TH sw1|sw2 \r \n TDMstring: t d A_XH A_XL A_YH A_YL A_ZH A_ZL 'T' \r \n SFLPstring: s t A_XH A_XL A_YH A_YL A_ZH A_ZL G_XH G_XL G_YH G_YL G_ZH G_ZL Q0_L Q0_H Q1_L Q1_H Q2_L Q2_H gbia