Imaging (sensors)

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?

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

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.

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_S

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,

I am using the above 2 EVAL boards from ST. I am trying to get the video pipeline going to the point that I do receive the images in memory and the appropriate frame based interrupts are triggered to verify. I have tooled my code for minimal application and it fails. I have started with ST provided x-cube-n6-ai-h264-usb-uvc reference and am using the STM32Cube_FW_N6_V1.3.0 SDK provided. I am using the STMCubeIDE for development.From the terse documentation/information it seems that the 2 EVALs procured should be compatible. However, as mentioned in the other post: https://community.st.com/t5/stm32-mcus-boards-and-hardware/stm32n6-fpc-camera/m-p/755889 , I have found the hard way that the sensor MIPI lane polarities are flipped. i.e. Dx_P and Dx_N from the sensor to the Nucleo Eval.Q1. I have looked through the documentation and have no i

Hi,It seems that some of my measurements (in a green jojo tank) are resulting in a `VL53L4CX_RANGESTATUS_OUTOFBOUNDS_FAIL` error.The measurement itself seems to still be correct as the tank is empty, and the result is around 1800mm.I check the documentation and i don't really see an explanation for this error. It says things are 'out of bounds' but does that simply mean there's not enough reflection?I've taken this sensor because it would do up to 4m, so i'm wondering what i'm doing wrong :) 

I am using VL53L4CX with VL53L4CD ULD driver v2.2.2, due to an I2C issue on my side the VL53L4CD_RdWord fails and the number_of_spad variable is set to 0. The divide by zero happen at the very end of VL53L4CD_GetResult.I checked the function in ULD v2.2.3 and the number_of_spad value is still used for division without checks :VL53L4CD_Error VL53L4CD_GetResult( Dev_t dev, VL53L4CD_ResultsData_t *p_result) { VL53L4CD_Error status = VL53L4CD_ERROR_NONE; uint16_t temp_16; uint8_t temp_8; uint16_t raw_spads; uint8_t status_rtn[24] = { 255, 255, 255, 5, 2, 4, 1, 7, 3, 0, 255, 255, 9, 13, 255, 255, 255, 255, 10, 6, 255, 255, 11, 12 }; status |= VL53L4CD_RdByte(dev, VL53L4CD_RESULT__RANGE_STATUS, &temp_8); temp_8 = temp_8 & (uint8_t)0x1F; if (temp_8 < (uint8_t)24) { temp_8 = status_rtn[temp_8]; } p_result->range_status = temp_8; status |= VL53L4CD_RdWord(dev, VL53L4CD_RESULT__SPAD_

Hi,i'm playing around with the VL53L4CX after putting it on my own pcb (yay).The user guide states that for the SPAD caliberation, NO target should be placed. The crosstalk requires a 600mm target.Do i understand correctly that the SPAD caliberation therefor is best performed outside and upwards to the sky? Or maybe in a room that is at least 6 meter long?It confuses me because i wonder how this is done in a factory where space is a premium :) Kind regards,        Ruben 

Hello There  I have question regarding calibration of offset and cross talk for VL53L4CD / VL53L4ED.For my application i need to config Signal Threshold, Sigma Threshold, Timing Budget etc to other than sensor's default value,  So, my question is should i do xtalk & offset calibration with sensor's default config? or i need to do  calibration with my custom config?   Regards

Hi, I'm trying out the VL53 series to try to measure the height of liquids in a container. In my use case, we are measuring sauce in sauce cups - ranch dressing, hot sauce, etc. One issue we have noticed is that with oil or oily sauces such as olive oil. The sensor is not responding with the correct depth measurement. The sauce can be 4-6 inches from the sensor. Looking at the documentation, there could be some cross talk issue, however we don't what sauce will be used. (The user can provide different sauces) - Do you have recommendations on how to get better results with this sensor?

Does anyone have access to documentation with an actual list of registers with addresses and functionality and a full description of the register bits for the VL53L0X?  All I have been able to find is documentation that refers to the questionable API driver package and some doxygen-generated document based on the comments in the API.  

For the same setup the distance values jump between a very high and a very low value. Setup 1: unit facing an open space(ceiling) Result 1 Result 2 Result 3 2514, 2483, 2466, 2407, 2752, 2799, 2808,   15,    0,    0,    0,    0,    0,    0,    0,    0 2474, 2461, 2475, 3021, 

I have an application that uses 10 VL53L0X sensors on an I2C bus.  I seem to have ended up damaging multiple STM32 dev boards trying to get this configuration to work reliably.  Any help to understand what I am doing wrong would be appreciated.So, there are 10 VL53L0X sensors on a single I2C bus connected to the I2C port on a Nucleo dev board.  There is a mechanism to enable each independently to set the I2C address, after which they all operate in continuous sampling mode and the MCU polls for results periodically.  This works fine, sort of, and the data comes in OK.  At some point everything stops and that's the end of it. I have found that the I2C port on the dev board seems to have been damaged and no longer works at all (probing with multi-channel scope).  There was nothing else connected to the dev board, just the I2C lines.The VL53L0X sensors have their own 3V power supply which is manu

Hi Team,In this post regarding VL6180x proximity sensor, the sensor is detecting the address(0x29) but the readings are receiving as 255 value even the object it detected in front of sensor. for reference purpose go through this code snippet wrote in arduino IDE for ESP32-WROVER-IE. What might be the problem?Regards, #include <Wire.h> #include "Adafruit_VL6180X.h" #define SDA 23 #define SCL 22 Adafruit_VL6180X vl; void setup() { Serial.begin(115200); delay(1000); Serial.println("Starting I2C..."); Wire.begin(SDA, SCL); delay(100); Serial.println("VL6180X test"); if (!vl.begin()) { Serial.println("Failed to find VL6180X"); while (1); } Serial.println("VL6180X found!"); } void loop() { //Serial.println("hi"); uint8_t range = vl.readRange(); uint8_t status = vl.readRangeStatus(); // if (status == VL6180X_ERROR_NONE) { Serial.print("Range: "); Serial.println(range); //} //de

Hi，     1》In the dark，Place the white target 140mm from the sensor          call function         Status = VL53L0X_perform_offset_calibration(&vl53l0x_dev,0x8c0000,&pOffsetMicroMeter);     2》In indoor environments ，Place the black target  600mm from sensor         call function         Status = VL53L0X_perform_xtalk_calibration(&vl53l0x_dev, 0x2580000, &pXTalkCompensationRateMegaCps);    3》in main function               Status = VL53L0X_set_offset_calibration_data_micro_meter(&vl53l0x_dev,&pOffsetMicroMeter);

Hello, I have a VL53 sensor that's outputing distance data but the distance measurements I'm getting are getting "stratified" into about 3 different distances seemingly randomly. I'm using the ULD driver on a custom PCBA with a TM4C1239 microcontroller and sampling the sensor at 10 Hz. This first video is with no obstacle in front of the sensor. You can see the data is not consistent

Hi,I am using the STEVAL-EVK-U0I kit with the VD55G0 sensor and the provided Python SDK. Firstly, I wanted to say I really love the capabilities of this sensor and it looks extremely useful for my work. My goal is to capture high frame rates (200-500 FPS) using subsampling. I have configured the sensor for 4x4 Subsampling and a short frame length. Based on the VD55G0_REG_STATUS_FRAME_COUNTER and VD55G0_REG_STATUS_FRAME_RATE, the sensor is successfully generating ~530 FPS.My problem is the following: While the sensors seem to be running at 530 FPS, the Python get_raw_image() function appears to be retrieving frames at 80-110 FPS. I am also getting a heap corruption error (perhaps the SDK cannot keep up with this high framerate? I am not sure).My questions :- Is this Python SDK capable of handling that high framerate, or am I doing something wrong?- How can I capture these high framerates? - Is there any other API (C/C++?) whi

Hello,  I try to get data from a X-NUCLEO-53L8-A1 board connected to a Nucleo board and visualize it in my computer. If I use the VL53L8CX Gui and connect my COM port and click on the start button, it is working well. However, I would like to get data outside of the app (ex: Tera Term or python script) but I do not have data available. I suppose that the sensor/board is waiting for "start" but I can not find any documentation on the subject.  Can someone help me on the subject ?   Best regards

Hello, I have multiple VL53L0X sensors that I am communicating with over an STM32 board. Two of the sensors started throwing errors (only reading 8191), and so I moved them to an Arduino for the flexibility of using the downloadable API. They worked perfectly fine on the Arduino, so I am wondering what the issue with the STM code might be. I am using the following repo: https://github.com/MarcelMG?tab=repositoriesalong with i2c code that I wrote because I have a different stm model, but don't see that being the problem. Any help would be appreciated!

    I have performed crosstalk calibration of VL53L7CX ToF sensor using a 0.2 mm thick polycarbonate cover glass. I had used a sheet of white paper (assuming 80% reflections) placed at 600m as reference surface & 4 samples were used for calibration.    The calibrated sensor's accuracy was tested using a similar setup but with reference surface at 400 mm. The distance values observed in the 64 zones ranged from 396 to 426 mm. The standard deviation of the distance values were in the range of 2.2 to 4.5 mm. The heatmap of the zones also looked uniform.    But when I mounted the sensor in an enclosed space (around 1m X 1m X 1.5m) upside down pointed towards my objects of interest, I'm observing some random ghost detection in some of the zones. There are no objects in these zones at distances given by the ghost detections. But there could be objects/surfaces in nearby zones. Also, these ghost detections were not present when I did the

Hello,We have lately been seeing in some cases that one or two pixels seem to be stuck at distance_mm==0. Sometimes the pixel goes back to returning normal values after some time or after a power cycle, but sometimes it seems to report a zero value consistantly. I will implement some more debugging to get the status of the measurements, but I was wondering if you had any input into why a zero value could be measured for one or two pixels?

ULPM for the MIPI CSI interface of VD55G1 is not clearly described.Errata (es0643) section "QVGA at 480 fps" say that we should put MIPI in ULPM. Why does this affect timing?WRITE_REG8 STREAM_STATICS_OIF_ULPM 'h01 # MIPI in ULPMIs this a MIPI setting (continuous/discontinuous)? Additionally, a register write is referred to that is not documented anywhere in the datasheet or integration guide.WRITE_REG8 CHANNEL_STATS_ROI_REDUCE_FACTOR 'h10 # 16 lines removed to the stats ROIWhat is this register? The address is not even known.

Hello community, I am working with the VL53L0X Time-of-Flight distance sensor and the official ST API driver (VL53L0X API package).My hardware platform is: STM32H747I-DISCO board (CM7 core) I2C3 used to interface the VL53L0X FreeRTOS running on CM7 Display controlled using TouchGFX I copied the VL53L0X API (platform.c, platform.h, vl53l0x_api., vl53l0x_platform. etc.) into my STM32 project. Issue:  When I call any API functions Inside a FreeRTOS task, the code does not proceed beyond the first API call.