Problems with legacy controler

Still warranty...send it in. Either call or send one of those "Talk To Us" emails.

I agree, contact Lionel. I had an issue with mine, original from the Legacy Big Boy. No charge repair in January 2016, upgraded to the latest and greatest version AND they had it back to me in a week!

Thanks problem solved - off to Lionel next week and thanks to the Forum.  If I was not a member, might have never known.

If you are attempting to operate the tmcc engine in conventional mode, that may be the issue. The presence of a signal from the base will prevent the engine from going to conventional mode.

if these are two separate engines, another device is needed to control track power. The legacy base will not control track power as a stand-alone.

Did I miss something in your post? was it edited?

replacing the batteries is ok, the blinking light indicates the remote is communicating with the base.

Which power and control equipment do you have and how is it connected?

Ok, went back and checked out some previous posts.

First, I read that the batteries expired for the Legacy remote and that you resolved that. Next I read that you have a ZW-C and had issues with controlling one channel.

Did you resolve that?

I would suggest that you reset the ZW-C to non-command and then back to command mode to reprogram it. Use TR 1-4 for the channels.

Do you have the track wire from the Legacy base connected to the U terminal of the ZW-C? Try that, if it is not.

If you have done all of this and still have no joy, call Lionel to return the Legacy set for a check up.

yes I do have ZW-C and I am able to control voltage to track and therefore operate conventional. I set the handle for full 18 volts then I can bring track voltage via Legacy red knob and of course can control Legacy and TMCC. Everything worked fine for a year or so then I got the constant signal.  I replaced the legacy with  my old TNCC  and everything operated fine som problem must be in Legacy unit.

Ok, I have it now.  Switching out the unit for the cab1 definitely identifies the issue. You do know that you have to ship all of it to Lionel. Wall adapter, base, antenna, cab2, y-cable. They want to check all of it, so it doesn't have to come back again.

Good luck!

yeah, I still run a ZW-C, 4 bricks. I don't run anything conventional, I just set the handles and turn it on.

Has the chip in the ZW-C ever been replaced to run with Legacy?

Gweedo posted:

Has the chip in the ZW-C ever been replaced to run with Legacy?

I hope so.  They show unavailable.

MartyE posted:

Gweedo posted:

Has the chip in the ZW-C ever been replaced to run with Legacy?

I hope so.  They show unavailable.

O boy take cover incoming!

Never replaced chip.  Never heard about this but I ran it 2 years before this problem.

Art Lites posted:

Never replaced chip.  Never heard about this but I ran it 2 years before this problem.

With Legacy?  If it operated fine before with Legacy then that is probably not the issue.

The problem here doesn't really sound like the symptoms of the legacy / zw chip incompatibility.

The normal symptoms were random shutdowns of the entire system due to certain strings of legacy instructions being misinterpreted by the ZW-C as a "halt" command.

graz posted:

The problem here doesn't really sound like the symptoms of the legacy / zw chip incompatibility.

The normal symptoms were random shutdowns of the entire system due to certain strings of legacy instructions being misinterpreted by the ZW-C as a "halt" command.

 

Mine was to the point of I could even get the system to come on.  It would boot, the voltage could be dialed up and then poof.  Zero.  It seemed to manifest itself in different ways.  At first it was as you say be ok and run.  Towards the end before JonZ sent me a new chip it seemed more like I first described.  It was getting to the point I couldn't even get my layout to fully power.

It may not be the issue but worth putting out there.