In brief

Fault code A9 on Viessmann Vitocal means: Fault code A9 is often linked to a temperature/sensor measurement or a control inconsistency (depending on version). A structured diagnosis helps isolate whether the problem is from a sensor, wiring, or settings. Most common cause: Common causes: faulty temperature sensor, poorly engaged connector, damaged cable, or abnormal hydraulic condition (insufficient flow) leading to inconsistent measurements. First action: Isolate the power supply before any work on connections.. Call a registered engineer if the fault returns after basic checks or involves refrigerant work (F-Gas registered engineer required).

According to field data, the Viessmann Vitocal A9 is recurrent due to insufficient hydraulic flow, often from a dirty dirt separator or blocked circulation pump.

A9ViessmannVitocal

Fault code A9 Viessmann Vitocal: causes, diagnosis and solution

Fault code A9 is often linked to a temperature/sensor measurement or a control inconsistency (depending on version). A structured diagnosis helps isolate whether the problem is from a sensor, wiring, or settings.

Source: Viessmann documentation (installer/service manual – according to product reference)

Équipe Ask Marcel

Équipe Ask Marcel

Techniciens CVC certifiés

Rédaction et validation terrain par des installateurs PAC, clim et chauffage. Données croisées avec plus de 50 000 fiches pannes documentées.

What does fault code A9 on Viessmann mean?

Fault code A9 is often linked to a temperature/sensor measurement or a control inconsistency (depending on version). A structured diagnosis helps isolate whether the problem is from a sensor, wiring, or settings.

Common causes: faulty temperature sensor, poorly engaged connector, damaged cable, or abnormal hydraulic condition (insufficient flow) leading to inconsistent measurements.

Symptômes

  • Shutdown or degraded operation
  • Irregular heating/DHW
  • Intermittent restarts
  • Fault code A9 displayed on the interface

Diagnostic

1. Secure and gather information

  • Isolate the power supply before any work on connections.
  • Note the model (Vitocal), state (heating/DHW) and time of occurrence.
  • Check the fault history and recent changes (settings, servicing).

2. Check sensor(s) and connections

  • Inspect connectors: oxidation, moisture, bent pins, poor contact.
  • Check cable routing (pinching, abrasion, overheating).
  • Re-clip connectors then restart to confirm stability.

3. Check hydraulics and operating range

  • Check flow/circulator, filters, valves, circuit pressure.
  • Compare measured temperature with actual (if accessible).
  • If fault persists, apply Viessmann procedure (ohmic values/measurements per sensor).

How to reset fault code A9 on Viessmann?

If a sensor shows inconsistent or unstable values, replacement usually resolves it. If no visible anomaly, follow the Viessmann manufacturer procedure corresponding to fault code A9 for your exact reference (electrical tests, module checks).

When should you call an F-Gas engineer?

Common at first commissioning or after a heating season without hydraulic filter maintenance.

Affected models

  • Vitocal 350A
  • Vitocal 300
  • Vitodens 300-W

Field context

Common at first commissioning or after a heating season without hydraulic filter maintenance.

Technical source data

The Viessmann Vitocal A9 is recurrent in the field due to insufficient hydraulic flow: dirty dirt separator, protection pressure switches, or blocked internal circulation pump (Vitodens 300-W). Documented solution: clean dirt separator, check flow, sometimes a full power cycle.

Sources: chaleurterre.com — Vitocal A9 (p. 1)

Questions fréquentes

Viessmann A9 returns after reset: what to do?

Inspect the dirt separator and actual circuit flow: A9 is often linked to hydraulic fouling, not a random electronic fault.

Need help with this diagnosis?

Marcel reads your error codes and walks you through them step by step, with sourced answers.

Mobile app
Download on the App StoreGet it on Google Play

Or keep going right now in your browser:

Handling this fault code at scale? Plug AskMarcel into your own tools