Imaging (sensors)

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

Hi, I would like to know if VL53L5CX emits only signals at this wavelength 940nm or from 900nm to 940 nm, because when I put the sensor in front of a lidar using 905nm, it is clear that the lidar picks up the interference signal from VL53L5CX. If so, how can I remove/reduce the Interference to Lidar when I use VL53L5CX?Thanks,Wayne

I am using a VL6180x with an Atmega8a in a lower-power application. The Atmega8a runs at a clock frequency of 1 MHz. After struggling for a few weeks to get the sensor working, I discovered an issue with the VL6180x. After writing 0x01 to register 0x038, to initiate a single-shot measurement, the value of register 0x04F remained 0 forever.I then switched from the Atmega8a to an ESP32 and the problem was solved. I then discovered that the problem reappeared when I set the SPI clock speed on the ESP32 to less than 20kHz. Is this a known issue with the VL6180x?I then wrote the following inline assembler code that does bit-banging. The VL6180x now works fine with the Atmega8a.void startSingleShot(){ // SDA = PC4 // SCL = PC5 // Port C address = 0x15 __asm__ __volatile__( // Set pin PC4 as output "SBI 0x14, 4 \n\t" // Send start "CBI 0x15, 4 \n\t" // Take SDA low to indicate start "CBI 0x15, 5 \n\t" // Take SCL low // Send address "CBI 0x15, 4 \n\t" // bit 7 is low "SBI 0x15, 5

Dear Sir,We connect VL53L1X to our host that provide 3.3V VDDIO. We will use VL53L1X ULD API as driver for our system. By check VL53L1X ULD API code, I can not find code about setting power mode to 2V8. Would you like to give any information for this question?I wonder if VL53L1X may be broken, when a 3.3V power is given before software initialization.The datasheet say the default power mode is 1V8.best regardsDai Sai

We use VL53L1X for our product development. Based on the datasheet, the typical operating condition for AVDD is 2.8V. I wonder if we can use a 3.2V for AVDD? If 3.2Vis provided for AVDD, is there any problem that may affect the performance of VL53L1X?best regardsDai Sai

Dear Sir,We are going to port VL53L1X API driver to our threadX environment.We download the en.STSW-IMG007.zip and a document stsw-img007.pdf.The document of API described that there are Api, ApiExample and doc in this package, but there are only Api and Doc folder in this package. I think the ApiExample is very important to understand how to use API driver.Would you like me how to get the ApiExample?best regardDai Sai

Dear Sirs, I have some problems with VL53L1 and VL53L1X sensors which i'm using in my project.Now i'm trying to figure out how to switch them to different modes and apply different settings in accordance with API manuals and datasheets. I'm also using STM32F3DISCOVERY board to control sensors.After i configured I2C bus and other stuff in CubeMX, i included driver files using this instruction: https://forum.digikey.com/t/adding-the-vl53l1x-driver-to-an-stm32cube-project/13276After that i'm able to receive range data in single ranging mode for both sensors (VL53L1 and VL53L1X) with the same code. I'm sending single range data via UART and it's correct.After that i've tried to set my sensors in threshold mode (Autonomous mode for VL53L1) and nothing happened. I used UM2356 API Manual for VL53L1X (and also manual for VL54L1). Both sensors still works in signle ranging mode. Code example in the attachment.Checking the status of the sensor pins with oscilloscope showed that I2C is working (I

..

Our products integrate the above PNs and we would need these documents in order to submit them to the cerification laboratory.As reported in the datasheet both ToF sensors are "designed to remain within Class 1 laser safety limits under all reasonably foreseeable conditions including single faults in compliance with IEC 60825-1: 2014 (third edition)."  Thank you

I'm looking at the I2C spew from a VL53L5C, and it appears to be values for each of 64 zones. Data for a particular zone starts with Z_______ where the blank is the zone number. But instead of starting with Z 0 to Z3F (0 to 64) it goes from ZFFFFFFC to Z3C ( -4 to 60). Is this how it should be? or does this indicate something wrong? Is the format of the I2C spew documented somewhere or do I go fishing in the ULD source code to figure it out? Thanks!

Identifying TOF chips in a system... Is there a way to determine what chips are attached to a board? We would like to support multiple TOF parts, but need to know what parts are attached to the I2C bus before writing to them.

Hi there,Following this topic, I've made a box out of black paper, perhaps it work for calibrating xTalk.We couldn't get the customized paper, but here's the box with side's distance = 25cm.    The results of both offset and xTalk are inconsistent, given I'm ranging at night with room's lights off.Any suggestion to improve the setup to accurately perform both offset and xTalk?Best Regards,Hamza Hajeir

The software driver VL53L1X full driver (STSW-IMG007) doesn't have data structure to support multirange data. Any idea if there are any drivers which supports this? Also are there any specific drivers for VL53L1CB? Any support is really helpful. (I have seen may example program for development boards but I'm looking for a custom board implementation)Thank you

I would like to make a gesture recognition to be less sensitive for my application. I know that I am able to change parameters like GW_MIN_SPEED_X_MM_S, GW_MIN_VX_ON_VY, etc, but I am not exactly sure which parameters to change and how much I need to change them in order to get desired result.

Hello, I'm currently using ToF sensor with Particle Tracker SoM board. I took the driver from VL53L1CB_BareDriver bare driver and ported it to the Tracker SoM. I have followed the same APIs as the example code but the sensor doesn't complete measurement (or generate interrupt) but the same software works fine on STM32 Nucleo board. I tried debugging with logic analyzer and I found during "VL53L1_DataInit(Dev_st)" the sensor I2C response is different compared to the STM32. Any help would be really valued.Thank you

Hi ST Team,I just integrated ULD driver of VL53L1X but it keeps returning range status: 4. What could be the problem?Settings:Timing: 100Inter Measurement: 100Distance Mode: ShortROI: 16x16Signal: Default ( 1026 something )Sigma: 90The I2C communication is tested to be working correctly and I’m successfully able to get all the reference register values. I don’t know why it keeps returning range status 4.

I'm using 8 sensors to detect the object position.This image is the part of them. The result of detecting is like the attached video.It's the capture video of my application. It visualizes the angle and distance of 2 sensors.It only shows 2nd row 8 zones in 8x8 zones. 2nd row 8 sensor x 2 sensor = 16 zones.So it's showing the detecting result of 16 zones.I don't know the reason of ghost object presence. (small red triangle in the video)If it's influenced by the ambient light, why does it appear in only specific zones?-----Finally, I need to position the sensors facing together to get the accurate position data.As you see, the sensors are under the light. And the light facing angles are different per each zone.Do I have to calibrate regarding these facing angles for each sensor zone?

HiI'm getting range status 6 while I'm reading the sensor, which corresponds to (No Update) Status.Test code (kept the necessary debugging prints):int16_t getDistance(void) { int status = VL53L1_StartMeasurement(Dev); uint8_t firstTimeInterrupt = 1; static VL53L1_RangingMeasurementData_t RangingData; do /* interrupt mode */ { __WFI(); // SENSOR_DEBUGF("got an interrupt,IntCount=%d\n", IntCount)); if (IntCount != 0) { // Is this necessary ? >> yes. IntCount = 0; if (firstTimeInterrupt == 0) { status = VL53L1_GetRangingMeasurementData(Dev, &RangingData); if (status == 0) { Serial.printf("Status:%d\tD=%d\tSignalC=%u\tAmbientC=%u\n", RangingData.RangeStatus, RangingData.RangeMilliMeter, RangingData.SignalRateRtnMegaCps / 65536.0, RangingData.AmbientRateRtnMegaCps / 65336.0); } status = VL53L1_ClearInterruptAndStartMeasurement(Dev); return RangingData.RangeMilliMeter; } else { /* Must not read data at the first interrupt, must clear interrupt and start measu