Add option to disable Refresh Modules
code to use persistent config
#255
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.
What does this Pull Request accomplish?
Add option to disable
Refresh Modules
code to use persistent configRefresh Modules
during auto-detect or deploymentWhy should this Pull Request be merged?
For customers with unique EtherCAT configurations, the default logic in the Custom Device can delete a working configuration file set on the RT Target. If the ECAT config was set programmatically or in LabVIEW, this setting allows users to detect and deploy to an existing configuration that is not regenerated in VeriStand.
What testing has been done?
Configured ECAT config in LabVIEW, deployed the ECAT Master, re-enabled VeriStand as the startup .rtexe, then auto-detected with the modified custom device build.
I tested with one EtherCAT AKD, making a 'fake revision' ESI file for it that wouldn't otherwise be detected by auto-detect in VeriStand. Then I deployed successfully.