Imaging (sensors)

According to api Manuals, for VL53L0CX and VL53L1CX, Offset calibration should be performed before Crosstalk calibration, but for newer ToF sensors, such as VL53L3CX or VL53L1CB, it's said Crosstalk calibration should take place before Offset calibration. Are alll these guides correct? Or order guide in earlier api manuals should be revised to be consistent with newer products?

Hi, I'd like to know what is the minimum size or gap between 2 objects the sensor is able to detect ? My first test shows a surface of 600 cm² seems to be the minimum, i.e a "hole" square of 25 cm x 25 cm or a rectangle of 20 x 30 cm.When I do the math for the size of the 8x8 zone the result is a resolution of 15x15 cm. Why is there this important diffference ? Any parameter to setup ? Thanks

Have a question about VL53L1XIn the vl53l1x.pdf, it says on page 23/35 that"The default driver mode is 1V8. 2V8 mode is programmable using device settings loaded by the driver. For more details please refer to the VL53L1X API user manual (UM2356)"Want to know if the tof sensor, P/N, VL53L1CXV0FY/1 can be integrated to a custom board operating at 3v3.VL53L1CXV0FY/1 has operating voltage range of 2v8 to 3v6 per the manual. My intention is to use it in a single power supply, 3v3.What confuses me,is that,the VL53L1CXV0FY/1 has a profile set for 1v8 out of the factory, if I understand it correctly. 2v8 is programmable that support 3v3, but how? Do I have to re-flow VL53L1CXV0FY/1 firstly to a custom PCB & program it to 2v8, before re-flow it on to the final PCB, that has only 3v3 ? I could not find any more insight in UM2356.Thank you.

..

Good day, Is there currently any support for gesture recognition with the VL53L5CX ToF sensors, as shown in the Video "Gesture Tracking on Thermostat with VL53L5CX"?I could not manage to find any examples or information about how to implement this.Regards, DMeie.2

..

We are trying to use 3 number of VL53L4CD on one I2C line... is it possible?Sensor used: VL53L4CD we are trying to do this. using Xshut pin, but when we change voltage level on xshut pin, we need to reinitiate sensor for measuring sensor.can someone guide how to readdress this considering 3 sensors are on same line.

HiDo we need to calibrate every sensor in the production line, or we just need to make the calibration once to the standard product?Sensor: VL53L1X.Thanks

Hi,I need to get distances of objects located between 1.40 m and 2.50 m away from the sensor (cardboard or film-wrapped cardboard) in various light light conditions. 8x8 ranging continuously @ 2Hz. Some of measured distances (real world) are over the typical and minimum values in table 18, page 20. Does it mean they are not trustable ?How to interpret terms "typical" and "minimum" for the maximum range capabilities ?Thanks.

I can't connect to the VL53L5CX-SATEL board & STM32F401 (Nucleo-64)  in order to run the "VL53L5CX GUI Software". I think I installed the correct drivers. See "Device Manager Driver" screenshot. Does this look correct?In the About tab I click Refresh List but nothing appears. See "GUI About Tab" screenshot. I'm using the en.Quick_Start_Guide_X-NUCLEO-53L5A1.pdf. I've tried two different computers, tried different USB ports. What else should I check?I installed stlink_winusb_install.bat in administrator mode and did this: "In case of issue, it's also possible to run (as administrator):  - dpinst_amd64.exe on 64 bits machines"I have a Dell Precision 7510 running Win 10.What am I doing wrong?

Hi, I've been testing out the VL53L4CD and it's working really well so far, however I'm having a bit of an issue at one specific short range point. Everything works smoothly until I get to about 15 mm above the sensor, then the numbers jump up erratically, intermittently, and actually start to decrease the closer I get towards the 0 mm mark (when my hand completely covers the sensor). I've attached a screenshot of my serial monitor readings when my hand is hovering roughly 15mm above the sensor (with the values in my code constrained between min 200 kcps and max 10,000 kcps), and as you can see it jumps to 10,000 sporadically. Basically I just want a gradual increase and hit the max threshold (i.e. 10,000 or whatever I set it to) when my hand is physically touching the sensor.I suspected this might have something to do with either the "sigma threshold" or the "signal threshold" described on page 9 of the PDF attached (section 3.3), because a default value of 15mm is mentioned there, ho

Dear ST and Team,Am using ST's VL53L3CX STEL Board for water level sensing project prototyping. I Have Queries following belowis VL53L3CX is suitable for water level sensing ?do we need any calibration for accuracy ?i have generated code simple raging application using STCubeMx (Using STM32F103RCT6 Controller ). is simple ranging application can also measure water level ?While detecting object am getting almost better accuracy distance, while distance is increasing of object from accuracy is becoming low. +- 20mm is for upto 1000 mm target is getting. how to increase the accuracy ?While testing for Water detection, Some times distance is showing totally wrong and some times distance accuracy is +- 10mm for 150mm target.i have tested in multiple containers like Glass, Jug and Bucket. but not able to read correct values.am using some cables for interfacing the VL53L3Cx. attaching the pic. Does it anything wrong using some length cable ?I am sharing some pics for your reference. Plea

Hi all,I'm trying to get the GUI to perform Xtalk calibration, but every attempt so far returns the error 'Error from ULD: XTalk error, invalid parameter provided'. I've tried altering the default parameters in various combinations but no luck so far.Does anyone have a clue as to what I'm missing here?Arie

I've seen a brief data sheet about VL53L8CA, but it is currently not available. I'd like to know when am I able to buy one.

..

I am on a robotic forum where we have been studying using this VL53L5CX for robotic vision, mapping and SLAM for the last two months. We are on page 12 of this thread: "<link provided if requested and I'm permitted>"The problem we have run into concerns the distance readings we're getting out of it. The problem is explained in detail in the second half of this post "<link provided if requested and I'm permitted>" with pictures and previous posts to that thread give detailed output from the sensor.Since I am new to this forum and can't provide the links, I'll summarize the problem here:We have the sensor square-on to a wall 1000 mm away.The wall is house-painted whiteThe ambient lighting is very low (barely readable)Since the FoV angle from corner to corner is ~64 degrees, the corner distances should follow standard Trigonometry theory and be further away than the central pixels.Theory says, if the center is 1000 mm away, the distance to the center of all four corner pixels

And what does it do?

Can we use VL6180X to measure distance of an object through an optical medium (lens assembly). Can we achieve good accuracy?

..

Hi,I have sensor VL53L5 and MCU STM32H753ZI. I want to use the gesture library(STSW-IMG035. Turnkey gesture recognition solution based on VL53L5CX multizone Time-of-Flight ranging sensor), but I found in it that there is a compiled driver (libGesturesMZ.a) for Cortex M0+ and M4. Do you have a driver (libGesturesMZ.a for Cortex M7? or can be used from Cortex M4?

..

Hi,The vl53l5cx_api.h file contains information about interesting functions to enable or disable the internal VCSEL charge pump:/** * @brief This function is used to disable the VCSEL charge pump * This optimizes the power consumption of the device * To be used only if AVDD = 3.3V * @param (VL53L5CX_Configuration) *p_dev : VL53L5CX configuration structure. */ uint8_t vl53l5cx_enable_internal_cp( VL53L5CX_Configuration *p_dev);     /** * @brief This function is used to disable the VCSEL charge pump * This optimizes the power consumption of the device * To be used only if AVDD = 3.3V * @param (VL53L5CX_Configuration) *p_dev : VL53L5CX configuration structure. */ uint8_t vl53l5cx_disable_internal_cp( VL53L5CX_Configuration *p_dev);Unfortunately, I cannot find other usefull information about this topic in the documentation.What is the default state of the internal charge pump after initialization (ULD ver. 1.3.4)?What is the expected power consumption delta when ch

Hi, I am using a VL53L1X sensor and using the LITE driver version 1.0.2. I am finding a condition where in a random situations the sensor is returning 0 in the range measurement while looking at a long distance <4m. This distance will continue returning the same value after reaching that condition.After trying to change some of the configurations I discovered that the only way to recover the device is to switch from long distance mode to short distance mode, and back to long distance mode. My best guess is that at some point there was an unwrap status which was not recovered. Unfortunately I don't have good means to recover the status information from that code. After taking a more detailed look at the LITE driver and Full driver documentation, I found that the later presents some other status not directly documented on the LITE driver. Nonetheless, in the cases of errors, I could not find good documentation on what would cause the status error, nor if there is any means to recover

Hi,I am using VL53L1X in our cortex-m33 platform.Do you have any library for our cortex-m33 based on your VL53L1X tof sensor for people counting. If yes, please share the library. If the library is not available for our platform, what is the challenge to implement the ppl counting logic in our platform.Regards,Anil

Hi,I would need a technical information about VL53L5CX Ultra Lite Driver (ULD).Specifically, what is the format of the reflectance value returned by the vl53l5cx_get_ranging_data() function?I am supposing that the format is a percent value expressed as a decimal number limited to the range [0, 100].However, in particular conditions, with high reflectivity targets, it happens that values above 100 (i.e. 127) are returned by the above function. How could be explained and handled correctly?Furthermore, in vl53l5cx_api.c, the reflectance value is halved before being returned:#ifndef VL53L5CX_DISABLE_REFLECTANCE_PERCENT p_results->reflectance[i] /= (uint8_t)2; #endifThis change appears to have been introduced from the release v.1.3.0.Version : 1.3.0 Date : 02/11/2022 Comments : - Corrected reflectance format (output divided by /2 vs previous driver version) ...Could you elaborate on the subject?Thank you