PLC Motor Control — DOL, Star-Delta, Auto/Manual, Trips & Feedback

Typical PLC-controlled DOL motor

Control signal path

Command is not proof of running

A PLC output ON only proves that the controller requested the motor to run. Use independent feedback—contactor auxiliary contact, VFD run status, current switch, pressure/flow proof as appropriate—to verify actual equipment response.

DOL sequence

IF AutoMode AND StartDemand AND AllPermissives AND NOT Trip THEN MotorCommand := TRUE ENDIF IF StopDemand OR Trip OR NOT CriticalPermissive THEN MotorCommand := FALSE ENDIF

Star-delta sequence

Main + Star contactors close after permissives are healthy.
Star timer allows acceleration.
Star opens.
A transition dead-time prevents overlap.
Delta closes for normal operation.

Important: Main/star/delta electrical and mechanical interlocking must prevent Star and Delta contactors from being closed simultaneously. Do not depend on software alone for this exclusion.

Auto / Manual / Local / Remote

Define authority clearly. A common pattern is Local for maintenance/field control and Remote for PLC/HMI control. Auto mode may let process logic generate start demand, while Manual remote mode lets an operator command the motor from HMI subject to trips and critical permissives.

What you should understand first

A robust motor-control design separates command, permissive, interlock, trip and feedback. Each should be represented as a distinct signal or state instead of combining everything into one opaque rung.

Signal and energy boundaries

A PLC is a controller, not the power source for a motor. Separate the low-energy logic side from the field power circuit. Digital outputs often command an interposing relay, contactor coil, valve solenoid or VFD input. The motor power still passes through the MCC/MCCB/contactor/VFD power circuit.

Fail-safe thinking

For critical shutdowns, do not rely only on software logic. Emergency-stop, trip and safety functions may require dedicated safety-rated hardware and a risk assessment. A normal PLC output should not be assumed to provide a safety function unless the architecture is specifically designed and certified for it.

Common mistakes

Using motor command as running feedback
No timeout alarm when commanded ON but feedback stays OFF
Star and delta interlock only in software
Restarting automatically after power restoration without process review
Bypassing trips without a controlled authorization path

Commissioning checklist

Create a cause/effect table for start, stop and trips.
Verify contactor/VFD feedback independently.
Test loss of each permissive while running.
Test power fail and restoration behavior.
Record all bypasses/overrides and make them visible on HMI.

Frequently asked questions

Should overload trip be NC or NO to PLC?

Often a healthy contact is wired so loss of power/wire can be detected, but exact fail philosophy depends on design.

Can PLC directly perform star-delta timing?

Yes for logic, but the power circuit still needs correct interlocking, contactor selection and protection.

Should a motor restart automatically after trip reset?

Only if process risk assessment and operating philosophy explicitly permit it. Many systems require a fresh start command.

Safety / engineering note: These diagrams are conceptual training material. Do not wire mains, safety circuits or field equipment from a generic web diagram. Use the exact PLC manual, device datasheets, applicable standards, isolation practices, risk assessment and a qualified controls/electrical engineer for final design and commissioning.