If your Mitsubishi City Multi system is showing error code 6607, part of your control network has stopped responding.
The short version: a device on the system sent a message to another device and got no acknowledgment back. The equipment is often mechanically fine. The units have simply stopped talking to each other, and the system shuts down the zones it can no longer reach.
What this means for your building
City Multi units coordinate over a control network called M-NET — a daisy-chain that links the outdoor unit, the indoor units, the BC controller, and the remote controllers. Every device on that chain has to be reachable.
When one stops acknowledging, the system reports 6607 and stops the zones it cannot confirm. Tenants notice within hours.
The important thing to understand is that this is usually not an equipment failure. Compressors, coils and fans are frequently in perfect condition. The fault is in the communication path between them — which is good news for your budget.
How urgent is it?
Urgent, but not dangerous. There is no safety risk and no refrigerant escaping. What you have is a comfort and tenant-relations problem that will not resolve on its own.
A 6607 does not clear itself. If it appeared once after a power event and has not returned, it may have been a one-off. If it keeps coming back, something physical is degrading and it will get worse.
What it typically costs
Low to medium — one of the less expensive faults a VRF system can throw.
Most 6607 calls resolve to wiring, terminals, or addressing. That is diagnostic labour and minor materials rather than major components. Someone has to trace a control network across a building, which takes time, but there is usually no expensive part at the end of it.
Cost climbs in one scenario: a damaged transmission board. That happens after surges, or when a marginal connection has been arcing for months because the code was repeatedly reset instead of diagnosed.
What causes it
In roughly the order we find them:
- Loose or corroded M-NET terminal connections — vibration and time work screws loose, and terminals in rooftop or mechanical room environments corrode
- A break in the daisy-chain wiring — often caused by other trades working in ceilings, or damage during tenant improvement work
- A power interruption or surge — units restart out of sequence, or a transmission component is damaged
- A unit that has lost power — one indoor unit on a tripped breaker takes itself off the network
- Recent changes to the system — units added, removed, or replaced without the addressing being updated
- Electrical interference — noise from other equipment corrupting messages on the control line
What happens if you leave it
The affected zones stay down. That is the immediate cost, and in a commercial building it is usually the one that generates calls.
The longer risk is that a marginal connection rarely stays marginal. A terminal loose enough to drop messages tends to get looser, and the fault spreads to more of the chain. What starts as one unresponsive zone becomes several. A fault caught while it affects one branch is a much smaller job than one that has propagated across the building.
What we check
When we respond to a 6607, the diagnostic path is:
- Confirm which device is not acknowledging — the code tells us communication failed; it does not tell us where. Narrowing this is the first job.
- Inspect M-NET terminals at the outdoor unit, BC controller, and affected indoor units for looseness and corrosion.
- Test the daisy-chain wiring for continuity and damage across its run.
- Verify addressing — confirm no conflicts or gaps, particularly if equipment has changed recently.
- Check power to every device on the affected branch.
- Look for interference sources where the control line runs alongside other building systems.
- Test transmission components if the wiring and addressing are sound.
What you can tell us before we arrive
You do not need to open anything or touch the equipment. But three pieces of information make the first visit substantially more productive:
- Which zones are affected? One area, one floor, or the whole building — that alone narrows where on the chain to start.
- Did anything happen recently? A power outage, electrical work, a tenant build-out, roof work, or anything that put trades in the ceilings.
- Has the code appeared before? A first occurrence and a recurring one point in different directions.
Related codes
If you are seeing other numbers alongside 6607, they are worth mentioning — they are related but not the same fault:
- 6600 — Address overlaps. Two devices configured with the same address. A configuration problem, not a wiring one, and common after equipment changes.
- 6602 — Transmission processor hardware error. Points at a hardware fault rather than the wiring between units.
Codes that look similar here lead to genuinely different repairs, which is why “it’s a communication error” is not a diagnosis.
Get it looked at
We are certified on Mitsubishi, Daikin and LG VRF platforms, and we service systems we did not install — including buildings whose original installing contractor is no longer available.
Next business day service for commercial VRF.
Related codes
Error 6600 means two devices on your VRF system share the same address. A configuration fault, not a broken wire — and usually cheap to correct.
Error 6602 is a transmission processor hardware fault. Unlike other M-NET codes, this one usually points at a board rather than wiring or configuration.
Frequently asked questions
What does error code 6607 mean on a Mitsubishi City Multi system?
It is a communication fault. One device on the M-NET control network sent a message and received no acknowledgment back. The equipment itself is often perfectly healthy — the problem is that the units have stopped talking to each other, so the system shuts down affected zones.
Is a 6607 error an emergency?
It is urgent but rarely dangerous. There is no fire or safety risk, and no refrigerant is escaping. The practical impact is loss of heating or cooling in the affected zones, which in a commercial building usually means tenant complaints the same day.
Can I reset a 6607 error myself?
A power cycle sometimes clears it, and that is reasonable to try once. If the code returns, the underlying cause is still present. Repeated resetting masks a fault that is usually getting worse, and it delays the diagnosis rather than avoiding it.
How much does it cost to fix error 6607?
Usually one of the less expensive VRF faults. Most cases trace to wiring, terminals, or addressing, which is labour rather than parts. Cost rises if a control board has been damaged, which can happen after a power surge or if the fault has been left unresolved.
What causes a 6607 error to appear after a power outage?
Power interruptions and surges are among the most common triggers. Units may restart out of sequence, or a surge can damage a transmission component. If the code appeared immediately after an outage or electrical work in the building, that timing is the most useful diagnostic clue you can give us.
What is the difference between 6607, 6600 and 6602?
All three are M-NET communication faults with different causes. 6607 means no acknowledgment was received. 6600 means two devices share the same address, which is a configuration problem. 6602 indicates a transmission processor hardware fault. They look similar but lead to different repairs.
Do you service Mitsubishi VRF systems you did not install?
Yes. We are certified on Mitsubishi, Daikin and LG VRF platforms, and we regularly take on systems installed by other contractors — including buildings whose original installer has gone out of business or no longer returns calls. Next business day service for commercial VRF systems.