I created a new lash up yesterday and today when I pressed startup the engines started, but they didn’t move, neither forward or reverse. After shutting down the lashup I then started each one individually and they both responded. I shut them down and brought up & started the lash up again, this time the lash up operated perfectly. I was just curious if anyone had this same experience.
TIA
Replies sorted oldest to newest
I could only guess that there was a signal problem where or when you first built the consist.
You didn't state if you were using the app or the remote. If the app, which version (ios or android).
What version of DCS is in each control unit.
Etc., etc.
My experience with lash-ups has been that they don't keep well when the power is interrupted. One of the engines doesn't respond well. I usually end up selecting and starting each engine, then selecting and starting the lash-up.
Sometimes an engine gets lost in which case the lash-up has to be deleted, everything reread, and the lash-up rebuilt.
I generally delete my lash-ups when I'm through running.
Matt, Thank you. My problem is the lashup starts and runs alright but is loud. As soon as I hit volume decrease the lead engine’s sound (all) cuts out and will not start again until I run it separately. All other functions work and the tail engine is unaffected. I will try your technique.
It's likely that one of the lashup ropes is loose... 
Bill, don't let Rich get under your skin. Here we are talking about the mating, or lash-up, of the electronics of two toy train engines that have DCS or TMCC so they run together. The train companies use this term in their manuals and to limit confusion, especially for newbies, I think it can be used in discussions like this. However, using consist like Joe did will keep Rich happy.
Anyway, DO NOT USE LASH-UP when talking about running your train, or in operations. To keep me out of trouble with Rich and other members of this forum with railroad backgrounds, I use multiple unit (MU) or consist when running diesels, and double- or triple-headed when running steamers or if each engine has its own engineer at the controls.
In both our cases, the lash-up isn't working and we are not able to run our double-headed engines (or MU) in a train.
If I get banned from the forum I may have to rethink this.
@Rich Melvin posted:It's likely that one of the lashup ropes is loose...
@CAPPilot posted:Bill, don't let Rich get under your skin…However, using consist like Joe did will keep Rich happy…To keep me out of trouble with Rich and other members of this forum with railroad backgrounds, I use multiple unit (MU) or consist when running diesels, and double- or triple-headed when running steamers or if each engine has its own engineer at the controls.
If I get banned from the forum I may have to rethink this.
No one will be banned if you use the word “lashup.” I’ll rattle the cage of the poster a bit, but they won’t get banned.
@Rich Melvin posted:It's likely that one of the lashup ropes is loose...
You sure are getting a lot of mileage out of this picture. I’ll start looking for my royalties check in the mail. Lol!
@MartyE posted:You sure are getting a lot of mileage out of this picture. I’ll start looking for my royalties check in the mail. Lol!
Yes, I should have credited you for these images. They are classics!
I think I owe you 3 cents on this so far. The check is in the mail.
LionelBill,
You didn't say if they are MTH engines or Lionel, but I guess your name here is a good clue. I have less experience with TMCC than with DCS, but I'm still curious about this because I run both so I'm following along.
I have had good luck with DCS Mash-Ups and even Distributed Power using an iPad app. I hope the phrase "Distributed Power" is allowed here....LOL.
Rich, I love your rodeo pic!
Bob
@AGHRMatt posted:My experience with lash-ups has been that they don't keep well when the power is interrupted. One of the engines doesn't respond well. I usually end up selecting and starting each engine, then selecting and starting the lash-up.
Sometimes an engine gets lost in which case the lash-up has to be deleted, everything reread, and the lash-up rebuilt.
I generally delete my lash-ups when I'm through running.
I have the exact same experience. Also , I notice an issue loading new engines when there is a "lash-up" still in the engine list. The new engine will not be recognized. If I then delete the lash-up, the engine is found and can be entered. So, I delete the lash-up now after the running session. I make new ones all the time anyway.
Mike
@LT1Poncho posted:I have the exact same experience. Also , I notice an issue loading new engines when there is a "lash-up" still in the engine list. The new engine will not be recognized. If I then delete the lash-up, the engine is found and can be entered. So, I delete the lash-up now after the running session. I make new ones all the time anyway.
Mike
Mike, are you talking TMCC or DCS? I have only had real problems with DCS after Apple did one of their so-called updates. Raised all kinds of **ll with DCS finding engines, etc etc....
Bob
@endless tracks posted:Mike, are you talking TMCC or DCS? I have only had real problems with DCS after Apple did one of their so-called updates. Raised all kinds of **ll with DCS finding engines, etc etc....
Bob
Bob, DCS problems only. I have no issue with Legacy lash ups.
Mike
Access to this requires an OGR Forum Supporting Membership
