Imaging (sensors)

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 

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!

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

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 ?

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, 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.

I am currently testing the VL53L7CX sensor(w/ vl53l5cx_api) with the STM32F7 MCU. The default resolution of 4x4, when running, would consistently return distances around 2.5 -3.0 meters with a target status code of 5 for multiple runs. I then tested 8x8 resolution and it began to return distances no higher than 1 meter with numerous error codes within the 64 zones target status (0,13,255 if I recall). Though, when I would hold my hand over the device it would return the ranges under a meter(this makes sense) with a target status 5 for all zones even when repeated. Please note that the room conditions of the 4x4 measurements and the 8x8 measurements were the same.  Is there any reason for the readings to be present incorrectly when 8x8 resolution is used but 4x4 seems to work as expected?   

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.

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

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

We are designing a lens cover to be used with VL53L9CX. Can you share any more data on the FoV of the time of flight sensor? The attached data sheet on the part page is for a different sensor "VL53L7CX" is there a data sheet for the "...9CX" version? In "Description of the fields of view of STMicroelectronics' Time-of-Flight sensors" Sections 3.2 & 3.3 reference exclusion cones which are given in a product data sheet. Could you please share this file? Also, 3.3 references keep-out cones which can be shared by contacting support. Any additional information would be helpful to ensure our lens does not interfere with the required FoV. Thank you! 

I have questions regarding estimated_reflectance and range_sigma in VL53L5 and L8The reflectance: how is it calculated? Is it R=signal_rate_per_spads*depth^2/K? the number_of sapds_enabled seems a useless parameter for a user? Can we know this calibrated constant K?The ambient_light has nothing to do with the R calculation?For these multi zone TOF, if we place a flat target in front of TOF, it shall give the same R. ST’ already does the internal compensation for the depth and for the angle of incidence. Right??  I can not find this kind of info in ST’s doc. Can only guess. If it has, please point out the Docs sourceThe range_sigma: for L5, if the resolution is 4 x 4, the readout is zero. I can read out  this parameter if it is 8 x8What is the default sigma_threshold for distance in L5? Is it the same for resolution  8x8 and 4 x4? Also, when I change this threshold, it is unclear if this threshold, e.g.,100mm shall multiply with a scale factor 128. Please confirm thatThan

I'm using the library here: https://github.com/stm32duino/VL53L1, and it seems to stop measuring around 3.2-3.5 meters. I may be wrong, but think that means that it is not using the histogram? I set it to long distance ranging mode.Here is my code:bool Sensor::ConfigureSensor(TOF &tofSensor) { Log.noticeln("Configuring [%s]", tofSensor.name); if (tofSensor.sensor_object == nullptr) { Log.fatal("No TOF sensor object initialized."); return false; } VL53L1_Error status; status = tofSensor.sensor_object->InitSensor(tofSensor.address); delay(10); if (status != VL53L1_ERROR_NONE) { Log.fatal("Failed to initialize %s. Status: %d. Halting.", tofSensor.name, status); while (1){;} return false; } Log.noticeln("%s address set to 0x%x", tofSensor.name, tofSensor.address); status = tofSensor.sensor_object->VL53L1_SetPresetMode(VL53L1_PRESETMODE_RANGING); delay(10); if (status != VL53L1_ERROR_NONE) { Log.errorln("Failed to set preset mode for %s", tofSen

Hello, I am using this sensor for a project where it is mounted on a cane to detect overhanging objects that could hit visually impaired people. This works fine indoors, but outdoors, when the ambient light is around or greater than 10k Lux—and keeping in mind the sensor is pointed upwards and hit directly by sunlight—it only catches obstacles when they are very close. I am currently using a 4x4 resolution with continuous ranging at 30Hz. My question is: is there a way to increase its efficiency? By efficiency, I mean increasing the detection distance through hardware, structural, or software solutions.

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.  

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. 

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