Engine Sounds Only During Shutdown

I'd consider reloading the chain and sound files and see if that's the problem.

Many thanks. Interestingly, I put the engine on a isolated track and all of a sudden I was back in business! Every once in a while, an engine either fails to be recognized or I lose features. I typically reset the engine or remove it completely and re-add it.  I’m going to look into your recommendation for sure.

If it works on the separate track, then I doubt you need to reload the files.  Sounds like an issue with the layout DCS signals.

Thanks for that. I will check the signal strength and look for potential conflicts.

Do you have other DCS engines? Do they always work ok? Asking because we have a steam engine that suddenly has no sound after sitting for months on a shelf.

I am not sure how the engine defaults to ID #1 on its own.  That is odd, so even if it runs on the new section, I would do a reload of the sound file.  I would also listen to the shutdown by turning track power off.  Does it play or abrubtly stop sounds.  That could be a bad super cap, or solder joint.

When I see this it is usually because the engine was in  a lashup or features turned off by owner. I always start troubleshooting in conventional, and a conventional rest always brings back all the features.  So maybe a lashup been programmed in.   G

@howardih posted:

         I did both a features reset and a full engine reset. I also have tried multiple times to turn engine sound on and off. I even deleted and then re-added the engine to DCS which seems to work fine but I get the same problem. Adding the  engine defaults to address #1 but I've renumbered the engine as #6. Has anyone seen anything like this?

When doing a DCS full engine reset, it will delete the engine address. When adding the engine back into the system, it will add to the lowest available address. It is best to have only one engine on the track where adding the engine. Apparently address #1 was open. 

I am interested in seeing what is causing the problem with the engine sounds.

Yes, address #1 was open. Long story short, I have somekind fo quirkiness where address #1 and address #5 deem to create conflicts. It seems to have some bizarre origin in RK R-12 PS3.0 subway set that "likes" being address #5. I immediately rename number the adddress #1 to something else whenever a new engine is added. The engine in question may have indeed been part of a lashup, but it did appear as an engine in its own right with a good address position during startup. And the horn, bell, and shutdown sound worked fine. I don't think we should underestimate the importance of adding new engines on a track that is not occupied by other engines. While most of the time I have no issues, there is a PS3.0 engine that, from time-to-time, will only be recognized when it stands alone. I even have a couple of engines (a RK S2 6-8-6 and a RK M1a steamer) that randomly have to be deleted and readded because they aren't seeing the watchdog signal (and you can't hear a click anyway because they are PS3.0). And my layout is all "9s or 10s" when it comes to DCS strength. Admittedly, I think it's time for PS3 to undergo an update; it surely is more sensitive than PS2.

If the engine does not see the watch dog it would start up in conventional.  You than just address it and hit start up.  At that point you should have control of it and you can do a shutdown.  No need to delete and readd it.

If you have a large volume of engines and such in your remote along with several TIU you can start to run into issues with association depending on how you set the TIUs up.

I may have misinterpreted your first post.  But you can go into the volume setting and see if certain sounds have been lowered.  Though a feature or factory reset should have taken care of it.  I am baffled if an engine keep going back to setting that you have not initiated just based on run time and or idle time.  G

Thanks. I did  ot realize that an engine starting up in conventional can be acquired thgat way. Always something new to learn!

I find that many times an engine that starts up in conventional must be shutdown and restarted in command before you have full control.  Specifically, many times you can get horn/bell control, but no motion control unless you go through a shutdown/startup sequence.