DCS Lashup Error

Have you tried entering 95 on the keypad? I just had a similar problem that showed an MU that didn't exist showing it at 250 smph. I split the remote and reseated the board and no more problems.

>>>Have you tried entering 95 on the keypad?<<< Yes, that's how I got to 95 on the list

Well??

For some reason, it thinks engine #38 is part of the consist.

I could only say that I would delete and rebuild the consist.

Are the remote and TIU both running DCS version 6.1?

What are the addresses of all the engines in the consist?

>>>Are the remote and TIU both running DCS version 6.1?<<<  Yes

>>>What are the addresses of all the engines in the consist?<<<  85 & 16

>>>I could only say that I would delete and rebuild the consist.<<< Yes, that's what I did. But this happens again and again.

I have never had this issue? (that I remember)

I'm thinking that maybe an engine is somehow associated to 2 addresses in the remote?

So..... What is in address #38?

Call it up on the remote by typing it in after pressing engines button

I might suggest to delete that engine #38 and then build a consist to see what happens if you feel like playing along here.

Were one of these 2 engines in that address before?

I'm only guessing at why you are seeing this. I build consists all the time.

Are you experiencing any communication issues using this remote?

Do you have another remote or the app?

Actually, I think this is  a bug in DCS. My remote is nearly full of locos & lash-ups. I believe it is  a  problem with  memory management.  Data from one lash-up is contaminating another.  In computer terms the "files" are getting "cross chained".  This problem is not specific to this particular lash-up pair. It happens with others too.

that's interesting but how come no body else is seeing that bug?

Try tethering the remote and build a consist!

How are commands with just a single engine?

any problems or issues with the thumbwheel?

Is this the only TMCC lashup with a problem? 

I don’t think anyone mentioned TMCC. 

Ids 91 - 99 are reserved for TMCC lashups

If this is not a TMCC lashup, then how is an address in the 90 range being used?

If this is not a TMCC lashup, then how is an address in the 90 range being used?

The DCS bug is that it allows one to edit the address of a lashup or engine and set it into the reserved range 91 - 99. After this is done, results are unpredictable.

Reference page 106 of Barrys book

my page 106 is about passive wiring

I read the page you are pointing to. I don't see anywhere that it states anything about a DCS lash-up in those specific addresses.

Do you have specific info on DCS lash-ups created in addresses 91-99?

Where did you get this info? How about when the remote is full and starts using addresses 91 thru 99 on it's own? (mine has)

This is from page 106 in Barrys book. 'The DCS bug is that it allows one to edit the address of a lashup or engine and set it into the reserved range 91 - 99. After this is done, results are unpredictable' is my opinion.  

Well, this would be easy for the OP. Build the consist in a lower open address. If there isn't one, move something or delete something to open a lower address. See if the issue clears up.

I must have an edition where Barry didn't state that opinion. I have the first edition I believe? I seem to remember someone making that comment years ago here. I just haven't substantiated it for myself.

It's an easy work around here if that's causing the issue. Hopefully MTH will see this and comment or fix the bug if it exists.

My DCS does this repeatedly. The latest issue was today, involving a different lashup and different locos completely unrelated to my original example.  Has to be a bug in the system and not specific to any one lashup or set of locos. Since my remote is near its limit for number of engines, I believe that the information from one lashup is corrupting another.  Whatever "file system" DCS uses is having issues. I wonder if the memory (chips?) in the remote is faulty.

What was this lash-up issues address this time? In the 90's?

My remote is nearly full as well. I haven't seen this issue myself. I did make space some time back by moving all my G scale to another remote. I build consists every session and I think I'd have seen this by now?

I have three remotes all running 6.1. One of them is a very old remote that has been thru a lot of abuse. It still works with it's own issues, but not this.

There might be something particular about your set-up, that's causing this error for you. I was digging for info above to see if it might be a thumbwheel failing.

I'd always first think it's a loose transceiver board when strange stuff starts happening. A tether helps find it if that's what's wrong.

 Right now I could only guess that your remote might have some corruption in addresses and needs resetting. If it's truly that full, Then I'd guess you have some housekeeping issues like I've had keeping stuff straight.

 You could try to go thru the remote addresses and clean up anything not used like old lash-ups. Down load the info to your computer, reset the remote, and then upload the info back to the remote.

 I am not a tech and I'm just guessing where you could go next. Again, I don't see other posts about any bug like this. So I'd guess it's not a DCS bug, but an issue that's occurring for you for some still unknown reason. Maybe this remote's main memory board is failing?

How many TIUs do you have?

I may have found the culprit. Contacted my train repair guru who in turn contacted MTH. They gave us a fix to try. Will post it if it fixes the problem. Film at eleven...

This one is bizarre. By process of elimination, a lot of trial and error and a whole lot of bad words I determined that whenever a certain MTH PS2 loco was on the layout, things would go badly for DCS stuff, particularly lash-up building and recalling lash-ups.
Take that loco off the layout and things would return to normal.  I didn't know exactly what was going on, only that there was something odd about this loco. My tech guy called his tech guy at MTH and gave me the solution. The main wiring harness lays directly on top of the board(s). Voltages and other RF are mixing with the DCS signal and the corrupted DCS signal propagates across the entire system affecting the TIU and Remote. The result in my case was that this locomotive would "hijack" the lash-ups I was trying to build or run and fool DCS into thinking it was part of some lash-up that it wasn't.

The solution was to either re-route the wire harness away from the boards or create a shield/insulator between the harness and electronics. Re-routing the harness was not an option because there wasn't enough slack or room within the body shell.  I made an insulator and slipped it between the harness and the top of the boards.

It worked. Everything works now. All the lash-ups issues I had are gone and my DCS is happier in general.  The problem wasn't DCS or the remote, just a flaky loco that was introducing interference and digital nonsense into the system whenever it was present.

I can't give any more technical explanation than that, as I'm not a technical guru. I just followed what MTH recommended and it worked!

Ralph, What did you use for the insulator material.  Thanks,  Joe

Normally that engine will exhibit symptoms that make it easier to figure this out. It would miss the watchdog signal and start right up for example. The remote would have trouble talking to it when selected.

 Many users keep extra engines off of the powered rails to prevent stuff like this.