No UR5 model in gazebo #672
Comments
|
I have also encountered this problem. Have you resolved it？ |
|
This seems like some dependencies are missing, that is way too little output for the For reference, this is what a complete startup should look like: |
|
@RobertWilbrandt I install this package from the github repository ' https://github.com/fmauch/universal_robot ' |
|
Please do not use my fork directly. Please use either the released packages ( |
|
@fmauch |
|
@Gaben21 could you maybe provide more output? Did you delete the source-built version from your workspace and cleaned and built your workspace again? Otherwise it might still try to use your old source-built version. |
Hi fmauch ! I have tried to run the Gazebo version of repo and I am encountering same issue , i have tried the cloned version as well as the sudo apt-install version. Do you have any suggestions :
|
|
I've just verified that with a clean system things seem to be working. I created a Dockerfile: FROM ros:noetic
RUN addgroup --gid 1000 ros_user && \
adduser --uid 1000 --gid 1000 --home /home/ros_user --disabled-password --gecos "" ros_user
ARG DEBIAN_FRONTEND=noninteractive
RUN apt-get update && apt-get install -y ros-noetic-ur-gazebo
USER 1000:1000
ENV DISPLAY=:0Assuming here, that your host's user ID is 1000. then, building an image docker build -t ur_noetic .and starting it This brings me a working ur5 gazebo simulation. |
|
Thanks fmauch , turns out trying it on my another pc worked just fine for me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I roslaunch execute the following command ur_gazebo ur5_bringup.launch, Robotic arm model cannot be displayed in gazebo. But the output in the terminal seems normal.
SUMMARY
PARAMETERS
NODES
/
gazebo (gazebo_ros/gzserver)
gazebo_gui (gazebo_ros/gzclient)
robot_state_publisher (robot_state_publisher/robot_state_publisher)
ros_control_controller_spawner (controller_manager/spawner)
ros_control_stopped_spawner (controller_manager/spawner)
spawn_gazebo_model (gazebo_ros/spawn_model)
auto-starting new master
process[master]: started with pid [8558]
ROS_MASTER_URI=http://localhost:11311
setting /run_id to 6a1edc90-aa15-11ee-ac74-b727aa385e75
process[rosout-1]: started with pid [8568]
started core service [/rosout]
process[robot_state_publisher-2]: started with pid [8575]
process[gazebo-3]: started with pid [8576]
process[gazebo_gui-4]: started with pid [8580]
process[spawn_gazebo_model-5]: started with pid [8585]
process[ros_control_controller_spawner-6]: started with pid [8587]
process[ros_control_stopped_spawner-7]: started with pid [8592]
[ INFO] [1704271945.879807302]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1704271945.880620311]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
[ INFO] [1704271945.933302851]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1704271945.934067506]: waitForService: Service [/gazebo_gui/set_physics_properties] has not been advertised, waiting...
[ INFO] [1704271946.186580186, 0.001000000]: waitForService: Service [/gazebo/set_physics_properties] is now available.
[ INFO] [1704271946.199761296, 0.014000000]: Physics dynamic reconfigure ready.
The text was updated successfully, but these errors were encountered: