Fuelcut decel overrun TPS base
Feb 11, 2014, 02:49 AM
#1
Fuelcut decel overrun TPS base
53040010:
52680022:
This is used when in fuelcut for overrun, higher number = more TPS, good for if you run a high compression motor that has lots of drag.. I guess this would be good for the racers as you should have much less engine braking when in decel.
I still gotta workout how the TPS is controlled when not in fuelcut..
good luck.
Code:
<table name="Fuelcut Decel TPS overrun base" category="Misc" address="5c9c8" type="2D" scaling="uint8"> <table name="RPM" address="60d6e" type="Y Axis" elements="16" scaling="RPM"/> </table>
Code:
<table name="Fuelcut Decel TPS overrun base" category="Misc" address="5c98c" type="2D" scaling="uint8"> <table name="RPM" address="60d32" type="Y Axis" elements="16" scaling="RPM"/> </table>
I still gotta workout how the TPS is controlled when not in fuelcut..
good luck.
Last edited by tephra; Feb 11, 2014 at 06:00 PM.
Feb 11, 2014, 05:39 PM
#2
so, more testing of this, it seems to work as expected..
once your in fuel cut decel increasing this table sets your TPS higher..
I only increased it by 1.5x (which resulted in 16% tps instead of 13%) and my engine braking is muchly reduced, to the point that my speed increases in 3rd on a medium downhill slope..
once your in fuel cut decel increasing this table sets your TPS higher..
I only increased it by 1.5x (which resulted in 16% tps instead of 13%) and my engine braking is muchly reduced, to the point that my speed increases in 3rd on a medium downhill slope..
Feb 12, 2014, 04:06 AM
#4
Is this what Golden has been modifying to help with decel that people have complained about?
My car sometimes has terrible decel or should I say lack there of which I've always thought is more of a safety issue. I am used to standalone engine systems which when setup correctly always have repeatable decel. One thing I've hoped for is a true fix for on stock ecu. Nothing worse then decel not really kicking in coming down a steep grade such as the bridge I cross every day for work and the car actually gaining a little speed.
My car sometimes has terrible decel or should I say lack there of which I've always thought is more of a safety issue. I am used to standalone engine systems which when setup correctly always have repeatable decel. One thing I've hoped for is a true fix for on stock ecu. Nothing worse then decel not really kicking in coming down a steep grade such as the bridge I cross every day for work and the car actually gaining a little speed.
Trending Topics
Feb 26, 2014, 02:55 PM
#8
Newbie
Join Date: Oct 2011
Location: Brazil
Posts: 18
Likes: 0
Received 0 Likes
on
0 Posts
<table name="Fuelcut Decel TPS Overrun Base" category="Misc" address="5ca6c" type="2D" scaling="uint8">
<table name="RPM" address="60f4e" type="Y Axis" elements="16" scaling="RPM"/>
</table>
Last edited by rpacheco; Feb 28, 2014 at 04:28 AM.
Feb 26, 2014, 08:04 PM
#10
Is this what Golden has been modifying to help with decel that people have complained about?
My car sometimes has terrible decel or should I say lack there of which I've always thought is more of a safety issue. I am used to standalone engine systems which when setup correctly always have repeatable decel. One thing I've hoped for is a true fix for on stock ecu. Nothing worse then decel not really kicking in coming down a steep grade such as the bridge I cross every day for work and the car actually gaining a little speed.
My car sometimes has terrible decel or should I say lack there of which I've always thought is more of a safety issue. I am used to standalone engine systems which when setup correctly always have repeatable decel. One thing I've hoped for is a true fix for on stock ecu. Nothing worse then decel not really kicking in coming down a steep grade such as the bridge I cross every day for work and the car actually gaining a little speed.
Mar 17, 2014, 06:33 AM
#15
58590004:
Code:
<table name="Fuelcut Decel TPS overrun base" category="Misc" address="5cc58" type="2D" scaling="uint8"> <table name="RPM" address="6175c" type="Y Axis" elements="16" scaling="RPM"/> </table>