LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Executing TestStand code within LabVIEW GUI

Hello, I'm looking to create a LabVIEW GUI which maintains a connection and status to an external device.

 

I'm really familiar with TestStand and it's various ways of manipulating API's, and I already have a sequence with multiple subsequences which i call from main test sequences to manipulate this external device.

 

I'm fairly inexperienced with LabVIEW, aside from the basics; but I do have access to LabVIEW code which makes calls to TesStand sequences.

 

I guess I'm just wondering from LabVIEW architects if it's acceptable to use LabVIEW in this manner to call TestStand seq code instead of the other way around. The only reason I'm looking to do this is because another team maintains and updates the sequence which i'm looking to make calls to. So by doing it this way my LabVIEW GUI is effectively being updated anytime my other team makes a change to the gut sequence.

0 Kudos
Message 1 of 8
(3,500 Views)

I'm not a Labview architect, but I would avoid calling Test Stand from a Labview application, if not needed,

i.e. if you are not performing a sequence test.

 

You say you want to "create a LabVIEW GUI which maintains a connection and status to an external device".

In my opinin this is purely a "Labview task", and should be coded this way.

 

What if you need this application on a different PC: are you going to buy a Test Stand runtime license?

Are you going to launch Test Stand (taking more than a few seconds and some resources) just to execute a couple of configuration step?

 

Of course I don't know your special case, so these are just general toughts....

 

Marco

 

 

 

0 Kudos
Message 2 of 8
(3,492 Views)

This is actually company related and is only used on test benches which contain both labVIEW and TestStand, so the issue of wanting to run on a bench which does not contain teststand will not be an issue...

0 Kudos
Message 3 of 8
(3,489 Views)

Your question is a bit confusing. How do you normally run your TestStand Sequences? Through the TestStand editor or do you use a Operator Interface? There are examples of LabVIEW Operator Interfaces in TestStand.

Now Using LabVIEW 2019SP1 and TestStand 2019
0 Kudos
Message 4 of 8
(3,480 Views)

Yes, this is possible and as mentioned above you would lokk to the examples of the operator interfaces to see how this is done. A word of caution though regarding the operator interface examples. They have not been pdated in a LONG time and do contain some examples of poor programing practices (Sequence frames, local/global variables, etc.).

 

Our automated test system has a very complex and feature rich operator interface that controls our test execution and sequences which are executed using TestStand. What you describe is a fairly typcial way of building and distributing operator interfaces.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
Message 5 of 8
(3,477 Views)

Would you happen to have an example of LabVIEW VI calling TestStand Seq to execute this that isn't so outdatted?

0 Kudos
Message 6 of 8
(3,462 Views)

@knowledge_is_power wrote:

Would you happen to have an example of LabVIEW VI calling TestStand Seq to execute this that isn't so outdatted?


Nothing that can be posted. Not to mention our GUI is comprised of over 1000 VIs. It would be tough to whittle it down to something small. The shipping examples do show what you need to do.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
0 Kudos
Message 7 of 8
(3,460 Views)

Here is a pretty good overview webcast of using and editing a LabVIEW operator interface if you haven't seen it already.

Now Using LabVIEW 2019SP1 and TestStand 2019
0 Kudos
Message 8 of 8
(3,439 Views)