Jump to content

run the LabVIEW program @ windows background


Recommended Posts



i want to launch the LabVIEW program automatically whenever windows starts.(windows xp or 7)

The program must be running at background so the computer operator shouldn't recognize that it is running.

if windows task manager not detects that is very good but not mandatory.




Link to comment

You need to run this as a windows service to achieve this.


There is no native way to do this but I have seen people use other tools that allow this. I can't remember the name but if you search run any exe as a service I imagine you would find something. What happens is that EXE runs as a service and then launches your EXE based on a registry key.

Link to comment

We looked at doing something similar to this a few years ago. What we needed was to monitor a temperature of a test fixture that could be used by a number of test rigs. This was achieved by adding a USB thermocouple device (NI USB-9211A and later an NI USB-TC01) and running a LabVIEW executable in the background that read the temperature and logged it to a database. We wanted this to start as soon as the PC was on regardless of if it had been logged in and didn't want the logging application be visible to the users so we ran it using a service.


Initially we used a tool called FireDaemon although we had some issues between this and our antivirus software so I created a small service to call a LabVIEW executable every 10 minutes. This is still working today and meets all our requirements. I posted a summary of this on my blog although there is no much detail there (contact me if you want any further details).


One important thing to remember is if you run as a service (or are calling a LabVIEW exe from a service) there can be no user input. Don't try and update a front panel and make sure all errors are handled so no dialogue boxes appear.

Link to comment

We use FireDaemon. As Swinders said you cannot have any UI when running as a service in Windows after XP/Server 2003. In the end we found the best way to handle per-instance configuration was to pass data in environment variables, which are settable in FireDaemon (which does have a UI for configuration) on a per-instance basis and easily read from the target application using a WinAPI call.


If you want a free solution, try srvany from Microsoft.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.