Skip to content
Tutorials Center
My learning

Topics

Lesson 1 of 36 ยท Getting Started

What Is LabVIEW?

Learn what LabVIEW is, how graphical dataflow programming differs from text code, where engineers use it, and what you need before you start.

LabVIEW (Laboratory Virtual Instrument Engineering Workbench) is a graphical programming environment from NI (formerly National Instruments). Instead of typing lines of code, you draw a program as a diagram: boxes that do work, connected by wires that carry data. It is used heavily for measurement, test automation, instrument control, and industrial monitoring.

This lesson explains the big ideas so that the rest of the course makes sense. It is a conceptual track about a desktop product: LabVIEW is not available on this site. Everything you read describes menus and workflows from the real product, and the runnable examples are small, clearly labelled stand-ins written in JavaScript that model the same ideas. They are not LabVIEW output.

Programs are drawn, not typed

A LabVIEW program is called a VI (virtual instrument). Every VI has two linked windows:

  • The front panel is the user interface: knobs, graphs, buttons, text boxes.
  • The block diagram is the code: nodes, structures and wires.

The name "virtual instrument" comes from the original goal. A VI imitates a physical lab instrument, such as an oscilloscope or a function generator, with a panel you can look at and logic behind it.

Dataflow, not line by line

Text languages like C or Python run statements in the order you wrote them. LabVIEW uses dataflow: a node runs when all of its inputs have data, and it passes results to the nodes wired to its outputs. Two nodes with no wire between them have no defined order, and LabVIEW may run them in parallel.

Text code versus dataflow

Text code Runs top to bottom
Dataflow Runs when inputs arrive
Parallel Independent wires run together

Wires decide the order.

1 / 3

Where LabVIEW is used

  • Data acquisition (DAQ): read voltages, temperatures or strain from sensors through measurement hardware and log them.
  • Instrument control: drive oscilloscopes, power supplies and multimeters over GPIB, USB, Ethernet or serial.
  • Automated test: run a sequence of measurements on a product and report pass or fail.
  • Embedded and control: with add-on modules and hardware such as CompactRIO, run real-time and FPGA code.
  • Education and research: quickly build an experiment and see live graphs.

LabVIEW is strongest when you are close to hardware and need a user interface fast. It is less common for web servers, text processing or large business applications, where other languages fit better.

Strengths and trade-offs

Strengths: built-in charts and graphs, hardware drivers, easy parallelism, quick prototypes, and a visual form that engineers who are not full-time programmers often find natural.

Trade-offs: diagrams get messy without discipline, version control diffs of binary VIs are harder to read than text, and the product is commercial. Later chapters teach habits that keep diagrams tidy and teams productive. See clean diagrams and documentation.

G, the language

The language you draw in is named G. It has types, functions, loops, conditionals and subroutines (called subVIs), just like a text language. You will meet all of them: loops in while loops and for loops, and data types in numeric and boolean data.

Modeling dataflow with a stand-in

The runnable code below is not LabVIEW. It is a tiny JavaScript model of the dataflow rule: a node fires only once every input has a value. Add two numbers, then multiply by a third, and watch the order be decided by availability of data.

JS Dataflow stand-in: a node fires when all inputs are ready

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Notice that sending the multiplier first did not make Multiply run early. Wires, not line order, controlled execution. A second stand-in below mimics how a VI has controls (inputs) and indicators (outputs), with the diagram as a function between them.

JS A VI as controls, logic and indicators (stand-in)

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Real LabVIEW needs NI's installer and, for most uses, a license. NI has offered evaluation and non-commercial editions in the past; check NI's website for what is currently available.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What are the two windows of a VI?

    The front panel is the user interface and the block diagram holds the graphical code.
  2. 2. When does a node in a block diagram run?

    LabVIEW uses dataflow: a node fires once every input has data.
  3. 3. What is the graphical language of LabVIEW called?

    The language is called G.
  4. 4. Which task is LabVIEW best known for?

    LabVIEW is strongest close to hardware, measurement and test.

Summary

  • LabVIEW is a graphical programming environment from NI; the language is G.
  • A VI has a front panel (interface) and a block diagram (code).
  • Execution follows dataflow: nodes fire when all inputs have data, and independent paths can run in parallel.
  • It excels at measurement, instrument control, test and quick user interfaces.
  • On this site the runnable code is JavaScript stand-ins that model ideas; real LabVIEW is not available here.

Next: Installing LabVIEW and First Launch