WTIU DCS Signal Quality Issues with Legacy Engines on Track - SOLVED

@Jerryrails posted:

In summary: Unless a team of you is willing to come over here and walk me through this, I’m sticking with my Cab 2 and DCS. Thank you very much.

I think the smart money for you is to adopt a wait-n-see attitude.  There are plenty of folks working on sorting out the issues and providing feedback to get them resolved.  In a few months or perhaps a bit more, I suspect the landscape will be a lot clearer.  You have DCS and Legacy, so what either of these products bring to your table isn't nearly as great as for the people that don't have one or more of those products.

Some of the issues appear to be a lack of understanding of how to use some of the new capabilities, but other issues are almost certainly still to be resolved by the manufacturer.  There's no reason to beat your head against the wall until it's necessary.

@MartyE posted:

Hardly solved.  I have a lot of Legacy engines and I am not about to open everyone of them to install a inductor to satisfy the WTIU especially if they are under warranty.  I really hope @MTH RD can tweak the WTIU code to be more forgiving.  I've used DCS since it came out without any issues and want to continue to do so but again without modifying my Legacy engines.

There's likely very little that MTH can do to help the issue with Legacy engines squashing the DCS signal. Sure, they can turn the signal up, but there is only so much power they can apply before the signal becomes distorted.

As I said before... This is where the big O-scale/O-guage manufacturers chickens will come home to roost. The lack of DCC support is really showing now 30 years on.