No Engine Found MTH ES44AC

Did you check to see if your switches are set to "3-Rail" and "DCS"?

Yes, both are set to 3 rail and DCS. 

How are you adding the ES44AC?  Are you using "read"  or going to "engine" - add MTH engine?

Engine then add engine.

Can you run it in conventional?  Does it run forward-neutral-reverse-neutral in conventional?

If so - get in neutral - try a conventional factory reset.  Then go to DCS and add engine.

Happened to me once with a ES44ac ps3...one remote would not load,2nd remote did and then the first remote loaded fine..go figure. I am 4.20. I run several 4 and 5 engine mu's which are 4.2 friendly.

I am able to try a reset with the horn and bell buttons, it responds with horn. It does not run in conventional forward reverse. It just starts and sits. I can add other Proto 3 engines no problem. However, when I tried "recover" and powered up it started to move forward. Blah! 

John

what softrware on TIU,Remote?

Version 5.0

jnadpa posted:

Tried to test run my brand new MTH ES44AC Evo-hybrid. When I power up the track the engine starts and idles. I tried to add the engine several times. Same result - no engine found. Trial and error, removed and added other MTH engines no problem. Tried channel 2. Reset remote and TIU. Also tried an isolated test track, same result. Looked through the  DC Companion for some answers. I'm stumped and probably overlooking something really simple. Any help would be appreciated.  Thanks.

I don't think you've overlooked anything. (different channel, reset remote& tiu, test track)

 The engine seems lock in forward in conventional mode and is missing the watch dog signal. I would think the first step is a factory conventional reset . This might be a little tricky with the engine moving forward. Even if you have success where do you go from there?   I haven't had much experience with proto-3  but recall reading similar threads on the dcs forum. It's probably fixable without taking anything apart.

No luck so far. "Engine not found" It won't  run in conventional  mode, just starts and idles, sounds, smoke, lights ok. Factory reset, two blasts from horn. Then starts right up in DCS, not found. Missing watchdog. 

Any suggestions? 

I hate to call MTH or send back.

Thanks,

John

Is this the newest PS3 model?

What are you powering it with?

I think so, 20-20506-1. Just delivered last week. Not sure if there is a newer one.

Z-4000 and TIU. I also tried the wi-fi controller, same results.

John

If the switch is defective or wire opposite it could be in DCC mode.  First, with TIU not attached, or DCS signal turned off, can it run and function in conventional. Your post seem contradictory on this?  If it runs and operates fine in conventional, but won't load in DCS try clearing ID#1 and try again.  Try switch in DCC position, if still no go shell needs to come off to check some other issues.  G

Thank you G.

I will try it out and post the results.

John

OK go figure, it operates in conventional with switch in DCS and TIU bypassed. Forward and reverse, all lghts, smoke and sounds. Powered down switched to DCS connected TIU,  powered up, add engine..."no engine found".

John

Try changing the batteries in your hand held unit.

Good luck,john

jnadpa posted:

OK go figure, it operates in conventional with switch in DCS and TIU bypassed. Forward and reverse, all lghts, smoke and sounds. Powered down switched to DCS connected TIU,  powered up, add engine..."no engine found".

John

Still missing the watch dog?     Reset the remote again..... Try the recover engine feature, Do a track signal test  at the adding track.  

OK I replaced batteries, reset remote, powered up engine started, "not found", recovered -then engine shut down. Powered up engine started to move forward.  Turned off power, power up and engine is dark. 

John

jnadpa posted:

OK I replaced batteries, reset remote, powered up engine started, "not found", recovered -then engine shut down. Powered up engine started to move forward.  Turned off power, power up and engine is dark. 

John

I'm not sure if this is good or not? If you received the message "engine recovered" that's  a good sign. However the engine doesn't automatically get added to the remote. Now's the time to try adding it again... Having the engine dark & silent is also a good sign. See what happens  with another add try.

The processor can do weired stuff when testing like this.  So it work fine in Conventional.  But won't load in DCS.  Did you try loading with switch in DCC position?  If that still does not work, I would remove shell and take the 40 pin connector out carefully without pulling on wires.  Make sure continuity on DCS switch when in the DCS position.  2 wires should be connected.  Make sure the 2 end pins are not bent or damaged and reconnect 40 pin full.  Make sure no wires around the signal transformer (small 4 legged donut with wire wrap near the black relay).  Try again.   G

John:  Is there any way to test your TIU  with some isles TIU .

Sound like the TIU may be defective  

Good luck, John 

I will try out these ideas.

Thank you all for the help! Enjoy your holiday.

John

John,

When you finally figure it out.

Please e-mail me.

I would like to know the final out come here.

kb2agpjohn@aol.com 

Thanks, John

Will do. Thanks

John

What George suggested will usually work for you.  Pins 1 and 2 go to the DCC/DCS switch.   Check for continuity back to the wires on the 40 pin.  Also, pull and reseat the 8 pin plug.

Thank you very much Marty I will keep trying and congratulations on your layout milestone. That's awesome! I have plans for future expansions, enjoying the hobby so far.

There is so much experience and knowledge from the members here on the forum. That really helps out newer railroaders like me.

Thanks again.

Enjoy your 4th of  July.

John

A common problem with lack of any or a weak DCS signal on MTH PS3 diesels is routing of the wires from the 40 pin harness under the 4 large capacitors on the PS3 board.  Carefully pull the wires from under the caps, flatten the caps against the board and route the wires above the caps on top of the board.  I like to push the caps back against the leads so that the legs form a 90 degree angle.  Also, as mentioned above, try to route wires away from the exposed coil next to 8 pin plug, although this is not as important as clearing the area under the caps (the coil strips the DCS signal from track power).  Pay careful attention when reinstalling the shell to be sure that no wires above the cab will not rub the flywheel and that wires are not pinched under body posts or frame sides. Any engine that I service at MTH is checked for this issue and corrected.

Jon G posted:

A common problem with lack of any or a weak DCS signal on MTH PS3 diesels is routing of the wires from the 40 pin harness under the 4 large capacitors on the PS3 board.  Carefully pull the wires from under the caps, flatten the caps against the board and route the wires above the caps on top of the board.  I like to push the caps back against the leads so that the legs form a 90 degree angle. 

If your already showing 10's for dcs signal does the above help with the occasional "smothered" signal or start up on its own with out the command?

Jon G posted:

A common problem with lack of any or a weak DCS signal on MTH PS3 diesels is routing of the wires from the 40 pin harness under the 4 large capacitors on the PS3 board.  Carefully pull the wires from under the caps, flatten the caps against the board and route the wires above the caps on top of the board.  I like to push the caps back against the leads so that the legs form a 90 degree angle.  Also, as mentioned above, try to route wires away from the exposed coil next to 8 pin plug, although this is not as important as clearing the area under the caps (the coil strips the DCS signal from track power).  Pay careful attention when reinstalling the shell to be sure that no wires above the cab will not rub the flywheel and that wires are not pinched under body posts or frame sides. Any engine that I service at MTH is checked for this issue and corrected.

Great advice Jon, have had to do this wire re-route to a few engines with DCS response issues.

Jon G posted:

A common problem with lack of any or a weak DCS signal on MTH PS3 diesels is routing of the wires from the 40 pin harness under the 4 large capacitors on the PS3 board.  Carefully pull the wires from under the caps, flatten the caps against the board and route the wires above the caps on top of the board.  I like to push the caps back against the leads so that the legs form a 90 degree angle.  Also, as mentioned above, try to route wires away from the exposed coil next to 8 pin plug, although this is not as important as clearing the area under the caps (the coil strips the DCS signal from track power).  Pay careful attention when reinstalling the shell to be sure that no wires above the cab will not rub the flywheel and that wires are not pinched under body posts or frame sides. Any engine that I service at MTH is checked for this issue and corrected.

Jon, Interesting, the bulletin on this did not mention under cap wires.  In conversations with Don, he stated he can see the impact of specific wires next to the signal transformer degrade DCS Signal.   G

The interesting thing to me is, my PS3 and some PS2 engines miss the watchdog signal and then refuse to respond to commands. A simple power cycle does not fix it. It seems like if you wait a few days, it cures itself. That's when I posted about the software.

 No, this doesn't happen all the time. Many of my engines are not affected. That makes finding the problem elusive to me. It always has occurred with lashups only.

 There was a problem in the past limited to just PS3 engines just missing the watchdog signal. They could be addressed and started up relieving the issue. So I believe there are many things at play here. When it's just a PS3 engine running alone and stubbornly missing signals, it seems easier for me to locate the issue. Hopefully that's all that's happening to this engine for the OP. I don't wish to make this a big drama. For readers searching for answers, there maybe issues complicating the answers.

 I am patiently waiting for the next DCS release to cure some issues.

willygee posted:

Jon G posted:

A common problem with lack of any or a weak DCS signal on MTH PS3 diesels is routing of the wires from the 40 pin harness under the 4 large capacitors on the PS3 board.  Carefully pull the wires from under the caps, flatten the caps against the board and route the wires above the caps on top of the board.  I like to push the caps back against the leads so that the legs form a 90 degree angle. 

If your already showing 10's for dcs signal does the above help with the occasional "smothered" signal or start up on its own with out the command?

It may help.  It is the preferred way to wire the diesels.  If the loco starts like a jackrabbit before any sounds come up, that is a software issue that must be corrected by reloading the sound file via the pogo fixture which is only available at MTH.  It is a rare occurrence, and it won't do it on every startup, but I've had a few that exhibit this issue.  

GGG - Don and I have found that the wiring under the caps is more of an issue affecting DCS signal than wiring near the coil, but we will route the wires above the caps and away from the coil, as best as we can.