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

State interface velocity is wrong with position command interfaces #363

Open
christophfroehlich opened this issue Aug 6, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@christophfroehlich
Copy link
Contributor

State interface velocity is wrong with position command interfaces. Sometimes the value remains zero, sometimes it is a random value.

I guess that the physics engine just does not report a valid velocity, and we should warn users with this configuration, manually set the velocity zero, or even disallow it.

Steps to reproduce

Run a position-only demo

ros2 launch gazebo_ros2_control_demos cart_example_position.launch.py

launch a GUI, e.g, plotjuggler with this layout gazebo.pj.zip

ros2 run plotjuggler plotjuggler -l gazebo.xml

And send a command

ros2 topic pub --once /joint_trajectory_controller/joint_trajectory trajectory_msgs/msg/JointTrajectory "{joint_names: ['slider_to_cart'], points: [{positions: [-0.1], time_from_start: {sec: 5, nanosec: 0}}]}"

Versions

gazebo11 + tested on humble as well as rolling built from source.

@christophfroehlich christophfroehlich added the bug Something isn't working label Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant