Getting Started with LCC Fusion

Table of contents

Getting Started with LCC Fusion

Introduction

LCC Fusion is an open‑source automation platform for model railroads built on NMRA LCC (Layout Command Control). It combines inexpensive hardware, modular PCBs, and event‑driven networking to let you design, build, and expand layout automation in a structured, scalable way.

This page is your orientation guide. Its purpose is not to teach every detail, but to help you understand where to begin, how the documentation is organized, and which path makes sense for you.

If you are completely new to LCC or want the architectural “big picture,” start here first:

Understanding LCC Fusion — background concepts, architecture, and why Fusion is structured the way it is
- Documentation & podcast companion: https://patfleming.github.io/LccFusionPosts/understanding-lcc-fusion/

If you want help navigating the documentation and posts ecosystem:

Navigating LCC Fusion Documentation & Posts (Podcast)
- https://patfleming.github.io/LccFusionPosts/podcast-navigating-lcc-fusion-posts/

Roles and Responsibilities

LCC Fusion spans hardware, firmware, wiring, and system design. Most users wear more than one hat, but thinking in terms of roles helps you find the right documentation quickly.

Use the site navigation and the Explore Subjects page to browse documentation by role and topic.

The table below maps common roles to the parts of the documentation most relevant to them.

Not sure where to begin? Start with the Quickstart Paths to try a simple working example.

Role	Responsibility	Start Here
Builder	Expert in assembling, wiring, and troubleshooting hardware cards and breakout boards. Recommends component choices and PCB build practices.	Builder’s Guides
Layout Planner	Designs the block structure, signal plans, and sensor layout for the railroad. Focuses on automation flow and system behavior.	Planner’s Guides
Layout Installer	Does the wiring and network setup. Connects LCC nodes. Connects the Fusion nodes, cards, breakout boards, and devices.	Installer’s Guides
Administrator	Configures the firmware for the installed devices. Configures CDI, and ensures LCC events are routed correctly across the system.	Configurator’s Guides
Firmware Developer	Writes and customizes firmware for LCC Node devices, manages CDI structure, and builds automated test logic.	Developer’s Guides

How the Documentation Is Organized

LCC Fusion documentation is organized by intent, not by board name alone:

Understanding LCC Fusion — concepts, architecture, and mental model
Quickstart Paths — small, complete examples that work end‑to‑end
Planner’s Guides — design decisions made before building
Builder’s Guides — PCB assembly and hardware construction
Installer’s Guides — wiring, mounting, and layout integration
Configurator’s Guides — CDI configuration and behavior setup
Developer’s Guides — firmware internals and advanced customization

This structure lets you enter at different points depending on your experience and goals.

Hardware Overview

LCC Fusion is built around modular hardware:

Node Cards — ESP32‑based controllers that generate and consume LCC events
Node Bus Hubs — distribute power and communications to multiple cards
I/O, sensor, output, and other specialty cards — interface with device specific breakout boards
breakout boards — simplify direct wiring to real‑world devices

You do not need every card to get started. Most users begin with a single Node Card and expand as needed.

Building Hardware

If your goal is to assemble boards:

Follow the Builder’s Hardware Assembly Guides for step‑by‑step instructions
Use the PCB Parts and PCB Components references to source components
Review Testing and Verification sections to confirm correct assembly before installation

Hardware guides are written to assume basic soldering skills and a multimeter, not professional electronics experience.

Configuration and Setup

LCC Fusion uses CDI (Configuration Description Information) to define behavior such as:

What devices a node controls
How inputs map to outputs
How logic and automation rules behave

To get started with configuration:

An Introduction to the CDI Configuration Tool
Configuration (CDI) Guides

These tools allow configuration without writing code and are central to how Fusion remains flexible as layouts grow.

Connecting and Installing

Installation covers:

Mounting Node Cards and Node Bus Hubs
Running CAN bus cabling
Connecting sensors, turnouts, signals, and accessories

Use the Installer’s Guides for wiring diagrams, connection tables, and best practices.

Using the System

Once installed and configured, LCC Fusion supports:

Event‑driven automation
Signaling and interlocking logic
Detection‑based behavior
Audio, lighting, motion, and turnout control

Examples and scenarios are documented throughout the Planner’s and Quickstart sections.

Troubleshooting and Support

If something does not behave as expected:

Review the Testing and Verification steps for your hardware
Check troubleshooting sections in the relevant guide
Use serial output and built‑in diagnostics to identify configuration or wiring issues

References

Licenses for LCC Fusion

Hardware License

This project is licensed under the CERN Open Hardware License Version 2 - Permissive (CERN-OHL-P v2.0).

This license allows you to use and modify this design for any purpose, including commercial, provided that you:

Attribute the original source of the design to us by including the following copyright notice in all copies or substantial portions of the licensed material:

“Copyright (C) [Year] [Your Name or Organization’s Name]. This work is licensed under the CERN OHL-P v2.0.”
Include a copy of the license itself with the distributed work. The license text is available at: https://ohwr.org/cern_ohl_p_v2.txt
Indicate if changes were made to the original design, in a way that is trackable from the modified work back to the original source.

Applying the License

To apply the CERN OHL-P v2.0 to your work, include a file named LICENSE or LICENSE.txt in the root of your project source repository, containing the full text of the license, and reference the license in your README as shown here.

For more details on the license, its permissions, conditions, and limitations, please read the full license text at the link provided above.

Based on the copyright notice and license conditions you’ve provided, it seems you are using a license similar to the BSD 2-Clause “Simplified” License for your firmware. Here is a Markdown (MD) template for the “License” section of your README file that reflects this license. Make sure to replace [firmware Name] with the actual name of your firmware project.

Firmware License

This firmware is licensed under the BSD 2-Clause “Simplified” License.

Copyright

This license permits personal and commercial use, distribution, and modification of the firmware under the following conditions:

Redistribution: Redistribution of source code must retain the above copyright notice, this list of conditions, and the following disclaimer. Redistribution in binary form must reproduce the copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.
Disclaimer: THIS FIRMWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS FIRMWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Applying the License

To apply this license to your firmware, include a file named LICENSE or LICENSE.txt in the root directory of your project source repository, containing the full text of this license. Reference this license in your project’s README file as shown here to inform users and contributors of the licensing terms.

For more information on the BSD 2-Clause “Simplified” License, visit https://opensource.org/licenses/BSD-2-Clause.

Disclaimer of Liability

LCC Fusion is provided “as is”, without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose, and noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages, or other liability, whether in an action of contract, tort or otherwise, arising from, out of, or in connection with the firmware or the use or other dealings in the firmware/hardware.

The user assumes all responsibility and risk for the use of this firmware/hardware. The information and powered hardware provided are subject to change without notice and should not be construed as a commitment by the author.

Use caution and common sense when working with electrical components and always follow the manufacturer’s instructions and safety guidelines. The creator of this project cannot be held responsible for any injuries, damages, or violations of local codes or laws that may arise from the use of this project.

References

Contact Information

Pat Fleming (PatFlemingHTC@gmail.com)