Deploy TestStand System and Override Module Settings

[MaximeR]

Thanks for your reply and the clarification of the behavior.

I still don't understand why it takes so much time to have these answers when it have to be inside the TestStand help !

The future behavior if definitely the only option that can push me to use this option execpt if I want to deploy my bench with Source Code Control.

I will not spend some time to force myself to have a project+lvlib+build spec + another project to reference builded ppl without ability to distribute only an already builded PPL without distributing sources (even if we can remove block diagram and other options to protect sources).

For the moment, if we want to use it, you ask developper to give a huge effort without real benefits in my point of view.

---

If it's the case, what is the interest of this functionnality except my understanding to have a deployment process with Source Code Control and be able to run sequences with the RTE only ?

I did not fully understand this question.

---

Take a look at my second post of this thread for the explanation.

Best regards

[PragmaTest]

Thanks @Maximr for pointing me to this post.

And thanks @PRJ for your useful answers.

I'm glad NI finally gave detailed answers after two years (our first post related to this issue is from 2021).

To bypass this issue we took the decision to call directly PPL from our LV code modules, without any lvproj and without using overide options. We try to test intensively our LV code modules before compiling them into PPL.

However, we wrote a TestStand idea exchange HERE

From the @PRJ answer we can conclude that this idea will be fulfilled in the future...(finger crossed)

Best regards,

[python007]

Hello to all

I very confused about the discussion here. My english isn't very good so for me its hard to fallow you.

If I understand it right at the moment the fallowing scenario is not possible?

Developmentmachine: Switch between pre Build PPL and Source e.g. for Debugging

Productionmachine: Only have the pre Build PPL without the Source Files

So can you tell me what is the best approach at the moment?

Best Regards

[TRJ]

Hi python007,

Sorry if the long explanations added to the confusion.

Development machine: Switch between pre Build PPL and Source e.g. for Debugging - this is possible, when you configure a step to use Overridden modules.

Production machine: Only have the pre Build PPL without the Source Files - this is currently not possible through deployment for Overridden Module steps. If you create a deployment through Teststand Deployment Utility, the source files will be included for the Override Module steps.

If you prefer all your VIs to be present in PPLs in production machines and do not want to include any source files, you can also enable the option to "Output VIs to a Packed Project Library" (under Distributed File tab-> LabVIEW Options). This will put all the VIs you call from your sequence file into one or more PPLs.

Hope that helps.

Regards,

Tinu

[TRJ]

Thank you Sébastien for the inputs on desired behavior.

Will look into the points mentioned on the idea exchange link when this is implemented.

Regards,

Tinu

[python007]

Thanks TRJ for clarification

So the best approach if i don't want any Source Files on the Production machine and i wan't to use my pre built ppl's is to use my pre built ppl directly in the LabVIEW Module "VI Path" without the "override code Module" configurated?

Best regards

[PragmaTest]

Hi python007,

Yes it's probably the best approach until the next TestStand release : calling a VI inside a PPL, no overide, no .lvproj configured.

[PragmaTest]

---

@TRJ  a écrit :

Thank you Sébastien for the inputs on desired behavior.

Will look into the points mentioned on the idea exchange link when this is implemented.

Regards,

Tinu

---

Hi TRJ,

I am a user of LV 2020 and TS 2020, for fun I tried TS 2022 Q4.

I am very confused : in this 2022 Q4 version, and with the following combination :

-a LV step configured with a .lvproj an PPL override

-LV Adapter configured on Runtime + always use VIs in Packed Project Library

--> each time the execution starts, it launches the LabVIEW Development System

--> each time the execution starts, if the LabVIEW Development System is not installed it throws an error

My conclusion is that its' even worse than the TS 2020 version, where, at least, the LabVIEW Development System is not launched with this combination (even is source VIs can't be deleted).

I hope that there is some plans to fix this, because it sounds like a big annoying bug to me.

Regards

Sébastien