Table of contents
Table of contents
- Auto-Discovery and Plug-and-Play Configuration
- 1. The Traditional Configuration Problem
- 2. Every Fusion Card Identifies Itself
- 3. The Node Card Handles Discovery and Coordination
- 4. Automatic CDI Population
- 5. Manual Addressing Is Required — Manual Configuration Is Not
- 6. Plug-and-Play Expansion
- 7. Consistency Across Layouts and Installations
- 8. Designed for Change
- Why This Matters
Auto-Discovery and Plug-and-Play Configuration
How LCC Fusion removes manual addressing, reduces setup effort, and keeps systems consistent as they grow.
Once the roles of the Node Card, I/O Cards, and Breakout Boards are understood, the next question is often:
How much configuration does all of this require?
In many systems, the answer is “a lot.” In LCC Fusion, the answer is as little as possible.
Fusion is designed so that cards identify themselves, integrate automatically, and present meaningful configuration information without requiring the user to manage addresses, offsets, or internal wiring details.
1. The Traditional Configuration Problem
In many automation systems, adding a new board means:
- selecting or setting an address
- avoiding conflicts with existing boards
- updating documentation
- manually mapping inputs and outputs
- remembering how everything was wired
As layouts grow, configuration becomes fragile. Small changes can ripple through the system, creating errors that are hard to track down.
Fusion was designed to avoid this entirely.
2. Every Fusion Card Identifies Itself
Each Fusion card includes onboard identification stored in EEPROM.
This information describes:
- what type of card it is
- what capabilities it provides
- how it should be represented in configuration tools
- how it fits into the overall system
When a card is plugged into the Fusion Node Bus Hub, it does not need to be “declared” or manually registered.
The system discovers it automatically.
3. The Node Card Handles Discovery and Coordination
The Node Card continuously monitors the cards attached to the Fusion Node Bus Hub.
When a card appears, the Node Card:
- detects its presence
- reads its identification information
- assigns internal resources as needed
- integrates it into the configuration model
From the user’s perspective, the card simply becomes available.
No addressing decisions are required.
4. Automatic CDI Population
One of the most visible benefits of auto-discovery is how it affects configuration.
As cards are discovered, the Node Card:
- builds the Configuration Description Information (CDI) dynamically
- presents only the configuration fields that actually exist
- labels entries with meaningful descriptions tied to the card
Users see:
- real card names
- real capabilities
- real configuration options
They do not see placeholders for hardware that is not present.
5. Manual Addressing Is Required — Manual Configuration Is Not
I²C systems require unique addresses, and LCC Fusion is no exception.
During build or installation, the installer assigns the appropriate address information to each card.
Where Fusion differs is how that addressing is used.
Once a card is installed, the Node Card detects it, reads its identity, and incorporates it automatically. The user does not configure addresses in the CDI, track address ranges, or manage offsets during configuration.
Addressing is handled once at installation; configuration is driven by detected hardware.
6. Plug-and-Play Expansion
When a new card is added to the hub:
- Power is applied
- The card identifies itself
- The Node Card integrates it
- Configuration entries appear automatically
Nothing else changes.
Existing cards continue operating normally. Existing configuration remains intact.
Expansion becomes routine rather than disruptive.
7. Consistency Across Layouts and Installations
Because discovery and configuration are automatic:
- systems behave consistently
- documentation matches reality
- installations are repeatable
- troubleshooting is easier
This is especially valuable for:
- club layouts
- modular layouts
- educational setups
- systems built by multiple people
Everyone sees the same structure and the same configuration model.
8. Designed for Change
Layouts change. Cards are replaced. Hardware is upgraded.
Fusion’s auto-discovery model supports this naturally.
When a card is removed:
- it disappears from the configuration view
When a card is replaced:
- the new card identifies itself
- configuration updates accordingly
There is no need to manually clean up stale entries or re-map unrelated hardware.
Why This Matters
Auto-discovery is what allows Fusion to feel modern and approachable.
It ensures that:
- hardware changes do not require configuration overhauls
- users do not manage internal addressing
- systems remain understandable as they grow
- mistakes are minimized
Instead of asking users to adapt to the hardware, Fusion adapts the configuration to the hardware.