-
Notifications
You must be signed in to change notification settings - Fork 18
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
Launch yarprobotinterface
manually instead of when spawning the robot in simulation
#193
Comments
Specifically for running the ROS2 nws a possibility is to run a separate This could introduce an overhead in performances (@elandini84 and @randaz81 know it better) cc @traversaro |
No, I think this is not a viable solution. The nws should run in the same process space of the device, inside gzserver. |
The best solution that comes to my mind is to use two different urdfs. ergocub.sh
ergocub_ros2.sh
|
Ideally it would be cool to be able to pass some kind of parameter from a Gazebo world, and then launch a different world based on the kind of ergocub you want to run. Would it be a suitable solution for you @SimoneMic ? How are you launching the simulation and/or adding the model to a running simulation? |
Hi @traversaro, I am launching the simulation using this command: |
Would it be a problem if you inserted the model directly in the world instead of drag and drop manually it? |
On my side I don't have any problems |
Cool, thanks! I try to understand how we can pass parameters to |
Done, a proposal is ready in robotology/gazebo-yarp-plugins#672 . |
Since there are two different versions of the "basic" configuration of the
yarprobotinterface
: namely ergocub.xml and ergocub_ros2.xml it would be nice to have the possibility to select which one to launch. Now, the robot interface it's launched when the robot spawns in simulation, via robot urdfThe main issue is that is not possible to launch the ROS2 remappers separately in a different file, at a different time.
For simplicity, I think that removing it from the URDF would be the easiest path. Then the user can launch whichever configuration suits him best via
yarprobotinterface --config <path/to/xml>
Would this be a feasible option?
I am also open to other solutions, if anything comes to mind.
Thank you
The text was updated successfully, but these errors were encountered: