Imaging (sensors)

I am currently working with the VL6180X proximity sensor and would like to inquire about its long-term performance characteristics:      1. What is the expected Light/Luminous Depreciation time frame for the VL6180X's VCSEL source? Could you                provide any data regarding its lumen maintenance curve or L70/L50 specifications?     2.How does Light/Luminous Depreciation affect the sensor's performance over time?        Specifically:                 1. Does it primarily manifest as a reduction in return signal rate?                 2. Are there any observable changes in measurement accuracy?                 3. What are the typical indicators that Light/Luminous Depreciation has occurred?      3.

I’m using a VL53L5CXV0DH/1 sensor in my current setup (see pictures). The goal is to detect a ball rolling between the sensor and the background. The red box is about 12cm apart.The settings is 4x4 for speed, i also noticed that 60 is not the highest scan frequency in code : status = vl53l5cx_set_ranging_frequency_hz(&dev,60);if i set 120 this works too, while scanning seems to be lot faster and just as accurate, why is 60 defined as maximum in the datasheet?However (even at 60), I often see target_status = 255 for 3-4 pads, without the ball passing and wonder why this happens. When this occurs, the distance information is apparently correct but the datasheets states that the distance readings become unreliable, and I want to ensure I get the most accurate and dependable measurements.When the ball passes i see 255 in even more status records.What could be causing this issue?Additionally, I’d appreciate any advic

I need to calibrate a VL53L4CX and have been reading UM2923. The functions described do not seem to bear any obvious relationship to the functions in the STM32Cube middleware which was generated for my project, which I find confusing. I it is not clear which functions I should be calling in order to satisfy the flow charts in UM2923. I have found essentially no other useful information about this device or its specific set of registers. I'm usually a huge fan of ST devices and documentation... The first sticking point is how to properly understand what to do with calibration settings. Am I supposed to store them in my own flash somewhere? That seems to be implied by UM2923. I can do this, but imagined the device would have its own NVM storage on board, since it is calibrated in the factory anyway. Is this the case? I thought so because the wrapper function VL53L4A2_RANGING_SENSOR_OffsetCalibration() ends by writing a data structure over the I2C interface from a function calle

Hi everyone,I know there are 25 and 35 degree detection angles of VL53L3. I am aware that this situation is a mechanical situation. But I want to make a timing gate and find people's speeds. We have submitted our product to reliability and validity tests, but the detection situation at 25 and 35 degree angles prevents us from getting this reliability and validity tests. We want it to detect when the target is right in front of (linear detection) the sensor. Is there a software solution for this?  

Hello again!I've been trying to measure water level using the VL53L1 sensor and reading forum posts on it, and I've gathered that RefSPAD calibration isn't really recommended anymore.From my research on the topic, I know that water reflects only 2% of perpendicular incident light, with the rest getting transmitted and also that the transmitted rays will be fully absorbed at a minimum water level of 10cm.I was wondering if doing the RefSPAD calibration utilizing the VL53L1 (with a cover glass) leveled parallel to a water suface from a body deep enough to absorb all transmitted laser could end up improving the sensor's results by giving more weight to SPADs more likely to detect those perfectly reflected photons.Thanks in advance!

Hello,For the vd55g0, you provide a kernel driver and device tree as source here: https://www.st.com/en/embedded-software/stsw-img505.htmlYou also provide a libcamera integration stack (STSW-IMG505_LCAM), but this is closed source, and only the libcamera-base.so and libcamera.so files are provided via the .deb package. This makes it such that we cannot work with the libcamera source or custom applications, unless we use your pre-compiled libcamera libraries.Could we please get source code for the changes, per LGPL 2.1, which libcamera uses? Or, for now, if this takes some time for you to do, please just the camera helper file would be massively helpful. This is likely called "camera_helper_vd55g0.cpp" inside of "src/ipa/rpi/cam_helper/".

I bought a STEVAL-55G0MBI1, which is the VD55G0 S-Board eval kit. Trying to output the image to my PC, nothing is coming out.  What could be the issue with my setup?  

Hi, when using the VL53L1X, it is suggested to check for the range status and 0(zero) is considered the desired range status. Now, as I understand it, the range status 2(two) is dependent on the signal threshold. By default, the signal threshold is set to 1024, and can be adjusted by calling the SetSignalThreshold().My problem is that, at larger distance (around 2m), the signal rate that I am getting by checking GetSignalRate() is way below. Sometimes around 30-60. This results in getting range status 2 all the time. So should i modify the signal threshold value to less than 50 so that I can consider the distance I read is valid. But are the distances valid if I do this? Or what are the possible signal threshold value that I could set so I can get the range status 0?Another issue is that even in open air, I am getting range status 2 with distance being reported at 2.2m~2.7m. This affects my reading because I cannot differentiate between the valid signal betwe

We use VL53L1X for liquid level detection purposes.We believe that the “signal-rate” needs to be high in order to accurately detect the surface of the water at a distance.We are considering the VL53L1CB as a candidate.Is the VL53L1CB a good candidate?It is important that the VL53L1CB is software-compatible with the VL53L1X.Thank you. 飛行時間

Hi, Is there anyway I can add more dynamic gesture to Gesture Kit ULD? Currently What I see is that it supports up to UP, DOWN, LEFT, RIGHT, TAP, and Double TAP. If there is a way, could you share what is the process of it? Thank you.  

May I ask how to convert the IR channel ADC value of VD6283TX45 to IR optical power, only the RGB channel is converted to Lux in Driver, and there is no description about this IR optical power in Datasheet. 

Greetings!When I measure objects closer than 10 mm from the VL53L4CD, the result deviates significantly from what was expected, and the result also varies significantly depending on the texture and gloss of the object.Is it possible to configure the VL53L4CD to be more accurate in the range 0 - 10mm distance from the sensor?I have carried out some simple test measurements in the range 20 - 0 mm with the colors matt black, matt grey, light yellow and shiny white. Please read the uploaded PDF showing measuring test results and graphs. Regards Jorgen

Hi ST,I wanted to validate/confirm our Calibration procedure.  When we calibrate prior to calibration we set timing budget and intermeasurement to what they are normally when our code boots up.  So,  during calibration we do the same.  Can someone please confirm this is the correct procedure? Meaning,  should we set TimingBudget, InterMeasure, ROI and ROI Center to "anything" prior to running calibration or are we correct in how we are doing this. .....VL53L1X_SetTimingBudgetInMs(33);VL53L1X_SetInterMeasurementInMs(40);VL53L1X_SetROI(4, 4);VL53L1X_SetROICenter(191);status = VL53L1X_CalibrateOffset(TargetDist, &Offset);..... Thanks,Will   

The "vl53l8cx_buffers.h" file bundled with X-CUBE-TOF1 seems to have been updated several times, but I would like to know what problems have been fixed in each version. Please let me know in which document the revision notes is listed.Thank you in advance.

We are having issues with the VL53L4CD Time of Flight Sensor.The sensor works properly after initialization, but after some measurements it starts having problems. It either stops ranging or returns a ranging result similar or equal to the previous one, while returning data ready TRUE and ranging OK (Results status 0).  Here's a description of what happens when the sensor still ranges but gives wrong results (second case):- We take an initial ranging (distance from an object)- We move the sensor away from the object- We ask for a ranging: the result is similar or equal to the initial measure.- Now we move the sensor away again- We ask for a new ranging: the result is the one we expect after the first movement. Some detailed info:- The sensor initialization is copied from the "ranging basics" example attached wit

Hello all,We are once again using one of the VL53 TOF sensors for a close-proximity ranging application. For this application we are using code from the VL53L4CD_ULD_Driver.After initialising the system using the VL53L4CD_SensorInit function, we are obtaining single measurements by starting the sensor via VL53L4CD_StartRanging and getting results via get_data_by_interrupt()We are noticing that if the target distance is changed, the first 2 or 3 measurements after the target distance change, are incorrect (look like values from the previous target distance). The 3rd or 4th measurement (and onwards) are correct. Please have a look at the below log: --------------------------------------------------------------------------------------------------------------------------------------bVL53L4CD ULD ready ! - VL53L4CD INITIALISEDTARGET PLACED ~85MM FROM SENSO

Hello ! My environment:Windows 11Arduino IDE 2.3.2STM32 Cores    https://github.com/stm32duino/Arduino_Core_STM32/wiki/Getting-StartedLibrary                 X-NUCLEO-53L5A1   1.1.1   https://github.com/stm32duino/X-NUCLEO-53L5A1                 VL53L5CX    1.2.3     https://github.com/stm32duino/VL53L5CX

Hi, I'm hosting a VL53L8CX with a STM32F4, 48-pin instead of the 64-pin on your eval board. There's a 5" flex cable between processor and L8. The vl53l8cx_init() function was failing. Slowing the SPI baud didn't help. Increasing wait time on line 276 of the api file didn't help. The thing that fixed it was inserting a brief delay at line 274 of the api file, which was slightly before you have a delay. Source code snippet below shows my delay.BTW, I noticed that the .ioc file that came with your ULD has the SPI bus disabled. Did you do some custom monkeying with the HAL SPI driver? I'm using the .ioc and HAL driver, as is, with my application. And it works, as long as I add the delay described here. status |= VL53L8CX_WrByte(&(p_dev->platform), 0x000F, 0x43);status |= VL53L8CX_WaitMs(&(p_dev->platform), 1);status |= VL53L8CX_WrByte(&

I'm using the VL43L4CX and with every measurement, I get the next range status: VL53LX_RANGESTATUS_RANGE_VALID_NO_WRAP_CHECK_FAILFrom the documentation, I can't find any indications of what to do in this case and how to solve it.From the code I see that this is set when wraparound check isn't performed. This is also visible because for longer distances 3m+ I get an offset with around 3m offset.I'm using the same code as in this example: https://www.st.com/en/embedded-software/stsw-img029.htmland I haven't changed any of the tuning parameters.How to address this and make the algorithm perform the wraparound check?

Hi, I've been developing a simple water level sensor with the VL53L0X and i'm having trouble putting it into the enclosure that is protected from the moisture. I've been mainly experimenting now, but one of my problems is mounting the sensor behind glass or something like that. I'm happy to glue that on over a hole or something, but wanted to figure out what works.I've followed some of the video's around crosstalk and have made a 3d print that should help (please see photos).The sensor works as expected in the 3d printed element, but doesn't work properly when i add the glass lens filter. I took the lens filter after trying a few other things, but not being great at materials, i wanted to be sure, so i tested with this filter from one of my camera lenses.I think i'm doing everything correctly, albeit not professionally, but can't get it to work.I would be greatful if somebody could point out some issues that i might have made.

Hi,Is there a way to obtain the actual SDAD location that is currently being detected. The reason for this is because I want to map out the locations and can see what are actually being triggered.I am using 4x4 ROI with 199 as the center.Thanks.

Hi there,My first post on here, and I appreciate your time reading it.I have some VL53L0X time-of-flight boards, and want to interface one with the Espressif ESP32 development board.My primary objective is to run this set up at low power, so I want to be able put the ESP32 to sleep and wake it up when the VL53L0X detects a "below the low distance threshold" event. To do this I will need the GPIO1 pin to fire an interrupt when the threshold is breached. I have copied the Pololu VL53L0X library source and am currently using that as my library. It works well for basic measuring functions in both continuous and single shot modes. But no matter what I do I have been unable to get it to generate an interrupt. I've tried lots of approaches... the code posted here is working for basic measurement at least. #include <Adafruit_GFX.h> #include <Adafruit_ILI9341.h> #include <Wire.h> #include <VL

I'm looking to integrate a ToF into our product for gesture recognition. I have my eyes on theVL53L8CH, VL53L8CX and the previous VL53L7CH, VL53L7CX. I understand the difference between the different generations. But I've been all over the datasheet, and yet I can't find the difference between the so call "AI enabling" CH ones, and the "High Performance" CX ones. Is there an actual difference, or is it just a marketing gimmick.Thanks!https://www.st.com/en/imaging-and-photonics-solutions/vl53l8cx.html 8cxhttps://www.st.com/en/imaging-and-photonics-solutions/vl53l8ch.html 8ch

HelloI open this thread as a continuation of this other one, which is very long. My problem is that the boot states I read with "VL53L1X_BootState" (0x02 and 0x03) do not match the documentation (0x00 and 0x01).As John says in the aforementioned thread: "The bootstate register spec is: [1] firmware_first_range: FW first range status [0] firmware_bootup

Hi everyone,I'm thoroughly flummoxed and in need of guidance.  I have a VL53L4CD rangefinder on the SparkFun breakout board that will not play nice with my Raspberry Pi.  Long story short, the rangefinder seems to be ACKing prematurely under certain conditions.  Confusingly, an identical setup has worked great in the past.BackgroundLast year I used the VL53L4CD as part of a simple Raspberry Pi 4B-controlled payload.  Using the SparkFun breakout board we did some lab testing with the rangefinder connected straight to the Pi, powered by the Pi's 3V3 regulator.  We had some issues with continually bombarding the rangefinder with DataReady() requests but by waiting a few ms between queries our problems went away.  The final product involved a couple custom PCBs with a beefier 3V3 linear regulator for the non-Pi electronics an