Description of Issue

Back in 2018, we had engines stop-and-go on turnout T161 for quite a while, especially steam engines, or short non-MU engines. The turnout was always in the normal position when this happened. Back then, it was determined the frog power routing on the Fulgurex created a resistance. This was solved in 2018-12-12 by replacing the Fulgurex. The issue re-appeared last year, and it was “fixed” by Allen spiking the frog in place. This worked for a while, and now the issue is reappearing again, with trains going dead on the frog.

Frog issue: Issue is frog power via the Fulgurex contacts. Last time, it was solved by swapping the Fulgurex. Eventually the contracts just oxidize or present some kind of resistance, likely to complete lack of use. And we cannot throw that turnout since the throw bar has been spiked.

We’re having a “dead spot” problem at turnout T161. Again. For the 3rd time.

I was going to ramble at length on the complexities of turnout designs and what causes them to short. Instead I’ve decided to skip that because https://dccwiki.com/Turnout has much better graphics, and better explanations. So please go read that.

One thing I do not know for sure is what kind of turnouts are installed at Randall. I should know. And document it.

Description of Issue

We’ve had some specific steam engines derail here in the past. It was identified the point rails were loose because there is no turnout throw rod at all. Previously the point rails were spiked.

We recently were having problems again with some specific engines, this time being this BLI 844 Challenger. The suspicion was that the spike may have been too high and derailed the engine.

Back in November, I did a major update to the Vision software that drives the Vision computer at the museum for the Train Vision Project. A major issue was the image detection had a lot of false triggers and would erroneously detect a change in the image when there was no motion. I reworked the image analyzer, and I also added logging to capture what motion is detected. The logging system dumps data to a JSON file compatible with the chrome://tracing protocol and the Perfetto web UI, which I can then collect remotely and analyze later.

Here’s an example of run from last Saturday:

What we see above is an automated run from the mainline Freight train. Rows represent cameras 1, 2, and 3 respectively. Let’s look at camera 1 in detail:

This year I’d like my projects to enhance the automation. There are two automation additions I want to get to, namely Fairfield and the Trolley line; however I realize these require a lot of research & preparation work that is mostly software and, if I go there, it will be yet another 6-9 months with nothing tangible for others to actually see.

So instead I’d like to focus on enhancing the variety of the current automation.

1- Branchline Automation

We currently have a single engine running, and we park it on the B811/B801 storage track. However the track & panel supports 3 storage tracks.

Branchline/Mainline Track Diagram (blue is mainline, green is branchline).

I’ve spent some time updating the Randall Documentation git repository. What’s changed:

• There’s a new hardware folder.
• Currently it only contains the PFM Fulgurex documentation.
• I plan to add more to collect the user manual of all the hardware we currently use on the train layout, from the command station, to the various electronic boards such as auto reversers or electronic circuit breakers.
• There’s a new ggmrc_history folder.
• This contains paper documentation I found on the layout’s archives. I scanned them all a few years ago. Scan quality was so-so; image contrast is really poor on many of these. I tried my best to find what they describe and rename them accordingly.

I was particularly interested in the historical documents I could find. They cover a wide time range, from 1965 up to 2010.

Layout wiring standard “adopted June ‘65”.

However these documents are a mixed bag. Some are early design schematics for the mainline or the yards, which may or may not be relevant today. There are some early construction standards for the layout. Others describe equipment which is not there anymore. There are a few yard or panel descriptions that I could not quite relate exactly to the layout, so these are labeled as ‘unknown’.

On the software side, while traveling during the xmas break, I have spent time cleaning up the Conductor source code, which is my script-based software that drives the entire model layout automation. I have not changed any functionality, just done maintenance on the code base; I have modularized the code to split the parser and the script engine into an engine module, and I have updated all the dagger components to make it easier to write tests for just the scripting engine.

I have remotely deployed the new version on the layout, and as desired this update was totally silent and unnoticed.

On the train model side, we’ve had issues with the Branchline for a little while.

Last month, the 2-car Santa Fe RDC from Rapido stopped working. I “solved” that by just running it with only one of the two RDC cars. The unit is also not doing sound anymore, at least not in a consistent manner.  That’s unfortunately the second Rapido RDC unit that developed similar problems. The small motors they use for each truck is apparently the weak link, and since they use two of them, the unit can’t run well once one of the motors fails. For the RDC SP 11, I worked around that by disconnecting one of the motors, making it single-truck powered, which is fine on our flat branchline. I could do that too here, however it won’t solve the sound issue (it does make sound from time to time IIRC so it’s not a speaker/wiring issue, maybe more like a decoder issue).

The other way I “fixed” the branchline automation is by thoroughly cleaning the engine wheels and then scrubbing the track where it was losing power with the Walthers hand cleaning tool.

But at some point we need to just work around the problem and address it. Time for an engine/train change on the branchline.

There’s a similar issue on the mainline. The trains were not stopping at the right spot, and that got solved by cleaning the engine wheels. But more importantly, we’re going to have to swap the engines at some point. Out of the two UP SD70ACe engines, one is out of commission, and I’m currently running with the backup UP 8749. There is no backup for the backup so we’ll need to deal with that.

The easy solution here is to try to get yet another UP SD70ACe once available. Currently Walthers or TrainWorld have none though. In any case, one of the many pending tasks I have is to look at what’s wrong with the first unit and fix it. What I have done in the past that worked well is get any similar unit from the same OEM and just do a shell swap.

Happy New Year 2022 from the Randall Museum Model Railroad team.

2021 was yet another odd year. It was marked by the museum reopening in October. The usual lot of mandatory layout maintenance happened with various things to fix (B91, B320, B321, T150, T320, T450, etc). Some new stuff happened like balloon auto-reversers for Bridgeport yard, and a good amount of time spent understanding the lighting.

I’ve spent the last couple weeks doing background computer maintenance mostly. The kind of stuff nobody at the layout will notice, because things magically get fixed before they are too broken.

If you don’t like computer stuff, you can skip this one as we’re going to get deep in the weeds with Linux commands.

I keep all the source code and configuration files related to the automation in git repositories on Bitbucket. At first I was using my private workspace, and I finally moved the various projects into a proper dedicated workspace:

        https://bitbucket.org/model-railroad/

This now contains three repositories:

• conductor: The main repository that holds the various projects used for the train automation of the railroad exhibit. Most notably it contains the sources for the Conductor software that drives the automation, the RTAC program that runs on the Android display tablets, and a few other Arduino/Pic16f projects.
• vision: The software that runs on the Vision computer at the museum, playing recorded videos, and also playing live feeds from cameras located around the layout.
• randall-documentation: This one is totally new. I moved here all the public documentation I have for the Randall Museum Model Railroad.

The documentation repository contains files for layout maps, layout schemas, layout labels, and all the documentation I wrote for the museum staff and the Saturday Operators. I do have links to that in the introduction page however all the source material was just on my own drive. Now it’s properly archived as it should with proper revisions. One goal of having a public repository is to have volunteers submitted patches to extend it. For that purpose I’ve clarified in the README the license and the file formats that can apply here.