The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
FlexBE can do something like that.
| | 2 | No.2 Revision |
I don't have a satisfactory answer for controlling the node launch order. ROS1 wasn't really intended to be used that way.
A better ROS1 approach would be to launch a bunch of services or action services simultaneously. A state machine could be used to manage the way each node reacts to error signals (e.g. shut down node B node A emits X error msg). Two ROS packages for that are FlexBE and SMACH. FlexBE sounds a bit more sophisticated because you can do something like that.update it on the fly.
| | 3 | No.3 Revision |
I don't have a satisfactory answer for controlling the node launch order. ROS1 wasn't really intended to be used that way.
A better ROS1 approach would be to launch a bunch of services servers or action services servers simultaneously. A state machine could be used to manage the way each node reacts to error signals (e.g. shut down node B node A emits X error msg). Two ROS packages for that are FlexBE and SMACH. FlexBE sounds a bit more sophisticated because you can update it on the fly.
| | 4 | No.4 Revision |
I don't have a satisfactory answer for controlling the node launch order. ROS1 wasn't really intended to be used that way.
A better ROS1 approach would be to launch a bunch of servers or action servers simultaneously. A state machine could be used to manage the way each node reacts to error signals (e.g. shut down node B if node A emits X error msg). Two ROS packages for that are FlexBE and SMACH. FlexBE sounds a bit more sophisticated because you can update it on the fly.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
