LabVIEW

Developer(s)	National Instruments
Initial release	1986; 38 years ago (1986)
Stable release	LabVIEW NXG 5.1 LabVIEW 2024 Q3 / July 2024; 5 months ago (2024-07)
Written in	C, C++, C#
Operating system	Cross-platform: Windows, macOS, Linux
Type	Data acquisition, instrument control, test automation, analysis and signal processing, industrial control, embedded system design
License	Proprietary
Website	www.ni.com/labview

Laboratory Virtual Instrument Engineering Workbench (LabVIEW)^[1]: 3 is a graphical system design and development platform produced and distributed by National Instruments, based on a programming environment that uses a visual programming language. It is widely used for data acquisition, instrument control, and industrial automation. It provides tools for designing and deploying complex test and measurement systems.

The visual (aka graphical) programming language is called "G" (not to be confused with G-code). It is a dataflow language originally developed by National Instruments.^[2] LabVIEW is supported on a variety of operating systems (OSs), including macOS and other versions of Unix and Linux, as well as Microsoft Windows.

The latest versions of LabVIEW are LabVIEW 2024 Q3 (released in July 2024) and LabVIEW NXG 5.1 (released in January 2021).^[3] National Instruments released the free for non-commercial use LabVIEW and LabVIEW NXG Community editions on April 28, 2020.^[4]

The programming paradigm used in the LabVIEW "G" language is based on data availability. If there is enough data available to a function, it will execute. The execution flow is determined by the structure of a graphical block diagram (the LabVIEW-source code) on which the programmer places nodes and connects them by drawing wires. A node can be a control, indicator, structure, function, or recursively, another block diagram. An example of a simple four-node block diagram is two controls and an indicator wired to the addition function, causing the indicator to display the sum of the two controls. The wires connecting nodes propagate data as variables, and any node can execute as soon as all its input variables (data) become available. Since this might be the case for multiple nodes simultaneously, LabVIEW can conceptually execute in parallel.^[5]: 1–2 Multi-processing and multi-threading hardware is exploited automatically by the built-in scheduler, which multiplexes multiple OS threads over the nodes ready for execution.

LabVIEW integrates the creation of user interfaces (termed front panels) into the program development cycle. LabVIEW programs are collections of one or more virtual instruments (VIs). Each VI has three components, a front panel, back panel, and connector panel, all composed of nodes and wires represented graphically to the user. The front panel is built using controls and indicators. Controls are inputs, they allow a user to supply information to the VI. Indicators are outputs, they indicate or display the results based on the inputs given to the VI. The back panel consists of a block diagram containing the graphical source code. All of the objects placed on the front panel will appear in the back panel block diagram as terminals. The block diagram also contains structures and functions, chosen from a Functions palette, which perform operations on controls and supply data to indicators. The connector panel has terminals whose wires go to or come from nodes in the front and back panels, and is used to represent the VI within the back panel of upstream (calling) VIs and downstream (called) VIs to which it might be connected.

There are two ways to run a VI. It can be run by itself as a program, with the front panel serving as a user interface. Alternatively, it can be treated as a node that is dropped onto the block diagram of another VI and wired to its nodes through the connector panel. In that case it runs as a subroutine within a larger program, and the front panel controls the inputs and outputs of the VI node. Thus, each VI can be easily tested as a stand-alone program before being embedded as a subroutine into a larger program.

The "G" graphical approach allows non-programmers to easily build programs by dragging and dropping virtual representations of lab equipment with which they are already familiar. The LabVIEW programming environment includes examples and documentation to guide and simplify the creation of small applications. As with all introductory programming guides, the ease of construction of working "G" programs may cause the programmer to underestimate the expertise needed for high-quality "G" programming. For complex algorithms or large-scale code, a programmer must possess extensive knowledge of the special LabVIEW syntax and the topology of its memory management. The most advanced LabVIEW development systems offer the ability to build stand-alone applications. Furthermore, it is possible to create distributed applications that communicate using a simple client–server model which takes advantage of the inherently parallel nature of "G".

Applications in LabVIEW are typically designed using well-known architectures^{[citation needed]} known as design patterns. The most common design patterns for graphical LabVIEW applications are listed in the table below.

LabVIEW includes extensive support for interfacing to instruments, cameras, and other devices. Users interface to hardware by either writing direct bus commands (USB, GPIB, Serial) or using high-level, device-specific drivers that provide native "G" function nodes for controlling the device. National Instruments makes thousands of device drivers available for download on their Instrument Driver Network (IDNet).^[9]

LabVIEW has built-in support for other National Instruments products, such as the CompactDAQ and CompactRIO hardware platforms and Measurement and Automation eXplorer (MAX) and Virtual Instrument Software Architecture (VISA) toolsets.

LabVIEW includes a compiler that translates "G" code into native code for supported CPU platforms. The graphical code is converted into Dataflow Intermediate Representation, and then translated into chunks of executable machine code by a compiler based on LLVM. These code chunks are called by the "G" run-time engine, providing for fast, high-performance native execution of the graphical code. The LabVIEW syntax is strictly enforced during the editing process, and when "G" code is run or saved, the compiler is automatically invoked. "G" code is saved to a single binary file that contains both the source and executable code. Execution is controlled by the run-time engine, which contains some pre-compiled code to perform common tasks defined in the "G" language. The run-time engine manages execution flow, and provides a consistent interface to supported operating systems, graphic systems and hardware components. The use of a portable run-time environment makes the source code files portable across supported platforms. LabVIEW programs are slower than equivalent compiled C code, although it is often possible to mitigate speed issues with program optimizations.^[10]

LabVIEW includes a large number of libraries containing functions for data acquisition, signal generation, mathematics, statistics, signal conditioning, analysis, integration, filtering, and other specialized abilities such as data capture from hardware sensors. In addition, it includes MathScript, a text-based programming component with built-in functions for signal processing, analysis, and mathematics. MathScript can be integrated with graphical programming using script nodes and uses a syntax that is generally compatible with MATLAB.^[11]

LabVIEW is an inherently concurrent language, so it is very easy to program multiple tasks that are performed in parallel via multithreading, for example by drawing two or more parallel while loops and connecting them to two separate nodes. This provides a great benefit for test system automation, where it is common practice to run processes like test sequencing, data recording, and hardware interfacing in parallel.

Due to the longevity and popularity of the LabVIEW platform and the ability for users to extend its functions, a large ecosystem of third-party add-ons has developed via contributions from the community. Most of these add-ons are available for direct download and installation into LabVIEW using the VI Package Manager (VIPM),^[12] the official package manager for LabVIEW add-ons. National Instruments also hosts a marketplace for both free and paid LabVIEW add-ons, called the NI Tools Network.

There is a low-cost LabVIEW Student Edition aimed at educational institutions for learning purposes. There is also an active community of LabVIEW users who communicate through several electronic mailing lists (email groups) and Internet forums.

National Instruments provides a low cost LabVIEW Home Bundle Edition.^[13]

National Instruments provides a free-for-non-commercial use version called LabVIEW Community Edition.^[14] This version includes everything in the Professional Editions of LabVIEW, has no watermarks, and includes the LabVIEW NXG Web Module for non-commercial use. These editions may also be used by K-12 schools.^[15]

LabVIEW is a proprietary product of National Instruments. Unlike common programming languages such as C or Fortran, LabVIEW is not managed or standardized by any third-party standards committee.

Since the "G" language is non-textual, common software tools such as versioning, side-by-side (or diff) comparison, and version code change tracking cannot be applied in the same manner as for textual programming languages. There are, however, some source code control (versioning) tools that do enable code comparison and merging, such as subversion, CVS and Perforce.^[16][17][18]

In 2005, starting with LabVIEW 8.0, major versions are released around the first week of August, to coincide with the annual National Instruments conference NI Week, and followed by a bug-fix release the following February.

In 2009, National Instruments began naming releases after the year in which they are released. A bug-fix is termed a Service Pack, for example, the 2009 service pack 1 was released in February 2010.

In 2017, National Instruments moved the annual conference to May and released LabVIEW 2017 alongside a completely redesigned LabVIEW NXG 1.0 built on Windows Presentation Foundation (WPF).

OpenG and LAVA Code Repository (LAVAcr) serve as repositories for a wide range of Open Source LabVIEW applications and libraries. SourceForge has LabVIEW listed as one of the possible languages in which code can be written.

VI Package Manager has become the standard package manager for LabVIEW libraries. It is very similar in purpose to Ruby's RubyGems and Perl's CPAN, although it provides a graphical user interface similar to the Synaptic Package Manager. VI Package Manager provides access to a repository of the OpenG (and other) libraries for LabVIEW.

Tools exist to convert MathML into "G" code.^[28]

National Instruments also offers Measurement Studio, a product that offers many of the test, measurement, and control abilities of LabVIEW as a set of classes for use with Microsoft Visual Studio. This allows developers to harness some of LabVIEW's strengths within the text-based .NET Framework. National Instruments also offers LabWindows/CVI as an alternative for ANSI C programmers.

When applications need sequencing, users often use LabVIEW with the National Instruments TestStand test management software.

The Ch interpreter is a C/C++ interpreter that can be embedded in LabVIEW for scripting.^[29]

DSP Robotics' FlowStone DSP also uses a form of graphical programming similar to LabVIEW but is limited to the robotics industry.

LabVIEW has a direct node with modeFRONTIER, a multidisciplinary and multi-objective optimization and design environment, written to allow coupling to almost any computer-aided engineering tool. Both can be part of the same process workflow description and can be virtually driven by the optimization technologies available in modeFRONTIER.

• Comparison of numerical-analysis software
• Dataflow programming
• Fourth-generation programming language
• Visual programming language
• Graphical system design

Related software titles

• Lego Mindstorms NXT, whose programming environment NXT-G is based on LabVIEW and can be programmed within LabVIEW.
• 20-sim
• LabWindows/CVI
• MATLAB/Simulink
• Virtual instrumentation
• CompactDAQ
• CompactRIO
• TOMVIEW

Free and open-source packages

• PWCT — GPL license
• DRAKON — public domain, with some open-source components

• Bress, Thomas J. (2013). Effective LabVIEW Programming. [S.l.]: NTS Press. ISBN 978-1-934891-08-7.
• Blume, Peter A. (2007). The LabVIEW Style Book. Upper Saddle River, NJ: Prentice Hall. ISBN 978-0-13-145835-2.
• Travis, Jeffrey; Kring, Jim (2006). LabVIEW for Everyone : Graphical Programming Made Easy and Fun (3rd ed.). Upper Saddle River, NJ: Prentice Hall. ISBN 0-13-185672-3.
• Conway, Jon; Watts, Steve (2003). A Software Engineering Approach to LabVIEW. Upper Saddle River, NJ: Prentice Hall PTR. ISBN 0-13-009365-3.
• Olansen, Jon B.; Rosow, Eric (2002). Virtual Bio-Instrumentation : Biomedical, Clinical, and Healthcare Applications in LabVIEW. Upper Saddle River, NJ: Prentice Hall PTR. ISBN 0-13-065216-4.
• Beyon, Jeffrey Y. (2001). LabVIEW Programming, Data Acquisition and Analysis. Upper Saddle River, NJ: Prentice Hall PTR. ISBN 0-13-030367-4.
• Travis, Jeffrey (2000). Internet Applications In LabVIEW. Upper Saddle River, NJ: Prentice Hall PTR. ISBN 0-13-014144-5.
• Essick, John (1999). Advanced LabVIEW Labs. Upper Saddle River, NJ: Prentice Hall. ISBN 0-13-833949-X.

• Desnica V, Schreiner M, Vladan; Schreiner, Manfred (October 2006). "A LabVIEW-controlled portable x-ray fluorescence spectrometer for the analysis of art objects". X-Ray Spectrometry. 35 (5): 280–286. Bibcode:2006XRS....35..280D. doi:10.1002/xrs.906. Archived from the original on 2010-08-18.
• Keleshis C, Ionita C, Rudin S, C.; Ionita, C.; Rudin, S. (June 2006). "Labview [sic] graphical user interface for micro angio-fluoroscopic high resolution detector". Medical Physics. 33 (6): 2007. doi:10.1118/1.2240285.{{cite journal}}: CS1 maint: multiple names: authors list (link)
• Fedak W., Bord D., Smith C., Gawrych D., Lindeman K., W.; Bord, D.; Smith, C.; Gawrych, D.; Lindeman, K. (May 2003). "Automation of the Franck-Hertz experiment and the Tel-X-Ometer x-ray machine using LABVIEW". American Journal of Physics. 71 (5). AAPT: 501–506. Bibcode:2003AmJPh..71..501F. doi:10.1119/1.1527949.{{cite journal}}: CS1 maint: multiple names: authors list (link)

• Belletti A., Borromei R., Ingletto G., A.; Borromei, R.; Ingletto, G. (September 2006). "Teaching physical chemistry experiments with a computer simulation by LabVIEW". Journal of Chemical Education. 83 (9). ACS: 1353–1355. Bibcode:2006JChEd..83.1353B. doi:10.1021/ed083p1353.{{cite journal}}: CS1 maint: multiple names: authors list (link)
• Moriarty P.J., Gallagher B.L., Mellor C.J., Baines R.R., P. J.; Gallagher, B. L.; Mellor, C. J.; Baines, R. R. (October 2003). "Graphical computing in the undergraduate laboratory: Teaching and interfacing with LabVIEW". American Journal of Physics. 71 (10). AAPT: 1062–1074. Bibcode:2003AmJPh..71.1062M. doi:10.1119/1.1582189.{{cite journal}}: CS1 maint: multiple names: authors list (link)
• Lauterburg, Urs (June 2001). "LabVIEW in Physics Education" (PDF). A White Paper About Using LabVIEW in Physics Demonstration and Laboratory Experiments and Simulations.
• Drew SM, Steven M. (December 1996). "Integration of National Instruments' LabVIEW software into the chemistry curriculum". Journal of Chemical Education. 73 (12). ACS: 1107–1111. Bibcode:1996JChEd..73.1107D. doi:10.1021/ed073p1107.
• Muyskens MA, Glass SV, Wietsma TW, Gray TM, Mark A.; Glass, Samuel V.; Wietsma, Thomas W.; Gray, Terry M. (December 1996). "Data acquisition in the chemistry laboratory using LabVIEW software". Journal of Chemical Education. 73 (12). ACS: 1112–1114. Bibcode:1996JChEd..73.1112M. doi:10.1021/ed073p1112.{{cite journal}}: CS1 maint: multiple names: authors list (link)
• Ogren PJ, Jones TP, Paul J.; Jones, Thomas P. (December 1996). "Laboratory interfacing using the LabVIEW software package". Journal of Chemical Education. 73 (12). ACS: 1115–1116. Bibcode:1996JChEd..73.1115O. doi:10.1021/ed073p1115.
• Trevelyan, J.P. (June 2004). "10 Years Experience with Remote Laboratories" (PDF). International Conference on Engineering Education Research. ACS.

• Official website