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 model parameters #8

Open
ZhiangChen opened this issue Sep 9, 2022 · 1 comment
Open

robot model parameters #8

ZhiangChen opened this issue Sep 9, 2022 · 1 comment

Comments

@ZhiangChen
Copy link
Member

when spawning a robot model using Bullet physics engine in Gazebo, it has an error.
[ERROR] [1662689537.978797450, 0.040000000]: ROS get_physics_properties service call does not yet support physics engine [bullet].

Thus, the robot model uses the default friction coefficient of 1. Even though you modify the value in the robot URDF model, the physics parameter can't be passed to Bullet.

One solution is to first load the robot model in Gazebo and modify the friction coefficient using model edit. Then save the model to your gazebo model path.

Next, you need to follow the steps below to load the robot and controller.

  1. roslaunch the robot model with robot_description, regardless of the wrong or ignored friction coefficient.
roslaunch pbr_gazebo prismatic_large_box.launch 
  1. delete the robot model in gazebo
  2. insert the saved model with correct friction coefficient. Now you can check the friction coefficient in Gazebo
  3. roslaunch the controller
roslaunch pbr_gazebo prismatic_controller_large_box.launch
  1. rosrun the controller server and client
rosrun pbr_gazebo pulse_motion_server.py
rosrun pbr_gazebo pulse_motion_smart_client.py
@ZhiangChen
Copy link
Member Author

this also applies to coefficient of restitution

@ZhiangChen ZhiangChen changed the title robot model friction robot model parameters Sep 9, 2022
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

1 participant