by Detlef Kurpanek/photos as noted
What if I told you there was a system out there that would allow you to integrate all types of layout control functions such as track occupancy detection and turnout position; provide a means to generate realistic signal indications; allow control of layout accessories such as crossing gates and even layout lighting; all seamlessly integrated into a personal computer (PC), if so desired? This control system would be stand-alone, which means it can start up and run without a computer connected to it. Plus, it’s easily expandible, using open-source communications. Not possible, you say? Somewhere out there in the far future? Not at all, and it is here today. Welcome to Layout Command Control (LCC).
This three-part series will provide an introduction to LCC, including what it is, what it does, a high-level look at how it works, and some ideas on how you can apply these systems to your layout. Whether you are someone who has never heard about it, or someone who is ready to dive in, hopefully this will provide a good foundation of understanding, and perhaps even an encouragement to give it a try!
The impetus for me implementing LCC was control of a staging yard on my layout. The staging yard is nine tracks wide and can hold three trains each. With the clearance between the top of the rail and bottom of the deck above, it at right around 14 inches, it was hard to tell which trains were on which tracks. Additionally, I needed a way to confirm the entry and exit routing so I was not running trains into occupied tracks. Furthermore, I wanted whatever system I ended up installing to be expandable to allow control of the main line switches, signaling and possibly integrate the option of centralized traffic control (CTC). While we operate with track warrants during my operating sessions, I wanted true automatic block signaling (ABS) to provide protection for the trains.
ABOVE: While DCC is designed to run trains, LCC is designed to run the layout, everything from track detection and signaling to accessories. —Robert Bridges photo
In addition, I had a few other criteria I wantged to see in my layout control system:
Signal system must run independently of a PC. While I don’t mind a PC for dispatching, I wanted the layout controls, including turnout push buttons and signals, to come on and function 100 percent independently of a computer. Sometimes I just want to come down to my layout to run some trains, and not deal with booting up a computer. However, I also wanted the system to easily interface with a PC, if desired.
Minimal programming. I built a junction using Arduino controls (Arduinos are small, affordable microprocessors and controllers that can be programed to perform specific tasks). Sure, it was very doable and cost-effective. But I felt the wiring of the shields (expansion boards) and programming was quite burdensome. Having addressed one junction in this manner, the prospect of interfacing multiple Arduinos over the entire layout was daunting.
Hardware needs to be readily available and easily wired. This was something else that I learned from installing the Arduino driven junction. Having input/output (I/O) cards ready to go is very important!
Flexible enough to handle complex interlockings. Rarely on our layouts do we have a simple single track main with nicely defined blocks running block after block. The hardware should be up to the task of controlling junctions and interlockings that include complex trackwork and multiple points of entry and exit.
A decent support community. I was ready to take a deeper dive into LCC, but some kind of coaching along the way would be helpful.
Looking at options, the list quickly became pretty short. No disparagement intended, but in short, most layout control systems were ultimately PC-based. Loconet, Computer/Model Railroad Interface (C/MRI), and others bring the data to and from the layout into a PC for processing. For the most part, most systems out there have any required logic running in the PC.
ABOVE: LCC will seamlessly integrate into a PC through JMRI (Java Model Railroad Interface) or other platform. What makes it unique is that the logic lives in the LCC nodes, regardless of whether the PC is on or not. It can even be set up so the nodes will operate differently if the PC is to provide control or not. —ARHS photo
The Arduino option, while very cost-effective, did not offer a “plug-and-play” solution that I was looking for. Setting up communications protocols, addressing, memory, and so forth is not a part of the hobby I care for.
Dedicated and packaged signal systems had some appeal. But for the most part, they had limited ability to interface layout controls, and the ability for them to display complex signal indications in response to interlocking switch positions and occupancy was just not there, or required considerable effort in assembling their discrete logic boards.
ABOVE: LCC allows for relatively complex signal indications to be developed. Here two three-headed signals protect the Turay Crossovers, and the signals function both to indicate to the engineers whether it is clear to proceed, as well as provide route information and permission to enter the yard.
This brought me to LCC. This was something new to me, and something none of the other layout owners in my area had tried. Yes, this would be something of a challenge, but I don’t mind trying something new. From what I discovered, LCC seems to carry a bit of stigma with it: it’s the “next thing” in model railroading, but somehow is always just out of reach, with a limited number of vendors, a new technology with a steep learning curve, and so forth.
But my research and experience shows it is far from that. The hardware is available and reliable, and there are many home and club layouts that are using it. There are a wide variety of products available as well. New products come out regularly and even more are planned to roll out in the near future. It’s almost like the best kept secret in model railroading! Let’s get to it…
