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 advice on settings or adjustments to improve detection, especially for reflective plastic balls passing through the sensor's field of view.
Based on the readings in distance_mm and target_status:
- Values 12-15 correspond to the desk near the sensor.
- Values 8-11 represent the next row of the 4x4 matrix.
- Values 0-7 accurately measure the red box at the correct distance.
However, I’m puzzled why values 8-11 are so unreliable. If the issue is related to the object being horizontal, it would make sense only if values 12-15 also returned 255.
Any insights would be appreciated.
Thank you,
Steve
