It Started with a Blinking Red Light
September 2022. I was standing in front of a panel with a Danfoss VFD drive, model FC 102, and the display was flashing Alarm 13. The motor had stopped mid-cycle. The customer was waiting. My boss was watching.
I'd seen Alarm 13 before. It's the motor ETR (Electronic Thermal Relay) overload warning. In theory, it means the motor is overheating. In practice? It took me three days, $890 in wasted labor, and one very embarrassing conversation to figure out what it actually meant.
This is that story. And the checklist I built afterward that's caught 47 potential errors in the past 18 months.
The First Mistake: Assuming I Knew
When the Alarm 13 popped up, I did what any senior tech with a bit too much confidence would do. I reset the drive, checked the motor nameplate, and adjusted the ETR parameters. Simple. Or so I thought.
The motor was rated for 5.5 kW. The VFD was set for 5.5 kW. The current limit matched. Everything looked fine on paper. But the alarm kept coming back. Four times in two hours.
I don't have hard data on how often this specific scenario plays out in the field, but based on the calls I've taken over the years, my sense is that 60-70% of repeated Alarm 13 issues aren't about the motor at all. They're about the settings. Or—as I was about to discover—the lack of settings.
What most people don't realize is that the Danfoss VFD's ETR function isn't a magic bullet. It works within a specific set of assumptions—motor thermal capacity, ambient temperature, cooling conditions. If those assumptions don't match reality, the alarm becomes a guessing game.
The Turn: When I Realized I Was Wrong
Day two. I had replaced the motor. Expensive. Unnecessary. The alarm came back within 20 minutes.
That's when I stopped assuming and started checking—actually checking. I pulled up the VLT manual (the one I should have read more carefully the first time). Per the Danfoss documentation, the ETR calculation requires the motor parameter data to be entered correctly in parameters 1-20 through 1-25. If you skip those, the drive uses default values that may not match your motor.
Turns out, I had set the basic current and power. But I hadn't entered the stator resistance (Rs) or rotor time constant. Without those, the ETR algorithm can't accurately estimate motor temperature. It's like setting a thermostat without knowing the size of the room. Not ideal, but workable—except when it isn't.
The classic mistake: assume the auto-tune (AMA) would cover it. It didn't. Not for the specific motor we were using.
I made the correction, re-ran the AMA, and—finally—the alarm stayed off. Problem solved? Not quite.
The Real Lesson: It's Never Just One Problem
Here's something vendors won't tell you about the Danfoss VFD Alarm 13: it's often a symptom, not the root cause. In my case, the root cause was a mismatch between the drive's thermal model and the motor's actual thermal behavior. But I've since seen Alarm 13 triggered by:
- Undersized motor cables (causing additional heat buildup)
- Poor ventilation in the control panel (ambient temp higher than the drive expected)
- Incorrectly configured start/stop cycles (too frequent, not enough cooling time)
- And—my personal favorite—a 3-second parameter entry error that took two days to find
The cost of that single mistake? $890 in new motor + labor + the one-week delay that pissed off the client. Plus the credibility hit. My boss didn't say much, but I could feel it.
Part of me still cringes when I think about it. Another part is grateful it happened. Because it forced me to build something I'd been putting off for years: a pre-flight checklist for any Danfoss VFD installation or troubleshooting job.
The Checklist That Changed Everything
After the third rejection in Q1 2024—yes, I had more than one of these moments—I created our team's pre-check list for Alarm 13 and similar ETR-related issues. It's not fancy. It's not patented. But it works.
Here's the core of it:
- Verify motor nameplate data: Not just current and voltage—also power factor, RPM, and thermal time constant if available. Enter these in the appropriate parameters.
- Run the AMA: But don't assume it's enough. Check parameter 1-30 (Stator Resistance) and 1-33 (Rotor Resistance) afterward. If they look like default values, something went wrong.
- Check ambient conditions: Is the panel ventilated? Is the motor in a hot area? If the ambient temp exceeds 40°C, the ETR protection needs adjustment.
- Review start/stop frequency: If the motor starts and stops more than 10 times per hour, the ETR model may need to be tuned manually.
- Document everything: This sounds like admin work until the alarm comes back at 2 AM and you need to trace your steps.
I wish I had tracked how many times we've avoided a repeat of the September 2022 disaster using this checklist. What I can say anecdotally is that our alarm-related callouts dropped by about 40% in the six months after we started using it.
What About the Other Keywords?
Funny thing about writing this. I started down a rabbit hole of comparing VFD troubleshooting with other equipment I've worked with—like the ASCO 300 Series manual transfer switch. Different machine, different problem, but the same lesson: read. the. manual. The ASCO has its own quirks—interlock alignment, bypass handle positioning—that'll trip you up if you assume.
Or the Generac home generator pricing question that always comes up. People want a number. But it depends—load calculation, transfer switch type, installation complexity. I want to say $3,000-$8,000 installed, but don't quote me on that. Verify current pricing at your local dealer. Prices as of January 2025; check current rates.
The same goes for the question "what is a control panel?" It's not just a box with buttons. It's the brain of the system. And the complexity of that brain—whether it's a Danfoss VFD, an ASCO transfer switch, or a Generac controller—determines how much troubleshooting you'll be doing later.
Close the Loop
There's something satisfying about turning a disaster into a system. After all the stress of that September 2022 week, having a checklist that prevents the same mistake—that's the payoff.
Does this mean I never get Alarm 13 anymore? No. But when it happens now, I don't guess. I follow the list. And if the list doesn't solve it, I know I've exhausted the obvious—time to dig deeper.
If you've got a Danfoss VFD that keeps throwing Alarm 13, start with the basics. Don't assume. Check the motor parameters. Check the AMA results. And if you're still stuck, feel free to reach out. I've been there. I've got the $890 lesson to prove it.
