Skip to content
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

Robot is moving in Gazebo when no controller is started #26

Closed
smihael opened this issue Feb 18, 2021 · 1 comment
Closed

Robot is moving in Gazebo when no controller is started #26

smihael opened this issue Feb 18, 2021 · 1 comment

Comments

@smihael
Copy link
Contributor

smihael commented Feb 18, 2021

I want to use this package for testing my own ros_control plugins before running them on the real robot.

As the custom panda_gazebo_ros_control_plugin does not seem to provide a working EffortJointInterface (#25), I modified the panda_world.launch file so that

<param name="robot_description" command="$(find xacro)/xacro --inorder $(find franka_panda_description)/robots/panda_arm_hand.urdf.xacro load_gripper:=$(arg load_gripper) load_gazebo:=$(arg load_gazebo)"/>

becomes

<param name="robot_description" command="$(find xacro)/xacro --inorder $(find franka_panda_description)/robots/panda_arm_hand.urdf.xacro load_gripper:=$(arg load_gripper) load_gazebo:=$(arg load_gazebo) use_gazebo_control:=true"/>

Now instead of the custom panda_gazebo_ros_control_plugin the default gazebo control is loaded. The EffortJointInterface now works as expected, after Gazebo gets initialized and before the controller is loaded robot moves weirdly. Wouldn't it be expected that the robot stays still before any controller is initialized?

@justagist
Copy link
Owner

See #25 (comment) first.

The EffortJointInterface now works as expected, after Gazebo gets initialized and before the controller is loaded robot moves weirdly. Wouldn't it be expected that the robot stays still before any controller is initialized?

This could be because the simulator still depends heavily on franka_ros_interface which requires gazebo to use the custom PandaRobotHWSim hardware interface. By adding the flag use_gazebo_control:=true, this is disabled and may provide weird behaviour. You could instead use gazebo_panda which does not depend on franka_ros_interface at all, and uses the default gazebo hw interface.
Also, I have noticed that sometimes in gazebo, starting some controllers when launching any robot simulation seems to cause weird motion in the beginning, but this does not happen when switching to this controller after the simulator is fully loaded.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants