The Motor Was Fine: What 14 Replaced Siemens Motors Taught Me About Protection

I Replaced a Motor I Should Have Diagnosed

In 2017, I swapped out a Siemens motor that had tripped three times in one week. The motor looked fine on the bench. We sent it to a rewinding shop, and their report came back clean: no shorted windings, no bearing damage, no insulation breakdown. I bought the replacement anyway because production was down. Three weeks later, the replacement tripped the same way.

That first mistake cost roughly $1,800 in labor and downtime, and it started a five-year learning curve that I now document for my team. Honestly, the Siemens motor wasn't the problem. The protection system was.

If you've ever watched a new motor fail in its first week, you know the sinking feeling I'm talking about. Trust me on this one: read the trip log before you order a replacement.

The Surface Problem: Nuisance Trips Become Motor Failures

The visible problem was simple. A motor would run for a few hours, trip a breaker, reset, run again. Eventually, someone would say 'maybe the motor is weak' and order a replacement. I made that call 14 times between 2017 and 2024, and I estimate the total wasted budget was around $28,000. Not all of it was purchase cost; a lot of it was overtime, expedited shipping, and the credibility you lose when the fix doesn't hold.

If you're searching for siemens-motor spare parts because a machine keeps tripping, stop. The motor is usually the last thing that fails.

The Deep Cause: We Misread the Protection System

The deeper issue wasn't the motor. It was how we thought about motor protection.

I used to treat a Siemens SIRIUS motor protection circuit breaker as a switch that opens when the current is too high. That's what it does, but it's also a diagnostic device. The 3RV2-style SIRIUS breaker has thermal memory. It integrates the heating that comes from repeated overloads and stalled starts. Reset it too quickly after a trip, and it will trip earlier the next time because the device remembers the previous heat in the motor and in itself. The breaker wasn't being random; it was being careful.

This was true 15 years ago when a motor starter was a contactor, an overload relay, and a prayer. Today, a SIRIUS breaker can communicate with a PLC and give you an actual trip history. The old 'bigger breaker is safer' thinking comes from an era when you couldn't tell the difference between a transient torque spike and a real locked-rotor condition. That era is over.

The communication failure that cost the most

Looking back, the most expensive mistake was a communication failure. I said 'motor protection.' The purchasing team heard 'circuit breaker.' Result: we sized the device for short-circuit protection and ignored overload coordination. We were using the same words but meaning different things. We discovered this when a 7.5 kW motor kept tripping a 25 A breaker that had been selected for the wire size, not for the motor's full-load amps.

I'm not a code expert, so take this with a grain of salt, but as of the 2023 NEC, Article 430 still treats motor branch-circuit protection and overload protection as separate jobs. One device can do both, but only if it's set for the motor's nameplate data.

The drive module is not a substitute for protection

Then there's the modern version of this mistake. On a retrofit in 2022, we used a Siemens single motor module in a SINAMICS S120 drive system. It gave us all the diagnostics we wanted: current, torque, temperature. I convinced myself that meant we didn't need a separate motor protection circuit breaker upstream.

It worked until a cable fault turned into a burned busbar. The single motor module is a drive component. It controls the motor and monitors it, but it doesn't replace the branch-circuit protection and disconnecting means required by the system design. That failure cost about $3,200, and the root cause was my decision, not the module.

The Mechanical Reality: Bevel Gears and Actuators

The same mental shortcut appears in electric actuator design. I've seen actuators with perfectly good motors stall because someone specified a bevel gear reducer using static torque only. The motor tripped on overload because the gearbox was fighting it, not because the Siemens motor was weak. A bevel gear with high breakaway torque can make a good motor look like a warranty failure.

This is why I tell our design team to check the mechanical load before changing the motor. If an actuator stalls at the same rotation angle every time, the issue is probably the gear teeth, the lubrication, or the load profile. Replacing the motor just masks the problem until the next cycle.

Asking 'what happened to Pete Jackson gear drives?' might seem like a strange detour, but it's the same story. The gear drive concept didn't die because it was bad. A specific consumer application faded as engine technology moved on. The same thing is happening in industrial drive trains. We're not going back to the old days of oversized contactors and vague overload settings. The fundamentals haven't changed, but the execution has transformed.

What the Problem Really Costs

Let me be specific about the cost of getting this wrong.

• Fourteen motor replacements between 2017 and 2024, roughly $28,000 in direct waste. Some were unnecessary; all of them were avoidable.
• A three-day production delay in September 2022 after a misapplied protection device caused a motor burn in an electric actuator application.
• One burned busbar because I treated a Siemens single motor module as if it were the safety boundary.
• Countless hours of 'we already replaced that, why is it still tripping?' conversations.

Those are the costs that show up on a work order. The hidden cost is worse: every time you replace a motor and the failure comes back, you lose confidence. People start blaming the brand, the capacitor, the bearing supplier, the line voltage. Anywhere except the actual system design.

The motor is almost never the first thing to fail. The protection, the wiring, or the mechanical load fails first.

What I Do Now: A Short List

I'll keep this short, because the point of the article is the problem, not a product pitch.

1. Read the trip history on the SIRIUS breaker before touching the motor. It will tell you if the trip was overload, phase loss, or short-circuit.
2. Set the overload protection from the motor nameplate, not from the machine's average current.
3. In a drive system, treat the Siemens single motor module as the axis control, and keep the upstream motor protection coordinated.
4. In electric actuator design, calculate peak dynamic torque, not just static torque, before choosing the bevel gear ratio.
5. Keep a maintenance log. The pattern will tell you the root cause.

Take it from someone who spent $28,000 to learn this. The Siemens motor is robust. The real question is whether the protection and the mechanical components around it are giving it a fair chance.