-
Notifications
You must be signed in to change notification settings - Fork 80
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
Support starting the driver, before the robot is booted #98
Conversation
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.
Looks mostly fine with me. Thank you @urmahp. This is a great contribution.
If you could address the mentioned formatting issues and maybe apply my comment suggestion, that would be great.
This will not completely fix #94 as we also have the connection to the secondary interface and to the dashboard server would need a reconnect to fully support starting the driver before a booted robot. @urmahp would you like to address this in this PR, as well? |
If it can wait until next week, then I can have a look at it next week and address it in this PR. |
I would be fine with that. Maybe it will itch me enough before, to implement it myself, though ;-) |
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.
Looks good to me. I'll quickly add the missing dot in producer.h
then we should be good to go.
Refactored client library to support starting the client, before the robot is booted. Changed producer to wait until robot is reachable on configured IP, instead of throwing an exception.
Co-authored-by: Felix Exner <felix_mauch@web.de>
Fix typo
This will enable the dashboard client and secondary client to wait for a robot to be booted
…ots#98) * Support starting the driver, before the robot is booted Refactored client library to support starting the client, before the robot is booted. Changed producer to wait until robot is reachable on configured IP, instead of throwing an exception. * Move the endless connection attempts to the tcp socket This will enable the dashboard client and secondary client to wait for a robot to be booted * Fix formatting. Co-authored-by: Felix Exner <felix_mauch@web.de>
Refactored client library to support starting the client, before the robot is booted.
Changed producer to wait until robot is reachable on configured IP, instead of throwing an exception.
This will fix issue #94.