DCC++ EX and Turnout Control

Hi all,

Still planning my new mid-sized layout and intend to use DCC++ EX for running locos. I expect only to run 2-3 locos max. I have 16 turnouts and used AnyRail to plan the layout.

My basic question which I have struggled to get answered since most videos/research I have found go into detail without a general overview so I thought I try this learned group.

I’d like to use DCC++ EX for locos running on an Android phone using EngineDriver and possibly JMRI and PanelPro to control switches on a tablet. Since I used AnyRail I noticed I can export the plan for PanelPro.

Since I have a small number of turnouts and plan to operate the layout only by myself I’d like a very simple way to control the turnouts but didn’t really want to build a control panel since it appears the technology has advanced so much. I also would hope to find a relatively turnkey solution to start and then, if I get advanced expand to other automations. I looked at Cobalt Alpha Control as a possibility but not sure if that is a good approach as it looks a bit dated.

With all that said, if I am making sense, any insight and how to start would be very much appreciated.

1 Like

use your fingers to throw the turnouts. no control panel required.
I did it for years on the main line just make sure each turnout has a keeper spring on the throw bars. The only places I used slow motion switch machines is in the yards, I had a control panel at each yard for the operator to control turnouts in front of him where tracks were closer together and reaching cars is a pain. As far as using an Android phone you’ll need some kind of interface that works with Android.
You may want to post this same question at Model Railroad Hobbyist Magazine forums They also are a free to use forum,
There are a couple of people there that are really on top of all that phone control and going wireless with phones as well as operating everything by phone. I think a couple of them were in on inventing the interface and a few of them explain everything step by step. Hope this helps!
Dan

1 Like

You are aware that if you import your AnyRail plan into PanelPro, if done properly, it will automagically build a logical panel for you and enumerate your turnouts, so you can operate them from ED, right?

I built my four control panels in JMRI before any of those tools were available (it was fairly simple once you grasp the basics), so I cannot offer any real help with how it’s done. But I’m sure if you look at the JMRI doc and ask your questions on jmriusers, you will get the info you need to proceed.

The JMRI developers hang out on that list. It’s really the best place for JMRI questions/issues/etc.

2 Likes

What is your reason to wanting to control them via DCC and JMRI? Do you want to create routes? Some sort of scripting?

If you just want to throw them, use ground throws, mechanical toggles, or switch machines with simple DPDT switches mounted in the fascia.

For some reason, people seem to jump into DCC thinking that for some reason just because you’re using DCC to run trains that you should run switches on DCC. DCC turnout control can be great for computer automation, dispatcher control, or using macros to throw a bunch of switches into staging, for example, but if you want to control them one at a time… just control them electrically or mechnically.

1 Like

Actually to your point, my thinking has evolved over the past few days, now my approach is to create a separate DC bus for just accessories, primarily switches and build my own panel. So you have just reaffirmed my thinking, thanks.

With that said, assuming you are fairly well versed on DCC, I’m heavily leaning towards DCC++ EX and have a 4 reverse loops which I’d like to address with a PSXX-AR, does anyone see any issues with using that device with DCC++ EX?

As always, any help is most appreciated.

1 Like

DC bus makes sense for switches, that’s how I do it on my switching layout.

As long as the DCC-EX system you’re using has enough current, it should be fine. The PSXX boards are fast. The EX-CSB1B can output 5A, so that should work with the PSXX boards and provide plenty of power. The EX-CSB1B is an insane value for a purpose-built DCC board for $145 US with a power supply.

1 Like

That’s exactly the direction I’m heading so thanks for the reaffirmation. This community is the best for helping out us newbies to make good decisions.

Any thoughts on switches if I go the DC route? I’m open but probably leaning towards Cobalt or Tortoise. I will be buying all new locos so not worried about powered frogs or DCC needs at all. I welcome your best thinking.

Thanks again.

1 Like

Most people are happy with just using finger flick or ground throws. I use Tortoise motors with my Fast Tracks, as I need a way to switch frog power as well, although there are options for that with ground throws, Blue Points, or you can use Frog Juicers. If you want motors, Tortoise are tried and true, the Cobalt iP Analog appears to be quite good, they’re popular in Europe, and the MP-4/5/10 motors are very compact and quite good as well.

1 Like

Just as a counterpoint, I usually throw my DCC-controlled switches one at a time. I do have a few routes set up for my yard ladder, but I seldom use them.

But by using DCC and JMRI panels, I can throw individual turnouts from virtual panels on tablets located (or carried!) around the layout, as well as from ED, without having to build physical panels, or install another bus (the DCC bus is already there) and the associated toggles, etc.

And if I ever decided I wanted physical panels instead of or in addition to the virtual ones, I could do that, too, since my DCC stationary decoders accept simple push-button inputs. With the DCC system tied into JMRI, those turnout position changes would also be reflected on the virtual panels.

An added benefit is that if the layout configuration ever changes, all it takes is a few edits to your JMRI panel. No additional DC bus wiring or toggles, no unfilled holes where the old toggles were, etc.

Oh, and even if you’re running a DC layout and insist on running another bus, why not make that bus a simple DCC system, a stand-alone LocoNet, or LCC? Then you can take advantage of something like JMRI’s virtual panels while still using analog DC to run your layout.

My point being, there’s lots of flexibility in all the various methods. If you get stuck on “This is only good for that”, you’ll likely lose out on potential solutions.

1 Like

I’ve operated on one layout that used tablets with JMRI. While I’m generally not a fan of the touchscreen interface, and would just prefer ground throws, I will admit that it was useful with a clogged up aisle during an op session, as the tablets were mounted, but they’re tablets, so I just took it out of its holder and moved it 10’ down the layout and I could remotely control the turnouts.

I just generally don’t think that DCC control of turnouts is either worthwhile or a good interface if you’re going to throw individual turnouts on the layout manually. It’s great for automation, CTC, or setting up complex routes and triggering them with a control panel wired to LocoNet, LCC, Mini Panel, etc.

1 Like