SC: Output Short Circuit / IGBT Protection Trip

Meaning and first evidence

An SC indication places the investigation at the output short-circuit and IGBT-protection boundary. The operator message is not sufficient to order parts: record stored trace information, the condition of the machine at fault, whether a previous module failure occurred and whether the motor/cable remains connected.

The initial external separation matters because output wiring or motor faults can cause the same protection response as internal semiconductor failure. Only after the external path is safely cleared does the drawing-based internal layer become justified.

Internal mapping after isolation

The reviewed A1000-22KW set identifies multiple isolated auxiliary rails and a current-feedback/protection path. If SC remains with the motor/cable excluded, an investigation should compare output-stage static evidence, driver-support rail symmetry and current-feedback/reference state. Damage in any of these relationships may make a replacement IGBT unsafe to energise.

What makes this better than a generic fault page

A generic page ends with “test motor and IGBT.” This record routes the fault through preserved trace data, external isolation, power-stage comparison, isolated supply evidence and CT/protection feedback before a replacement decision. This is the difference between a fault definition and a repair-qualified technical record.

Escalation boundary

Where safe comparative testing cannot be performed, the correct outcome is specialist evaluation rather than a speculative module purchase. Include full model, trace data, board/module labels, isolation outcome and photographs in any request.

SC must be treated as a protective shutdown, not a reset problem

A short-circuit type output trip indicates that releasing switching again without identifying the cause can be destructive. First preserve the fault record and the operating instant. Next separate external motor/cable causes under qualified procedures. A fault that remains with the external branch excluded increases the probability of an internal output-stage, driver-supply or feedback/protection failure.

The 22 kW circuit evidence supports an internal branch only after that isolation: the multi-rail driver supply must be credible, current/phase feedback routes must be considered and any visible output-stage damage must be linked to its driving/protection circuitry. This prevents an expensive module from being replaced into an unfixed drive.

Fault history first, power-stage suspicion second

On an industrial drive, the displayed protection code is a starting point rather than a component verdict. Capture the fault record and timing before repeated resets. Establish whether the event occurs during control power, immediately after run command, during acceleration, or after a disturbance. Then remove the external motor/cable branch from the decision only through appropriate qualified testing and manufacturer-safe procedures.

Where SC or GF persists after external causes are excluded, the reviewed drawing set supports a more disciplined internal branch: isolated driver-supply rails, CT/current-feedback conditioning, DC-bus or phase scaling, comparator protection and the output power stage. The correct question becomes which evidence separates these branches, not which expensive module should be changed first.

Do not bypass protection as a repair strategy

Any temporary diagnostic method that changes or suppresses a protective input carries a risk of destroying the drive or creating an unsafe motor condition. Such methods belong only in an appropriately protected specialist bench procedure with a documented purpose and a restoration check. They are not field reset instructions and should never be used merely to make a drive run.

Completion is not “fault no longer displayed.” Completion requires restored protection, stable supply and feedback evidence, an understood original cause, and an authorised functional test plan. That standard is particularly important for a high-value A1000 drive where repeat failure can multiply cost and downtime.