You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 20, 2020. It is now read-only.
When the connection is lost, the driver should inform of that through its state topic.
A connection loss might mean a protective stop was triggered in the robot. This circumstance should be notified to any higher level nodes that might be interested.
E.g. when we implement #7 and #2, if we don't notify the higher level nodes that the robot was offline for a certain time, those nodes could keep sending targets to the robot regardless of its state. So when the robot comes back online that could have undesired effects.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When the connection is lost, the driver should inform of that through its state topic.
A connection loss might mean a protective stop was triggered in the robot. This circumstance should be notified to any higher level nodes that might be interested.
E.g. when we implement #7 and #2, if we don't notify the higher level nodes that the robot was offline for a certain time, those nodes could keep sending targets to the robot regardless of its state. So when the robot comes back online that could have undesired effects.
The text was updated successfully, but these errors were encountered: