-
Notifications
You must be signed in to change notification settings - Fork 312
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] - A non active controller should not be reported as error #1183
Comments
Hello @firesurfer! Yes, it makes sense that it shouldn't be reported as an error if the controllers are loaded but are deactivated. Feel free to open a PR fixing this part of the code: ros2_control/controller_manager/src/controller_manager.cpp Lines 2539 to 2563 in 65353ff
I would say it would be an OK state to be in the inactive state, if you are interested, you can also log the information of the controller stats like their update_rate and if they are async or not etc. Thank you |
@saikishor I created a PR which just makes the switch from Error to Warn. Not sure if there is any other error information to report about controller (such as ros2 control could not active the controller) |
Is this fixed with #1184? |
@christophfroehlich yes it should be fixed. Now it won't report it as an error |
Describe the bug
Currently controllers that are loaded but are deactivated are reported as errors via ROS diagnostics.
I think this should be a warning. In my system for example I regularly switch controllers (e.g. from a compliant controller to the jtc and back). The other controller being inactive is desired behavior in that case and should not be reported as an error.
To Reproduce
Load a controller and deactivate it
Expected behavior
Report nothing or just a warning via ROS diagnostics
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: