Switching between VIs and Packed Project Libraries

[RayFarmer]

In the LabVIEW adapter configuration dialog box, does the override the module settings for all LabVIEW steps and always run the VI in the packed library prevent you from running a particular step in its source code version?

[RayFarmer]

I am having problems with this topic.

I have a simple PPL and I have a sequencefile with one step using the source VI, one step using the PPL VI and a third step with the project and the source.

The first two steps behave as previous versions of TestStand where one would have to relink from the PPL VI to the source VI to do any editing etc.

The third VI should be setup to try this new feature of TestStand 2019 where one can switch between source and PPL but its not working. I am getting an error with the OverrideBinaryProjectPath.

As you can see there is an error telling me it can not find the VI in the lvlibp file.

I have zipped up the labview 2019 project and the TestStand 2019 sequencefile for someone to tell me what I am doing wrong.

[Anand_Jain]

Hi, 

You cannot use the same project for both the source VI and the Packed Project Library. To fix this issue, you can either create a new project that refers to the Packed Project Library or you remove the project configured for the Packed Project Library in the "Override Module Settings" dialog. 

There is a CAR reported to improve the error message for this use case. 

I hope this helps. 

Regards

Anand Jain

National Instruments

[RayFarmer]

Hi Anand,

Are you saying the Project Path can not be the same as the Source Project Path?

Or you don’t need to specify the Project Path?

[Anand_Jain]

Hi Ray, 

My answers below:

Are you saying the Project Path can not be the same as the Source Project Path?

- Yes

Or you don’t need to specify the Project Path?

- Yes, you do not need to specify a project path for the Packed project library to use the feature but can. 

Regards, 

Anand Jain

National Instruments

[RayFarmer]

Not quite there yet.

Step1 - this I cannot override and runs the PPL function, this I expect.

Step2 - Always runs the source regardless of the override setting.

Step3 - I have removed the PPL settings from the Override Setting Dialog. This  always runs the PPL functions both with the override enable and disabled. This one I would have expected to run the source VI with the override enabled

Provided a new version of the project

[Anand_Jain]

Hi Ray, 

How did you verify if the VI or the PPL executed? One approach you can take is to execute your sequence using LabVIEW development system and debug the module called by step 3. You should notice that in one case the VI is executed and in another case the PPL is executed. 

Let me know if that is not the case. 

Regards

Anand Jain

National Instruments

[RayFarmer]

Yep that’s what I did!

[RayFarmer]

In my sequencefile, all I have is the one step.

With the Configure Adapter, Always run VI in PPL disabled and the Step Override Module Setting - Always run VI in PPL disabled, the step runs in the source VI.

With The Configure Adapter, Always run VI in PPL disabled and the Step Override Module Setting - Always run VI in PPL enabled, the step runs the VI in the PPL.

With the Configure Adapter, Always run VI in PPL enabled, it doesn't make any difference with the setting in the Step Override Module Setting - Always run VI in PPL whether enabled or disabled, the step always runs the VI in the PPL.

This is the Override Module Setting dialog.

I would have expected the Override setting to override the Global setting similar to the Result Recording Option where you can override the Sequence setting if the sequence has the result recording disabled.