You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been using the Fetch Gazebo model in a Ubuntu 18.04 machine with ROS Melodic on it (Gazebo 9). We notice that when we spawn the robot in Gazebo, it takes several tries before the robot starts properly (controller kicked in, arm in a collision-free pose). More often than not, 90% of the times, the controllers don't start at all and the arm falls all the way through the robot base, getting in a stuck pose
We eventually get the robot to load properly and use it in Gazebo, but this controllers-not-starting initial situation takes up too much time. Is this a normal occurrence or are there any ideas of why this might be happening?
The text was updated successfully, but these errors were encountered:
We have been using the Fetch Gazebo model in a Ubuntu 18.04 machine with ROS Melodic on it (Gazebo 9). We notice that when we spawn the robot in Gazebo, it takes several tries before the robot starts properly (controller kicked in, arm in a collision-free pose). More often than not, 90% of the times, the controllers don't start at all and the arm falls all the way through the robot base, getting in a stuck pose
We eventually get the robot to load properly and use it in Gazebo, but this controllers-not-starting initial situation takes up too much time. Is this a normal occurrence or are there any ideas of why this might be happening?
The text was updated successfully, but these errors were encountered: