CDI Configuration Assistant Video

Table of contents

CDI Configuration Assistant Video

Here’s the revised version of your script:

Introduction to the CDI Configuration Assistant Tools

Welcome to the CDI Configuration Assistant! In this video, I’ll walk you through the tools you’ll use to simplify and streamline your CDI configurations. We’ll explore the Fusion Toolbar, the right-click context menu called “Fusion,” and the buttons at the top of both the Mast and Logic sheets. Let’s get started!

The Fusion Toolbar is your go-to resource for quick access to CDI Configuration Assistant features. By default, it’s locked at the top, just below the Libre Calc toolbar. Need more flexibility? Right-click on it and select Undock Toolbar to float it. Once undocked, you can drag it wherever it’s most convenient for you. Let me show you how this works.

The right-click context menu is another handy way to access the Fusion tools. Just right-click anywhere in your sheet, select Fusion, and you’ll find the functions to work with the sheet.

LCC Fusion Buttons

At the top of your Mast and Logic sheets, you’ll find the LCC Fusion Buttons. These act as a hub for key functions. For example, clicking the Save CDI button allows you to export the CDI restorable text to a file.

Summary of Functions Provided

Here’s a quick summary of the tools available in the Fusion Toolbar, context menu, and buttons, along with how they can help you:

Tool	Description	Toolbar	Context Menu	Button
Go To Sheet	Navigate to sheet selection	X	X	-
Duplicate Sheet	Duplicates current sheet	X	X	-
Move or Copy Sheet	Move or copy current sheet to a new location	X	X	-
Rename Sheet	Rename current sheet	X	X	-
Delete Sheet	Delete current sheet	X	X	-
Zoom in/out	Zooms the view in/out	X	X	-
Print, Print Preview, Print Selection	Printing options	X	X	-
CDI View (on/off)	Toggles on/off the viewing of the CDI (restorable) text	X	X	X
Save CDI	Saves the CDI (restorable) text the specified file and folder, opening the file for viewing. Use a CDI Configuration Tool (e.g., JMRI) to restore this file.	X	X	X

Why Use These Tools?

Why use these tools? Simply put, they make your life easier! By centralizing essential functions, the Fusion Toolbar, context menu, and buttons help you stay organized and focus on creating and managing your CDI configurations without distractions.

In the next section, we’ll explore how to set up a mast definition using these tools, starting with the basics and building up to more advanced configurations.

Here’s the script for your demonstration video on configuring Card 1’s Mast 1 for a dwarf signal, with two rules for Stop and Clear aspects, based on the new example provided:

Dwarf Signal Configuration Example

Introduction

In this video, we’ll explore an example of configuring a dwarf signal mast with two rules: Clear and Stop. At this time, we won’t be demonstrating how to edit or configure fields, but instead, we’ll focus on understanding the layout of the configuration and how the different fields relate to one another. This foundational overview will help you become familiar with the interface and prepare you for more advanced topics in future videos.

In the next video, we’ll demonstrate configuring another mast with three rules, including step-by-step editing and setup. For now, let’s dive into the example configuration.

Card Information Configuration

The first step is to set up the configuration information for the LCC Fusion card supporting the signals.

In the LCC Fusion Project, signaling is managed by a Node Card and PWM Card connected to a Signal Mast Breakout Board, which in turn is connected to the signal head’s lamps (LEDs). For this setup, the LCC Node’s Node ID must be specified in the Card Node ID field.

Next, the Card # identifies the card in the system. This number ranges from 1 to 8, allowing each LCC Fusion Node to support up to 8 card configurations, with each card handling up to 8 masts—for a total of 64 masts.

The Card Reference ID is optional but helpful as a label to identify the card’s purpose. Similarly, the Card Description provides context about the card’s role or location, though it is not mandatory.

The Card Communications Bus and Card Addressfields specify how the Node’s firmware connects to the PWM Card and must be configured correctly. The LCC Fusion Project supports two communication buses: Bus A and Bus B. Additionally, each PWM Card can have one of 8 physical addresses, configured using a set 3 slide switches on the card to configure values 0-7. This provides a total of 16 configurations (8 addresses per bus). It’s essential that these fields match the card’s COMM BUS and COMM ADDR selections to ensure proper communication with the firmware.

Mast Configuration

Let’s explore the Mast Configuration fields, which are crucial for defining the behavior and identity of the signal mast. These fields ensure the mast operates correctly and is linked to the corresponding track circuit for proper signaling.

Starting with the Mast #, this field assigns a unique number to the mast for identification within the system. In this example, the mast is assigned 1, signifying its unique place in the configuration.

The Mast Operational Mode defines how the mast operates. Here, it’s set to Normal, indicating standard operation without any special modes like testing or fallback.

The Mast Identifier field provides a unique textual identifier for the mast, such as MF54-00-01-E. This name typically reflects the signal’s location or specific function in the network.

Next, we have the Track Circuit Link Event ID, which is critical for linking this mast to the corresponding track circuit. In this example, the Event ID is 05.01.01.5C.66.16.E0. This linkage allows the mast to respond to track conditions by activating the appropriate rules and aspects.

Finally, the Lamp Fade field defines how lamps transition between on and off states. It’s currently set to None, meaning no fade effect is applied, and lamps change states instantly.

Track Circuit Configuration

Directly tied to the mast configuration is the Track Circuit Configuration, which ensures the mast communicates with the correct track circuit.

The Remote Mast Description field specifies the linked mast’s description, matching the mast identifier MF54-00-01-E to ensure consistency.

The Remote Mast Link Address Event ID serves as the connection point for the mast to receive updates from the track circuit. Here, it’s the same Event ID as defined earlier: 05.01.01.5C.66.16.E0. This confirms the track circuit and mast are properly synchronized.

By defining these Mast and Track Circuit Configuration fields, the system establishes a clear relationship between the mast and its corresponding track circuit. This linkage ensures accurate signaling and smooth transitions between aspects. In the next segment, we’ll dive deeper into the rules and aspects driven by this setup. Stay tuned!

Rules To Aspect Mapping Configuration

Now that we’ve wrapped up the card and mast configuration discussions, let’s explore the Rule to Aspect Mapping Configuration for my dwarf signal, focusing initially on Rule 1, labeled ‘0–Stop.’ This rule enforces a train to come to a complete stop at the signal by setting the track speed to ‘Stop’ and displaying a red aspect indicator, shown here as ‘R, R/R – Stop before Signal.’

This rule is activated when the Node firmware receives the Set Aspect Rule Event ID (05.01.01.5C.66.15.00). This Event ID signals that the STOP rule is in effect and sets the signal’s aspect lamps as defined below. The Aspect Rule Set Event ID (05.01.01.5C.66.15.01) is produced when the rule is successfully set. Monitoring this Event ID allows additional tasks to be performed, such as illuminating LEDs or updating the state of another signal mast. When the Node firmware receives an Event ID for a different rule, this rule clears, and the Aspect Rule Cleared Event ID (05.01.01.5C.66.15.02) is sent. This provides an opportunity for the system to execute further tasks, such as turning off the red LED or preparing the signal for the next aspect.

Below the rule settings, you’ll see Aspect Lamp 1 configured to Lamp Output 1. In this example, this output is connected to a red LED in the signal head, which is attached to the LCC Fusion Signal Card’s Lamp 1 connection. When this rule is set, the red LED for the STOP aspect is lit with the Lamp Phase configured to Steady and Brightness set to 50%. The Lamp Glow Effect Duration is defined as 1000000, creating a smooth fade effect when the lamp turns on or off. The remaining lamps –2, 3, and 4—are marked ‘Unused,’ as only one lamp output is required for this dwarf signal’s STOP indication.

Moving on to Rule 2, labeled ‘29–Clear,’ this rule signals the train to proceed along the mainline by setting the track speed to Clear/Proceed and displaying a green aspect indicator, shown here as ‘G, G/R – Proceed on Mainline.’

This rule is activated when the Node firmware receives the Set Aspect Rule Event ID (05.01.01.5C.66.15.03). Similar to the STOP rule, this Event ID signals the system that the CLEAR rule is in effect and activates the corresponding aspect lamps. The Aspect Rule Set Event ID (05.01.01.5C.66.15.04) confirms the rule is active, allowing additional actions like updating downstream signals. When the rule clears, the Aspect Rule Cleared Event ID (05.01.01.5C.66.15.05) is sent, resetting the system for the next signal state.

For this rule, Aspect Lamp 1 is configured to Lamp Output 1, which connects to a green LED in the signal head via the LCC Fusion Signal Card’s Lamp 1 connection. The Lamp Phase is set to Steady, and Brightness remains at 50%. The Lamp Glow Effect Duration is set to 1000000, providing the same smooth fade effect as the STOP rule. The remaining lamps –2, 3, and 4—are once again marked as ‘Unused,’ as only one lamp output is required for this indication.

With both rules defined, the signal transitions between STOP and CLEAR seamlessly based on the received Event IDs. Rules 3 and 4 are configured with all lamps marked as Unused, resulting in no aspect being shown. Effectively, these rules are not defined and are ignored by the system. In the next segment, we’ll dive into additional rules and configurations to expand on these basic aspects. Stay tuned!

Closing:

This walkthrough explains how Card 1’s Mast 1 is configured for a dwarf signal with two rules: Stop and Clear. Each field in the example has been explained to highlight its purpose and relevance. In the next video, I’ll demonstrate how to validate and test this configuration.