Added Profinet Monitor #7
Open
Conversation
This file contains hidden or 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
…ofinet devices, log failures and automatically assigns the device name to devices that have lost their device names.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I had some problems with fault Profinet devices, that sometimes lost their PN Names after power failure. Si I wrote this tool to monitor and automatically assign an profinet name if an configured device has lots its name.
In configuration mode (no cmd line parameters), this tool allows you to create an configuration file with the "good" state of monitored devices. This is done by discovering current devices and saving them to an CSV file.
If you then start the Tool with the "-monitor" flag it will launch an discovery request and assign PN Names to any known device that lost its Name. It will also write log messages if an device is not available anymore and if it returns. This allows you to essentially log failures to an log file.
Details about its command line usage are in Readme.md
The UI is done in Winforms though, since i am not really proficient in WPF and needed an quick solution. Anyhow i hope this will help somebody, it sure helped me out and saved me from a lot of sleepless nights.