Menu

Theme

Learn and fix · Fix · CHECKED ON 5.0.0

Logisim red wire, blue wire and the other wire colours, and how to fix each

Red (value E) means two outputs drive the same wire with different values. Blue (value U, called X in older versions) means nothing drives the wire, often because a wire end is not touching a port. Orange with Incompatible widths means the components on that wire have different bit widths. Grey everywhere after opening a file means the simulation has not shown its values yet: click once on the canvas or press Ctrl+R (Reset Simulation).
FOR
Logisim-evolution 5.0.0, classic 2.7.1 where noted
CHECKED
11 Nov 2026
FIX TIME
about 2 min
Checked against Logisim-evolution 5.0.0 on 3 machines
On this page

What do you see?

Colours are Logisim's own defaults. They can be changed in Preferences, and some courses change them for colour-blind students. Every swatch carries its letter.

Red wire, E value: E

Two outputs drive the same wire with different values, or an error value is travelling along it. Equal values give that value.

ABY
Pins A and B tied to one wire: with A = 1 and B = 0 the wire is E.

Likely causes, most common first

  1. Two outputs on one wire that disagree. F07
  2. Two enabled buffers on a shared bus with different values. F10
  3. A feedback loop with no stable state. F06
  4. An error coming out of a subcircuit.

How to find it

  • Trace back from the red wire to every output pin or gate output attached to it.
  • Tunnels with the same label count as the same wire.
  • Open each subcircuit and look for red inside.

Fix

  • Remove one driver, or select between them with a multiplexer.
  • On a shared bus, use Controlled Buffers and enable only one at a time.
  • Do not delete wires until the colour goes away: find the second driver.

We tested this in Logisim-evolution 5.0.0 (F07, F10).

Full section belowControlled BufferTunnelsSubcircuits

Not this? Try

All colours at a glance

Colour Value Meaning Most common cause First fix Evidence
Bright green The wire carries 1 Normal None F03
Dark green The wire carries 0 Normal None F03
Black, thick bus A wire wider than one bit Normal None Logisim default
Blue Nothing drives the wire Wire end not on a port Reconnect it F08
Red Drivers disagree, or an error Two outputs on one wire Remove or select between them F07, F06
Orange Bit widths differ 4-bit wire into a 1-bit pin Match Data Bits F09
Grey no value Not shown yet File just opened Click the canvas or press Ctrl+R F45, F49

Only red, blue, orange and grey need action. The other rows are the circuit working.

LAB lab-lnx · Linux lab5.0.02026-11-09

The same Logisim-evolution 5.0.0 window after the simulation was reset. The first wire is bright green with pin value 1, the two wires driven by two outputs are red with E, the wire nothing drives is blue with U, and the width-mismatch wire stays orange.

Four cases in one circuit after a reset: green, red, blue and orange with Incompatible widths at the bottom. The pin on the blue wire is labelled X in our file but reads U. Linux lab with a virtual display, 5.0.0, 9 Nov 2026.lab-lnx-le500-wire-colours-after-reset-01
After a reset: green wire at 1, two red wires with E, a blue wire with U, an orange width-mismatch wire.

You can open the same four cases as circ-wire-colors-showcase.circ and compare its command-line table with the one we captured (see Downloads below).

Red wire and E: two outputs disagree

When two outputs drive one wire, Logisim compares what they send. If the values are equal, the wire carries that value. If they differ, the wire is red and reads E (F07). Our smallest case ties two input pins to one wire and asks for the table:

Command-line table of two input pins tied to one wire (F07). Only the rows where A and B differ give E.
#ABY
000
01E
10E
111

circ-wire-colors-conflict-broken · mainscroll to see all
ABY
Broken: pins A and B are the same wire. When they differ, the wire is red and Y reads E. CC BY 4.0 · SHA-256 f3440b78992b
Describe this circuit

Components: Input pin A; Input pin B; Output pin Y.

  • Input pin A connects to Input pin B, Output pin Y (net A, B, Y).

Find the two drivers

Start at the red wire and follow it to every output attached: pins that are inputs to the circuit, gate outputs, subcircuit outputs and constants. Tunnels with the same label count as one wire, so a driver can be far from the red wire on screen (see Tunnel). A splitter can also join two outputs you did not mean to connect.

To fix it, remove one driver, or put a multiplexer in front so that only one source drives the wire:

circ-wire-colors-conflict-fixed · mainscroll to see all
ABSelY
Fixed: a multiplexer picks A or B by Sel, so only one source drives Y. CC BY 4.0 · SHA-256 dc2862b0bfb6
Describe this circuit

Components: Input pin A; Input pin B; Input pin Sel; Multiplexer 1; Output pin Y.

  • Input pin A connects to Multiplexer 1 (net A).
  • Input pin B connects to Multiplexer 1 (net B).
  • Input pin Sel connects to Multiplexer 1 (net Sel).
  • Multiplexer 1 connects to Output pin Y (net Y).

Shared buses: use Controlled Buffers

A shared bus is the one place where several outputs on one wire is the design. Each source goes through a Controlled Buffer, which puts nothing on the wire when its control input is 0. Our two-buffer circuit gives this table (F10):

Two Controlled Buffers on one wire. Nothing enabled gives U, one enabled gives its value, both enabled give the value if equal and E if different (F10).
#ABSelASelBY
0000U
00010
00100
00110
0100U
01011
01100
0111E
1000U
10010
10101
1011E
1100U
11011
11101
11111

circ-wire-colors-tristate-bus · mainscroll to see all
ABSelASelBY
Both buffers enabled with A = 1 and B = 0: the shared wire is red. Enable one at a time. CC BY 4.0 · SHA-256 2278dccbf377
Describe this circuit

Components: Input pin A; Input pin B; Input pin SelA; Input pin SelB; Controlled Buffer 1; Controlled Buffer 2; Output pin Y.

  • Input pin A connects to Controlled Buffer 1 (net A).
  • Input pin B connects to Controlled Buffer 2 (net B).
  • Input pin SelA connects to Controlled Buffer 1 (net SelA).
  • Input pin SelB connects to Controlled Buffer 2 (net SelB).
  • Controlled Buffer 1 connects to Controlled Buffer 2, Output pin Y (net Y).

Rule of thumb: at most one buffer enabled at a time. If the enables come from a decoder, check that it can never enable two at once.

Red from a loop

A feedback loop with no stable state also shows E and a red loop (F06). That is oscillation, and it has its own fix guide: see Oscillation apparent.

LAB lab-lnx · Linux lab5.0.02026-11-09

Logisim-evolution 5.0.0 canvas with a NOT gate whose output wire loops back to its own input. The wire is red, and the output pin Q shows E.

A NOT gate fed by its own output. The loop is drawn red and the pin reads E (F06).lab-lnx-le500-oscillation-loop-01
A NOT gate whose output wire loops back to its own input: the wire is red and the output pin shows E.

Red that spreads from a subcircuit

An E inside a subcircuit comes out of its output pins, so the red may be far from the cause. Open the subcircuit (double-click it in the circuit list, or use Simulate, Go In To State) and look for the red wire inside. See Subcircuits.

Blue wire and U (or X): nothing drives it

A blue wire has no driver. In Logisim-evolution 5.0.0 its value is U; older documents and many course sheets call it X. It is the same state (F08). In our test the output on an undriven wire read U for every input, while the output next to it still followed its input:

Y sits on a wire that nothing drives; Z follows A (F08).
#AYZ
0U0
1U1

The wire end is not on the port

This is the most common cause. A wire that stops one grid step short looks connected but is not. In Logisim a connected end shows no gap and a junction dot where wires meet. To check, drag the component a little and watch whether the wire follows, or click the wire end and look for where it stops.

circ-wire-colors-floating-broken · mainscroll to see all
AYZ
Broken: the wire to Y stops 10 units before the next segment, so Y is undriven and reads U while Z follows A. CC BY 4.0 · SHA-256 6bc89aab4e44
Describe this circuit

Components: Input pin A; Output pin Y; Output pin Z.

  • Input pin A connects to Output pin Z (net A, Z).
circ-wire-colors-floating-fixed · mainscroll to see all
AYZ
Fixed: one continuous wire, so Y follows A. CC BY 4.0 · SHA-256 1cb3e0190cc9
Describe this circuit

Components: Input pin A; Output pin Y; Output pin Z.

  • Input pin A connects to Output pin Y, Output pin Z (net A, Y, Z).

An input pin of a subcircuit is not connected outside

Inside the subcircuit everything may look right, but if the instance has an input nobody drives, the signal is U from there on. Connect the input in the parent circuit. See Subcircuits.

A three-state output with nothing enabled

A Controlled Buffer with its control at 0 drives nothing, so the wire is U (the first rows of the table above). If you want a defined value when nothing is enabled, add a Pull Resistor to the wire (Wiring library). See Pins and probes.

Input pins that should pull down

Some course guides advise restarting Logisim when many wires turn blue. That is a community report. We did not meet a case where a restart was needed; Simulate, Reset Simulation is the first thing to try.

Orange wire and “Incompatible widths”

An orange wire joins things of different bit widths. Logisim says so at the bottom of the canvas, and the output reads U for every input (F09):

Incompatible widths

Canvas status line, orange wire; both versions

LAB lab-lnx · Linux lab5.0.02026-11-09

Logisim-evolution 5.0.0 window with four test wires. Three of them are grey and their pins show 0. The fourth, from a 4-bit input to a 1-bit pin, is orange, with the words Incompatible widths at the bottom of the canvas.

The orange wire and the message are visible even before the reset: a 4-bit pin D into a 1-bit pin W. Linux lab, 5.0.0. The other wires are still grey (see below).lab-lnx-le500-wire-colours-grey-before-reset-01
Four test wires: three grey with pins at 0, and an orange one with Incompatible widths at the bottom.

Find the mismatched end

A wire takes its width from what it touches. Select each end and read Data Bits in the Properties panel on the left. The wire between a 4-bit pin and a 1-bit pin cannot be both, so Logisim marks it orange.

circ-wire-colors-width-broken · mainscroll to see all
44bDY
Broken: the 4-bit input D goes straight to the 1-bit output Y. The wire is orange and Y reads U. CC BY 4.0 · SHA-256 7b1c413920b8
Describe this circuit

Components: Input pin D; Output pin Y.

  • Input pin D connects to Output pin Y (net D, Y), 4 bits wide.

Fix: match Data Bits, or convert with a splitter

If both ends should be one width, set Data Bits to match. If you want one bit of a bus, use a splitter: its Bit Width In matches the bus, and each output takes the bits you assign. A Bit Extender widens or narrows a value when you want to keep the number rather than pick a bit. Tunnels with the same label must also have the same width. See Splitter and Tunnel.

circ-wire-colors-width-fixed · mainscroll to see all
44bDY
Fixed: a splitter takes bit 0 of D, so Y follows the lowest bit. CC BY 4.0 · SHA-256 6af4ba09ea4b
Describe this circuit

Components: Input pin D; Output pin Y; Splitter 1.

  • Input pin D connects to Splitter 1 (net D), 4 bits wide.
  • Output pin Y connects to Splitter 1 (net Y).

Common orange traps

A constant has its own width, which defaults to 1 bit. A multiplexer select input is as wide as the multiplexer’s Select Bits setting. A counter or register has a Data Bits value that must match the bus it drives. Check these three before anything else.

Grey wires after opening a file: click the canvas or press Ctrl+R

Click once anywhere on the canvas, or press CtrlR (⌘R on macOS) (Simulate, Reset Simulation). Moving the mouse is not enough.

After opening a circuit in the 5.0.0 window, every wire stays grey and the pins show 0 until the first click on the canvas or a Reset Simulation. Afterwards the right colours appear: green for 1, red for E, blue for U. We saw it with a file saved by 5.0.0 itself, not only with classic files (F45, which replaces the narrower F03), on a Linux lab machine and on a Windows desktop with the MSI install (F49), and on a macOS 15 machine with a native 5.0.0 file, where one click inside the canvas brought the colours (F64). On a Mac the shortcut shown above is Command+R.

The same window after one click: the first wire is green, the double-driven wire red, the undriven wire blue.
Logisim-evolution 5.0.0 on Windows with three grey test wires whose pins show 0.
Before the clickAfter one click
Windows Server 2025 desktop on a GitHub runner, 5.0.0 from the MSI. Moving the mouse over the canvas first changed nothing (F49).ci-w25-le500-native-v5-before-click-01 · ci-w25-le500-native-v5-after-click-01
The same three cases after Reset Simulation: green for 1, red where two outputs disagree, blue where nothing drives the wire.
Logisim-evolution 5.0.0 with three test wires before any reset: every wire is grey and the pins show 0.
Before resetAfter Simulate, Reset Simulation
The Ctrl+R route on the Linux lab machine.lab-lnx-le500-wire-colours-grey-before-reset-02 · lab-lnx-le500-wire-colours-after-reset-02

Other reasons for grey wires: Auto-Propagate is switched off (see Clock and simulation), or a wire has nothing attached, which Logisim draws in its Unconnected colour.

Dark green and black: normal

On a one-bit wire, 1 is bright green and 0 is dark green. A wire wider than one bit is drawn thick in the bus colour, and its value shows when you hover or attach a probe, in the radix you choose. See Pins and probes. Only red, blue, orange and grey need action.

Values you see on pins and probes

Chip Meaning
Low
High
Undriven (X in older documents)
Error: conflict, loop or an error from inside
A multi-bit pin shows one character per bit, so one bad bit stays visible

Command-line users see the same characters: U and E appear in the table printed by –tty table (command line).

Still stuck? A 5-step check

Five checks, in this order0 / 5 done

Then read Oscillation apparent, look up your exact message in the error list, or check the file in the .circ Viewer.

Classic 2.7.1 differences

Feature2.7.15.0.0
Undriven wire shown as2.7.1: untestedX in the 2.7.1 documentation5.0.0: yesU (F08)
Red for conflicts, orange for widths2.7.1: untested5.0.0: yesseen (F07, F09)
Grey until a click after opening a file2.7.1: untested5.0.0: partialseen with any file (F45, F49)
Colour-blind colour preset2.7.1: untested5.0.0: untested

Cells say untested where we have no capture from 2.7.1.

Downloads: broken and fixed circuits

Each circuit was checked in Logisim-evolution 5.0.0 against the expected table. The broken ones are checked against the table with E and U written out; the fixed ones with a test vector.

Circuit What it shows Checked by
circ-wire-colors-showcase.circ (2.7.1 format) The four cases in one circuit T-ERR-05
conflict-broken, fixed Two outputs on one wire, and a multiplexer fix T-ERR-02
floating-broken, fixed A wire end that stops short T-ERR-03
width-broken, fixed 4-bit into 1-bit, and a splitter fix T-ERR-04
tristate-bus Two Controlled Buffers on one wire T-ERR-06

All files are CC BY 4.0. Open any of them in the .circ Viewer to list its widths and unconnected pins.

Frequently asked questions

What does a red wire mean in Logisim?

Two outputs are driving the same wire with different values, or an error value is travelling along it. The pins on that wire read E. Find the second driver rather than deleting wires.

Why are my wires blue in Logisim?

Nothing drives them. The most common cause is a wire end that does not touch the port it should connect to. Logisim-evolution 5.0.0 shows the value as U; older documents call it X.

What does E mean in Logisim?

E is the error value. It appears when two drivers disagree, when a loop never settles, or when an error comes out of a subcircuit.

What does U (or X) mean in Logisim?

U means unknown or undriven: nothing puts a value on the wire. In 5.0.0 we saw U on an undriven wire; older course sheets call the same state X.

What does Incompatible widths mean?

The things joined by one wire have different bit widths, for example a 4-bit pin wired to a 1-bit pin. The wire turns orange, and the output reads U until you match the Data Bits or use a splitter.

Why are all my wires grey after I open my file?

In 5.0.0 a freshly opened circuit stays grey until the first click on the canvas or a Reset Simulation (Ctrl+R). Moving the mouse is not enough. We saw it with files saved by 5.0.0 itself, on Linux, Windows and macOS.

Can I change the wire colours?

Yes. Logisim lets you change its colours in Preferences, and some courses do so for colour-blind students. The colours on this page are the defaults.

Sources

  1. Wire colour and value tests on Logisim-evolution 5.0.0, logisim.dev lab data: test-data/lab1-2026-11-09-linux-local/logs/ (err-conflict, err-floating, err-width, err-wire-colours, tristate-bus, err-oscillation-wired)
  2. Grey wires after opening a file, logisim.dev lab data: test-data/lab3-2026-11-09-gui/, test-data/ci-round3-2026-11-09/windows/
  3. Colour values used by the explainer, Logisim-evolution 5.0.0 source (AppPreferences defaults)

Try: , , ,