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
Added watchdog configuration for the reverse socket #178
Added watchdog configuration for the reverse socket #178
Conversation
This enables the possibility to configure the read timeout for the reverse socket running in the external control script Separated control modes into realtime and non realtime to have different possible configurations for the watchdog Added test to verify the changes Updated test and examples to coincide with the new changes
Codecov ReportPatch coverage is
📢 Thoughts on this report? Let us know!. |
Moved timeout check to the reverse interface Changed timeout from float to std::chrono::milliseconds
I have updated the PR based on your comments. |
We should also add a test, that verifies that the reverse interface timeout as well with in the expected time. |
As the timeout is configured in the script the reverse interface will not timeout, the script will timeout. We could add a test that verifies that the script times out, but that would be a test under the UrDriver class, as it would require robot communication. |
True. And yes that is a good idea |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking really good and it reads much better with the RobotReceiveTimeout :-)
@urmahp a quick response to my comments would be nice, then I think we are good to merge this, as most of them is mainly aesthetics.
Usually it happens if two UrDriver objects are created to close to each other, this change should catch this
I have updated the PR in relation to the comments and added a better test coverage of the changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me! I'll deploy it on my test system and merge if everything goes fine on the real robot.
This enables the possibility to configure the read timeout for the reverse socket running in the external control script
Separated control modes into realtime and non realtime to have different possible configurations for the watchdog
Added test to verify the changes
Updated test and examples to coincide with the new changes