My Imperial Christmas Diesel has a smoking problem

Are you running it conventionally or with DCS?

Just started running DCS today with that inexpensive Remote Commander.

Okay.  I'm not familiar with the Remote Commander so someone else will need to chime in.  Barring an easier solution, you could always pop the shell and unplug the smoke unit.  I believe the smoke-dial is meant to reduce the volume of the smoke rather than turn it on/off.

Thanks Mike, as the Remote Commander is new to me as well I haven't a clue what is going on.

@Former Member posted:

I am perplexed to say the least since the smoke unit appears to be producing smoke regardless of the setting w/o any smoke fluid.  Other than the obvious wish not to set off smoke detectors, I don't want to burn up the smoke unit either.

Any ideas?

The hint- you are running DCS command mode.

The volume pot and smoke switch or pot in PS2 or PS3 is read by the firmware on power up. However, if it sees a DCS signal- then the action or function is then controlled by DCS controls- and smoke defaults to ON.

Again, what is different?

Last year, you ran conventional only- so the engine followed your conventional only settings with the smoke pot off.

This year, you added remote commander- the most basic form of DCS command control. In doing so, you had to reset the engine to factory defaults and that combination, along with how the firmware handles or only reads the smoke pot or switch state at startup in conventional- not surprising in the least to find smoke enabled in DCS regardless of the physical setting. Working as intended.

Vernon, thanks for the insight. But given my circumstances i.e. not wanting the smoke unit to operate how do I disable it?  I do not have a clue.

@Former Member posted:

Vernon, thanks for the insight. But given my circumstances i.e. not wanting the smoke unit to operate how do I disable it?  I do not have a clue.

Here is a note from @GGG about turning off the smoke unit when using the DCS remote commander: https://ogrforum.com/...68#70974704628220768

When using DCS Remote Commander, you need to turn smoke off before applying power.  Normally, smoke and volume off is CCW.  Then put on track and apply power.  The Engine will read the setting of the smoke and volume switch and use those settings.  Sounds like you finally got it.  Once you make a setting change you do need to wait at least a minute before trying again.  The processor can still have power and be running with previous settings.  If you apply power too early, it won't use the new settings you did.

There was an issue with early PS-3 that the smoke unit would still run at a low volume, but that was fixed with new flash code.

@H1000 posted:

Here is a note from @GGG about turning off the smoke unit when using the DCS remote commander: https://ogrforum.com/...68#70974704628220768

When using DCS Remote Commander, you need to turn smoke off before applying power.  Normally, smoke and volume off is CCW.  Then put on track and apply power.  The Engine will read the setting of the smoke and volume switch and use those settings.  Sounds like you finally got it.  Once you make a setting change you do need to wait at least a minute before trying again.  The processor can still have power and be running with previous settings.  If you apply power too early, it won't use the new settings you did.

There was an issue with early PS-3 that the smoke unit would still run at a low volume, but that was fixed with new flash code.

Thanks H1000.  Very informative and interesting reply.  

I am using the inexpensive entry Remote commander and as such I do not have a lot of button options (unless there is a sequential equivalent) and certainly no ability to enter codes.

My engine was purchased new last year around this time.  I do not know where that falls in the PS-3 timeline.

#1 Yes, you bought the cheapest and lowest feature control version of DCS. Unfortunately, it has NO smoke control feature at all. NONE. I blame MTH for the situation or lack of control system options and have given them ideas on how they could improve that (example app update and upgrade to the Explorer limitations) met with deafening silence.

https://ogrforum.com/...-unlock-the-features

and, and, and, and, there was supposed to be an app update anyway- and we are all still waiting on that.......

https://ogrforum.com/...0#180354858570968420

#2 The means you are depending on the manual smoke switch or potentiometer settings to also carry over to DCS operation. As stated previously, that status is read when the engine is first powered by the firmware, however can be overridden by the DCS operation defaulting to on. This is an inherit limitation of "the system" of both the control you chose and deciding not to run with smoke on (when that control system is limited DCS commands with no smoke control command).

#3 Hence, best practice is to ensure the smoke unit is filled  "just in case" a momentary power loss or other glitch with this limited control system ends up with the smoke unit on.

#4 to recap- your only way of turning smoke off with your current control system setup is the manual control switch or pot. Due to limitations of how the firmware uses that setting, it might turn on even with your manually setting off. All you can do is power down the track completely (no, the shutdown button on the remote does not solve this), wait for some time for the engine to 100% shut down internally, and then try again.

Vernon,

Thanks for the bad news!

#1 yes, I was over in traditional MTH tin plate land during the DCS evolution and have almost none of those products which now sell at a premium as I understand it.  I have a more elaborate hand held remote but no TIU.

#2 agreed as I am my own worst enemy. .  

#3 Sound advice.

#4 Understood

#5 go back to the Z1000 controller and wait for the new DCS system to become available.