Hi All,

As part of my "study" into the throttle routines, I have found out the correct scaling for the 3d boost maps (BTEL and Reactive Solenoid BWGDC):

If you stick this into your evo10base.xml and then change the "Throttle %" to this for these 6 maps you should get the right scaling:

<scaling name="Throttle_Main - Stored Minimum Throttle %" units="%" toexpr="(x+(90/4))*100/255" frexpr="x*255/100-(90/4)" format="%.1f" min="0" max="100" inc="2" storagetype="uint16" endian="big"/>

Its not a very nice name, but it means something

Now this isn't 100%, mainly because the "Stored Minimum Throttle" is always changing. On my car I have logged this as 90 or 91, which is why I have 90 in the formula above.

Once you have put the right scaling in you will see that the throttle maps actually range from 8.8% to 89% (which should roughly match your logging formula (as long as you use x/255*100)

This is also means you have extended range (particularily under 30% TPS):



This new scaling will hopefully work its way into ECUFlash - eventually

Cheers
D.

 

do you mean change the throttle % formula to this formula?

 

nah just copy the whole scaling - then change the scaling in the axis...

 

I guess I need more sleep tephra...

What does this do for us, in simple terms?

 

it just gives us some certainty about the X-Axis for the boost maps.

 

I assume this applies to both BTEL & BWGDC for both main and alt maps?

 

What about the Airflow Check tables and the Torque Limiter Tables?

If you change the Throttle % scale over to this one, it makes them go up to 99%.

 

You are adding this scaling, then changing each individual boost table from "throttle %" -> "Throttle_Main - Stored Minimum Throttle %". It shouldn't cause any changes to tables that you have not changed.

 

yeah i have another scaling for those maps...

 

^^^ I'm interested.

I'm one of the few that mess with air flow tables to see how it affects my load curve. It does make a distinct difference.

 

For the airflow tables:

evo10base.xml:

<scaling name="ThrottleMAINorSUBInvertedOpening %" units="%" toexpr="100*(x-26)/(204)" frexpr="(x+26)/100*(204)" format="%.1f" min="0" max="100" inc="0.5" storagetype="uint16" endian="big"/>

<table name="Airflow Check #1 - Error?" category="Limits" type="3D" swapxy="true" scaling="EngineTorque">
<table name="Throttle Main or SUB Inverted Opening" type="X Axis" elements="14" scaling="ThrottleMAINorSUBInvertedOpening %"/>
<table name="RPM" type="Y Axis" elements="17" scaling="RPM"/>
</table>

<table name="Airflow Check #2 - Hot/Interpolated" category="Limits" type="3D" swapxy="true" scaling="EngineTorque">
<table name="Throttle Main or SUB Inverted Opening" type="X Axis" elements="14" scaling="ThrottleMAINorSUBInvertedOpening %"/>
<table name="RPM" type="Y Axis" elements="17" scaling="RPM"/>
</table>

<table name="Airflow Check #3 - Cold/Interpolated" category="Limits" type="3D" swapxy="true" scaling="EngineTorque">
<table name="Throttle Main or SUB Inverted Opening" type="X Axis" elements="14" scaling="ThrottleMAINorSUBInvertedOpening %"/>
<table name="RPM" type="Y Axis" elements="17" scaling="RPM"/>
</table>

I actually want to talk to you about getting all the xml's standardised and given to colby for inclusion in the next release of ecuflash

 

Nice job. Seems that Mitsu has done some pretty wierd stuff with the throttle variables. Good to know that it is throttle % and not something else.

 

its because of the electronic throttle

a lot of the problem is that the ECU can never "guess" what the range of the throttle is

so after you shut the car down the ECU will do a MIN-MAX-MIN sweep of the throttle and record the min and max..

then it will apply those min/max's to a LOT of the throttle routines to come up with a proper range.

its taken me a LONG time to figure this stuff out but at least we have a better understanding of it now...

 

What is EngineTorque scaling?

 

oh its just x*3 - still working out that one 100%