Tuning Wiki

This is a historical revision. Read the current page or return to its history.

Page organisation in this revision
Page type
Technical article
Subject
Tuning
Parent
Simos 19
Applies to
Simos 19.6
Tool groups
None
Manufacturers
None

Temperature can change both the performance a tuned engine produces and the protection requests the ECU applies. This guide uses Volkswagen's documented EA888 Evo4 Simos 19.6 examples and COBB's Mk8 monitoring information to organise a useful log. Channel availability, calibration and hardware depend on the vehicle and tool; the sources do not establish universal temperature limits for every Simos 19 installation.

What the temperature channels describe

Volkswagen SSP 822223 identifies Simos 19.6 on its stated GTI, Atlas, Arteon and Golf R EA888 Evo4 examples. Separately, Volkswagen's German-market Golf R Estate introduction describes an electronic coolant regulator on that Evo4 application. These descriptions do not establish identical cooling hardware or sensor placement on all variants.

COBB's Mk8 engine monitor list separates its pre-CCF and fast-monitor lists. Its pre-CCF list names coolant temperature, coolant outlet temperature, coolant setpoint and rotary-valve angle and setpoint. Its fast list names Coolant Temp., Coolant Temp Set Point, Coolant Temp for Trq Lim, Engine Oil Temp., IAT, Charge Air Temperature, and fan PWM actual and setpoint channels. These are product-specific labels. Verify the logger version, units and channel definitions; the monitor list does not prove that a named value is a physical sensor, identify every sensor location, or give acceptance limits.

A setpoint is a request; a coolant-temperature value describes a different quantity from oil or charge-air temperature. A rotary-valve angle or fan PWM channel may help establish what the controller is requesting or reporting, but a value alone does not demonstrate actual coolant flow or fan airflow. The list does not explain how the coolant value used for torque limiting is derived or establish its activation threshold.

Dashboard, log and protection

In its Mk8/8Y tuning guide, COBB describes the dashboard coolant and oil temperature indication in its example as modelled rather than current and recommends logging its Coolant Temp channel during dyno work. This is a statement about the documented product and vehicles, not proof that every dashboard or log channel has the same filtering. A dashboard warning must still be taken seriously and investigated using the vehicle's current service information.

The COBB fast list also names Max Trq. Overheat Prot., Trq Lim Turbo Overheat and Turbo Protection Active. These names give potential context for a thermal complaint; the list alone does not define their exact thresholds, source signals, sign conventions or which limit is active. A changing torque limit does not by itself prove overheating, and a channel that remains steady does not rule out a cooling-system fault.

Fan demand and head-temperature setpoints

EcuTek’s EA888 Evo4 engine-tuning guide describes multiple coolant-fan demand maps for its supported software and says the highest PWM setpoint among the relevant maps and modes is selected. Its examples include general coolant fan demand and an idle sports-mode demand. A change to one map may therefore not change the selected request if another active demand is higher; the guide does not establish which map is active on every vehicle. Confirm ECU software, drive and operating mode, and supported fan request and feedback channels before interpreting the result.

The same guide identifies head-temperature setpoints associated with drive mode, intake-air temperature and vehicle speed. These are separate calibration inputs from a logged coolant reading and the PWM demand itself. A reported request or duty cycle does not prove pump circulation, radiator airflow, actual cylinder-head temperature or cooling capacity. Investigate cooling-system condition and use the appropriate workshop procedure; do not copy another software’s setpoints or treat a changed temperature target as evidence of a repaired mechanical fault.

Repeatable log review

  1. Record the vehicle and engine, ECU and calibration identifiers, logger and software version, modifications, fuel, warning messages, fault codes and freeze-frame data. Resolve active coolant loss, temperature warnings or mechanical faults before increasing load.
  2. After reaching comparable operating conditions, log engine speed, load or torque request, ambient temperature, coolant temperature and its setpoint, oil temperature and available intake or charge-air temperature. Add relevant fan and rotary-valve values only if supported and correctly identified.
  3. Where supported, add the relevant reported torque or air limits, throttle, pressure request and actual, ignition timing and per-cylinder corrections. Compare similar runs at the same load, gear, ambient conditions and cooling intervals; a hotter repeat run may have a different request, intervention or ignition response.
  4. If coolant or charge-air temperatures change unexpectedly, distinguish sensor plausibility, coolant level and leaks, air path, radiator or intercooler condition, fan operation, actuator feedback and circulation using the current diagnostic procedure. A log difference points to an investigation; it does not identify a failed component.
  5. After a repair or hardware change, repeat the same comparison. Keep the ECU's component protections and confirm that the tune and cooling hardware suit the intended conditions. Do not copy numerical limits or table addresses between software versions.

For air-pressure request and wastegate feedback, see Simos 19 EA888 Evo4 boost and wastegate control. For interpreting ignition and per-cylinder knock feedback, see Simos 19 EA888 Evo4 ignition and knock log review.

Sources

For selected Evo4 intercooler kits, dimensional specifications and conditions for comparing charge temperatures, see the EA113 and EA888 intercooler comparison.