Now that we have some basic automation running and, most importantly, some feedback on how it is running, it’s time to account for error conditions. The post from 2018-02-12 did mention that earlier but it was more academic with any actual basis. Now I do have basis:

• On the Branchline, a repeated issue is the RDC failing to stop and reverse on the reverse block.
• Now that the RDC is moved to the mainline, I did experience the same issue at least once. However that’s not clear cut as in this instance I was also trying to update/restart RTAC remotely. It happened in a second instance for the RDC.
• At least once the same issue happened with the Amtrak train.

That picture is, ironically, exactly what I want to avoid and which happened:

In trains parlance, this is called a runaway.

So it’s the beginning of January 2018, I am being told the museum opens in one month and I have two engines that are constantly derailing. Not a good way to demonstrate that automated train layout that I’ve been working on for the last 2 years (or at least trying to, when I had access).

Logical plan: have backups. Nothing new, I had mentioned this multiple times in the past. In an effort to move on towards that goal, I got hold of some of the previous GGMRC-owned engines appropriate for the task, namely three P42 and three GE Dash 8-32BWH. The P42s seem in dubious shape, having run quite a lot.

The three GEs seemed better. One was still DC and two had their original Atlas decoders and seemed to run adequately. These are from the Atlas Master line, and came equipped with dual DC/DCC decoders.

After some lubrication (and learning the hard way how to take the shells off) followed by basic speed matching, two GE Dash 8-32BWH are used in the automation program and we get through the Randall Museum’s Reopening Ceremony fairly well, including two follow up Saturday.

The third Saturday is the Science Fair exhibit at the museum. Very large attendance. Record on the RTAC tablets show that the branchline RDC ran 120 times (!) and the Amtrak train ran 45 times.

And by the end of the day one of the engines stalls on some turnouts.

I take both engines home, remove the shell and realize that one of the motor is… smoking :-/

Running under automation is only one aspect for the train model railroad on the Randall Museum.

The other aspect is supporting people who want to run on Saturdays. There are a few challenges to solve here, such as complying with museum requirements and defining our own screening and approval process. That could be tricky since ex-members might want to run as if they were back in their old club, using their old ways.

One point I have been trying to make is that running on this layout is more tricky than it looks. The panels are confusing, labeled yet hard to understand. Most people have the natural bias of overestimating their own proficiency and that is clearly visible when operating this layout. That is why I want to insist in everyone, including ex-members, in having a training before running again yet at the same time there’s little traction for it from said people -- the typical “how hard can it be”.

But before getting there, one issue to address is the lack of maintenance on the mainline.

5913 approaches turnout T322. The point was stuck and throwing it shorted the mainline.

Now that the barrier is up, the automation toggles are hard to reach.

The original design goal was that operators can quickly look whether the toggles are physically up or down, and being able to easily flip with up or down. So having them in a central location made a lot of sense. During the renovation, we used to work in the middle area and have direct access to the mountain panel. Now we don't.

What would make sense now is to have them in the valley panel area.

Another choice is to have both, e.g 3 state toggles (off, rest, on), repeated on both panels. Push up for on, down for off. The computer keeps the state. By then at that point, we might as well not have physical toggles and move the control to the tablet. The “downside” is that it makes the tablet indispensable for the automation, which is a big no-no.

Issues noted during the Randall Opening Day:

• Passenger:
• One derailment from 204 going down on B320 between the signal bridge and the turnout.
• Two derailments from 209 going up right when leaving the station. This is again a very very subtle left turn.
• Branchline:
• About 4~5 times, the RDC stopped at a station and never left again. One time it missed the stop at the reverse station.
• 2 times we couldn’t figure where it was.

To deal with the Passenger train issue leaving the station: this happens where the train accelerates and there’s a very very slightly left curve. ⇒ Delay the acceleration till the train is in the straight line after, which leads to a right curve.

The main passenger automation runs using two new Rapido F40PH engines. They have superb detail and superb sound.

Since we use them for the automation in a back-and-forth route, our initial concern was that some dirty track where the engine stops and reverse would have them lose power. Thus we got two ESU current keeper which I installed.

Many weeks pass and I finally complete the automation of the route. At first everything is fine and then we realize quickly that one engine derails consistently in one of the curves, just before the canyon bridge by the entrance.

Oddly enough we have seen hundreds of engines go through that route, and even though the layout track is not exactly new, it does seem OK.

Description of Issue

Engines often stop / hesitate on the turnout. Some pass unaffected, others totally stop.

Frog issue: Measurement with multimeter shows a DC offset of 3 V on the frog.

The power for the Branchline includes a Lenz Digital Plus LK100:

http://www.lenzusa.com/1newsite1/Manuals/lk100.pdf

This is a DCC Reverse Loop polarity reverser.

Yes, the branchline is a reverse loop.

An engine going from B321 (mainline) to branchline will come “in the back” in the tunnel in the reverse direction.

The signal mast on Sonora is a double track signal bridge.

What we want, for trains going up hill:

• T330 Normal aka “mainline” (block 320). Mainline green, Siding red.
• T330 Reversed aka “siding” (block 321). Mainline red, Siding green.

First I need to identify wires under the layout, there are likely 6 of them, 3 for each signal.

Apparently most of these use a common anode (e.g. http://www.sbsignal.com/ho-signals-and-systems.html).

[Update ⇒ 5, one is a common anode.]

Issue: short push on activation buttons are not detected fast enough by the AIU01 polling.

Solution: use a basic RC to make the signal seem longer.

Experiment at home:

• Use a 1000 µF between GND and the input.
• Use a 110 Ω R in serie from input to button (to avoid shorting the capacitor).
• This results in a hold time of about 5-7 seconds when fully charged.
• When powering up, this also activates the input while the capacitor charges.

Quick drawing: