Stationary or Accessory Decoders

Search for stationary or accessory decoders.  There are several on the marker that will do exactly what you want.

Digitrax DS64

@ AJay, Since you are considering Digitrax, you might consider their (recently superseded) DS64, four Tortoises per DS64.  A few days ago Litchfield Station (an MRH sponsor) still had several in stock, and other vendors may also have some remaining stock.

The DS 64 will also allow you the option to install push-switches where your DPDT switches are currently located, allowing you to control the turnouts locally if desired, as well as being 'network' (LocoNet) controlled.  This includes feedback to the LocoNet.  Especially useful if you are considering any type of remote or automated control.

If you don't need feedback and local control, the Digitrax DS44 is a less expensive solution.

EDIT: If you plan computer controlled signals, the Digitrax SE8c is an even better solution, 8 Tortoises, optionally 8 push-switches, and up to 32 signal heads per board.  FWIW I am using several of the DS64's and SE8c's on my layout. (and have upgraded from a Zephyr to the DR5000)

Good luck!!

DCC controlled turnouts

Standard ElectroFrog turnouts don't have frog polarity controlled by the switch machine, they get their power through the points themselves, and thus aren't DCC friendly (but many DCC layouts use them, and if maintained well, they can work reasonably well). Have you modified ElectroFrog turnouts to have the polarity controlled by the turnout machine?

In terms of turnout control, start out with what you have now, and then once you get DCC up and running, you can decide if you want control of the turnouts through LocoNet or DCC.

On most layouts, in most cases, DCC or LocoNet control of turnouts is not needed, and mechanical or DC-powered systems work better for controlling the turnouts. There are some use cases, like dispatcher control, remote operations control, or making complex routes, where controlling turnouts with DCC or LocoNet makes sense.

Think through what your use case is, and what you are trying to achieve beyond what your current DPDT switches do before converting turnout controls over to DCC or LocoNet, as this will inform what method to use. If you decide that having only local control is fine, then keep the DPDT switches. On my layout, I want physical toggle switches, and don't need dispatcher control, so the turnouts are powered with 12VDC through DPDT switches, with isolated frogs powered by the aux contacts on the Tortii while the track is powered by Digitrax.

a couple of examples

The above are correct, but let me give you a specific example: I use NCE SwitchIt8's, which are stationary decoders that have DCC signals going in and 8x connections to stall motor switch machines (Tortoises). I happen to use JMRI to control them. In other words I taught JMRI that the siding at West Ham is switch 9, and when I tell it to throw the turnout at West Ham, it sends the appropriate signals to that Tortoise.

There are many stationary decoders, but I picked with SwitchIt8's because each board handles 8 turnouts, of which I have a fair number in yards, making them both convenient and relatively inexpensive.

Decoder to replace DPDT turnout switch

Thanks for the info. I'll consider those options when the time comes.

Throttle control of turnouts

Do people like switching turnouts from the throttle? I had that on my earlier layout and didn't like it much. Current rebuild is just going to use Peco and finger flick. If any not within easy reach I will just use the Peco motors.

Controlling turnouts from the throttle

I wouldn't think so. DCC makes sense for dispatcher control, you could use the throttle temporarily while setting up fascia pushbuttons for them, but I wouldn't think people would want to use a throttle to control turnouts in most cases. Even routes can be set up with pushbuttons through a variety of means.

For local switching and Form D/TWC/OCS and TT&TO territory, the ultimate is a wireless DCC throttle with local turnout controls on the fascia or layout. For CTC or Rule 251 territory with towers, the ultimate is a layout control system with the dispatcher or tower operator controlling turnouts, and a wireless DCC throttle. 

The only way….

I’ve used the throttle for turnouts significantly is for routes.  It always seems that when I have routes established something happens like a throttle update and they all go away.  Ug…. Occasionally it is very handy when I’m on my back under the layout to throw a singe switch with the throttle to watch the switch machine perform.  Otherwise the push button on the facia works very well.  The old Switch’s-its and Wabbits were my choices because I could use a bi-directional LED, a single push button and track power.  The power consumption for 40 switches in less than 1 amp.  The group of components also made for a good looking and good operating assembly.  The power for the Tortoise switch machines is also supplied from the switch-it or the Wabbit.  The only thing I would change is to use capacitive “push buttons” instead of the mechanical ones.  I have a dozen switches to reinstall in two side by side staging yards that have five tracks each and two more stub ends.  I want to use an Arduino to choose the thrown switch and keep the rest routed.  I will have all Tortoise switch machines when I’m finished.

Re Routes

Yes, good point about routes. as mentioned above I did use a stationery decoder and set up some routes and it was pretty neat to use. However that was when I was using NCE. I am now using Lenz which doesn't seem to support routes.

Our club layout has toggles on the fascia adjacent to the turnout. The turnouts are marked with numbered mileposts so it is easy enough to identify the correct toggle but it still requires looking away from the layout to the fascia.

Routes

Routes could be handy in a very complex application with multiple overlapping routes, but in most cases, you could do routes with a pushbutton, whether through a DCC decoder like a DS74 or via LCC. The system can do routes, but they can also be done through the decoder and LocoNet, without system support.

more on routes

I didn't mention that I mostly use routes rather than throwing individual turnouts from the throttle. I do it via JMRI, so it is relatively more straightforward to preserve the configuration against resets/disasters. Since JMRI saves this stuff as a file, regular backups mean that it is not terribly difficult to recover from such problems. (I'm computer skilled, so I regard the recovery process as essentially trivial: stop JMRI, copy the backup files to their locations, restart JMRI.)

I agree that with computer support such as this, it is entirely feasible to have both fascia pushbuttons as well as throttle control. I didn't do that on my prototype layout, but I plan to do so on The Real Thing. I plan for the pushbuttons to be linked to a mix of individual turnouts (say, in the case of passing sidings) and routes (yard throats). With JMRI, both are simultaneously available to the throttles.

For context, both layouts are fully capable of being operated by the JMRI Dispatcher, which was originally one of the motivating reasons for both powered switch machines and then centralized control. The fact that the throttles have access to the turnouts and routes was actually an accidental byproduct, although I'm glad of it.