Remove concept of "fresh" from mount backends #31758
Open
+11
−46
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.
CaddX, XFRobot and the two storm32 gimbals all have code around not sending data if it isn't "fresh".
This really isn't required. The gimbals must be able to handle angle commands coming in at the same rate as neutral-or-retract-angles - that's how we point the gimbal somewhere!
If a gimbal can't handle the full rate we might send things in at then it should be throttle properly - but the fact they all work well with angle tangles means this is not a problem.
storm32-serial retains its "timeout" define as the device will only talk to us if spoken to.
Testing:
MNT1_RC_RATE)gimbal mode retract) in MAVProxy*(adjust parameter angles or just have it offset at an angle before this)gimbal mode neutral) in MAVProxy**Make sure your MAVProxy is running off master; I recently fixed MAVProxy's commanding of gimbals!