Fujitsu General 25: guided diagnosis

Narrow it down

What you can check, and what needs a technician

Technician verification sequence

For the attending technician — these steps involve live equipment or sealed systems and are not homeowner checks.

1. Confirm the exact model and the manufacturer's own definition for the displayed code, including whether it describes an IPM condition, the DC link, the pre-charge or PFC stage, a drive-module or heatsink temperature, the drive's control, its output, a frequency restriction or a compressor-drive interaction.
2. Establish which of those the code actually reports before anything is changed — the families of cause behind them do not overlap.
3. Review recent building power events and any electrical work, since a drive reports supply conditions before anything else.
4. Review recent board, compressor and service history, including whether a replacement board is the correct part for this model.
5. Separate an incoming-supply condition from a drive-stage condition before any work inside the unit, following correct isolation and stored-energy practice.
6. Inspect the wiring, connectors and terminals between the supply, the control board, the drive and the compressor for heat damage, corrosion and partial seating.
7. Confirm the thermal and ventilation conditions the drive depends on: condenser condition, outdoor fan operation, clearance around the unit and heatsink cooling.
8. Verify the compressor and load interaction where the code involves it, by measurement to the manufacturer's documented method rather than by assumption.
9. Follow the manufacturer-supported inverter diagnostic procedure for this model, including any documented drive test sequence and board configuration requirements.
10. Establish an actual board, module or compressor failure only once the supply, connections, DC side, cooling, control side, output and load have been excluded — and only by measurement to the manufacturer's method.
11. Decide between repair and replacement after that model-specific diagnosis, and establish what caused the failure before any replacement is fitted, so the new part is not exposed to the same condition.
12. Confirm whether the unit uses the current E:xx code set or the legacy two-character set before reading the code against documentation — the maps differ.

About resetting

Switching the system off at its wall switch or isolator once, waiting ten minutes and switching it back on is reasonable, and what happens next is genuinely useful evidence: a drive code that clears and stays away behaves differently from one that returns immediately.

When not to reset: Do not keep resetting it. Each reset returns the drive to whatever condition it protected against, and repeated protection events are capable of causing damage as well as removing the pattern a technician would use.

What this code can point to

The supply arriving at the unit Most likely

This stage sits directly downstream of the building supply, so a supply condition reports here first — and it is established before the stage itself is doubted.

Wiring, terminals or connectors around the drive Most likely

The drive sits between the incoming supply, the control board and the compressor, and every one of those paths runs through connectors and terminals that heat, vibration and servicing affect. A connection is a likely area to inspect before any board or module is suspected, because it is common, inexpensive to correct and frequently the actual cause.

The input / power-factor-correction stage Likely

The stage that conditions the incoming supply before the DC link is directly exposed to supply quality. A condition reported there is investigated from the building supply inwards, because the stage is often reporting what reached it rather than a fault of its own.

The DC-link condition inside the drive Possible

The drive works from an internal DC level created from the incoming supply. When that level sits outside the window the drive accepts, the supply, the input stage, the charging path and the load all decide it — so the reading is a finding about a circuit, not about a component.

Model-specific diagnosis required Possible

Drive codes carry model-specific protection behaviour, documented test procedures and board compatibility rules, and several brands reuse the same characters across generations with different meanings. Where that applies, documentation for the exact model decides what the code reports and what may safely be tested.

A temporary drive protection that may clear Possible

Drives latch protections and hold them, sometimes until a proper restart. Where the code followed a supply event and cleared cleanly on one controlled restart, that is a possible cause worth establishing first because it costs nothing to rule in or out.

The pre-charge / charging path on the DC side Possible

Before a drive starts it brings its DC link up to working level through a charging path. If that sequence does not complete, the code appears at start-up — and the supply, the connections and the charging components are all part of that sequence. This is an electrical charging circuit and has nothing to do with refrigerant charge.

Drive temperature, cooling and heat rejection Possible

Power modules and heatsinks are cooled by the same airflow the condenser uses. A dusty coil, a fan that is not turning, an enclosed outdoor position, recirculating hot air or extreme ambient conditions raise module temperature long before anything inside the drive is at fault, and this is a likely area on any code that appears after some minutes of running.

The drive's own control, sensing or feedback Possible

A drive decides what to do from its own sensing and from the control board's instructions. A sensing circuit, a feedback path or the link between boards can produce a drive fault with the power stage intact, which is why the control side is separated from the power side rather than merged with it.

The drive's output towards the compressor Possible

The output the drive produces depends on the DC level behind it, the connections carrying it and the load in front of it. A code reported on the output is therefore a finding across that path, and the same report is produced by a connection or by the load as by the output stage itself.

The load the compressor presents to the drive Possible

The drive is watching the compressor constantly, and a compressor that is hard to turn, hot, running against a refrigerant-side condition or starting under an unusual load makes the drive object. That is an interaction between two things: it identifies neither of them as failed.

A protection inside the power module operated Possible

A protection event records that a limit was reached and that the module acted on it — which is the protection working. What pushed it there, usually the load, the temperature, the supply or the connections, is the diagnosis, and it is normally somewhere other than the device the protection sits in.

Compressor failure (only after the drive side is excluded) Less common

The compressor may genuinely be at fault, and drive codes are frequently the first sign of it. It is also the conclusion that costs the most to get wrong, so it stands only on measurement taken after the supply, the drive, its output and the connections between them have been excluded.

Which drive condition this code refers to

Power-factor-correction stage condition. On the drive's input / power-factor-correction stage in the outdoor unit, between the incoming supply and the DC link.

The stage that conditions the incoming supply before the DC link reported a fault. It sits directly downstream of the building supply, so supply quality, the incoming connections and that stage itself are all part of what the code covers.