@T Ansley posted:"......Another Note: You don't need to use NCE. I've also built an Aurdino-based command station, with a Raspberry Pi 4 mini computer using JMRI software, with my phone and tablet as throttles. It's called DCC++ EX, you can find it on the web. Very inexpensive and works well, I just used my Booster to run my G scale trains with it. Heck, I used a base Bachamm DCC system I got for $100 back about 10 years ago with my MRC booster, and then Bachmann Booster to run G scale trains too. Just pick which system you like and you can get cheap. Right now, IMHO, one of the best out-of-the-box systems with 7 Amp booster built-in is the ESU 50210 CabControl Wireless DCC System with 7Amp booster variable voltage 15-21v. It is PERFECT for O scale DCC MTH based layout, and runs about $375 total. Let me know if you have any questions or need more info on anything.
I know I'm replying to my own post, I'd like to add some info. First, I stick with NCE, even though I REALLY like some of the new systems like the ESU one I mentioned because.... the NCE Mini-Panel! That thing is like magic, seriously, if you want DCC train automation it is cheap and works well! Take a look at all of James Ingram's videos and drawings on AutoControls.org. Also, look across scales at his videos, pretty much every video and setup he does can be adapted to another scale. I used one of his N scale 2 and 3 train DCC videos and code in my mini-panel for my G scale engines. I was looking for a way to automate running 2 G scale DCC engines around my modular layout without having to constantly monitor them. I found with one reed switch, I use an LGB track contact but any reed switch works, and will work in O scale too, I can run 2 trains safely around the layout. I programmed the mini-panel so that I push a button and one train starts, then when it crosses the reed switch it slows down, blows its horn and starts and speeds up the 2nd loco. Then it continues when the 2nd loco hits the reed switch, it blows its horn, slows down and then speeds up the 1st loco. Then it repeats, simple, but very effective and keeps the trains spaced regardless of what brand loco and DCC decoder you use. You can also do it with 3 locos if the layout is larger. Yes, it requires some tweaking for each loco you run but it works. There are many things you can do with mini-panel, throw turnouts, run 3+ trains from sidings. Pretty much whatever you can fit in the code in 130 steps. It's essentially an extra Cab on the NCE bus that sends DCC commands according to your code. You can have plenty of track sensors, use accessories and switches, and send any commands to the locos you would send form a normal CAB. Yes, there's a learning curve if you have no experience with step-driven commands with logic (sort of like programming light). However, it really is amazing what you can do with very little hardware and programming. I just purchased my 4th O scale MTH Rail King engine with Proto-Sound 3. I plan on fully automating 3 engines running on a simple loop with a siding. It will be cool, I've already been doing this in G scale for years. I can post wiring examples, or anything else if anyone needs help, or how to build this stuff if James' site is confusing to anyone. However, the original point is that MTH Proto 3 engines are god send to anyone in any other scales that uses DCC, you can simply use the system you already own, and a booster if needed.
What i don't understand is why other DCC manufacturers haven't added a small mini computer option to their DCC lineup so you can connect and automate sending commands?
I have another tidbit of info that might blow your mind. You can actually hook the same DCC system to two different scale layouts at the same time! When I setup an Xmas layout about 10 years ago I had a multi scale layout, the innermost loop of track was N scale, then I had a loop of HO, loop of O and two loops of G. The N scale loop, HO loop, and outer G loop all ran DCC trains. I used my NCE PowerCab with Bachmann Booster (at 16V to the track) connected to all 3 loops. I ran 1 DCC engine on each loop, N, HO and G with different DCC addresses at the same time. Worked like a charm. So, in theory I could have two big layouts right next to each other, any scale really, with proper boosters. (with proper grounding, and remember each booster can have different Amps and voltage), I could run both layouts with the same DCC command station! To make it easier, use one throttle for the 1st scale and the 2nd throttle for the other scale, or just add more throttles if needed! This could easily be accomplished wtih NCE or an Aurdino Based DCC+ EX system w/JMRI computer using phones/tablets as throttles, with multiple power districts.
One last thing. When I wire my layouts, I had one temp layout with about 7 blocked sections for standard non-DCC wiring, I double block all the sections with DPDT switches, then I can turn on/off completely both rails for any section of the layout, That way I can have DCC on one side of the DPDT switches and standard Analog on the other and can run either Analog or DCC on any given block at the same time on the layout, usually loops of tracks, or sidings. This is also a good way to run standard Lioncheif locos and regular O-scale analog on the same layout. Most people don't have a good understanding of blocking, and when and why you block 1 rail or 2. Many do understand and do the same, but I've noticed in forums this is complicated for many people. But, this is a good way to run DCC and Analog on the same layout too. When i take my modular layout to train shows, I typically run DCC on the outer loop and 3 Analog trains on the inner loop, but I can run either. Wiring is my strength, scenery not so much! :-)
