topic Re: Compiled vi always runs when opened, Labview 2013 bug? in LabVIEW

Compiled vi always runs when opened, Labview 2013 bug?

LarsM — Wed, 20 Nov 2013 14:21:17 GMT

I'm presuming it's not a bug, but right now it looks like that:

I compile a vi to an exe using the application builder, but no matter how I adjust the settings, the vi will always run when opened.

I'm running LabVIEW 2013.

Re: Compiled vi always runs when opened, Labview 2013 bug?

GerdW — Wed, 20 Nov 2013 14:32:00 GMT

Hi Lars,

when I run an executable (regardless LabVIEW or any other programming language was used to create it) I expect it to run when opened.

Do you expect something different when you start MSWord, FireFox or any other program you need?

Re: Compiled vi always runs when opened, Labview 2013 bug?

JÞB — Wed, 20 Nov 2013 14:40:30 GMT

@LarsM wrote:

I'm presuming it's not a bug, but right now it looks like that:

I compile a vi to an exe using the application builder, but no matter how I adjust the settings, the vi will always run when opened.

I'm running LabVIEW 2013.

That would be what happens to any "Start-up.vi" when an application starts up

Re: Compiled vi always runs when opened, Labview 2013 bug?

LarsM — Wed, 20 Nov 2013 14:43:39 GMT

I want to enter values and set up things before I actually run the vi.

Why am I able to uncheck "run when opened" if it actually doesn't do anything?

If you're not going to answer the question, please refrain from posting.

Re: Compiled vi always runs when opened, Labview 2013 bug?

JÞB — Wed, 20 Nov 2013 14:48:35 GMT

The start up vi will run. This is expected behavior.

If you want the running vi to wait for user input before executing a process you need to code a proper arcetecture to do that. Look into the Producer Consumer (Events) design pattern. It is a good way to start an application like you describe.

See, asking a question (or at least explaining what behavior you want) gets more specific answers.

Re: Compiled vi always runs when opened, Labview 2013 bug?

LarsM — Wed, 20 Nov 2013 15:17:13 GMT

Are you saying that the "run when opened" checkbox is obsolete?

What's the purpose of having a run mode (as opposed to edit mode) if nobody's expected to use it?

Re: Compiled vi always runs when opened, Labview 2013 bug?

jcarmody — Wed, 20 Nov 2013 15:27:56 GMT

"Run when opened" and "edit mode" apply to the VI file, not the exe.

Re: Compiled vi always runs when opened, Labview 2013 bug?

LarsM — Wed, 20 Nov 2013 15:32:14 GMT

In the app builder properties, under "Source File Settings" I can click "Customize VI Properties..." and there uncheck "Run When Opened". Does this actually do anything?

Re: Compiled vi always runs when opened, Labview 2013 bug?

GerdW — Wed, 20 Nov 2013 15:35:59 GMT

Hi Lars,

the point is: any executable is set to "run when opened", that's the expected behaviour on any OS. You cannot change that behaviour!

But you can (or "have to") program a good UI that allows the user to start a measurement when (s)he is ready to do so. In the simplest form you just wait in a polling loop for a "Start now" button, in more advanced schemes you will use an event structure and maybe a state machine. A producer/consumer scheme can be used to, but will probably use the event structure and the state machine too...

Re: Compiled vi always runs when opened, Labview 2013 bug?

LarsM — Wed, 20 Nov 2013 15:36:32 GMT

A problem is that even though it runs when opened, it only runs once, not continuously.

Re: Compiled vi always runs when opened, Labview 2013 bug?

RavensFan — Wed, 20 Nov 2013 15:44:51 GMT

If you want it to run continuously, then you need to have a while loop in it.

Please don't tell me that when you were creating this VI in the development environment you were using the "Run Continuously" button.

Re: Compiled vi always runs when opened, Labview 2013 bug?

LarsM — Wed, 20 Nov 2013 15:48:39 GMT

I was not using the "run continuously" button, no, but if a compiled vi is expected to always run, then that would be the logical behaviour.

Re: Compiled vi always runs when opened, Labview 2013 bug?

GerdW — Wed, 20 Nov 2013 15:50:20 GMT

Hi Lars,

it is not expected to "always and forever run", it is expected to "run when opened".

That's quite a difference!

Re: Compiled vi always runs when opened, Labview 2013 bug?

Intaris — Wed, 20 Nov 2013 16:01:19 GMT

Your program, if it is not controlled by a loop, will only run once.

If you want continuous execution you need to program it that way. If you want something like when you press "Run continuously" in development mode, then you'll have to program that I'm afraid. The mode of execution in an EXE is comparable to a single click of the "run" button in the IDE.

Melander. It's a few years since I came across that name. It always sparks memories of the Snork Maiden and such.

Re: Compiled vi always runs when opened, Labview 2013 bug?

altenbach — Wed, 20 Nov 2013 16:49:27 GMT

A LabVIEW executable should run when opened and close when done. A stopped program is pointless, since you cannot edit anyway. The easiest would be to look at the help. Takes 5 seconds and is much faster than posting here and waiting for an answer. 😄

From the help:

Note LabVIEW ignores this option in the following scenarios:

When you use the VI Server to load the VI. Use the Run VI method to run a VI you use the VI Server to load.
When you designate the VI as a startup VI in a built application. Startup VIs run when they are opened by default and LabVIEW overrides the option you set in this dialog box. You can configure a startup VI to not run when it is opened when you configure the build specification. On the Source File Settings page of theApplication Properties dialog box, click the Customize VI Properties button. In the VI Properties (Application Builder) dialog box, remove the checkmark from the Run when opened checkbox.

As you can see, the option is ignored for startup VIs.

If you need to enter values before running the main code, a state machine is the answer. have the program start up in the idle state, then progress into a processing state.

Re: Compiled vi always runs when opened, Labview 2013 bug?

LarsM — Wed, 20 Nov 2013 18:14:37 GMT

"You can configure a startup VI to not run when it is opened when you configure the build specification."

The help text contradicts what you are writing. Maybe you should follow your own advice.

Re: Compiled vi always runs when opened, Labview 2013 bug?

altenbach — Wed, 20 Nov 2013 18:56:02 GMT

I agree that the help is somewhat contradictory 😉

Re: Compiled vi always runs when opened, Labview 2013 bug?

0utlaw — Wed, 20 Nov 2013 19:11:18 GMT

I have to admit that I'm also a bit confused- the build option does seem to work, at least on my machine. Example attached. Built in 13.0.0. This KnowledgeBase also indicates that this should work:

KnowledgeBase 1MA7L97T: Why Does My LabVIEW Application Default to "Run When Opened"?

http://digital.ni.com/public.nsf/allkb/F5E0C938A602A7028625678D004B4F5A?OpenDocument

LarsM- Could you provide an example of a case where the option you're using fails?

Regards,

Re: Compiled vi always runs when opened, Labview 2013 bug?

JÞB — Wed, 20 Nov 2013 19:12:51 GMT

OK lets revisit it.

Yes you can get a startup vi to launch without running. note the two builds in the attached .zip

Why you would chose to launch an application without running the top-level vi is the point of our questions.

Christian got bit by a common miss-reading of that help file line- the "Run when opened" property cannot be set to "Use vi Property" this is the meaning behind "the setting is ignored. By default a start-up vi is set to run when opened irrespective of the vi properties. You can change it BUT, some would argue this should NEVER have been exposed since it is very bad programming practice. However: the attached zip contains a build of the same vi with each run when opened option set.

I hope I made it clear that this is a silly way to configure a build spec to get around coding a proper UI.

The source file is also attached.

Re: Compiled vi always runs when opened, Labview 2013 bug?

altenbach — Wed, 20 Nov 2013 19:21:35 GMT

Yes, I got confused. Back in LabVIEW 8.2 (?) there was a bug that did not allow the setting work (exe runs even if told not to in the builder). I think I even posted a workaround, placing a small while loop with an USR, that would immediately stop the VI when it run for the first time, but not at later runs.

In any case, disabling "run when openend" only makes sense when exe debugging is enabled. Also applications typically have the toolbar and LabVIEW specific menu entries removed, in which case you would not even be able to run the exe if it start as not running. 😮