psi based boost control
question: when the alt map is activated, it will be getting the "atmospheric boost" right? i mean i'm setting the ALT BTELs and it is set at psia8 instead of load. let me know. thanks!
No. When in PSI mode, it uses the same table with different scalings. You will need to add new tables to your definition for the psi based alt map table.
For the 2010 USDM evos, I use these:
* Notice that the addresses are the same as the normal Alt Load Boost tables.
For the 2010 USDM evos, I use these:
Code:
<table name="Alt Boost Target PSI Based #2 (Low Gear Range)" address="f0517" category="TephraXMOD V1" type="3D" swapxy="true" scaling="psia8"> <table name="Throttle" type="X Axis" address="6286a" elements="9" scaling="Throttle %"/> <table name="RPM" type="Y Axis" address="627e8" elements="18" scaling="RPM"/> </table> <table name="Alt Boost Target PSI Based #1A (High Gear Range)" address="f05c7" category="TephraXMOD V1" type="3D" swapxy="true" scaling="psia8"> <table name="Throttle" type="X Axis" address="6286a" elements="9" scaling="Throttle %"/> <table name="RPM" type="Y Axis" address="627e8" elements="18" scaling="RPM"/> </table> <table name="Alt Boost Target PSI Based #2 (Low Gear Range) (Omni4bar)" address="f0517" category="TephraXMOD V1" type="3D" swapxy="true" scaling="Omni4barpsia8"> <table name="Throttle" type="X Axis" address="6286a" elements="9" scaling="Throttle %"/> <table name="RPM" type="Y Axis" address="627e8" elements="18" scaling="RPM"/> </table> <table name="Alt Boost Target PSI Based #1A (High Gear Range) (Omni4bar)" address="f05c7" category="TephraXMOD V1" type="3D" swapxy="true" scaling="Omni4barpsia8"> <table name="Throttle" type="X Axis" address="6286a" elements="9" scaling="Throttle %"/> <table name="RPM" type="Y Axis" address="627e8" elements="18" scaling="RPM"/> </table>
No. When in PSI mode, it uses the same table with different scalings. You will need to add new tables to your definition for the psi based alt map table.
For the 2010 USDM evos, I use these:
* Notice that the addresses are the same as the normal Alt Load Boost tables.
For the 2010 USDM evos, I use these:
Code:
<table name="Alt Boost Target PSI Based #2 (Low Gear Range)" address="f0517" category="TephraXMOD V1" type="3D" swapxy="true" scaling="psia8">
<table name="Throttle" type="X Axis" address="6286a" elements="9" scaling="Throttle %"/>
<table name="RPM" type="Y Axis" address="627e8" elements="18" scaling="RPM"/>
</table>
<table name="Alt Boost Target PSI Based #1A (High Gear Range)" address="f05c7" category="TephraXMOD V1" type="3D" swapxy="true" scaling="psia8">
<table name="Throttle" type="X Axis" address="6286a" elements="9" scaling="Throttle %"/>
<table name="RPM" type="Y Axis" address="627e8" elements="18" scaling="RPM"/>
</table>
<table name="Alt Boost Target PSI Based #2 (Low Gear Range) (Omni4bar)" address="f0517" category="TephraXMOD V1" type="3D" swapxy="true" scaling="Omni4barpsia8">
<table name="Throttle" type="X Axis" address="6286a" elements="9" scaling="Throttle %"/>
<table name="RPM" type="Y Axis" address="627e8" elements="18" scaling="RPM"/>
</table>
<table name="Alt Boost Target PSI Based #1A (High Gear Range) (Omni4bar)" address="f05c7" category="TephraXMOD V1" type="3D" swapxy="true" scaling="Omni4barpsia8">
<table name="Throttle" type="X Axis" address="6286a" elements="9" scaling="Throttle %"/>
<table name="RPM" type="Y Axis" address="627e8" elements="18" scaling="RPM"/>
</table>
and how i active my psi based in evo x 2010
what value i need to put in variable for boost , and shlr, and boost error tables
i have 5557006 rom
thanks
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...
So, either the max upward correction cap does not work, or the logic behind the wgdc correction routine is flawed 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...
So, either the max upward correction cap does not work, or the logic behind the wgdc correction routine is flawed or a combination of the two.
Does it really matter tho what the boost control does in vacuum or at low boost? Your wastegate wont be able to open until you reach a minimum pressure that the WGA spring is rated at.
Rich pointed out the issue may be to do with the scale values of -6.2 and +6.2 on the boost error correction table, these are out of bounds and may be causing the strange behavior... more info latter on after i test.
Last edited by Mad_SB; Sep 28, 2011 at 07:59 AM.
Hey Tephra,
Is there a way to have the ROM reference a sensor value instead of a static set value within the ROM?
As in, can "Atmospheric Boost" reference the Baro sensor rather than the number we set in the ROM, so that the PSI based boost is more elevation independent?
Just a thought, I might have even asked this before but I can't remember.
Is there a way to have the ROM reference a sensor value instead of a static set value within the ROM?
As in, can "Atmospheric Boost" reference the Baro sensor rather than the number we set in the ROM, so that the PSI based boost is more elevation independent?
Just a thought, I might have even asked this before but I can't remember.




