I have 2 Lionel Legacy SD40 engines lashed up. Everything was fine until today. When I hit crew talk or the horn, I get sound from both engines. I have tried reprograming, but still have the problem. Any suggestions? Thanks
Replies sorted oldest to newest
when building the lash up look for an icon that adds sound and horn. don't add sound. did you recently update to version 1.52?
I have version 1.51 which I thought was the latest version. I turned off the sound and horn on the lead unit but the trailing unit still has crew talk and horn on. The lead unit has no sound. I could make the trail unit the lead, but that is not solving the problem. Could it be a computer chip problem?
fixed the post 1.52 is latest but 1.51 is almost the same.
when you turned off the lead loco that is why you have the second loco with sound and horn. each loco has to be programed individually in the lash up. look closely when creating the lash up.
One of the new features was sound masking, look at the icons above each engine and you can assign engines to play some or all their sounds. It's in the manual for the latest manual. You may want to double check all the settings
Sound masking will only work with newer models, most of the older stuff won't have that capability.
Well he didn't say when the SD-40's were built. I think its many engines in the last 2-3 years
I have 2 Lionel Legacy SD40 engines lashed up. Everything was fine until today. When I hit crew talk or the horn, I get sound from both engines. I have tried reprograming, but still have the problem. Any suggestions? Thanks
I actually like the dual horns, but clearly not the crew talk.
I've discovered a work-around, because I ran across the same thing. I program the crew talk to come from the trailing locomotive, and then the lead locomotive shuts up. This is apparently a bug in the MU code.
The SD40's are from the latest catalog. I am wondering if there is a bug in the programming
Did some testing. Trail unit always has crew talk. When icons are off, lead unit does not have crew talk. I switched the lead units and it is not an individual engine problem. I also have the latest GP35's lashed up in their own train. No problems with the icons and everything works great. Does anyone have the the latest SD40's lashed up.? I will have to call Lionel today. Interested in knowing if anyone else has this same problem before I call.
Like I said, I see the identical issue with several different pairs of Legacy locomotives, the only way I got them to be reasonable was to move the crew talk to the trailing locomotive.
It may be worth dropping a note to Jon, he might know of a fix or at least like to be made aware of the bug so they can fix it in future releases.
Or when we begin to ask for questions for the Legacy meeting at York, this may be a good one to detail and ask about
I called Lionel and they suggested reprogramming. Tried that, --did not work. I will call them back
Problem Solved. I called Lionel. After going thru the entire process again with no success, they suggested numbering my lash up as 7 and not 76. (76 is the first 2 digits in the road number) Called it train 7 and everything works fine. They said that sometimes a double digit will cause problems. Oh well, it works. Thanks for all the input on this thread.
Interesting bug
This would be a good question for the LUG meeting at York. Please submit it
As a test, and if you feel like proving the bug, if you use a different 2 digit engine ID (say 33, but never 99) ) does the bug follow you ?
in a train (TR) I have never had an issue using 99.
I think this is a known issue. If the rear loco is *reversed*, and if the TR# is 2 digit; the sound masking is not working on the rear loco on some production locos. This has been fixed in current production (~ 6 months ago), but there are locos in the field with the issue.
The fix is to use a single digit TR#; as CS advised.
Jon, thanks for the info
Thanks for the info Jon, I'll try that with my problem MU configurations.
Interesting bug
This would be a good question for the LUG meeting at York. Please submit it
As a test, and if you feel like proving the bug, if you use a different 2 digit engine ID (say 33, but never 99) ) does the bug follow you ?
I will have to try that sometime. I will post the results.