PURESETUP ENGINEERING WORKFLOW
Every PureSetup starts with data, then moves through engineering refinement and development-driver validation. Cosworth Pi Toolbox telemetry helps us make cleaner setup decisions; on-track work establishes whether those decisions create the predictable balance and repeatability a race stint demands.
01
Development starts from the race you are actually preparing for: the car, circuit, session format and official iRacing race-week conditions where available. This sets the operating window before any setup direction is chosen.
02
Cosworth Pi Toolbox lets our engineering team inspect the relationship between driver inputs, vehicle response and tyre behaviour. We look for patterns that explain a car’s balance—not just a fast trace from one exceptional lap.
03
Engineering changes are made with a clear hypothesis, then returned to the same test environment for review. This preserves cause and effect instead of chasing feel with disconnected adjustments.
04
Data creates the direction, but the setup is not released on data alone. Our development drivers complete repeated on-track runs to assess whether the engineering target translates into a car they can drive precisely, consistently and with confidence.
05
A PureSetup is built to make performance repeatable: stable enough to brake late, clear enough in its balance to manage traffic and tyre life, and predictable enough to carry confidence from the opening lap into the final phase of the stint. A qualifying lap is a data point; race consistency is the standard.
It does not guarantee results, lap times or race wins. Driver performance still depends on driving style, track knowledge, tyre management, traffic, race conditions, hardware and consistency.
SETUP PACKS
Find setup packs developed from telemetry, refined by engineering and validated for repeatable race-week performance.
