NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Error code:-17208 / Teststand was unable to access the LabVIEW class member

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.

xiaoY_1-1696749219708.png

 

xiaoY_0-1696749086256.png

 

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.

0 Kudos
Message 1 of 7
(2,514 Views)

Do I see this correctly, is the class in question part of an lvlibp/ PPL?

0 Kudos
Message 2 of 7
(2,439 Views)

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.

JorrEl_0-1696855747631.png

 

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`

JorrEl_1-1696856018832.png

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.

Jorr-El
Systems Engineer
Testeract: Automated Test Specialists
0 Kudos
Message 3 of 7
(2,425 Views)

It could be related to this:

ShockHouse_0-1696864984898.png

 


The internal path of your ppl, based on the image, is long. If the path to the PPL is also long, you may be seeing this issue.

0 Kudos
Message 4 of 7
(2,416 Views)

nope, the lvlibp/PPL looks well. it just shows error when invoked by teststand.

0 Kudos
Message 5 of 7
(2,362 Views)

thanks. i will try it.

0 Kudos
Message 6 of 7
(2,360 Views)

thanks. i will check the path

0 Kudos
Message 7 of 7
(2,359 Views)