Imaging (sensors)

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 multip

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); sta

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

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.    

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:

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?

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.

 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

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.