VL53L5CX: Info about target status [renewed]

[AlexCloned]

I am renewing this conversation because I had added this concern to a conversation with the same subject that was marked as solved. Originally posted by @MBela.3 .
I have not received a response. However, it is very important to me not only for my application with the VL53L5CX but for every forum member interested in these sensors.

UM2884-Rev 3, chapter 5.5 Results interpretation, shows in table 4 (list of available target status) a short description of the target status 0 to 13 and 255.

Do you have any additional information regarding target status codes? I am currently working with a fixture consisting of 3 VL53L5CX sensors at 8x8 resolution and a 15Hz sampling rate. We have a substantial amount of data, and we are encountering many target status codes that differ from the ideal code 5, with this deviation occurring at a rate of 80% under various real-world working conditions.

I have the feeling that we might be missing out on valuable measurements due to these target status codes. With a comprehensive explanation of these codes, particularly those that are not self-explanatory, we could make better sense of a significant amount of data. As we are in a stage previous to massive production of our product this could potentially lead to improvements in our measurement fixture and working conditions.

The sensor is indeed impressive!

Thank you.

[ramprakash08]

The VL53L5CX sensor uses target status codes to provide information about the status of a target. These codes range from 0 to 13 and 255, as described in UM2884-Rev 3, chapter 5.5 Results interpretation, table 4. Each code provides a short description of the target status.

As per the previous discussion in the community forum, status 14 is a new feature introduced in the latest version of the firmware. It indicates that if the target separation is too close, the 2nd target could be a false target.

For the other target status codes, unfortunately, there isn't a more detailed explanation available in the public documentation. However, it's important to note that these codes are designed to provide a general idea of the status of a target, and may not always provide a complete picture of the situation. Therefore, it's recommended to use these codes as a guide, but also to rely on other information and observations to understand the full context.

For example, if you're seeing a high rate of non-ideal codes under real-world conditions, it could be due to a variety of factors such as environmental conditions, sensor configuration, or the nature of the targets themselves. It might be beneficial to experiment with different configurations or conditions to see if this improves the rate of ideal codes.

[Anne BIGOT]

Thank you for your interest for our products and sorry for the delay to answer.

Ramprakash08 is right. The codes are designed to provide a general idea of the status of a target. Therefore, it's recommended to use these codes as a guide, but also to rely on other information and observations to understand the full context

As per your request, I reach your request internally to give more details on status code in a further version of the UM but meanwhile I will try to give more details in this forum by end of this week.

Regards

Anne

[AlexCloned]

Thank you for your response, @ramprakash08. I am taking all of this into consideration and completely agree. I'm also awaiting a response from ST regarding clarification, if possible, on every target status code.

[Anne BIGOT]

As per the promise, the question of giving more details on target status is still under discssion internally.
Sorry for the delay