Overview

SLCAN is the mechanism that allows a computer to communicate with an LCC CAN network using a standard serial connection.

In practical terms, SLCAN answers a simple question:

How does software running on a computer talk to an LCC CAN network?

This document explains what SLCAN is, how it is used in LCC Fusion systems, and how recent firmware updates allow a Node Card to replace a dedicated CANable adapter.

This is a conceptual reference, not a setup guide.

What Is SLCAN?

SLCAN (Serial Line CAN) is a lightweight protocol that sends CAN messages over a serial connection.

It is best thought of as a translation layer:

  • On one side: a computer program (such as :contentReference[oaicite:0]{index=0} LccPro™)
  • On the other side: a physical CAN network used by LCC nodes

SLCAN does not define LCC behavior.
It simply provides a way for a computer to exchange CAN messages with the layout.

SLCAN Is a Protocol, Not a Device

A common source of confusion is associating SLCAN with a specific piece of hardware.

Important clarification:

  • SLCAN is not a CANable
  • SLCAN is not an LCC protocol
  • SLCAN is not tied to a specific vendor or adapter

Any device capable of:

  • receiving serial data from a computer, and
  • forwarding that data onto the CAN bus,

can act as an SLCAN bridge.

The Role of an SLCAN Bridge

To use SLCAN, a bridge device is required between the computer and the CAN network.

The bridge is responsible for:

  • receiving SLCAN commands over a serial connection
  • converting them into CAN frames
  • sending received CAN frames back to the computer

Historically, this bridge role was filled by a dedicated USB adapter.

Traditional Approach: CANable

A CANable is a common USB-to-CAN adapter that supports SLCAN.

In this model:

  • the computer connects to the CANable via USB
  • the CANable connects to the CAN network
  • software such as LccPro communicates using SLCAN

This approach is still valid and fully supported.

LCC Fusion Approach: Node Card as a Dongle

With LCC Fusion firmware, a Node Card can now perform the same SLCAN bridge role.

In this configuration:

  • the Node Card connects to the computer via USB
  • the Node Card connects to the CAN network
  • SLCAN is handled directly by the Node’s firmware

From the computer’s point of view, the Node Card behaves exactly like a traditional SLCAN adapter.

Why This Matters

Using a Node Card as an SLCAN bridge:

  • eliminates the need for a separate CANable
  • reduces cost and hardware complexity
  • uses the same USB cable already required for firmware updates
  • integrates cleanly with existing LCC Fusion tooling

For new systems, this is the recommended approach.

Wired vs Bluetooth SLCAN

LCC Fusion firmware supports SLCAN over two transport types:

Wired Serial (USB)

  • Uses a standard USB serial connection
  • Appears to the computer as a normal serial device
  • Fully compatible with LccPro and other PC-based tools

This is the primary and recommended method.

Bluetooth Serial

  • Uses a Bluetooth serial connection
  • Intended for diagnostics, development tools, and mobile applications

Important limitation:

LccPro does not currently support Bluetooth SLCAN connections.

This is a limitation of the LccPro/JMRI connection layer, not of LCC Fusion firmware.

Bluetooth SLCAN should be considered an advanced or auxiliary feature, not a replacement for wired connections when using LccPro.

What SLCAN Does Not Affect

Using SLCAN:

  • does not change how LCC nodes communicate with each other
  • does not alter LCC Event IDs or CDI behavior
  • does not require special configuration on the CAN network

It only affects how the computer connects to the layout.

When You Need to Understand SLCAN

You typically only need to think about SLCAN when:

  • connecting a computer to the CAN network
  • configuring LccPro or similar tools
  • troubleshooting PC-to-layout communication
  • deciding whether a CANable is required

For normal layout operation, SLCAN is invisible.

Summary

  • SLCAN is the standard method used by PC tools to communicate with an LCC CAN network
  • It is a protocol, not a specific device
  • A Node Card running LCC Fusion firmware can act as a full SLCAN bridge
  • This removes the requirement for a dedicated CANable adapter
  • Wired USB SLCAN is supported by LccPro; Bluetooth SLCAN is not

Understanding this distinction helps simplify system design and avoids unnecessary hardware.

Last updated on: February 05, 2026 © 2026 Pat Fleming