A motor that stops unexpectedly can interrupt a conveyor, pump, production line or building system. For facility managers, the fastest useful response is not to guess which component failed; it is to collect observations that help a qualified technician reproduce and isolate the problem safely.
A motor control troubleshooting checklist should distinguish what operators observed from what a technician later confirms. That separation prevents an unverified theory from becoming the maintenance record and helps teams recognize patterns across shifts.
Start with the equipment and its function
Identify the equipment name, asset number, location, motor size from existing records, and the process it supports. Note whether the stop affected one motor, an entire line, or multiple devices sharing an electrical supply. If the facility has drawings, operating manuals or a prior repair history, flag their availability without assuming they are current.
Operational impact matters: a failure on a standby pump may be handled differently from a fault that stops an active production process. Include production constraints and approved access windows in the initial service request.
- Asset ID, location, equipment owner and affected process
- Last normal operating time and the first observed interruption
- Whether similar equipment is operating normally
Capture alarms without repeatedly restarting equipment
Operators may see a drive fault code, motor overload indication, PLC alarm, building-management-system event or mechanical interlock message. Record the exact message, time and sequence, preferably from the permitted operator interface. An alarm often identifies a condition, not the root cause.
Repeatedly clearing faults or bypassing safety devices can hide evidence and create hazards. Follow the site’s operating and lockout/tagout procedures. Only qualified and authorized personnel should test circuits, adjust protective settings or open electrical enclosures.
- Exact alarm text or code and screenshot if permitted
- Whether the fault cleared on its own or required an authorized reset
- Other alarms appearing immediately before or after
Describe the conditions before the failure
An intermittent issue may relate to motor starting, a particular speed range, heavy product loading, humidity, washdown, ventilation restrictions or changes in the production schedule. Record what was occurring without claiming that the condition caused the failure.
If an equipment change preceded the problem, identify its date: replacement motor, new VFD parameter set, revised PLC logic, added conveyor section or recently modified electrical distribution. This history can narrow the inspection plan substantially.
- Motor start, stop, speed change or steady operation
- Process load and surrounding conditions
- Recent electrical, mechanical or controls changes
Separate control, power and mechanical symptoms
A stopped motor can result from a control command, a permissive or interlock, a protective-device trip, a power-supply issue, or a mechanical condition. These different possibilities often produce similar operator-level symptoms.
Facility teams should avoid deciding in advance that a VFD, PLC or motor is defective. The contractor can determine suitable diagnostic steps using the equipment documentation, safe test methods and qualified personnel.
Prepare access and the restoration plan
Explain whether the equipment can be isolated, which shifts are affected, and who can authorize a maintenance window. Make applicable drawings, equipment manuals, fault logs and maintenance records available. Agree on who will verify functionality and release the equipment back to operations.
After service, update the incident record with the confirmed cause, corrective action and any follow-up maintenance recommendation. That closes the loop for future technicians without substituting an unproven diagnosis.
What a useful contractor handoff contains
Prepare a short issue summary that begins with the operational symptom and ends with the requested decision. For example: “Conveyor 4 stopped during loaded startup on Tuesday; drive showed this code; the stop affected packing only; the fault recurred on the next shift; approved access is after 7 p.m.” That is more useful than “motor not working.”
Provide maintenance records without editing historical entries. If an operator believes a fault followed a configuration change, label that idea as a hypothesis and identify who made the change. The electrical contractor can then compare event data, supply conditions and control permissions using appropriate procedures. Capture the final recommendation in terms that the operations team can act on, including whether the equipment may return to service and who has authority to approve it.
Frequently Asked Questions
Should operators reset a tripped motor drive repeatedly?
No. Follow established procedures and qualified-personnel guidance. Repeated resets can conceal a fault condition and create additional operational or safety risk.
Does a fault code prove that the VFD needs replacement?
No. Fault codes describe detected conditions; further evaluation may involve the motor, wiring, load, configuration and connected controls.
Discuss Your Facility’s Electrical Needs
For a motor control problem at a Houston-area industrial facility, share the documented symptoms, operating constraints and available asset records when discussing a suitable electrical assessment.
