MEMS and sensors

Can you increase the delay between Start and end frame packets.I want to make sure there's enough time for it to be detected with the STM32N6. Registers i've tried to use.  * VSYNC_START_DELAY - is for gpio output* FSYNC_IN_DELAY - not sure what it does  VD56G3 cam End frame packet.  

i have a new phone and the app that is used to get the data is in an oldest version and no newer were done and so i cant acces the data anymore the app is the ST BLE sensore clasic

Hi, i am a student using the VL53L0X time of flight sensor for a final project. I am having trouble getting the sensor data to settle the measured distance is very jumpy and out by 6 cm when measured with s ruler. how would i calibrate the sensor to stop jumping around and spit out the correct distance?. I am plotting distance vs time in MFC visual studios. the resolution of the sensor is + or - 1mm and i am out by 6cm. 

I have an X-NUCLEO-IKS4A1 mounted on top of a NUCLEO-L476RG and I am trying to connect that to Mems Studio. I get one of the two errors in the attached screenshots. Either "Board not identified" or "Some device is already connected".

I've been using this part from NXP (originally Freescale, I think)  for a while now.I've just noticed that it now has an ST Product Page:https://www.st.com/en/mems-and-sensors/fxls8967af.htmland the datasheet says:The ST Accelerometers portfolio page also lists a few other NXP part numbers: Is this a 2nd-source arrangement, or have these products fully transferred from NXP to ST ?  

Hi, I'm using the image sensor evaluation kit with STEVAL-66GYMAI, STEVAL-EVK-U0I and the PC software of STSW-IMG501 to capture video stream. I would like to change the setting of MIPI lane from default dual-lane to single-lane operation. But, I failed to change it, so please tell me how I can complete to change the setting. I tried to change the MIPI lane setting by changing the register value of OIF_CTRL at 0x030c. I changed the register value via the PC software from 0x0082 to 0x0081 in accordance with the VD66GY manual. The ROI size, the frame rate and the MIPI data rate were set at 288x288, 12 FPS and 1500 Mbps, which seemed to be enough for single-lane operation. The frame rate was adjusted by changing LINE_LENGTH register. However, I couldn't get the video stream. The excution rate displayed on the top left of the PC software window was 0.5 in streaming, and any picutures were not shown on the PC software.  I could see the video stream with the default dual-l

Any way how can I get in touch with ST on availability on this product? We would like to implement this into our devices, a devkit or hardware preview would help, we had previously integrated with the VL53L8 and VL53L5 which the result are good, and with the release of VL53L9, it will produce even better result for 3D mapping. ThanksVince 

I'm trying to figure out how to make a driver for your camera. The problem seems to be the licensing. The driver is all GPL which would be fine because with the datasheet i could figure out all the calls i need to make my driver work on a non linux device. The problem is the patches. The only place i can find about the patches are on the github driver page. Are they located another place thats not under GPL.* https://github.com/STMicroelectronics/vd56g3-linux-driver

Hello.I'm working on project with LSM6DSO and I use FSM.For easier programming I use the FSM Feature in MEMS studio, but it looks like it's buggy:1 - SRP doesn't change the graphical diagram of FSM. It always point to start of the program on RNC.Example: 2 - Adding STIMER3/4 lead to error when I try to export the register config (save device configuration as):There are also missing settings from the Fixed Data section (CONFIG_A, CONFIG_B, SETTINGS) which could be important.Thanks

Hello,I am working with the Machine Learning Core (MLC) of the LSM6DSOX and I would like to better understand how to extend or reuse existing ST models.In particular, I am using preconfigured models available from ST (e.g. Activity Recognition), which are provided as .ucf files.My goal is to:reuse an existing ST model as a baselineadd my own labeled data (custom activities)generate a new combined model without starting completely from scratchFor this reason, I would like to ask:Is it possible to access or obtain the original datasets used by ST to train the provided MLC models?Is there a way to extract or inspect the underlying decision tree from a .ucf configuration?Is there an official workflow to extend an existing model (e.g. retrain by adding new data) rather than creating a new model from zero?I understand that .ucf files represent the final register configuration, but I am interested in working at a higher level (model/data level) if possible.Any guidance or recommended approach

Hi everyone,I'm working on a project involving the STEVAL-MKBox Pro and would love some guidance from the community, especially since I'm still relatively new to this ecosystem.Here's what I'm trying to achieve:• Configure sensors on the STEVAL-MKBox Pro via Bluetooth using PnPL commands• Control data logging (start/stop) remotely over BLE• Save the collected data locally on the SD card• Once logging is complete, transfer the data to a Raspberry Pi 4 via BLEThe reason I chose to log first and transfer later rather than streaming directly over BLE  is the bandwidth limitation of BLE. My application requires high-frequency data acquisition, so buffering to SD card first and transferring afterward seems like the more reliable approach.My main question is: where should I start?Should I build on top of an existing firmware like FP-SNS-DATALOG2, or would it make more sense to start from scratch given my specific requirements?I have a basic understanding of the tools involved, but I'd re

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 issue, I changed step 7 to the following: For i-th reading 7.1 Read the FIFO patte

Hello,after updating MEMS Studio to version 2.3.1 I am experiencing an issue when working with FSM configurations.Previously everything was working correctly, but now I cannot reload FSM configurations saved as JSON files.Steps to reproduce the issue:Create a new FSM in MEMS Studio.Save the configuration as a JSON file.Try to reopen the same JSON file.The file loads without any error message, but the FSM editor remains empty and the FSM configuration is not shown.However, individual FSM examples included in MEMS Studio open correctly without any issues.This happens both with:JSON files generated previously with an older version of MEMS StudioJSON files generated directly from example FSM projects in the current versionSo the issue does not seem to be related to the JSON content itself.My setup:MEMS Studio version: 2.3.1Sensor: LSM6DSOXQuestions:Has the FSM JSON handling changed in MEMS Studio 2.3.1?Is there a specific way to reopen a saved FSM configuration JSON?Is this a known issue o

Dear Sir or Madam,I require a RoHS declaration of conformity for the following component:STEVAL-MKI208V1KCould you please share it?Thank you very much and kind regards,Thomas

In the past, I have used an LSM330 to wakeup on a gyro z-axis threshold and activate the INT1 pin as shown below:Gyro_WrByte(GYRO_CTRL_REG1, 0x3f); // 95Hz DataRate : 25Hz Cutoff : Normal Mode : Enable All AxesGyro_WrByte(GYRO_CTRL_REG2, 0x07); // HPF Normal Mode : 0.045Hz HPF Cutoff Freq : HPF Normal ModeGyro_WrByte(GYRO_CTRL_REG3, 0x80); // INT on INT1_Gyro PinGyro_WrByte(GYRO_CTRL_REG4, 0x00); // Continuous Update : Little Endian Data : 250 dps FS : 4-Wire SPI IntfcGyro_WrByte(GYRO_CTRL_REG5, 0x04); // Normal Mode Reboot Mem Content : FIFO Disable : HPF Disabled : INT1 Select = 01b : OUT Select = 0 : Use HPF for INT1 to account for any incr gyro bias drift due to incr temperatureGyro_WrByte(GYRO_INT1_CFG, 0x20);      // OR Combination : Z-High EventGyro_WrByte(GYRO_INT1_TSH_ZL, 0x3b);   // Gyro_WrByte(GYRO_INT1_TSH_ZH, 0x02);   // Z-Threshold = 571(0x023b) * 8.75mdps = 5Deg/sGyro_WrByte(GYRO_INT1_DURATION, 0x8a); // WAIT Enable : INT Duration

After reviewing the website, we noticed that the LSM9DS1 is currently listed as obsolete. We would therefore appreciate your guidance on the following points:Is the LSM9DS1 still recommended for new designs, or should it be avoided given its obsolescence status?We understand that the LSM6DSO (https://www.st.com/en/mems-and-sensors/lsm6dso.html) is currently recommended. However, this is a 6-axis IMU. Our application requires a full 9-axis solution including a magnetometer.What is your recommended 9-axis solution today?Do you recommend pairing the LSM6DSO with a specific ST magnetometer device?If we implement a 6-axis IMU together with a separate ST magnetometer, do you provide a 9-DoF (Degrees of Freedom) fusion algorithm that supports such a configuration?Can your fusion algorithms (e.g., MotionFX or equivalent) run on any ARM-based MCU, or are they restricted to STM32 devices?Are there licensing requirements associated with using your fusion libraries?Are there any usage limitations

Hello, I have encountered some issues while developing with the  ASM330LHH. During the initialization sequence of the ASM330LHH interface, I first read the WHO_AM_I  register. After confirming that the value is correct, I proceed to access other registers. In my tests, the WHO_AM_I value read back was correct. After checking the datasheet, it mentions that DEVICE_CONF set 1 to enable configuration. Now, after reading WHO_AM_I and before accessing other registers, I set DEVICE_CONF to 1. When I test again, the value read back from WHO_AM_I becomes incorrect. Could you explain why this happens? I am using SPI for communication in both cases, and the SPI configuration has not be changed at all — I only added the DEVICE_CONF operation.

Hi, just wondering if these constants (specifically NONE and OR both being 0) in the ULD for VL53L8CX are correct#define VL53L8CX_OPERATION_NONE ((uint8_t)0U) #define VL53L8CX_OPERATION_OR ((uint8_t)0U) #define VL53L8CX_OPERATION_AND ((uint8_t)2U) it look like it should be a sequence (0, 1, 2) so the repeated (0, 0, 2) appears out of place. It's hard to tell from the examples if this is intentional though.

I`m doing project using connection of Pololu VL53L7CX multizone sensor to STM32 NUCLEO-F103RB. It`s my first expirience with that. I would like to ask more experienced developers for help and, if possible, an example of the code. Thank you!

I am evaluating the MotionFX library for a 9-axis orientation project. To confirm our hardware selection and production path, I have three quick questions:MCU Lock: Is the MotionFX static library (.a) restricted to STM32 microcontrollers only, or can it be linked and executed on a generic ARM Cortex-M platform?Sensor Lock: Does the algorithm require ST-branded sensors (Accel/Gyro/Mag) to function, or can it accept raw data from any 3rd party sensor?Commercial Licensing: Is there a "per-unit" royalty fee for shipping MotionFX in a commercial product, or is it royalty-free for use with STM32 silicon?We need to know if we are "locked" to the STM32 ecosystem before we begin development.

Dear STMicroelectronics Support Team,I am currently working with the A3G4250D gyroscope and evaluating its temperature sensor output over I²C.According to the datasheet, the temperature sensor output change versus temperature is specified as −1 °C per digit. I would like to clarify one point regarding the absolute digital value.At an ambient temperature of 25°C, is there a specified or typical digital output value for the OUT_TEMP register? Or is the temperature output only defined relative to an internal reference without a guaranteed absolute value at 25°C?In other words, should we expect a specific digital code at 25°C, or is the temperature register intended purely for relative temperature measurement and compensation?Your clarification would help ensure correct implementation and validation during thermal chamber testing.

I'm using a LIS3MDL magnetometer on my board, and I figured out how to calibrate it to account for distortions  caused by the board, and the procedure works. However, it seems that every time the same magnetometer is turned off and re-powered, the measurements received are different. I saw somewhere that the LIS3MDL will self calibrate at startup and I think this might be what causes the differences. Is there any way to disable this process, and if that isn't the issue, do you know what it might be?

Hi everyone,I am developing a custom board using an STM32U5 and the LSM6DSV16BX. I am using MEMS Studio to train and configure the Machine Learning Core (MLC), but I noticed that the generated .h configuration file seems to set INT1_MLC1 bit at MLC_INT1 register by default.Even though I haven't explicitly set up physical pin routing in my project, the exported C array includes bank-switching logic that forces this configuration. I see the following sequence in my generated header:  { .type = MEMS_CONF_OP_TYPE_WRITE, .address = 0x01, .data = 0x80 }, // Switch to Embedded Bank // ... [other configs] ... { .type = MEMS_CONF_OP_TYPE_WRITE, .address = 0x0D, .data = 0x01 }, // MLC_INT1: Route MLC1 to INT1 // ... [other configs] ... { .type = MEMS_CONF_OP_TYPE_WRITE, .address = 0x01, .data = 0x00 }, // Return to Main Bank Because of this, INT1 pin is firing on MLC state changes. Since this is a custom design, I need strict control over my interrupt routing.My questions are:Can s

Hello,I have a question about the distance values returned by the VL53L8CX across the 16 cells in 4*4 mode.I performed repeated measurement with my sensor facing the ground, both with and without a glass cover.I noticed significant discrepancies between the distance values of the different cells, even though the target is a flat ground plane.By repeating the measurements and plotting the 16 cell distances as bar graphs, I observed a consistent pattern.Graphs 1 and 2 were taken consecutively at 30 Hz.Graph 3 was taken with the sensor farther from the ground, while still facing it.     From this pattern, it seems clear that the sensor was not perfectly parallel to the ground plane during the measurements. However, I am surprised by the magnitude of the difference between the highest and lowest cells. I have read in several posts that the VL53L8CX may return the perpendicular distance to the target plane rather than the radial distance along each cell’s line of sight. I would l

Dear all,I'm trying to get a VD55G0 sensor (promodule connected via P-board) working on a Raspberry Pi 5. I followed the Linux Start Guide for the driver. The only difference with respect to the guide were the name of the device tree file (guide says pcb4189.dts which the repository does not contain, so I used pcb4189_vd55g0.dts), and the names of the libcamera packages (the filenames seem to have changed, I have installed both .deb packages from the STSW-IMG505_RPI download). However, the camera sensor is not detected at all:$ rpicam-hello –-list-cameras [0:12:15.584143721] [1262] INFO Camera camera_manager.cpp:340 libcamera v0.0.0+5981-73aeb895-dirty (2025-12-09T14:49:21UTC) Made DRM preview window Preview window unavailable ERROR: *** no cameras available *** $ ls /sys/bus/i2c/drivers dummy stmpe-i2c $ uname -r 6.12.62+rpt-rpi-2712There is some output in the system log regarding the sensor, but I'm not sure what to make of that:$ sudo dmesg | grep vd55g0 [ 0.938491] /axi/pcie