Boost Spike
Well my experience from the Xede is that dropping boost by 1% doesn't even drop the boost. I was overboosting with my stock map also. I would change those percentages to about 92%, then take all the 100's and change those to about 96%. I would think that would drop you about 2 lbs of boost allong the spectrum. Thats what I did atleast and I am not overboosting again.
Evolved Member
iTrader: (20)
Joined: Mar 2003
Posts: 4,941
Likes: 0
From: Danville/Blackhawk, California
Originally posted by Jev3gs
Well my experience from the Xede is that dropping boost by 1% doesn't even drop the boost. I was overboosting with my stock map also. I would change those percentages to about 92%, then take all the 100's and change those to about 96%. I would think that would drop you about 2 lbs of boost allong the spectrum. Thats what I did atleast and I am not overboosting again.
Well my experience from the Xede is that dropping boost by 1% doesn't even drop the boost. I was overboosting with my stock map also. I would change those percentages to about 92%, then take all the 100's and change those to about 96%. I would think that would drop you about 2 lbs of boost allong the spectrum. Thats what I did atleast and I am not overboosting again.
A 1% change in duty cycle is pretty small. My recommedation is to make changes to boost in 5% increments first. Then make fine adjustments when you're close to where you want to be.Cheers,
shiv
Another call for datalogging, it seems. 
If you are at 5000RPMs and then floor it, does the boost spike?
I don't see how adjusting that table could possibly get rid of a boost spike. In order to get rid of a spike, a boost controller needs to keep track of boost as it rises, plot the slope, and then react to the increasing boost BEFORE boost hits its max level. This should be done at any RPM, and any load cell.
Actually, are those load cells in the vertical axis, or is that something else? Load cells don't really make sense for a boost controller since load is essentially just another way of expressing boost.

If you are at 5000RPMs and then floor it, does the boost spike?
I don't see how adjusting that table could possibly get rid of a boost spike. In order to get rid of a spike, a boost controller needs to keep track of boost as it rises, plot the slope, and then react to the increasing boost BEFORE boost hits its max level. This should be done at any RPM, and any load cell.
Actually, are those load cells in the vertical axis, or is that something else? Load cells don't really make sense for a boost controller since load is essentially just another way of expressing boost.
Originally posted by shiv@vishnu
I agree
A 1% change in duty cycle is pretty small. My recommedation is to make changes to boost in 5% increments first. Then make fine adjustments when you're close to where you want to be.
I agree
A 1% change in duty cycle is pretty small. My recommedation is to make changes to boost in 5% increments first. Then make fine adjustments when you're close to where you want to be.Thanks, will do that.
Originally posted by ShapeGSX
Another call for datalogging, it seems.
If you are at 5000RPMs and then floor it, does the boost spike?
I don't see how adjusting that table could possibly get rid of a boost spike. In order to get rid of a spike, a boost controller needs to keep track of boost as it rises, plot the slope, and then react to the increasing boost BEFORE boost hits its max level. This should be done at any RPM, and any load cell.
Actually, are those load cells in the vertical axis, or is that something else? Load cells don't really make sense for a boost controller since load is essentially just another way of expressing boost.
Another call for datalogging, it seems.

If you are at 5000RPMs and then floor it, does the boost spike?
I don't see how adjusting that table could possibly get rid of a boost spike. In order to get rid of a spike, a boost controller needs to keep track of boost as it rises, plot the slope, and then react to the increasing boost BEFORE boost hits its max level. This should be done at any RPM, and any load cell.
Actually, are those load cells in the vertical axis, or is that something else? Load cells don't really make sense for a boost controller since load is essentially just another way of expressing boost.
As far as your current ASSumption dont worry about it the Xede does a fine job of actually controlling and firing the FBC No BS here
Trending Topics
Originally posted by ShapeGSX
Another call for datalogging, it seems.
If you are at 5000RPMs and then floor it, does the boost spike?
Another call for datalogging, it seems.

If you are at 5000RPMs and then floor it, does the boost spike?
Sometimes it does but it really depends on what RPM you are at and what turbo, The factory tubo can hit REALLY high boost from 3500-48-4900 but after that you can set it to 100% and be fine, I think 4500 was the hardest to tune good and keep boost down in the higher gears becase going through 2nd from 3000rpm to redline is fine but dropping into 4th from 5th at 4500 and hitting the gas would cause the spike, I did add some additional RPM ranges to help this and now it works pretty damn good, I think with the xflash the boost spike will not be as big a deal because it just spikes for a second or 2 but enough to hit boost cut, if boost cut is raised it will be fine. If you are getting on it 1-4th I have 20psi all the way. Also in my old TT rx-7 boost was a real pain in the *** with the 2 turbos lol. The evo's turbo is MUCH easier to work with.
Last edited by Ryanmcd3; Jan 27, 2004 at 09:36 AM.
Originally posted by MP5
Geeze Shape do you ever quite? Datalogging is coming then we wont have to listen to you- well youll still prolly complain that the Xede doesnt come with a stick of bubblegum
As far as your current ASSumption dont worry about it the Xede does a fine job of actually controlling and firing the FBC No BS here
Geeze Shape do you ever quite? Datalogging is coming then we wont have to listen to you- well youll still prolly complain that the Xede doesnt come with a stick of bubblegum
As far as your current ASSumption dont worry about it the Xede does a fine job of actually controlling and firing the FBC No BS here
I'd ask you if you ever stop, MP5, but I already know what it takes to make you stop.
Welcome back.
I presume the numbers in the table are the duty cycle of the boost control solenoid, and load is the vertical axis. Less duty cycle = less boost.
Lowering the duty cycle at lower load points would help catch transient overboosting too.
Lowering the duty cycle at lower load points would help catch transient overboosting too.
Originally posted by Ron
I presume the numbers in the table are the duty cycle of the boost control solenoid, and load is the vertical axis. Less duty cycle = less boost.
Lowering the duty cycle at lower load points would help catch transient overboosting too.
I presume the numbers in the table are the duty cycle of the boost control solenoid, and load is the vertical axis. Less duty cycle = less boost.
Lowering the duty cycle at lower load points would help catch transient overboosting too.
Originally posted by Ron
Lowering the duty cycle at lower load points would help catch transient overboosting too.
Lowering the duty cycle at lower load points would help catch transient overboosting too.
Regards,
shiv
Evolved Member
iTrader: (20)
Joined: Mar 2003
Posts: 4,941
Likes: 0
From: Danville/Blackhawk, California
Originally posted by whiterexman
Shiv,
Just wondering....
Since I'm seeing overboost/spike at about 23.65psi (1.63bar) with the stcok map does it means that this is "acceptable" to you?
Shiv,
Just wondering....
Since I'm seeing overboost/spike at about 23.65psi (1.63bar) with the stcok map does it means that this is "acceptable" to you?
Cheers,
shiv
Originally posted by ShapeGSX
I know I can do that on my car with the airflow per rev (what the ECU uses for load) that my datalogger spits out using a multiplication factor.
I know I can do that on my car with the airflow per rev (what the ECU uses for load) that my datalogger spits out using a multiplication factor.
Which isn't to say that it's untuneable, quite the contrary, just that I'd take the "airflow" values themselves with a grain of salt.


