mrfred

iTrader: (50)

The RPM/MPH value for each gear is highlighted in yellow. Say for instance that you want to use one set of boost control maps for 1st and 2nd gear and the other set of boost control maps for 3rd gear +. RPM/MPH is about 120 for 2nd gear and is about 90 for third gear. Set the crossover point to anywhere between these values, preferably in the midpoint, say about 105.

Yeah, I was thinking last night after I signed off that you might have erased this stuff. As razorlab said, I'm not sure how many people will use it. I'm kinda thinking that I will set up different boost control maps for 5th and 6th gear. Or maybe I'll do what razorlab said and set 1st/2nd for more boost for entertainment.

gear head

iTrader: (3)

Nice find.....this may come in handy.

dan l

iTrader: (3)

Wow mrfred, this is amazing. Tire spin was becoming a problem in first gear and even second on colder damp days, this is really going to help a lot on the street AND at the track. I can now set up friends cars and really limit how much the drivers emotions mess with clean passes. Just line it up, drop the clutch, and flat shift down the track.

SeanV

Wow excellent find

What changes, if any needs to be done to the scalings etc, for those of us who use kmh?

Thx for the great work MrFred.

mrfred

iTrader: (50)

In the scaling definition, 22.6 -> 37.7.

Jorge T

iTrader: (18)

I could not change the 2900 value unless i changed frexpr="22.6/x" to 22.6*x

<scaling name="RPMPerMPH" units="RPM/MPH" toexpr="x/22.6" frexpr="22.6/x" format="%.0f" min="0" max="3000" inc="5" storagetype="uint16" endian="big"/>

funks

iTrader: (4)

are the values the boost control duty cycle?

for example, on the 2006 EVO IX GSR/RS section

5th gear by 7500 rpm has a value of 161.1.

Is 161.1 the boost control solenoid duty cycle?

Jorge T

iTrader: (18)

After I changed the rpm/Mph crossover to 105

"Boost Control Limiting Speed". changed to on=18 off=138 from on/off 510

you think these values are a range or completely unrelated?

Charlie_B

iTrader: (1)

Is there any chance 96530006 can get some love? It would be fun to play with it this winter in the snow.

logic

iTrader: (2)

As I said above, it's the same as the third set of ROM IDs that mrfred quoted (ie. 94170008, or address 2204).

For anyone looking for this: the scaling is the same for everyone, the table address is the address of your existing "Boost Control Limiting Vehicle Speed" table.

Charlie_B

iTrader: (1)

MR Turco

iTrader: (16)

This is sick!!! Great find mrfred! I would love to have some control over 1st and 2nd. It annoying only hitting like 21/22 psi when i want 26

MR Turco

iTrader: (16)

So do we know what BWGDC/BDEL #2 and 4 are used?

Jack_of_Trades

iTrader: (17)

This is awesome. I'd say its especially useful for people running the load targeting rather than the JDM map and PSI targeting. I know my car hits totally different boost levels in 4th than it does with third since the load values change and the ECU tries to hit my taget load values in my BDEL table. So there were 4 BDEL and BWGDC tables originally right? So now only 2 of them are proven to do anything?? Sorry, trying to catch up here.

mrfred

iTrader: (50)

Yep, that was an error on my part. Wasn't paying attention. I fixed the first post.


Only the values highlighted in yellow are relevant. The other items are all vehicle speed based on RPM and gear selection.


Hmm. Did you not read the entire first post? Boost Control Limiting Speed is an incorrect interpretation of the ROM code. RPM/MPH crossover point is the correct interpretation. The Boost Control Limiting Speed entry in the ECUFlash xml files should be deleted because its wrong.


Your Avatar says you have an Evo IX, but it sounds as if you are asking about an Evo 8. Either way, there are only two sets of tables that are used. For the Evo 9, its set #1 and #3. #2 is never called by the code. For Evo 8s, I'm not sure which two of the four tables gets called because I've never bothered to go through the boost control code in detail on an Evo 8. tephra might be able to answer, but otherwise, I recommend figuring it out by trial and error.