Telemetry Validation Process

01

Race-week environment

Validation starts from the official iRacing series week where available, matching the car and track combination with the session format and race-week requirements.

• Official weather profile where available
• Air temperature, track temperature and wind where available
• Sky condition, humidity and track state where available
• Series-specific session requirements

02

Simulator testing

Repeated iRacing runs are used to evaluate how the setup behaves across the lap and through a run, with attention on balance that remains predictable rather than a single isolated peak lap.

• Braking stability and corner entry rotation
• Mid-corner balance and corner exit traction
• Kerb and surface behaviour
• Long-run balance and tyre behaviour across a run

03

Telemetry review

Telemetry is reviewed in Cosworth Pi Toolbox to analyse the signals that support cleaner setup decisions.

• Throttle trace, brake trace and steering angle
• Steering corrections and driver correction frequency
• Tyre behaviour and platform stability
• Lap-to-lap consistency and sector repeatability

04

Iterative setup development

Setup work moves through a repeatable loop so each change can be tested on track and checked against telemetry before final release.

1. Baseline run
2. Setup direction
3. Simulator test
4. Telemetry review
5. Long-run validation
6. Final release review