My sensor track doesn't always register an engine going over it, especially my SW switchers, it gets them in reverse but not forward.  Sometimes an engine goes multiple loops without if registering.  And sometimes going slow over it,  it will trigger.

Have you tried the LCS bus terminator.  Maybe that's what you need.

John, I’ll try it. Where would I get one?

Just to refresh: this saga started when for no apparent reason the Sensor Tracks started recognizing Legacy engines 'hit or miss' then just stopped recognizing IR sensor equipped engines altogether. All other functions worked and still do.

Update:  I decided to contact Lionel.  When I described all the steps I took to identify the problem, they suspected it was an  issue with the serial signal. I sent the Legacy Base to them and here's what the tech said:  "Changed out the DB9 and tested. It recognize the train. Thanks" I reconnected the fixed Legacy Base.  However, the Sensor Tracks still do not recognize IR sensor equipped engines. I downloaded the Legacy Base software update fresh and reinstalled it into the Legacy Base just to be sure the software was not corrupted. That didn't make a difference. I replaced the PDI cable connecting the 1st Sensor Track with a new one. No joy.  I connected the PDI cable from the LCS DB-9 Cable with Power Supply, directly to the 1st Sensor Track in the daisy chain. (It had been connected from the last component in the LCS module chain:  (BPC2). No joy.  The only component that has not been changed is the original DB-9 cable with LCS power supply. I bought it new 10 years ago. I found a new one and it's on order. I'm going to make the 'bus terminator' gunrunnerjohn suggests as well.

I have noticed the Yellow Light on the Legacy Base blinks constantly...not sure if that's an indication of a problem.  All the manual says its for feedback for special functions of the base.  ????

I can't think of any other component in the LCS Sensor Track system to replace.  As before, any suggestions welcome.

@ToledoEd posted:

I have noticed the Yellow Light on the Legacy Base blinks constantly...not sure if that's an indication of a problem.  All the manual says its for feedback for special functions of the base.  ????

The yellow light on my Legacy base blinks constantly as well, and my stuff is working fine.

As long as a serial or LCS device is hooked up to the Legacy Base the Yellow LED will blink.

This may sound silly, but make sure the sensors on the track are clean. I've seen before where dust or other residue on the LED can block the IR transmission.

I read somewhere putting white electrical tape on the bottom of your locomotives and rolling stock where they roll over the sensors can help them be detected by the sensors.

@Gary P posted:

I read somewhere putting white electrical tape on the bottom of your locomotives and rolling stock where they roll over the sensors can help them be detected by the sensors.

Different sensor. You are talking about a plain "is something there" retro-reflective sensor.

That uses an IR transmitter facing up, reflecting off the rolling stock or engine, then being received by the optical detector (photodiode or phototransistor)

The Lionel LCS sensor is looking for a pulsed IR transmitter on the engine facing downward sending data in the format expected.

White tape isn't going to do (a productive thing) for a Lionel LCS sensor track.     Replace between the ( ) with your favorite saying.

@Dave Olson posted:

This may sound silly, but make sure the sensors on the track are clean. I've seen before where dust or other residue on the LED can block the IR transmission.

Thanks Dave. I'll clean them...but all four, at the same time, even the brand spanking new one???  But, I hope you're right.  I take it you don't think it's the actual DB-9 cable? 

@gunrunnerjohn posted:

The yellow light on my Legacy base blinks constantly as well, and my stuff is working fine.

Thanks John. I never paid attention to it in the past, only now with this gremlin.  Good to know the blinking is not a result of some problem.

@Gary P posted:

I read somewhere putting white electrical tape on the bottom of your locomotives and rolling stock where they roll over the sensors can help them be detected by the sensors.

Gary, I had a Z-stuff trolley set up and placing a strip of white on the bottom of the trolley helped in that case.

@Dave Olson posted:

This may sound silly, but make sure the sensors on the track are clean. I've seen before where dust or other residue on the LED can block the IR transmission.

Dave, I brushed the sensors, used compressed air and a Q-tip.  Just before I ran the engine over the track I said a little prayer....NADA.

@Vernon Barry posted:

Different sensor. You are talking about a plain "is something there" retro-reflective sensor.

That uses an IR transmitter facing up, reflecting off the rolling stock or engine, then being received by the optical detector (photodiode or phototransistor)

The Lionel LCS sensor is looking for a pulsed IR transmitter on the engine facing downward sending data in the format expected.

White tape isn't going to do (a productive thing) for a Lionel LCS sensor track.     Replace between the ( ) with your favorite saying.

(Thank you for letting me know that the Lionel LCS Sensor works different!)☝️(It's a good day when I get to wake up, even better when I learn something new!)😁

Well, after all the steps I've taken, to include Lionel customer service replacing the DB-9 in the Legacy Base,  it still does not work.  So, as a last ditch effort, I just installed a new (6-81499) LCS 10' DB9 (LEGACY Base) to PDI Cable with 12V Power Supply. It was the only link in the circuit not replaced. The Sensor Track still does not recognize my engines. I can ping them, they still respond (The HI-Rail App makes it easy) but they do not respond when a Legacy engine runs over them.  I tried 3 different engines. I'm at a loss and other than Dave O. in this thread suggesting I clean the sensors (which I have done) Lionel has not responded to my latest plea for help. All other accessories controlled with the LCS system work: Gantry Crane, Log Loader, both use the SER2 interface, and all the accessories (ASC2) and track blocks controlled by a BPC2. So despite Lionel's action:  "Changed out the DB9 and tested. It recognize the train. Thanks" I'm out of ideas.  I do have spiffy clean sensor tracks!    Oh, if Lionel has no other ideas, I'm holding out hope that the new Base3 will fix this....

John suggested the jumper higher up on this thread. You can get it here.

It installs in the last open PDI slot in the system. It can take out noise in some systems that prevent the SensorTracks from working.

Q: Does the green light on the SensorTrack come on when an engine passes over it?

@Dave Olson posted:

John suggested the jumper higher up on this thread. You can get it here.

It installs in the last open PDI slot in the system. It can take out noise in some systems that prevent the SensorTracks from working.

Q: Does the green light on the SensorTrack come on when an engine passes over it?

Dave, thanks for the reference where to get the jumper and 'no' the green light does not come on except when the layout is first powered up and when I run the "identity check."

Okay. Can you email me? There are more things we can do to help diagnose it.

OK, I did email you. thanks.

@gunrunnerjohn posted:

Have you tried the LCS bus terminator.  Maybe that's what you need.

John, Dave Olson suggested the same and I bought one from Lionel. I installed it and the SensorTracks still do not respond. Fortunately, Dave has asked that I send in my Base2, cable, and a sensor track for testing. I hope he can figure out what's wrong.  Thanks.

Ed

Here's the latest. I have been exchanging emails with Dave Olson, who by the way, has been very helpful.  (He responded directly to me after I posted my problem in this forum.  Impressive.)   After a few attempts trying to diagnose the problem he asked that I send in all my LCS modules.  Well, after extensive testing, etc., they could not find anything wrong.

I want to commend him and his folks for their efforts on my behalf. Lionel's Customer Service in this case, went  well 'above and beyond.' 

HAPPY ENDING!   (As Reacher often says, "In investigations, details matter!") 

Well, once Lionel returned the modules, it gave me the incentive to tackle my wiring, etc. around power and the LCS modules. I hooked everything back up and for the first few loops around the layout...the sensortracks worked, but the same issue returned. Then I realized I overlooked a 'detail.' The one component I ignored throughout this episode was a TMCC signal booster I had installed a few years back. I disconnected it, and like magic, the  sensortracks worked flawlessly.  I contacted Gunrunner about this issue with the DM TMCC Booster and here's what he advised:

@ToledoEd posted:

HAPPY ENDING!   (As Reacher often says, "In investigations, details matter!")

Well, once Lionel returned the modules, it gave me the incentive to tackle my wiring, etc. around power and the LCS modules. I hooked everything back up and for the first few loops around the layout...the sensortracks worked, but the same issue returned. Then I realized I overlooked a 'detail.' The one component I ignored throughout this episode was a TMCC signal booster I had installed a few years back. I disconnected it, and like magic, the  sensortracks worked flawlessly.  I contacted Gunrunner about this issue with the DM TMCC Booster and here's what he advised:

"This is a known issue and why the amplitude adjustment mod was added.  Jon Z. told me that too much TMCC signal could affect the sensor tracks, so now you can tune it.  Too much signal can also cause issues with the DCS signal on the track.  The trick is to turn the amplitude down a bit and test, you'll get to a point where everything works as a rule."

As he advised I turned down the amplitude until the sensortracks triggered. That did it.

I put Dave and his engineers through a whole lot effort for a mistake I made in not mentioning the DM TMCC Bosster when I started my exchanges with them.  My apologies, guys.

                                                                               👍

@ToledoEd posted:

HAPPY ENDING!   (As Reacher often says, "In investigations, details matter!")

Thanks for letting us know the solution.  Too many times we never do hear the outcome of a problem good or bad.

Marty, you're welcome. I agree and try to close out my "problems" no matter the final outcome...