D500 posted:Just to condense my (and other's) feelings on the matter: wire it with DCS in mind.
TMCC is more robust and flexible, and can overcome most things - in fact, it seldom has issues per the layout and signal. (The "ground plane" issue does exist, but seldom happens; typically it comes up with stacked metal bridges and the like.)
Nailed it pretty tightly 🤔
Make even sized isolated blocks out of each power drop around a line; each drop centered on about every 6pc of track per block.
RJR, data signals can sort of perform a looping and cause echoing and mabe the loco sees it twice. No telling what the loco "brain" might be looking for numerically already, exactly when the data comes around turnout #2 for it's second pass in a micro-second later, hitting its own data tail end like a long train on a small reverse loop...except merging, and the data string is now "random numbers" but still read, the chip isn't smart enough to see that merge and stop reading.
Maybe a new command used fixes it, maybe a reset, et.. but the wiring runs suggested really should help keep that issue at bay. I've had data jump 3ft airborne into a similar but unrelated machines data lines too.
MTH DCS is a little more sensitive to this and tmcc gr.plane issues are a case by case; Lay it; test it, move any plane/signal around near the issue as needed until it's gone.
