Allow configuration of retry behaviour for timed out PDUs #102
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
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 builds on #101 and makes the retry behaviour much more robust. In my local testing, I can unplug the EtherCAT network cable and replug it and the slaves (EL2828, EL2889 in my case) pick the PDI back up again.
According to https://infosys.beckhoff.com/english.php?content=../content/1033/el34x3/1036979339.html&id=, the slaves won't fall out of OP when no PDI is received but their watchdogs will trigger, causing outputs to be turned off for safety.