Getting Started with LCC Fusion

Introduction

  • Brief overview of the LCC Fusion Project.
  • Purpose and target audience (model railroad hobbyists).
  • Key features and benefits of using this project.
  • LCC Q&A

Roles and Responsibilities

The LCC Fusion Project is targetted at a broad spectrum of topics including hardware and firmware, that impacts layout automation planning, design, and implementation. This typically requires skills from one or more people. Below is a roles and repsonsibility summary and its relationship to this project and its documentation.

Use documentation’s navigation area and the Explore Subjects page to find documentation based on your role.

Note that responsibilities listed below may well be implemented by a single person as they plan, design, and implement a own layout. In other situations, the repsonsibilities my shared across model train club members, each working together.

Depending on your role or interests, use the links below to begin exploring the LCC Fusion Project from the perspective most relevant to you.

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

Role Responsibility Start Here
🧱 Hardware Specialist 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
🔌 System Installer Bridges firmware, wiring, and network setup. Connects CAN devices, configures CDI, and ensures LCC events are routed correctly across the system. Installer’s Guides
📐 Layout Engineer Implements track wiring, turnout motor control, and signal logic physically. Ensures systems operate smoothly and as designed. Installer’s Guides
🔧 Firmware Developer Writes and customizes firmware for LCC Node devices, manages CDI structure, and builds automated test logic. Developer’s Guides
🧰 DIY Hobbyist Interested in simple, hands-on projects to personalize layouts using ready-to-use kits or guides. Often wears many hats across roles. Quickstart Paths
🧑‍🏫 Educator Uses LCC Fusion in classrooms or workshops to teach electronics, systems thinking, or programming through model railroading. Planner’s Guides

Project Overview

  • Detailed description of what the project is.
  • Explanation of how it integrates with model railroading.
  • Highlight the unique aspects or advantages of your project.

Hardware Requirements

  • List of required components (PCBs, sensors, etc.).
  • Sources or recommendations for obtaining these components.

PCB Assembly Guide

  • See Hardware Assembly Guides
  • Step-by-step instructions for assembling the PCBs.
  • Include any already completed sections here.
  • High-quality images or diagrams to assist in assembly.

Configuration and Setup

Connecting the PCBs

  • Diagrams showing which PCBs get connected together.
  • Explanation of the connections and their purposes.
  • Troubleshooting tips for common connection issues.

LCC CDI Configuration Tool Configuration

  • Step-by-step guide on configuring the boards using the LCC CDI Configuration Tool.
  • Screenshots or diagrams to assist in this process.
  • Explanation of different configuration options and their effects.

Usage and Operation

  • Instructions on how to use the system in a model railroad setting.
  • Examples or scenarios of the system in action.

Troubleshooting and Support

  • Common issues and their solutions.
  • Information on where users can seek help (forums, contact information).

Contributing to the Project

  • Guidelines on how others can contribute to the project.
  • Information on open-source licensing and credits.

    Change Log and Updates

  • Record of changes and updates made to the project.
  • Future plans or upcoming features.

References

Acknowledgments

  • BOB AI (my AI avatar the ChatGPT chatbot developed and hosted from OpenAI.com) - Bob has been relentless has been instrumental in all aspects of this project, from helping with electronic designs and technology, C++ sketchs for the firmware, Windows installer, and the overall layout and documentation
  • Robert Heller - for his working examples of both hardware and firmware for LCC Nodes and I/O boards. His was the inspiration and basis upon which this was built.
  • The OpenMRN-Lite development team for macros to help with the CDI design and example code.

Licenses for LCC Fusion Connect

Hardware License

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

Summary of the License

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.

firmware License Summary

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 Connect 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.

Contact Information

  • Pat Fleming (PatFlemingHTC@gmail.com)
Last updated on: December 17, 2025 © 2025 Pat Fleming