Check if LV, LVRT, and ECAT are installed before launching the "Manage 3rd-Party ECAT Slaves" dialog from the custom device main page. This was done by adding a sub VI to read the appropriate registry keys before launching the dialog (and all of the initialization logic that happens with it).
Throw an error if any components are missing:
Why should this Pull Request be merged?
This issue came up in escalation 1924218. The existing behavior is confusing, as several different errors can be thrown (as seen in #209).
What testing has been done?
Tested on VMs with:
VeriStand and all necessary software installed
Only VeriStand and the custom device installed
VeriStand and only LabVIEW (no RT or ECAT) installed
SEECD System Explorer.lvlib--Check Host Software Installed.vi.png
![capture](https://raw.githubusercontent.com/niveristand-diff-bot/diff-images/master/NI/niveristand-scan-engine-ethercat-custom-device/PR-210/2022-05-02/12%3A16%3A07/SEECD%20System%20Explorer.lvlib--Check%20Host%20Software%20Installed.vi.png)SEECD System Explorer.lvlib--Main - Manages 3rd Party Slaves.vi.png
![capture](https://raw.githubusercontent.com/niveristand-diff-bot/diff-images/master/NI/niveristand-scan-engine-ethercat-custom-device/PR-210/2022-05-02/12%3A16%3A07/SEECD%20System%20Explorer.lvlib--Main%20-%20Manages%203rd%20Party%20Slaves.vi.png)
What does this Pull Request accomplish?
Check if LV, LVRT, and ECAT are installed before launching the "Manage 3rd-Party ECAT Slaves" dialog from the custom device main page. This was done by adding a sub VI to read the appropriate registry keys before launching the dialog (and all of the initialization logic that happens with it).
Throw an error if any components are missing:
Why should this Pull Request be merged?
This issue came up in escalation 1924218. The existing behavior is confusing, as several different errors can be thrown (as seen in #209).
What testing has been done?
Tested on VMs with: