NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview "Getting Started" Window

Everytime I run my testand sequence it loads up labview (2010) "Getting Started" window which interfere's with a VI I'm running as part of my sequence.  Is there any way to prevent labview or the getting started window from constantly popping up?

 

0 Kudos
Message 1 of 9
(4,283 Views)
0 Kudos
Message 2 of 9
(4,274 Views)

I'm wondering if anyone has other ideas to solve this problem.  I'm worried about switching to run-time engine without doing a deployment, and I don't like the idea of touching every Labview Step just to change a property.

 

I was considering launching a DoNothing.vi from my user interface, but that is less than ideal.  Would prefer to just disable that window completely, but that option is only applicable when opening Labview doesn't make a difference when running Teststand engine from custom user interface.

 

Although doesn't the Teststand Sequence Editor always stay in front?  hmm.

 

Kevin

0 Kudos
Message 3 of 9
(4,122 Views)

Minimize LabVIEW before starting your sequence. So long as it's been minimized in Windows then I've yet to see it show the Getting Started screen.

CTA, CLA, MTFBWY
0 Kudos
Message 4 of 9
(4,118 Views)

I pretty much always open LabVIEW and make sure it is fully up and running before starting TestStand.  I find it helps the loading process.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 5 of 9
(4,110 Views)

Both are reasonable solutions when a knowledgable engineer is running the software.  However we have operators running a custom UI.  I have already had situations where the operator closes Labview in the middle of the test when the Getting Started window pops up in front of the UI. 

 

Kevin

0 Kudos
Message 6 of 9
(4,099 Views)

You shouldn't be using LabVIEW Development on deployed benches. Deploying your code and running the LabVIEW Run-Time Engine is a much better solution.

CTA, CLA, MTFBWY
0 Kudos
Message 7 of 9
(4,096 Views)

Hi MMP14,

 

Do you have the LabVIEW environment option to skip the getting started window enabled?  This will prevent the getting started window from appearing if your sequence is starting LabVIEW.

 

2013-02-28_135733.png

Al B.
Staff Software Engineer - TestStand
CTA/CLD
0 Kudos
Message 8 of 9
(4,082 Views)

Tried that option, and it only disables the getting started window when I open Labview from the start menu.  It still shows it when my sequence executes from the custom UI.

 

Eventually I will do a full deployment on the station, but right now we are kind of a hybrid.  Still doing develovpment in addition to testing prototype hardware.

 

Kevin

0 Kudos
Message 9 of 9
(4,078 Views)