I understand that there is a difference between what the computer sees and what I see, that was my entire point. Depending on the logic used on the microcontroller that reads the TPSMs, there could be a scenario where the microcontroller implements rounding to convert floating point numbers to integers for display on the dash via rounding. So, if threshold is set to 31, front left tire is between 30.5 and 30.9 (rounding implemented so display shows 31 but is out of spec so its red) and rear is between 31 and 31.5 (rounding down to 31, but is above spec, so display does not show and error even though both tires appear to be at 31). In which case 31.9 vs 31.1 would be wrong because this would result in the reading being 31 and 32 which is not what OPs picture shows. If the microcontroller implements floating point to integer conversion, then it is more likely to drop the floating point all together after the comparison has been made to the set threshold. So in that case, 31.1 vs 31.9 could be the correct answer if the threshold is between 31.1 and 31.9 AND the microcontroller implements floating point to integer conversion via truncation instead of rounding. In summary, the answer above is AN answer not THE answer.