Changed timing of actuator_controls_0 message from rover_pos_control #12519
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.
Describe problem solved by the proposed pull request
The
rover_pos_control
module was publishingactuator_controls_0
messages at a constant 250Hz, independent of any polling on any other UOrb topic. This was causing issues with Gazebo where it would get slightly out of sync with sensor readings. Closes #12490Test data / coverage
Ran several missions in Gazebo.
Describe your preferred solution
Changed
rover_pos_control
to poll onsensor_combined
to time the publication ofactuator_controls_0
. This sensor data is not actually used, it is only necessary for timing.