LCS Won't Enter Engine Data When Running Over Sensor Track

Chuck, Try setting up a separate short length of track with the sensor track as a test. Connect up the Legacy base and track power as normal to this separate track. And run your loco over the track. See if it reads the engine data correctly now. If not delete the engine info from the Cab 2 and try again. 

Let me know how you get on.

Nick

I did disconnect all but the WiFi, SER2 and one sensor track and it still did not work. I tried bypassing the SER2 and still doesn't work. I still get the one blink of the WiFi PDI led when the engine went over the sensor, but nothing gets stored in the base.

Thanks for the interest...

Chuck, Do you have more than one sensor track? If so is it only one track or all the tracks that malfunction?

Did you try deleting the engine info and then running the engine in cab 1 mode over the track? Sometimes if the engine info was loaded via a module originally it can play up. And the fix is to delete the info and then run it over the track so the engine info loads via the IR sensor.

Nick

This happens over all the sensor tracks (I only tried two actually). I do delete the info in the base and then try to reload.

One thing I am wondering, at first I thought the WiFi module was needed for this feature. But now I am thinking all the program is in the base and all I need is a base and one sensor track. I have the WiFi module in series with the base and the first sensor track. I'll try removing it.

Yes, that's correct the info is stored in the NV RAM in the base. The WiFi unit should not effect it.

I had issues with my Base but I had trouble saving LCS changes to the Base as well. This turned out to be a subtle hardware error in the base according to Jon when I sent it in for repair.

Nick

What version is the base and cab?

It's Version 1.6 base and cab2.

I tried a number of connection configuration things without joy but it seems to work now. I say seems because clearing the engine data on LSU (I immediately see the CAB 2 display showing it cleared),  and trying to reload by running over a sensor track does not reload the data.

Again, if I clear with LSU, I do immediately get "CAB 1" (this is a new Legacy Berk) on the CAB 2 display. Then running over the sensor does not reload the info.

But, if I clear the info with the CAB 2 by "Info, scroll, clr, yes", the engine sounds the whistle and THEN running over the sensor restores the info data.

So...this all started with an engine (New 611) of a friend running on my layout this AM not loading info when it ran over the sensor track. He also had some issue trying to turn on and off the marker lights...couldn't. Our tests only tried to clear info from the LSU. We never tried clearing from the CAB 2.

I hope I made that clear. It would not restore info data unless I cleared info data with CAB 2 even though the CAB 2 display showed all the info data gone. My mistake seems to be thinking that clearing info from either one, the LSU or CAB 2 was the same. It's not. Should it be?

Whatever the 611's issue was is not known now since we never did a CAB 2 clear and thought it was the LCS at fault. I'm thinking the 611 was ok and the load data from a sensor feature might have been off on the LCS. And my turning it on with ACC 99, AUX 1, 4 revealed nothing since I never tested using the CAB 2 to clear what he punched in manually to test. Sort of weird...but I learned more about the system. Especially, that nothing is needed but a base and a sensor track. Don't know why I thought the WiFi had some function in this, but clearly see it doesn't.

Thanks for the interest and help. Very appreciated.

Nick12DMC posted:

Chuck, Do you have more than one sensor track? If so is it only one track or all the tracks that malfunction?

Did you try deleting the engine info and then running the engine in cab 1 mode over the track? Sometimes if the engine info was loaded via a module originally it can play up. And the fix is to delete the info and then run it over the track so the engine info loads via the IR sensor.

Nick

And this was a good tip since I thought clearing from LSU was the same as clearing from CAB 2...kind of gave me a thought along the way to try the CAB 2 clearing. Thanks.

I'm confused.  Is the data entering into the Cab2 when the engine runs over the sensor track but not the LSU?

MartyE posted:

I'm confused.  Is the data entering into the Cab2 when the engine runs over the sensor track but not the LSU?

No. The data didn't enter either the CAB 2 display or the LSU as long as I cleared data with the LSU. The LSU showed no engine for that ID # and the CAB 2 showed no info data when running over the sensor. It was only when I cleared the info with the CAB 2  that info appeared on the CAB 2 when running over the sensor. Then of course I had to close the LSU program, restart it, and reload the Engines from the base to see it there. This last bit didn't surprise me.

Ah gotcha. Too little sleep.