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

Status info #102

Open
MoffKalast opened this issue Nov 8, 2021 · 0 comments
Open

Status info #102

MoffKalast opened this issue Nov 8, 2021 · 0 comments

Comments

@MoffKalast
Copy link
Contributor

MoffKalast commented Nov 8, 2021

So there seems to be a lot of info that move_basic is aware of during goal movement, but cannot be communicated back to the action client. There is technically a string in GoalStatus, but there doesn't seem to be a way to access that in the python implementation at least.

I would propose creating an extra topic where some of this data could be published, such as:

  • current action being taken (rotating, linear move)
  • are we waiting for an obstacle
  • distance remaining to goal
  • etc.

That could then be displayed as relevant info in breadcrumb an ezmap, since it's sometimes not clear why the robot is standing still near a goal that's close to a wall or something, which is unintentionally triggering the obstacle wait.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant