TOSOT Lc: 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 compressor operation, a protection, a start failure, a thermal state, a drive condition or a mechanical condition.
2. Establish which of those the code actually reports before anything is changed — the families of cause behind them do not overlap.
3. Review the history: power interruptions, recent servicing and any part replacement, since each one changes which cause is likely.
4. Separate a building or supply-side condition from a unit-side one before any work inside the unit.
5. Inspect the compressor circuit's wiring, terminals, switching device and connections for heat damage, corrosion and partial seating, following correct isolation and stored-energy practice.
6. Verify the relevant protection and control inputs the code depends on, to the manufacturer's documented method for this model.
7. Assess heat rejection, airflow and the operating load where the code or the evidence implicates them, including condenser condition and outdoor fan operation.
8. Evaluate refrigerant-side and load conditions only where the code supports it, by measurement rather than by assumption.
9. Evaluate the inverter drive and its power stage where the equipment and the code involve them, observing stored-energy precautions.
10. Establish whether the compressor is electrically or mechanically failed only once the supply, connections, starting path, protection, load and drive have been excluded — and only by measurement to the manufacturer's method.
11. Decide between repair and compressor replacement only after that model-specific diagnosis, and establish what caused the failure before any replacement is fitted.

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 compressor code that clears and stays away behaves differently from one that returns immediately.

When not to reset: Do not keep resetting it. Each reset is another start attempt into whatever condition caused the trip, and repeated start attempts and repeated protection trips are themselves capable of causing damage — as well as removing the pattern a technician would use.

What this code can point to

The compressor did not achieve a start Most likely

The system commanded a start and did not get it. That is a finding about the outcome, not about the reason: the supply, the starting components, the drive and the compressor all decide whether a start succeeds, and this stays a symptom until one of them is proven.

Wiring, terminals or connections in the compressor circuit Likely

The compressor circuit runs through terminals, a switching device and connections that carry high current, and heat, vibration and servicing all affect them. A connection is a likely area to inspect before the compressor is suspected, because it is common, cheap to correct and frequently the actual cause.

The starting path — command, switching device, capacitor or drive output Possible

Between the control's decision to start and the compressor turning sit a command, a switching device, a starting or run capacitor on some equipment, and the drive output on inverter equipment. Any of them can prevent a perfectly healthy compressor from starting, which is why the path is proven before the compressor is judged.

The supply arriving at the unit Possible

A compressor is the largest load in the system and the first thing to object when the supply is low, unbalanced, interrupted or unstable. A supply condition is a likely area to consider whenever the code followed a power event or more than one appliance is affected — and it is upstream of everything else here.

Inverter drive or power-stage condition Possible

On inverter equipment the drive decides how the compressor is fed and monitors what it does. A drive fault, its own supply, its cooling and the connections to the compressor can all produce a compressor-labelled code with the compressor undamaged — which is why a drive condition is separated from a compressor condition rather than merged with it.

Temporary protection state that may clear Less common

Systems latch a protection and hold it, and some hold it 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.

Heat rejection, airflow or thermal load Less common

Compressor and discharge temperatures are set by how well the system rejects heat: a blocked or dirty condenser, an outdoor fan not running, restricted airflow, recirculating hot air or extreme ambient conditions raise them long before anything inside the compressor is at fault. This is a likely area on any code that appears after some minutes of running.

Refrigerant-side or operating-load condition Less common

The load the compressor works against is a refrigerant-circuit condition: flow control, a restriction, the charge and the indoor load all change it. A code produced by that condition is a system finding — and it is not by itself an indication that refrigerant should be added, which is a claim only a technician's measurements can support or refuse.

A protection device or limit operated Less common

A protection trip records that a limit was reached and the system acted on it. That is the protection working, not a broken part: what pushed the system to the limit is the diagnosis, and it is usually somewhere other than the component the protection sits on.

Mechanical condition inside the compressor Less common

A compressor can be mechanically restricted, stalled or unable to start, and these codes exist because that happens. It is established by measurement after the supply, the starting path, the connections, the drive and the load have been excluded — because each of those imitates it exactly.

Model-specific diagnosis required Less common

Compressor codes carry model-specific protection behaviour, drive logic and documented test procedures, 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.

Compressor operation feedback or detection Less common

Some codes report that the system could not confirm the compressor was doing what it was told, rather than that it failed. The sensing or feedback path is then part of the picture alongside the compressor, and a detection fault with a running compressor is a recognised outcome.

Which compressor condition this code refers to

Compressor start or start-sequence failure. In the outdoor unit, across the compressor's starting path — the control command, the switching device, the drive output, the connections and the compressor itself.

The system asked the compressor to start and did not get the start it expected. That is a statement about a sequence, not about a component: the command, the switching device, the drive output, the supply arriving, the connections and the compressor are all on that path, and only the last of them needs a compressor.