Lash-up disappearing ...

Could be static from our Webmaster's reaction when he sees that term

He just posted his gratitude when someone wrote of a multiple unit consist.  Now this . . .

At least he was happy on Christmas Day

 You maybe describing part of the 4.x bug? I have had some strange things going on too. I wish there was a definite list of the bug's problems and fixes. I get bits and pieces and then forget them until they show up again. Something about different TIUs than the original added one effect it?

 Oh Barry...........

You probably used rope that was too small when you tied your LASHUP together. The rope breaks and the LASHUP is gone.

Use bigger rope...

Lash-ups,(that's what we make in toy train land) have always needed the watch dog signal to move. They would start up , pSAs , couplers light sounds etc  worked as they should  etc but they wouldn't move. I've never had one disappear from the remote though. maybe the odd  lash-up member engine and needed the recover engine feature to get it back.

 At first I lost an engine. I didn't think much of it. A while later I lost another and it was sitting on the rails right there. I knew something was off. When a whole lashu multi-engine consist went, I thought it was the pain killers.

 Barry, thanks for posting that as I'm making a list so I remember. I've actually had engines disappear from the remote. I had wondered if it was because I bought a new TIU and had not readded some to that one. The remote added a new engine over that one address the first time so I was not even sure what or when it occured.

 The second time an engine disappeared, it was sitting right there and I tried to find it in the remote to run. I noticed it wasn't anywhere to be found? I had the system look for it and it added it to that  still open address if I remember correctly. It added as if it was never in there?

 Is that any part of a known bug??

Joe,

 Is that any part of a known bug?

Yes and no.

There is a known bug that can cause an engine slot to disappear from the remote, however, when it happens the only way to get the DCS ID# to become available again in the remote is to either restore a cloned copy of the remote, or to reset tne remote,

Under DCS  4.x, the empty slot typically doesn't just reappear.

 Well than this was different. The first time it happened, I had built a consist and it loaded into that slot of the missing engine. I had an older list that I wrote to keep track of addresses. Trouble was I didn't notice until some time later when I couldn't find that engine in the remote. When I tried to add it, I got engine error. I used the loader to find the address. I moved the consist out of it and the engine loaded fine.

 Second time it happened, the engine disappeared. I notice quicker as I was trying to run that engine sooner (different engine). I reloaded it without the same error trouble if I remember right.

 I just found it wierd that it happened at all. The first engine occured roughly when i added a new tiu without loading the engines into it. I just figured it was some kind of problem caused by me. This second engine happened some time later, I never justified it.

 So, is this a system failure? The engine remembered it's address. The remote had that address available. I did notice that there was no trace of that engine or address until I reloaded. Not sure if this happens to anyone else. I still wonder if it's because of the new tiu and maybe I missed something. By the second engine's disappearance, I had previously reloaded each engine and built new lashups into the new "L" TIU to smooth out operating problems.

My conventional lash-ups only disappear when they run into tunnels ...

Joe,

I got engine error.

That's a known DCS 4.20 bug. It happens when the engine that you're adding has the same DCS ID# as a lashup that's already in the remote.

The engine remembered it's address.

As long as the battery is good and the engine hasn't been factory reset, it always should.

 Ok then, so why do these disappear from the remote?

Joe,

 Ok then, so why do these disappear from the remote?

It's your remote, so you tell me.  

Barry,

Wouldn't it help most folks to place Lash-ups at a high ID # in the remote after they are added and save the lower ID#s for single engines?

This would keep a new engine from trying to add into the next lower Lash-up spot and avoid the bug in most cases.

 Well let's see. The board stores the address. The engine remembered it so it's not the problem. The fact that when trying to readd it to the system, I get an error because the system can't move a consist and doesn't seem able to change an address until it's added, right?

 Well.... the second engine was lost, it added right back..... the remote stores the slots?? so the remote has trouble remembering things like me!! Got it! How'd I do?? Maybe the remote clone thingy takes on my bad habits??

 I had wondered if adding the newer TIU improperly caused something in the remote to wander. I readded all the engines to the new TIU and built new MU consists. So, when it lost the second engine............nope I got nothing.

 Seems there maybe a remote memory failure executing in my future? Low batteries effect memory??Chip wearing out? trouble assigning and keeping track of engine slots?

 Is that software or hardware??

My problem is I build the lash-up and it works fine for that session.  The two engines get shifted to "inactive list" when the lash-up is built.

Once I power off the layout and the remote, then later power them back up, the lashup is gone from the remote.  The two engines are still in the inactive list.

I've tried this with all three remotes and the result is the same.

I don't see the lash-up taking up an existing engine ID ....

Wonder what I'm doing wrong.

If there isn't power on the track, should the lash-up go to the inactive list or is it expected to disappear?

Wouldn't it help most folks to place Lash-ups at a high ID # in the remote after they are added and save the lower ID#s for single engines?

I start mine in the 80's.

Barry,

I start mine in the 80's.

Wise idea!

Kerrigan , sorry for the interuption. I thought you were describing an issue that I've seen. I've lost two engines and possibly one consist, days at least, apart. I was thinking it might be a bug. The fact that you lose it every time maybe totally different.

 Is it stored in the same address each time?? How does the rest of the remote's responses go? Three different remotes?? Wow. Isn't the lashup stored in the remote?? or tiu??

 I guess no one else is seeing this??