Closed Karl-G1 closed 2 years ago
Admittedly the worst part of this (possibly too-large-to-review) PR is the logic in the Get Local Chassis Slots Configuration
VI:
Because the custom devices uses 3 different GUIDs for slots (depending if they are empty, populated with an RSI module, or 'inactive') AND the slot number is only retrievable if there is an RSI module tied to a lot, it is difficult to retrieve the list of local slots and their properties in order.
The 'fix' I implemented is ugly: read the children of the local chassis, then retrieve the name for each, finding "SlotX" in the name to determine which ones are slots. This was in lieu of adding a Slot Number property to each, since the name is not configurable and this didn't modify how the slot section was added or stored. But if this logic is too flaky, it is on my radar to replace.
Bleep bloop!
LabVIEW Diff Robot here with some diffs served up hot for your pull request.
Notice something funny? Help fix me on my GitHub repo.
Bleep bloop!
LabVIEW Diff Robot here with some diffs served up hot for your pull request.
Notice something funny? Help fix me on my GitHub repo.
Bleep bloop!
LabVIEW Diff Robot here with some diffs served up hot for your pull request.
Notice something funny? Help fix me on my GitHub repo.
Bleep bloop!
LabVIEW Diff Robot here with some diffs served up hot for your pull request.
Notice something funny? Help fix me on my GitHub repo.
What does this Pull Request accomplish?
FPGA / Scan Interface mode
setting on the controller page, as that property is necessary on first deployment of FPGA bitfiles.Apply Module Mode
is enabled.Full list of changes:
Slot Programming Mode
to persist the value ofCustom Device Source/System Explorer/Type Defs/Slot Programming Mode.ctl
.Apply Module Mode
to the local chassis.System Explorer/Type Defs/Slot Programming Mode.ctl
typedef to have the default value of 0 be 'Don't Modify'. This made logic easier to handle when searching for the property and returning the default when not found.System Explorer/Utility/Auto Detect/Programming Mode.vi
and its sub VIs:System Explorer/Utility/Auto Detect/Add Local Chassis from Config.vi
)System Explorer/Utility/Auto Detect/Add Local Chassis from Config.vi
)Apply Module Mode
property on the chassisProgramming Mode
VI/dialog was cancelledSystem Explorer/Action VIs/ActionVIOnDownload - Set Scan Rate.vi
Apply Module Mode
property is True. Previously, this was based off of theFPGA / Scan Interface mode
setting.test Reading Slot Configuration.vi
to validate reading the slot numbers and configuration from a system definition fileWhy should this Pull Request be merged?
What testing has been done?