I was at the local LHS yesterday, and they had several Legacy sets in for a very reasonable(mail-order competetive) price.
Given that I’ve been planning on purchasing Legacy anyway, I couldn’t help but pick it up.
Anyway, I’ve a good little while since yesterday running one of my better TMCC engines, my K-line Club Trainmaster, with it.
Just a few minutes ago, I had a train pulled by it running at a fairly low speed. From across the room, I attempted to bring the train to a stop, and, much to my surpise, it wouldn’t stop. I walked closer to the base, and could see that the red light wasn’t blinking in response to commands. A few more button presses, and I had the dreaded “base not found” message on the LCD.
I powered down the remote and powered it back up-still the same thing. I then, with the remote sitting in the cradle of the base, told it to scan the channels-still no luck finding the base.
I know I’ve heard several stories about folks having to reload the software after things like this happened-will I need likely need to do this? Do you folks who are more experienced with Legacy have any other suggestions?
By the way, I’m really enjoying it so far, and can’t wait to actually get a Legacy engine.
You could this before reloading the base software. Power down the HH remove the batteries and unplug the base and let it sit for a little bit. Plug it back in, put the batteries back in and repower the remote. If that doesn’t work you’ll probably need to reload the base software. The “patch” will fix this when it comes out. Make sure you register your Legacy on the Lionel website.
This is very important and I probably don’t have to tell you but DON NOT power the layout until yopur base and HH are connected and talking. Several folks had issues when they repower multiple times causing the electronic e units to cycle without the Legacy watchdog signal. Of course 18 volts and off they go.
Oddly enough, however, the base never stopped transmitting. When the message first appeared, the train kept running as if nothing had happened-i.e. it didn’t sputter or stop as would normally happen if the signal dropped.
I power my layout with a PW ZW, and always ramp the power on and off so that I can keep any command control mishaps from happening. Before I powered down the base to reset it, I went ahead and powered up the track. The signal was still there.
In any case, thanks again. I’m thinking that I may pull out the Y cable and wire in the old CB so that I can still use the CAB-1 HALT button if this happens again.
Ben, mine did it the other day. First time in months. Only bad thing is you have to reload all those engines. Wish they had a way of recording engine data in a chip and then you could “mass reload” them. I think the bad RCC board on that upgrade screwed with mine. Oh well.
Chief,
There is supposed to be a ‘black’ user writable module coming out… when I have no idea… but would be cool if that is what it could be used for… to store all your layout info so if you have to reload everything it is a simple ‘load the black module’ and you are off and running.
I managed to avoid having to reload. For me at least, however, since I only have four TMCC engines and hadn’t yet named switches or routes, a reload wouldn’t have been a big deal.
In any case, though, I’m now noticing something else that may or may not be a problem.
When I first turn on the remote from being “cold”(i.e. off for a few minutes), I get lines all across the LCD screen. They seem to fade away within a few seconds.
Has anyone else noticed this happening with theirs?