Virtual Instrument: Difference between revisions
New page: This is a stub. Please expand this page and make it valuable by adding more information. |
Added some initial content for VI |
||
| Line 1: | Line 1: | ||
VI stands for '''V'''irtual '''I'''nstrument, the basic building block of programs written in [[LabVIEW]]. It is similar to a function or subroutine in other programming languages. It includes the [[Front Panel]] (containing [[Controls]] and [[Indicators]]), the [[Block Diagram]] (containing Control Terminals, Wires, and Structures and various other [[GObject]] nodes), the VI's [[Icon]] and its [[Connector Pane]] (as well as compiled executable code which is hidden behind the scenes). | |||
The term Virtual Instrument is a play off of the fact that LabVIEW applications are designed for writing software that simulates the functionality of instruments -- rather than being a physical instrument on a laboratory bench, they are virtual and exist in software. | |||
LabVIEW VIs are saved as *.vi files in a proprietary binary format defined by [[National Instruments]], the makers of LabVIEW. | |||
Revision as of 23:07, 18 March 2007
VI stands for Virtual Instrument, the basic building block of programs written in LabVIEW. It is similar to a function or subroutine in other programming languages. It includes the Front Panel (containing Controls and Indicators), the Block Diagram (containing Control Terminals, Wires, and Structures and various other GObject nodes), the VI's Icon and its Connector Pane (as well as compiled executable code which is hidden behind the scenes).
The term Virtual Instrument is a play off of the fact that LabVIEW applications are designed for writing software that simulates the functionality of instruments -- rather than being a physical instrument on a laboratory bench, they are virtual and exist in software.
LabVIEW VIs are saved as *.vi files in a proprietary binary format defined by National Instruments, the makers of LabVIEW.