Imaging (sensors)

Dear ST,Now I'm testing my VL53L7CX sensor that is on the package P-NUCLEO-53L7A1 in Autonomous Mode with integration time = 2ms, ranging freq. = 4Hz and 4X4 Resolution, the attached screen-shot represents the output current related to my integration time and it's typically 2ms.My question is about the added peaks after the integration time peak, Why could this happen?and, How can I eliminate or reduce it?Knowing that the duration of these peaks illustrated in the other screen-shot attached.Thank you.    

Dear ST,Now as you mentioned in VL53L7CX_ULD the Firmware is uploaded through the I2C protocol to the VL53L7CX every initialization in (Hex form) from the Buffers.h file as also it includes the default configurations for the VL53L7CX While I'm testing it in the Autonomous Mode with parameters integration time = 2ms, ranging freq. = 4Hz and 4X4 Resolution, making also the host board (NUCLEO-F401RE) in sleep mode which means that, there is no communication data on the I2C Bus.I found the current peak as illustrated in the screenshot attached, the first peak represents the integration time which is typically 2ms as configuration.Now I need a detailed explanation about the wave regions illustrated after the first peak and how can I minimize or eliminate them.As also I need to know how to update this firmware and if it has a datasheet or source code.Thank you

Hello!We use the VL53L0X as a time-of-flight sensor on a custom PCB. We used Arduino to configure and read the VL53L0X during development of our embedded system. Now later in development, we find differences between Arduino readings and readings taken from our Linux-based Embedded System (LES). I am investigating what differences exist between our Arduino application used during development and the application running on the LES. While not every sensor is showing shifts in range measurement, the worst case shifts are 6-7mm difference and repeatable.I have collected all I2C communication with the VL53L0X from boot to when we enter the measurement loop for both Arduino and LES hosts. I see some differences and have investigated what I can, but I have a hard time understanding what exactly those differences mean without a register map and descriptions. I understand ST will not provide this information, so I am hoping you can instead provide any insight on my below questions. The

I am trying to capture video streams from two VD66GY cameras connected to the CSI0 and CSI1 ports of a Compute Module 5 IO Board. My OS is : Linux raspberrypi 6.12.75+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.75-1+rpt1~bookworm (2026-03-11) aarch64 GNU/LinuxBoth seem to be recognized:However, when I try to capture video from both cameras simultaneously, only the CSI0 port works. The CSI1 port returns the following error with this command ( rpicam-hello --camera 1):I also tried a GStreamer command, but it didn't make any difference.I don't have much experience with V4L2 or camera systems in general, so I'm not really sure how to fix this problem. Maybe I missed a step during setup, but that seems unlikely. Even after searching for similar issues, I haven't found anything conclusive.What I have already tested:When using two different cameras — CSI0 = VD66GY and CSI1 = IMX296 — I can capture both video streams successfully. The reverse configuration does not work if VD66GY is connect

Hello, I am currently working on a project where we want to use the VL53L7CX sensor for motion detection.  Looking through the documentation, I couldn't find any information on what the read and write addresses and values are for communicating with the VL53L7CX, there was just the X-CUBE-TOF1 Time of Flight expansion software for the STM32Cube IDE. I wanted to know if there was information available to communicate with the VL53L7CX via I2C, since I wanted to use the ESP32 for writing the firmware using the Espressif platform.

Would it be possible to use a Time-of-flight sensor to measure water level in a pipe?The pipe is vertical with a diameter of 50 or 75 mm and a height  of 800 mm. At bottom there is a 90 degree bend. Sensor should be at top looking down the pipe. I assume that best sensor would be VL53L4CD since it has smallest field of view. Would reflection from pipe walls disturb measurements?   

Hi，   vl53L0x goto sleep and wakeup to reduce power.  I used single_mode,program as follow:   I find add          sensor_init(dev,vl53_mode);            //activa  The measurement time was 600 mS. long more than not add  this function？  how  to reduce the time?      

Hi, When performing two measurements per second, how can the power consumption of the VL53L0x be reduced? Is a single measurement or continuous timed measurements preferable? I adopted continuous timed high-speed measurements, setting the measurement duration to 22 ms with a 900 ms interval between measurements, resulting in an average measured current of 19 mA (according to the specification). Based on this, I calculated the average power consumption.(22 mS × 19 mA + 5 μA × 878 mS) / 900 mS = 0.4693 mA. I don't understand why others can achieve 20 μA.

Hi, I am experiencing a technical issue with the ST 16GZMAI camera when connected to the EVK-U0I1 control board. While the system works fine with my 55G1MBI1 camera, the EVK GS 1.1.2 GUI fails to recognize this specific model and displays the following error: "Error: could not broadcast input array from shape (341,280) into shape (340,280)" I am also unable to change the detector format. Could you please refer me to a technical expert who can assist with the configuration of this model? Best regards, Sean

Hi, I was trying to create a small 8x8 / 4x4 point cloud using a VL53L5CX sensor, and I can get the depth data for each zone, but I was wondering if there was a way to get x,y,z from this information? Like if there was a way to know the vertical and horizontal angle for every zone on the VL53L5CX and then calculate the x,y,z location of the points using that and the depth data. Any help would be appreciated!

I am trying to understand one point in the official VL53L8CX datasheet.In the pin description table, pin C5 (MISO) is described for SPI as:“SPI: Main input secondary output. Push-pull output, driven to IOVDD level.”But in Figure 6 (“Typical application schematic for SPI”), the MISO line seems to have a 47 kΩ pull-down resistor to GND.I attached two screenshots:1. the table entry for C5 / MISO2. the SPI typical schematic with the suspected 47 kΩ pull-down highlightedMy question is: how should this be interpretedcorrectly?Does ST mean that MISO is a push-pull output, but an external weak pull-down is still recommended as a default line state? Or is this schematic being misread, and that 47 kΩ resistor actually belongs to another signal?I would appreciate clarification from anyone who has used VL53L8CX in SPI mode or has already resolved this ambiguity.

Dear ST Support Team,I am writing to express my interest in the VD55H1 iToF sensor for an upcoming project.Currently, we are preparing for development using the i.MX8MP platform running on a Linux Kernel. Upon reviewing the technical specifications, I noted that the VD55H1 utilizes a MIPI-CSI data interface.Could you please confirm if ST provides an official Linux driver for the VD55H1?As driver availability is a critical factor for our initial integration and development phase, we would appreciate any information regarding existing software support or a roadmap for Linux integration.Thank you for your time and assistance.Best regards,seobi

Hi - when I attempt to download the driver for this device the download never completes; I get a file "Unconfirmednnnn.crdownload" in my download folder. I'm using Edge browser on a Windows 11 Home 64 bit operating system. Using Norton, can't see anything there that would prevent the download. Have successfully downloaded from other sites many times with no issues.Anyone with any insights?Thanks.

Hi,I've P-NUCLEO-6283A1 and downloaded the graphical user interface STSW-IMG301. The quick start guide does not seem to be up to date as I did not find "VD6283_setup.exe" I was supposed to install, just a plain exe in the zip.At the first try GUI complained that it cannot communicate with the board. Next I updated the firmware with the GUI. Now when trying to start I get error complaining about invalid product version. What is going on here? Does the GUI ship with incorrect firmware binary?My board 

We will design a layout for the VD55G1 Promodule with Image read out over I3C. Alternative there is also a VD55G4 camera with an additional SPI image read out. Is it possible to get the pin assignment for the new VD55G4 promodule ?

Dear ST, For the ToF sensors supported VL53L8CH or VL53L7CH is it possible to make a hardware that depends on 4 x VL53L8CH or 4 x VL53L7CH integrated to increase the number of zones from 8 X 8 to 16 X 16 ?and if it is possible what would be the limitations in both HW and SW for this system?also provide me a reference for this implementation if exists.Thank you.

Hi everyone,I am a beginner working with the VL53L1X sensor on an STM32F103C8T6 using the STSW-IMG009 (Ultra Lite Driver). I am trying to implement a calibration routine, but I am encountering two specific compilation errors inside my VL53L1X_calibration.c file:The errors:1. 'VL53L1X_ERROR_TIMEOUT' undeclared (first use in this function); did you mean 'HAL_DMA_ERROR_TIMEOUT'?2. implicit declaration of function 'VL53L1_WaitMs' [-Wimplicit-function-declaration]I have checked the driver files but cannot find their declarations.I have not changed any of the driver files. Am I missing something? Any help is appreciated. Thank you!

I am using a VL53L0 ToF sensor.If an interrupt occurs, repeat the measurement using the "VL53L0X_GetRangingMeasurementData" function and the VL53L0X_ClearInterruptMask function.Normally, it operates, but the sensor outputs data that seems to be looking in the air due to unknown causes such as static electricity.From the IR camera, there is no light in ToF.Two functions, VL53L0X_GetRangingMeasurementData and VL53L0X_ClearInterruptMask, do not return errors.When I initialized the phenomenon after checking it, the sensor operated normally.I'm wondering if there's any data I can check because the data is similar to what I'm seeing in the air about the above phenomenon.

raw ID and is_alive() work Hello,I am using a Chinese VL53L8CX module from AliExpress, not the official ST evaluation board. I want to stress that in the first sentence because this may be important: this is a Chinese AliExpress breakout, not the original ST hardware. The same module works on my setup over I2C, but I am trying to bring it up over SPI on an ESP32-S3 and I am stuck at a very specific point.What already works:- The same sensor/module works over I2C on this board.- In SPI mode I can repeatedly read the hardware ID correctly: `dev=0xF0`, `rev=0x0C`.- `vl53l8cx_is_alive()` often returns `status=0, alive=1`.What fails:- `vl53l8cx_init()` never completes successfully.- The failure happens around the software reboot / boot polling stage.My hardware/software context:- ESP32-S3- custom firmware using Arduino + ESP-IDF SPI path- Chinese AliExpress VL53L8CX module- `SPI_I2C_N` forced HIGH for SPI mode- level-shifted module, jumper wires about 20 cm- SPI mode 3- SPI clock curre

I am trying to implement Time-of-Flight data acquisition using an STM32F405 microcontroller running FreeRTOS, with the MCU and the VL53L8CX communicating via SPI. However, the vl53l8cx_check_data_ready() function keeps failing, and I have been trying to track down the root cause.Here is what I have verified so far:After loading the firmware to the VL53L8CX and starting it, I confirmed that the sensor is emitting infrared light (observed using a camera).I checked the status return values from the API functions, and no errors were reported.There were no issues with the 3.3 V power supply, and no temporary voltage drops were observed during sensor reboot.I probed the INT pin with an oscilloscope to check if the VL53L8CX is outputting an interrupt signal at the interval set by vl53l8cx_set_ranging_frequency_hz. However, no interrupt signal was observed.For comparison, I tested a bare-metal (non-FreeRTOS) SPI implementation on a NUCLEO-F446RE evaluation board. In that setup, the interrupt s

I connected the VD55G1 promodule on the LS-CAM-I3C and connected it to the NUCLEO-H563ZI.The Display X-NUCLEO-GFX02Z1 is also connected.This is exactly the same configuration from the README.md.I get always an error in "ret = platform_i3c_assign_dynamic_address(p_dev->p_ctx);" (Line 82 display_qvga_streaming_i3C.c) I3C ErrorAccording to https://www.st.com/resource/en/user_manual/um3224-how-to-integrate-and-configure-the-vd55g1-sensor-stmicroelectronics.pdf Page35 I assume a ACK at the second W=0x7E (ENTDAA).I have a very shot cable between the NUCLEO Board and the LS-CAM-I3C.What could be the Problem

Greetings - I would like to request consideration for a Latched INT option similar to that of the STHS34PF80 sensor (Register: CTRL3 22h). I typically utilize the VL53 with Min/Max threshold values and would like the option to have the INT signal latched when the object is within threshold values.Thank you for the consideration,Terry

Is there a way to change the Horizontal front and backporch?   This is a addon to this question* https://community.st.com/t5/imaging-sensors/vd56g3-camera-change-the-frame-start-and-frame-end/m-p/888134#M6406@Jean_Poire 

I am using the VL53L7CX to measure a black object. When the object is placed at a distance beyond 200 mm, the readings become very unstable and a large number of erroneous points appear. Additionally, when a highly reflective object enters the sensor’s field of view, the points that were previously showing valid data for the black object also start returning errors. Once I remove the highly reflective object, those points recover and start reporting correctly again. In the error state, the affected points return no data at all — it seems as if the sensor does not detect any object. However, the black object is still present in the scene. The only change is the removal of the white object, which causes the sensor data to change significantly. Has anyone encountered a similar issue? Could this be related to crosstalk, or are there specific configuration settings recommended for black targets at longer distances? Any advice would be greatly appreciated.

I have an application where I run the VL53L1X in lite ranging mode and short distance mode with a timing budget of 10 ms (100 Hz) as described in AN5263.I recently noticed that on at least one unit (and probably more) the VL53L1X reports a spurious distance reading of 0 mm with no errors even though the sensor is pointing into an empty space and there are no objects within the 1.3 meter range of short distance mode.  This spurious reading happens about 10 times per minute, and the rest of the readings are regular expected errors.I am not using the API (STSW-007) directly, but have implemented code that does the equivalent thing.Here are some VL53L1X register values from these spurious readings:The lower 5 bits of the VL53L1X result__range_status register (0x89) is always 9.  That corresponds to VL53L1_DEVICEERROR_RANGECOMPLETE and that is the value that the API maps to 0.The result__stream_count register (0x8B) is between approximately 130 and 250.  The&nb