Sharp Accelerator drop -->> TPS maps
May 5, 2014, 04:14 AM
#1
Sharp Accelerator drop -->> TPS maps
Hi All,
Further to my previous thread (https://www.evolutionm.net/forums/ec...-tps-base.html) I have uncovered some more APP/TPS related maps:
53040010:
"TPS overrun - minimum APP change to activate" is the minimum amount of DE-APP (ie when your letting off the Accelerator Pedal)...
"TPS overrun base (pre decel fuelcut)" is the initial setting, ie as soon as the ECU detects the APP dropping by the above value (16) it sets the TPS to this value.
This value will then decay at either "10" or "1"
The two "decay rate decider" maps basically work out which decay rate to use, ie when the current decay'ing value is GREATER than these maps it uses 10, otherwise it uses 1
Example (bottom blue trace is APP, bottom red trace is the output from these maps):
I didn't notice this before - but this image also demonstrates the 1st gear thing, you see the first red line - quickly decays down to about 60, whereas the second red line quickly decays down to 40ish.. thats because the first red line is using the 1st gear set of maps - which has 61 in it for ~1200 rpm.. second redline is in 2nd gear and that map has about 45 in it for 2400rpm.. nice
How do you modify these maps?
Well I just multiplier the first couple the "TPS overrun base (pre decel fuelcut)" columns by 1.5 and it made a nice difference.. I think I will also change the "TPS overrun - minimum APP change to activate" from 16 to 8, so that it detects smaller APP changes...
Conceivable you could also increase the 2 decay decider maps so that it doesn't go into super fast decay mode straight away.. i will probably do this as well..
Regards
David
Further to my previous thread (https://www.evolutionm.net/forums/ec...-tps-base.html) I have uncovered some more APP/TPS related maps:
53040010:
Code:
<scaling name="x4_word" units="units" toexpr="x*4" frexpr="x/4" format="%.0f" min="0" max="510" inc="1" storagetype="uint16" endian="big"/> <table name="TPS overrun - minimum APP change to activate" category="Misc" address="548DC" type="1D" scaling="x4_word"/> <scaling name="x2_byte" units="units" toexpr="x*2" frexpr="x/2" format="%.0f" min="0" max="510" inc="1" storagetype="uint8" endian="big"/> <table name="TPS overrun base (pre decel fuelcut)" category="Misc" address="5fe39" type="3D" swapxy="true" scaling="x2_byte"> <table name="APP" address="629ee" type="X Axis" elements="8" scaling="uint16"/> <table name="RPM" address="629d4" type="Y Axis" elements="10" scaling="RPM"/> </table> <table name="TPS overrun base (pre decel fuelcut) ECT Multiplier" category="Misc" type="2D" level="2" scaling="Percent255" address="5fe8e"> <table name="ECT" address="61016" type="Y Axis" elements="8" scaling="TempC"/> </table> <table name="TPS overrun 5MT 2nd+ decay rate decider" category="Misc" address="5fe24" type="2D" scaling="uint16"> <table name="RPM" address="629c0" type="Y Axis" elements="7" scaling="RPM"/> </table> <table name="TPS overrun SST or 5MT 1st decay rate decider" category="Misc" address="5fe10" type="2D" scaling="uint16"> <table name="RPM" address="629c0" type="Y Axis" elements="7" scaling="RPM"/> </table>
"TPS overrun base (pre decel fuelcut)" is the initial setting, ie as soon as the ECU detects the APP dropping by the above value (16) it sets the TPS to this value.
This value will then decay at either "10" or "1"
The two "decay rate decider" maps basically work out which decay rate to use, ie when the current decay'ing value is GREATER than these maps it uses 10, otherwise it uses 1
Example (bottom blue trace is APP, bottom red trace is the output from these maps):
I didn't notice this before - but this image also demonstrates the 1st gear thing, you see the first red line - quickly decays down to about 60, whereas the second red line quickly decays down to 40ish.. thats because the first red line is using the 1st gear set of maps - which has 61 in it for ~1200 rpm.. second redline is in 2nd gear and that map has about 45 in it for 2400rpm.. nice
How do you modify these maps?
Well I just multiplier the first couple the "TPS overrun base (pre decel fuelcut)" columns by 1.5 and it made a nice difference.. I think I will also change the "TPS overrun - minimum APP change to activate" from 16 to 8, so that it detects smaller APP changes...
Conceivable you could also increase the 2 decay decider maps so that it doesn't go into super fast decay mode straight away.. i will probably do this as well..
Regards
David
Last edited by tephra; May 5, 2014 at 04:36 AM.
May 6, 2014, 07:45 PM
#4
Newbie
Join Date: Oct 2011
Location: Brazil
Posts: 18
Likes: 0
Received 0 Likes
on
0 Posts
Nice work again. Could you get the code for a SST rom so that I can replicate it? I was trying to identify these maps for my SST rom (57140001) and found out that a few of these maps have a different type of header structure so I had some difficulty in getting the scales right.
Cheers.
Cheers.
May 7, 2014, 04:55 PM
#5
Evolving Member
Join Date: May 2005
Location: Santa Monica, CA
Posts: 100
Likes: 0
Received 0 Likes
on
0 Posts
Very nice! I'm sure these maps are used not only for driveability (reducing jerkiness especially in low gears, reducing chance of driver feeling driveline lash) but also for emissions. A faster throttle close causes a more severe momentary rich condition which newer cars avoid at all costs because it severely affects emissions during the EPA drive cycles. Therefore adjusting these tables will probably affect emissions (very) slightly but the affect on actual gas mileage will be negligible.
I have a couple questions here.. First of all, I'm not sure I understand the "minimum APP change" to activate decel cut. Isn't decel cut determined by an APP % threshold? I'm trying to think how and why different negative TPS rates would affect when the ECU went into full decel fuel cut.
Also, the values you tried and liked (multiplying pre-decel cut by 1.5) would tend to make the car take longer to go into maximum decel rate (max closed throttle) correct? How did it actually affect the car? I tend to like to increase engine braking personally, so I've lowered the values in the TPS overrun base table you found a few weeks ago which seemed to help. I assume I'd be doing the same here, opposite from what you were doing.
And thanks as always
Beau
I have a couple questions here.. First of all, I'm not sure I understand the "minimum APP change" to activate decel cut. Isn't decel cut determined by an APP % threshold? I'm trying to think how and why different negative TPS rates would affect when the ECU went into full decel fuel cut.
Also, the values you tried and liked (multiplying pre-decel cut by 1.5) would tend to make the car take longer to go into maximum decel rate (max closed throttle) correct? How did it actually affect the car? I tend to like to increase engine braking personally, so I've lowered the values in the TPS overrun base table you found a few weeks ago which seemed to help. I assume I'd be doing the same here, opposite from what you were doing.
And thanks as always
Beau
May 9, 2014, 07:45 PM
#6
I'm trying to dig out the addresses for these tables but this one is proving a little difficult since ROM information has changed and I can't seem to find matches. If anyone has anything please post as any little bit helps. The 5689 and 5958 series I haven't really found anything yet and 5268 I have mostly done.
I believe the below is correct for 55570006 but as always please be cautious.
I believe the below is correct for 55570006 but as always please be cautious.
Code:
<scaling name="x2_byte" units="units" toexpr="x*2" frexpr="x/2" format="%.0f" min="0" max="510" inc="1" storagetype="uint8" endian="big"/> <scaling name="x4_word" units="units" toexpr="x*4" frexpr="x/4" format="%.0f" min="0" max="510" inc="1" storagetype="uint16" endian="big"/> <table name="TPS overrun - minimum APP change to activate" category="Misc" address="54912" type="1D" scaling="x4_word"/> <table name="TPS overrun base (pre decel fuelcut)" category="Misc" address="5fee7" type="3D" swapxy="true" scaling="x2_byte"> <table name="APP" address="62c0a" type="X Axis" elements="8" scaling="uint16"/> <table name="RPM" address="62bf0" type="Y Axis" elements="10" scaling="RPM"/> </table> <table name="TPS overrun base (pre decel fuelcut) ECT Multiplier" category="Misc" type="2D" level="2" scaling="Percent255" address="5ff3c"> <table name="ECT" address="6120a" type="Y Axis" elements="8" scaling="Temp"/> </table> <table name="TPS overrun 5MT 2nd+ decay rate decider" category="Misc" address="5fed2" type="2D" scaling="uint16"> <table name="RPM" address="62bdc" type="Y Axis" elements="7" scaling="RPM"/> </table> <table name="TPS overrun SST or 5MT 1st decay rate decider" category="Misc" address="5febe" type="2D" scaling="uint16"> <table name="RPM" address="62bdc" type="Y Axis" elements="7" scaling="RPM"/> </table>
May 12, 2014, 10:48 AM
#7
Evolving Member
iTrader: (1)
Join Date: Mar 2010
Location: PA
Posts: 304
Likes: 0
Received 0 Likes
on
0 Posts
I'm trying to dig out the addresses for these tables but this one is proving a little difficult since ROM information has changed and I can't seem to find matches. If anyone has anything please post as any little bit helps. The 5689 and 5958 series I haven't really found anything yet and 5268 I have mostly done.
I believe the below is correct for 55570006 but as always please be cautious.
I believe the below is correct for 55570006 but as always please be cautious.
Code:
<scaling name="x2_byte" units="units" toexpr="x*2" frexpr="x/2" format="%.0f" min="0" max="510" inc="1" storagetype="uint8" endian="big"/> <scaling name="x4_word" units="units" toexpr="x*4" frexpr="x/4" format="%.0f" min="0" max="510" inc="1" storagetype="uint16" endian="big"/> <table name="TPS overrun - minimum APP change to activate" category="Misc" address="54912" type="1D" scaling="x4_word"/> <table name="TPS overrun base (pre decel fuelcut)" category="Misc" address="5fee7" type="3D" swapxy="true" scaling="x2_byte"> <table name="APP" address="62c0a" type="X Axis" elements="8" scaling="uint16"/> <table name="RPM" address="62bf0" type="Y Axis" elements="10" scaling="RPM"/> </table> <table name="TPS overrun base (pre decel fuelcut) ECT Multiplier" category="Misc" type="2D" level="2" scaling="Percent255" address="5ff3c"> <table name="ECT" address="6120a" type="Y Axis" elements="8" scaling="Temp"/> </table> <table name="TPS overrun 5MT 2nd+ decay rate decider" category="Misc" address="5fed2" type="2D" scaling="uint16"> <table name="RPM" address="62bdc" type="Y Axis" elements="7" scaling="RPM"/> </table> <table name="TPS overrun SST or 5MT 1st decay rate decider" category="Misc" address="5febe" type="2D" scaling="uint16"> <table name="RPM" address="62bdc" type="Y Axis" elements="7" scaling="RPM"/> </table>
I just need to take some time and learn how to find maps that are defined for one ROM and find it in another ROM.
Trending Topics
May 12, 2014, 11:41 AM
#8
I cannot find these tables in the 2011 ROM's and above. I've looked in 56890007, 56890009, 56890013, 58010005, and 59580004.
Anyone that has disassembled the ROM's care to take a look?
Below are the 2008 ROM's.
52680015:
52680024:
Anyone that has disassembled the ROM's care to take a look?
Below are the 2008 ROM's.
52680015:
Code:
<scaling name="x2_byte" units="units" toexpr="x*2" frexpr="x/2" format="%.0f" min="0" max="510" inc="1" storagetype="uint8" endian="big"/> <scaling name="x4_word" units="units" toexpr="x*4" frexpr="x/4" format="%.0f" min="0" max="510" inc="1" storagetype="uint16" endian="big"/> <table name="TPS overrun - minimum APP change to activate" category="Misc" address="548ce" type="1D" scaling="x4_word"/> <table name="TPS overrun base (pre decel fuelcut)" category="Misc" address="5fdfd" type="3D" swapxy="true" scaling="x2_byte"> <table name="APP" address="629b0" type="X Axis" elements="8" scaling="uint16"/> <table name="RPM" address="62996" type="Y Axis" elements="10" scaling="RPM"/> </table> <table name="TPS overrun base (pre decel fuelcut) ECT Multiplier" category="Misc" type="2D" level="2" scaling="Percent255" address="5fe52"> <table name="ECT" address="60fda" type="Y Axis" elements="8" scaling="Temp"/> </table> <table name="TPS overrun 5MT 2nd+ decay rate decider" category="Misc" address="5fde8" type="2D" scaling="uint16"> <table name="RPM" address="62982" type="Y Axis" elements="7" scaling="RPM"/> </table> <table name="TPS overrun SST or 5MT 1st decay rate decider" category="Misc" address="5fdd4" type="2D" scaling="uint16"> <table name="RPM" address="62982" type="Y Axis" elements="7" scaling="RPM"/> </table>
Code:
<scaling name="x2_byte" units="units" toexpr="x*2" frexpr="x/2" format="%.0f" min="0" max="510" inc="1" storagetype="uint8" endian="big"/> <scaling name="x4_word" units="units" toexpr="x*4" frexpr="x/4" format="%.0f" min="0" max="510" inc="1" storagetype="uint16" endian="big"/> <table name="TPS overrun - minimum APP change to activate" category="Misc" address="548e0" type="1D" scaling="x4_word"/> <table name="TPS overrun base (pre decel fuelcut)" category="Misc" address="5fdfd" type="3D" swapxy="true" scaling="x2_byte"> <table name="APP" address="629b0" type="X Axis" elements="8" scaling="uint16"/> <table name="RPM" address="62996" type="Y Axis" elements="10" scaling="RPM"/> </table> <table name="TPS overrun base (pre decel fuelcut) ECT Multiplier" category="Misc" type="2D" level="2" scaling="Percent255" address="5fe52"> <table name="ECT" address="60fda" type="Y Axis" elements="8" scaling="Temp"/> </table> <table name="TPS overrun 5MT 2nd+ decay rate decider" category="Misc" address="5fde8" type="2D" scaling="uint16"> <table name="RPM" address="62982" type="Y Axis" elements="7" scaling="RPM"/> </table> <table name="TPS overrun SST or 5MT 1st decay rate decider" category="Misc" address="5fdd4" type="2D" scaling="uint16"> <table name="RPM" address="62982" type="Y Axis" elements="7" scaling="RPM"/> </table>
May 15, 2014, 01:38 PM
#10
Newbie
Join Date: Oct 2011
Location: Brazil
Posts: 18
Likes: 0
Received 0 Likes
on
0 Posts
I guess these are the tables for 59590004. The last 3 tables use a different type of header structure so it's harder to find them (not to mention the scales). So I would ask someone else to validate them.
These tables are also higher resolution tables compared to 53040010, as you can see from the attached picture, with somewhat different values too.
59590004
These tables are also higher resolution tables compared to 53040010, as you can see from the attached picture, with somewhat different values too.
59590004
Code:
<scaling name="x4_word" units="units" toexpr="x*4" frexpr="x/4" format="%.0f" min="0" max="510" inc="1" storagetype="uint16" endian="big"/> <scaling name="APP614" units="%" toexpr="100*x/614" frexpr="x/100*614" format="%.1f" min="0" max="100" inc="0.5" storagetype="uint16" endian="big"/> <table name="TPS Overrun - Minimum APP Change to Activate" category="TPS" address="54924" type="1D" scaling="x4_word"/> <table name="TPS Overrun Base (Pre Decel Fuelcut) ECT Multiplier" category="TPS" address="60260" type="2D" scaling="Percent255"> <table name="Coolant Temp" address="6189a" type="Y Axis" elements="8" scaling="Temp"/> </table> <table name="TPS Overrun Base (Pre Decel Fuelcut)" category="TPS" address="60144" type="3D" swapxy="true" scaling="uint16"> <table name="APP" address="633c8" type="X Axis" elements="10" scaling="APP614"/> <table name="RPM" address="633aa" type="Y Axis" elements="14" scaling="RPM"/> </table> <table name="TPS Overrun 1st Decay Rate Decider" category="TPS" address="60100" type="2D" scaling="uint16"> <table name="RPM" address="633aa" type="Y Axis" elements="14" scaling="RPM"/> </table> <table name="TPS Overrun 2nd+ Decay Rate Decider" category="TPS" address="60120" type="2D" scaling="uint16"> <table name="RPM" address="633aa" type="Y Axis" elements="14" scaling="RPM"/> </table>
May 16, 2014, 09:14 AM
#11
I guess these are the tables for 59590004. The last 3 tables use a different type of header structure so it's harder to find them (not to mention the scales). So I would ask someone else to validate them.
These tables are also higher resolution tables compared to 53040010, as you can see from the attached picture, with somewhat different values too.
59590004
These tables are also higher resolution tables compared to 53040010, as you can see from the attached picture, with somewhat different values too.
59590004
Code:
<scaling name="x4_word" units="units" toexpr="x*4" frexpr="x/4" format="%.0f" min="0" max="510" inc="1" storagetype="uint16" endian="big"/> <scaling name="APP614" units="%" toexpr="100*x/614" frexpr="x/100*614" format="%.1f" min="0" max="100" inc="0.5" storagetype="uint16" endian="big"/> <table name="TPS Overrun - Minimum APP Change to Activate" category="TPS" address="54924" type="1D" scaling="x4_word"/> <table name="TPS Overrun Base (Pre Decel Fuelcut) ECT Multiplier" category="TPS" address="60260" type="2D" scaling="Percent255"> <table name="Coolant Temp" address="6189a" type="Y Axis" elements="8" scaling="Temp"/> </table> <table name="TPS Overrun Base (Pre Decel Fuelcut)" category="TPS" address="60144" type="3D" swapxy="true" scaling="uint16"> <table name="APP" address="633c8" type="X Axis" elements="10" scaling="APP614"/> <table name="RPM" address="633aa" type="Y Axis" elements="14" scaling="RPM"/> </table> <table name="TPS Overrun 1st Decay Rate Decider" category="TPS" address="60100" type="2D" scaling="uint16"> <table name="RPM" address="633aa" type="Y Axis" elements="14" scaling="RPM"/> </table> <table name="TPS Overrun 2nd+ Decay Rate Decider" category="TPS" address="60120" type="2D" scaling="uint16"> <table name="RPM" address="633aa" type="Y Axis" elements="14" scaling="RPM"/> </table>
Attached is what my 5958 based ROM using the 5959 addresses which I presume would match up.
May 19, 2014, 12:59 PM
#13
Evolving Member
Join Date: May 2005
Location: Santa Monica, CA
Posts: 100
Likes: 0
Received 0 Likes
on
0 Posts
I went ahead and tried the 59590004 stuff posted by rpacheco and my car hasn't exploded yet and the tables do seem to work as described! I'm on TephraXMod V2. The descriptions of a few of these tables and their functions are still a bit unclear however.
May 20, 2014, 06:22 AM
#14
Newbie
Join Date: Oct 2011
Location: Brazil
Posts: 18
Likes: 0
Received 0 Likes
on
0 Posts
I've also tested these tables for my 2011 MR and it works as described too. Table "TPS Overrun 2nd+ Decay Rate Decider" seems to work too. Car is smoother now in low load/rpm liftoffs.
Jun 15, 2014, 06:16 AM
#15
Newbie
Join Date: Oct 2008
Location: Japan
Posts: 7
Likes: 0
Received 0 Likes
on
0 Posts
52360018 (2008 jdm 5mt)
Found in 52360018 (2008 JDM 5MT), thanks.
There is not too much about themselves information about "TPS overrun - minimum APP change to activate".
52680018 USDM : 16
52360018 JDM : 12
There is not too much about themselves information about "TPS overrun - minimum APP change to activate".
52680018 USDM : 16
52360018 JDM : 12
Code:
<scaling name="x2_byte" units="units" toexpr="x*2" frexpr="x/2" format="%.0f" min="0" max="510" inc="1" storagetype="uint8" endian="big"/> <scaling name="x4_word" units="units" toexpr="x*4" frexpr="x/4" format="%.0f" min="0" max="510" inc="1" storagetype="uint16" endian="big"/> <table name="TPS overrun - minimum APP change to activate" category="Misc" address="548d2" type="1D" scaling="x4_word"/> <table name="TPS overrun base (pre decel fuelcut)" category="Misc" address="5fe01" type="3D" swapxy="true" scaling="x2_byte"> <table name="APP" address="629b6" type="X Axis" elements="8" scaling="uint16"/> <table name="RPM" address="6299c" type="Y Axis" elements="10" scaling="RPM"/> </table> <table name="TPS overrun base (pre decel fuelcut) ECT Multiplier" category="Misc" address="5fe56" type="2D" level="2" scaling="Percent255"> <table name="ECT" address="60fde" type="Y Axis" elements="8" scaling="Temp"/> </table> <table name="TPS overrun 5MT 2nd+ decay rate decider" category="Misc" address="5fdec" type="2D" scaling="uint16"> <table name="RPM" address="62988" type="Y Axis" elements="7" scaling="RPM"/> </table> <table name="TPS overrun SST or 5MT 1st decay rate decider" category="Misc" address="5fdd8" type="2D" scaling="uint16"> <table name="RPM" address="62988" type="Y Axis" elements="7" scaling="RPM"/> </table>