Page review information
Edition covered
Field troubleshooting practice — symptom-driven diagnostic trees — n/a — practice reference
Content status
Reviewed
Coverage
Troubleshooting tree index; OEM documentation and site safety procedures govern any intervention.
Last reviewed
August 2026
Primary reference
The official published standard — required for final decisions

Confirm the governing edition, jurisdiction, and project-specific requirements before applying anything on this page.

Scope: Routing page for field diagnosis. It is not an OEM fault manual or an SOP — it points at the right workflow, reference, or commissioning template for the symptom in front of you.

Decision Trees by Symptom

VFD Faults

Overvoltage, overcurrent, overtemp, ground fault, and "faults but I don't know why" — by fault category, routed to the wiring guides.

Motor Won't Start

Does the contactor pull in? Branch from there into control-circuit vs power-side vs mechanical causes.

Analog Signal Faults

4–20 mA and 0–10 V reading zero, full-scale, noisy, or offset — bisect the loop to find where it breaks.

Communication Dropouts

Total vs intermittent, one device vs a segment — triage that routes into the Communications diagnostics workflow.

Motor Symptoms

General motor symptom decision tree — noise, heat, vibration, and performance patterns.

Other Starting Points

Category Where to start
PLC systems Async faults in distributed systems · Machine state model
Safety circuits Safety circuit wiring · Interlocks and permissives
Wiring practice Wiring & installation guides — the underlying wiring for every symptom above

How to use this section

  1. Confirm the machine is safe to inspect and test before anything else.
  2. Identify the dominant symptom category from the table above.
  3. Open the linked workflow or reference and follow it end-to-end — do not skip the “practical sequence” steps even when the fault seems obvious.
  4. Record what was checked, what the measurements were, and what was changed. The commissioning templates contain checklist formats that double as field-notebook templates.
Trust Boundary — Engineering Judgment Required

This site is an independent educational reference for industrial automation standards. It paraphrases and organizes guidance in original language; it is not a substitute for the official published standards, professional engineering judgment, or legal review, and content has not been independently verified against current published editions.

Items marked Review pending await technical review against the identified edition. Items marked Planned have no reviewed source material behind them. Do not rely on this site for compliance determinations, safety-critical design decisions, or legal interpretation.