Fault-tolerant outstation serial task #215
Merged
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
…ns a task that controls the serial port in the background
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.
The existing outstation serial task tries to open the serial port during creation, and fails if the port isn't available. The task will also exit if the serial port disappears during execution. It is possible for serial ports to come and go for example with USB to serial converters... I'm sure there are other cases too.
This PR adds additional methods for spawning serial outstations that control the port on the background task. They are "self-healing" and retry opening the port at a configurable rate.
The old methods still exist for API backwards compatibility in the 1.x release series, but will probably be removed once we eventually do a 2.0 release.