Lash Up Issues

Maybe the speed match was off a bit.  I always watch the couplers to see if one is pushing or pulling.

I run multiple units all the time. You have to watch closely now, as bugs are messing things up. I have had units running backwards and even had one get locked in conventional reverse.

I believe with every new version of DCS, lashups are getting messed up more. Lighting is all over the place with no certain results. I know of guys who stayed with older versions to avoid the headaches. I upgraded because of WiFi. It just keeps me on my toes. It does work but you must watch every time you run any older lashups. I believe it maybe best to rebuild every one. I'm a big fan of using DCS. It has been more of a challenge every year.

 Btw, I have not lost a board to any bug. 

I agree with Joe !  Strange things happen as long as there is one lashup in the remote. and PS2 is better than PS3 locomotives,  at least that is the way it seems to me .

Engineer-Joe posted:

I run multiple units all the time. You have to watch closely now, as bugs are messing things up. I have had units running backwards and even had one get locked in conventional reverse.

I believe with every new version of DCS, lashups are getting messed up more. Lighting is all over the place with no certain results. I know of guys who stayed with older versions to avoid the headaches.

That would be me...willygee..still 4.20 and i run 3 MU's 5 engine each ps2 and 3 mix. One of the MU's approaching 5500 scale miles

 

Ken,

I have MTH locomotives that "like" being lashed, and others that don't. The 4141 Bush SD70ACe (PS-2) and N&W ES44AC (PS-3) have run together for hours. None of my three J's like being lashed with anything. My goofiest lashup is a RK VO100 w/ the Galloping Goose. While not physically connected, I frequently set them for a lash-up so I can control both at the same time. They have run very close together for long periods with no perceptible variation in their spacing. Seems the slower they run, the better.

As David said, probably speed related. When I setup a MU consist, I leave the units decoupled for a loop or two around the layout before I physically connect them. If they stay together, great. If one runs away or if they crash together, I punt the idea of running them together. FWIW I was doing this with an older TIU/remote. Not sure if this makes any difference.

Gilly@N&W posted:

Ken,

I have MTH locomotives that "like" being lashed, and others that don't. The 4141 Bush SD70ACe (PS-2) and N&W ES44AC (PS-3) have run together for hours. None of my three J's like being lashed with anything. My goofiest lashup is a RK VO100 w/ the Galloping Goose. While not physically connected, I frequently set them for a lash-up so I can control both at the same time. They have run very close together for long periods with no perceptible variation in their spacing. Seems the slower they run, the better.

As David said, probably speed related. When I setup a MU consist, I leave the units decoupled for a loop or two around the layout before I physically connect them. If they stay together, great. If one runs away or if they crash together, I punt the idea of running them together. FWIW I was doing this with an older TIU/remote. Not sure if this makes any difference.

I agree the problem is most likely due to a speed mismatch, however I did check both pairs by creating the lash up and running them together, but not coupled to see if there was a speed mismatch. Both pairs that failed looked pretty well matched.

Is there some kind of specification for MTH's speed control that says how close actual speed is to the SMPH shown on the remote? For example plus or minus 1 SMPH. I thought all MTH engines whether PS2 or 3 were calibrated to run at the same speed the remote displays.

Ken

They're suppose to run at the same speed  however they always  don't. Even the same engines might run slightly different.   It's too bad there  isn't some type of adjustment available. 

One other thought.....Get rid of the traction tires and there would be less fighting if the engines were a little  off . Maybe the odd skid but enough to do any real damage.  Might even save the odd board.  

I don't run lash-ups much anymore .

kanawha posted:

I have three pairs of engines that I've run in two unit lashups. For two of the pairs, both engines are 3 volt PS2's. The other lashup pair is a PS3 and a 3 volt PS2. The one with the PS3 board failed while being lashed up (fortunately it was still under warranty). Recently one of the PS2 pairs lost a board while being lashed up. By failed or lost I mean the engine stopped dead with the accompanying burned electrical smell.  Both sets that failed maybe had a couple of hours run time on them in lashup mode.

Needless to say I am reluctant to run any of my MTH engines in lashup mode any more. I haven't experienced any other PS board failures on any of my other MTH engines, but none of them have ever been lashed up. Has anyone else had this problem or am I just unlucky?

Ken

 

What firmware are you running?

willygee posted:

 

What firmware are you running?

The first failure was with the PS2/PS3 pair. At the time I was running V4.3. The second failure was with a PS2/PS2 pair running with V5.0. I had built this lashup using V5.0.

Ken

I wonder how many other multi-power unit operators are having success or issues with the latest firmware...it's almost like we need a poll. I could not give up my MU operations

Gregg posted:

They're suppose to run at the same speed  however they always  don't. Even the same engines might run slightly different.   It's too bad there  isn't some type of adjustment available. 

One other thought.....Get rid of the traction tires and there would be less fighting if the engines were a little  off . Maybe the odd skid but enough to do any real damage.  Might even save the odd board.  

I don't run lash-ups much anymore .

I bet there may be some way to have a multiplier or in the software or a pot that could be used to adjust the speed from the tach reader's findings??