Diagnostic workflow

Schneider ATV61 / ATV71 Command and Reference Evidence Workflow

Entry symptom: Drive is ready but does not run, runs from keypad but not terminals, or speed reference is missing/unstable.

Safety controls before proceeding
  • Unexpected start is possible during command testing.
  • Secure the machine before changing command source or references.

Investigation sequence

1

Record local/remote state

Capture whether the drive responds to keypad, terminal or communication command.

2

Photograph terminal wiring

Save digital input, analog input, common and relay wiring evidence before changes.

3

Check control supply

Verify available low-voltage control supply and input common route.

4

Trace run permissive

Check enable, fault reset, external fault and interlock signals.

5

Validate reference

Check analog or communication reference scaling and source selection.

Stop conditions

  • Machine cannot be secured
  • Terminal wiring is undocumented
  • Command source is unknown

Linked records

Evidence intake

Turn this record into a qualified service request

A repair decision is much more reliable when the request includes the exact identity of the drive, the first fault evidence and the machine condition when the symptom appeared.

  • Complete drive type code / MLFB or nameplate model
  • Fault code, fault value and first event before reset
  • When the event appears: power-up, enable, ramp, run, decel or stop
  • Motor/cable connected or isolated during the symptom
  • Visible board, option-card, module and connector identifiers
  • Previous repair history, replacement parts and repeat-failure pattern
Prepare request →