5. Reading the report

• Peak torque at the shaft and peak power, with their engine speed and the manufacturer's figures.
• 0–60 km/h, 0–100 km/h, 402 m with the speed at the finish, 100–200 km/h and the top speed.
• The number of faults the ECU logged in each run.
• The emulator release that made the report.

A figure the car did not reach during the test is shown as "not reached".

The torque and power curve shows both values against engine speed with the peaks marked. The acceleration graph shows speed against time with the gear changes.

The report shows how the coolant and the oil warmed up during both runs, and the peak loads against the limits of the vehicle: engine speed, boost, knock, exhaust gas temperature, turbo pressure ratio, clutch, gearbox, tyres, coolant and oil.

A component that goes past its limit is marked as likely damaged, with the cause and the moment it happened. Limits come from the model and engineering data for each vehicle and are still being calibrated in the beta: until a vehicle's limits are set, the report shows peak loads without a verdict.

At the point of peak power the report estimates what the radiator, intercooler, turbo, injectors, clutch, gearbox and tyres must handle, compares it with what the car has and shows the margin. It shows which parts need upgrading for the tune.

The report lists the faults the ECU logged during each run, with DTC codes where the firmware has them. A fault that repeats is shown once, with how many times it happened and when it first and last appeared.

Faults, and an engine that does not reach its torque, are a result of the test, not an error of the service: the test is still completed.

Notes explain the result in plain words and give recommendations. Under the report:

• Download report (JSON) — the report as data;
• Download report (HTML) — the report as a page to keep or send;
• Download image — the image you uploaded.