VFD · FEEDBACK

Why a VFD Needs Fault, Ready and Running Feedback — Not Just a RUN Command

A PLC output saying RUN and a motor actually running are different facts. Feedback closes the state loop.

VFDFaultReadyRunningFeedback

A command is only the intention

The PLC output may be ON while the VFD is faulted, disabled or missing a permissive. For the same reason, an HMI running lamp should normally come from verified drive state rather than the command bit alone.

Closed-loop state
PLC RUN CMD→VFD→READY / RUN / FAULT→PLC decision

Think in at least three feedback states

FeedbackMeaningPLC use
ReadyDrive available to runRun permissive
RunningActual running stateStatus / next sequence step
FaultDrive abnormal conditionBlock run / alarm

Add a feedback timeout after the command

If Running does not arrive within a defined time after RUN is commanded, the PLC can identify a “commanded but not running” condition. This timeout is process logic, not a replacement for safety functions.

Treat fault reset as a separate action

Repeated automatic reset can hide the underlying cause. Separate the reset request and only allow it when the process and restart conditions are understood.

ENGINEER DISCUSSION

How would you handle it in the field?

Challenge the wiring, sequence, interlocks or commissioning assumptions. Posts and replies appear only after moderation.

Server rate limit · moderated before publication

Loading engineer discussion…