Table of contents
Table of contents
- Planning a Layout with LCC Fusion in Mind
- 1. Start by Thinking in “Scenes,” Not Wires
- 2. Identify the Devices in Each Scene
- 3. Map Devices to Breakout Boards First
- 4. Choose Hub Locations Based on Scenes
- 5. Decide Early: Centralized or Distributed
- 6. Plan for Growth, Not Completion
- 7. Don’t Over-Plan I/O Cards Early
- 8. Think About Maintenance and Access
- 9. Planning Is About Reducing Surprises
- Why This Matters
Planning a Layout with LCC Fusion in Mind
How to think about structure, placement, and growth before building or wiring anything.
With the core concepts of LCC Fusion established, the next step is planning.
This article is not about schematics, parts lists, or installation steps. Instead, it focuses on how to think about a layout when Fusion is the control system—so decisions made early remain valid as the layout grows.
1. Start by Thinking in “Scenes,” Not Wires
Traditional planning often starts with wiring questions:
- Where does this wire go?
- How many conductors do I need?
- How far back to the control panel?
Fusion planning starts differently.
You begin by identifying scenes:
- a siding
- a yard throat
- a town
- an industrial spur
- a signal bridge
- a module
A scene is simply a group of devices that work together:
- turnouts
- signals
- detection
- sensors
Scenes become the natural boundaries for hubs, cards, and breakout boards.
2. Identify the Devices in Each Scene
For each scene, list the physical devices involved:
- how many turnouts
- how many signal heads
- how many blocks
- how many sensors or indicators
At this stage, you do not worry about:
- wiring paths
- cable lengths
- addressing
- configuration details
You are only identifying what exists.
3. Map Devices to Breakout Boards First
In Fusion, devices always connect to breakout boards, not directly to I/O cards.
Planning becomes much clearer when you ask:
- What breakout board does each device require?
- Where can that breakout board be physically mounted?
This naturally answers:
- how many network cables leave the hub
- where short device wiring will live
- where access is needed for maintenance
4. Choose Hub Locations Based on Scenes
Once scenes are defined, hub placement becomes obvious.
A Fusion Node Bus Hub is typically placed:
- under a scene
- near a group of related devices
- where breakout boards can be reached easily
Good hub placement:
- shortens device wiring
- reduces clutter
- improves troubleshooting
- supports future expansion
You are not choosing a “central control panel.” You are placing local control points.
5. Decide Early: Centralized or Distributed
Fusion supports both styles equally well.
Centralized approach
- hubs grouped in a drawer or cabinet
- network cables run out to scenes
- easy access to electronics
Distributed approach
- hubs placed near each scene
- one network cable between hubs
- minimal device wiring length
Neither approach is “better.” The layout geometry usually makes the decision for you.
6. Plan for Growth, Not Completion
Most layouts grow.
Fusion planning assumes:
- more turnouts will be added
- more signals will appear
- detection will expand
- logic will become more sophisticated
Good planning leaves:
- empty hub slots
- room for an additional hub
- accessible cable paths
You don’t need to plan everything up front—but you should plan so nothing blocks future expansion.
7. Don’t Over-Plan I/O Cards Early
It is tempting to map every card type in advance.
Fusion allows a lighter approach:
- plan by capability, not exact card count
- allow card selection to follow device installation
- let auto-discovery shape configuration later
This reduces upfront decisions and avoids premature constraints.
8. Think About Maintenance and Access
Planning is not complete without considering:
- how you’ll reach breakout boards
- how cables can be unplugged
- how a card can be replaced
- how a module can be disconnected
Fusion’s use of hubs and network cables makes this easier—but only if access is considered early.
9. Planning Is About Reducing Surprises
Good Fusion planning ensures that:
- wiring paths are short and obvious
- hubs are never overloaded unexpectedly
- expansion doesn’t require rewiring
- configuration aligns naturally with hardware
When planning is done well, the build and installation phases feel routine rather than stressful.
Why This Matters
Fusion is designed to remove complexity—but good planning ensures you actually benefit from that design.
By thinking in scenes, hubs, and breakout boards:
- wiring becomes predictable
- expansion becomes routine
- documentation stays accurate
- troubleshooting becomes local
Planning with Fusion in mind turns layout automation from a wiring challenge into a structured design exercise.