Brand New MTH F40PH Not Responding In DCS Mode **PROBLEM SOLVED**

 throw the switches inside the engine to make sure they're not stuck halfway. ( make sure it's set to DCS and 3 rail)

Try adding the engine on a short piece of track as the only engine powered up. Sometimes the remote sees another engine and gets confused.

Make sure it plays shutdown sounds for a few seconds when you cut the power. If it doesn't, I believe the remote can't add it properly.

 I would still tether the remote incase something happened recently.

MTH engines can be finicky when they are first added.  In addition to the good advice above, I would take all the other locomotives off the track.  Sometimes, when adding a new MTH locomotive, the presence of other DCS locomotives or TMCC locomotives causes problems.  Why, I am not sure but it does.  

Do you have more than one TIU in use on the layout?

Ray Lombardo posted:

MTH engines can be finicky when they are first added.  In addition to the good advice above, I would take all the other locomotives off the track.  Sometimes, when adding a new MTH locomotive, the presence of other DCS locomotives or TMCC locomotives causes problems.  Why, I am not sure but it does.  

Yes I agree use a programming track or follow Ray's advice.... This could be a simple ID conflict&  hopefully the engine remains dark & silent when it first receives power indicating it's seeing the dcs signal.

Oddly enough, on a couple of initial "add MTH engine" events, I used the handheld as close as possible to the TIU (a few inches) and was able to load. 

Oddly enough, on a couple of initial "add MTH engine" events, I used the handheld as close as possible to the TIU (a few inches) and was able to load. 

Most likely due to a poorly seated transceiver board in the remote, TIU or both.

Greetings All,

 First, thanks to those of you who responded to my predicament.   I tried all of your suggestions and as a result a new problem has surfaced.  When trying to Add The Engine on a  programming track it sat silent for a few seconds and all of a sudden the start-up sequence came on (sounds and no movement).  After killing the power, the sounds stayed on for a few seconds.   I tried using a tether between the remote and the TIU (I am only using 1 TIU at this time) as well.  Still, "No Engine Found".  It's lookin' more like a Road Trip back to MTH.  Am I right?

 Chief Bob (Retired)

Happy Easter  

Do an engine reset with a conventional transformer, 1 horn 5 bells.

Do a conventional reset and you should get it to add to your remote in DCS.  Do not let people tell you that will not work.  Try it and see for yourself.  Sorry Dave, I did not see your post.  Good advice.  

Guys, if you have good signal on your track, add the engine there.  The program track is not needed.  If your track signal is questionable, use a program track.  

I would also try the "recover engine feature" using tiu # 1 . I would also use a programming track   or...all your other engines on dead tracks or off the layout. .  

It seems now with Proto-3 doing a conventional reset sometimes help?  Beats me  why though ??

Greetings All,

 Well, I think I've found the problem.  It's NOT the engines, it's the TIU!  I decided to test my theory by deleting an known functional engine already installed in the system.  When I tried to load it back into the system, guess what, "No Engine Is Found".  So I tried my Rev. G Back-up TIU and the same thing happened, "No Engine Is Found".  This was done on a separate Programming Track.  Here's the common denominator, both TIU's were successfully upgraded to the 5.0 software last year and I never tried loading an engine because I was dismantling my old layout.  Is there a possible problem that I am not aware of?  I tried the Reset (horn and bells) using a Z4K with no luck  I really need help on this one.  Thank you in advance!

 Chief Bob (Retired)

Happy Easter!

When you upgraded TIUs last year, did you also update the remote(s) to 5.0?

Recover engine is no help if the engine never added.

Here's the common denominator, both TIU's were successfully upgraded to the 5.0 software last year and I never tried loading an engine because I was dismantling my old layout.  Is there a possible problem that I am not aware of?

No, DCS 5.0 is absolutely not the culprit. Much more likely is a loose transceiver board in the TIU or the remote. This could have happened when you took the TIU and remote off the layout for upgrading and handled them differently than you do through normal use.

Connect the TIU's Remote Input port to the base of the remote with a 4-conductor (curly) telephone handset cord and see if things improve. If they do, we can proceed from there.

This and a whole lot more is all in “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!

Marty Fitzhenry posted:

Recover engine is no help if the engine never added.

I don't know Marty,,I know about the hard reset and ID 99 (trouble there) . I guess MTH doesn't test before shipping??

I think Barry's nailed it with the loose transceiver board. ( probably in the remote.)

Here's another thought   ..does the "read"  find the TIU??  without the tether? with tether?

Read should find the TIU both ways. If it don't find it without the tether, it may sure be the transceiver board.

Greetings Everyone,

 First, thank you all for your input and suggestions to correct my problem.  However, I think we are getting a little off course with the "loose boards in the TIU and Remote.  To be sure, I handle these items like the delicate instruments that they are, so loose boards are probably not the problem.  Here's what I DO know.  ALL of the functions worked with BOTH of these (Rev. L and Rev. G) on all of the engines previously installed.

1. Both Remote/TIU pairs (Rev. L and Rev. G) were successfully upgraded to 5.0 and continued to function as expected until today.
2. All functions of my "Test Engine" (MTH Premier Genset) functioned as expected using the Rev. L TIU and Remote that was upgraded last year.
3. The Remote "Finds" the TUI with and without the use of a tether. The message displayed on the remote is as follows: "Found TIU Addr 1 With 0 AIU Boxes Connected". This is the case with both Remote/TIU pairs (Rev. L and Rev. G).
4. I reset both the Remote and TIU (Rev. L) and when I tried to Re-Load the Genset , the following message appeared on the remote "No Engine To Add".

a). Power is off on programming track.

b). Engine is placed on programming track.

c).  Engine "clicks" when power is applied.

d). Attempt to enter engine into system.

e).  "No Engine To Add" is displayed on remote.

 At this point the Rev. L TIU/Remote pair will NOT allow me to load any engine into the system.  Folks, I'm at my wits end.  None of this makes any sense to me.  BIG THANKS!

 Chief Bob (Retired)

BTW, neither of the Remote/TIU pairs (Rev.L and Rev.G) will allow me to add any engines into the system.  When I try all I get on the remote display is; "No Engine To Add".  Again, these were both successfully Upgraded to 5.0 last year.  Strange really?

Delicate handling doesn't always preclude loose boards.  The simple test is whether tethering makes a difference.  Items a-e will occur even if remote is off.  If you're unwilling to "borrow" a handset cord from your wired phone to try tethering, then all I can say is mazel tov.

RJR posted:

Delicate handling doesn't always preclude loose boards.  The simple test is whether tethering makes a difference.  Items a-e will occur even if remote is off.  If you're unwilling to "borrow" a handset cord from your wired phone to try tethering, then all I can say is mazel tov.

Hi RJR,

As stated in my above post, The Remote "Finds" the TUI with and without the use of a tether. The message displayed on the remote is as follows: "Found TIU Addr 1 With 0 AIU Boxes Connected". This is the case with both Remote/TIU pairs (Rev. L and Rev. G).