Handle cases of the lidar sensor becoming unpowered during operation #119
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@tombrodie thanks for your contribution, I will try to take a look at your PR towards the end of the last of the month. |
Closed
This was referenced Aug 9, 2024
Closed
This was referenced Aug 23, 2024
|
included/resolved by #362 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issues & PRs
Summary of Changes
retry_configuration(defaultfalse) which, whentrue, will continue to attempt to configure the lidar sensor if the sensor is uncontactable on initialisation instead of the current behaviour of the code crashing. Additionally, if the sensor becomes uncontactable during operation, this branch periodically attempts to re-establish a connection to the sensor using the configuration provided on initialisation.Validation