how-to: ECU-based direct boost control
I already have the system very well setup with PSI based boost. I did not zeroed out the upward correction because I use it to reduce taper at high RPMs. I also use it to get to target and use a low WGDC to avoid overshoot when step on it and when changiing gears in strong acceleration. So far it is working perfectly without zeroing the upward correction.
mrfred - I had a question about the boost limit.
Is it possible for you to make it so that boost limit is PSI dependent rather than load based? Also are there any intricacies to the way that the boost limit code works other than just seeing if current load > limit and has been for more than the boost delay timer is set for?
I have tried to use the boost limit but it does not work exactly how I always expect it to. It would be nice to have it operate in a very simple PSI based way.
Thanks
Is it possible for you to make it so that boost limit is PSI dependent rather than load based? Also are there any intricacies to the way that the boost limit code works other than just seeing if current load > limit and has been for more than the boost delay timer is set for?
I have tried to use the boost limit but it does not work exactly how I always expect it to. It would be nice to have it operate in a very simple PSI based way.
Thanks
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
KnockSumNuts
Thanks to all contributing to these tuning threads. This is one of the major reasons I switched from my aging WRX to my new/used evo9MR. I am a big reader and so far stealth and doing little posting. I can't thank mrfred and the others enough. Very cool stuff. Though my brain hurts at times.
I have done very basic tuning in the past on the suby and am totally into the information provided here. Its fundamentally different than the suby though, but I am slowly getting it.
I have completed the JPMMAP install and reflashes associated with that. I have NOT made any changes to maps (that I know of, it was a used car). The car seems strong, and doesn't make any odd noises engine wise.
In my first week of logging with the JDMMAP sensor for boost, I am getting weird KnockSum numbers. Really high, but listening to the car (windows up) there is no audible sign of knock or any hesitation that might come for timing being pulled or boost being pulled.
Do any of you have any experience with doing these mods on a 8859000015 ROM and getting weirdly high KnockSum results. So high that it seems a setting or scaling is accidentally way off. Numbers spiking into 60s.
Correction - Knock, which is actually spiked at 7, unrelated to JDMMAP install
M
I have done very basic tuning in the past on the suby and am totally into the information provided here. Its fundamentally different than the suby though, but I am slowly getting it.
I have completed the JPMMAP install and reflashes associated with that. I have NOT made any changes to maps (that I know of, it was a used car). The car seems strong, and doesn't make any odd noises engine wise.
In my first week of logging with the JDMMAP sensor for boost, I am getting weird KnockSum numbers. Really high, but listening to the car (windows up) there is no audible sign of knock or any hesitation that might come for timing being pulled or boost being pulled.
Do any of you have any experience with doing these mods on a 8859000015 ROM and getting weirdly high KnockSum results. So high that it seems a setting or scaling is accidentally way off. Numbers spiking into 60s.
Correction - Knock, which is actually spiked at 7, unrelated to JDMMAP install
M
Last edited by fireroasted; Aug 13, 2008 at 09:59 AM. Reason: knock unrelated to JDMMAP install
Yup, Thanks for the input. Don't know why that one time I didn't look at the xcel file right away. Can't see the forest for the trees thing I guess.
It goes to 4 then spikes to 7. So I guess its in line with the expected need to pull back some timing advance as the first step. Based on what I have read.
M
It goes to 4 then spikes to 7. So I guess its in line with the expected need to pull back some timing advance as the first step. Based on what I have read.
M
Double checking my work on some of this stuff, I don't seem to have added the code from the 3rd post to my evoscan file.
<DataListItem DataLog="Y" Color="" Display="Boost Error" LogReference="BoostError" RequestID="8A" Eval="0.0241*x-3.087" Unit="psi" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-5" GaugeMax="5" ChartMin="-5" ChartMax="5" ScalingFactor="1" Notes=""/>
<DataListItem DataLog="Y" Color="" Display="WGDC Correction" LogReference="WGDCCorr" RequestID="8B" Eval="0.5*x-64" Unit="WGDC%" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-50" GaugeMax="50" ChartMin="-50" ChartMax="50" ScalingFactor="1" Notes=""/>
Where in the file or the tags specifically should it be pasted? The ending tags are like this.
</Mode6>
</ecu>
</vehicle>
</EvoScanDataLogger>
Sorry for the newb'd question, but I am going through everything I learned again and again, and finding little questions.
Thx
M
<DataListItem DataLog="Y" Color="" Display="Boost Error" LogReference="BoostError" RequestID="8A" Eval="0.0241*x-3.087" Unit="psi" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-5" GaugeMax="5" ChartMin="-5" ChartMax="5" ScalingFactor="1" Notes=""/>
<DataListItem DataLog="Y" Color="" Display="WGDC Correction" LogReference="WGDCCorr" RequestID="8B" Eval="0.5*x-64" Unit="WGDC%" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-50" GaugeMax="50" ChartMin="-50" ChartMax="50" ScalingFactor="1" Notes=""/>
Where in the file or the tags specifically should it be pasted? The ending tags are like this.
</Mode6>
</ecu>
</vehicle>
</EvoScanDataLogger>
Sorry for the newb'd question, but I am going through everything I learned again and again, and finding little questions.
Thx
M
Any thoughts on the below log? I can't seem to figure out the error correction. I can bet the boost to hit 23, but it then fades to 17-18psi. Would like to hold closer to 20 or see what I can do when the error correction and such is dialed in.
THoughts?
THoughts?
Last edited by fixem2; Sep 11, 2008 at 10:19 PM.

You have error correction off so it's not affecting your boost at all. It's currently pure WGDC







