# Throttle maps, pedal maps & drivability

> With drive-by-wire the pedal is a torque request, not a throttle cable. The pedal map shapes how predictable torque is at small openings — which decides how hard the driver can lean on the rear tyres on exit.

Area: Engine & Hybrid · Starting level: L1 Foundation · Updated 2026-11-16
Source page: https://race-engineer-academy.vercel.app/lesson/engine-throttle-pedal-maps

## L1 · Foundation

In almost every modern racing car the throttle pedal is a sensor. The ECU reads pedal position and, through a **pedal map**, decides what throttle-blade angle (or what engine torque) to deliver. The driver does not feel the engine directly; they feel the map.

Why maps exist: a throttle butterfly is extremely non-linear. At low rpm, the first 15–20 % of blade angle can already produce 60–80 % of the available torque, while the last 50 % adds almost nothing. A 1:1 pedal-to-blade relation would make the car "binary" on corner exit: tiny pedal movements, large torque steps, rear tyres overwhelmed.

A good pedal map makes **wheel torque roughly linear with pedal travel** — or deliberately progressive at small openings — so the driver can meter torque precisely at the point where the rear tyres are combined-loaded (lateral + longitudinal).

Typical options on a GT or prototype steering wheel:
- **Dry / race map** – close to linear torque vs pedal.
- **Wet map** – softer initial response, sometimes reduced peak torque in low gears.
- **Fuel-save / lean maps** – less fuel per stroke, sometimes lower torque.
- **Qualifying / push maps** where permitted.

Key vocabulary:
- **Pickup / tip-in** – the moment of going from 0 to partial throttle. A snappy pickup unsettles the car mid-corner.
- **Overrun / engine braking** – the torque when the pedal is released. Too much braking torque can lock the rear inside wheel on entry; too little makes the car feel like it "runs on".
- **Throttle lag** – delay between pedal and torque (turbo spool, manifold filling, DBW motor speed).

When a driver says "the car is snappy on power" the cause may be the chassis — or the first 10 % of the pedal map. Always check the map before you change the rear end.

## L2 · Practitioner

**What to look at in data.** Plot pedal position (APS) against throttle position (TPS) or engine torque request, coloured by rpm or gear. You should be able to read the map back from the car. Then look at corner exits:

- **Pedal trace shape**: a hesitant "staircase" or repeated small lifts during pick-up (the classic "pickup" complaint) often means the torque step at small openings is too big for the grip available.
- **Engine torque vs pedal**: in turbo engines the actual torque lags the request by 100–300 ms at low rpm; the driver compensates by over-pressing, then gets a surge. A boost-anticipating or more progressive map at low rpm helps.
- **Driveline lash**: the transition from overrun (negative torque) to drive (positive torque) passes through zero; backlash in gears, diff and driveshafts produces a "clunk" and a yaw kick. Maps often include a **tip-in filter** — a slight ramp-rate limit around zero torque.

**Overrun torque.** Releasing the pedal closes the blade and produces engine braking (−50 to −150 Nm at the crank for a GT engine; at the wheels this is multiplied by $i_{tot}$, so it is ≈ 2–3× larger in 2nd than in 6th — which is why downshift lock-ups happen in the low gears). Many ECUs let you hold the blade slightly open or add fuel/ignition on overrun ("engine braking map"). More engine braking:
- adds rear braking (shifts effective brake balance rearwards — see brakes),
- loads the diff on coast (more coast locking → more entry stability),
- can lock the inside rear on downshifts.

**Pitfalls**:
- Don't confuse "throttle %" in the logger with torque. Two maps with the same TPS at 40 % pedal can deliver very different torque at 4000 rpm vs 7000 rpm.
- A map that is linear in throttle angle is *not* linear in torque.
- Rain maps that simply scale peak torque (e.g. 70–80 % at full pedal) are a blunt tool. A linear scale does make each pedal % worth less torque, but it permanently gives away 20–30 % of torque on straights and fast exits where even a wet car is power-limited, and it leaves the steep blade/torque non-linearity at small openings in place. A map clipped at 70 % (1:1 below, flat above) is worse: bottom resolution is unchanged and the top of the pedal travel goes dead. Prefer a map that is progressive over the first 30–40 % of travel — resolution exactly where the tyre is at the limit — and keeps full torque available where it is usable.

**Workflow**: if the driver reports poor pickup, overlay the exits of the complaint corner with a reference lap. If the pedal trace has steps within the first 20 % and lateral g is still high, test a softer initial map before touching springs or diff.

## L3 · Advanced

**Designing a torque-linear map.** The airflow through a butterfly, and hence torque, depends on blade angle, rpm and manifold pressure. At low rpm the engine's demand is small, so a small blade opening already brings the manifold close to atmospheric; at high rpm the same angle is far more restrictive. A torque-based map therefore needs a **2D table: blade angle = f(pedal, rpm)**. Procedure:

1. From dyno or in-car torque model, build $T(\alpha, n)$ – torque vs blade angle and rpm.
2. Choose the desired response $T_{req} = T_{max}(n) \cdot g(p)$, where $g$ is the shaping function of pedal $p$ (linear, or progressive such as $g = p^{1.2..1.5}$ in the first third).
3. Invert per rpm column to obtain $\alpha(p, n)$.

**Gear-dependent maps.** Wheel torque is engine torque × $i_{tot}$, so the same pedal % in 2nd gives roughly twice the wheel torque of 4th. Some ECUs allow per-gear scaling of the pedal map so that pedal % means a similar *wheel* torque fraction in low gears — effectively a traction aid by calibration (and often explicitly policed in regulations where TC is banned).

**Turbo dynamics.** The torque response is two-stage: a fast manifold-filling term (~50 ms) and a slow turbo spool term (200–800 ms depending on boost and rpm). Anti-lag and wastegate strategy change what the driver feels far more than the pedal map. Where anti-lag is restricted (most GT3/LMH), a progressive map plus higher idle air on overrun can keep the turbo partially spooled through slow corners at a fuel cost.

**Regulatory reality.** In homologated categories the ECU is often sealed or a spec unit: GT3 maps are homologated and teams select among a few positions; single-seater ladder series (F4–F2) use spec ECUs with fixed or very limited pedal maps; hypercars have torque-demand-based control where the pedal requests total powertrain torque, split by the control unit between ICE and MGU. The engineer's job there is less about building maps than **choosing** among them and **coaching** the driver to the map — and knowing which complaints a map can fix.

## Key formulas

**Torque-demand pedal map**

$$T_{req}(p, n) = T_{max}(n)\, g(p), \quad g(0)=0,\; g(1)=1$$


**Wheel torque from engine torque**

$$T_w = T_e\, i_{tot}\, \eta$$


## Trackside takeaways

- The pedal is a torque request — the map, not the engine, is what the driver feels on pickup.
- Throttle blades are highly non-linear at low rpm: build maps as blade angle = f(pedal, rpm).
- Rain maps should soften the first 30–40 % of pedal, not just cap peak torque.
- Overrun/engine-braking calibration changes effective brake balance and diff coast locking.
- Check the pedal map and tip-in filtering before changing the rear suspension for a "snappy on power" complaint.

## By car category

### GT3

Homologated maps; usually several pedal-map positions selectable on the wheel (dry/wet/fuel). BoP changes in boost or restrictor can change the feel of the same map.

### One-make Cup

Maps are fixed by the manufacturer; the engineer’s lever is driver coaching and choosing among the few supplied positions.

### Hypercar (LMH/LMDh)

Pedal requests total powertrain torque; the supervisor splits it between ICE and MGU under the BoP power cap. Drivability issues can come from torque-blending transitions, not the engine.

### FIA F3

Spec ECU and fixed maps; NA engine, so response is immediate — throttle technique is coached rather than calibrated.

### FIA F2

Turbo V6 with spec electronics: turbo lag at slow exits is a real drivability factor; drivers pre-load the throttle to build boost.

### TCR

FWD with turbo: an aggressive tip-in produces torque steer and front-inside-wheel spin; softer initial pedal maps are a common tool where allowed.

## References

- Segers, Analysis Techniques for Racecar Data Acquisition, 2nd ed. (SAE 2014): §4.2–4.3 Traction, TCS and Slip Ratios (throttle application vs slip on exit)
- Milliken & Milliken, Race Car Vehicle Dynamics (SAE 1995): Ch. 20 Driving and Braking
- Other: Bosch Motorsport / MoTeC ECU documentation (drive-by-wire torque structure, pedal maps)
