Hi team,

Is there a way to cap or filter the displayed torque curve when torque converter multiplication causes artificially high values at flash RPM?

For example, I’ve had several auto cars that report peak torque around 2000 RPM — sometimes showing 650Nm — even though the rest of the run averages closer to 500Nm once the converter is fully coupled. This artificially high torque skews the dyno graph and also shows up incorrectly in the peak torque readout at the end of a run.

In one particular case, the car came on boost right at converter flash, and didn’t fully settle until around 3500 RPM, with a redline of 6000. I don’t want to set the dyno to delay the start until 3500 RPM, as it would ignore almost half the usable data range.

What I’d like is a way to apply a user-defined torque filter, such as:

“If torque > X at RPM ≤ Y, then don’t display or include that value in the graph or summary.”

That way, we can preserve the full run data, but filter out misleading peak torque values due to converter multiplication, and instead display the actual peak engine torque.

Is this possible, or could it be added as a future feature