Hi guys, Found this board and the DCC++ stuff in my search for some Arduino based control of my (planned) layout. Already have done some experiments which are looking very promising. As always, a couple of questions: 1. does the WiFI board currently only work with the Mega? I've seen some contradicting comments here and there which make me doubt. Fact is that the EX installer won't work if you select Uno and subsequently click the WiFi box. A manual install on my Uno didn't work either. 2. If I take one of the recommended Motorshields then current is more or less limited to 2 Amps. Fine for a couple of loco's but in case of more loco's more then 2 Amps is a must. This could be achieved through a different brand Motorshield (e.g. the 43 amps one) but in case of a derailment the loco will be welded to the tracks. Another approach could be to have the lay-out broken down into segments where each segment has it's own Command Station. Segments are obviously carefully electrically isolated from each other and only if a loco drives from one segment into the next there is a momentary shortcut (which is not an issue with the commercially available boosters). However, how can I have multiple Command Stations all communicating with the PC running JMRI (or in my case its equivalent DDW)? Anyone any thoughts here? Thanks in advance, Martin
Hi Martin, welcome to the group. I'm sure the DCC++ guru's will be able to answer your questions properly. 1. I think the Wifi exceeds the memory capacity of the Uno, hence why its recommended to use a mega. I'm sure there is a thread about that on here somewhere - if you do a search you should find something. 2. Multiple command stations - I'm pretty sure you can add multiple command stations within JMRI (I run several separate CMRI connections) but I don't know if they would all synchronise together or act independently, so setting the throttle on one DCC++ connection would not transfer to the other DCC++ connection and your loco would stall on the junction - until you set the throttle on the next one. I'm guessing boosters would be the better option as then they are all connected.
Knew I had read it somewhere. I have an uno with built in Wifi and wondered if it would work -- it didn't.
That is my plan. I've bought the parts but haven't put them to use yet. Have DCC++EX up and running on an Uno (actually 2 but the second is just a spare) and a short test track. I bought 1 Tam Valley booster ($43) and 2 Tam Valley Circuit Breakers ($25 each). I'll be a single user so the 3 amp booster ( 5 Amps for short periods, 3 Amps continuous) will probably be plenty for me but could always add more. The 2 circuit breakers are so I can have 2 power districts (could add more) and they will connect to the booster. Now the Uno won't be supply any track power only sending the DCC signal to the booster. If you wanted to build a booster (I bought the parts) maybe see how you feel about Dave's booster... http://www.trainelectronics.com/DCC_Arduino/DCC_Booster/ Sumner
So it means the "Main Track" output from the motorshield goes to the DCC In of the Tam Valley booster? And the "Programming Track" from the motorshield remains for the programming track on the layout Is this correct?
I have not wired mine yet but yes I would say that is correct. I'll have the programming track wired with a DPDT switch to that it can be powered by either the Arduino/Shield or the Booster as it will be part of the layout.......... If the program track wasn't connected as one of the layout's tracks it would only be connected to the Arduino/Shield, Sumner
Yes, you would Wire the B cab from the Arduino Motor Shield to the insulated Programming Track and the A cab wires from the Arduino Motor Shield to a IBT2 or other Booster for the Main line tracks making sure you have adequate circuit and and over amp fuse protection in place on the main. I would also recommend a Center Off DPDT Switch as a good precautionary item for this Hardware implementation version. But what comes next? We are currently testing in a next General release version of DCC++EX a New software implementation version of a DPDT switch that's dubbed 'Drive Away' It will allow you to place a DCC Engine on the insulated PROG track but part of the main layout as a spur while the Program track is Active. DCC++EX will notice the Engine, search and read the CV1 Short and CV 17 & 18 Long addresses, load the Loco# and allow the Command Station to automatically send the <1 JOIN> command to switch the PROG track to MAIN and allow you to use a Engine Driver Throttle and drive it away. If you inadvertently touch or send any Programming command while it is sitting on the PROG track while it's active as a [JOIN] Main line track, the software Automatically kicks back to Program Track Mode before accepting any other commands as safety procedure. Kind of a cool idea and keeps making DCC++EX even more fun! Our Greatful Thanks to Chris, Harold, Steve & Fred and the rest of the DCC++EX Team!
