-
Notifications
You must be signed in to change notification settings - Fork 58
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
Kobuki Dashboard - Extra Features #14
Comments
|
We do have enable/disable motors.
The diagnostics button turns orange/red, when warnings/errors are published on the diagnostics topic. Additionally the rosout button behaves similar.
We could make better use of diagnostics, e.g. within all important apps. There is one problem though: If a process dies on start-up or during runtime, it might do so before being able to publish an error message on the diagnostics topic. On the other hand dying processes are also caught by the rosout widget, but using this would require the non-ros-developers to get acquainted with the logs, i.e. which warnings/errors are important, which are not. That might not be trivial for them. So, bottom line is, we have already tools in place, which report the problematic situations, but they are not convenient enough. Any ideas how we can change that? |
rosnode pings nodes to get its status. Can reuse its code to make a watchdog? another idea: make use of the node attribute "required":
But I wonder if we are not pushing to far the dashboard; to me it's (mostly) a convenient hardware status check tool. |
Should I implement this? Now? It's in my issues disintegration card... |
We all have it. Basically I think we get together after refamiliarising ourselves and draw up a list of desirata for a demobot. |
Useful (but probably not priority) additions:
|
👍 We would appreciate a PR for that! ;-) |
Update with extra features that help non-developers exhibit kobuki for us.
As we test over the next two-three weeks, list here things we think should be in it.
The text was updated successfully, but these errors were encountered: