Smoke control through DCS

Pat,

You don't say what version of DCS you're using or what is the engine's type, i.e., PS2 or PS3. In the future, it would be very helpful to know the version of DCS and the MTH model number if the engine when you ask for assitance.

Regardless, , a few things:

• First, if you aren't using DCS 6.1, you should be.
• Second, the DCS smoke setting at Startup is determined by the smoke setting on the engine's smoke pot.
• Third, if the engine doesn't hold the setting from power-up to power-up, check the battery, if it's a PS2 engine,

Set the engine's smoke pot to max and make sure the battery is in good shape.

This and a whole lot more about DCS is all in MTH’s “The DCS Companion 3rd Edition!" This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at MTH's web store!

This and a whole lot more about DCS WiFi is all in MTH’s “The DCS WiFi Companion 2nd Edition!" This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at MTH's web store!

PS 3, Not sure of DCS version where do I check that? engine 30-20298-1

Barry Broskowitz posted:

Regardless, , a few things:

• Second, the DCS smoke setting at Startup is determined by the smoke setting on the engine's smoke pot.

 Doesn't work that way at my house Barry.  The smoke pot doesn't have any effect in command mode, either starting or running as near as I can figure.  I just turned the smoke pot all the way off on a 20-3172-1 4-4-0, put it on the tracks, and did a factory reset.  When I start it up, it has smoke enabled and running.  I can't see any effect of the smoke pot in command mode.

John,

I can't say why you aren't seeing the smoke coming on, unless your engine has smoke off as the factory default.

If you have an opportunity, try doing the same with a feature reset. That's the way I verified my engine's behavior.

Pat,

That's a PS3 engine so the battery isn't a factor, since it doesn't have one.

FWIW, I have the 30-20215-1 Interstate RS-3, pre-ordered when it came out. It has never smoked well for me. Looks to be a year or so earlier version than yours so I guess something could have been changed/upgraded along the way?

Mine has the smaller MTH smoke unit, single resistor if I remember correctly. It's not the one they use in most of their other diesels anyway, somewhat smaller than those. I have changed the wick and updated the engines PS-3 sound file with not much of an improvement. Still, this is one of my favorite engines, great sounds, IMO.

You may need a chain file update for your RS-3.  I recall there was a problem with the single element smoke units smoke output, and it was because of incorrect settings in the chain file.  I'll bet GGG remembers the details.

I agree, it sounds great I surmise that is a pure diesel sound not a diesel electric sound (?)

Barry, who said anything about batteries?  I tried Factory reset, Feature reset to no avail

I'm no sound or train expert, but it does sound like the old Alco diesels as I recall them...old memory involved here too! My brother-in-law is a BIG Alco fan and he was even impressed with the sound! Years ago ('70s-'80s) he went all over the country taking pictures of all the Alcos he could find! It's a cool engine, IMO.

GRJ, I take it the chain file does not come with the sound file and has to be obtained separately? If it does come with, I'll go get the latest version and see what happens. Thanks for the tip!

Maybe GGG will be along to comment. I have another engine I am going send to him one of these days too. Just waiting on a round tuit...

The PS/3 "sound" files come in a ZIP file with the sound file proper and the chain files in another ZIP file inside.  Unzip the two inner files and fire up the DCS loader, and use DCS Loader 5.0. 

Do not unzip the chain file zip, the loader will do that when you load the firmware.  You upload the sound file and chain file as separate steps.

Here's the PS/3 sound file for your engine from the MTH page, note the two files.  The small one is the chain file.

Thanks GRJ, I'm off to download some files! I am 99% certain I only updated the sound file before, and not the chain file.

Note that I don't know if yours is one of the affected units, only that it's worth a shot to see if it helps.  The issue with the old chain file was anemic smoke, so that's a positive sign.

It's pretty anemic, so definitely worth a try, or a re-try with chain file this time. Thanks! 

Pat,

I did.

 When I learned it was a PS3 engine (by looking it up) I backed off a battery as a possible culprit.

It is also easier to get the single small smoke element wick burned and not producing good smoke.  I would inspect the smoke unit.  Also these units take much less smoke fluid, if over filled you could spill into the smoke fan and it may not be running. At which point wick burns and no to little smoke.

IF this smoked well to start it is not a chain file issue.

Barry, what you say about smoke switch seems correct for PS-2 engines, but I am not sure it is for PS-3.  I have not studied it specifically, but I know it does not work on the bench tester when I am loading sf.  G

GGG posted:

Barry, what you say about smoke switch seems correct for PS-2 engines, but I am not sure it is for PS-3.  I have not studied it specifically, but I know it does not work on the bench tester when I am loading sf.  G

George, I tested a PS/2 locomotive on my bench, the smoke pot has no effect in command mode.  I haven't actually tested an upgrade with just the switch, maybe that works differently?

If the battery is attached and works.  If you turn smoke off via the conventional switch.  When you start the engine up it looks at the setting and uses those on a first time add.  Ever notice a low volume on DCS that goes loud on DCS Reset.  It can be traced to the conventional setting, which the DCS uses as a baseline.  Once you set a DCS Setting, that is what is used otherwise.  That is what we were taught.  G

Odd, I'm sure the battery works, and I didn't get that behavior.  Don't know exactly what happened, I'll have to try it again.