I have made a sequence with LabVIEW libraries. I worked with PPL, so I referenced my LV project file, with the VI in the lvlib :
I set the Override Settings to target the right Build Specification :
When I was developping, during my tests, I had the Preloading Modules window. I always used the "Always run VIs in PPL" in the LV adapter options. Everything was fine.
Now, I need to go to production mode. So I deleted sources, and keep only PPL (lvlibp), and lvproj of course.
It is working at the end, but the "Preloading Modules" window is very very very slow (few minutes).
Do you know what's happening ?
How do you manage dependencies in your project? Do you have your driver in labview\instr.lib directory? Are you sure that TS/LV can easily find your driver? I'm guessing that you have a problem with relative paths.
All my drivers are packaged in a lvlib.
I attached a sample sequence with drivers. I also attached CPX400DP drivers if needed (provided by TTi company).
For this example, I timed the launching, from Click on "Execture >> Test UUT (F5)" until the dilogbox requesting UUT Serial number, here are the results :
- Sources directory keeped : 21s
- Sources directory removed : 4mn 40s (This is huge long time !)
Sequence is stored in "D:\Sequences\SomeTestSequence.seq" (D mounted via Windows command)
I have the following settings for this test :
LabVIEW Adapter Configuration :
Search Directories :
Thanks for your help.
Can you try to use lvlibp (packed)?
Il used lvlibp, but via the "Always run VI in Packed Project Library" LV adapter option.
The idea is to develop in LV edition mode, for the debug. When I want to push to production the sequence, I check the PPL option and I remove sources.
Of course, I can target directly the VI in the lvlibp, but I'm trying to use the PPL LV adapter option (available since TS 2019).