Every error code. What it means. What to check first. Built for Australian HVAC contractors who don’t have time to dig through manuals on site.
By Airnexus™ · Intelligent HVAC Platform
Why Fault Codes Matter
When a Daikin VRV system throws a fault code, you have two choices. You can pull out the installation manual — assuming it’s still in the plant room and hasn’t been used as a doorstop — and start flipping through pages of tiny text. Or you can look it up here, get the answer in seconds, and get back to fixing the problem.
This guide exists because fault codes are not just error messages. They’re the system telling you what went wrong, and more importantly, where to start looking. A fault code that says “high pressure” could be a blocked condenser, an overcharged system, a failed fan motor, or a faulty pressure sensor. The code gets you into the right neighbourhood. Your experience gets you to the front door. This guide fills the gap in between.
We’ve structured every entry the same way: what the code means, what to check first, the most common cause in real-world Australian installations, and how continuous monitoring changes the game. No fluff. No filler. Just the information you need when you’re standing in front of a unit at 2pm on a 42-degree day in Western Sydney and the building manager is calling you every five minutes.
Daikin VRV fault codes fall into five main categories, and understanding the prefix tells you immediately which system is involved:
U codes — Communication and refrigerant circuit faults E codes — Sensor and protection device faults L codes — Compressor and inverter faults A codes — Indoor unit faults (airflow, drain, PCB) F, H, J codes — Miscellaneous faults (refrigerant circuit, system-level)
Communication Faults — U Codes
Communication faults are the most common category you’ll encounter on VRV systems, and they’re responsible for a disproportionate number of call-outs. The good news: most of them are wiring issues. The bad news: wiring issues on a multi-unit system with 200 metres of communication bus can take hours to find without the right tools.
U0
Low refrigerant / low pressure detection
What it means
The system has detected low suction pressure, typically indicating insufficient refrigerant charge. The outdoor unit’s low-pressure sensor has triggered a protection shutdown. This code can also appear during extreme low-ambient heating operation if the system isn’t configured for it.
What to check first
Check for visible leaks at flare connections — look for oil stains around joints, especially at branch joints (refnets) and indoor unit connections. Check subcooling at the outdoor unit liquid service valve. If subcooling is below 3K, you almost certainly have a charge issue. Check the low-pressure sensor reading against a gauge set to rule out a faulty sensor. On systems with long pipe runs (60m+), check for restrictions in the liquid line — a kinked pipe or partially blocked strainer will mimic low-charge symptoms.
Common cause
Slow leak at a flare connection that’s been losing charge for months. Also common after initial commissioning if the additional charge calculation was wrong — particularly on systems with long pipe runs where the charge tables were misread.
Nexus iQ™ advantage: Subcooling and suction pressure are trended continuously. A gradual decline over weeks is visible on the diagnostics chart long before U0 triggers — giving you time to schedule a leak check rather than respond to an emergency call.
The outdoor unit has detected abnormal supply voltage. This includes both under-voltage and over-voltage conditions, as well as phase loss or phase imbalance on three-phase units. The system will lock out to protect the inverter and compressor.
What to check first
Measure all three phases at the outdoor unit terminals — not at the switchboard, at the unit. Check for voltage imbalance (more than 2% between phases indicates a problem). Check for loose connections at the isolator and contactor. If the fault is intermittent, it’s likely a supply issue — check with the electricity provider for voltage dips during peak demand. On single-phase units, check that the supply voltage is within the 220–240V range under load.
Common cause
Loose neutral connection at the switchboard causing voltage fluctuation. Phase loss from a blown fuse in one leg of a three-phase supply. Undersized cabling on long cable runs from the switchboard to the outdoor unit.
Nexus iQ advantage: Voltage logging captures intermittent supply issues that only occur during peak demand periods — the kind you’ll never catch with a multimeter on a service visit.
The outdoor unit has lost communication with one or more indoor units on the two-wire communication bus. This is one of the most common Daikin VRV fault codes and is responsible for a significant number of call-outs across the industry.
What to check first
Check the two-wire communication bus for correct polarity — F1 to F1 and F2 to F2 all the way through the system. Measure voltage between F1–F2 at the outdoor unit (should be 1–2V AC during active communication). Check for damaged wiring, loose terminals, or shielding issues. If the communication cable runs parallel to power cables, electromagnetic interference may be the cause. Disconnect indoor units one at a time to isolate which unit is causing the fault. Check for water ingress into junction boxes along the communication bus.
Common cause
Reversed polarity on one indoor unit in the chain. A damaged communication wire pinched during ceiling works. Water ingress into a junction box. In older installations, corroded terminals at the outdoor unit PCB.
Nexus iQ advantage: Continuous communication monitoring detects intermittent dropouts before they become persistent faults. The platform logs every communication event, so you can see the pattern — is it always at the same time of day? Does it correlate with a specific indoor unit coming online?
90% of U4 faults are wiring issues. Before you replace a PCB, check every connection on the communication bus.
U9
Communication error — between outdoor units (multi-system)
What it means
On multi-outdoor-unit systems (2-module or 3-module configurations), this code indicates that the master outdoor unit has lost communication with one or more slave outdoor units. The inter-unit communication bus uses the same F1–F2 wiring but is a separate circuit from the indoor unit bus.
What to check first
Check the inter-unit communication wiring between outdoor units. Verify correct master/slave addressing via the DIP switches or field setting. Ensure each outdoor unit has a unique address. Check for loose connections at the outdoor unit PCB terminals. On rooftop installations, check for UV degradation of the communication cable insulation.
Common cause
Incorrect DIP switch settings after a PCB replacement. Corroded terminals on rooftop installations exposed to weather. Communication cable damaged during condenser cleaning with a pressure washer.
Nexus iQ advantage: Multi-module system health is monitored as a single entity. If one module drops out, the platform immediately flags the imbalance in load sharing and compressor frequency distribution.
Communication error — indoor unit address conflict
What it means
Two or more indoor units have been assigned the same address on the communication bus. The outdoor unit cannot distinguish between them, causing communication conflicts and unpredictable behaviour across the system.
What to check first
Use the wired remote controller or Daikin’s Intelligent Touch Manager to list all connected indoor unit addresses. Look for duplicates. Check the address setting on each indoor unit PCB (rotary switches or DIP switches depending on the model). This fault commonly occurs after a new indoor unit is added to an existing system without checking the address allocation table.
Common cause
New indoor unit installed with factory-default address matching an existing unit. Address rotary switch bumped during servicing. PCB replacement where the address wasn’t reconfigured.
Nexus iQ advantage: The platform maintains a full address map of every indoor unit on the system. Any address conflict is flagged immediately at commissioning time, before it causes operational issues.
The main outdoor unit PCB has lost communication with the inverter PCB. This is an internal outdoor unit communication fault, distinct from the bus communication errors (U4, U9). The inverter PCB controls compressor frequency, and without communication, the compressor cannot operate.
What to check first
Check the ribbon cable or connector between the main PCB and inverter PCB inside the outdoor unit. Look for signs of heat damage, rodent activity, or corrosion. Check the DC bus voltage at the inverter PCB. If the inverter PCB has failed, there are usually visible signs — burnt components, discoloured solder joints, or swollen capacitors.
Common cause
Inverter PCB failure due to power surge or lightning strike. Loose ribbon cable connector caused by vibration. In coastal installations, salt-air corrosion on PCB components.
Nexus iQ advantage: Compressor frequency data disappearing from the trend log is an early indicator of intermittent UF faults, often visible days before the system fully locks out.
E codes cover sensor failures and protection device activations. These range from simple thermistor faults (quick fix) to high-pressure lockouts (potentially serious). The key with E codes is distinguishing between a sensor that’s actually failed and a sensor that’s reading correctly but the system condition is genuinely out of range.
E0
Indoor unit protection device activated
What it means
A safety protection device on the indoor unit has triggered. This is a general protection code that covers the indoor unit’s built-in safety circuits, including overcurrent protection and thermal fuses.
What to check first
Check the indoor unit’s fan motor for seizure or excessive current draw. Check the indoor unit PCB for visible damage. Inspect the thermal fuse on the indoor unit heat exchanger. On ducted units, check that the return air path isn’t completely blocked — a clogged filter or closed damper can cause the coil to freeze, triggering the protection device.
Common cause
Fan motor bearing failure causing overcurrent. Completely blocked return air filter on a ducted unit. Indoor unit PCB fault after a power surge.
Nexus iQ advantage: Fan motor current draw is trended over time. A gradual increase indicates bearing wear, and the platform flags it as a declining health score before the motor fails completely.
The indoor unit’s main PCB has detected an internal error. This may be a memory corruption, processor fault, or communication failure between the PCB and its onboard components (fan motor driver, expansion valve driver, thermistor inputs).
What to check first
Power cycle the indoor unit — isolate it, wait 30 seconds, and restore power. If the fault clears and doesn’t return within 24 hours, it was likely a transient glitch caused by a voltage spike. If it returns, check the PCB for visible damage: burnt components, swollen capacitors, or corroded connectors. Check the power supply voltage to the indoor unit. Also check the wiring harness to the fan motor and electronic expansion valve — a short circuit on these outputs can cause the PCB to register an internal fault.
Common cause
Power surge damage to the PCB. In humid environments, condensation on the PCB causing short circuits between traces. Age-related capacitor failure on units older than 10 years.
Nexus iQ advantage: When E1 occurs intermittently, the platform logs the exact timestamp and correlates it with other system events — was there a power anomaly? Did other units on the same circuit experience issues at the same time?
The high-pressure sensor on the outdoor unit has detected discharge pressure exceeding the safety threshold. This is a critical protection that prevents compressor damage and potential refrigerant release. The system will lock out immediately and require a manual reset on most models.
What to check first
Check the condenser coil for blockage — dirt, leaves, cotton from nearby trees, or bird nesting material. Verify that all condenser fans are operating and spinning in the correct direction. Check the refrigerant charge — overcharge is a common cause of high pressure, particularly if someone has topped up the system without checking subcooling properly. Measure subcooling at the liquid service valve; if it’s above 12K, the system is likely overcharged. Check outdoor ambient temperature — if the unit is installed in an enclosed plant room or against a wall with poor airflow, recirculation of hot discharge air will cause high pressure on extreme days.
Common cause
Blocked condenser coil on a rooftop unit that hasn’t been cleaned in 12 months. Overcharged system after a top-up where subcooling wasn’t measured. Failed condenser fan motor. In summer, a unit installed in a poorly ventilated location hitting its ambient limit.
Nexus iQ advantage: Discharge pressure and condenser approach temperature are trended daily. A gradual increase over weeks tells you the condenser is fouling — schedule a clean before E3 trips on the hottest day of the year.
The low-pressure sensor on the suction line has detected pressure below the protection threshold. This overlaps somewhat with U0 but specifically refers to the pressure sensor circuit and its protection logic. On some models, E4 indicates a low-pressure sensor that is open-circuit or reading out of range.
What to check first
First determine whether this is a genuine low-pressure condition or a sensor fault. Connect a gauge set to the suction service valve and compare the reading with the sensor value displayed on the PCB’s LED readout. If the readings match, treat it as a refrigerant charge issue (see U0). If the sensor reads significantly differently from the gauge, the sensor has failed. Check the sensor wiring and connector for damage.
Common cause
Genuine low charge causing low suction pressure. Faulty low-pressure transducer giving erratic readings. Kinked or restricted suction line after installation or modification work.
Nexus iQ advantage: The platform compares sensor readings against calculated expected values based on operating conditions, flagging sensor drift before it causes nuisance trips.
The compressor is drawing more current than the inverter can safely deliver. This is a critical protection — it prevents damage to both the compressor motor and the inverter power module. The fault can be caused by mechanical issues in the compressor, electrical faults, or operating conditions that force the compressor to work beyond its design envelope.
What to check first
Measure compressor winding resistance (phase-to-phase and phase-to-ground) with the system powered off. Look for low insulation resistance which indicates winding degradation. Check for liquid slugging — if the suction superheat is below 3K, liquid refrigerant may be reaching the compressor. Verify that the electronic expansion valves on connected indoor units are functioning correctly. On systems with long suction lines, check for oil logging which increases compressor load.
Common cause
Compressor motor winding degradation — the insulation breaks down over time, especially in systems running with contaminated refrigerant or moisture in the circuit. Liquid slugging from a stuck-open expansion valve. Oversized pipe runs causing oil logging in the suction line.
Nexus iQ advantage: Compressor current draw relative to frequency is a key diagnostic ratio. When the current-to-frequency ratio starts climbing, it indicates increasing mechanical resistance — visible on the trend months before E5 trips.
A fault code tells you what failed. Trending data tells you what’s about to fail. That’s the difference between reactive and predictive maintenance.
E7
Outdoor fan motor fault
What it means
The outdoor unit’s condenser fan motor has failed to operate or is not reaching the expected speed. On inverter-driven fan motors, this can indicate a motor driver fault, a wiring issue, or a mechanical failure of the motor itself.
What to check first
Try spinning the fan by hand with the power off. If it’s stiff or makes grinding noises, the bearings are failing. Check the fan motor resistance between all three phases (should be balanced and typically 5–20 ohms depending on the model). Check the fan motor connector on the outdoor unit PCB — corrosion or a loose connector is common on rooftop units. Look for physical obstruction — debris, bird nesting material, or a displaced fan guard that’s catching the blade.
Common cause
Fan motor bearing failure — especially on rooftop units exposed to weather. Corroded motor connector on the PCB. Fan blade hitting a displaced guard after cleaning or maintenance. On DC fan motors, the motor driver on the PCB fails while the motor itself is fine.
Nexus iQ advantage: Fan motor speed data trending allows early detection of slowing or erratic fan operation. A fan that’s gradually losing speed indicates bearing wear — replace it during the next scheduled service, not during an emergency call-out on a 40-degree day.
The system has detected that the four-way (reversing) valve has not switched correctly between heating and cooling modes. This is determined by comparing discharge and suction temperatures after a mode change — if the temperatures don’t match the expected pattern for the requested mode, the valve is assumed to be stuck or only partially shifted.
What to check first
Check the four-way valve solenoid coil for continuity. Check the voltage at the solenoid coil during a mode change command. Listen for the valve clicking when energised — if you hear the click but temperatures don’t change, the valve body is stuck. This can sometimes be freed by rapidly cycling the mode several times. On systems that have been in one mode for a long time (e.g., cooling only for the entire summer), the valve slide can become stuck.
Common cause
Valve slide stuck after extended single-mode operation. Failed solenoid coil (open circuit). Debris in the refrigerant circuit lodging in the valve body and preventing full travel. On VRV IV systems, the valve timing can be affected by low charge conditions.
Nexus iQ advantage: Mode change events are logged with before/after temperature comparisons. If the four-way valve is sluggish (taking 30+ seconds to fully shift when it should take 5–10), the platform flags it as a developing issue.
L codes are the ones that make your stomach drop. These relate directly to the compressor and inverter — the most expensive components in the outdoor unit. The good news: not every L code means a compressor replacement. Some are caused by external factors (power supply, charge, airflow) that, once corrected, allow the system to resume normal operation.
L1
Inverter PCB fault
What it means
The inverter PCB has detected an internal fault in its power stage — the IGBTs (Insulated Gate Bipolar Transistors) that convert DC bus power into the variable-frequency AC output for the compressor. This is a serious fault that requires the inverter PCB to be replaced in most cases.
What to check first
Before assuming the inverter PCB is faulty, check the DC bus voltage (should be approximately 360–400V DC on a 240V single-phase unit, or 560–650V DC on a 415V three-phase unit). If the DC bus voltage is abnormal, the issue may be upstream — check the rectifier section and supply voltage. Check the compressor motor insulation resistance — a shorted compressor winding will destroy the inverter output stage. If the compressor checks out, the inverter PCB likely needs replacement. Check for visible signs of failure: burnt components, discoloured areas on the PCB, or a burnt smell.
Common cause
Lightning strike or power surge damaging the IGBT modules. Compressor winding short circuit pulling excessive current through the inverter. In humid coastal environments, salt-air corrosion degrading the PCB over time. Failed capacitors in the DC bus filter section.
Nexus iQ advantage: DC bus voltage and inverter temperature are monitored continuously. Abnormal voltage fluctuations or temperature spikes are flagged as early warnings of inverter stress before L1 occurs.
The temperature sensor inside the outdoor unit’s electrical compartment has exceeded the safety threshold. The electronic components (PCBs, capacitors, wiring) are overheating, which accelerates component degradation and increases the risk of fire.
What to check first
Check that the electrical compartment ventilation openings are not blocked. On some VRV models, the electrical compartment has its own small fan — verify it’s operating. Check the ambient temperature around the unit — if the unit is installed in direct afternoon sun with no shade, the electrical compartment temperature can exceed the threshold on extreme days. Check for excessive dust buildup inside the compartment that’s acting as insulation. Verify that the compartment cover is properly sealed — a missing or damaged seal can actually increase temperature by allowing hot condenser discharge air to enter.
Common cause
Blocked ventilation holes on the electrical compartment (often covered during painting or building maintenance). Failed compartment cooling fan. Unit installed in a location with poor ventilation and direct sun exposure. Excessive dust buildup from nearby construction work.
Nexus iQ advantage: Electrical compartment temperature is logged alongside ambient temperature, creating a clear baseline. When the delta between ambient and compartment temperature starts increasing, it indicates a developing ventilation issue.
The inverter heatsink — which dissipates heat from the power transistors — has exceeded its maximum operating temperature. In most VRV systems, the inverter heatsink is cooled by refrigerant flowing through an integrated plate heat exchanger. When heatsink temperature is too high, it means either the cooling is inadequate or the inverter is generating excessive heat.
What to check first
Check for dust buildup on the heatsink fins. Verify the heatsink cooling fan operation (if equipped). Most importantly, check the refrigerant charge — the inverter is cooled by liquid refrigerant in the subcooling circuit, so low charge means poor inverter cooling. Check subcooling at the outdoor unit: if it’s below 5K, the heatsink isn’t getting enough liquid refrigerant for cooling. Also check that the heatsink thermistor is properly seated — if it’s fallen off the heatsink surface, it will read ambient temperature instead of heatsink temperature, causing erratic readings.
Common cause
Low refrigerant charge reducing the cooling capacity available to the inverter heatsink. Dust-clogged heatsink fins restricting airflow. Failed heatsink fan. In extreme cases, a partially blocked subcooling circuit (debris in the capillary tube feeding the heatsink heat exchanger).
Nexus iQ advantage: Heatsink temperature trended against compressor frequency reveals the thermal load relationship. If heatsink temperature starts climbing at the same compressor frequency where it was previously stable, it indicates degrading cooling capacity — typically a slow charge loss.
The inverter has detected an instantaneous current spike from the compressor that exceeds the safe operating threshold. Unlike E5 (sustained overcurrent), L5 is triggered by a sudden spike — typically caused by a mechanical event inside the compressor, a short circuit in the motor windings, or a ground fault.
What to check first
This is often a compressor failure indicator. Measure compressor winding resistance between all three phases — they should be balanced (within 5% of each other). Measure insulation resistance (megger test) between each phase and ground — minimum 1 megohm, ideally above 10 megohms. If insulation resistance is below 1 megohm, the compressor windings are degraded and the compressor needs replacement. If the compressor tests OK electrically, check for liquid slugging (low superheat) which can cause hydraulic lock and current spikes. Also check the inverter output wiring for any short circuits between phases.
Common cause
Compressor motor winding insulation breakdown. Liquid slugging during startup (especially after a long off period in cold weather). Ground fault in the compressor motor. On rare occasions, an intermittent short in the wiring between the inverter and compressor.
Nexus iQ advantage: Compressor startup current profiles are captured and compared against baseline. Increasing startup current spikes indicate winding degradation — giving you weeks or months of warning before L5 permanently trips.
Communication fault between inverter and control PCB
What it means
The inverter PCB and the main control PCB inside the outdoor unit are not communicating correctly. This is similar to UF but specifically relates to the control signal path rather than the power stage communication. The compressor cannot receive frequency commands and will not operate.
What to check first
Check the signal cable between the inverter PCB and control PCB for damage or loose connectors. Check both PCBs for visible damage — particularly look for corroded connectors or burnt traces near the communication circuit. Power cycle the outdoor unit (full isolation, 60 seconds, restore). If the fault persists after a power cycle, one of the two PCBs has likely failed.
Common cause
Corroded connector pins on the inter-PCB cable. PCB failure due to moisture ingress. Signal cable damaged by rodent activity inside the electrical compartment.
Nexus iQ advantage: Compressor response latency — the time between a frequency command and the actual speed change — is monitored. Increasing latency indicates degrading communication between the control and inverter PCBs.
Nexus iQ monitors discharge temperature, superheat, subcooling, and compressor frequency 24/7. It catches the patterns that lead to fault codes — before they happen.
These codes cover indoor unit airflow issues, refrigerant circuit faults, and system-level errors. They’re generally less common than U, E, and L codes, but some — like A3 (drain) and F3 (discharge temperature) — are extremely common in Australian conditions.
A1
Indoor unit PCB defect
General indoor unit PCB malfunction. Power cycle the unit first. If the fault persists, check for visible PCB damage, corroded connectors, or swollen capacitors. On units in high-humidity environments (pools, kitchens), moisture ingress is the most common cause.
The condensate drain pan float switch has risen, indicating the drain is blocked or the condensate pump has failed. This is one of the most common indoor unit fault codes in Australian installations, especially in humid coastal areas. Check the drain line for blockage (algae buildup is the usual culprit), verify the condensate pump operation, and clean the drain pan. Installing drain pan treatment tablets during regular maintenance prevents most A3 faults.
The indoor coil temperature has dropped below the freeze protection threshold. This occurs when airflow across the coil is insufficient — typically a blocked filter, closed damper, or failed fan motor. Check the filter first (always check the filter first). On ducted units, verify that all zone dampers are not simultaneously closed. If airflow is adequate, check the electronic expansion valve — a stuck-open EEV can flood the coil with refrigerant, causing freeze-up.
The indoor unit’s fan motor has failed to start, is running at an abnormal speed, or has stopped unexpectedly. Check for physical obstruction of the fan wheel. Measure motor winding resistance. On DC brushless motors (standard on most current Daikin models), check the hall sensor connector. If the motor spins freely by hand but won’t run electrically, the motor driver circuit on the indoor PCB may have failed.
On indoor units equipped with an air filter differential pressure sensor, the filter restriction has exceeded the service threshold. This is a maintenance reminder rather than a critical fault. Clean or replace the filter and reset the filter timer via the remote controller or centrally through the Intelligent Touch Manager.
Compressor discharge temperature has exceeded the safety threshold (typically 115–120°C). This is a critical protection — sustained high discharge temperature accelerates oil breakdown, damages valve seats, and degrades compressor windings. Common causes: low refrigerant charge (insufficient suction gas cooling), blocked condenser, non-condensable gases (air) in the system, or compressor valve leakage. Check superheat and subcooling first. If superheat is above 20K, you likely have a charge or restriction issue.
High pressure switch activated (redundant protection)
The mechanical high-pressure switch has physically tripped. This is a redundant safety device that operates independently of the electronic pressure sensor (which triggers E3). If F6 trips, the high pressure has exceeded the mechanical switch setpoint — typically 4.15 MPa for R-410A systems. Check all the same items as E3, but treat this as more serious because the electronic protection (E3) should have caught it first. If F6 trips without E3, the electronic pressure sensor may be faulty.
If the mechanical high-pressure switch (F6) trips without the electronic sensor (E3) catching it first, you have two problems: high pressure and a faulty sensor.
H6
Position detection sensor fault (compressor)
The inverter cannot detect the compressor motor rotor position. On sensorless DC inverter compressors (which most VRV systems use), the rotor position is estimated from back-EMF signals. H6 indicates the inverter has lost lock on the rotor position — the compressor either stalled or the back-EMF signal is too noisy to track. Check for liquid slugging, mechanical seizure, or excessive load at startup. A common cause is a locked rotor after a power outage during operation.
The compressor current sensor (CT) is reading abnormally. This sensor provides current feedback to the inverter for overcurrent protection and efficiency calculations. If the CT is faulty, the inverter cannot safely control the compressor. Check the CT sensor connector on the inverter PCB. Verify the CT is properly clamped around the correct wire. A displaced CT (moved during maintenance) is the most common cause.
The outdoor ambient air temperature sensor has failed or is reading out of range. The system uses ambient temperature for capacity control calculations, defrost timing, and ambient limit protection. Check the thermistor resistance (typically 10kΩ at 25°C for NTC type). If the sensor is covered in dirt or in direct sunlight, it may be reading inaccurately. Relocate or clean the sensor if readings are offset from actual ambient.
The compressor discharge temperature sensor has failed or is reading out of range. This is a critical sensor — without accurate discharge temperature, the system cannot protect the compressor from overheating. Check the thermistor resistance and verify it’s properly strapped to the discharge pipe with thermal paste and insulation. A loose thermistor will read lower than actual discharge temperature, potentially allowing the compressor to overheat without triggering F3 protection.
The outdoor heat exchanger (condenser/evaporator in heat pump mode) temperature sensor has failed. This sensor is used for subcooling calculation, defrost control, and capacity management. Check the thermistor resistance and its physical position on the coil. On units that have been in service for several years, the thermistor leads can become brittle and break, especially if they were routed near hot components during installation.
Fault codes are reactive. By the time a code appears, the problem has already occurred. The real value of monitoring isn’t knowing what went wrong — it’s knowing what’s about to go wrong.
Here’s how it works in practice. A Daikin VRV system has dozens of operating parameters that are continuously changing: discharge temperature, suction pressure, superheat, subcooling, compressor frequency, fan speed, expansion valve position, coil temperatures. In a healthy system, these parameters maintain consistent relationships with each other. Discharge temperature tracks predictably with compressor frequency and ambient temperature. Superheat stays within a narrow band. Subcooling remains stable.
When something starts to degrade — a slow refrigerant leak, a fouling condenser, bearing wear in a fan motor — these relationships start to shift. The changes are tiny at first. A degree here, half a kelvin there, a few hertz of extra compressor frequency to maintain the same capacity. No fault code triggers because no individual parameter has exceeded its protection threshold. But the trend is unmistakable when you have the data.
Nexus iQ captures this data continuously, stores it, and analyses it against the system’s own historical baseline. It doesn’t compare your system to a generic model — it compares your system to itself, two weeks ago, two months ago, two seasons ago. When the patterns diverge, you get alerted. Not with a fault code, but with a diagnostic insight that says: “Subcooling on outdoor unit 1 has decreased by 2.4K over the last 30 days. This is consistent with a charge reduction of approximately 8%.”
That’s the difference between finding a leak and chasing a lockout.
Scenario
Without Monitoring
With Nexus iQ
Slow refrigerant leak
U0 fault on the hottest day. Emergency call-out. Tenants in 32°C offices.
Subcooling trend flagged 6 weeks earlier. Leak found and repaired during scheduled service.
Condenser fouling
E3 high pressure lockout. System down for hours.
Condenser approach temperature increasing 0.5K/week. Clean scheduled before summer peak.
Fan motor bearing wear
E7 fan motor fault. No spare in stock. 3-day wait for parts.
Fan speed variance detected. Motor ordered and replaced during next service visit.
Knowing what a fault code means is step one. Preventing it from happening is step two. Here’s how to move from reactive to predictive maintenance on your Daikin VRV systems.
1. Book a Demo
See Nexus iQ monitoring a live VRV system — real fault history, real diagnostic charts, real trending data. We’ll show you exactly how the platform detects developing issues before they become fault codes. No slides, no hypotheticals — just a live system managing real buildings across Australia.
2. Connect Your System
A Nexus controller connects directly to the Daikin VRV communication bus. Installation takes under a day, requires no downtime, and doesn’t affect the operation of your existing system. The controller reads every data point the VRV system generates — temperatures, pressures, frequencies, valve positions, fault codes, operating hours — and streams it to the Nexus iQ cloud platform in real time.
3. Start Monitoring
Within 24 hours of installation, you’ll have a complete diagnostic view of every outdoor and indoor unit on the system. Within two weeks, the platform has enough historical data to establish baseline operating patterns. Within a month, you’ll start receiving predictive insights — the subtle trend changes that no fault code would ever catch.
Check your indoor unit display panel, wired controller, or remote controller. Most Daikin systems display the fault code directly on the unit or controller screen when an error is detected. Note down the code and search it above for the meaning and recommended action.
How do I reset a Daikin fault code?
Turn the unit off at the isolator switch, wait 30 seconds, and turn it back on. If the fault code returns, the underlying issue has not been resolved and you should contact a qualified HVAC technician. Some Daikin systems allow a manual code reset via the controller.
Can I monitor Daikin fault codes remotely?
Yes. The AirNexus Nexus iQ platform connects to Daikin systems and provides real-time fault code alerts. When a fault occurs, you receive an immediate notification on your dashboard — no site visit required. Search all 530+ fault codes here.
This site uses cookies to improve your experience. Learn more