Skip to main content

Replies sorted oldest to newest

The only problems I've run into with mixing PS2 with PS3 in an MU lash-up is differences in momentum when stopping suddenly. If you use your direction button to stop and reverse, while clipping along at a pretty good speed, or if power is cut to the tracks while the engines are moving, the PS3 in the mix will stop earlier and get drug for a few inches. When this happens, sometimes a traction tire will pull off. Other times all the engines won't receive the change of direction command or the brake command all together (while running forward at higher speeds) and dragging will occur this way too. It's very possible that these issues could be caused from dirty track but I'm only guessing. I've learned it's best to stick with using the thumb wheel to come to a stop, then hit your direction button to reverse, when running MU's mixed or straight.

Last edited by Dave Zucal

Dave,

If you use your direction button to stop and reverse, while clipping along at a pretty good speed

I disagree, that's incorrect. If the deceleration (1-10) is set the same for both engines, they will both slow at the same rate. If they do not, most likely there's a defect in one of the engine's sound file (PS2) or Chain File (PS3).

or if power is cut to the tracks while the engines are moving, the PS3 in the mix will stop earlier and get drug for a few inches.

I agree, that's correct. Under DCS, there's no difference in the stopping distance when speed is decrease or reverse, as long as the declaration settings are the same for the engines.

Last edited by Barry Broskowitz

I have 2 MUs, one both PS3 and the other one of each. If I cut power they both stop dead. If I hit the direction button, they come to a slow stop. I always have ACC and DEC set at one. I have noticed one difference. If I hit shutdown when running single, the PS3 stops in about one car length. If I hit shutdown with my PS2 engines, they go about six car lengths before stopping. I just checked the mixed MU, and the PS2 engine was still turning long after the lead engine shut down.

Barry: If the individual engines are set to DEC differently and you set the MU at 1, which one takes priority?

John & Dave,

If the individual engines are set to DEC differently and you set the MU at 1, which one takes priority?

I really don't know.  

I tend to not fiddle with acc/dec rates at all. I leave the individual engines and the lashups at their respective acc/dec defaults setting, and have never had any problems stopping or starting a lashup.

Thanks Barry and John. This has given me an idea of a test that could be performed that would be all telling as far as stopping is concerned. I normally run 3 units together in an MU. I will separate the engines leaving about one foot between them. Start them and run them as a lash-up even though they are separated. Get them up to a decent speed then hit brake or direction and see if they all slow down and come to a stop together. I'm thinking all the engine's individual deceleration rates should be overridden by the lash-up deceleration setting and they should all stop at the same rate. Off to the layout I go.

Barry Broskowitz posted:

John & Dave,

If the individual engines are set to DEC differently and you set the MU at 1, which one takes priority?

I really don't know.  

I tend to not fiddle with acc/dec rates at all. I leave the individual engines and the lashups at their respective acc/dec defaults setting, and have never had any problems stopping or starting a lashup.

When ever I've done it, the lash-up setting takes priority. Of course the app didn't allow for any changes in these rates in the past. So most of my experience is with the remote.

 I always wondered if there was a sort of flaw in the software. When I'm running engines they always seem to revert to the factory settings. I was told over the years that was from different things like low battery or even poor signal. I have always wondered if it was actually caused by the software when an engine has been part of a lash-up and brought back as a single engine. Nothing seemed to keep track of the setting so the setting always seems to go back to factory. I know, I'm probably wrong again.

Your right Joe. The lash up setting does take priority over the individual settings. I ran a test after setting my MU engines deceleration rates to be all different and when they came around my staging yard I hit the direction button and they all stopped together. After the test I noticed their individual setting were all changed to the deceleration rate that the MU was set at. So the MU actually changed each engines individual settings to be the same and isn't just an over ride.

Attachments

Videos (1)
stop test
Last edited by Dave Zucal

Add Reply

Post
This forum is sponsored by MTH Electric Trains

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.
×
×