10-08-2023 02:17 AM
hello,
I got a problem in teststand shows "File or directory not found", "Teststand was unable to access the LabVIEW class member". but the very strange is the vi is exist in labview class.
I wonder what's the problem is, and how to fix it.
many thanks.
Details:
Could not find member 'TSTagEngine Init.vi' in LabVIEW Class '...TSTagEngine\TSTagEngine.lvdass'
TestStand was unable to access the LabVIEW class member:
'TSTagEngine Init.vi'
Ensure it has public scope and that is belongs to the selected class.
Error code:
-17208;File or directory not found.
10-09-2023 04:46 AM
Do I see this correctly, is the class in question part of an lvlibp/ PPL?
10-09-2023 07:54 AM
I've seen this happen before in PPLs when the "Preserve disk hierarchy" option is not checked in the build spec. If you happen to have multiple virtual folders and classes in a library, TestStand can run into issues where it is not able to find the class at the level it expects.
This is because when disk hierarchy is not preserved in the PPL build, the application builder will flatten the structure of your PPL and have all the VIs and classes directly under the Library file.
To fix this, check the box next to "Preserve disk hierarchy" in your PPL build spec. If this option is grayed out, you can manually check this box by opening your .lvproj file in a text editor (like Notepad++), searching for the keyword "Hierarchy", then changing the property from `false` to `true`
After making this change, save the .lvproj file, close your text editor, open your .lvproj again, rebuild your PPL and install it in the search directory your TestStand application expects it to be. TestStand should be able to find the class in your PPL now.
10-09-2023 10:22 AM - edited 10-09-2023 10:23 AM
10-12-2023 06:25 AM
nope, the lvlibp/PPL looks well. it just shows error when invoked by teststand.
10-12-2023 06:26 AM
thanks. i will try it.
10-12-2023 06:27 AM
thanks. i will check the path