Resolved: PSI Boost issues with 2010 RA/ max upward correction not working
Resolved: PSI Boost issues with 2010 RA/ max upward correction not working
So, i noticed today a possible error in the PSI boost logic for the 2010 RA Roms (55590006) but it may actually be a logic error in how the boost error is calculated in general..
What i noticed is any time you are running in vacume the boost error is reported at - vacume reading so if you are running 20% tps at 6psi vacume and your boost target table is set to zero at that point your boost error is -6psi which causes the wgdc to ramp all the way to 100% even if the max upward correction is zero at that tps setting.....
log
map log was taken from
In the past i did not see this if the larger boost error table values were set to zero... so lets say the boost error table is set to zero above -2.0 psi the duty cycle would remain at zero... Obviously I can use this as a workaround but it would seem better to address the issue directly.... So, either the max upward correction cap does not work for this rom (or possibly in general), or the logic behind the wgdc correction routine is flawed and should not correct when map < baro or a combination of the two.
What i noticed is any time you are running in vacume the boost error is reported at - vacume reading so if you are running 20% tps at 6psi vacume and your boost target table is set to zero at that point your boost error is -6psi which causes the wgdc to ramp all the way to 100% even if the max upward correction is zero at that tps setting.....
log
map log was taken from
In the past i did not see this if the larger boost error table values were set to zero... so lets say the boost error table is set to zero above -2.0 psi the duty cycle would remain at zero... Obviously I can use this as a workaround but it would seem better to address the issue directly.... So, either the max upward correction cap does not work for this rom (or possibly in general), or the logic behind the wgdc correction routine is flawed and should not correct when map < baro or a combination of the two.
Last edited by Mad_SB; Sep 27, 2011 at 08:58 AM.
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
One possible suspect... the custom scale of your Target Boost Error Correction - the uppermost scaling cell, in fact.
Try changing it from "6.2" to "6.1". Internally, that will bring it back from a 9-bit 0x100 value to an 8-bit 0xff value.
See if that stops the crazy WGDC.
Rich
Try changing it from "6.2" to "6.1". Internally, that will bring it back from a 9-bit 0x100 value to an 8-bit 0xff value.
See if that stops the crazy WGDC.
Rich
One possible suspect... the custom scale of your Target Boost Error Correction - the uppermost scaling cell, in fact.
Try changing it from "6.2" to "6.1". Internally, that will bring it back from a 9-bit 0x100 value to an 8-bit 0xff value.
See if that stops the crazy WGDC.
Rich
Try changing it from "6.2" to "6.1". Internally, that will bring it back from a 9-bit 0x100 value to an 8-bit 0xff value.
See if that stops the crazy WGDC.
Rich
Just a note for anyone else that runs into this issue...
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
Hey, great! 
Yeah, I think the limits are:
Direct boost: -6.2 ... +6.1
Load boost: -20.0 ... +19.8
EcuFlash doesn't impose a "max" limit, when set. Well, the versions you and I have right now, anyway...
Rich
Yeah, I think the limits are:
Direct boost: -6.2 ... +6.1
Load boost: -20.0 ... +19.8
EcuFlash doesn't impose a "max" limit, when set. Well, the versions you and I have right now, anyway...
Rich
Thread
Thread Starter
Forum
Replies
Last Post
