cancel
Showing results for 
Search instead for 
Did you mean: 

Vl53L5CX - cause of stop_ranging() to fail

ALohr.1
Associate II

I am encountering a strange problem on the VL53L5CX sensor. Here is the rundown of my setup:

  • 3 sensors
  • each gets initialised and new i2c address is set so they can run simultaneously
  • turn all sensors on and wait for external input

The 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() command
  • each 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() command

This 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 to fail? How does it even fail? How is it more complicated than to just stop all ranging processes on the sensor MCU? Even if there was no ranging process running on the sensor, the stop_ranging() command shouldn't fail - because it would simply stop what's already stopped. Is there something I'm missing here?

Now that error code might not be exactly right as it changes when the I2C bus has an error. But I'm inclined to believe the I2C bus is fine due to the fact it gets through the entire process before failing. The final call to stop_ranging() on the 3rd sensor is literally the last step.

1 ACCEPTED SOLUTION

Accepted Solutions

I have downloaded the latest driver and have not encountered this issue yet. At this stage I can say it is fixed, however I will update this post should it happen again.

View solution in original post

4 REPLIES 4
Anne BIGOT
ST Employee

Hello

The issue has been raised internally. We will shortly upload a new version of the driver.

Thank you for your feedback,

Anne


Our community relies on fruitful exchanges and good quality content. You can thank and reward helpful and positive contributions by marking them as 'Accept as Solution'. When marking a solution, make sure it answers your original question or issue that you raised.

ST Employees that act as moderators have the right to accept the solution, judging by their expertise. This helps other community members identify useful discussions and refrain from raising the same question. If you notice any false behavior or abuse of the action, do not hesitate to 'Report Inappropriate Content'

any update on this issue?

The new driver is curently under test.

Thank you for your patience


Our community relies on fruitful exchanges and good quality content. You can thank and reward helpful and positive contributions by marking them as 'Accept as Solution'. When marking a solution, make sure it answers your original question or issue that you raised.

ST Employees that act as moderators have the right to accept the solution, judging by their expertise. This helps other community members identify useful discussions and refrain from raising the same question. If you notice any false behavior or abuse of the action, do not hesitate to 'Report Inappropriate Content'

I have downloaded the latest driver and have not encountered this issue yet. At this stage I can say it is fixed, however I will update this post should it happen again.