Editing LabVIEW (section)

==  Features and Resources ==
{{Advert section|date=July 2022}}
=== Interfacing to devices ===
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).<ref>{{cite web |title=3rd Party Instrument Drivers - National Instruments |url=http://www.ni.com/downloads/instrument-drivers/ |url-status=live |archive-url=https://web.archive.org/web/20141128134304/http://www.ni.com/downloads/instrument-drivers/ |archive-date=2014-11-28 |website=www.ni.com}}</ref>

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.

=== Code compiling and execution ===
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 system|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.<ref>{{cite web|url=https://www.ni.com/pl-pl/support/documentation/supplemental/10/ni-labview-compiler--under-the-hood.html#section-1599648034|title=NI LabVIEW Compiler: Under the Hood|date=4 February 2020|website=ni.com}}</ref>

=== Large libraries ===
LabVIEW includes a large number of [[Library (computing)|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]].<ref>{{cite web|title=LabVIEW MathScript RT Module|url=http://www.ni.com/labview/mathscript/|website=www.ni.com|url-status=live|archive-url=https://web.archive.org/web/20160805161725/http://www.ni.com/labview/mathscript/|archive-date=2016-08-05}}</ref>

=== Parallel programming ===
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.

=== Ecosystem ===
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),<ref>{{Cite web|url=https://www.vipm.io/desktop|title=VIPM Desktop|website=www.vipm.io|access-date=2023-06-09}}</ref> 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''.

=== User community ===
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 list]]s (email groups) and [[Internet forum]]s.

===Home Bundle Edition===
National Instruments provides a low cost LabVIEW Home Bundle Edition.<ref>{{cite web|url=http://sine.ni.com/nips/cds/view/p/lang/en/nid/213095|title=LabVIEW Home Bundle for Windows - National Instruments|website=sine.ni.com|url-status=live|archive-url=https://web.archive.org/web/20160704163634/http://sine.ni.com/nips/cds/view/p/lang/en/nid/213095|archive-date=2016-07-04}}</ref>

=== Community Edition ===
National Instruments provides a free-for-non-commercial use version called LabVIEW Community Edition.<ref>{{Cite web|url=https://www.ni.com/en-us/shop/labview/select-edition/labview-community-edition.html|title=LabVIEW Community Edition - National Instruments|website=www.ni.com|access-date=2020-04-28}}</ref> 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.<ref>{{Cite web|url=https://www.ni.com/en-us/support/documentation/supplemental/20/labview-community-edition-usage-details.html|title=LabVIEW Community Edition Usage Details - National Instruments|website=www.ni.com|access-date=2020-04-28}}</ref>