LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Operator Interface using TestStand sequence that uses Source Distribution, how to proceed?

Solved!
Go to solution

Important information

Windows 11 Enterprise

TestStand custom sequences that use VIs in a Source Distribution

Operator Interface that uses different VIs, but not in a Source Distribution

However, the VIs in the Operator Interface ARE in the Source Distribution

The OI VIs are in a folder that is in the LabVIEW Modules folder that has been 

- Mass Compiled all this together

- Built into a Source Distribution with all this together.

 

The Project.

I have moved old code to modern LV and TS, and have done the above list of things.  The TestStand sequences using the Source Distribution VIs and support files runs in the RTE of the TestStand Editor.

I have built the OI project using the raw VIs that are only in the OI source folder which calls the TestStand sequences.

The OI runs the TS sequences that use the Source Distribution VIs.

 

In order to deploy this code on a computer that only has the TestStand deployment (run time license only), do I need to build the OI project using Source Distribution code?

If so, can I use the Source Distribution code that was created when I created the overarching mass compile and source distribution?  Should I create a separate a separate source distribution for the OI only to use?

 

I inherited all this code.  I migrated them forward and modified it all to work in a source distribution as suggested by an NI support tech.  With this I am pretty sure the just running the TestStand sequences will work on a run time environment at the target computers.  I am not so sure about the OI made with the raw VIs and suspect I need to do more.  But am not sure.

 

I understand most of what is going on within the environment I have created, and I believe I understand how to move what I have built to another computer.  

Except for the OI.  Since that is pure LabVIEW, will that run on a computer with only a run time license?  I am a little vague about the difference between a licensed TestStand RTE and running a LabVIEW program on a system that that only the LabVIEW RTE.  Is the TestStand RTE the same RTE as the LabVIEW code will use?

 

Any advice is appreciated.  I only know enough to be dangerous.

 

Be well,

DLC

 

 

0 Kudos
Message 1 of 3
(321 Views)
Solution
Accepted by topic author DLMC

The Operator interface should just be a UI to run the sequence, it shouldn't matter which one you use (unless it's somehow tweaked).

Start by running it from TS with LV in dev mode and if that works, try switching LV to Runtime (in TS). If that works the OI should work and you can have a runtime station. Else you might need to do a new code export with some tweakage to which VI to include.

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
Message 2 of 3
(270 Views)

@Yamaeda wrote:

The Operator interface should just be a UI to run the sequence, it shouldn't matter which one you use (unless it's somehow tweaked).

Start by running it from TS with LV in dev mode and if that works, try switching LV to Runtime (in TS). If that works the OI should work and you can have a runtime station. Else you might need to do a new code export with some tweakage to which VI to include.


Thanks for the input.  It runs fine in both the dev. mode and RTE mode.  I can rest assured now. 

 

be well,

DLC

0 Kudos
Message 3 of 3
(254 Views)