Imaging (sensors)

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

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!

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

Hi, Was wondering if there is any info on when the VL53L9CX is expected to be released? Regards 

Dear Sir/Madam,I am currently using a Nucleo development board to perform trials with the VL53L4CD ToF sensor.I have a question regarding the sensor’s performance in the near field range of approximately 1 to 15 cm. During testing, I positioned a matte white reference object at around 10 cm. In the data log files, I frequently observe NaN values in the measurements. However, in the GUI, a distance value is always displayed, which may possibly be interpolated.I have attached a figure from my data log showing the measurements with the reference object at approximately 10 cm.- Is this a known issue? Additionally, are there recommended methods or configuration settings to improve data quality at short distances?- What would be considered a proper or expected signal rate for this sensor? Is there a recommended range to strive for in order to ensure reliable measurements?Thank you in advance for your support.Kind regards,Jort 

Hello,we are using VL6180X and VL53L4CD sensors in an outdoor setup and we have issues with sunlight (even reflected light).To improve sunlight rejection, we added Thorlabs bandpass filters:FBH850-10 for VL6180X (850 nm)FBH940-10 for VL53L4CD (940 nm)Both filters are 2 mm thick.The filter is placed ~1 mm in front of the sensor window.We have four identical sensors per type; only one has the filter.Observations:Sensors without filter measure correctly (e.g. 143 mm → 143 mm, 70 mm → 70 mm).The sensor with the filter almost always reports a short distance (~20–30 mm).Even when the real target distance changes significantly, the filtered sensor reading remains almost constant.This looks like strong optical crosstalk rather than noise.Questions:Is a 2 mm interference filter likely to introduce severe crosstalk?Could the 1 mm air gap be the main cause?Would a much thinner IR-pass filter be more appropriate?Can the crosstalk calibration compensate for this configuration?Any guidance on proper

Hi Team, I could only find the databrief and not the datasheet for VL53L1X-SATEL breakout boards. Could you provide a detailed datasheet mentioning the current consumption and power consumption at 2.8V, 3.3V and 5V respectively?I currently have a VL53L1X-SATEL breakout board for development and do you recommend the input voltage to be in 2.8V, 3.3V or 5V for this breakout board to obtain best performance from this sensor breakout board?Looking forward to your immediate and esteemed response.Best RegardsSreejith R Nair

Dear altruist, I need urgent help. Can I apply hardware-based external triggering in the VL53L8CX sensor by STM32 Nucleo F401RE? Will the sensor work for external triggering? Thank you 

I've interfaced the VL53L4CD with ESP32-S3, but I'm unable to get accurate ranging values below 70mm.I'm using the ESP32-S3 with Arduino IDE.How can I resolve this issue ?#include <Wire.h> #include "vl53l4cd_class.h" #define SDA_PIN 8 #define SCL_PIN 9 VL53L4CD sensor(&Wire, -1); // -1 = XSHUT not used void setup() { Serial.begin(115200); delay(1000); Wire.begin(SDA_PIN, SCL_PIN); Wire.setClock(400000); Serial.println("VL53L4CD Init..."); if (sensor.begin() != 0) { Serial.println("VL53L4CD not detected"); while (1); } Serial.println("VL53L4CD detected"); sensor.VL53L4CD_SetRangeTiming(50, 0); // 50ms timing sensor.VL53L4CD_StartRanging(); } void loop() { uint8_t dataReady = 0; VL53L4CD_Result_t results; sensor.VL53L4CD_CheckForDataReady(&dataReady); if (dataReady) { sensor.VL53L4CD_GetResult(&results); sensor.VL53L4CD_ClearInterrupt(); Serial.print("Distance: "); Serial.print(results.distance_mm); Serial.println(" mm"); } delay(20);

 Title: VL53L8CX pulls SCK line low on ESP32 – PCB or power-up issue?Hello everyone,I’m currently developing a prototype using a VL53L8CX sensor together with an ESP32 controller. On our PCB, the sensor seems to permanently pull the SCK line low. This is already the second revision of the PCB, so with fairly high confidence I can rule out a basic PCB layout or routing issue. Here are my questions: Can you spot any possible mistakes in the schematic?Do you know under which conditions the VL53L8CX might actively pull SCK low? (To me it looks like an internal IC problem)Could this be related to the power-up or reset sequence of the sensor?Do you have any general debugging tips for this kind of issue?The SCK line is connected through a TXS0108 level shifter. With a different I²C device, the TXS0108 works perfectly fine, so I’m not sure if it’s involved here — but could the TXS0108 still cause problems in this setup?On the software side, I already tried:Running an I²C scanner

HiI am using Vl53L1X to measure dark surface upto 1000 cm far.. I am using a split cover glass(specifications attached). The benefits of using the split cover is that it prevents crosstalk. But even after attaching the cover, the distance measured by the sensor decreases when the object moves away from the sensor.  Do I still need crosstalk calibration with cover glass or the cover is not ok.I have configured my sensor as follows:status = VL53L1X_SetDistanceMode(dev, 2); /* 1=short, 2=long */ status = VL53L1X_SetTimingBudgetInMs(dev, 100000); /* in ms possible values [20, 50, 100, 200, 500] */ status = VL53L1X_SetSignalThreshold(dev, 1024);//500); VL53L1X_SetROI(dev, 16, 16); // Full FoV (start here)  

Hi Community,I’m just finishing off development of a product containing VL53L4CD and need to start to think about approvals etc. ready for product launch. The product as a whole relies on human interaction, so users will be physically close to the product and therefore the beam.Judging by the datasheet for the part, there is no need to perform any testing for eye safety, relying instead on ST’s own certified testing, provided that we use the device in accordance with the datasheet (which of course we do) and there’s no attempt to focus the beam (which there isn’t). This will all be wrapped up in a detailed technical file, along with ST's certs.The artwork on the product carries the Class 1 laser radiation logo and in the instructions the customer is warned never to attempt to focus the beam, nor to stare into it.Is this sufficient due diligence, or have other developers done more and if so, what?TIA.

 I am currently trying to control a VL53L8CX sensor via SPI communication from the microcontroller mounted on a Crazyflie drone.However, inside vl53l8cx_check_data_ready(), the values in temp_buffer became as follows. Indices [0] to [2] look correct, but at temp_buffer[3], the condition  ((p_dev->temp_buffer[3] & (uint8_t)0x10) == (uint8_t)0x10)evaluates to false.What exactly is this comparison checking?When temp_buffer[3] returns an incorrect value like this, which specific part of the communication or control process is likely failing?temp_buffer[0]: 0x0temp_buffer[1]: 0x5temp_buffer[2]: 0xC5temp_buffer[3]: 0xC1

Hi, I'm supporting a legacy product which uses this older sensor, VL6180X.Where could I find the API source code for download? It seems that all links for "STSW-IMG003", "STSW-IMG011" etc. which are listed in the docs have been erased from the site. Could someone provide a working link to the latest API version, or perhaps just attach the .zip here for posterity?Thanks in advance!

What is the marking on the bottom side of these sensors i.e. VL53L1X and VL53L1? for eg. on the bottom of VL53L1X it is written VL53LIB...so what is the marking for VL53L sensor. Basically I want to know how can I distuingh between these 2 sensors as both of these sensors returns the same model and module id.

HiI have been messing around with VL53L4CD for the last few months, and I recently realized that my readings differ significantly, depending on the target color/texture.Here is my setup: The sensor is set on its side, and directly in front of it, at the 20cm mark, I place a few different gray-level cardboard boxes, ranging from black to white, mostly gloss-textured.The sensor readings vary by about 10mm (222 shortest, 233 longest) depending on the box.Performing offset calibration helps to have an accurate reading on a gray target, but the error persists for other colors.I have tried performing cross-talk calibration, although I don't have a cover glass for this test, but that doesn't seem to help either.My question is - do we have to know the target reflectivity in advance and calibrate for it? Am I wrong to expect more consistent readings against various targets?Thanks!

Hi,I'm working on a people counting system using the VL53L1X in multi-zone mode with a single sensor. It works well in general, but I'm seeing accuracy issues when people wear black or dark clothing—likely due to low reflectivity.I’d appreciate some guidance:Would the VL53L5CX provide better detection for dark clothing?Does it handle low-reflectivity surfaces more reliably?Or would it be better to use multiple VL53L1X sensors?Any other sensor recommendations for more reliable people detection?Thanks in advance!Basil

Hello, I have a question about the temperature calibration for the VL53L0X Time-of-Flight sensor.The UM2039 manual states the following:> [Temperature calibration] has only to be done before offset and cross-talk calibrations, after Reference SPADs  management and before the first ranging is performed.During assembly of our product, those calibration steps (SPADs, Temperature, Offset, XTalk) are performed in order.To account for possible temperature changes when the device is in use, we call both  `VL53L0X_PerformRefSPADManagement` and `VL53L0X_PerformRefCalibration` on device boot to ensure the sensor is ready for use for the current temperature.My question is if this would affect the offset and xtalk calibrations, since the docs state that temperature calibration must be perfomed before those. Or is that sequence merely to ensure the offset and xtalk calibrations are done with the correct temperature calibration.Thank you for your time.

This is a continuation from this post, where I erroneously marked the post as solved: https://community.st.com/t5/imaging-sensors/vl53l7cx-distance-data-stratification/td-p/866073Unfortunately I'm still experiencing the issue where range data continue to be unstable, and appear to stratify or cluster into discrete magnitudes.Test setup:2x VL53L7CX sensors on one I2C busCover glass installed on both sensorsRanging enabled on both sensorsThe video is showing data from a single sensorI have a test setup with a sensor looking at the back of a notebook at a fixed distance as shown in this picture. The range data returned from the sensor varies between actual the distance, and shorter distances. You can see this in the video below. In addition, in the video I'm also printing the `target_status` for all 64 zones on the terminal output to the right. Would anyone have insight, or perhaps offer troubleshooting steps?  Thank you EDIT: Added test setup details

HeyI've got great success with the VL53L4CX at sorter ranges, but at longer ranges i seem to get two objects. One closeby between 10 and 30mm away, and one at the distance that it should be.I've done calibration and i cant' get this to go away. I'm assuming it's crosstalk but i've done the crosstalk calibration and so on. What could this be?Example of some of my log output, where you can see the two outputs and some other values from the same measurements.[995156] PerformMeasurement(offset=0, maxdepth=2000, ignoreBelow=10)[995162] Read 388 bytes...[995163] VL53L4CX_SetCalibrationData status: VL53L4CX_ERROR_NONE[995166] VL53L4CX_SetXTalkCompensationEnable status: VL53L4CX_ERROR_NONE[995166] VL53L4CX_SetMeasurementTimingBudgetMicroSeconds status: VL53L4CX_ERROR_NONE[995166] VL53L4CX_SetDistanceMode status: VL53L4CX_ERROR_NONE[995166] VL53L4CX_SetOffsetCorrectionMode status: VL53L4CX_ERROR_NONE[995166] VL53L4CX_SmudgeCorrectionEnable status: VL53L4CX_ERROR_NONE[995166] VL53L4CX_SetUserROI

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

HI,I'm using the VL53L4CX and in an enclosure and thus have a cover glass over the sensor.i've been doing some simple calibration, but have noticed that this requires a strict procedure and preferably a good setup to perform the calibration.I therefor want to make a box to perform the calibration in. This should remove any variables and make sure that calibration is handled the same every time.I know i should be able to copy the calibration data from one device to the other, but due to it being a lorawan device, and my current provisioning/flashing steps, it's easier for me to calibrate the sensor afterwards.I posted the same question here: https://community.st.com/t5/imaging-sensors/vl53l4cx-refspad-caliberation-no-target/m-p/869701/highlight/true#M6277 but that's a fairly old topic, so i'm starting a new one. My current idea for a wooden calibration box is:Wooden (probably MDF) box with an internal height from sensor to top of 60cm, probably 40cm wide.Matt black paint