Legacy diesel loses diesel sounds, crew talk, tower comms, after running in a lashup.

Try Pressing  the whistle/horn button one time followed by several pushes of # 1 on the keypad.

Tried that, no joy.

We have two locos without diesel sounds after a lashup was cleared.  Made multiple reset tries, still no diesel sounds.  In conventional mode, the sounds are generated, but are silent in command mode.

Are these the same engines at the show where you reported speed 0 issues? (https://ogrforum.com/...91#76748553621230691) I'm only half-serious, but was all your equipment subjected to some gigantic electro-magnetic pulse that has messed everything up?

Let's start with a couple questions.

When the engine is in command mode and exhibiting the problem, do you hear ANY of the following:
horn
bell
crewtalk
background diesel roar

When the engine is in CONVENTIONAL mode, pls confirm you hear ALL of the following:
horn
bell
crewtalk
background diesel roar

Old foggy head stuff before Legacy, when you un-did a consist, you had to assign the engine(s) to TR 0 (Train Zero) to restore all functions.  Still applies to all of us still using Cab1 remotes and the original command base(s).

TR 0, Eng (##), Set.  horn should sound.

Tracker John posted:

We are trying to figure out how to restore sounds to a Legacy diesel after clearing the loco from a lashup.  This has occurred on four locos at a recent show, and multiple resets of the locos have restored sounds on three of them.  An Alaska GP38 is resisting all attempts to restore sounds after multiple reset attempts.

The horn and bell work fine.  This is not an Alt1+1 issue to raise the volume.  Diesel sounds come on in conventional mode but not under command control, so this is some glitch in the Legacy logic.

Any suggestions?

John

 

did you try reprograming the engines?

happens to me and I just put engine in to set reprogram back to run and everything is fine.

6 dash number would help.

Thanks for that suggestion, BIGDODGETRAIN. That is an excellent idea, reprogramming the engine ID does much more than the numeric zero "reset."

Railsounds posted:

Thanks for that suggestion, BIGDODGETRAIN. That is an excellent idea, reprogramming the engine ID does much more than the numeric zero "reset."

So Rudy,    Now that you've brought it up what does reprogramming the engine do in addition to setting the engine number?

Thanks

It should restore everything to factory defaults.

Rudy, thanks for your suggestions on testing the sounds.  Yesterday, using the club's power cabinet running Legacy v1.60,  I tried resetting/reprogramming the engine with no joy on the sounds.  Our show layout was torn down today so the power cabinet used when the engines sounds vanished (and the set absolute speed 0 issue was observed) has gone to the next show venue. 

I set up a test bed at home using a 1033, Legacy base v1.52, WiFi, and SER2, and brought the engine in from the cold to test. 

Apparently, the process of packing the engine in the box, transporting it, letting it sit in a cold garage, and unpacking at home for testing has restored all sound functions.  I started testing in conventional mode - all sound functions worked.  Switched to command mode and all sound functions worked.

Could this be a Legacy Base failing issue?  The club's LCS WiFi and a Z4000 were replaced during the show, but the base is an early production unit and may need replacement.  I have seen other problems such as garbage characters in engine names that may be indicative of failing memory.

John