AP_RangeFinder: populate last_reading_ms in the backend for some sensors #27620
+4
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was noticed when trying to use Lightware LW20 I2C with AP_Periph. The Rangefinder support inside AP_Periph checks for the backends last update time so that we don't send duplicates:
https://github.com/ArduPilot/ardupilot/blob/master/Tools/AP_Periph/rangefinder.cpp#L67
I did a drive-through of all the other backend and it looks like only one other backend suffers from the issue.
This problem has been reported a few times in the past: https://discuss.ardupilot.org/t/ap-periph-not-working-with-lightwarei2c/95913