Handle glitched connections #15
Open
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
Signed-off-by: Alastair D'Silva <[email protected]>
Signed-off-by: Alastair D'Silva <[email protected]>
deece
pushed a commit
to InfernoEmbedded/TWCManager
that referenced
this pull request
Jan 12, 2022
Prevent car charging if Powerwall needs to charge
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.
This PR makes connections to the TWC more robust by reestablishing the connection if no slaves are present.
I have a ~10m run of mains rated, unshielded Cat5 from my power management machine to the TWC. The connection is properly terminated, but frequently stops communicating. Restarting TWCManager fixes the problem, but just resending the link-ready packets is insufficient, however, reopening the serial port does work.