Revision as of 02:53, 19 August 2004 editDanakil (talk | contribs)2,873 editsm cat← Previous edit | Revision as of 17:30, 27 August 2004 edit undo68.38.97.141 (talk) Add mention of labview drivers and free alternatives to LabviewNext edit → | ||
Line 3: | Line 3: | ||
LabVIEW programs are called virtual instruments or simply VIs. Each virtual instrument has two components, a ] and a front panel. Controls and indicators on the front panel allow an operator to input data into or extract data from an already running virtual instrument. In terms of performance, LabVIEW includes an actual ], so the graphical code is compiled, rather than interpreted. | LabVIEW programs are called virtual instruments or simply VIs. Each virtual instrument has two components, a ] and a front panel. Controls and indicators on the front panel allow an operator to input data into or extract data from an already running virtual instrument. In terms of performance, LabVIEW includes an actual ], so the graphical code is compiled, rather than interpreted. | ||
The most capable alternatives to LabVIEW would be text-based programming languages such as ] |
The most capable alternatives to LabVIEW would be text-based programming languages such as ], ], or ]; however, these approaches require specific skills to use that LabVIEW avoids - the graphical approach allows non-programmer users to construct sophisticated systems by simply dragging and dropping virtual representations of the lab equipment that they are already used to, allowing them to remain focused on their application instead of the details of arcane programming languages. Often another reason LabView is implemented is the availability of LabView drivers for data acquisition cards. An alternative driver framework for ] is the ] driver library. | ||
One of the main benefits of LabVIEW is that people with little or no previous programming experience are able to write programs and deploy test solutions in a minimal amount of time. | One of the main benefits of LabVIEW is that people with little or no previous programming experience are able to write programs and deploy test solutions in a minimal amount of time. |
Revision as of 17:30, 27 August 2004
LabVIEW is a graphical programming language from National Instruments. Originally released for the Apple Macintosh in 1986, LabVIEW is used for data acquisition, instrument control, and industrial automation on a variety of platforms including Microsoft Windows, various flavors of UNIX, Linux, and MacOS.
LabVIEW programs are called virtual instruments or simply VIs. Each virtual instrument has two components, a block diagram and a front panel. Controls and indicators on the front panel allow an operator to input data into or extract data from an already running virtual instrument. In terms of performance, LabVIEW includes an actual compiler, so the graphical code is compiled, rather than interpreted.
The most capable alternatives to LabVIEW would be text-based programming languages such as C, Visual Basic, or Python; however, these approaches require specific skills to use that LabVIEW avoids - the graphical approach allows non-programmer users to construct sophisticated systems by simply dragging and dropping virtual representations of the lab equipment that they are already used to, allowing them to remain focused on their application instead of the details of arcane programming languages. Often another reason LabView is implemented is the availability of LabView drivers for data acquisition cards. An alternative driver framework for Linux is the Comedi driver library.
One of the main benefits of LabVIEW is that people with little or no previous programming experience are able to write programs and deploy test solutions in a minimal amount of time.
The newest version of LabVIEW is version 7.1.
Category: