Skip to content

Virtual dyno for your ECU tune

Beta

Upload a tuned firmware image and get two tests — a power and torque pull on a working gear and a standing-start acceleration run — simulated on a model of the car, with a full dyno-style report. Available in beta to TCEPro license holders.

Included with an active TCEPro license.

An estimate on a model of the car — it does not replace a real dyno. Results on a real car depend on its condition.

Latest virtual dyno runs

Recent tests by TCEPro users, shown anonymously with the owner's consent. Figures are estimates on a model of the car.

No runs to show yet — results appear here as tests finish.

Two tests, one report

Power and torque pull

3rd gear, wide-open throttle from 1500 to 6500 rpm. Torque and power curves at the shaft in 250 rpm steps, with peaks marked.

Standing-start acceleration

Full throttle from rest up to 200 km/h, at most 60 seconds. 0–60 and 0–100 km/h, the 402 m (quarter mile) time and speed, 100–200 km/h, top speed, gear at 100 km/h and wheel slip.

Both tests start with a warm engine, as after a short stop.

Your firmware, realistic physics

The virtual dyno runs your firmware image unchanged, instruction by instruction, on an emulated ECU processor. Around it is a model of the whole car, so the ECU reads its sensors and drives its actuators as it would on the road.

  • Engine. Airflow, fuelling, ignition timing and torque — and on turbocharged engines, boost with turbo spool-up and the wastegate driven by the ECU.
  • Heat. Coolant, oil, intercooler, thermostat and fan warm up and cool down during the run.
  • Driveline. The gearbox with its clutches, torque converter or hybrid motor, road load, tyre grip and wheel slip, with the mass and gear ratios of the car.
  • ECU decisions. Torque limits, boost targets, ignition retard on knock, rev and fuel cuts and fault codes come from the calibration you uploaded, not from the model.

The models are built from the car's specifications and the stock calibration, and every physical law is checked by automatic tests. It is still a model — see the method note.

Overload check and hardware estimate

  • Overload check. Each run tracks 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.
  • Hardware estimate. 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 — so you see which parts need upgrading for your tune.

Limits and estimates come from the model and engineering data for each vehicle, not from measuring a real car. They are being calibrated for each vehicle in the beta: until a vehicle's limits are set, the report shows peak loads without a verdict.

How it works

  1. Upload the image. A full raw flash dump (.bin) of a supported unit — stock or tuned.
  2. Automatic checks. The image is identified, and its checksums are verified within seconds.
  3. Queue and test run. Both tests run one after another on a model of the car: about 20 minutes, depending on the image, plus time in the queue. You can close the page — we email you when the report is ready.
  4. Read the report. Results against the manufacturer's figures, curves, acceleration, temperatures, component loads with an overload check, a hardware estimate and the faults the ECU logged during the test.

What the report includes

  • Test conditions
  • Results vs. manufacturer figures
  • Torque and power curve
  • Acceleration times and speed graph
  • Coolant and oil temperatures
  • Component loads and overload check
  • Hardware estimate
  • ECU faults with DTC codes
  • Notes
  • Method note

Vehicles in the beta

  • Haval H3 2026 1.5T, 7-speed DCTBosch MG1US018 · Program ID CJ1VE2A384
  • Haval F7 2.0T 4WD, 7-speed DCTBosch MG1US008 · Program ID ZJA307A320
  • Haval M6 PLUS 1.5T, 7-speed DCTBosch MG1UA008 · Program ID F01R0AD6SJ
  • Jetour Traveller (T2) 2.0T 4WD, 7-speed DCTBosch MG1US008 · Program ID Z22907A2D2
  • Dongfeng Fengon iX7 2.0T, 6-speed automaticBosch MG1US008 · Program ID ZK1107A854
  • Geely Atlas, 7-speed DCTBosch MG1CS080 · Program ID ZL5CX5A2A1
  • GWM TANK 400 Hi4-T 2.0T PHEV 4WD, 9-speed hybrid automaticBosch MG1US008 · Program ID ZJ9N07A323
  • Changan CS35 Plus 1.6, 6-speed automaticDelphi MT92 · Program ID B4NSAD03b1

The list grows as new vehicle models are prepared. A tuned image is accepted when it is based on the same software (Program ID) as a supported image.

Requirements

  • A full raw flash image (.bin) — not HEX, S19, a ZIP archive or a partial dump.
  • Valid checksums. A real ECU refuses to start firmware with broken checksums, so the virtual dyno refuses it too. TCEPro does not recalculate MG1US008 checksums yet — correct them with your usual tool before uploading.
  • An active TCEPro license.

Method note

Results come from a model of the car running your firmware in an emulator. They are an estimate, not a measurement, and the virtual dyno does not replace a run on a real dyno. A real car can behave differently depending on its condition: engine and turbo wear, fuel quality, sensors, intake and exhaust, clutch and gearbox, tyres and weather. Confirm the final tune on a real dyno before using it on the road. Reports from different emulator releases are not comparable.

Your files

Your firmware images and reports are yours: they are never shared with other users or third parties. If you leave “Show in the public log” on, only the vehicle, stock or tuned, the day and the headline figures appear in the log below — never your name, label, file or report. Reports are kept for 365 days, and you can delete your tests and images at any time; a deleted test leaves the log too.

FAQ

Included with an active TCEPro license.