04-14-2023 01:10 PM
I have Labview 2022 Q3 (64bit) and TestStand 2022 (64 bit) on a windows 10 PC. I'm running into an issue when a testStand sequence calls a VI that uses Clear Error.vi shows an error or crashes TestStand. It's so odd that I am attaching a screen capture of the entire process. I can't be the only to have seen this. any ideas as to what is wrong and how to fix it would be apricated. The only work around that I have so far is to use the development version of the LabView runtime.
04-17-2023 09:18 AM
If I had to guess this is due to LabVIEW by default changing to checked for "Separate compiled code from source file" on new VI's. So your cache isn't getting the VI correctly. This change happened with LabVIEW 2022 Q3. If you go the VI Properties for the VI you created, and uncheck that box, does it load properly in TestStand with LabVIEW Runtime after that?
04-17-2023 10:19 AM
ShockHouse, Thank you for the, I forgot about that change, but sadly this did not solve the issue.