Happy Monday! I have a question (which may lead to several more, I know). I am reworking an existing N scale layout 6' x 3', which currently has two electrically separate (no crossover) main line loops, each loop having either one or two turnouts to spur tracks and each loop powered by it's own MRC 6 Sound Controller 2. These units have limited DCC capabilities. The locos I currently run have a mix of decoders, Paragon 3, Digitrax, ESU, and Soundtraxx. All but two are sound equipped. What I want to do is delete the two MRC units and use in their place a single more modern and capable DCC system. First, will there be any problem powering both loops from a single DCC system? Can I simply tie the two separate power busses together? Second, what system would any of you advise for this use case? I should add that my goal is to be able to run trains on both loops at the same time (up to a maximum of four) from the single system, perhaps ultimately adding a crossover between the two now separate loops. Ease of operation is a big consideration. Main line programming would be a plus. Any and all advice welcome, and thanks in advance!
Yes I don't see why not. Are you interested in putting something together yourself that isn't that hard to do like this .... https://dcc-ex.com/ ? Of are you interested in purely in a commercial unit. I build a DCC-EX system, not expensive, very powerful and love it. I'm aware of at least one other person here who has gone that route also who had/has a well know commercial unit and uses the DCC-EX system now. I just build 2 wireless throttles for the DCC-EX system for under $50 each that will also work with a number of other DCC systems also. You can also use a phone throttle with the system and run a lot of trains at the same time. Sumner
ill second that DCC++EX system cheap and works great with no hiccups. able to run 6 trains no problem . I have 3 amp power plug thingy running everything. You can use a 1.5 amp power source too. Does require a bit of installing sketches ect . But over all fairly easy to set up. I also have a NCE power cab , but its in a box someplace . ever sense i build the DCC++EX i prefer it over any thing and i can use my phone for a throttle controller.. Sumner has a great build on this . step by step very easy to follow, even i can do it. (im not that smart)
Though I live in the US, I joined the MERG model electric railroad group in Europe. They have everything you need if you like building PCBs, I do. I built their 5A booster, command and throttle. for peanuts and they all work with JMRI and even NCE throttle. I'm glad I went this route.
merg is an excellent resource for diy / home made projects ...i based a decoder [non sound] on one of their projects, and it worked to ten dollars each [ for quantity ten] including shipping and assembly an image of the bare decoder is part of my signature
Hard to beat 10 dollar decoders. I'm considering a second throttle. I could use that right now as I only have half a layout and trying to run 2 trains on it is difficult to say the least. I probably should just get busy completing the second half though.
Give this some serious consideration.... https://1fatgmc.com/RailRoad/DCC/WiTcontroller-Index.html You aren't going to build it for $10 but well under $50 and I don't think you can find a better WiFi wireless throttle that will do what this one can do for anywhere near that price plus Peter is adding new features to it all the time. It that can connect to a wThrottle Server (JMRI, DCC-EX and many others). What command station are you running? Sumner
The Pi Sprog 3 Plus DCC system (R-Pi hat) includes a CBUS controller & interface. The SW protocol from the host R-Pi to the Pi SPROG 3 series command stations is also CBUS. JMRI, running on the R-Pi, controls the whole show, including communications with WiFi throttle/apps. Unfortunately, they have no plans to support an NMRA LCC bus on that port. I believe the NMRA standard LCC peripheral bus is a better long-term solution, especially if you are not interested in assembling components on printed circuit boards. Both LCC and CBUS communicate via CAN bus, but are not compatible with each other. LCC command stations communicate over WiFi, primarily for throttles, and to JMRI on a separate computer. To date, the primary provider of LCC (non-throttle) peripherals, and a host/bus USB interface is RR CirKits (despite their name, they offer only assembled and tested printed circuit board products.) They also offer a Loconet/LCC gateway. The TCS CS-105 DCC command station also uses LCC for peripherals and throttles, via CAN bus & WiFi. Their LT-50 handheld throttle/command station also has a CAN bus RJ-45 jack. Their UWT series WiFi throttles operate via WiThrottle or LCC protocols over WiFi.
The problem I have with wifi throttles is the PC requirement. If I'm going to run JMRI, then I'm going to use my phone for the throttle.
Love my... https://1fatgmc.com/RailRoad/DCC/page-3.html ... phone throttle above running EngineDriver but.......................... https://1fatgmc.com/RailRoad/DCC/WiTcontroller-Index.html ... now love the WiTcontroller throttle even more. The software for EngineDriver (if you have an Android phone) and the WiTcontroller throttle both come from Peter Akers. He is bringing more and more features to the WiTcontroller throttle almost every day. I've been helping on the testing end and designed one of the cases you can 3D print for the throttle but there are other case options also. There are still some features to the phone throttle that are nice and I'm not throwing mine away but basically all I'm using now is the WiTcontroller throttle. Battery last way longer, connects and is up in running in 30 seconds or less. Besides the physical throttle like the option of having other physical buttons like the 7 I have on my throttle (above) plus the keypad can be assigned functions also. It is up to you on which functions you want on the buttons or the keypad and for which keys. The throttle is easier to hold and I find it easier and more precise to operate a loco with. I added the physical throttle knob to the phone throttle (shown further above) but that also adds length to the throttle that is already larger than the WiTcontroller throttle. Still it comes down to personal preference. Sumner
Both Digitrax and NCE offer WiFi Wi-Throttle interfaces for phone apps or dedicated WiFi throttles, with no PC or JMRI required. They both use the same Wi-throttle protocol that JMRI uses. The CS-105 uses the LCC WiFi protocol for wireless throttles. There is an LCC WiFi throttle app available for I-phones, but not (yet) one for Android phones. Multiple Android LCC throttle apps are in development. The LCC WiFi throttle protocol handles multiple throttles controlling the same loco more gracefully than the Wi-Throttle protocol does. The CS-105 also directly supports wired NCE Cab Bus throttles and wired Lenz, Roco, & ZTC XpressNet throttles. NCE's Wi-throttle interface is actually a 3rd party product, but it is also sold by TCS, as an option to use Wi-Throttles or smartphone apps. RR-CirKits' LCC-Loconet Gateway can be used by the CS-105 to use Digitrax wired throttles and radio throttle systems, as well as any other Loconet accessories. Thus, a club could use a CS-105 system (with appropriate protocol adapters) to allow its members and guests to use their own WiFi, TCS, NCE, Digitrax, Lenz, Roco, ZTC and WiTcontroller throttles or smartphone throttle apps, seamlessly and simultaneously.
Again, thanks to all who replied/answered. My needs are simple, and at this stage of the game, I find that I am really looking for something simple that works out of the box, usable with the layouts I have already built and the locos I already have (or have modified) for DCC and sound. I am going to go with the Digitrax Zephyr Express, and possibly later add a DT throttle.
If you need to MU engines, I'd steer you away from Digitrax. It's harder to do vs. NCE or TCS. I have had a Digital system for years and found it not intuitive and would need a cheat sheet. I've decided to switch to TCS system
Thanks for the tip, James. It IS a small layout, and I don't really do much MUing. I have a pair of RDCs I run together (never apart), and a PA-1/ PB pair, also always run together. Here's a question... since each of those have their own decoders, should each unit of each pair get the same loco number? i.e. both RDCs with the same ID?
If you run a particular pair always together, e.g., an A and a B, then you can assign the second unit the same number as the first unit. This will save you a consisting step. I have used Digitrax for years and so do almost all N-Trak and T-Trak clubs. Consisting is not an issue once you know how it's done. A throttle with two controls, like a DT series makes it a no brainer.
Most cab diesels were consisted tail-tail so the crew could just swap cabs to run the other way (particularly on an out-and-back local freight run.) All they need is a passing siding to swap ends of the train, even with a caboose to swap too. Consisting is preferred over giving them all the same address, so you can make some of the maneuvers associated with making and breaking (and adding to/subtracting from) consists on the rails. These activities can be entertaining in their own right. Or not... A lot depends on the way your DCC system/throttle helps/hinders with consisting, or whether you use JMRI (even on the main).
