Imaging (sensors)

When executing "vl53l0x_SingleRanging_Example" or "vl53l0x_SingleRanging_High_Accuracy_Example", the distance can be measured correctly, but when executing "vl53l0x_ContinuousRanging_Example", it cannot be measured.Is there somewhere I can check?Below is the log when running "vl53l0x_ContinuousRanging_Example".VL53L0X PAL Continuous Ranging exampleCall of VL53L0X_DataInitAPI Status: 0 : No ErrorVL53L0X_GetDeviceInfo:Device Name : VL53L0X ES1 or laterDevice Type : VL53L0XDevice ID : VL53L0CXV0DH/1$CProductRevisionMajor : 1ProductRevisionMinor : 1Call of VL53L0X_StaticInitAPI Status: 0 : No ErrorCall of VL53L0X_PerformRefCalibrationAPI Status: 0 : No ErrorCall of VL53L0X_PerformRefSpadManagementAPI Status: 0 : No ErrorCall of VL53L0X_SetDeviceModeAPI Status: 0 : No ErrorCall of VL53L0X_StartMeasurementAPI Status: 0 : No ErrorIn loop measurement 0: 0

I have a very simple question concerning the size of the zones and the field of view for (for example) the VL53L8CX sensor. which has a diagonal FoV of 65 degrees. Can anyone provide a simple answer to this question:If the sensor is 1 meter from the target, what size is each (8 x 8) zone at the target?I have tried to follow the app note and calculated 0.37 x 0.37 meter - but I have little faith in my calculation. Thanks

HI, i am studying how to controll vl6180 with a custom board which MCU is STM32L452CCU6. At the beginning , i tried to avoid implementing the api by changing register directly using i2c, however,0x018 is set to 0x2 or 0x0 both did not generate the raw value in 0x064. Therefore, i think there are more config i need to be made before the sensor start reading and an API is required . During searching in the internet, i only found STSW-IMG003 for VL6180X, can i use it for VL6180?Which example could i use just for 1 sensor read range?

Hey, I am using a customize board (MCU:STM32L452CCU6) to develop a gate checker with vl6180/V1 and cover glass with IR filter. Implemented a default value and setting ,the sensor and code works fine indoor. But in the outdoor condition under the sunlight, the sensor only shows 255. I read the datasheet, some setting could help me to overcome this situation, but I don't know which steps should i go first( crosstalk,threshold , convergence time or SNR?). So, which parameter should i deal with it first in order to solve this problem?

Hi, I would like to download older versions of the VL53L5CX gesture library (to be exact the 1.7 and 1.8 versions for cortex M4), but I'm only allowed to download the latest one (1.9). Is there any possibility to download these two versions?Regards.Stepan

Dear ST Engineers,I am planning to port this device driver to another 8 bit MCU:https://www.st.com/en/embedded-software/stsw-img023.htmlMy 8 bit MCU has I2C slave address range from 0x00 to 0x7F.However, hint of that ST driver code insists on using uint16_t as I2C address, for example, typedef struct { /* To be filled with customer's platform. At least an I2C address/descriptor * needs to be added */ /* Example for most standard platform : I2C address of sensor */ uint16_t address; } VL53L5CX_Platform; How do I reconcile this conflict?  Or do I misunderstand something about ARM 32 bit architect?Please give your valuable opinions.  :cowboy_hat_face:

Hello,I am developing a system using VL53L1X.I have read UM2356 (VL53L1X API user manual).I would like to know the background of the recommended conditions for the offset calibration procedure Chart distance: 140mm.Is it a peculiar point that Chart distance: 140mm is characteristic of the sensor?If anyone knows the effects of calibrating at other than 140mm, it would be helpful if you could let me know. Best regards.

In my product I use the VL53L1X sensor for more than 2 years. But the last 50 sensors I bought had a problem. The measurement is too incorrect and the peak_signal_count_rate_MCPS and ambient_count_rate_MCPS parameters are too low. I purchased sensors from two different vendors and both had the same problem. The image below shows my test device. The first two lines of the display show data from the new sensor with a problem. And the last two lines show data from a sensor that is working correctly, used as a reference. My doubts are:Have there been any firmware updates recently?As I import this component, could the customs X-ray have damaged the sensor?

I’ve used the VL53L1X and found it to be very reliable, I obtained a few VL53L5CX the (Sparkfun Breakout version) for assessment to a particular project.A similar issue has been logged on the Spark fun forum a couple of years ago without any resolution.I’m not sure if this issue has been resolved with later firmware and I’m not sure if the issue is with the VL53L5CX firmware or the Spark fun Library? (but there hasn't been an update to the Sparkfun Lib in quite some time).I don’t know of any other mulit-zoned ToF sensors like the VL53L5CX, so I really want to use this sensor for the project.The locations that require this sensor, are large rooms, 4 meters x 4 meters or grater , the sensor would be mounted in an enclosure and sited to a fixed location at low level looking into the room.when the sensor is first initialized the data returned for all zones that are out of range (greater than the sensors max read range

..

Is it possible to have a computer ask the sensor for only certain pixels when it is needed?From what is posted by your vendor Sparkfun, the data array can be 4x4 or 8x8, and repetition rate can be 1, 15, or 60Hz. Are these options set by the approximately 90 KB of firmware sent to the sensor on power up? Are details of the firmware available?Thanks

I ordered / received the P-NUCLEO-53L8A1 development kit to evaluate the VL53L8CX ToF sensor.It includes:X-NUCLEO-53L8A1 Time-of-Flight expansion board based on the VL53L8series for STM32 Nucleo• NUCLEO-F401RE development boardCould someone possibly point me to a quick-start guide? Thanks in advance!   

Hello I want to add a glass to my VL53L1X ToF sensor . How should I calibrate for using with glass?I tried to calibrate with the help of the um2510 pdf (I used VL53L1X_CalibrateOffset and VL53L1X_CalibrateXtalk respectively).  After the calibration when I try to move the object away, the result distance is decreasing.  I dont get what the problem is but when I remove the glass ıt gives the correct result.Thanks for your helps.

For a project i need to add the sensor VL53L0X to a program, i've found the Library for the sensor ( STSW-IMG005 ) i can compil the program with no error , but don't work , i'm pretty sure it's from the adaptation from the library to my STM32, if you have a similar case or can help me it will be appreciated !

I'M JUST TRYING TO MEASURE DISTANCE USING VL6180X SENSOR WITH STM32 BUT I COULDN'T SUCCEED.CHECKED THE I2C DEV ADDRESS(0X29),VL6180 SENSOR ID(0XB4).AND JUST USING A FEW FUNCTIONS FROM API LIKE INIT, PREPARE, AND POLL MEASUREMENT. I CANN'T IDENTIFY WHERE THE PROBLEM IS. NEED HELP

Please tell me about "5.2.4 Range accuracy in continuous mode" described in the VL53L5CX data sheet.Is the listed precision (error) value the precision (error) value due to individual differences ?Or does that precision (error) value mean the range of variation for the same individual ?

When I use vl53l5cx_get_target_order, it returns 2.I assume there are only two values (1 & 2). Does 2 = CLOSEST or Strongest?Thanks.Giri

I am encountering a strange problem on the VL53L5CX sensor. Here is the rundown of my setup:3 sensorseach gets initialised and new i2c address is set so they can run simultaneouslyturn all sensors on and wait for external inputThe external input is simply an interrupt from a pin (yes I do block interrupt calls while this process is running so theres no overlap). Upon this interrupt being fired the following occurs:Each sensor sent the start_ranging() commandeach sensor takes 10 measurements (this is done by looping over each sensor and calling the check_ranging_data() command and then get_ranging_data() )after 10 measurements each sensor is sent the stop_ranging() commandThis is where the problem occurs, the first 2 sensors have no problem stopping, then the final sensor seems to timeout during this function call and returns an error 49 (decimal). What would cause the stop_ranging() command

..

hello.I am trying to measure the level of cooking oil in a metal container using the VL53L0X chip.The length and width of the metal container are 25 cm and the height is 35 cm.Please refer to the picture for detailed measurement environment. However, the lower the level of cooking oil, the more inaccurate the sensor's measurement.In other words, as the distance between the sensor and cooking oil increases, the error in the value increases.In order to solve this problem, I tried to correct the value by measuring the error range by height, but it is failing to determine the range that matches greatly.Do you know why this situation occurs? Or do yo

For Using VL53L1CX Sensor on PIC24 Controller with Specific Data Sheet(VL53L1CX).But there is no details about registers. how can get Details of Registers ?

Hello. I am seeking to perform a series of tests to demonstrate the effect of enabling/disabling the cross-talk compensation on the VL6180x ToF sensor. For some context, I'll be setting targets of different reflectance across different distances and taking measurements for insight on our application of the sensors.The datasheet suggests that enabling cross-talk compensation is simply performing the cross-talk calibration procedure to find the compensation factor, then writing that value to the SYSRANGE__CROSSTALK_COMPENSATION_RATE register (in 9.7 format). However, if I decide to 'disable' the compensation, is it as simple as writing to the SYSRANGE__CROSSTALK_COMPENSATION_RATE register 0? Does it require the sensor to reset? It's implied that after a power cycle the sensor loses its internal compensation value, but I can't find anything related in the datasheet. Any guidance would be appreciated

So from my understanding, after polling the sensor we can read directly from the RESULT__*** registers to reveal things such as distance, return rate, error code and such to view the results from the sensor range measurements. However, I've seen that when reading the RESULT__RANGE_RETURN_CONV_TIME register, it returns the same number, 16777215 microseconds (0x00FFFFFF). This number should be waaaay smaller that (below the Max_Convergence_Time threshold), and it should also change based on the target's distance and reflectance. Below I have a snippet of a terminal printing out values from a ToF sensor's measurements. I used my hand as a target and waved up and down perpendicular to the sensor in an attempt to see a change in the convergence time, but as we can see it stays the same.

Hello,Standard library for ToF sensors, as far as i know, works in blocking mode and it needs few seconds to initialize sensor and later on to gather all of 64 results. In my project I need to handle other process during this time and using DMA seams like proper move. Is there any alternative library that might solve my problem?

Hi, I would like to know if we can configure GPIO0 or GPIO1 as a logic output mode. In datasheet, we can configure in INT mode. But we need to clear the flag each time we have a value. So we have a wrong value during the clearing. I would like to configure the sensor for exemple 40cm detection, and have "1" when we detect somthing, and "0" when not without clearing or something else. Is that possible ?