I read that HPT editor was going to have a function to auto populate the Inverse Torque tables when you changed the Torque tables. Is this true and is it already implemented? If so, how does it work?
I read that HPT editor was going to have a function to auto populate the Inverse Torque tables when you changed the Torque tables. Is this true and is it already implemented? If so, how does it work?
subb
2020 Mustang GT Daily driver
|Hellion Sleeper|10R80|Full weight, full exhaust, BABY seat in the back|
8.3@167mph
2014 Mustang GT
|Hellion TT|Powerglide|Ignite114|
6.87@200mph
Jordan Performance and Racing
It's one of many functions in the works.
How are you guys calculating torque and inverse torque if you're trying to update for new power levels? The main torque table makes sense but what are y'all doing to get the corresponding inverse tables updated?
2020 Mustang GT Daily driver
|Hellion Sleeper|10R80|Full weight, full exhaust, BABY seat in the back|
8.3@167mph
2014 Mustang GT
|Hellion TT|Powerglide|Ignite114|
6.87@200mph
Jordan Performance and Racing
This formula works to populate the Inverse table:
ITxTL/T=New IL
IT is Inverse Torque
TL is Torque Load
T is Torque
IL is Inverse Load
For example using a stock coyote Torque/Inverse OP Table
IT is 516.3, TL is 1.2 and T is 484.33
516.3 x 1.2 = 619.56/484.33=1.27
Excellent! I'm going to make a spreadsheet incorporating that. Thank you!
2020 Mustang GT Daily driver
|Hellion Sleeper|10R80|Full weight, full exhaust, BABY seat in the back|
8.3@167mph
2014 Mustang GT
|Hellion TT|Powerglide|Ignite114|
6.87@200mph
Jordan Performance and Racing
He sent it to me. Here you go.
Thank you txcharlie!
I did something very similar with the timing tables. The problem was they had negative numbers and zeros in them. My work around was to add 360, do the percentage difference formula(ratio), then subtract 360. It worked out really well. This way you don't loose negative values in your timing and you don't have to worry about the values you change from negative to positive and the out put values being really off. The number doesn't have to be 360 it just needs to be high enough to make all negatives positive before the ratio and make sure you subtract the same value you added. The torque tables don't have negatives or zeros in them so they don't need this. Just an FYI on how to use this for tables with negatives in them. I've attached a very rough spreadsheet here so you can take a look.
Very nice, thank you guys!
'17 Whipple'd S550
Too many other projects to list.....see my YouTube channel for more: https://www.youtube.com/channel/UCr7...-XfDG53sCh6tcw
Any updates on when the auto populate will be working in all strategies?
Does auto populate work for torque/inverse, in 3.0? If so, how does it work? HPT???
It has not been implemented yet.
Eric Brooks
HP Tuners, LLC
how about...............now?
Now? Lol better yet someone to explain how to calculate for a car that makes way more power than before........
I thought you just use a dyno to calculate torque at the flywheel, and add a bit more, for the torque table. Then use the math above to calculate the inverse.
Here is my post from thread. Just trying to make sure I get a definitive answer before I go and mess up something.
I have increased boost on my car and need to update the tables
Using the math in the link posted and my most recent dyno graph I think I understand how to update the tables correctly just want to make sure.
My understanding is under indicated engine torque (optimum power), lets say at 4000rpm ( just focusing on one cell at the moment as an example).
I would look at my dyno graph, plug in the torque number measured at 4000rpm into the indicates engine torque table, then using the math in the link posted above I would calculate the torque inverse table for 4000rpm.
Then under driver demand I would pretty much put what my car makes at each cell from 3-7000
2011 coyote btw.
Thanks.
Would it not be better to fine tune logging wheel torque error instead of dyno numbers? Dynos vary so much but if you're logging error from the ECU you're seeing what it actually expects vs is calculating for torque.