-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Action call in a stage #601
Comments
Currently, MTC doesn't allow for running code during task execution: it is primarily a framework planning trajectories. Side-effects cannot be transmitted to the |
I have a vacuum gripper and I'd like to call a ros service to turn on/off the vacuum gripper during execution. From the sounds of it, MTC doesn't support calling the service at the appropriate point during the execution? Are there any workarounds for using MTC with a vacuum gripper? Thanks |
Yes, that's currently not supported as the MTC node just sends the planned trajectory for execution to the main |
Thanks for the quick reply. As a horrible horrible workaround, what about having a fake gripper joint that MTC activates as normal and then the gripper node subscribes to the state of the fake gripper joint to turn the vac on and off. |
An approach that works is to execute the sub-trajectories up to the point where you need to call the gripper service, and then execute the remaining sub-trajectories afterward. Yes, its a workaround, but it fit my needs |
Both of these approaches will work. |
Hi, I want to run a custom stage called attach object which runs things externally to MTC/Move it.
So I want to run this action call when task is being executed and robot is in the correct position, but when I add this stage into MTC (the stage is inherited from PropogatingForward stage), in the task.plan() stage it is being executed and the rest of my stack fails since robot is not in the correct position.
How do I add the constraint of only running code in the custom stage during task.execute() ?
The text was updated successfully, but these errors were encountered: