DCC++EX is definitely a lower cost way to go, and while JMRI may not be required to run trains with WiFi throttles, I wouldn't be without JMRI Decoder Pro to program them, and that takes four boards boards to do that (three for a Tinkerer level project). Whereas a turnkey Pi SPROG 3 system is two boards (Pi & SPROG hat) in a custom case, comes with both power supplies, and an SD card that boots the Pi up with Panel Pro and Wi-Throttle server running. You select the option at purchase for access point or station mode WiFi, and either is easy to change with a single config file (printed documentation included). But it's $190. You can add a KVM or separate monitor/keyboard/mouse for GUI access, or just VNC into it from another computer (what I do). But just running trains and throwing switches requires only a Wi-Throttle-compatible throttle or app. Is it possible that a future version of DCC++EX could use the programming track output as a secondary, auto-reversing track output that duplicates the primary track output? The upcoming Pi-SPROG 3 Plus (and USB-based SPROG 3 Plus) has a secondary DCC output that can be configured as a programming track output, duplicate layout output, or auto-reversing layout output. Both outputs can supply up to 2.5 amps each. Seems like a very useful option for a system that has two DCC outputs...
The current version of DCC- EX has the <1 JOIN> command that joins the two tracks (using separate H-Bridges). This saves you from having to waste a piece of track for occasional use. We also have a "driveaway" feature. It is implemented in Engine Driver. When done programming, the program track turns into main and you can just drive the train off the siding or whatever isolated track you are using to program. Have to think about autoreverse. We are working on power districts now.
Are you saying that a section of track can be wired to the program track terminals and be switched between program track and main without a DPDT switch but via engine driver? If so what version of engine driver and DCC++EX do we use? Thanks, Sumner
NCE makes an Auto Switch module that can be used to create separate main and program track outputs. The main output does not get programming commands and the programming output does not get ops mode commands. However, you can use it just to run the main track, and still send the unswitched bus to the program track, for the same effect discussed for DCC++EX. It interprets the DCC commands and connects the main or program track output to the input accordingly. It works with any DCC system AFAIK. You can use a second Auto Switch for a "dead track" section, between them, to prevent a walking, programmed locomotive from crossing the junction between main and programming tracks, thus shorting the programming track to the main and conveying programming commands to the mainline.
Yes, it is all done in the code. There are no switches. There is a <1 JOIN> command from 3.0 and then "driveaway" in 3.1 and above of DCC++ EX. I'm not sure what version of Engine Driver supports it. I'll find out. Mine updates automatically. You can put a loco on the programming track and acquire it there. Program it and then just drive it off onto the main track. It syncs the DCC signal between the 2 H-Bridges and also makes them both main tracks. There are other new features like automatically discovering a DCC-EX Access point and showing it in the list, the ability to request a loco's ID, and something I asked Steve for, haptic feedback on my throttle speed slider I just like the feel of it "clicking" along the imaginary "stops".
