AFR never were on target until first boost no matter how fine a tune. It was consistent every time.
Now I realized there is a pcm table for atmospheric pressure. It reads the MAP sensor before the engine kicks over and marks this as ambient pressure. It is 97 kPa where I am and when logging the barometric sensor, [PID.2340], it remains at 97 kPa until I hit boost. Apparently the boost is pushing the MAP sensor right up to 104 kPa. Not a problem when using a MAF sensor but it adjusts the fueling. The PCM doesn't know it's boosted so the pressure must be the atmospheric pressure. It will rise to 104 kPa and stay there until shutdown.
Now the manifold kPa can bounce around all day below 97 kPa and the baro variable remains at 97. But hit 102 kPa manifold pressure in WOT once and the baro stays at 102 kPa.
So if your tuning a turbo with a 1bar map (using a MAF), only use data when the baro sensor, [PID.2340]>103.
This way the AFR will be off a bit at first, but will be spot on after the first spool up.
This anomaly was persistent for a while. Finally found the gremlin responsible.
The image below describes what I am posting up. This is just one instance I have a pic for. I've seen consistently the same effect. It almost appears a voltage issue but is just coincidental in that image.
Now I realized there is a pcm table for atmospheric pressure. It reads the MAP sensor before the engine kicks over and marks this as ambient pressure. It is 97 kPa where I am and when logging the barometric sensor, [PID.2340], it remains at 97 kPa until I hit boost. Apparently the boost is pushing the MAP sensor right up to 104 kPa. Not a problem when using a MAF sensor but it adjusts the fueling. The PCM doesn't know it's boosted so the pressure must be the atmospheric pressure. It will rise to 104 kPa and stay there until shutdown.
Now the manifold kPa can bounce around all day below 97 kPa and the baro variable remains at 97. But hit 102 kPa manifold pressure in WOT once and the baro stays at 102 kPa.
So if your tuning a turbo with a 1bar map (using a MAF), only use data when the baro sensor, [PID.2340]>103.
This way the AFR will be off a bit at first, but will be spot on after the first spool up.
This anomaly was persistent for a while. Finally found the gremlin responsible.
The image below describes what I am posting up. This is just one instance I have a pic for. I've seen consistently the same effect. It almost appears a voltage issue but is just coincidental in that image.
Comment