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

Diagnostics should not be OK if the realtime control loop is overrun #46

Open
haudren opened this issue Nov 9, 2020 · 1 comment
Open
Assignees

Comments

@haudren
Copy link

haudren commented Nov 9, 2020

Hello,

I noticed the following behavior today during some testing:

  • Connect to a running F60 controller attached to a RS007N
  • Diagnostics are published correctly, showing "OK" as message and the diagnostics status is OK (0)
  • Turn off the robot controller
  • Message turns to "Realtime loop used too much time in the last 30 seconds.";
  • Status stays OK (0)

I guess the problem is here:

status.level = 0;

I would expect to see a 1 (WARNING) or 2 (ERROR) or even 3 (STALE)

By the way, I would recommend using Enums, as in

diagnostics_msgs::DiagnosticStatus::WARN

Instead of directly using the values

@d-nakamichi d-nakamichi self-assigned this Nov 17, 2020
@d-nakamichi
Copy link
Contributor

Yes, currently status.level changes to 0 when overrun continues.
So I try to modify its level and overrun counting.

https://github.com/d-nakamichi/khi_robot/commits/modify_diagnostics_level

It would be helpful if you comment something about this.

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

No branches or pull requests

2 participants