electronic throttle
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
ok - here are some more tables which are in usual driving conditions make up the X-axis for the Throttle Map tables:
As you can see the max in the table is 429, so under normal driving conditions the X-Axis of the Throttle Maps wont go above 429 - hence I *think* if you smooth the throttle maps across you are limitting your max-throttle.
I am working out the X-Axis for these new tables as we speak.
Code:
<scaling name="ThrottleInput1" units="units" toexpr="x*3" frexpr="x/3" format="%.0f" min="0" max="510" inc="1" storagetype="uint8" endian="big"/>
<table name="2) Potential X-Axis Throttle Table 0x5936e (interpolated/cold)" category="Misc" type="3D" swapxy="true" scaling="ThrottleInput1" address="0x59375">
<table name="Unknown" type="X Axis" elements="17" scaling="Hex16" address="0x613e4"/>
<table name="RPM" type="Y Axis" elements="16" scaling="RPM" address="0x6135e"/>
</table>
<table name="2) Potential X-Axis Throttle Table 0x59486 (interpolated/hot)" category="Misc" type="3D" swapxy="true" scaling="ThrottleInput1" address="0x5948d">
<table name="Unknown" type="X Axis" elements="17" scaling="Hex16" address="0x613e4"/>
<table name="RPM" type="Y Axis" elements="16" scaling="RPM" address="0x6135e"/>
</table>
I am working out the X-Axis for these new tables as we speak.
here is a pic of the table:
apparently there is a blitz throttle controller for the X and it adjusts the speed at which the throttle valve opens. Is that what the other map could be for? Extreme mode on the blitz opens the valve 4x faster than economy mode.
http://www.nengun.com/blitz/throttle-controller
http://www.nengun.com/blitz/throttle-controller
I noticed this the other day when I specifically tested acceleration with the throttle pushed down at 30% and watched as boost fell off and throttle decreased as RPM's rose even though I didn't change the position of my foot. I'm not sure I'll extend the max values as high as you guys did but evening out the cruising range and widening the low RPM range somewhere between where it is and what cruising RPM's ends up being.
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
yeah its because at higher RPM's the X-Axis to the throttle maps actually drops (as you can see by my table I posted above, look at the 333 column, 429 -> 336)
I am not sure why Mitsu have done this...
I am not sure why Mitsu have done this...
.. actually you have a reply
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
52680015 -> 20:
The OUTPUT of these tables are used as the INPUT to the TPS3/4/5 tables...
Code:
<scaling name="ThrottleInput1" units="units" toexpr="x*3" frexpr="x/3" format="%.0f" min="0" max="510" inc="1" storagetype="uint8" endian="big"/>
<table name="2) Potential X-Axis Throttle Table 0x5936a (interpolated/cold)" category="Misc" type="3D" swapxy="true" scaling="ThrottleInput1" address="0x59371">
<table name="Unknown" type="X Axis" elements="17" scaling="Hex16" address="0x613a8"/>
<table name="RPM" type="Y Axis" elements="16" scaling="RPM" address="0x61322"/>
</table>
<table name="2) Potential X-Axis Throttle Table 0x59482 (interpolated/hot)" category="Misc" type="3D" swapxy="true" scaling="ThrottleInput1" address="0x59489">
<table name="Unknown" type="X Axis" elements="17" scaling="Hex16" address="0x613a8"/>
<table name="RPM" type="Y Axis" elements="16" scaling="RPM" address="0x61322"/>
</table>
