MEMS and sensors

I have bought a new eval board from semikart via aquatronics. The device mounted on dil 24 of mk1251 kit is lsm6dsv320. The whoamI address of the device is 0x73 but it was not coming when we integrate with nucleo board. So, I waited for eval kit IKS4A1 to double check which I had ordered on coming of eval mk1251. I got MEMS Studio running on a windows 11 machine. But when I opted for dil sensor lsm6dsv320 , it threw inconsistent whoAMI address error. I am trying to contact semikart and aquatronics from last 10 days but none of them are responding. kindly tell a way to correct it or replace the eval kit mk1251. 

Hi, Post-development testing of the acceleration sensor reveals that the collected XYZ axis values are inconsistent with the actual physical acceleration values, and one axis continuously outputs a value of 0.What is the specific corresponding relationship between the sensor’s feedback value and the actual physical value?I also hope you can provide relevant technical parameters (such as sensitivity, zero offset) and calculation formulas for reference, so as to help us troubleshoot the problem quickly.thank you!!

We have used LSM6DSOXTR and IIS2MDCTR for our boards and we require any kind of certification test reports or certifications if applicaple. Where can I find them.

Hello, the values of my accelerometer axes are affected by temperature changes and require calibration at each temperature. What method should be used for compensation? How can Bias Drift and Scale Factor Drift be determined each time the temperature changes?

Hi What is the function of the RES pins on the ASM330LHHX?The datasheet indicates: “Connect to VDDIO or GND.”Is there a preferred connection?Can I add a 4.7 kΩ pull-up or pull-down resistor?BR

Hi,I am using the STEVAL-EVK-U0I kit with the VD55G0 sensor and the provided Python SDK. Firstly, I wanted to say I really love the capabilities of this sensor and it looks extremely useful for my work. My goal is to capture high frame rates (200-500 FPS) using subsampling. I have configured the sensor for 4x4 Subsampling and a short frame length. Based on the VD55G0_REG_STATUS_FRAME_COUNTER and VD55G0_REG_STATUS_FRAME_RATE, the sensor is successfully generating ~530 FPS.My problem is the following: While the sensors seem to be running at 530 FPS, the Python get_raw_image() function appears to be retrieving frames at 80-110 FPS. I am also getting a heap corruption error (perhaps the SDK cannot keep up with this high framerate? I am not sure).My questions :- Is this Python SDK capable of handling that high framerate, or am I doing something wrong?- How can I capture these high framerates? - Is there any other API (C/C++?) which could be used to achieve this high framerate ?&nb

Hi ST Community,I am encountering a specific issue with the LSM6DSO configured in FIFO Mode with the Sensor Hub (Master I2C) active.Hardware Setup:IMU: LSM6DSO (SPI to STM32).Slave Sensor: LIS2MDL Magnetometer connected to LSM6DSO via I2C (Sensor Hub mode).I2C Bus: Standard 100 kHz. External pull-up resistors are populated on the PCB (in addition to the internal ones enabled via configuration).Configuration:ACC ODR: 6667 Hz (High Performance).GYRO ODR: 6667 Hz (High Performance).MASTER_CONFIG: 0x4C (Write Once + Pull-Up Enabled + Master On).FIFO: Streaming Mode (storing Acc + Gyro + Slave0 Mag).The Issue: When I enable both Acc and Gyro at 6667 Hz, the FIFO gets populated almost exclusively with Accelerometer and Magnetometer data. The Gyroscope data is missing or appears extremely rarely (effective rate ~6 Hz instead of 6667 Hz). The Accelerometer works perfectly (full 6.6k sample count).However, if I lower the ODR to 3333 Hz, both Acc and Gyro work perfectly and are synchronized.Hypo

Hello, I have multiple VL53L0X sensors that I am communicating with over an STM32 board. Two of the sensors started throwing errors (only reading 8191), and so I moved them to an Arduino for the flexibility of using the downloadable API. They worked perfectly fine on the Arduino, so I am wondering what the issue with the STM code might be. I am using the following repo: https://github.com/MarcelMG?tab=repositoriesalong with i2c code that I wrote because I have a different stm model, but don't see that being the problem. Any help would be appreciated!

    I have performed crosstalk calibration of VL53L7CX ToF sensor using a 0.2 mm thick polycarbonate cover glass. I had used a sheet of white paper (assuming 80% reflections) placed at 600m as reference surface & 4 samples were used for calibration.    The calibrated sensor's accuracy was tested using a similar setup but with reference surface at 400 mm. The distance values observed in the 64 zones ranged from 396 to 426 mm. The standard deviation of the distance values were in the range of 2.2 to 4.5 mm. The heatmap of the zones also looked uniform.    But when I mounted the sensor in an enclosed space (around 1m X 1m X 1.5m) upside down pointed towards my objects of interest, I'm observing some random ghost detection in some of the zones. There are no objects in these zones at distances given by the ghost detections. But there could be objects/surfaces in nearby zones. Also, these ghost detections were not present when I did the same experiment

Case Description:Title: LSM6DSL FIFO data misalignment (XYZ rotated) and FIFO_PATTERN always 0 — how to align reads?Body:I’m using an LSM6DSL over I²C with an STM32. Goal: batch accelerometer-only samples into FIFO and drain clean (x,y,z) triplets at a fixed watermark. I keep running into two issues:Data misalignment — the XYZ triplets appear “rotated”. I’ll get a few normal lines, then a line where one column looks like a big random number (e.g., ~168xx), then it stabilizes again. Example:x,y,z 5, 250, 16870, 17, 258, 16825, -66, 221, 16828, -53, 284, 16834, Sampling End Sampling Start -22, 4, 242, 16846, 13, 281 16830, 51, 230 16882, 39, 242 16850, 11, 258 16803, -14, 220 16843, -24, 232 16855, 0, 241FIFO_PATTERN is always 0 — I expected to use FIFO_STATUS3/4 (FIFO_PATTERN[9:0]) to know which axis comes next and align before parsing, but I always read 0, even when the FIFO is clearly non-empty and STOP_ON_FTH has fired.Hardw

hi,     we use one LSM6DSL sensor to read 3 axis acc FIFO data each second, but after some times, the FIFO out data become misaligned. the sensor setting is below:XL_ODR_26HZGyro disabled.FIFO ODR = 26HzFIFO threshold (water mark) = 128No decimationBDU Block Update enabledFIFO Is in continuous modewe have a timer to trigger to read FIFO data by Zephyr I2C(frequency: 100000bits/s) each second, before data reading, we check the numbers of FIFO by checking FIFO_STATUS1 and FIFO_STATUS2 register, then we read a multiple of 3 axis sets each time, for example if the FIFO data number has 78, we will read all FIFO data one time, if the number is 76 or 77, we only read 75 data one time. it can make sure reading data is complete 3-axis data. firstly, the reading data is the right like as (X_ACC, Y_ACC, Z_ACC). but after some time (the time is not fixed) the data will become (Y_ACC, Z_ACC, X_ACC). we don't know how to fix this issue. please help us.

Now I am working on my own project which involve with detecting the pattern of hand gestures using LSM6DSOX. I planned to use decision tree to detect each gesture and use FSM to detect the sequence of gestures and send the interrupt signal.Now the project has 2 decision trees which detect different type of gesture. Both are working fine. In FSM, It program to detect 2 results from the decision tree. I use SETP command to change the DECTREE variable to check other decision tree address and value. But when upload the config, it doesn't work.I not sure that I am misunderstanding something about MEM_ADDR and MEM_VAL in SETP command, or my FSM has other issueThe picture attached is the FSM I use now for clarification. I want to check decision_tree_1 if the result is 4 first, then check decision_tree_0 if the result is 4.p.s. Actually, I have other question, how can I program the FSM to detect if the sensor is tilt and stay still for a period of time (the tilt data is from dec

Hello group,I'm a humble hardware guy integrating the LSM6DSV16X into a robotic application.We are going to use it in control loops, between 3kHz and 5kHz sampling.Between the main mode and the OIS mode, there are tons of ODR to choose from.However, is there a way to make the ADC sample at EXACTLY 5kHz?? Like a triggered or synced ODR?Or do I have to set the ODR at 7.68kHz and read the latest value from the FIFO and deal with the small discontinuities?I see the Triggered-ODR section 6.6 in the datasheet. Does it means enabling this will sync the ADC with an external INT2 pulses? Does the new values appears in the FIFO after a defined short delay?Thanks!

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.

Hello,We have lately been seeing in some cases that one or two pixels seem to be stuck at distance_mm==0. Sometimes the pixel goes back to returning normal values after some time or after a power cycle, but sometimes it seems to report a zero value consistantly. I will implement some more debugging to get the status of the measurements, but I was wondering if you had any input into why a zero value could be measured for one or two pixels?

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)  

ULPM for the MIPI CSI interface of VD55G1 is not clearly described.Errata (es0643) section "QVGA at 480 fps" say that we should put MIPI in ULPM. Why does this affect timing?WRITE_REG8 STREAM_STATICS_OIF_ULPM 'h01 # MIPI in ULPMIs this a MIPI setting (continuous/discontinuous)? Additionally, a register write is referred to that is not documented anywhere in the datasheet or integration guide.WRITE_REG8 CHANNEL_STATS_ROI_REDUCE_FACTOR 'h10 # 16 lines removed to the stats ROIWhat is this register? The address is not even known.

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

Hello community, I am working with the VL53L0X Time-of-Flight distance sensor and the official ST API driver (VL53L0X API package).My hardware platform is: STM32H747I-DISCO board (CM7 core) I2C3 used to interface the VL53L0X FreeRTOS running on CM7 Display controlled using TouchGFX I copied the VL53L0X API (platform.c, platform.h, vl53l0x_api., vl53l0x_platform. etc.) into my STM32 project. Issue:  When I call any API functions Inside a FreeRTOS task, the code does not proceed beyond the first API call.The task appears to get stuck, and my LCD (TouchGFX) stops updating as well. When I comment out these VL53L0X API functions, FreeRTOS and the LCD work normally.  FYI I have attached Latest API 

Hi,I was wondering if it's planned for the current STEVAL-EVK-U0I board to work with the 5 Mp VD5943 and VD1943 Image Sensors when they're launched in spring 2026 or if a new USB interface board is planned for evaluation of VD5943 and VD1943?The page for the STEVAL-EVK-U0Ihttps://www.st.com/en/evaluation-tools/steval-evk-u0i.htmlsays "CAM-56G3, CAM-66GY, CAM-55G0, CAM-55G1" so I wasn't sure if it was planned to for it to support evaluation of the VD5943 and VD1943 as well. Will 

Hi there, I'm trying to figure out how to configure VD55G1 monochrome sensor to differential mode (e.g. disruptive mode, event mode) as branded in user manual. However, after going through https://github.com/STMicroelectronics/stm32-mw-camera, I have no clue. Could you help me with this? Thank you.