ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
See this Answer:
https://answers.ros.org/question/9776/action-server-with-more-than-one-action/?answer=14266#post-id-14266
2 | No.2 Revision |
See this Answer: Answer:
https://answers.ros.org/question/9776/action-server-with-more-than-one-action/?answer=14266#post-id-14266
Summary (from linked Answer):
- There is no limit to how many action servers a node can have. It is perfectly possible to have one ROS node with multiple action servers; just pass them different topic names on creation.
- Each SimpleActionServer is limited to one goal; whenever there is a new incoming goal, the currently pending goal is cancelled. This behaviour is a simplification of the actionlib API which catches most use cases.
- If you want to have a more sophisticated handling of goals, you are free to do so using the actionlib API directly (without the SimpleActionServer). You could have multiple goals executing in parallel, queue goals, and generally do whatever you want.
3 | No.3 Revision |
See this Answer:
Summary (from linked Answer):
- There is no limit to how many action servers a node can have. It is perfectly possible to have one ROS node with multiple action servers; just pass them different topic names on creation.
- Each
SimpleActionServerSimpleActionServer
is limited to one goal; whenever there is a new incoming goal, the currently pending goal is cancelled. This behaviour is a simplification of theactionlibactionlib
API which catches most use cases.- If you want to have a more sophisticated handling of goals, you are free to do so using the actionlib API directly (without the
SimpleActionServer).SimpleActionServer
). You could have multiple goals executing in parallel, queue goals, and generally do whatever you want.