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, refrigerant and power supply faults E codes: outdoor PCB, pressure and protection faults L codes: compressor and inverter faults A codes: indoor unit faults (PCB, drain, fan, capacity adapter) F, H and J codes: refrigerant circuit and sensor faults
U Codes: Communication, Refrigerant and Power Faults
U codes on VRV systems cover three different things: transmission faults on the F1-F2 (DIII-NET) line (U4, U9, UA, UF), a refrigerant shortage (U0), and a power supply abnormality (U2). The transmission faults are the ones you will see most often, and most of them come back to wiring: a loose lug, a crossed pair, or a short between F1-F2 and a power leg.
U0
Refrigerant shortage
What it means
The outdoor unit has detected the refrigerant shortage signature: low pressure on the suction line with high superheat at the outdoor coil sensors. The system stops to protect the compressor.
What to check first
Confirm the calculated charge against the piping-length figure for the run, then leak test and weigh in refrigerant if it is low. Check that both stop valves are fully open, since a partly open valve mimics low charge. Rule out a faulty thermistor or high pressure sensor, because the U0 logic relies on those readings. On long runs, recalculate the charge for piping length rather than trusting the nameplate value.
Common cause
A sustained refrigerant shortage that repeats U0 on every run. Also common where the charge was never corrected for a long piping run, so the simple nameplate value left the system short.
Nexus iQ advantage: suction pressure and superheat 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.
Power supply abnormality or instantaneous power failure
What it means
The outdoor unit has detected an out-of-band supply: no zero-cross within 10 seconds, a DC bus voltage drop below 150 to 180 V, or a DC bus over-voltage. The compressor is held off and the system retries after 3 minutes.
What to check first
Measure phase-to-phase and phase-to-neutral at the outdoor terminals. Imbalance must stay under 10% with no frequency drift. If U2 followed a known site brownout or outage, allow the unit to self-restart after the 3-minute stand-by; no hardware action is needed once the supply has stabilised. If it recurs, discharge the DC bus and verify before any connector work, then inspect the DC voltage detection circuit and the inverter main capacitors for a bulge or leak.
Common cause
A faulty supply or phase imbalance at the outdoor terminals. Also a momentary site outage: if U2 clears on the 3-minute timer and the supply has stabilised, no hardware action is required.
Nexus iQ advantage: voltage is logged continuously, so intermittent supply events that only occur during peak demand are captured with a timestamp, the kind you will never catch with a multimeter on a single service visit.
Transmission abnormality between indoor and outdoor
What it means
The VRV system has lost transmission between the indoor units and the outdoor bank over the F1-F2 (DIII-NET) line. The affected indoor units stop until transmission is restored.
What to check first
Trace F1-F2 from each indoor back to the master outdoor and reterminate any loose lug. F1 and F2 are non-polarised, but a short to a power leg is fatal: it takes out the DIII-NET driver on both indoor and outdoor PCBs. Confirm the outdoor unit is powered up and its service LED is blinking at regular intervals, because without outdoor power every indoor on the system reports U4. Cross-check indoor and outdoor address settings, and run auto-address from the outdoor once transmission is restored.
Common cause
A loose or crossed F1-F2 termination, or the transmission line routed alongside power cabling causing noise injection. The outdoor unit left unpowered. An address mismatch after indoor units were added or moved.
Nexus iQ advantage: continuous transmission monitoring detects intermittent dropouts before they become persistent faults. The platform logs every transmission event, so you can see the pattern: is it always at the same time of day, or tied to 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
Transmission fault from another indoor unit in the same system
What it means
The indoor unit reporting U9 has detected a malfunction signal from another indoor unit in the same system. The unit reporting U9 is not itself faulty: it stops while the originating unit is in fault.
What to check first
Wait at least 2 minutes after U9 first appears, then walk every other indoor on the system and read its current code. The originating unit usually carries the primary fault, often a U4 transmission fault or an expansion valve fault; repair that first and the U9 on the neighbours clears after. Test F1-F2 wiring between every indoor and the outdoor, and cross-check addresses if units were recently added or moved.
Common cause
Another indoor unit on the same system is in fault, typically a transmission fault or an expansion valve fault. The unit showing U9 is only reporting the knock-on, so servicing the originating unit clears it.
Nexus iQ advantage: the platform reads the current code on every indoor unit, so it points you straight at the originating fault rather than the units that are only reporting the knock-on. No guessing which of a bank of indoors to open first.
Improper combination of indoor unit and remote controller
What it means
The outdoor unit has detected a transmission abnormality consistent with mismatched indoor or outdoor models, or wrong inter-unit wiring. The system halts.
What to check first
Trace the indoor-outdoor wiring and reterminate any loose lug, verifying F1-F2 against the diagram; a wrong-polarity termination on some controllers throws UA on first power-on. Cross-check the indoor and outdoor model pairing against the official combination list and replace any unit that is not listed. Mixing R32 and R410A units in one system always throws UA. Confirm the wired remote is one of the models listed for the indoor.
Common cause
Wrong inter-unit wiring, or an indoor and outdoor pairing that is not an approved combination. A remote controller that is not compatible with the indoor unit.
Nexus iQ advantage: the platform maintains a full map of every indoor and outdoor unit on the system, so a mismatched pairing or a wrong controller shows up as soon as the unit is connected, before it becomes a callout.
During check operation, the number of indoor units seen on the transmission line does not match the number that responded to a temperature change. The system will not run until check operation completes.
What to check first
Walk the system from each indoor back to the outdoor and confirm the F1-F2 transmission line and the refrigerant pair go to the same indoor; re-pair where crossed. Crossed liquid and gas lines with correct wiring will also throw UF. Open all liquid and gas stop valves on every outdoor module. Then run check operation from the master outdoor: press and hold the RESET button for 5 seconds and allow up to 12 minutes; the system will not run during that window.
Common cause
Indoor-outdoor wiring or refrigerant piping crossed between two indoor units, so the wiring pair and the pipe pair no longer match. A single stop valve left closed. Check operation not run.
Nexus iQ advantage: the platform sees every indoor unit on the transmission line, so a unit that is wired but not correctly paired shows in the Diagnostics view rather than surfacing only when check operation fails on site.
A Nexus controller sits on the system's control network and logs every fault the moment it happens: the code, the unit address, and the time. It lands in the AirNexus app before anyone calls you.
Supplied by AirNexus to HVAC partners across Australia.
9:41AirNexus
Fault · Daikin · 2 min ago
U0
Unit 12 · Level 3 east Logged the moment it happens, with the unit address. Start at the entry above.
Callout likely · check the entry above
Cleared · Yesterday
An earlier fault that cleared on its own
E Codes: PCB, Pressure and Protection Faults
E codes on VRV cover the outdoor PCB (E1), the high and low pressure switch trips (E3, E4), compressor motor lock or overheat (E5), and the outdoor fan motor (E7). The trap with the pressure and protection trips is telling a genuine out-of-range condition apart from a switch or sensor that has failed, so confirm the reading before you condemn hardware.
E1
Outdoor unit PCB abnormality
What it means
The outdoor main PC board on the VRV outdoor module has logged an internal hardware fault. The system stops and the code is reported on the wired remote and the outdoor PCB seven-segment display.
What to check first
Measure phase-to-phase and phase-to-neutral at the outdoor terminals; imbalance must stay under 10% with no frequency drift. Verify the capacity adapter fitted to the outdoor PCB matches the unit, and meter the outdoor fan motor windings against the manual. If E1 clears on a power reset and returns intermittently, sweep nearby plant for VSD, RF or paging-system noise and confirm the earthing is solid. Replace the outdoor main PCB only after supply, capacity adapter, fan motor and noise sources have been ruled out.
Common cause
A faulty supply or phase imbalance, or a capacity adapter that does not match the unit. External electrical noise injected onto a clean-tested board. The outdoor main PC board itself only after the rest has been ruled out.
Nexus iQ advantage: when E1 occurs intermittently, the platform logs the exact timestamp and correlates it with supply events, so you can see whether a power anomaly or a nearby noise source lines up with each occurrence.
The outdoor unit has tripped on high pressure: the high pressure switch opened above 4,170 kPa (41.7 bar / 605 psi), or high pressure control above 3,800 kPa (38 bar / 551 psi) was hit 16 times within 300 minutes. The unit halts.
What to check first
Inspect the outdoor coil for leaf litter, dust and damaged fins and clean it from the inside out, then confirm the fan reaches commanded speed once airflow is restored. Walk the outdoor and confirm both stop valves are fully open, because a back-seated valve trips E3 within seconds of compressor start. Test the high pressure switch: it must be closed at idle pressure, so replace it if it sits open or chatters. If the high side runs hot for the saturated temperature, suspect non-condensables or an overcharge; recover, weigh the charge against the nameplate and reduce to the nameplate value.
Common cause
A blocked or dirty outdoor coil, or insufficient outdoor airflow. A closed or back-seated stop valve. A refrigerant overcharge or non-condensables in the refrigerant, which is a common cause of repeated E3 events on this platform.
Nexus iQ advantage: discharge pressure and condenser approach temperature are trended daily. A gradual increase over weeks tells you the coil is fouling, so you can schedule a clean before E3 trips on the hottest day of the year.
The VRV outdoor unit has stopped because the low pressure sensor read below 230 kPa (2.3 bar / 33 psi) through the protection window, or evaporating temperature fell below the trip line.
What to check first
Inspect the low pressure sensor cable for chafing and seating at the outdoor PCB, and reseat or replace it where continuity fails, before condemning the sensor. Confirm the calculated charge for the piping length and weigh in if it is low, since a sustained shortage repeats E4 on restart. Check every indoor on the system for a filter, grille or coil restriction, because one starved indoor can pull the whole bank into E4 in heating. Verify every stop valve is fully open, and read low pressure on the wired remote against a manifold gauge to confirm the sensor.
Common cause
A refrigerant shortage, or a low pressure sensor cable that has chafed or come loose. Blocked indoor airflow on one or more units. A closed or partly open stop valve.
Nexus iQ advantage: the platform compares the low pressure reading against the value expected for current operating conditions, flagging sensor drift before it causes nuisance trips.
The VRV outdoor inverter has detected that the inverter compressor is not turning at the commanded electrical speed. On 14 to 20 hp classes the code reports for compressor 1 or 2; use monitor mode on the outdoor PCB to identify which.
What to check first
Walk the outdoor and confirm both stop valves are fully open before any compressor work, because a closed liquid valve presents as compressor lock. Mark and disconnect the U, V and W leads at the compressor terminals and verify each phase against the wiring diagram; a swapped phase reads as lock on first start. Meter U-V-W to ground and between phases against the manual. If non-condensables or moisture are suspected, recover, evacuate to a deep vacuum and recharge with virgin refrigerant. Discharge the DC bus and verify with a meter before any connector work on the inverter board.
Common cause
A closed compressor stop valve, or a U, V and W phase connected out of order. Refrigerant contamination. A faulty inverter board or compressor, but only after wiring, valves and charge have been ruled out.
Nexus iQ advantage: compressor frequency is trended against the speed the inverter is commanding. A compressor that stops tracking its commanded speed shows up on the chart, so a developing lock is caught before the hard E5 lockout.
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 abnormality
What it means
The VRV outdoor PCB has detected the outdoor fan motor is locked, has lost feedback, or is drawing locked-rotor current. The system halts to protect the motor and inverter.
What to check first
Inspect the fan motor harness for chafing and the connector at the outdoor PCB for spread or corroded pins, then reseat firmly, since a loose connector throws E7 intermittently in damp weather. Power off and rotate the outdoor fan by hand to clear any obstruction. Disconnect the motor and meter the windings against the manual, replacing it if the windings are open, shorted to frame or out of band. On heat pump platforms, low charge can drag the fan into protection, so confirm the calculated charge if the mechanicals check out.
Common cause
A chafed fan motor harness or a loose, corroded connector at the outdoor PCB. A failed outdoor fan motor, or an obstruction in the fan. On heat pump systems, a refrigerant shortage pulling the fan into protection.
Nexus iQ advantage: fan motor speed is trended, so slowing or erratic fan operation is caught early. A fan gradually losing speed points to bearing wear you can replace at the next scheduled service, not on an emergency call on a 40-degree day.
L codes sit on the compressor and inverter, the most expensive components in the outdoor unit. Not every L code means a compressor replacement: L4 (inverter radiating fin temperature) and some L1 trips come back to supply, charge or airflow, and clear once the external cause is corrected. Discharge the DC bus and verify with a meter before any connector work on these boards.
L1
Outdoor main PCB abnormality
What it means
The VRV outdoor inverter PC board has detected an internal hardware fault: a failed power transistor, a blown fuse, or a failed gate driver. The system halts.
What to check first
Discharge the DC bus and verify with a meter before any connector work. Measure phase-to-phase and phase-to-neutral at the outdoor terminals; imbalance must stay under 10%. Megger each outdoor fan motor to ground, since a failed fan can take the inverter board with it on the next start. Mark and disconnect each compressor phase and meter U-V-W to ground and between phases; a short to ground pops the inverter the moment power returns. Inspect the inverter board fuse for a blow signature and replace it with the rated spare. Replace the board only after supply, fans and compressor wiring have been ruled out.
Common cause
A faulty supply or phase imbalance. A failed outdoor fan motor, or a compressor winding shorted to ground that takes the board with it. A blown inverter fuse, which points to a downstream short rather than the board alone.
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 trips.
The outdoor inverter heat sink (radiating fin) temperature is above its protection threshold. The unit halts to protect the inverter power transistors.
What to check first
Spin the outdoor fan by hand and confirm free rotation, then meter the windings against the manual; a stalled fan is the most direct cause of L4. Inspect the inverter compartment for a dust mat, foreign matter or modified ducting restricting airflow across the heat sink, and clean it. Power off and inspect the heat sink to inverter interface: refresh the thermal paste if it is dried, missing or contaminated, and re-torque the mounting screws in the prescribed sequence. Meter the radiating fin thermistor against the published characteristic and replace it if it is out of band.
Common cause
A faulty or stalled outdoor fan motor. Restricted heat sink airflow from dust or foreign matter. Silicone grease at the heat sink that has dried out or gone missing. A radiating fin thermistor reading out of band.
Nexus iQ advantage: heat sink temperature trended against compressor frequency reveals the thermal load relationship. If the fin temperature starts climbing at a compressor frequency where it was previously stable, it points to restricted airflow or degraded thermal contact before the L4 trip.
The VRV outdoor inverter has measured instantaneous overcurrent on the AC output to the compressor. The unit halts to prevent damage to the inverter and compressor.
What to check first
Discharge the DC bus and verify with a meter before connector work. Megger the compressor windings to ground and meter U-V-W phase resistance; replace the compressor only after wiring, the expansion valve and the inverter board have been ruled out. Measure phase-to-phase voltage at the outdoor terminals, with imbalance under 10%. Power off, isolate, then attempt to spin the compressor shaft where the manual allows, since a mechanically locked compressor throws L5 on first start.
Common cause
A compressor winding fault, a mechanically locked compressor, or a faulty supply or phase imbalance. The inverter board only after the compressor and supply have been ruled out.
Nexus iQ advantage: compressor startup current profiles are captured and compared against baseline. Increasing startup current spikes point to winding degradation, giving weeks or months of warning before L5 permanently trips.
Transmission error between inverter and control PC boards
What it means
The VRV outdoor unit has lost the internal handshake between the control PC board and the inverter PC board. The system halts because compressor commands cannot be confirmed.
What to check first
Discharge the DC bus and verify with a meter before any connector work. Reseat the harness between the control and inverter boards at both ends, and inspect each connector for spread pins or oxidation, since a vibration-loosened pin throws LC after warm runtime. Replace the harness if any core is broken or the insulation has chafed. If LC clears on a power reset and recurs, sweep nearby plant for VSD, RF or paging-system noise and confirm the earthing is solid. Swap one board at a time only after the harness has been confirmed good.
Common cause
A loose or damaged harness between the control and inverter boards, or a spread pin at either connector. External electrical noise. A faulty board only after the harness has been confirmed good.
Nexus iQ advantage: compressor response latency, the time between a frequency command and the actual speed change, is monitored. Increasing latency points to degrading communication between the control and inverter boards.
Nexus iQ monitors discharge temperature, superheat, subcooling, and compressor frequency 24/7. It catches the patterns that lead to fault codes: before they happen.
A, F, H and J Codes: Indoor, Refrigerant and Sensor Faults
These codes cover the indoor units (A1 PCB, A3 drain, A6 fan, AH capacity adapter), the refrigerant circuit (F3 discharge temperature, F6 high pressure or overcharge), and the outdoor thermistors (H9, J3, J6). A3 (drain) and F3 (discharge temperature) are the two you will see most often in Australian conditions.
A1
Indoor unit PCB abnormality
The indoor unit main PCB cannot store or read its internal settings, or has detected a hardware fault during self-check. The unit halts until power is recycled or the board corrected. Reseat every terminal at the indoor unit and check the supply against the nameplate (imbalance under 10%), then power-cycle. Confirm the indoor and outdoor pairing is an approved combination before condemning the board. A power hit can also trigger A1 as a one-off noise event.
The indoor float switch on the S1L circuit has signalled a high water level and the unit has stopped to protect the drain pan. Check the drain pump runs when commanded and pulls water from the pan, and verify the drain run has continuous fall with no traps or blockage. Test the float switch for continuity and reseat the X8A connector. If no field drain pump kit is fitted, the X15A short-circuit jumper must be present and continuous. One of the most common indoor codes in humid coastal areas.
The indoor PCB has detected the fan motor stalled, lost feedback, or drew excessive current, and the unit has halted. Power off and rotate the fan by hand to confirm it spins freely and clear any debris or transit packing fouling the impeller. Inspect the fan motor harness back to the indoor PCB, reseat the connector and replace any chafed wire. Disconnect the motor and check the windings for continuity and the rotor for free spin; replace the motor if the windings are open or shorted to frame.
Capacity adapter or expansion valve motor type abnormality
The indoor unit reports that the capacity adapter is missing on a spare-part PCB, or that the expansion valve motor type set on the board does not match the fitted valve. The unit stops thermo until corrected. Confirm the expansion valve motor type setting (gear type versus direct drive) matches the fitted valve, then power reset. After fitting a spare-part indoor PCB, fit the matching capacity adapter onto the new board; recovery is automatic once it is in place.
The outdoor unit has detected discharge pipe temperature climbing above the protection threshold and has stopped to prevent compressor overheat damage. Low charge causes high superheat and high discharge temperature, so confirm the charge against the nameplate and weigh in after a leak test if it is short. Verify both stop valves are fully open, since a back-seated valve gives instant high discharge temperature on start. Confirm the expansion valve steps through its range, and meter the discharge pipe thermistor against the published characteristic.
High pressure abnormality or refrigerant overcharge
The outdoor unit has logged the refrigerant overcharge signature: high discharge pressure with subcooling above the high band. The system halts and needs the charge corrected. Recover the system and weigh the actual charge against the nameplate, reducing it to the calculated charge. Before condemning the charge, reseat the outdoor air, deicer and subcool thermistor connectors at the outdoor PCB, because a floating thermistor reads below ambient and triggers F6. Compare the high pressure sensor reading on the wired remote against a manifold gauge.
F6 is the overcharge signature, not a spare high pressure switch. Before touching the charge, reseat the outdoor thermistor connectors: a floating thermistor reads below ambient and trips F6 on its own.
H9
Outdoor air thermistor abnormality
The outdoor air thermistor (R1T) input is outside the valid band, so the outdoor PCB cannot trust the ambient reading and the unit stops until the input recovers. Trace R1T from the air sample point to the outdoor PCB and confirm the connector is fully seated. Inspect the connector for green or black corrosion, common on coastal sites. Disconnect R1T and meter it against the published characteristic for the measured ambient, replacing it if out of band.
The outdoor discharge pipe thermistor reads out of band or below the heat exchanger temperature, so compressor discharge protection cannot run. Inspect the thermistor connector for spread or oxidised pins and reseat it. Identify the failed thermistor (R21T or R22T) in monitor mode on the outdoor PCB, disconnect it and meter against the manual's resistance and temperature characteristic, replacing it if out of band and re-clipping firmly to the tube with insulation refitted.
The outdoor heat exchanging deicer thermistor (R7T) reads outside its valid range, so defrost control cannot run reliably and the unit halts. Inspect the thermistor connector for spread or oxidised pins and reseat it. Identify the failed thermistor in monitor mode on the outdoor PCB, disconnect R7T and meter against the manual's resistance and temperature characteristic, replacing it if out of band and re-clipping firmly to the tube with insulation refitted.
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.
The fault code meanings and diagnostic steps in this guide are drawn from the following Daikin service manuals. The VRV manuals are the primary reference; the shared Daikin service manuals carry the same codes and corroborate the meanings.
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 shows the fault in Findings & Insights and the Diagnostics view when the unit reports it, so you can see what is wrong before anyone goes to site. The AirNexus app also sends a push notification when a fault happens. Search the fault code lookup.