You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the MotorCommandSet service immediately returns instead of blocking for the motor command (like set position) to be completed. This is problematic because setting the position of a motor will take an unknown amount of time to complete. So correctly returning a future and using calls to spin_until_future_complete on the client side would solve this issue. The current workaround is a separate watchdog topic for waiting until the position goal is reached, which is a bit overcomplicated and ugly.
KINDA FIXED:
MotorCommandSet for velocity and position SHOULD (untested) not return until they have completed their goal now
TODO:
fix ALL the nodes! start with digger, then drivetrain etc
Test this and make sure it is right, then rewrite all the other nodes so they rely on this (seperate task?)
The text was updated successfully, but these errors were encountered:
* Initial implement of Auto Dig action
Doesn't check if services are running before calling them
* Added comments to CalibrateFieldCoordinates.action
* Made auto_dig_server executable
* Revert the changes previously made to the skimmer node
* Added TODO comments to the skimmer node for #257
* Auto Format
* we don't want to commit these changes
* Deleted the old auto procedures
* Fixed auto_dig_action to match the format of auto_offload_action!
* Deleted some old unused variables
---------
Co-authored-by: Jonathan Blixt <[email protected]>
Currently, the MotorCommandSet service immediately returns instead of blocking for the motor command (like set position) to be completed. This is problematic because setting the position of a motor will take an unknown amount of time to complete. So correctly returning a future and using calls to spin_until_future_complete on the client side would solve this issue. The current workaround is a separate watchdog topic for waiting until the position goal is reached, which is a bit overcomplicated and ugly.
KINDA FIXED:
MotorCommandSet for velocity and position SHOULD (untested) not return until they have completed their goal now
TODO:
fix ALL the nodes! start with digger, then drivetrain etc
Test this and make sure it is right, then rewrite all the other nodes so they rely on this (seperate task?)
The text was updated successfully, but these errors were encountered: