Have you ever automated any of your layouts or parts of them? Have you setup your staging yards for automatic operations so that you could “rail fan” your layout?
If so, tell us how you did it. Try and keep it fairly simple if you can. System used, how much did you automate, what it would do, etc.
I’ll start off with what I have done on my last layout. I automated a four track staging or storage loop. A track plan is below. I used a CTI Electronics Train Brain system connected to an old 486 computer I had laying around.
Edit: See www.cti-electronics.com for more information. The CTI system has different modules available and will inteface by computer with most major DCC systems that have a computer interface connector.
The program was set up to bring trains out of staging at specific time intervals (Timetable) as setup in the program. The first train would go around the layout one way, and the next train would go around in the reverse direction. This would continue until the program was stopped or a train did not return to staging (due to local switching) when it should have. Things would resume when the delayed train returned to it’s staging track. Each train was assigned a specific track and this could not be changed unless the operator intervened.
When the program would start, sensor S-1 would indicate that a train was present on track one. If not, the program would pick the next train. Turnout T-in/out, T-1, and T-2 would line up for track 1, and the train from track 1 would start up and exit the staging track. After a few seconds (by timing), the train would speed up to go up the grade on the Lead to the layout. (The storage track lead was about 16 feet long with a 3% grade.) When S-5 was tripped at the top of the grade, the train would slow down to layout speed and go onto the layout in the direction that the compu
I semi-automated my last layout without any fancy system. It was basically a folded “J” shaped dogbone, with a double track mainline and staging tracks in one of the return loops. I installed a signalling system using 7 of the NMRA block detectors. Relays operated the signals and controlled power to a section of track ahead of each signal. This prevented a following train from proceeding past a red board.
I manually selected which trains to bring out of the staging onto the layout. After an interval another train could be started, and so on. I usually operated 3 or 4 trains following each other around the trackage with no danger of a rear end collision. Operating more was possible, but involved a ot of stopping at red boards. All trains went through the staging on the through track unless I diverted it to one of the holding tracks.
I was not interested in operations, such as switching industrial sidings, etc. There weren’t any. This satisfied my craving to be a train watcher which you seem to be.
For my layout in planning, I have seen the error of my ways and am designing a layout that is designed for operations as well as continuous running. I will still be using an automated signal system, because in that way I can have a lot more trains running at one time using DC than I could possibly manage operating with DCC.
Although my layout operates point-to-point, the track makes a complete circle through a hidden staging yards. This allows me to re-stage unit coal trains.
Sometimes when I am working in the train room (basement) I like to set up several trains to run (same direction) so I can rail fan. It is also therapeutic to listen to the click-clack of the wheels. I use Digitrax Chief with Decoder Pro. I bring up several virtual throttles on Decoder Pro and set the trains in motion. The first lap or two I have to check the speed of the trains to make sure they are operating about the same speed so they maintain their seperation. I have operated up to three trains this way. I could do the same with the Digitrax throttles, but using the multiple throttles from Decoder Pro seems easier.
I have also used Decoder Pro to run a freight (hauller) in one direction wile I operate a freight (turn) in the opposing direction. I could use the digitrax throttles to do this as well.
The control system I use, MZL analog DC, has a ‘fire and forget’ capability that allows me to send a train on its way, secure in the knowledge that when it gets to where I want it to stop, it will stop. This is done with nothing more complex than a couple of cheap diodes, a resistor and contacts on the switch activating device (switch machine or manual throw with electrical contacts.)
One derivative of that capability allows me to send a train to back-in staging. When the train stops, all I have to do is throw the crossover to normal. That changes the locomotive from mainline power to staging power, which then backs the train into the selected staging track. Another diode stops it as soon as the locomotive is clear of the turnouts. In the meantime, I can do something else, somewhere else, and put the staging yard on disregard.
Using single-ended staging tracks cut the turnouts required by 45% and solved some overhead clearance problems in my under-scenery empire. Auto-stop is available to me anywhere I might want it, not only underground, but always, on both routes, at any place where a train can approach a turnout from the frog end.
Chuck (modeling Central Japan in September, 1964 - analog DC, MZL system)
Digitrax. JMRI Panelpro talking to DS54 for exact turnout feedback position and control thru CTC type panel. SE8C for lights and logic under same PanelPro control. Block detection is via BDL168. Looking into transponding a few cabooses for train ID.
Modified existing scripts to get loco back and forth, block to block, hit the lights, turn bell on. blow whistle and head back. But I have to get into scripting further. I’m just putsing around with all this till I get the layout room setup and I have some idea what I want exactly in a layout.
That seems to be MY biggest problem, defining a track plan. I figured out the electronics and DecoderPro/Panelpro on my own and reading but track planning seems to elude me for some dumb reason.
CTI does not say much about their DCC solution on the web site, does it.
One of my layouts was automated; at one time it had so many bugs that every time I turned the power on the first thing I did was automatically begin beating my head against the wall!
[banghead] work! work! work!.. The trick is to start beating before you touch anything. Then if it hurts too soon, you go do something else with your patience.
Setting up all the electronics was fun and most of it worked from the go. Little things did arrise but I was allways able to sit back and think, find out why, and correct them.
The PanelPro gave me the most fits but it was more how the program works that caused the most head beating and not the creating itself. At one point I’d end up with 13 copies of the same panel and tried to figure out what was going on or what I was doing wrong.
CTI’s website has little to say about DCC except to say that it is integrated with it. I too am a CTI user, happy in fact. If you want to know about the CTI DCC capability download their free manual and read the few pages on it. CTI and DCC run in parallel. BOth have to be connected to the computer. CTI will handle locomotive commands with sound easily including throwing turnouts throught the DCC and control accessory decoders fine. It will not, at this time accept feedback from DCC. CTI sells that hardware and chose for business reasons to only allow their software to work with their own feedback detection system, which by the way happens to be as cheap or cheaper than most DCC supplied feedback. (Measured by cost per sensor)
I use CTI hardware to handle block detection and signaling and DCC to do the rest. I am a Hare/Wrabbit decoder user which works seamlessly with CTI.
Why CTI? Because after I looked at 4 different systems, I found it to be the easiest to use. See my write up on the subject and other comments on my blog. I think there are at least 5 different entries including some assessment work posted there, free for your use.
I spent a long time just getting a DCC controlled trolley to go back and forth. I cringe when I think about the money I spent too.
CTI has a very easy to learn language that controls it. You can get started with a full working system from CTI for $99 bucks.
I have 4 separate passenger lines and one freight line on my HO layout which pass through a long mountain tunnel. I want to use the mountain for staging so the trains would disappear and reappear at different times. What would I have to use to cause the delay?
I also have a commuter line which I would like to have the cars go from one station to another wait for a few minutes (for passengers to get off) and return to the original station. Again I would need some sort of electronic delaying and reversing equipment.
If you decided to go with CTI as your automatied control system, you can do it by time. CTI has a function that you can use time, either by the clock on the computer, or by time from when you start the program. You can also set up a delay time from tripping a sensor. When train A enters staging, the sensor trips and train B would start at some amount of time after that. I have tried to get my head around JMRI Panel Pro and just can’t seem to get it. I have no problem with CTI’s control program.
I can definitely recommend JMRI as a good way to automate layouts. You can use JMRI in two ways:
If you are proficient in Java, you can directly write Java code that makes use of the underlying low level code.
If you are familiar with the Python language, you can use the built-in Jython interpreter to run scripts
Either way, JMRI gives you a powerful environment to control your trains. Here is a video of my old Marklin train layout running under JMRI control. I implemented the control software directly in Java.
I visited this place last Sept. In addition to probably hundreds of trains being automatically controlled, the vehicles have working lights (including turn signals!) and are also run automatically - stopping at red lights appropriately and indicating turns when appropriate etc.
