Compiled vi always runs when opened, Labview 2013 bug?

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.
Lars Melander
Uppsala Database Laboratory, Uppsala University

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.
Spoiler (Highlight to read)
See, asking a question (or at least explaining what behavior you want) gets more specific answers.
See, asking a question (or at least explaining what behavior you want) gets more specific answers.
Jeff

Similar Messages

Why does compiled (EXE) VI run when you double-click the icon even though I un-checked "Run When Opened"?

My VI code uses the VI's that came with the NI USB-8451 USB-to-SPI converter. Before compiling I needed to use one of those VI's to select the particular USB device that I'm trying to address, then I click the Run button. But after I compile my code into an EXE file, and then double-click the executable file it immediately starts running without allowing me to select the USB device - even though I un-checked the "Run When Opened" box. In fact I also un-checked the Show Menu Bar and Show Scroll Bars boxes as well, yet it shows both of them. What am I doing wrong?

It seems silly to start and stop a built LabVIEW application from the toolbar. A complete application should always run and have the LabVIEW toolbar hidden. A user of you code is not supposed to be familiar with LabVIEW mechanics.
You should do all this in code. Really!
Do a nice state machine with at least two states. (1) a state for where the device has not been entered and is simply waiting for your input, and (2) another state that verifies your device input and hands it to the rest of the code for afterwards.
Still, what LabVIEW version do you have. Did you set the "run when openend" setting in the application builder for the desired VI or just in the VI itself?
LabVIEW Champion . Do more with less code and in less time .

In application builder the top level vi is always set to "run when opened"; how do I turn this off so I don't have to change it each and every time I build a .exe??

I build a lot of executables using Application Builder under LabVIEW and in every one I build, I don't want the top level vi to take off and run when I open the executable. Currently, I edit each .exe I build within Application Builder and change the option of "run when opened" from Yes to No for the top level vi. All the other subvi's are already set to No. It would seem as though there should be some way to "turn this off" if you will so the top level vi is not always set to "run when opened" by default within Application Builder. Is there such a solution that anyone knows of?? Any help would be apprec
iated... thanks...

Indeed the Application builder forces "run when opened" to true for top levels VIs. If you don't want your VI to make any real work when the application starts, you should simply put a do-nothing loop in the beginning of the VI that will loop until the user presses a boolean. It will be more intuitive for users to press a Run button on the FP than clicking on the white Run arrow in the bar.
LabVIEW, C'est LabVIEW

Is it possible to have a VI "run when opened" when accessed via Internet Explorer?

I am trying to get a remote panel application to "run when opened" when is accessed via Internet explorer. I have multiple remote panel licenses on the server and the VI is Re-entrant. The application works well except for this issue. Having the VI "Run When Opened" via IE is very important to the user. As is, when IE opens, the user must click on the panel image once to get the VI's attention and then again on the start arrow to run the program. Is there any way around this or a way to simplify the process?
Thanks.
Solved!
Go to Solution.

This is actually the intended operation of remote front panels, however, we can simplify the operation to meet closer with what your customer wants. Basically, if you were to always have your program run in somewhat of an idle state, you can use the Application Control>>Property node for 'RemotePanel.ConnToClients' property to determine when a user is connected and run the proccess of the program as soon as a connection is detected. When no connection is detected you could have the program run in an idle state. The attached screenshot shows a general way to do this. Have a good evening!
-Bob
-Bob
Attachments:
idle state.JPG ‏45 KB

Why does application run when opened

If I run the executable it pops up and automatically runs. I had thought this was by design, but I have one application I built that does not automatically execute when called. I can't see any difference in the way I set them up, nor do I see a control in the application builder interface.
SOOOOooo, how do I keep the applications from automatically running when called?
-Regards
eximo
UofL Bioengineering M.S.
Neuronetrix
"I had rather be right than be president" -Henry Clay
Solved!
Go to Solution.

This is done in the main VI's properties. See if you can find it in the attached screenshot.
You can also override it in the build spec.
Attachments:
run when opened.png ‏45 KB
customize properties.png ‏49 KB

Running Datasocket in labview 2013 open labview runtime engine 7.0

Hello All,
I am trying to communicate with a COGNEX camera using Labview 2013. I am using Datasocket to read tags from cognex OPC server.
but when I open labview and run the code for the first time. An installer will automatically pop up trying to install labview runtime engine 7.0.
When i cancel the installation datasocket throws an error. Again if i run second time, datasocket works fine and communicate with cognex camera using OPC.
This problem comes everytime I open labview and run the datasocket. I cancel the installer. second time onwards when i run the code everything works fine.
This is actually annoying and i doubt how things will work when i make an executable.
Need help.
Is this due to datasocket version installed... how to resolve this.

Hi phil,
That is interesting that you were unable to find the offending key that the installation is having trouble with. Do you have Administrator privileges on your computer? You may even want to try to log in as the actual Administrator itself to make sure that you have access to all of the proper registry keys. Also, I was going to say that I do think you're right with Windows XP not having the Scanreg/fix function, but there are several free programs that you can download as registry checkers. You may want to try one of those to see if you can find the key and give it the proper permission.
As far as the other part of your question, the Run-Time Engines are very important for LabVIEW to be able to run, but the 7.1.1 Run-Time Engine should not be affecting a LabVIEW 8.2 installation as it will use the 8.2 Run-Time Engine. One thing that you can do is go into your Control Panel under Add or Remove Programs>>National Instruments Software and you can try and repair/modify your Run-Time Engine there. If you already have the 7.1.1 Run-Time Engine on your computer, this is where it will show up so you can make any changes you want. Also, if you go to www.ni.com and click on "Drivers and Updates" on the right, you will be able to find the Run-Time Engine there that you will need, but I would definitely try using a downloadable registry checker first before attempting to change any of the software that is currently on your computer. As stated in the Knowledgebase article, this is actually an error from Windows saying that the registry key does not have the proper permission settings, so I am reluctant to say that downloading the new Run-Time Engine from our website will help much. Please try some of these suggestions out and let me know how they work out for you. Thanks!
Regards
Noah R
Applications Engineering
National Instruments

Schedule report re-runs when opening

Hi,
I have a scheduled discover report in Discoverer 4.1.48 version, when opening that scheduled report its re-run the query again.
Please let me know, the reason.
BR,
Uma

Hi Uma
One of the reasons for this happening is that the query could be a fan trap. Discoverer will nearly always tell you that the results are invalid and suggest a rerun when there is a fan trap.
This was recognised as a bug but was only corrected in the 10.1.2.2 release of Discoverer. Many other scheduling bugs were fixed in this and subsequent releases. Have you considered upgrading?
Best wishes
Michael

Reports in Favorite Reports did not run when open

In SCOM 2012, I have run a few reports with the report template in the default SCOM management pack and saved them in the Favorite Report. When I open the saved reports at the Favorite Report again, they suppose to be run automatically. However, when I open
the report, it stopped at the parameters page and I need to click the run button explicitly. Does any one know why it is so and how can I make it run automatically when I open the reports which I have saved in the Favorite Report.
Thanks a lot for any advice.

Thanks a lot for your comment.
First of all, there is no error at all and no message in the event log that related to this issue. The report saved in Favorite Reports did able to run successfully without any error just only I need to click the run button manually. Suppose it should run
automatically, right?
Second, there actually two MS (say MS01 and MS02) and both of them point to the same SSRS. Say for example, the report saved in the Favorite Reports at the Operation console on MS01 will not run automatically when open it. The behavior is the same when using
the Operation console on MS02 to open that particular report saved on MS01.
However, when I save a report in the Favorite Reports at the Operation console on MS02, it will run automatically when I reopen it. Then I use the Operation console on MS01 to reopen this report, it will run automatically as expected.
In short, report saved in MS01 got problem no matter where you open it. Report saved in MS02 got no problem no matter where you open it. It is very weird and I don't know what setting in SCOM 2012 would affect this behavior. In a big head right now...

Why are some of my folders always expanded when opening my external hard drive on my iMac?

Certain folders are always expanded when I plug in and open my external hard drive and its more of a pain than anything to scroll through them all. If i close them, next time I open the hard drive folder they are open again!

Try re-indexing the mailbox. This can take awhile if you have a lot of mail.
Reindex messages

Script running when opening a file.

I am new at this so forgive me if this is a stupid question.
I have a script that allows me to insert today's date in a text box. So far, it works well when I run the script. However, I would like the script to automatically run when I open the file. This would save me from having to update the date manually.
Is there a way to accomplish that?

Hi,
try to put "#target indesign" at the bigening of you sript code, then you can launch the script from out of InDesign

Exporter plug-in doesn't run when open by clicking .prproj file

Hi everyone!
I am creating an exporter plug-in. It works fine when I open Premiere, open a project and choose to export using my plug-in. But when i open a project directly by double clicking the project file (like untitled.prproj), my plug-in always show up a "Error compiling movie" message.
I use log4cxx to help track the plug-in, but no log was created, so my guess is that the plug-in has not even been loaded.
Could anyone tell be the differences between starting Premiere -> open a project and open a project directly by double clicking its .prproj file. In both case, which file is loaded and which file is not?
I'm very appreciated if anyone would have the same problem and tell me how to fix this. I'm really stuck here

The version is CS5.5.
And my steps are:
1. open the project by double clicking the .prproj file
2. select a file in the project
3. Choose File -> Export -> Media
4. Select my plug-in in the drop down list and choose Export
=> Error
But if take these step:
1. Open Premiere Pro
2. select a project
3. select a file in the project
4. Choose File -> Export -> Media
5. Select my plug-in in the drop down list and choose Export
the plug-in run just fine.
So I think that there are something different between opening a project directly and open Premiere and choose a project. Could you verify this for me? Thanks.

Paradox concerning DEP (Data Execution Prevention) when opening LabVIEW

When I try to launch LabVIEW, DEP (Data Execution Prevention) prevents me from opening it. I have followed instructions and attempted to make an exception for LabVIEW, but I get a message saying the following:
"This program must run with data execution protection (DEP) enabled.
You cannot turn off DEP for this program."
It seems that I need this "DEP" program to run LabVIEW, but at the same time it is keeping me from running it. Help would be very much apprecaited.
Thanks in advance!
Cailin

Hello Cailin,
The Data Execution Prevention (DEP) is a security feature included in
modern Microsoft Windows operating systems that is intended to prevent
malicious code from running on the system.
Here are two methods to fixing this problem:
Method 1:
Follow these steps to add an exception for the program from the DEP error message:
When you receive the error message click Change Settings.
Select the check box next to the program, and then click Apply.
When you are prompted to restart your computer, click OK two times, and then restart your system.
Method 2:
You can also add an exception for the program by using System Properties in Control Panel. To do this, follow these steps:
Click Start, click Run, type sysdm.cpl, and then click OK.
Click the Advanced tab, click Performance, and then click Settings.
In Performance Options, click the Data Execution Prevention tab, and then click Add.
In the Open dialog box, locate and then click the program.
Click Open, click Apply, and then click OK. When you are prompted to restart your computer, click OK.
David A.
National Instruments
Applications Engineer

"This command is not available because no document is open" when opening Word 2013

Whenever I launch Word 2013, the error message "This command is not available because no document is open" appears. This causes an issue that prevents a program called SNAP used for education from working properly. I've been able
to work around the error message itself by disabling the start screen for Word 2013, so it opens straight into a blank document, but SNAP still does not work.
I've not been able to make any headway researching the issue. It seems most people run into this error scripting or coding, and it's usually that they try to save a document or something before they actually make the document.
I don't know that it's relevant, but this is occuring on a 32-bit Windows 7 box.

Hi, I work with SNAP Technical Support and this is a known issue with Cengage's KPDO add-in.
Cengage Keyboarding's Add-In to Word prevents the SnapPlayer application from communicating with Word. This add-in will
need to be disabled.
You
may see the following error in the log when this occurs:<Exception>System.Runtime.InteropServices.COMException
(0x80080005): Retrieving the COM class factory for component with CLSID {000209FF-0000-0000-C000-000000000046} failed due to the following error: 80080005.at
SnapPlayer.Skills.Applications.Word.Launch() in D:ProjectsVisual StudioSnap PlayerSnapSkillsApplicationsWord.vb:line 234
Disabling the add-in will resolve the issue.

After stop using bootcamp my Macbook Pro always stuck when open.

A week ago I had decided to stop using Windows Vista through Boot Camp because I ran out hard disk spaces and I think Windows Vista has no long necessary for me, so I go to Utilities and go Boot Camp Assistant to deleted my Windows Vista. after I deleted my Windows every time I shut down my Mac and open up again it always stuck with black screen and asked (.....to press any keys) and I did but nothing happen and sometime it stuck with empty white screen, to open up my Mac without any problems I need to hold down the Option keyboard when I start up my Mac and wait until the Mac OS Disk show up and select then it will be okay.
Please tell me what should I do to avoid this problems every time I start up my Mac without keep holding Option key.

Check the setting in the Startup Disk pane of System Preferences.
(51888)

Cs3 stops running when opening a picture file

HI, Ihave CS3 extended running on Vista.Program ran find for months until yesterday, Whenever I try to open a picture file CS3 stops working and shut down. It doesnt matter what type file. I removed program amd reinstalled, still got same probelem. Any suggestions on how to solve? thanks Craig

Well, when stuff stops working it means that something happened that made it go haywire so what did you install/configure/do before this happened? have you installed some photoshop plugins? updated some drivers? installed some new software?
Another (far fetched) possibility would be that your anti-virus program is up to no good after an auto update so try temporarily deactivating it, maybe that will solve it.
Or if it's as Chris says, a problem with the printer driver, try uninstalling the driver completely, not just disable it or maybe go to Control Panel->Printers, right click on Adobe PDF(or some other "printer" from the list) and select "Set As Default Printer"

Compiled vi always runs when opened, Labview 2013 bug?

Similar Messages

Maybe you are looking for