6 Months with Legacy Review

rdeal,

   If you are running FasTrack switches of any type and only have DCS, you must wire the Switches thru the AIU to be programed and run via the DCS hand held remote control.

IMO the best way to run FasTrack Command Control switches is with either the Legacy Cab 2 or the TMCC Cab1, set up correctly, using Blocked Track Power, you can run 99 switches. For years I used the DCS AIU, until the development of the wireless FasTrack Command Control switches.  

PCRR/Dave

I don't know what the process is to  "name" engines with DCS, but I think it is inconvenient to do so with the CAB-2.  That is why I use Lionel's LSU program to name my engines, switches, routes, etc. it is MUCH EASIER than scrolling through the alphabet with the red dial!

 

This is an interesting and informative thread.  I definitely see the advantages of a two-way system of communication.  I suppose Lionel's sensor track is the work-around for this, but it is not as efficient as MTH's design. 

Gentlemen,

   Owning and running both systems is the advantage!

PCRR/Dave

 

I have to say that I agree with Chris regarding the Legacy remote. When it was first announced years ago, I thought that it was overly gadgety and looked poorly designed with all of the odd buttons and sliders. I had to eat my words as the functional ergonomics of the remote really seem to work.

While I like app options, the lack of dedicated buttons that you can "feel without looking" is tougher to use as my regular, everyday remote.

 

The ones posting here that have both seem to also have the best answers. I only have one system but have watched many times as club members with the other system have tried to get their engines to run. That's not fiction, it's fact. Nobody's gonna win this race.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

I'm relatively new to the Command world, but I love it. 

 

I bought a Legacy system last year and was blown away.  Never ran a DCS system but I will buy one as my MTH roster increases.  

 

I'm sure I'll enjoy both systems.

 It was only a matter of time

 

 

You're so right, Scrappy!!  And I'm sooooo mad at myself for falling into the trap!!  There are a few select topics that I know better than to give an opinion on...and this was one of them.  I'm taking a seat on the bench and going back into my more typical "read-only" mode for the duration of this one.  Thanks for waking me up...I really do appreciate it!!

 

And to the OP, Peter (PJB), I apologize for my role in taking your thread off on a tangent.  As a fellow owner/user of both Command systems, I really appreciated reading your thoughts and comparison.  Happy Railroading!

Exactly. Anyone can have problems with either system on any given day. This is a fact. I am lucky, I have both DCS and Legacy and don't have any operational problems with either system. Legacy has been back for repair however, the base would not take the 1.53 update, the Lionel service tech at my LHS could not fix it either, Lionel had to fix it. I never had problems operating trains with it, just the update problem. I am glad it is back.

 

I agree with all the others that like them both. Each has some neat features, which others have already described. Probably an odd point of view here, but I actually like having the two systems. I also like both remotes, also each having a unique feel and features. It all adds to the variety. As with some of the others here, I like both systems equally well and would not want to have to give up either system. I would actually like to add DCC to the mix someday as well.

 

As for the upgraded remotes, I think those are already in the works, they will be iphones and ipads. I think this will apply to both the Legacy and DCS systems. I don't have an iphone, but I do have an ipad. I have not tried any of the new apps, but I have a feeling I will still prefer the conventional remotes. I will have to try the apps before deciding for sure and I am trying to view it with an open mind and not decide before giving the new apps a chance. I do think my grand kids will prefer the iphones and ipads as that's what they have been growing up with and are used to. Overall it may be good for the hobby. Time will tell on this one, then we can have the 'who's got the better app' battles discussions.  

 

I have TMCC and DCS, maybe when I acquire more Legacy locos ( currently 3 ) I will add Legacy. I don't know much about Legacy CC, I do operate my Legacy locos with DCS, can I run my PS-2 / 3 locos with Legacy ?

 

   Bill T

Not in command mode, only in conventional with a powermaster or other variable output device Lionel might have.

JoeyA and RD - guys!  This isn't supposed to be a brand X versus brand Y thread, and I cringed at it being described that way.  It is an update thread on my own experience with Legacy. I think other people relatively new to the hobby might find value in this sort of thread. And then I responded to a query regarding MTH DCS - and said right in that response that I feared it might get us off track.  Can we please keep things productive? 

In terms of DCS - I have to agree that I've gotten more than a handful of erratic fault messages. And I do find it to be more temperamental than Legacy, but so what?  Not going to villainize it because it isn't perfect. It has very many amazing features too - some of which I mentioned earlier. And it's true that DCS does recognize and load engines without having to plug in name. That's part of the beauty of the two-way communication.  That's not a knock on Legacy; it's a statement about DCS.  Similarly,  some see the Legacy modules as a deficit, but again, no system is perfect, and this "deficit" is far from a deal breaker by any measure. I happen to think the Legacy modules are pretty cool (an example of my delight was the roar when programming in the VL Challenger).

Frankly, I sort of thought RD was trying to be sarcastically funny. And JoeyA did raise some valid points too.  Can I ask for your cooperation in us all taking it down a notch and getting this thread back on track please?

Thanks

Peter

Yes!  Not sure if you saw my reply to Scrapiron's post earlier today, but this is what I said to you...

We are on the same page.  As stated earlier, I will certainly continue to read this thread.  There's a lot of good stuff here!  Thanks again for starting it.

thanks for all the information -

 

but if a person chooses "X" or "Y" - and uses only one brand

 

is this choice going to work

 

rdeal

 

Done Peter,

I have removed my contributions to the derailing of your thread... unfortunately I can't erase what others have quoted in their posts.

 

You were half right as to my intentions.. just trying to point out you can say good things about one without having to say bad things about the other.

If I understand your question, as long as you use "X" products with "X" systems (same for "Y") you should have no problems. Mixing the "X" & "Y" products between "X" & "Y" systems is where you have the potential for problems or at minimum don't get to use ALL the features available in both systems.

 

I would recommend using "X" products with the "X"  system and same for "Y" to get optimum results from either system. I have both systems and use the respective products with their own specific control system.