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.

Sign up for GitHub

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

Jump to bottom

Add timeout on receiving first robot state in ros_control codepaths #227

Open
gavanderhoorn opened this issue Nov 5, 2018 · 0 comments
Open

Add timeout on receiving first robot state in ros_control codepaths #227

gavanderhoorn opened this issue Nov 5, 2018 · 0 comments
Labels
enhancement help wanted kinetic Issues with the refactor in Kinetic

Comments

@gavanderhoorn
Copy link
Member

In #213 a robot_state_received_ was added as a guard against running the active controller against uninitialised state.

In essence, no controller is executed (and thus no control effected) until after the first state packet has been deserialised and run through the pipeline.

This nicely resolves #206, but it would be nice if we could warn users about situations where -- for some reason -- robot state is not received for some time when it should.
@gavanderhoorn gavanderhoorn added enhancement help wanted kinetic Issues with the refactor in Kinetic labels Nov 5, 2018
@gavanderhoorn gavanderhoorn added the wrid19 World ROS-Industrial Day 2019 label Jun 29, 2019
@fmauch fmauch mentioned this issue Jul 2, 2019
Closed
@gavanderhoorn gavanderhoorn removed the wrid19 World ROS-Industrial Day 2019 label Jul 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement help wanted kinetic Issues with the refactor in Kinetic
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fmauch @gavanderhoorn