Skip to content
Tutorials Center
My learning

Topics

Lesson 3 of 36 ยท Getting Started

Front Panel and Block Diagram

Learn how controls, indicators, terminals, nodes and wires fit together on a LabVIEW front panel and block diagram, with clear conventions for colors.

Every VI is built from two parts that mirror each other. Whatever you place on the front panel gets a matching terminal on the block diagram. Understanding that pairing, and the visual conventions LabVIEW uses, makes diagrams much easier to read. This lesson describes the real editor in words; the code samples are JavaScript stand-ins, not LabVIEW.

The front panel

The front panel holds controls and indicators:

  • A control is an input. The user (or a calling VI) sets its value. Examples: a numeric control, a knob, a switch, a text box the user types into.
  • An indicator is an output. The program sets its value for the user to read. Examples: a numeric display, a thermometer, a LED, a graph.

You add them from the Controls palette, which opens when you right-click on the front panel. Controls are grouped into Modern, System, Classic and others. Use Modern for most work and System if you want controls to look like the operating system's.

Any object can be changed between control and indicator: right-click it and choose Change to Indicator or Change to Control.

The block diagram

On the block diagram you find:

  • Terminals: one for every control and indicator. They are the doorway between the panel and the code.
  • Nodes: things that do work. This includes functions (Add, Multiply), subVIs, and structures such as loops.
  • Wires: connections that carry data from one terminal or node output to inputs.
  • Constants: fixed values you type directly on the diagram.

You open the Functions palette by right-clicking on the block diagram. It contains Programming (numeric, Boolean, string, array, cluster, comparison, timing), Measurement I/O, Instrument I/O, Mathematics, Signal Processing, and more.

Terminal conventions

Terminals follow strict visual rules:

  • A control terminal has its arrow on the right side and a thicker border. Data flows out of it.
  • An indicator terminal has its arrow on the left side. Data flows in to it.
  • The background colour tells you the data type: for example orange for floating point numbers, blue for integers, green for Booleans, pink for strings.

Wire colors

Orange Floating point
Blue Integer
Green Boolean
Pink String

Thickness shows scalar, 1D or 2D.

1 / 2

Wire style also encodes shape. A scalar is a thin wire, a 1D array is thicker, and a 2D array thicker still. Clusters are brown or pink depending on contents. A broken wire appears as a dashed black line with a red X in the middle; the VI cannot run until you fix it. Right-click the broken wire and choose List Errors, or press Ctrl+L, to see the cause.

Connecting wires

Hover the Wiring tool (it appears automatically near a terminal) and click the source terminal, then click the destination. LabVIEW highlights valid destinations. Useful details:

  • You can tap the wire's corner with a click to turn it.
  • Ctrl+B removes all broken wires, but check why they broke first.
  • Ctrl+Shift and drag on an empty area to pan.
  • Wires cannot connect an output to another output, or two different incompatible types without conversion.

When types differ slightly (for example an integer wired into a double input) LabVIEW shows a small coercion dot on the terminal. It means an automatic conversion happened. This is usually fine, but it can hide precision or overflow problems; see numeric and boolean data.

Running a VI

The toolbar at the top of either window has:

  • Run (white arrow). Runs once. It turns into a broken arrow when the VI has errors.
  • Run Continuously (two curved arrows). Re-runs the VI forever. Avoid it in real code.
  • Abort (red octagon). Stops immediately without cleanup. Use it only when stuck.
  • Pause.
  • Highlight Execution (light bulb). Slows the run and shows data moving along wires. A wonderful teaching and debugging tool; see dataflow execution model.

Modeling the panel and diagram

This stand-in separates the two halves of a VI in JavaScript. panel holds controls and indicators; diagram reads controls and writes indicators. It mirrors how terminals work. It is not LabVIEW.

JS Stand-in: panel versus diagram

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

No output.

A second stand-in models wire type checking: connecting a string to a numeric input is refused, while a compatible number is accepted with a coercion note.

JS Stand-in: can this wire connect?

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

No output.

Name every control and indicator clearly. The label is also the name you will see on the diagram and, later, on the connector pane of a subVI.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which object is an input that the user sets?

    Controls provide data; indicators display it.
  2. 2. What does a broken wire look like?

    A broken wire is dashed with a red X, and the VI cannot run.
  3. 3. What color is a floating-point wire?

    Floating point is orange, integers are blue, Booleans green, strings pink.
  4. 4. Which shortcut flips between the front panel and block diagram?

    Ctrl+E toggles between the two windows of a VI.

Summary

  • Front panel: controls (inputs) and indicators (outputs). Block diagram: terminals, nodes, wires, constants.
  • Every panel object has a matching terminal on the diagram.
  • Wire color shows type and wire thickness shows shape; a dashed wire with a red X is broken.
  • A coercion dot means LabVIEW converted a number type automatically.
  • Highlight Execution shows data moving along wires and is the best way to see dataflow.

Next: Your First VI: A Temperature Converter