Describe the bug
While developing tests to exercise the custom device when using different FPGA and Hybrid mode configurations, we found that changing the bitfile / scan engine mode between VeriStand deployments results in errors. These errors imply that LabVIEW RT is crashing, but regardless of the different errors returned, the target must be rebooted for subsequent deployments to succeed.
To Reproduce
The easiest way to reproduce this is to run the three system tests for a cRIO 9045 and 3x 9401s added in #207:
Hybrid (2 FPGA slots and 1 Scan Mode)
FPGA (2 FPGA slots)
UDV (no C Series IO, only UDVs of various datatypes)
Alternatively, manually deploy 2 of the system definition files contained in the test assets.
Workaround
Before changing the new configuration, reboot the cRIO. This appears to work every time, regardless whether all of LabVIEW RT crashes.
Expected behavior
Ideally the custom device could deploy any Scan Engine mode, FPGA bitfile, or combination thereof without a need to reboot the target.
Describe the bug While developing tests to exercise the custom device when using different FPGA and Hybrid mode configurations, we found that changing the bitfile / scan engine mode between VeriStand deployments results in errors. These errors imply that LabVIEW RT is crashing, but regardless of the different errors returned, the target must be rebooted for subsequent deployments to succeed.
To Reproduce The easiest way to reproduce this is to run the three system tests for a cRIO 9045 and 3x 9401s added in #207:
Alternatively, manually deploy 2 of the system definition files contained in the test assets.
Workaround Before changing the new configuration, reboot the cRIO. This appears to work every time, regardless whether all of LabVIEW RT crashes.
Expected behavior Ideally the custom device could deploy any Scan Engine mode, FPGA bitfile, or combination thereof without a need to reboot the target.