Oh, that one is easy. It is easily +/- 1% with the several test gasses that I used on the test bench. Slightly more accurate than the ECM/NGK unit that I tested ( Powerdex ).
BUT, the test was performed at atmospheric pressure ( 0psig ). And, I , now, know that the Powerdex was expecting the test gas at ~1.5psi ( 0.1bar ). So, they may be equal, overall. HOWEVER, IF YOU DO A FREE-AIR CAL AT ATMOSPHERIC PRESSURE, YOU GET THE SAME ORIGINAL ERROR!!!
This is one of those cases of chasing the 4th digit.
As for time-skewing the data due to Windows timing. When using CAN data the MPVI, all of the data is collected IN the MPVI, then sent, together, over USB. So, it is properly correlated, at least to itself.
The problem is with USB/Serial ports. They take a separate path from the MVPI data. And that data has an unknown time skew, as compared to the MPVI data. This is PROBABLY not a big issue because serial data-rates are generally pretty low. ( in the 10Hz / 100ms range ). So, 20ms-50ms of skew isn't "that bad".
But, it is still an issue when looking at what I call "cell velocity". "Cell velocity" is the rate at which the RPM and MAP readings move through VE table cells. i.e. During dynamic events, the VE cell may change 30 times in a second ( 33ms per cell change ). So, 50ms of data skew means that the wideband data could be 1 or 2 cells off, from where it SHOULD be applied. Another 100ms of latency makes it even worse.
This kind of skew is a big part of what makes tuning an art. Knowing how to read between the lines.
If the wideband data always wound up in the right VE cell, anybody could tune