Beckhoff Device Discovery structures #195
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
splatch
force-pushed
the
feature/beckhoff-discovery
branch
from
62d43c5
to
ed3fa8d
Compare
splatch
force-pushed
the
feature/beckhoff-discovery
branch
from
ed3fa8d
to
bf6ac83
Compare
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.
Given that I need to park this one for a moment and I managed to test and collect extra data for TC3 as well as extra sample for TC2 further work can continue on develop branch.
Discovery is based on UDP so requires separate discovery driver implementation. To start with this task we need to fully understand rest of discovery response frame which is used to identify device operating system and twincat runtime version. I made some comments in serializer XML tests for further investigation.