Mitsubishi VRF Communication — How It Works
Before you can troubleshoot a Mitsubishi VRF error code, you need to understand the bus the system is talking on. Mitsubishi City Multi systems — the PUHY and PURY series outdoor units that you’ll find on rooftops across every Australian capital — communicate using M-NET, the Mitsubishi Network protocol. M-NET is the spine of the system. Every outdoor unit, every indoor unit, every wall controller, every centralised controller talks to every other device on this single two-wire bus.
There are a few things about M-NET that catch out techs who’ve only worked on Daikin systems. First, it’s polarity-free. Unlike Daikin’s F1/F2 bus, you can wire the two M-NET conductors either way and the system will work. That sounds convenient until you realise that “polarity-free” doesn’t mean “immune to wiring problems.” A reversed pair will still work; a damaged pair, a high-resistance joint, or a section of cable run alongside a power cable will still cause faults.
Second, error codes appear in two different formats depending on the system. Newer City Multi VRF systems display 4-digit codes (1302, 6607, 4220) on the outdoor unit PCB seven-segment display, the MA Remote Controller (PAR-series wall controller), or the centralised controller (AE-200, GB-50, EW-50). Older residential and light commercial splits display 2-digit codes (E6, E9, P1, U2) on the indoor unit receiver LED. This guide covers both, and where the same fault appears in both formats we’ve listed both codes.
Third, M-NET carries a DC bias voltage of around 17V DC with a superimposed AC signal. When you measure with a multimeter, you should see between 7–10V AC across the bus during active communication. Anything significantly outside that range tells you the bus has a problem — either no devices are talking (open bus) or something is loading it down (short, water ingress, faulty PCB).
Mitsubishi error codes are 4-digit on City Multi VRF systems and 2-digit on residential and light commercial splits. This guide covers both formats — where the same fault has both codes, you’ll see them listed together (e.g. E6 / 4102).
Communication Faults — The Most Common Callbacks
If you’re going to memorise five Mitsubishi error codes, make it the ones below. These are the codes that account for the majority of after-hours callouts on City Multi systems — not because Mitsubishi communication is unreliable, but because M-NET buses are physical wires running through buildings and physical wires get damaged, corroded, and pulled on by other trades.
1302
Communication error — outdoor to indoor unit
What it means
The outdoor unit has lost M-NET communication with one or more indoor units. This is the single most common Mitsubishi VRF fault code in the field. The outdoor unit cannot receive temperature data, mode commands, or status updates from the affected indoor unit, so the unit is locked out for safety.
What to check first
Check M-NET wiring continuity from the outdoor unit through to the affected indoor unit. Measure voltage across the M-NET terminals at both the outdoor unit and the indoor unit — you should see 7–10V AC during active communication. If you see 0V, the bus is dead. If you see a steady DC reading with no AC, the bus has lost a device. Inspect every junction box on the run for water ingress — rooftop junctions are notorious for this. Verify indoor unit address settings on the rotary switches; an address conflict will manifest as a 1302 even though the wiring is fine.
Common cause
M-NET cable damaged during construction works (drilling, ceiling tile replacement, partition wall installation). Loose terminal at the outdoor unit caused by vibration over years of operation. Water ingress at a rooftop junction box where the gland has perished. Address conflict between two indoor units after a PCB replacement.
Nexus iQ™ advantage: M-NET communication drops are intermittent and almost impossible to catch on a single site visit. Nexus iQ logs every communication timeout with a precise timestamp — you arrive on site already knowing which indoor unit is dropping out, when it’s dropping, and whether it correlates with an external trigger like a lift starting or building lights switching on.
↓ Back to search
A 1302 communication fault has been intermittent for weeks before it becomes persistent. Monitoring catches the first drop.
1301
Communication error — between outdoor units
What it means
On multi-outdoor configurations — for example two PUHY-P450 units linked together to form a 900 class system — the master outdoor unit has lost communication with one or more sub units. The system cannot share load between modules and will lock out.
What to check first
Check the inter-unit communication cable between outdoor units. Verify the master/sub addressing is correct on the DIP switches (consult the wiring diagram inside the outdoor unit cover). Check for duplicate addresses — this is the most common cause after a PCB replacement, where the new board comes with default DIP switch settings. Inspect the cable for UV degradation if it’s rooftop-mounted in direct sun.
Common cause
DIP switch misconfiguration after a PCB replacement. Inter-unit cable damaged during condenser cleaning with a pressure washer. UV-degraded cable insulation on rooftop installations after 8–10 years of exposure.
Nexus iQ advantage: Multi-module systems are tracked as a single entity. If one module drops out, the platform immediately flags the imbalance in compressor frequency distribution between modules — the kind of detail you’d only catch on site with a meter and a stopwatch.
↓ Back to search
1102
Communication error — MA remote controller
What it means
The MA Remote Controller (PAR-series wall controller) has lost communication with the indoor unit it’s wired to. The user sees a blank screen or a communication error icon on the controller, but the indoor unit itself may still be operating.
What to check first
Check the two-wire connection between the controller and the indoor unit PCB — this is a separate two-wire bus from the main M-NET. Verify the controller address is set correctly (main vs sub controller in dual-controller setups). Power cycle the controller by isolating the indoor unit for 30 seconds and restoring power. If the fault clears and returns, you have an intermittent wiring problem.
Common cause
Loose connection at the indoor unit PCB terminal block, often the result of a previous service visit where the controller was disconnected and the wires were not fully re-seated. Controller address not configured after replacement. Wiring run too long (Mitsubishi spec is 200m maximum on standard cable).
↓ Back to search
6607
Outdoor unit communication bus error
What it means
The main outdoor unit PCB has detected a bus-level fault on the M-NET. Unlike 1302 (which points at a specific indoor unit), 6607 indicates the bus itself is unhealthy — the signal is being corrupted, shorted, or swamped by interference. This is a system-wide fault, not a single-unit fault.
What to check first
Inspect every M-NET connection at the outdoor unit terminal block for tight connections and clean terminals. Disconnect the M-NET bus and measure resistance between the two conductors with all indoor units powered off — should be open circuit. A short or low-resistance reading means there’s a fault on the bus itself. Check the M-NET cable routing — if it runs parallel to a power cable for any significant distance, EMI can corrupt the signal. Mitsubishi spec is minimum 50mm separation from power cables.
Common cause
M-NET cable run too close to power cables, picking up electromagnetic interference from inverter drives, lift motors, or fluorescent ballasts. Short circuit on the bus from a damaged cable or a screw driven through the M-NET conductor pair during a fitout. Failed PCB on one indoor unit dragging the bus voltage down.
Nexus iQ advantage: Bus health is monitored continuously. The platform detects rising bit-error rates and intermittent bus events long before 6607 triggers a hard lockout — giving you weeks of warning to track down the EMI source or replace the degraded cable section.
↓ Back to search
6600
Serial communication error — outdoor PCB internal
What it means
Internal communication failure between PCBs inside the outdoor unit itself — typically between the main control PCB and the inverter PCB. This is similar to the M-NET bus fault but it’s internal to the outdoor unit chassis, not the building wiring.
What to check first
Open the outdoor unit electrical compartment and inspect every ribbon cable and connector between PCBs. Look for corrosion on connector pins (very common on coastal installations), moisture, or physical damage. Check that connectors are fully seated — vibration over years can work them loose. If the cable looks fine, the issue is one of the two PCBs.
Common cause
Condensation on PCB connectors in humid environments or coastal locations. Loose ribbon cable after a previous maintenance visit. Salt-air corrosion on coastal installations (especially anywhere within 1km of the ocean). Rodent damage to internal wiring.
↓ Back to search
Sensor & Temperature Faults
Mitsubishi systems use a lot of thermistors and pressure transducers, and like every electronic component, they fail. The good news is that sensor faults are usually easy to diagnose — you measure resistance, you check the connector, and you replace the part. The trap is when a sensor reading looks wrong but the sensor itself is fine; the actual problem is somewhere else in the system. The list below tells you which is which.
E6 / 4102
Return air thermistor fault (indoor)
What it means
The indoor unit’s return air temperature sensor is open circuit, short circuit, or reading out of the expected resistance range. Without a valid return air temperature, the indoor unit cannot determine room conditions and shuts down to protect itself.
What to check first
Disconnect the thermistor and measure its resistance with a multimeter. Mitsubishi NTC sensors read approximately 10k ohm at 25°C, dropping as temperature rises. If the reading is open circuit or shorted, replace the sensor. Check the connector on the indoor PCB for corrosion or backed-out pins. Verify the sensor is physically present in the return air path — on cassette and ducted units, it’s easy to dislodge during filter cleaning.
Common cause
Sensor wire pinched during installation behind a ceiling tile. Sensor pulled from its mounting clip during routine filter cleaning and never re-seated. Connector corrosion on units in high-humidity locations like commercial kitchens or pool plant rooms.
↓ Back to search
E7 / 4103
Indoor fan motor fault
What it means
The indoor fan motor has failed to start, has stopped unexpectedly, or is drawing current outside the expected range. On DC brushless motors (standard on most current Mitsubishi indoor units), the PCB also monitors hall sensor feedback to verify the motor is actually spinning at the commanded speed.
What to check first
Power off and try spinning the fan wheel by hand. If it’s stiff, has a grinding feel, or wobbles, the bearings are failing. Check for physical obstruction — a loose insulation panel inside the casing is a surprisingly common cause. Measure motor winding resistance across phases. On DC motors, check the hall sensor connector at the PCB. On older AC motors, check the run capacitor for swelling or leakage.
Common cause
Dust and lint buildup on the fan wheel causing imbalance and bearing wear. Run capacitor failure on older AC fan motor units. Hall sensor wire damaged or unplugged after PCB replacement. On cassette units, a loose bearing housing causing the wheel to rub on the casing.
↓ Back to search
4100
High pressure sensor fault (outdoor)
What it means
The high pressure transducer on the outdoor unit is reading out of its expected range. This is distinct from a high pressure protection trip (5302) — 4100 indicates the sensor itself has failed or is reading erratically, not that the system has actually exceeded a pressure threshold.
What to check first
Connect manifold gauges to the discharge service valve and compare the gauge reading to the value the PCB is reporting. If they match, the sensor is fine and the system has a real pressure issue. If they differ significantly, the sensor or its wiring has failed. Check the transducer wiring and connector for corrosion, damage, or loose pins.
Common cause
Failed pressure transducer (typical lifespan 8–12 years on Australian rooftop installations). Damaged wiring at the transducer connector from condenser cleaning. Connector corrosion from exposure to the elements.
↓ Back to search
4105
Discharge temperature thermistor fault
What it means
The compressor discharge temperature sensor is reading out of range. Discharge temperature is a critical safety parameter — without it, the system cannot protect the compressor from overheating — so the unit will lock out as soon as this sensor goes invalid.
What to check first
Check the thermistor strapped to the discharge pipe just downstream of the compressor. Measure resistance and compare to the Mitsubishi service spec for that model. Verify the sensor is properly clamped to the pipe with thermal paste and insulation — a sensor that’s fallen off the pipe will read ambient temperature, which the PCB will flag as out of range during operation. If the sensor is good and properly mounted, but the discharge temperature is genuinely high, you have a real system problem — check condenser airflow, refrigerant charge, and superheat.
Common cause
Thermistor mounting clip corroded and detached from the discharge pipe. Sensor wire damaged by abrasion against the casing edge. Genuine high discharge temperature from low refrigerant charge or a fouled condenser.
Nexus iQ advantage: Discharge temperature is one of the most valuable diagnostic data points on a VRF system. Nexus iQ tracks it 24/7 against compressor frequency and ambient temperature, alerting when it starts climbing weeks before a 4105 or F3-style fault code triggers. You see the trend long before the lockout.
↓ Back to search
4106
Suction temperature thermistor fault
What it means
The suction line temperature sensor is reading out of range. Suction temperature is used together with suction pressure to calculate superheat, which drives the electronic expansion valve control loop. Without a valid suction temperature reading, the EEVs cannot be controlled accurately and the system shuts down.
What to check first
Locate the thermistor on the suction line near the compressor. Measure resistance and check the connector. Verify the insulation around the sensor is intact — if the insulation has deteriorated, the sensor may be reading ambient air temperature rather than suction line temperature, which gives erratic readings rather than a hard fault.
Common cause
Insulation degraded from UV exposure on rooftop installations. Sensor wire chewed by rodents inside the outdoor unit chassis. Connector corrosion at the inverter PCB.
↓ Back to search
4250
Outdoor air temperature sensor fault
What it means
The ambient temperature sensor on the outdoor unit has failed. This sensor drives capacity control calculations, defrost timing in heating mode, and ambient limit protection. The system will operate but with degraded control accuracy until the sensor is replaced.
What to check first
The sensor is typically mounted on the outdoor unit’s air intake side, clipped to the coil guard. Check that it’s physically present and not displaced. Measure resistance — an open circuit reading means a broken wire or failed sensor. Verify the sensor is not exposed to direct sun, which can give false-high readings without triggering a hard fault.
Common cause
Sensor displaced by bird strike or condenser cleaning. Wire broken at the connector entry point from years of vibration. UV degradation of the sensor lead.
↓ Back to search
Compressor & Inverter Faults
Compressor and inverter faults on Mitsubishi VRF systems are the codes that wake you up at night. The cost of getting these wrong is enormous — a misdiagnosed compressor overcurrent that’s actually a wiring fault can lead to an unnecessary $10,000 compressor replacement. Take your time on these. Test electrically before you assume mechanically.
4220
Compressor overcurrent
What it means
The inverter has detected current draw on the compressor motor that exceeds its safe operating limit. This is a critical protection trip — sustained overcurrent will damage both the compressor motor windings and the inverter IGBT modules, so the system locks out immediately and requires investigation before reset.
What to check first
Power down and isolate the unit. Megger the compressor windings phase-to-phase and phase-to-ground — minimum acceptable insulation resistance is 1 megohm, ideally above 10 megohms. If insulation is low, the compressor needs replacement. If insulation is good, check the suction superheat — if it’s below 3K, you have liquid slugging and that’s the cause. Check incoming supply voltage at the outdoor unit terminals under load — low voltage causes high current draw and can trigger 4220 on a perfectly healthy compressor. Verify electronic expansion valve operation on connected indoor units.
Common cause
Compressor motor winding insulation breakdown after years of operation, often accelerated by moisture in the refrigerant circuit. Liquid slugging from a stuck-open expansion valve. Low supply voltage during peak demand on undersized cabling. Ground fault in the compressor motor.
A compressor overcurrent fault left unresolved leads to compressor failure. Replacement: $8,000–$15,000 on a City Multi system, plus labour and refrigerant. The fault code is the cheap part.
Nexus iQ advantage: Compressor current draw is logged against compressor frequency continuously. When the current-to-frequency ratio starts trending upward, it indicates increasing mechanical resistance — visible on the diagnostic chart months before 4220 trips. That’s the difference between a planned compressor replacement and a Friday afternoon emergency.
↓ Back to search
4225
Inverter heatsink overheat
What it means
The inverter heatsink temperature has exceeded the safe operating limit. On most City Multi outdoor units, the inverter is cooled by refrigerant flowing through an integrated plate heat exchanger — so heatsink overheat usually points at a refrigerant-side problem rather than a fan or airflow issue.
What to check first
Check the heatsink fins for dust accumulation. Verify the heatsink cooling fan operation if equipped. Most importantly, check refrigerant charge — if subcooling at the outdoor unit liquid service valve is below 5K, the inverter heat exchanger isn’t getting enough liquid refrigerant for cooling. Verify the heatsink thermistor is properly seated; a thermistor that has fallen off will cause erratic readings.
Common cause
Slow refrigerant leak reducing the cooling capacity available to the inverter heat exchanger. Dust-clogged heatsink fins on units installed in dusty locations like construction sites or near unsealed roads. Failed heatsink fan on units that use forced-air cooling.
Nexus iQ advantage: Inverter temperature trending catches overheating patterns weeks before the fault code triggers. One scheduled cleaning visit prevents a $3,000 inverter board replacement — and the platform tells you exactly when the cleaning is needed.
↓ Back to search
An inverter board replacement costs $3,000. A heatsink cleaning costs $200. Monitoring tells you which one you need.
5101
Compressor startup failure
What it means
The compressor failed to start within the expected time after a start command. The inverter sent the run command, expected to see current draw and rotor position feedback, and didn’t. After several retries the system locks out and reports 5101.
What to check first
Check the compressor wiring at the inverter output terminals — loose or corroded terminals can prevent startup. Measure voltage at the inverter output during a start attempt. Try spinning the compressor by hand (with power off) to check for a locked rotor — a mechanically seized compressor obviously won’t start. Check the crankcase heater operation; on units that have been off for a long time in cold weather, refrigerant migrates into the compressor sump and causes hydraulic lock at startup.
Common cause
Liquid refrigerant migration to the compressor crankcase during long off-periods, particularly in winter or when the unit has been isolated for renovation works. Failed crankcase heater. Locked compressor rotor after a power outage during operation. Loose terminal at the inverter output.
↓ Back to search
5102
Compressor over-speed protection
What it means
The compressor frequency has exceeded the maximum allowed limit. This usually means the system is trying to deliver more capacity than it can — the compressor keeps ramping up trying to meet demand but the refrigerant circuit can’t move enough heat, so the inverter trips on over-speed protection.
What to check first
Check refrigerant charge first — an undercharged system will run the compressor flat-out to try to meet capacity. Check subcooling and superheat. Look for restrictions in the refrigerant circuit: a partially closed service valve, a blocked filter drier, a kinked pipe. Check that all electronic expansion valves on connected indoor units are functioning correctly.
Common cause
Slow refrigerant leak. Service valve not fully opened after maintenance. Stuck-closed expansion valve on one indoor unit reducing system capacity. Oversized indoor load relative to outdoor unit capacity (a design or commissioning mistake).
↓ Back to search
5301
Low pressure fault
What it means
Suction pressure has dropped below the minimum protection threshold. The system has shut down to prevent compressor damage from low-pressure operation, which causes oil return problems and motor cooling issues.
What to check first
Check refrigerant charge — this is the most common cause. Look for restrictions: blocked filter drier, kinked liquid line, partially closed service valve, restricted strainer at an indoor unit. Verify expansion valve operation on connected indoor units. Check the evaporator coils for ice buildup, which restricts airflow and drops suction pressure. On heat pump systems in heating mode, check the outdoor coil for blockage by snow or debris.
Common cause
Slow refrigerant leak at a flare connection or a brazed joint. Blocked filter drier after years of service. Stuck-closed expansion valve. Indoor coil iced over due to insufficient airflow (blocked filter, closed damper).
↓ Back to search
5302
High pressure fault
What it means
Discharge pressure has exceeded the high-pressure protection threshold. The system locks out immediately to prevent compressor damage and potential refrigerant release through the relief valve.
What to check first
Check the condenser coil for blockage by leaves, dirt, cotton from nearby trees, or bird nesting material. Verify all condenser fans are running and rotating in the correct direction. Check refrigerant charge — an overcharged system caused by a top-up without measuring subcooling is a very common cause. Measure subcooling at the liquid service valve; if it’s above 12K, the system is overcharged. In heating mode, check the indoor coils for blockage causing high condenser pressure on the indoor side.
Common cause
Blocked rooftop condenser coil that hasn’t been cleaned in 12+ months. Overcharged system after a top-up. Failed condenser fan motor. Recirculation of hot discharge air from poor outdoor unit installation in a confined plant room.
↓ Back to search
Monitoring catches problems before they become fault codes.
Nexus iQ tracks discharge temperature, compressor frequency, superheat, subcooling, and M-NET communication health 24/7 on every Mitsubishi City Multi system it’s connected to. Catch the trend, not the lockout.
See How It WorksSystem & Operation Faults
The codes below are the ones you’ll see less often but should still recognise on sight. Several — particularly P4 (drain) and P6 (freeze) — are extremely common in Australian humid coastal conditions.
P1 / 0403
Intake sensor fault (indoor)
The indoor unit’s intake air thermistor is open or out of range. Check resistance, check the connector at the indoor PCB, and verify the sensor is in its mounting clip in the return air path. Common cause: sensor displaced during filter cleaning.
↓ Back to search
P4 / 0900
Drain sensor / drain pan float switch activated
The condensate drain pan float switch has risen, indicating a blocked drain line or failed condensate pump. This is one of the most common indoor unit faults in Australian humid coastal installations. Algae buildup in the drain line is the usual culprit. Clean the drain pan and line, verify the pump operation, and use drain pan treatment tablets at the next service to prevent recurrence.
↓ Back to search
P6 / 2500
Freeze / overheat protection
The indoor coil temperature is below the freeze protection threshold (cooling mode) or above the overheat threshold (heating mode). In cooling, this is almost always insufficient airflow — check the filter, the dampers, and the fan motor. In heating, check for indoor airflow restriction or a stuck-open expansion valve flooding the coil.
↓ Back to search
E9 / 2502
Electronic expansion valve fault
The indoor unit’s electronic expansion valve has failed to respond to a step command, or the valve drive circuit on the PCB has detected a fault. Check the EEV coil resistance (should read approximately 46 ohms across each pair). Check the valve drive connector at the indoor PCB. A stuck valve body can sometimes be freed by power cycling the unit, which forces the valve through its full travel.
↓ Back to search
U1 / 0100
Protection device activation
A safety protection device has activated — this is a general code that covers high pressure switch, thermal fuse, or other hard-wired safety devices. Cross-reference with any other codes shown on the controller to identify the specific protection. Check the high-pressure switch first if no other code is present.
↓ Back to search
U2 / 0101
Power supply fault
The outdoor unit has detected an abnormal supply voltage condition — under-voltage, over-voltage, phase loss, or phase imbalance on three-phase units. Measure all phases at the outdoor unit terminals (not at the switchboard). Check for loose neutral connections at the switchboard. On long cable runs, check voltage drop under load.
↓ Back to search
What Monitoring Catches That Fault Codes Miss
Mitsubishi error codes tell you what’s broken. They don’t tell you what’s about to break. That distinction is the difference between reactive and predictive maintenance — and it’s the difference between an emergency callout on a Friday afternoon and a planned service on a Tuesday morning.
Every Mitsubishi VRF system generates dozens of operating parameters that change continuously: discharge temperature, suction pressure, superheat, subcooling, compressor frequency, fan speed, expansion valve position, M-NET bus health. In a healthy system, these parameters maintain consistent relationships. When something starts to degrade — a slow refrigerant leak, a fouling condenser, an inverter heatsink starting to clog with dust — the relationships shift. Tiny changes at first. Half a degree here, a few hertz of extra compressor frequency there. No fault code triggers because no single parameter has crossed a protection threshold. But the trend is unmistakable when you have the data.
Specific patterns Nexus iQ catches on Mitsubishi systems:
- Compressor discharge temperature trending up over weeks — the system is overheating, and 4225 or 4105 is coming. Schedule cleaning or charge investigation now.
- M-NET communication drops happening intermittently — the wiring is degrading or interference is increasing. The 1302 fault is weeks away. Track down the cause now.
- COP degrading from 4.5 to 2.8 over a season — no fault code triggers, but energy bills have doubled. The system is silently failing efficiency targets.
- Superheat and subcooling drifting from baseline — expansion valve performance is degrading. E9 / 2502 will follow.
- Runtime hours increasing for the same load — the system is working harder for the same outcome. Capacity is degrading and you have time to investigate before tenants complain.
Mitsubishi error codes tell you what’s broken. Nexus iQ tells you what’s about to break.
| Scenario | Without Monitoring | With Nexus iQ |
|---|---|---|
| Compressor stress building | 4220 overcurrent fault. Emergency callout. Compressor replacement risk. | Current-to-frequency trend flagged 8 weeks earlier. Diagnosed and repaired during scheduled service. |
| Inverter heatsink fouling | 4225 lockout. System down for hours. Risk of inverter board damage. | Heatsink temperature trend flagged. Cleaning scheduled before summer peak. |
| M-NET intermittent communication | Random 1302 faults. Multiple callouts. No pattern identified. | Bus dropouts logged with timestamps. Root cause isolated on first visit. |
| Slow refrigerant leak | 5301 low pressure fault on the hottest day. Tenants in 32°C offices. | Subcooling trend flagged 6 weeks earlier. Leak found during scheduled service. |
| Identifying which unit failed | Guessing which unit in a 32-unit system caused the fault. Hours of investigation. | Nexus pinpoints the exact indoor or outdoor unit instantly with full data history. |
| Cost of failure | $2,000–$5,000 emergency callout. $8,000–$15,000 if compressor fails. | $200 preventive service. Compressor stress caught months before failure. |
The most expensive Mitsubishi fault code is the one that triggers on a Friday afternoon in January. Monitoring doesn’t prevent failures — it prevents surprises.
Quick Reference Table
Use this searchable table to quickly find any Mitsubishi VRF or City Multi error code. Type a code (e.g. 1302), a 2-digit code (e.g. E6), or a keyword (e.g. pressure) to filter the results. Click any code to jump to the detailed section above.
| Code | Category | Description | Severity |
|---|---|---|---|
| 1302 | Communication | Outdoor to indoor communication error | Critical |
| 1301 | Communication | Outdoor to outdoor communication error (multi) | Warning |
| 1102 | Communication | MA remote controller communication error | Warning |
| 6607 | Communication | Outdoor unit communication bus error | Critical |
| 6600 | Communication | Serial communication error (outdoor PCB internal) | Warning |
| E6 / 4102 | Sensor | Return air thermistor fault (indoor) | Warning |
| E7 / 4103 | Sensor | Indoor fan motor fault | Warning |
| 4100 | Sensor | High pressure sensor fault (outdoor) | Warning |
| 4105 | Sensor | Discharge temperature thermistor fault | Critical |
| 4106 | Sensor | Suction temperature thermistor fault | Warning |
| 4250 | Sensor | Outdoor air temperature sensor fault | Info |
| 4220 | Compressor | Compressor overcurrent | Critical |
| 4225 | Compressor | Inverter heatsink overheat | Critical |
| 5101 | Compressor | Compressor startup failure | Warning |
| 5102 | Compressor | Compressor over-speed protection | Warning |
| 5301 | Refrigerant | Low pressure fault | Critical |
| 5302 | Refrigerant | High pressure fault | Critical |
| P1 / 0403 | System | Indoor intake sensor fault | Info |
| P4 / 0900 | System | Drain pan float switch activated | Info |
| P6 / 2500 | System | Freeze / overheat protection | Warning |
| E9 / 2502 | System | Electronic expansion valve fault | Warning |
| U1 / 0100 | System | Protection device activation | Warning |
| U2 / 0101 | System | Power supply fault | Warning |
Getting Started
Knowing what a Mitsubishi error code means is step one. Preventing it from happening is step two. Here’s how to move from reactive to predictive maintenance on your City Multi systems.
1. Book a Demo
See Nexus iQ monitoring a live Mitsubishi VRF system — real fault history, real diagnostic charts, real trending data on a real building. We’ll show you exactly how the platform detects developing issues weeks before they trip a fault code. No slides, no hypotheticals.
2. Connect Your System
A Nexus 32 controller connects directly to the Mitsubishi M-NET protocol. Installation takes under a day, requires no system downtime, and doesn’t affect the operation of your City Multi controllers or BMS integrations. The controller reads every data point the VRF system generates — temperatures, pressures, frequencies, valve positions, error codes, runtime hours — and streams it to the Nexus iQ cloud platform in real time.
3. Stop Guessing
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 baseline data to start flagging anomalies. Within a month, you’ll receive predictive insights — the subtle pattern shifts that no fault code would ever catch.