UNSTABLE AUX: Unstable Auxiliary Power Before Control-Board Diagnosis

When the display or fault history is not enough

Starvert iS5 product literature provides fault history and trip information during normal controller operation. But if the auxiliary supply is itself unstable or destructive, the controller may not provide trustworthy diagnostic information. A technician can then waste time pursuing keypad, communication or CPU-board symptoms while the upstream supply remains unsafe.

The SV185iS5-4N0 case supplies a practical anchor: several secondary outputs were elevated and variable at the same time, with a 24 V rail peaking near 56 V. This type of evidence justifies moving the investigation to the regulation and feedback circuit before fault-code interpretation.

What qualifies this route

This page is relevant when the unit has experienced combined IGBT/control-board damage, when a replacement control board fails rapidly, or when auxiliary rail readings are clearly high or unstable. It is not meant to assert that every iS5 trip is a supply failure. Normal overload, motor, wiring, parameter or cooling faults remain separate routes.

A complete technical request should include measured supply behaviour, exactly when the board failed, and whether original or donor parts were involved. This improves the probability of diagnosing the true damage boundary rather than buying another victim component.

Symptoms that can be generated downstream

An unstable auxiliary supply can create symptoms that look like controller faults: intermittent keypad behaviour, unreliable fault logging, communication interruption, reset-like behaviour or apparent hardware errors. Without a stable supply baseline, the meaning of those symptoms is uncertain. A replacement controller may only make the failure more expensive.

The appropriate first record is therefore not a software reset guide. It is an evidence check that asks whether the controller has clean, regulated power. Only after this boundary is stable does fault-history interpretation regain diagnostic value.

What this page does not claim

The documented case validates one severe supply-overvoltage route in a specific iS5 model. It does not establish that all Starvert iS5 no-display, fault-memory or communication cases are caused by R50 or ZD13. Cooling, wiring, input power, control configuration and other board failures remain possible.

The value of the page is narrower and stronger: it ensures that a potentially destructive supply problem is not ignored when the evidence matches the documented failure pattern.

Page routing rule

Once regulated control power is proven, the technician may return to fault-history, terminal, keypad or application diagnosis using the ordinary iS5 documentation. Until that boundary is proven, a fault log cannot safely outrank direct voltage evidence. This routing rule keeps a rare but destructive failure from being buried under generic troubleshooting.