Skip to main content

I have a Santa Fe Premier Dash 9 (20-20119-1) that was part of a dual-engine (lashup) set, and ran great. It was the trailing engine, and when going on reverse, its lights lit up just fine.

I decided to run this fine engine by itself, but the engine could not be found. After several tries with no luck, I decided to delete it and add it back (no more lashup). Now, it starts and runs fine, but other than the engine sound, there is no whistle, no bell, etc. It will not respond to volume changes, and all the lights are off.

I tried a feature rest, but that did no good, so I did a factory reset and added the engine back to the roster. Still, no lights, no sounds on demand. I ran the INFO, and it read: TRIP 0.1, ODOM 128.4, BATTERY LOW, CHRONO 83:53

But PS3 engines have no battery, so I do not know what the Battery Low means, nor what to do to make the sounds and lights functional.

Help, please?

Thanks

Alex

Original Post

Replies sorted oldest to newest

Greg,

Yes, that was it! All the sound volumes were turned down to 0%, and the lights off - no wonder. IIRC, when I did a Feature Reset on PS2 engines, the volumes were not turned down to 0%; as a matter of fact, I believe they were at 100%, the lights were on, and the smoke came on.

Barry - I guess MTH did not get around to update the menus to match the PS3 engines. Do you know when the new remote will be available?

Bottom line - The engine is 100% A-OK! 

THANK YOU very much!

Alex

PS. I also found out that one of my two remotes has very uncooperative buttons, and some have to be pushed really hard to make them work.

Last edited by Ingeniero No1

Gregg,

It seems a feature reset is no longer what it was for 14 years.

I'm not slo sure of that.

It could be that the fault lies not with the feature reset, rather, it's entirely possible that the feature defaults are where is the problem.

If the feature defaults were, instead of sounds at 100% or so and lights "on", that the defaults were sounds at 0% and lights "off", that would not only explain why a feature reset didn't correct the problem and also, perhaps, how the problem occurred in the first place.

If Alex is up for an experiment, all he needs to do to find out is to perform a Feature Reset of the engine.

I tried testing  with the hard key sound/  lights in the off position. A feature reset restored everything. I went to the sound menu and couldn't adjust the engine sounds volume, The sound hard key must be in the on position,

With the hard keys on.

With all the sounds set at  zero  under the sound menu, a feature reset restore everything to 100 %

There is a glitch though... Even though a feature reset retains the engine's ID, the custom name you've given the engine is lost and this engine reverted back to it's factory name. I don't have an upgraded engine to test but suspect the custom name just disappears.

I guess the bottom line is try all the options.. Hard keys, sound menu/ feature reset. BTW this was a proto-2.

Last edited by Gregg

Gregg,

Even though a feature reset retains the engine's ID, the custom name you've given the engine is lost and this engine reverted back to it's factory name. I don't have an upgraded engine to test but suspect the custom name just disappears.

That's a bug introduced with DCS 5.0 (or possibly with DCS 3.0, I can't really say for sure). Otherwise, Feature Reset appears to work as it should.

Add Reply

Post
The DCS Forum is sponsored by
×
×
×
×
Link copied to your clipboard.
×
×