Why won't a lash up stay in sync?

There was a bug that was given a work around by toggling the direction button. I am not sure if that is what you are seeing?

david1 posted:

Both my TIU and handheld is 6.0, the engines are PS3

when I make a lash up it runs and performs as it should. I can run it all day. But once I shut it down and come back later the rear engine is not in sync. I have done this with several sets of engines and each time the rear engine starts but is not in sync

what is the problem? 

 

I don't know, we're still at version 5 and not upgrading any further, but I'm curious how you get it working? delete  it and start over??

Sometimes I can bring up the rear engine on the remote and hit the start button. Then go back to the lash up and restart, they then will be in sync. 

It must be a bug in 6.0. Guess I'll wait for a fix from MTH. 

Dave 

My F7 NH exhibit this characteristic and moving it to a different place on the layout at startup solved the problem.  I think it is a signal issue where your engine is located on your layout.  When I park my F7s at a place that has a good DCS signal it always starts up properly.  When it is where a signal is not as strong I have found that changing the direction sometimes works as well as shutting down the trailing engine and restarting the MU.

This is a known, intermittent bug that's been around since DCS 5.0. However, my understanding is that it's only some (but not all) PS3 (but not PS2) engines that exhibit the bug. I have not been able to reproduce the bug with my own PS3 engines.

My understanding is that the typical workaround is to simply tap the DIR button once or twice to get the engines going in the same direction.

David1, check for thrown traction tires when this happens to you. Sometimes you'll find them laying track side where the engines fought to pull out.

Dave,

check for thrown traction tires when this happens to you.

Thrown traction tires can use problems, I agree, however, not an out-of-sync lashup problem.

Barry, let me clarify what I meant. I should have said, AFTER one of the engines in the MU lash up fails to run in sync, the other engines will experience wheel slip and many times will throw a tire. It is also best to replace it with a new one. Sorry for the confusion.

Dave,

I should have said, AFTER one of the engines in the MU lash up fails to run in sync, the other engines will experience wheel slip and many times will throw a tire. It is also best to replace it with a new one. Sorry for the confusion.

No need for any kind of an apology at all. I agree with your comment as restated.

I know this is an old post. My new MTH Maine Central f-3's have to be resynchronized EVERY time I run them. I use an MtH mobile commander since my layout is primarily Lionel Legacy. I took them to my friend who has a tiu and they misbehave there too. I think it's a DCs thing.

Actually, it's not that uncommon for TMCC/Legacy locomotives to have similar issues in an MU.  If a locomotive running backwards in the MU has a power glitch, it can switch to forward motion, then the engines in the MU are fighting each other.

Before you shut down. Do you push "save"  ?

Those units with (4) four, roller, center rail pick-ups, are the most reliable, IMO.  Atlas SW truck pictured.