DCS Lashup question

I have the same trouble and is frustrating.  Add to the fact that when I have to go and select the 2nd loco it has mysteriously moved to the inactive list so there are extra buttons to push.

My best luck with lashups is when ALL power is off and I lift up the handles on the Z4000 to start DCS operations.

If I am running other trains and decide to power up a dead section of track where a lash up already exists, it behaves very poorly.  I have to shut down everything and start DCS and the Z4000 fresh with the lashup ready to go.

Not having fun with Lashups.

Ron

Ron...... I'm on 6.0.........Seems like my lash-up's where better way back at 4.3 or older. I don't mind to much adjusting everything separately if it would stay that way. I still feel like I should only have to adjust a locomotive one time. and it stay that way until I change it.  Single or MU.     Guess I'll just keep using the ALL feature.

ALL won't work for me.  I have an ABBA set with independant PS3 A units.  I would have to turn the trailing A around facing forward and that would look silly.  It would also hamper operations if I have other users.  The save lashup button seems to only work for that session.  Next session, everything is messed up again.

It couldn't possibly be a DCS problem... it must be us. <grin>

Ron

ALL won't work for me.  I have an ABBA set with independant PS3 A units.  I would have to turn the trailing A around facing forward and that would look silly.

Yep having to ability to change the  direction on start up would be a neat feature... not only for your ABBA but also for units like Train Masters , RS-11 GP 7/9s . I've been pushing  this feature for years.

clem k posted:

As all you experts know I pretty much given up on MU's. Well decided to try again, After I build my lash up I adjust the sounds and other stuff, but only the lead locomotive accepts the change. I don't remember that before. I can select the other locomotive's and adjust each one separately, than go back to Lashup and push save button, it seems to be OK. Is this the way it is now?  I tried different locomotives ps2 and ps3.   Only these locomotives are on the powered tracks.

Thanks

Clem   

Yes that's how I've done it since MTH added the "save" soft key.  I haven't done it with the app yet.

clem k posted:

Ron...... I'm on 6.0.........

You should go to 6.1 for all the app updates.

Ron,

Add to the fact that when I have to go and select the 2nd loco it has mysteriously moved to the inactive list so there are extra buttons to push.

There's n nothing "mysterious" about it. That's the way that lashups work.

When a lashup is started up, its members go Inactive. When a member is started up, all lashups of which it's a member go Inactive. I expect that it's done this way so that lashups can be included in ALL Engines operations.

My best luck with lashups is when ALL power is off and I lift up the handles on the Z4000 to start DCS operations.

That's because if a lashup misses the watchdog signal, it will startup and do everything except move.

This and a whole lot more about DCS is all in MTH’s “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!

This and a whole lot more about DCS WiFi is all in MTH’s “The DCS WiFi Companion 1st 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! Get the free TMCC & Legacy Addendum here!

FWIW i run three/ 5 engine mu's each session. I stayed with 4.2 as it is very stable. All engines remain in the active list and remember there individual settings. It seems like 4.3 and beyond the stability disappeared. All my power is ps3 and ps2 3v.

Hey Joe will that fix the problem I'm having ?

I don't remember every update. I do know that stuff gets fixed and upgrades are made. So whenever there's an issue and an update was made, I would always do the upgrade.

 I know it added stuff to the app control of lashups.

Joe wish I knew it would make an improvement. Really don't care about the app, I sold my wifi. I think Willygee has the best answer so far. Unfortunetly  I 'm thinking I will have to go to super TIU with the expansion I have in mind.      

 If I were being fully honest, I haven't been that happy since the old days of DCS ( 2.x ??)

There have been issues with each release that have drove me nuts at times. So I'm afraid to announce that 6.1 is the best. I still wait for issues to pop up (and they do). Simple mistakes made in the program seem to get overlooked and then not caught until enough users complain. Somewhere after 4.x up until now, I had so many problems in different directions that I got lost keeping track of what fixed what.

 I had a couple of engines run the wrong speed and the people at MTH blamed me. Seems like a backwards way to run a business to me, blaming the customer for defects. Then denying that they exist. I've seen fellow users actually dump the system over issues. I got an Amtrak engine painted the wrong color and absolutely no reply or even acknowledgement. Ah well.

 So when I run into problems, I don't bother keeping exact logs of what happened as long as at some point, it got fixed. I could be a better supporting customer and I try to help others as I stick with this system. I constantly compare DCC stuff as I know where I came from. I remain a loyal MTH customer as I feel I can be. I still like the system and I live through any issues.

 So when I read posts where others state problems and replies seem to deny they exist, I follow along to see the issue thru. I have learned not to post every issue as sometimes they are my fault. Sometimes, it's a bug. Sometimes, I believe the program was not properly beta tested before releasing it. Now I'm not blaming each beta tester. What I'm saying is that the program was not fully tested. Each tester may not have all the components that some advanced customers do. I don't know what the answer would be? I do know that MTH seems to look into stuff if enough of us insist that there's a problem. Otherwise it appears to get swept under the rug and ignored.

 That leads to more issues down the road that never got fully fixed and can morph into something else.

 To make things more fun for me, some users question who I am to even respond as I'm not qualified. Heck MTH did it so why not? 100 MTH engines don't qualify me for even knowing what to do with problems. Several installs don't make me a tech. Numerous engine fixes and software fix suggestions still don't make me a tech. I don't want to be qualified. I am just a customer and try to be supportive.

 In closing, I do like 6.1 so far. The latest releases seemed geared towards the app. If one doesn't use the app they aren't getting the latest features or changes. The remote still works. Someday very soon, it may not. I feel as though it's on the back burner for any issues with the app being the star of attention. I got that, from a MTH reply, not something I made up. No matter which path MTH chooses to pursue, I will follow. I will speak up when I can.

Joe thank you, Your last paragraph says it all, I feel like I'm getting pushed into something I don't want. When it's no longer fun its time for me to leave. 

Willy,

It seems like 4.3 and beyond the stability disappeared.

That's just not true at all.

Barry Broskowitz posted:

Willy,

It seems like 4.3 and beyond the stability disappeared.

That's just not true at all.

I should have been more clear..the stability for mu's disappeared.

this is real interesting. 

it is the exact same lash up issue we are having at the club

I don't know anymore. I get lashups where member engines are silent with features as they should be. Then I get some where member engines sound their horns and bells. Every once in awhile I see flashing number boards or weird occurrences. I think things move forward and then they don't. It doesn't bother me anymore as long as they go the same direction!

 Overall I'm happy that I can run PS2 and PS3 engine together, at all! I'm sure it takes some extra programming and there will be issues.

I should have kept a list of all the stuff that sent me for a loop. There were engines stuck in the inactive, lost engine addresses, flashing number board lights, engines confused over direction, PFA engines would not resume speed after, etc. etc.

 MTH did a decent job fixing most if not all. It took several DCS versions to get stable full results. I believe 6.1 to be one of the best so far. I give up on what I consider the small issues left with DCS. I am happy overall now. I should make that clear, I'm just afraid to announce it still! I do still have small issues with volume, sounds, and lights that I learn to overlook.

the stability for mu's disappeared.

Still not true.

Mark,

Every time they would shut the power down (end of the day or an engine changeout on another loop and the layout was shutdown) they would have to go back in and re-enter the Lashup in the remote.

It simply isn't a DCS software problem. I'v built literally 50 lashups under DCS 6.0 and then DCS 6.1 and I never break them down. They just startup every time that I want to run them over a period of months and years.

If you truly experienced the issue that you describe, there was something else going on. One thing that comes to mind is that, perhaps, the version of DCS that you thought was in the TIU and remote was not actually the same. A second, although less likely, possibility is that the TIU or remote was somehow defective.

If this was actually a defect in DCS, I'm absolutely certain that I and other beta testers would have seen it firsthand.