Jeremy Towers

I have been pretty successful tuning my engine with a Wideband O2 sensor and data logging on the G4. No Dyno
There is one hitch though that messes up my logged results. That is LAG from the wideband sensor.
Is there any provision for entering Wideband sensor Delay when analysing data? Even a single delay time entry would improve accuracy a lot for road or track tuning. A 3D table would be awesome.
Maybe it is possible now to edit the log file in Excel by shifting all the Wideband data by the delay time, then loading it back into PCLink? But that sounds like hard work.
I know the Vipec guys use 'Mixture Map' and I am sure a method of correcting the errors from wideband delay would make that tuning tool WAY more accurate.
Your thoughts or suggestions please.
Jeremy

Hi Ashley
I hear what you are saying, but I still think it's a good idea. A lot of other functions in your PCLink/ECU also require a higher level of understanding, but not all users have to implement them.
Most high performance V8 engines have the O2 sensors at the collectors. That is some distance from the engine, so O2 data is always delayed. As far as 'actual' delay goes, I can see and measure the delay in mS between a throttle position change and an O2 response in the logged data. It is just frustrating that I can't compensate for it!
Jeremy