Implementation of Reachable PLC Scanner for TCP/IP #74
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
added 2 commits
July 18, 2017 22:34
…ons. Also includes an ready to go Discovery Modal Dialog
…s given to the "GetInterface" functions. This can happen during parsing of FB blocks, that do not have start values to be parsed
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 is an implementation for an Accesible PLC discovery Mechanism much like "Reachable Devices" in Simatic Manager. Currently this mechanism does only support TCP/IP.
For testing y added an new Menu Option into the Toolbox Project. Everything is implemented in "Communication.Discovery".
The Reachable PLC Scanner basically works the following way:
It gets all local IPV4 addresses from all Interfaces and then builds an list of addresses in each network interface from x.x.x.1 up to x.x.x.255 (This algorithm may not be optimal, but works in a lot of cases)
Then it goes on checking if any of these addresses are accepting connections on port 102, and if so, it tries to access the address via this library by checking the Slots 0 up to 5.
If any IP/Slot combination is found, it uploads the basic Controller Information, so it can be shown to the user.