Table of contents
  1. A Simple LCC Fusion Example
    1. Purpose of This Example
    2. The Scene: One Siding
    3. How This Maps to LCC Fusion
      1. Node Card
      2. Fusion Node Bus Hub
      3. I/O Cards
      4. Breakout Boards
    4. What the Wiring Looks Like (Conceptually)
    5. How Information Flows
    6. Where Configuration Fits (Conceptually)
    7. How This Scales
    8. Why This Example Matters

A Simple LCC Fusion Example

A conceptual, end-to-end example showing how LCC Fusion fits together — without wiring diagrams or configuration steps.

Purpose of This Example

This example is intentionally simple.

It is not a build guide, wiring guide, or configuration tutorial.
Its purpose is to show how the pieces of LCC Fusion relate to each other in a real, familiar railroad situation.

If you understand this example, you understand the core of LCC Fusion.

The Scene: One Siding

Imagine a very common layout situation:

  • a single siding branching off the mainline
  • one turnout controlling access to the siding
  • one signal protecting the entrance to the siding
  • block detection in the siding

Operationally, the goal is simple:

If the siding is occupied, the signal shows Stop.
If the siding is clear, the signal shows Clear.

No dispatcher panel.
No complex interlocking.
Just basic automation.

How This Maps to LCC Fusion

Instead of thinking about wires, we think in terms of roles.

Node Card

  • centralizes all logic and LCC communication
  • receives LCC events from the network
  • decides how devices should respond

There is one CAN cable connected to the Node Card.

Fusion Node Bus Hub

  • mechanically and electrically connects cards together
  • distributes power and inter-card communication
  • requires no cables between cards

All cards are simply plugged into the hub.

I/O Cards

For this scene, we need three I/O functions:

  1. Block occupancy detection card
    • senses whether the siding is occupied
  2. Turnout control card
    • drives the turnout motor
  3. Signal output card
    • controls the signal LEDs

Each card performs one specific job.

Breakout Boards

Each I/O card connects to a breakout board that is mounted near the actual device:

  • a block detection breakout near the track
  • a turnout breakout near the switch machine
  • a signal breakout near the signal mast

Each I/O card has one network cable leaving it and going to its breakout board.

What the Wiring Looks Like (Conceptually) 

flowchart LR
  %% A Simple LCC Fusion Example — Conceptual Flow

  CAN[(CAN Network)]
  NC["Node Card"]
  HUB["Node Bus Hub"]
  DET[BOD Card]
  SIG[PWM Output Card]
  TO[Turnout Card]

  BBO[Block Breakout Board]
  SBO[Signal Breakout Board]
  TBO[Turnout Breakout Board]

  TRACK["Track Block"]
  MAST[Signal Mast]
  MOTOR[Turnout Motor]

  CAN <-->|1 CAN cable|NC <-->HUB

  HUB <--> DET <-->|1 network cable| BBO
  HUB <--> SIG <-->|1 network cable| SBO
  HUB <--> TO <-->|1 network cable| TBO
  
  BBO <--> TRACK
  SBO <--> MAST
  TBO <--> MOTOR

Referring to the above diagrams, we can describe the entire system:

  • 1 Node Card and 3 I/O Cards are inserted in the Node Bus Hub, no wiring required
  • one CAN cable enters the Node Card
  • three network cables leave the 3 I/O cards
    • one to the block detector breakout
    • one to the turnout breakout
    • one to the signal breakout

There are:

  • no card-to-card cables (hub provides direct connections)
  • no ribbon cables
  • no shared wire bundles

Everything inside the hub connects automatically.

How Information Flows

Now consider what happens during operation.

  1. A train enters the siding
  2. The block detector senses occupancy
  3. The detection card reports this to the Node Card
  4. The Node Card generates an LCC event
  5. The signal output card responds
  6. The signal changes to Stop

When the train leaves, the process reverses.

The important point is this:

Devices do not talk to each other directly.
The Node Card coordinates everything.

Where Configuration Fits (Conceptually)

At configuration time, the user simply describes:

  • which block detector corresponds to the siding
  • which signal output controls the signal
  • what behavior should occur when occupancy changes

No firmware is written.
No cards are reprogrammed.
No wiring logic is embedded in hardware.

The behavior lives in configuration, not solder.

How This Scales

Now imagine expanding the scene:

  • add a second signal
  • add a second block
  • add another turnout

Nothing about the structure changes.

You:

  • plug in another I/O card
  • connect another breakout board
  • add another network cable

The hub stays the same.
The wiring model stays the same.
The logic model stays the same.

Why This Example Matters

This single siding example demonstrates every core idea in LCC Fusion:

  • centralized intelligence
  • no inter-card wiring
  • one job per card
  • breakout boards handling device details
  • simple, predictable wiring
  • clean expansion

If this example feels straightforward, then LCC Fusion is doing its job.

← Back to Understanding LCC Fusion

Last updated on: December 17, 2025 © 2025 Pat Fleming