Startup VIs vs Startup Executables on a Real-Time Operating System

Primary Software: LabVIEW Modules>>Real-Time Module
Primary Software Version: 8.5.1
Primary Software Fixed Version: N/A
Secondary Software: N/A

Problem:
On a regular operating system, the main benefits of building an executable is that an executable does not require the LabVIEW development environment to run. The LabVIEW development environment doesn't exist on a Real-Time Operating system, so what is the benefit of building a Real-Time executable and what, exactly, is a Startup VI?

Solution:
There are several benefits to building a Real-Time Application, such as:

An executable can be configured as a Startup executable, which will automatically begin execution when the controller boots up
Building an exe allows you to remove unnecessary source elements (such as block diagrams, unused polymorphic VI instances, etc.), reducing file size and overhead
It is possible to remotely debug startup executables in the LabVIEW development environment

Note that it is still possible to configure Startup VIs that will run automatically when the Real-Time controller boots up without having to compile them. Please see KnowledgeBase 3TFFQLQS Configuring Startup VIs on LabVIEW Real-Time Targets with a Source Distribution for more information on how to do this.

Startup executables should not be confused with Startup VIs defined in an executable's Build Specification. Startup VIs will run when the executable is launched and not necessarily when the controller boots up. To set an executable to start automatically, right-click the build specification in project and choose Set as Startup before deploying it.

Report Date: 05/09/2008
Last Updated: 04/02/2009
Document ID: 4L89M48A

Your Feedback!

Poor | Excellent

Yes

Document Quality?

Answered Your Question?

Please Contact NI for all product and support inquiries.