Skip to main content

I installed 2 LCS sensor tracks on my layout and I am unable to get them to go into the record mode.  When I push the record button, the LED will flash anywhere from 3 to 11 times.  I do not receive the bell strike when engine passes over the sensor track.  Nothing is recorded.  Both sensor tracks behave the same way.

 

What does work: 

     -  Automatic cab up date information from engine passing over sensor track

     -  Fuel and Water levels appear on Cab 2

     -  Engine data appears on LCS/iPad app

     -  All 10 action commands work as expected

 

Configuration:

    -  Cab2 and Legacy Base v 1.53

    `  First device in Daisy chain - WiFi Module

    `  Second devise is SER 2 Module

    -  Third and Fourth devices are LCS Sensor Tracks

    -  Sensor Track IDs are 81 and 82

 

Sense neither sensor track works, it must be something that I have done wrong.

 

Thanks for the help

 

Don

 

Original Post

Replies sorted oldest to newest

Originally Posted by traindriver5261:

I installed 2 LCS sensor tracks on my layout and I am unable to get them to go into the record mode.  When I push the record button, the LED will flash anywhere from 3 to 11 times.  I do not receive the bell strike when engine passes over the sensor track.  Nothing is recorded.  Both sensor tracks behave the same way.

 

What does work: 

     -  Automatic cab up date information from engine passing over sensor track

     -  Fuel and Water levels appear on Cab 2

     -  Engine data appears on LCS/iPad app

     -  All 10 action commands work as expected

 

Configuration:

    -  Cab2 and Legacy Base v 1.53

    `  First device in Daisy chain - WiFi Module

    `  Second devise is SER 2 Module

    -  Third and Fourth devices are LCS Sensor Tracks

    -  Sensor Track IDs are 81 and 82

 

Sense neither sensor track works, it must be something that I have done wrong.

 

Thanks for the help

 

Don

 

Contact me off forum.  I can help.

jon

I had the same problem with it not recording.  I called Lionel and they sent a filter capacitor that plugs into the last sensor track on your layout.  They said it had something to do with noise in the system that needed to be filtered out.  Once I got it and plugged it in,  everything began to record like it should.  The capacitor they sent was free of charge.

Marty I have a question about this sensor track.  Why did Lionel limit the sensor track to around 250 commands vs the 1000 or so on the cab2?  When I try to do a passenger station stop, pickup sounds as well as using the MTH disappearing passengers station, the buffer becomes full and won’t allow me to proceed in record mode.  With this being the issue, do you have any ideas that would allow me to do a descent recording of a passenger stop, pickup and return before buffering out?

Thanks for any input

I can't answer why the sensor track was limited to the current 250 or so commands.  The best thing to maximize the use is to limit any whistle blowing or other non essential sound commands.  The only thing you can really do is eliminate or curtail unnecessary commands.   Maybe they'll do an upgrade for new sensor tracks to increase the record length.  I'd certainly be interested in that as well.

I would like to see that as well.  Do you think if I were to place a sensor way ahead of the station stop with approaching sounds and such and a sensor past the station with departing commands, would this would remedy the problem?  I guess what I’m saying is would the second sensor allow for a second set of commands to take over and cancel out the first sensor recording?

For all of you that want a higher recording command limit...

I am a Lionel LCS Partner selling my own software.  With my software you can record Scenarios up to 2,000 commands.  You can also record as many Scenarios as you want.

Please let me know if you have any questions.

Please click on the links in my signature below for more information.

Blake Morris posted:

I would like to see that as well.  Do you think if I were to place a sensor way ahead of the station stop with approaching sounds and such and a sensor past the station with departing commands, would this would remedy the problem?  I guess what I’m saying is would the second sensor allow for a second set of commands to take over and cancel out the first sensor recording?

It would definitely help.  The first ST would need to be able to at minimum have enough commands to get the locomotive rolling again so it can trigger the second track recording.

Thanks to Harvy for the follow up on eTrain as well.

BTW, I just installed a commander M in a K-line makado steamer.  It runs great however, I noticed that when the locomotive falls into a curve, it slows down a notch and then goes back to regular speed.  Before the upgrade, the Loco never did this.  Have you ever had anything like that happen to you?  Any idea on what it could be?  All the settings are by the book.

Blake Morris posted:

So I have to manually stop the recording of the first ST or second ST will be ignored is that correct?

Yes when making the 1st ST recording end it after the locomotive starts moving again out of the station provided that didn't use up all of the memory.  The 2nd ST will take over an "outbound" speed adjustments and signal sounding.  I hope that explains it.

Add Reply

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