Dave,
Sorry for the confusion. Through DecoderPro, I run an instance of a throttle launched from within DecoderPro on my Windows 10 PC.
When using the programming portion of DecoderPro through the programming track, that’s when the odd read behavior occurs.
thenks,
Russ
