dcs legacy compatibility

It has been discussed often and even editorialized on by the main O-Gauge magazines, but there is no time in the foreseeable future that this will happen.

History of Command Control in O. Lionel released TMCC, published all the codes as open source and licensed TMCC to several other train manufacturers. A few years later MTH released DCS and declined to license it to anyone or publish the codes.

When Legacy was released the Legacy specific commands were not published. Although TMCC is still openly published, Lionel has kept Legacy specific commands to themselves.

DCS can control TMCC/ Legacy if you add a TMCC Command Base or a Lionel Legacy base to the system. Just remember you only get the TMCC functions, not the Legacy features.

DCS has some DCC features although I am not up on all of them. Also some people convert their ogauge engines to DCC, however I am unsure of the in's and outs. Also I was told that Lionel's American Flyer engines feature some DCC capability, however once again I am not familiar with them all

Dave Hikel is working on a iPhone DCS controller, so it appears that they might be modifying their stance on licensing DCS, or they just really needed an iPhone app.

Interesting..but still seems the issue is addressing the source....maybe a petition or a boycott..I am the type of person who takes action..but realize my acting alone is ineffective.. if we all stood together we could get these companies to meet a standard..or is what I am asking just to unrealistic..I do not think so, but I always reserve the possibility I am wrong..Usually I am not, because I rely on truth facts and logic as my only guides...DCC in HO has a standard..and it benefits the hobbyist..and the manufacturers..because I can use any decoder, controller or system and that allows me to spend my "train money" as I deem appropriate..with the knowledge that "plug and play" is the rule not the exception....I have MTH but am disheartened..when I bought my first Christmas set it was "Locosound" and I was told by the LHS that it would integrate with future products.. and that is just not the case..except in limited fashion or expensive upgrades..I think as a customer I should be able to get what I want..reasonably ....

Yes, it is. As cbojanower stated, there is no time in the foreseeable future this will happen.

Lionel and MTH now have way too much time and money invested in their own systems to toss them out and unite on one system or the other, and they're sure not going to spend any more starting all over to develop a joint system. Besides, if they changed control systems now, they would kill all the engines they've made for years, and it would kill their customer base as well.

K-Line, Weaver, Sunset/3rd Rail, Atlas O - all went with Lionel's system. But once Mikey decided he wasn't going to get on board with Lionel's system, that was the end of any hope for a united control system. It'll continue to be two separate worlds....MTH, and everyone else.

I don't think each company has to drop their own systems, but they should make them be able to talk to each other.  I am thinking of how DCS can control TMCC stuff now, but  you need either the legacy or TMCC command base too do so.  MTH should allow Legacy users to control DCS engines but by plugging in the TIU to the Legacy base.  

They need to work together to open up their code, or license it too each other so they can do that.  I would love to be able to control all my engines using my Cab2, or my DCS handheld.  

When I 1st got back into the hobby I planned to use only my DCS handheld to control all my TMCC and DCS engines, then a friend brought over his Legacy Berkshire and I had to get legacy.  Now I am back to using 2 handhelds because I can not get the legacy features on the DCS handheld.  

So it is possible to run 2 systems on the same track? or do you have to operate on blocks with "a toggle" between each system?  DCC is looking so much better

Yes it's possible, all you need is the MTH 50-1032 cable hooked up between the TIU and the Lionel Legacy Base and you're good to go.

Actually, the only reason you need that cable is to use the MTH remote to run TMCC locomotives.  If you just want to run TMCC/Legacy with their remote, and the DCS trains with the DCS remote, you don't need that cable.

That is 100% correct.

Individuals have to decide which way to go--if they wish to go with command control at all--on an individual basis based on their wants and needs.  Some go strictly DCS; some go Legacy; and some go with both (which is what I did).

The two systems do seem to play well together, and that was the most important consideration for me.

I like them both, they each have their strengths and weaknesses.  While I agree that it would be super keen to have a single control system, I'm a realist.  I know that ain't gonna' happen any time soon.

For a New Year's Eve display last year, I ran a TMCC train (K-Line EP-5 with Atlas coaches) and a DCS train (AEM-7 with Amfleets) on the same loop using the MTH controller and a TMCC command base connected to my TIU. Sometimes I ran one or the other, then I brought both out and ran one behind the other, only switching back and forth every so often to adjust their speeds.

Worked just fine that way. Adding the TMCC command base was just an extra $60 or so plus the MTH connector cable. I'm pretty certain I spent less than $80 total.

Once I even coupled up a Lionel TMCC (pre-cruise control) and an MTH DCS diesel and ran them double-headed. It was a bit of a juggling act for sure, but I pulled it off without losing any "magic smoke".

---PCJ