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
However, as these settings are only passed to pipeline planners, they will not become effective for the CartesianPath planner!
So basically, the max Cartesian speed parameter can be added to the PipelinePlanner straight away and all standard velocity parameters could be added to the other solvers as well. Adding the EEF Cartesian velocity to CartesianPath is quite a good idea I think.
Also, I would provide a WrapperBase container that can adapt all three time parameters for arbitrary stages.
setMaxCartesianEndEffectorSpeed()
should soon be available through the MoveGroup interface. Which would be the proper way to get a similar functionality in e.g. a moveTo stage? Is there some plan on integrating this?This is following my issue on using MTC for welding #251
The text was updated successfully, but these errors were encountered: