Trane VRF Systems (United States): How the Codes Read
These codes apply to Trane VRF sold in the United States (208-230 V and 460 V, 60 Hz), which is Mitsubishi Electric City Multi supplied through METUS (Mitsubishi Electric Trane HVAC US); Trane VRF sold in Australia and Europe is a different platform with a different code set, so do not use this page for those units. A fault shows as a 4-digit code on the outdoor unit seven-segment display, the PAR-series MA remote, or the AE-200 / AE-50 / EW-50 centralised controller.
The first digit points you at the system: 1 is the refrigerant cycle (pressure and temperature), 2 is water and drain, 4 is the inverter and power, 5 is a sensor, 6 is M-NET communication, and 7 is system and configuration. A common trap: the 6xxx codes are communication, not a pressure fault, and 6607 usually names the address of the unit that stopped answering.
Which Trane is this? US City Multi outdoor units are the PURY (R2 heat recovery), PUHY (Y heat pump) and PQHY / PQRY (water-cooled) families, with indoor units such as PKFY, PLFY, PMFY, PCFY, PEFY, PFFY and PVFY, and controllers AE-200A / AE-50A, EW-50A and the PAR-series MA remote. The earlier Trane VRF (4TVH / 4TVR, 2013, VRF-SVN34A-EN) was a different Samsung-based platform and is not covered here.
Communication Faults
The codes you will see most often on City Multi callouts. Trane US VRF runs the M-NET communication bus between outdoor units, BC controllers, indoor units and controllers, and most of these come back to wiring, polarity, a terminating resistor or addressing. Codes show on the outdoor PCB 7-segment display, the PAR-series MA remote, or the AE-200 / AE-50 / EW-50 centralised controller. 6607 reports the address of the unit at fault; a 6607 with no source address points at the centralised-control bus path rather than a single unit.
Know about 6607 before the tenant does.
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.
Pressure and Temperature Faults
High and low pressure trips and discharge-temperature protection. Confirm the trip against the gauges and the pressure sensor reading before anything else. On City Multi the pressures are read at the outdoor unit and the BC controller.
Inverter, Compressor and Power Faults
The codes that make your stomach drop. These sit on the inverter and the compressor, the most expensive parts in the outdoor unit. Discharge the DC bus and verify before any connector work. Confirm the incoming three-phase supply first: an open phase (4102) or bus-voltage fault (4220) can look like an inverter failure.
Sensor Faults
Thermistor and pressure-sensor faults on the indoor and outdoor units. These are a quick diagnosis: measure the sensor at the connector against the manual's resistance table, check the wiring, then replace the part.
Drain and Water Faults
Drain pump, float switch and drain-sensor faults on the indoor units. A recurring 2502 is a drain pump error: on float-switch models the float has been held on, and on drain-sensor models the sensor's own self-heating can be misread as immersion.
Tired of chasing City Multi codes?
Nexus iQ monitors discharge temperature, pressures, compressor current and M-NET communication health 24/7. It catches the patterns that lead to fault codes before they trip.
See How It WorksWhat Monitoring Catches That Fault Codes Miss
Fault codes are reactive. By the time a code appears, the fault has already happened. Every system generates dozens of parameters that change continuously: discharge temperature, high and low pressure, compressor current and frequency, and M-NET communication health. In a healthy system these hold consistent relationships. When something starts to degrade, a slow leak, a fouling coil, a communication line picking up noise, the relationships shift long before any single parameter crosses a protection threshold.
Nexus iQ captures this data continuously and compares each system against its own history. When the patterns diverge you get a diagnostic insight, not a lockout.
| Scenario | Without Monitoring | With Nexus iQ |
|---|---|---|
| Slow refrigerant leak | 1301 low-pressure fault on the coldest morning. Emergency callout. | Low-pressure trend flagged weeks earlier. Leak found during scheduled service. |
| Condenser fouling | 1302 high-pressure fault on the hottest day. | High-pressure trend rising. Coil clean scheduled before summer peak. |
| Compressor stress building | 1102 discharge-temperature fault, or a 4250 inverter overcurrent. Compressor risk. | Discharge and current trends flagged months earlier. Planned repair. |
| Communication intermittent | Random 6607 / 6608 faults. Multiple callouts, no pattern found. | M-NET dropouts logged with address and timestamp. Pattern identified on the first visit. |
| Discharge temperature climbing | 1102 discharge-temperature protection stop. | Discharge trend against frequency flagged. Charge or valve checked before the stop. |
The most expensive City Multi fault code is the one that trips on a Friday afternoon in July. Monitoring does not prevent failures, it prevents surprises.
Quick Reference: Every Trane US VRF Code in This Guide
Use this searchable table to find any City Multi code used on Trane US VRF. Type a code (e.g. 1302), a keyword (e.g. pressure), or a category. Click any highlighted code to jump to its detail above.
| Code | Category | Description | Severity |
|---|---|---|---|
| 0403 | Communication | Serial communication error / panel communication error | Medium |
| 0404 | Communication | Indoor unit EEPROM abnormality | Medium |
| 1102 | Pressure/Temp | Discharge temperature fault | High |
| 1301 | Pressure/Temp | Low pressure fault | High |
| 1302 | Pressure/Temp | High pressure fault | High |
| 1500 | Pressure/Temp | Refrigerant overcharge | High |
| 2500 | Drain | Drain sensor submergence | Medium |
| 2502 | Drain | Drain pump fault | Medium |
| 2503 | Drain | Drain sensor (Thd) fault | Medium |
| 2600 | Drain | Water leakage (humidifier) | Low |
| 2601 | Drain | Water supply cutoff (humidifier) | Low |
| 3121 | Inverter/Power | Out-of-range outside air temperature | Medium |
| 4102 | Inverter/Power | Open phase | High |
| 4106 | Inverter/Power | Transmission power supply fault | High |
| 4109 | Inverter/Power | Indoor unit fan operation error | Medium |
| 4115 | Inverter/Power | Power supply signal sync error | High |
| 4116 | Inverter/Power | RPM error / motor error | Medium |
| 4121 | Inverter/Power | Function setting error (outdoor) | Medium |
| 4124 | Inverter/Power | Electric system stopped by damper abnormality | Medium |
| 4220 | Inverter/Power | Abnormal bus voltage | High |
| 4225 | Inverter/Power | Abnormal bus voltage (fan inverter) | High |
| 4226 | Inverter/Power | Abnormal bus voltage (fan box) | High |
| 4230 | Inverter/Power | Heatsink overheat protection | High |
| 4240 | Inverter/Power | Overload protection | High |
| 4250 | Inverter/Power | IPM error / overcurrent | Critical |
| 4255 | Inverter/Power | IPM error / overcurrent (fan inverter) | Critical |
| 4256 | Inverter/Power | IPM error / overcurrent (fan box) | Critical |
| 4260 | Inverter/Power | Heatsink overheat protection at startup | High |
| 5101 | Sensor | Return air / OA-inlet thermistor fault (TH21 / TH4) | Medium |
| 5102 | Sensor | Pipe thermistor fault (TH22 / TH2) | Medium |
| 5103 | Sensor | Gas-side pipe / heat-exchanger-outlet thermistor fault (TH23 / TH3) | Medium |
| 5104 | Sensor | Intake / outside / discharge thermistor fault (TH1 / TH24 / TH4) | Medium |
| 5105 | Sensor | Accumulator inlet thermistor fault (TH5) | Medium |
| 5106 | Sensor | Heat exchanger inlet thermistor fault (TH6) | Medium |
| 5107 | Sensor | Outside temperature thermistor fault (TH7) | Medium |
| 5109 | Sensor | Continuous heating thermistor fault (TH9) | Medium |
| 5110 | Sensor | Heatsink thermistor fault (THHS) | Medium |
| 5111 | Sensor | Continuous heating / BC liquid inlet thermistor fault (TH11) | Medium |
| 5112 | Sensor | Continuous heating / BC bypass outlet thermistor fault (TH12) | Medium |
| 5115 | Sensor | BC controller LEV3 outlet thermistor fault (TH15) | Medium |
| 5116 | Sensor | BC controller LEV3 inlet thermistor fault (TH16) | Medium |
| 5120 | Sensor | DCL temperature sensor fault (THL) | Medium |
| 5201 | Sensor | High pressure sensor fault (63HS1 / BC PS1) | Medium |
| 5203 | Sensor | BC controller intermediate pressure sensor fault (PS3) | Medium |
| 5301 | Inverter/Power | ACCT sensor / inverter current fault | Critical |
| 5305 | Inverter/Power | Fan motor position / RPM error | High |
| 5306 | Inverter/Power | Fan motor position / RPM error (fan inverter 2) | High |
| 5701 | Sensor | Loose float switch connector | Medium |
| 6201 | Communication | Remote controller board fault (nonvolatile memory) | Low |
| 6202 | Communication | Remote controller board fault (clock IC) | Low |
| 6600 | Communication | Duplicate M-NET address | Medium |
| 6601 | Communication | M-NET polarity setting error | Medium |
| 6602 | Communication | M-NET transmission processor hardware error | Medium |
| 6603 | Communication | M-NET transmission bus busy | Medium |
| 6606 | Communication | M-NET internal processor communication error | Medium |
| 6607 | Communication | M-NET no acknowledgement (No ACK) | Medium |
| 6608 | Communication | M-NET no response error | Medium |
| 6831 | Communication | MA remote controller signal reception error (no signal) | Medium |
| 6832 | Communication | MA remote controller signal transmission error (synchronization) | Medium |
| 6833 | Communication | MA remote controller signal transmission error (hardware) | Medium |
| 6834 | Communication | MA remote controller signal reception error (start bit) | Medium |
| 6840 | Communication | A-control communication reception error | Medium |
| 6841 | Communication | A-control communication synchronism not recovered | Medium |
| 6842 | Communication | A-control transmit/receive hardware trouble | Medium |
| 6843 | Communication | A-control communication start bit detection error | Medium |
| 6846 | Communication | A-control start-up time over | Medium |
| 7100 | Config | Indoor capacity total exceeds outdoor limit | Medium |
| 7101 | Config | M-NET capacity code mismatch | Medium |
| 7102 | Config | Indoor unit count wrong or transmission down | Medium |
| 7105 | Config | M-NET outdoor or BC address out of range | Medium |
| 7106 | Config | Attribute setting error | Medium |
| 7107 | Config | Port setting error | Medium |
| 7110 | Config | Outdoor-to-indoor connection signal lost | Medium |
| 7111 | Config | Wireless remote sensor not available | Medium |
| 7113 | Config | CNTYP function-setting error (outdoor or BC) | Medium |
| 7117 | Config | Outdoor model identification error | Medium |
| 7130 | Config | Indoor unit refrigerant family mismatch | Medium |
Getting Started
Knowing what a City Multi code means is step one. Preventing it is step two. Here is how to move from reactive to predictive maintenance on your Trane US VRF systems.
1. Book a Demo
See Nexus iQ monitoring a live City Multi system: real fault history, real diagnostic charts, real trending data on a real building. No slides, no hypotheticals.
2. Connect Your System
A Nexus controller connects directly to the City Multi M-NET bus. It reads every data point the system generates, temperatures, pressures, currents, frequencies, error codes and runtime hours, and streams it to the Nexus iQ cloud platform in real time.
3. Stop Guessing
Within 24 hours you have a complete diagnostic view of every outdoor and indoor unit. Within two weeks the platform has enough baseline data to flag anomalies. Within a month you receive predictive insights, the subtle pattern shifts no fault code would ever catch.
Sources
The code meanings in this guide are the Mitsubishi Electric City Multi self-diagnosis codes, drawn from the following Mitsubishi Electric North America service document. The same 4-digit M-NET codes apply to Trane VRF supplied through METUS.
Trane US VRF fault codes: frequently asked questions
What does Trane error code 6607 mean?
6607 is an M-NET no-acknowledgement (No ACK) error: a device on the M-NET bus did not acknowledge a transmission within the expected window. The address shown alongside 6607 identifies the unit that failed to respond, which is where to start. If 6607 shows with no source address, suspect the centralised-control bus path rather than a single unit. Check the M-NET wiring, polarity, terminating resistors and power. This applies to Trane VRF sold in the United States (Mitsubishi City Multi).
Are Trane's US VRF codes the same as Mitsubishi City Multi?
Yes. Trane VRF in the United States is Mitsubishi Electric City Multi supplied through METUS, so it uses the same 4-digit M-NET self-diagnosis codes. Trane VRF sold in Australia and Europe is a different platform with a different code set.
Can I monitor Trane VRF fault codes remotely?
Yes. The AirNexus Nexus iQ platform connects to Trane / City Multi VRF 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.