Imaging (sensors)

Hello, I have tested, the VL53L8CX tof sensor in interior (fixation at 3m10), and the visualization of the matrices works very well, in an empty scene or with a person pass under the sensor. When my sensor is fixed at the same height, but light up with daylight, next to the window, my matrices are noised, and when a person pass under it, there are some noise with the passage of the person. For example, the sensor create lots of pixels with this situation rather than the other. How to reduce this noise and this sensibility to the daylight ? 

Hi,I am developing an object detection system using the sensor, integrated inside the inner wall of a toilet bowl to detect falling waste. I am experiencing persistent "Low Confidence" issues, and I am looking for expert advice on whether this is an inherent physical limitation or a configuration issue.Current Setup & Environment: Environment: Actual toilet bowl (highly reflective curved ceramic surfaces). Hardware Integration: The sensor is mounted behind a cover glass, and an active NIR/Visible fill light is installed inside the bowl to assist a separate camera system. Configuration: VL53L7CX_RANGING_MODE_AUTONOMOUS @ 60Hz. The Phenomenon: Static/Idle State: Even in this real-world environment (with cover glass and fill light), the sensor produces some "Low Confidence" data points even when nothing is happening. Dynamic Event (Object Drop): When an object is dropped, the frequency of "Low Confidence" reports increases significantly, often rendering the detection logic unrel

Hello Team,I am using the STM32N657x0-Q Nucleo board with the STEVAL-66GYMAI1 (VD66GY) camera board connected via FFC. Both CN8 and CN10 are connected to the PC, and I am viewing the camera stream through UVC.I tested the official precompiled HEX files from: X-CUBE-N6 Camera Capture STM32N6 Getting Started Object Detection In all cases, the image is heavily blurred. Objects appear relatively clear only at approximately 1–2 cm from the lens, while anything beyond that distance becomes significantly out of focus.I attempted to adjust the M12 lens focus across its full rotation range, but no noticeable improvement was observed. The same behavior occurs with multiple example projects and unmodified hardware.Could you please advise which of the following areas is most relevant to investigate? Camera board compatibility with STM32N657x0-Q Sensor/lens configuration in the example firmware Lens focus or alignment issue Defective lens or hardware issue Recommended reference project/co

Hello, I have attempted to set up threshold interrupts with the VL53L1X using the library from pololu, but the lesser known version implementing the ST API. As such, my code looks like this: #include <Wire.h>#include "vl53l1_api.h"#include <Arduino.h>// Timing budget set through VL53L1_SetMeasurementTimingBudgetMicroSeconds().#define MEASUREMENT_BUDGET_MS 50// Interval between measurements, set through// VL53L1_SetInterMeasurementPeriodMilliSeconds(). According to the API user// manual (rev 2), "the minimum inter-measurement period must be longer than the// timing budget + 4 ms." The STM32Cube example from ST uses 500 ms, but we// reduce this to 55 ms to allow faster readings.#define INTER_MEASUREMENT_PERIOD_MS 55VL53L1_Dev_t dev;VL53L1_DEV Dev = &dev;int status;void printRangingData();void setup(){ uint8_t byteData = 0; uint16_t wordData = 0; Wire.begin(5, 6); Wire.setClock(400000); Serial.begin(115200); delay(3000); Serial.

Hi,I've got an X-NUCLEO-53L9A1. The board is in volume production and the product page advertises "full system software supplied, including code examples and graphical user interface", but the only downloads on that page are hardware files (Gerber, BOM, schematic). There's no driver, no example code, no GUI, no user manual. I've searched the product page, this forum, and GitHub and found nothing.On the host side: I have a NUCLEO-N6 (N657X0), and I see UM3655 is written around the STEVAL-VL53L9 on the N657X0 — so that looks like the intended dev path. But the GUI was demoed on a NUCLEO-H563ZI. I can buy a H563ZI if that's what's actually required, but I'd rather not guess.So, plainly:- Does the 53L9A1 software package (driver + code examples) exist for download yet, and where?- Is the GUI available, and which host does it need — H563ZI, or does it run on my N6?- If any of this isn't public yet, what's the route to get it, and when does it land on the product page?I just want to get the

Could you tell me VL53L8CX FDA Accession Number?

My test conditionAs you can see the detection volume of FoV is going outside the reflective block (blue block) and I am not getting accurate reading. I want to know whether there is a way to make the FoV much narrower so that I can concentrate on the reflective block placed opposite to the TOF sensor.

I'm testing the VL53L9CX sensor with the X-NUCLEO-53L9A1 board. I'm conducting my tests with the Nucleo H561ZI board and the X-CUBE-53L9A1.zip software stack.The sensor works correctly indoors. However, outdoors, when moving from shade to full sun, the sensor malfunctions.The software returns the error: VL53L9_ERROR_INVALID_STATE. why?In the datasheet, this isn’t a description of all registers? So I cannot clear this error without resetting the device!Can have a complet datasheet of the product?

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 refer to the coating requirements in the newly updated AN5231 Cover Glass Guidelines for Single-Zone Time-of-Flight Sensor.Section 4.3 states “Additional coatings are not recommended.” Section 5.2 states “IR ink can be used over exclusion areas.” Table 3 under Section 7 states “Adding ARC can improve transmittance.”There appears to be an inconsistency. How should we interpret this? Are ARC coatings and IR ink permitted? Per AN5231, Section 3.1 and 7 recommend an IR transmittance target of 87%, and Section 4.2 defines the minimum requirement as ≥85%. Could you advise if 85% transmittance meets compliance? Polycarbonate typically achieves ~85% IR transmittance and is included in the guideline’s recommended material list.If we apply ARC coating to boost transmittance, this brings us back to the first question.    

Wondering if VL53L9CX generates per-pixel histograms?It looks like there is no relevant information either in the datasheets or the released firmware. Many thanks,Z

The Data Brief for the STEVAL-CAM-M0I adapter board references the FH12-24S-0.5SH(55), which is a 24-pin connector. However, the cable pinout appears to be the usual 22 pins. Is this a mistake in the Data Brief, or is there something I'm overlooking?Data brief - STEVAL-CAM-M0I - P-Board: Hardware MIPI CSI-2 kit for the evaluation and integration of promodules on embedded processing platforms

Hi there!I'd like to use the STEVAL-CAM-M01 P-board to evaluate the VD55G0 BrightSense image sensor with the Discovery kit for the STM32N6 MCU (STM32N6570-DK). The discovery kit does have a camera connector, however, looking at the schematics it seems that the polarity of the CSI data and clock lines is swapped compared to the P-board. Everything else looks fine.Is it possible to use the P-Board with the Discovery kit without destroying either of the two? ST's marketing material (slide 33) seems to suggest it is possible but the schematics are unclear. Note that a similar question has been asked in the MCU forum, but it was suggested to ask in this forum to be sure. Also note that I'm not asking about software driver support here, only hardware compatibility.Camera connector on STM32N6 discovery kit: Connector on P-board:Thanks a lot!Michael

I need to develop an application for night vision using NUCLEO-N657X0-Q for a customer and I want to connect the right camera to the CN6 connector.I don’t know which camera I should choose. I need support to find the best solution.Thank you

Hi there,the VL53L5CX datasheet mentions that RSVD6 is a GPIO and defaults to being an open-drain; my question is:Can I use RSVD6 programmatically? Are there any resources which show it being used? Otherwise, how can I use it? Many thanks in advance

Hello everyone. I am trying to communicate with a VL53L4CD on my PCB, on the same I2C Bus I have a LP LED Matrix Controller and an EEPROM that work just as I hoped they would.  But none of the VL53L4CD seem to be able to communicate over the Bus. I have by now tried to look at everything possibly wrong with it.  Software: The Software gives out the exact I2C Signal I would be expecting (Address 0x52 (derived from 0x29 of course)) but I always get NACK’s,  Hardware: All Sensors are on the same bus, where I Chip Select via the XSHUT Pins, those forms also look correct and only the one is high where I want to talk to the sensor, so there’s not 2 sensors that could respond to the same address having XSHUT on the same niveau. I have tested the connection to the pads, and those are all correct, so is the Power SUpply and GND to the Chip all of those seem correct according to the Datasheet.  My I2C Bus runs on 100kHz which as far as I can tell should work with the Sensor.  Furthermore I have

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

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

For STM VB1940 what is the minimum exposure/integration time that can be set in global shutter mode.

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 

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.    

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?