5 Troubleshooting Thermo Top Evo
502
5.3 Troubleshooting
Possible fault during heater operation are sorted in this
chapter according to the following criteria:
1) Component faults entered in the fault memory (see
Section 5.5).
A specific component which is defective is contained in
the control-unit fault memory. The component or next-
highest assembly must be replaced.
2) General faults entered in the fault memory (see
Section 5.6).
The heater has detected a problem (e.g. no starting),
however cannot identify the specific cause.
Troubleshooting is structured so that the periphery of
the heater is checked (e.g. the fuel supply) before the
heater or a sub-component is replaced.
3) Fault without fault entry in the control unit (see
Section 5.7).
Troubleshooting is structured so that first the periphery
of the heater is checked (e.g. the fuel supply) before the
heater or a sub-component is replaced.
5.4 Reading out fault memory
The fault memory of the heater can be read out with the
Webasto Thermo Test PC Diagnosis.
The fault memory displays up to 8 different faults. The older
an fault is, the higher its number. The current operating
duration and the current start-up number are entered in the
control unit summary.
If a fault is entered as "current" then the control unit has
discovered this fault since the last switch-on.
The fault message "Initial starting attempt failed" remains
current until either full-load combustion operation is
achieved in the restart or the second start-up also fails. In
this case, the fault message "Initial starting attempt failed"
is deleted and replaced with "No start".
The fault message "Flame abort" remains current until the
heater is switched off or several flame aborts lead to the
heating mode being aborted. In this case, the fault message
"Flame abort" is deleted and replaced with "Flame failure".
NOTE
The operation of the diagnostic unit is explained in the oper-
ating instructions. W bus must be entered under Heater
model.
It is recommended that the operating and fault data and the
extended fault environment conditions be printed out.