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

FPS won't initialise if a robot is collided #189

Closed
albireox opened this issue Oct 2, 2022 · 0 comments · Fixed by #190
Closed

FPS won't initialise if a robot is collided #189

albireox opened this issue Oct 2, 2022 · 0 comments · Fixed by #190
Assignees
@albireox
Labels
bug Something isn't working

Comments

@albireox
Copy link
Member

albireox commented Oct 2, 2022

When a robot is collided, with its firmware reporting a COLLISION_ALPHA or COLLISION_BETA flag, the FPS instance fails to initialise. jaeger won't run as an actor.
@albireox albireox added the bug Something isn't working label Oct 2, 2022
@albireox albireox self-assigned this Oct 2, 2022
@albireox albireox mentioned this issue Oct 2, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@albireox albireox

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix FPS initialisation if a positioner is collided sdss/jaeger
1 participant
@albireox