Package gazebo-ros is not starting the service /spawn_entity #195
Comments
|
Could this be related to #175 ? Can you try to install |
|
Oh yes, that ibprotobuf==4.25.1 did the trick, and now I'm getting all of the expected gazebo_ros services working. Thank you very much @traversaro. Steps to solutionAs a reference, in case someone is having the same issue as me, I just ran: mamba install libprotobuf==4.25.1And now all the expected services are up and running: ❯ ros2 node info /gazebo
/gazebo
Subscribers:
/clock: rosgraph_msgs/msg/Clock
/parameter_events: rcl_interfaces/msg/ParameterEvent
Publishers:
/clock: rosgraph_msgs/msg/Clock
/parameter_events: rcl_interfaces/msg/ParameterEvent
/performance_metrics: gazebo_msgs/msg/PerformanceMetrics
/rosout: rcl_interfaces/msg/Log
Service Servers:
/apply_joint_effort: gazebo_msgs/srv/ApplyJointEffort
/apply_link_wrench: gazebo_msgs/srv/ApplyLinkWrench
/clear_joint_efforts: gazebo_msgs/srv/JointRequest
/clear_link_wrenches: gazebo_msgs/srv/LinkRequest
/delete_entity: gazebo_msgs/srv/DeleteEntity
/gazebo/describe_parameters: rcl_interfaces/srv/DescribeParameters
/gazebo/get_parameter_types: rcl_interfaces/srv/GetParameterTypes
/gazebo/get_parameters: rcl_interfaces/srv/GetParameters
/gazebo/list_parameters: rcl_interfaces/srv/ListParameters
/gazebo/set_parameters: rcl_interfaces/srv/SetParameters
/gazebo/set_parameters_atomically: rcl_interfaces/srv/SetParametersAtomically
/get_model_list: gazebo_msgs/srv/GetModelList
/pause_physics: std_srvs/srv/Empty
/reset_simulation: std_srvs/srv/Empty
/reset_world: std_srvs/srv/Empty
/spawn_entity: gazebo_msgs/srv/SpawnEntity
/unpause_physics: std_srvs/srv/Empty
Service Clients:
Action Servers:
Action Clients: |
|
Thanks for opening the issue! Unfortunately in robostack we can't fix wrong dependency information for old packages, and a proper fix will require a rebuild of all packages, that will take time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Can someone please help me to understand the following issue of why is /spawn_entity not started on my RoboStack env. (FYI The following commands work like charm in my Ubuntu PC)
I have installed gazebo classic through the following commands:
Run the robot_state_publisher:
❯ ros2 run robot_state_publisher robot_state_publisher --ros-args -p robot_description:="$(xacro /Users/danitruc/ros2_ws/src/my_robot_description/urdf/my_robot.urdf.xacro)"If I launch gazebo:
❯ ros2 launch gazebo_ros gazebo.launch.py [INFO] [launch]: All log files can be found below /Users/danitruc/.ros/log/2024-08-06-21-13-46-474094-trucs-mac.local-52784 [INFO] [launch]: Default logging verbosity is set to INFO [INFO] [gzserver-1]: process started with pid [52795] [INFO] [gzclient-2]: process started with pid [52796] [gzserver-1] [INFO] [1723000482.719135357] [gazebo_ros_node]: ROS was initialized without arguments.And I want to spawn my urdf in gazebo using the spawn script, however I'm getting this message:
If I check the service list:
And this is the gazebo_ros node info:
❯ ros2 node info /gazebo /gazebo Subscribers: /clock: rosgraph_msgs/msg/Clock /parameter_events: rcl_interfaces/msg/ParameterEvent Publishers: /parameter_events: rcl_interfaces/msg/ParameterEvent /rosout: rcl_interfaces/msg/Log Service Servers: /apply_joint_effort: gazebo_msgs/srv/ApplyJointEffort /apply_link_wrench: gazebo_msgs/srv/ApplyLinkWrench /clear_joint_efforts: gazebo_msgs/srv/JointRequest /clear_link_wrenches: gazebo_msgs/srv/LinkRequest /gazebo/describe_parameters: rcl_interfaces/srv/DescribeParameters /gazebo/get_parameter_types: rcl_interfaces/srv/GetParameterTypes /gazebo/get_parameters: rcl_interfaces/srv/GetParameters /gazebo/list_parameters: rcl_interfaces/srv/ListParameters /gazebo/set_parameters: rcl_interfaces/srv/SetParameters /gazebo/set_parameters_atomically: rcl_interfaces/srv/SetParametersAtomically Service Clients: Action Servers: Action Clients:Like you can see the /spawn_entity service is not listed anywhere. Am I missing something or this ros-humble-gazebo-ros package is missing something? Or maybe there's another way to use Gazebo?
Additional information
❯ mamba info mamba version : 1.5.8 active environment : ros2_env active env location : /Users/danitruc/miniforge3/envs/ros2_env shell level : 2 user config file : /Users/danitruc/.condarc populated config files : /Users/danitruc/miniforge3/.condarc /Users/danitruc/miniforge3/envs/ros2_env/.condarc conda version : 24.7.1 conda-build version : not installed python version : 3.10.14.final.0 solver : libmamba (default) virtual packages : __archspec=1=m2 __conda=24.7.1=0 __osx=14.5=0 __unix=0=0 base environment : /Users/danitruc/miniforge3 (writable) conda av data dir : /Users/danitruc/miniforge3/etc/conda conda av metadata url : None channel URLs : https://conda.anaconda.org/robostack-staging/osx-arm64 https://conda.anaconda.org/robostack-staging/noarch https://conda.anaconda.org/conda-forge/osx-arm64 https://conda.anaconda.org/conda-forge/noarch package cache : /Users/danitruc/miniforge3/pkgs /Users/danitruc/.conda/pkgs envs directories : /Users/danitruc/miniforge3/envs /Users/danitruc/.conda/envs platform : osx-arm64 user-agent : conda/24.7.1 requests/2.31.0 CPython/3.10.14 Darwin/23.5.0 OSX/14.5 solver/libmamba conda-libmamba-solver/24.1.0 libmambapy/1.5.8 UID:GID : 501:20 netrc file : None offline mode : FalseThe text was updated successfully, but these errors were encountered: