Imaging (sensors)

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 between objects or open air. Wha

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 with the drivers.- We changed the interrupt to active high by changing the value of register 0x30 in VL53L4CD_DEFAULT_CONFIGURATION (VL53L4CD_api.c)- We se

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 SENSOR AND STARTED GETTING SINGLE MEASUREMENTSeStatus =  0, Distance =  86 mm, Signal =  832 kcps/spad

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/VL53L5CXNUCLEO-F401RE    https://www.st.com/en/evaluation-tools/nucleo-f401re.htmlX-NUCLEO-53L5A1  https://www.st.com/en/evaluation-tools/x-nucleo-53l5a1.html I managed to get X_NUCLEO_53L5A1_HelloWorld.ino to work.But I can't do it on another PC. Both have the same environment.In the failure case, even  "Initialize... Please wait, it may take few seconds..." doesn't show up on SerialMonitor.Nothing shows up by pressing the reset button. Upload is successful.Basic exa

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(&(p_dev->platform), 0x000F, 0x40);HAL_Delay(5); //FDT NOV 2024: NEEDS A 1+MS DELAY HERE OR IT WILL WORK THE FIRST TIME BUT NOT AFTE

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 <VL53L0X.h> // Copy of the Pololu VL53L0X library is included. Acknowledgement

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 8chhttps://www.st.com/en/imaging-and-photonics-solutions/vl53l7cx.html 7cxhttps://www.st.com/en/imaging-and-photonics-solutions/vl53l7ch.html 7ch

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: FW initial boot status, Set by FW after completing initial coldboot."And as VL53L1X_api.h says:In the above-mentioned thread, John suggests:"I had problems with this register too. I think the documentation has it backwards. So boot, read the register quickly, see what it reads a few millisec later, then range. With a little luck it will go from 0 to 2 to 3 after ranging."I have done all of the above John said except ranging. This is my code (my code is located at the beginning of the FIRST thread of the program, so It is the first thing to be executed after the internal MCU initializations).These are the values of the five calls to "VL

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 and an LTC4316 I2C address translator in between the Pi and rangefinder, and the whole setup worked great.  Software was the&nbsp

Hi,I noticed that the number of spad used reduces as an object gets closer to VL53L4CD. I was thinking about using this to make my distance measurement better. It also helps me to detect if the object is moving much in the field of view as i noticed, once i move away from the field of view of sensor number of spad increases again. But this behaviour can only be observed below 20cm as after that the number of spad peaks. Is there anyway i can reconfigure the sensor to give me similar behaviour till 40cm?I realise that reducing the number of active SPADs could reduce accuracy, but I'm wondering if there’s a way to reconfigure the sensor to maintain a similar pattern at greater distances. I just want to test and see if i could find something interesting out of it.Regards,Kiran

Hello, I've previously posted asking about gesture and hand posture output and I've finally got an output from both of the model. The problem is the method of getting an output for gesture and hand posture is different. For gesture, I'm able to use GestureEVK software and achieve some results for gesture but for hand posture I'm only able to get an result through local terminal/Putty. Is it possible to integrate both of the processses to have them running on one program that can recognize both gesture and posture?Or is it possible that there are already methods of have gesture and hand posture running on one program?Any ideas or hint would be useful! Thank you! Emily   

I'm evaluating the VD55G0 sensor - using the cam-55g0 camera module and the STEVAL-EVK-U0I evalkit. Looking at the datasheet and other documentation (VD55G0 - Compact and high-sensitivity 0.38 megapixel monochrome global shutter image sensor - STMicroelectronics), there are mentions of binning, analog binning and digital binning  in various places. Binning and digital binning seem to refer to the same thing and can be set to 2x or 4x in the eval-kit software. But the analog binning, indicated to provide higher frame rates, is not described in any more detail than just the info under "features". My question is if this really is an analog binning that can be performed on the sensor (in my understanding that is commonly not a feature for CMOS sensors) - or if this refer to some other operation (subsampling, cropping etc)? If it really is an analog binning, are there any way to evaluate this mode using the evalkit with the promodule cameras? From the

Hello !If you don't mind, could you tell me about how to calculate human position (x,y,z) in STSW-IMG048?In 8x8 mode, I can get 64 values. I'm wondering about how to  calculate the position from the values.Any form of help is appreciated. Thank you!

In vl53lx_platform.c  functions VL53LX_WriteMulti() and VL53LX_ReadMulti()  are taking care of the VL53LX_COMMS_CHUNK_SIZE which was set to 56.So, data is send in telegram chunks if length exceeds this definition.I'm wondering if this is due to VL53LX chip limitations or maybe the telegram length shouldn't  be too long for safe transmission or lack of transmission buffer size?

Hi, I am using a VD55G1 sensor with P-board to interface with Rpi 5. I am using Camera port #0 of Rpi. I downloaded the STSW-IMG506_V4L2, STSW-IMG506_LIPA and STSW-IMG506_LCAM. I followed the steps to install V4L2 driver from the "Linux Start Guide for ST BrightSense image sensors" document and updated the device tree to include pcb4189_vd55g1_cam0.dts, added the same to config.txt as well. I upgraded the system to support latest version of libcamera packahe and extracted both LIPA and LCAM .deb files, but rpicamera-hello or libcamera-hello doesn't detect camera. At the same time I found the libcamera version to get messed up upon extracting the LIPA and LCAM libraries (refer the attached image before and after installing the package). Before extracting the LIPA and LCAM library filesAfter extracting the LIPA and LCAM library filesDebugging steps:I did not find any external hardware from the /dev/ though I interfaced a FPC cable with P-board and promodule with

When i measure my distance in 4x4 i don't have any issues at all. But I need to change it to 8x8 for my project.To my knowledge you only need to change the resolution with vl53l5cx_set_resolution() to 8x8 and adjust the frequency accordingly. I have checked if my sensor is measuring with my webcam and it is a solid red light so not blinking or anything. And when i check the output it gives me this: Initializeddata not ready??data not ready??data not ready??data not ready??data not ready??data not ready??data not ready??data not ready??data not ready??Status ranging: 1Error retrieving ranging data on device 0.======== Device 0 ========23, 33, 28, 20, 17, 14, 12, 6,24, 33, 701, 26, 19, 15, 11, 10,21, 31, 32, 25, 21, 17, 13, 12,23, 31, 34, 30, 24, 18, 15, 13,828, 27, 33, 33, 0, 22, 0, 0,0, 0, 0, 0, 0, 0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0,0, 0, 0, 0, 0, 0, 0, 0,BrakingError while checking for data ready on device 0.data not ready??Error while checking for data ready on device 0.data no