Notices
Evo X Engine Management / Tuning Forums Discuss the major engine management systems.

psi based boost control

Old Jun 12, 2011 | 09:45 AM
  #121  
tonyboy's Avatar
Evolving Member
iTrader: (4)
 
Joined: Feb 2008
Posts: 408
Likes: 0
From: Fort Worth TX
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!
Reply
Old Jun 12, 2011 | 01:50 PM
  #122  
Golden's Avatar
Evolved Member
iTrader: (1)
 
Joined: Nov 2009
Posts: 1,456
Likes: 0
From: Omaha, NE
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:
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>
* Notice that the addresses are the same as the normal Alt Load Boost tables.
Reply
Old Jun 13, 2011 | 12:48 AM
  #123  
tonyboy's Avatar
Evolving Member
iTrader: (4)
 
Joined: Feb 2008
Posts: 408
Likes: 0
From: Fort Worth TX
cool thanks for clarifying it out!
Reply
Old Jul 11, 2011 | 10:18 AM
  #124  
mitsevolution's Avatar
Newbie
 
Joined: May 2011
Posts: 22
Likes: 0
From: canada
Originally Posted by Golden
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:
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>
* Notice that the addresses are the same as the normal Alt Load Boost tables.
so we need to add table if we want to use psi based,

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
Reply
Old Jul 11, 2011 | 01:26 PM
  #125  
Golden's Avatar
Evolved Member
iTrader: (1)
 
Joined: Nov 2009
Posts: 1,456
Likes: 0
From: Omaha, NE
Simply download a definition from my site. It's all in there.
Reply
Old Sep 27, 2011 | 08:54 AM
  #126  
Mad_SB's Avatar
Evolved Member
iTrader: (8)
 
Joined: Apr 2003
Posts: 2,138
Likes: 0
From: Georgia
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
Name:  boosterror_logic.jpg
Views: 0
Size:  148.5 KB

map log was taken from
Name:  boosterror_map.jpg
Views: 0
Size:  239.2 KB

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.
Reply
Old Sep 27, 2011 | 03:09 PM
  #127  
Golden's Avatar
Evolved Member
iTrader: (1)
 
Joined: Nov 2009
Posts: 1,456
Likes: 0
From: Omaha, NE
Looks like you logged APP, not TPS.

But still, 20% is low.

Last edited by Golden; Sep 27, 2011 at 03:14 PM.
Reply
Old Sep 28, 2011 | 03:41 AM
  #128  
Mad_SB's Avatar
Evolved Member
iTrader: (8)
 
Joined: Apr 2003
Posts: 2,138
Likes: 0
From: Georgia
Originally Posted by Golden
Looks like you logged APP, not TPS.

But still, 20% is low.
Yup app, but you can still see the duty cycle shooting up to 100% with my foot off the gas completely.... while the max upward correction table is zero up to 75% throttle...
Reply
Old Sep 28, 2011 | 05:00 AM
  #129  
rrkpitt15's Avatar
Evolving Member
iTrader: (1)
 
Joined: Mar 2010
Posts: 304
Likes: 0
From: PA
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.
Reply
Old Sep 28, 2011 | 07:50 AM
  #130  
Mad_SB's Avatar
Evolved Member
iTrader: (8)
 
Joined: Apr 2003
Posts: 2,138
Likes: 0
From: Georgia
Originally Posted by rrkpitt15
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.
I'll put it this way... with error correction off that duty cycle map was getting me a peak of 22 - 23 psi... with error correction on and duty cycle going to 100% BEFORE i ever went wot... I was spiking 28 - 29psi.

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.
Reply
Old Oct 14, 2011 | 10:53 PM
  #131  
xPRimNT's Avatar
Evolved Member
iTrader: (4)
 
Joined: Feb 2008
Posts: 610
Likes: 0
From: Edmonton, Alberta
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.
Reply
Old Oct 14, 2011 | 11:01 PM
  #132  
tephra's Avatar
Thread Starter
EvoM Guru
15 Year Member
iTrader: (6)
 
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
Yeh it's been in my mind for a while now...

it would require a small coding change - maybe I will incorporate it into V2!
Reply
Old Oct 15, 2011 | 08:02 AM
  #133  
xPRimNT's Avatar
Evolved Member
iTrader: (4)
 
Joined: Feb 2008
Posts: 610
Likes: 0
From: Edmonton, Alberta
Originally Posted by tephra
Yeh it's been in my mind for a while now...

it would require a small coding change - maybe I will incorporate it into V2!


That would be excellent!

I don't know if anyone has told you lately, but you're a genius. Thanks for all your work!
Reply
Old Oct 16, 2011 | 07:56 AM
  #134  
itzwolf's Avatar
Evolved Member
20 Year Member
iTrader: (9)
 
Joined: Mar 2005
Posts: 1,193
Likes: 2
From: Florida
Originally Posted by tephra
Yeh it's been in my mind for a while now...

it would require a small coding change - maybe I will incorporate it into V2!
This has win written all over it!
Reply
Old Oct 29, 2011 | 05:02 PM
  #135  
SiliconTek's Avatar
Evolved Member
iTrader: (3)
 
Joined: May 2009
Posts: 501
Likes: 0
From: Autocrossing Somewhere
I am bored so I thought I would give this a try. Do you have to define the OBTR variables and tables as well for this to work? I couldn't find any info on those.
Reply

Thread Tools
Search this Thread

All times are GMT -7. The time now is 04:42 AM.