Skip to main content

I recently added a TMCC command base to my DCS system. There have been no issues with MTH DCS engines. I wired the command base correctly because I can load the TMCC Atlas O GP-35 Wheeling and Lake Erie, start it up, blow the horn, open the front coupler, and move it forward. It will not go in reverse, fire rear coupler, and the speed is very sensitive. It goes from very slow to fast.

Each time I press a button on the DCS remote, I see the red light on the command base light up, even if the engine does not respond appropriately.

 

Any ideas on the lack of responsiveness by the engine?

 

Thanks

Original Post

Replies sorted oldest to newest

A few questions.

 

Is engine engine equipped with EOB cruise ?

 

Are you the original owner ?

 

Is this the only TMCC engine on your roster ?

 

Has the engine ever worked properly in a conventional or TMCC environment ? Unlike a Proto 2. I don't believe the couplers cán fire conventionally ?

 

 The fact that the engine responds to most commands and it moves. I'm sure you have it setup correctly. Can you possibly try running it with the TMCC base not connected in conventional form to see if it reverses. 

 If the engine is equipped with EOB cruise. In your manual it should tell you how to change the speed steps or disable them. The one Atlas engine I owned. Accelerated fairly quick. This was before they offered cruise. With EOB in 132 step mode. It should take of and accelerate slowly with no rapid jump between steps. If you aren't the original owner. The setting could be cruise off or 32 steps. There also could be something going on with tach tape or reader that would cause this to.

 As far as the rear coupler. Do you hear the Railsounds of the coupler releasing ?

 

 

 

Last edited by Dave_C

I am not the original owner - however, I do believe when I got it it was unused or very light usage.

 

This is the only TMCC on my roster.

 

The engine did work properly in conventional mode. It went in both directions no problem, but it was always a bit fast.

With the DCS remote, it does give a function to control the speed, and I did that so it is more responsive.

When I fire the front coupler, it releases and makes the sound.

The rear doesn't fire at all or make the sound when the button is pressed.

 

 

If the engine has EOB. The cruise feature is disabled running conventionally. In TMCC command there are 3 choices. Cruise off, 32 steps, 128 steps. The 128 shold make it perform similar to a DCS engine. Since you aren't the original owner. It may have been set at cruise off to run in a lash up. No way to tell other than resetting it. That could be the rapid acceleration your experiencing.

 

try. ENG, it's TMCC programmed ID ( the number you entered in the DCS remote ), DIR, AUX 1, AUX 1, AUX 1, you will hear a horn blast, then press 1 and you should hear another horn blast. This should put you in 128 step mode.

 

Originally DCS could only issue 32 TMCC speed steps. EOB had a workaround pressing the brake and boost buttons. A later DCS version gave the remote the capability of offering more steps enabling it to run both EOB and K-Line's cruise. I believe the setting on the DCS remote just sets up the remote. Not the engine.

 

 

I tried to reset it like you suggested Dave - it doesn't seem to reset - I didn't hear the horn.

 

However, if I press the AUX 1, and keep it highlighted on the remote screen, the direction button now works. 

If I also keep the REL button highlighted on the remote screen, the speed is more responsive and incremental.

 

Thanks for the replies, I'll keep fiddling with it.

Add Reply

Post

OGR Publishing, Inc., 1310 Eastside Centre Ct, Suite 6, Mountain Home, AR 72653
800-980-OGRR (6477)
www.ogaugerr.com

×
×
×
×
Link copied to your clipboard.
×
×