Skip to main content

So I was having a Legacy base issue over the summer.  When using the remote, the legacy base, would light up the middle yellow light and start sending commands on its own.  Engines would take off and go nuts.  I sent it to Lionel for repairs and they replaced the pcb for the serial port.  I get it back, and the problem starts again.  After some conversations with Lionel, I disconnected all serial devices but left the Y cable plugged in.  Base went nuts.  Disconnected the cable and the base resumed normal operation.  I then plugged in one of my serial devices directly into the legacy base (Accessory voltage controller) and all was still good.  Turns out I had two problems.  The pcb in the legacy base AND the Legacy Y cable.  Lionel sent me out a new Y cable and now I have all my devices connected again.

I never would have suspected the cable to go bad but it did.  New cable seems to be working fine.  Who would have guessed that one!

Great job to Lionel for figuring out the cable was also an issue.

Original Post

Replies sorted oldest to newest

Yeah, I would agree.  My base is pretty old, as it came with version 1.2.  I bought it years ago.  Once I plugged the Y cable in, it never gets touched or moved.  How it went bad is beyond me.  There are no frayed wires or bent pins.  All I know is when that cable is connected, the base goes nuts.  The yellow comes on when I send a command and it floods the track with signals to the last engine I talked to, making it go crazy.  Put the new cable in, and all is normal.

The base would go nuts when the cable was plugged into the serial port. I had nothing connected to the cable. Unplug the cable and the base would stop acting up.

Normally I use the cable to connect my tmcc command base, zstuff data driver, and accessory voltage controller.  when testing with Lionel, they asked me to plug the cable in but leave off all devices.  They were assuming a device was causing the problem and then I would connect one device at a time. I never got that far since the cable duplicated the problem.

Last edited by Joe Fermani

Add Reply

Post
×
×
×
×
Link copied to your clipboard.
×
×