Allows the user to enable or disable the custom device.
Why should this Pull Request be merged?
Allows the user to enable or disable the custom device.
What testing has been done?
Built and manually tested the system explorer embedded menu behavior. (See picts above) Verified the engine is not called when the the embedded data logger is disabled.
Other
The vi "Enable or Disable" was renamed "Get Control Condition State". The enable/disable support added a new VI called "Enable or Disable", which introduced confusion with the existing "Enable or Disable" VI. I opted to rename the existing VI to something that better reflects its purpose.
Embedded Data Logger System Explorer.lvlib--Enable Disable.vi.png
![capture](https://raw.githubusercontent.com/niveristand-diff-bot/diff-images/master/NI/niveristand-embedded-data-logger-custom-device/PR-32/2020-09-24/17%3A56%3A39/Embedded%20Data%20Logger%20System%20Explorer.lvlib--Enable%20Disable.vi.png)Embedded Data Logger System Explorer.lvlib--File Page.vi.png
![capture](https://raw.githubusercontent.com/niveristand-diff-bot/diff-images/master/NI/niveristand-embedded-data-logger-custom-device/PR-32/2020-09-24/17%3A56%3A39/Embedded%20Data%20Logger%20System%20Explorer.lvlib--File%20Page.vi.png)Embedded Data Logger System Explorer.lvlib--Get Control Condition State.vi.png
![capture](https://raw.githubusercontent.com/niveristand-diff-bot/diff-images/master/NI/niveristand-embedded-data-logger-custom-device/PR-32/2020-09-24/17%3A56%3A39/Embedded%20Data%20Logger%20System%20Explorer.lvlib--Get%20Control%20Condition%20State.vi.png)
What does this Pull Request accomplish?
Allows the user to enable or disable the custom device.
Why should this Pull Request be merged?
Allows the user to enable or disable the custom device.
What testing has been done?
Built and manually tested the system explorer embedded menu behavior. (See picts above) Verified the engine is not called when the the embedded data logger is disabled.
Other
The vi "Enable or Disable" was renamed "Get Control Condition State". The enable/disable support added a new VI called "Enable or Disable", which introduced confusion with the existing "Enable or Disable" VI. I opted to rename the existing VI to something that better reflects its purpose.