I created a packed Library in my LabVIEW project through moving all my VIs in the created project library.After that, I can find a .lvlibp file in builds folder. But when I tried to open it with 'Class Member call', I can only see the .lvlibp file in the window. but I can't open it . What is the problem?What is the right manner to create a PPL , in oder to use the VIs in TestSTAND?Thank you for answering.
I don't have TestStand installed to check this, but the image you attached shows you browsing the lvproj file, which contains the lvlib file.
You'll need to instead open the lvlibp file. Maybe you already tried this, but the picture doesn't show it.
It's certainly possible based on other threads like the following: https://forums.ni.com/t5/NI-TestStand/Using-LVLIBP-with-DLLs-in-TestStand/td-p/3878633 (they had a different and likely more complicated problem with DLL searching, but they used a PPL in TestStand).
I'll try break your message up into a few pieces, maybe you can clarify if I misunderstood...
maybe I haven't described it clearly. I think you have understood it correctly with the following point:
'Your VIs expected to find other VIs at a specific location, but instead found them somewhere else. This produces a warning and will change the source files, but doesn't cause an error in general. It often is an indication something isn't as you expected though.' But there was errors.
I had a folder of all my VIs of this project(only VIs, no project library of packed library), we call it 'x'. Because I want to try the PPL building in another folder,then I copied 'x' and created a new folder 'x copy'.All the VIs in 'x copy' are the same as in 'x'.
Then I built project with VIs in 'x copy', created project library(called y) with all VIs in 'x copy', and then PPL. All these are in 'x copy' saved.
After that, I tried to open my VIs in 'x' folder, the window appears always asking for the project library(which was created with VIs in 'x copy'). If I click cancle,the VIs is opened with errors, that other VIs are not excutable.
So I just tried to reproduce what you found and had no issues, so I guess it requires something a bit more complicated than my very simple test.
Let me just describe what I did and you can tell me if you do anything different:
So I'm not sure what happened for you. I suspect some sort of cross-linking, but I don't know how or why. Do you depend on some other already existing PPLs? Changing the relative path can cause a problem if so.
Make sure you actually made the library with the VIs in x_copy. It is sounding a lot like you accidentally used x instead.