The problem is caused by a Power Pro firmware issue that affects program track operations with both JMRI and the NCE throttle.

If you, by any means, attempt to write a value to any CV>256 in Program Track mode using an NCE Power Pro, the firmware will instead write to a CV<257, possibly corrupting ?your decoder.

For, example, if you use the NCE throttle to write a value to CV275, that value will be written to CV19 (the consist address) instead, making your decoder appear non-responsive to its normal address!

If you attempt use JMRI to write a value to CV275, JMRI intercepts that request (to protect your decoder) and instead throws an error (unfortunately not gracefully, but the error can be seen in the JMRI system console).

The DDE ?and other advanced panes in the TSU2 use CVs>256 so are affected.

The only workaround for these decoders is to read the decoder on the Program Track, then save and reopen in Program on Main mode. Attempting to use the NCE throttle as a workaround will simply corrupt other CVs in your decoder.

( The ESU decoders are not affected because ESU provides an in-decoder workaround that doesn't involve writing to CVs>256 so JMRI intercepts the write command and uses that workaround.)

If you have TSU2 decoders, your only choices are to use Program on Main or to get another programmer (such as a SPROG or an NCE Power Cab/NCE USB combination). JMRI can easily be configured to use two connections in the same session, with Program on Main, throttles, turnouts etc. being directed to the Power Pro and Program Track commands being directed to the SPROG/Power Cab.

Don't try other means to cheat around the firmware limitation in the Power Pro, it will inevitably lead to tears.

Dave in Australia