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

[BUG]: Initial position not set when velocity controller is loaded #13

Open
evan-palmer opened this issue Jul 16, 2023 · 1 comment
Open
Labels
bug Something isn't working needs triage This issue needs triage support

Comments

@evan-palmer
Copy link
Collaborator

Issue Description

When attempting to set the initial position of the manipulator using the initial_value state interface param for ros2_control, the position is never set when a velocity controller is loaded. This error occurs only in simulation. I have reported the issue at gz_ros2_control as well (see here.

Steps to Reproduce

Launch angler with SITL and a controller with a velocity command interface:

ros2 launch angler_bringup angler.launch.py use_sim:=true

Observe the initial position was not set. 😢

Expected Behavior

The robot is set to the configured initial position.

Error Message

No response

Runtime Environment

This is run inside the development container with ROS Rolling and Gazebo Garden.

Additional Context

I implemented the initial_position_setter as a temporary hack for this while I wait for a response/fix.

@evan-palmer evan-palmer added bug Something isn't working high priority This is a high priority issue labels Jul 16, 2023
@evan-palmer evan-palmer added needs triage This issue needs triage support and removed high priority This is a high priority issue labels Aug 29, 2023
@evan-palmer
Copy link
Collaborator Author

The ros2_control folks have resolved this issue. Just need to do some additional testing with it and then I can remove the dependency on my fork

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage This issue needs triage support
Projects
None yet
Development

No branches or pull requests

1 participant