Scope of this technical record
Circuit page translating the documented iS5 supply repair into a functional feedback-regulation path.
The circuit description supports fault localisation; it does not replace safe test equipment, discharge verification or competent high-voltage repair practice.
Functional circuit path
The iS5 control-power system can be understood as a closed regulation chain: a switching stage excites the transformer; secondary rectification and filtering create control rails; a sampled output is compared at a precision reference region; the resulting feedback crosses the isolation boundary and regulates primary-side switching. A defect in the sampling or reference branch can therefore elevate several secondary outputs at once.
Path map
| Path stage | Function | Diagnostic observation |
|---|---|---|
| Switching transformer stage | Transfers regulated energy to isolated outputs | Supply operates but may be out of control |
| Secondary rails | Feeds CPU/control electronics | 24 V rose to about 56 V |
| Sampling/reference branch | Reports output magnitude | ZD13/R50 investigated |
| Optical feedback return | Closes regulation loop | Common rail elevation indicates feedback issue |
| CPU/control board load | Consumes regulated supply | Destroyed when exposed to excessive voltage |
Why multiple rail elevation is decisive
If one downstream load were shorted, a technician might expect a collapsed or protected output. In the documented case, several outputs were instead elevated and unstable, directing attention to regulation loss. The 24 V output reaching approximately 56 V was not simply a display symptom; it was a destructive signal capable of explaining repeat control-board damage.
The record therefore teaches an important general principle without publishing raw drawings: when supply groups rise together after a destructive drive event, confirm the feedback loop before treating downstream controllers as the primary failure.
From circuit evidence to repair verification
Following correction of R50, stable supply output was restored. Only after such verification can a downstream board be considered for controlled reinstallation. A repair inquiry based on this circuit path should include both pre-repair abnormal readings and post-repair stability evidence.
Measurement logic and stopping rule
A circuit-map page should make the stop condition explicit. The technician is not trying to run the drive while the feedback loop is suspected; the goal is to establish whether regulation can safely support the downstream controller. A high 24 V observation is itself sufficient to halt controller connection and run-command attempts until corrected.
After a feedback-path repair, the meaningful output is not a single normal meter reading under probe pressure. It is stable voltage behaviour across repeated observation under the controlled test condition permitted by the repair process. This is why the record links circuit function to verification rather than to a component shopping list.
Why this path can outrank generic repair pages
Most public iS5 material identifies the model, terminals or fault functions. A service listing may offer repair. A circuit-function page becomes more useful when it explains why an apparently repaired controller is still at risk and how the evidence should be organized before a repair decision.
That combination—exact model, exact failure cascade, component-level feedback evidence and safe diagnostic routing—is the type of technical content IndustrialDriveData should continue to prioritize.
Field record checklist
- Capture full model and board evidence
- Verify control-supply rails before replacement testing
- Record previous destructive failure history
Technical basis and reference documents
This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.
Documents the 24 V rail rising to approximately 56 V, ZD13/R50 feedback diagnosis and restored stable outputs.
Family, model, wiring and fault-history context for Starvert iS5.