10-25-2011 09:41 AM
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?
10-25-2011 10:42 AM
try the following link
02-27-2013 05:57 PM
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
02-27-2013 06:30 PM
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.
02-28-2013 05:02 AM
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.
02-28-2013 10:04 AM
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
02-28-2013 10:08 AM
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.
02-28-2013 01:59 PM
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.
02-28-2013 02:17 PM
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