If I remember correctly the bias is a computation from other adders and if you zero them they won't compute. When I tried setting them to zero it didn't work for me. I'd look at altitude and octane retard. I think that's what they were called in $OD
If I remember correctly the bias is a computation from other adders and if you zero them they won't compute. When I tried setting them to zero it didn't work for me. I'd look at altitude and octane retard. I think that's what they were called in $OD
No need to re-invent the wheel. But we can make it better
I did some more playing with it and it seems to have something to do with turning off the EGR etc for Datalogging. When I run the normal tune with the same VE and Spark tables it seems to come out a lot closer to what the main spark table is supposed to be. I tried to set the EGR spark bias to 0 but that still did not seem to make much of a difference.Originally Posted by ralmo94
is this for tbi/tpi? if so have you verified your initial timing is set the same as what is in the calibration?
It's a TBI and yes, the initial timing is correct. It seems to have something to do with when I disable the EGR functionality to data log. I'm just not sure what setting is causing the timing to be off when the EGR is disabled.
how are you disabling egr?
I used the method laid out in the XDF file
Last edited by IamBrad; 09-26-2022 at 05:17 PM. Reason: correction
Posting Permissions
Reply With Quote
Bookmarks