Many tables in Pro Racer use TP as one of the axis and I wanted to post this here to save anyone new to Pro Racer and LiveLink a LOT of time.
LiveLink from SCT allows you to datalog your car while it is running, and two of the PID's that are available for logging relate to Throttle Position. They are called TP_ABSOLUTE and TP_RELATIVE.
I did some basic testing when I started using Pro Racer and incorrectly assumed that the TP that was referenced in these tables was TP_ABSOLUTE. This is wrong, and I have since re-tested and confirmed that TP_RELATIVE is the value used in Advantage III tuning tables. It turns out that TP_RELATIVE is a "learned" value based on TP_ABSOLUTE.
My shift schedule and TC lock posts have been updated to refer to TP_RELATIVE instead of TP_ABSOLUTE.
I found this old post by mach1_cal_man on the SCTFLASH forum from June 2007:
So how do the two compare to each other? I took about 60 minutes' worth of datalogging in mixed city/highway driving and compared the average of TP_RELATIVE to different TP_ABSOLUTE values:You typically use tp_rel in Ford-speak. This is the absolute TP value - ratch. Ratch is the learned offset of the closed throttle body which varies a bit over time and car-to-car, but the differences are small. The strategy uses tp_rel for most throttle position related functions and maps.
I love looking at data like this almost as much as RacerX likes to dremel stuff!!! The leftmost column shows how many lines in the datalog had the corresponding TP_ABSOLUTE (+/- 25). The rightmost column shows the AVERAGE of the TP_RELATIVE data for the corresponding TP_ABSOLUTE (+/- 25). As you can see, most of the time driving is spent with a TP_RELATIVE under 100. This is VERY important to consider when building out your TP-related tables!
My next step was to try to define "scenarios" for different TP_RELATIVE positions. After looking through several logs and taking notes, I have summarized the following for my Marauder:
(other cars may vary, as TP_RELATIVE values are learned by the ECU)
NOTE - the highest TP_RELATIVE I saw in my logs was 750. This is an important observation as many scalars in Advantage III involve WOT and you need to know what numbers will actually apply. Some of these settings come pre-set at 900, which is obviously too high!
So what have we accomplished with this scenario breakdown? Because Shift Schedules and TC Lockup schedules are TP-based, you enjoy very good control over when these events occur. Following are some examples.
Continued on Post 2...