Since the single byte RPM value via the MUTIII doesn't provide much resolution, how does ecuEdit calculate the HP/TQ? Does it throw out repetitive RPM values? Would getting a 2-byte RPM response make the HP/TQ calculations better/smoother/accurate?

Hello, could someone address my question?

No problems with 1 byte RPM. The major problem is due to time which is not accurate, the ECU deciding when it can send something, and time tagging being hard to do acurately.
Anyway, I never experienced problem getting smooth and good dyno traces (smoothing between 4, 5, 6 or 7, never more), and playing with the end point (must be dropping rather than increasing).

XNWRX wrote:and playing with the end point (must be dropping rather than increasing).

I did not know that. I'll give it a try.