-
Danfoss VFD Not Working in Auto Mode: Compare Before You Touch Anything
-
Dimension 1: Where the Control Comes From — PLC vs. Keypad
-
Dimension 2: Manual Cross-Reference — Model-Specific vs. Generic Parameter Guessing
-
Dimension 3: Measuring Current with a Multimeter — Signal Check vs. Output Check
-
Dimension 4: What Happens on Fault — Trip vs. Soft Reset
-
When to Manual Override and When to Fix the Auto Path
Danfoss VFD Not Working in Auto Mode: Compare Before You Touch Anything
I'm about to say something you probably don't want to hear. When a Danfoss VFD won't run in auto mode but works fine in local mode, the problem is rarely the drive itself. More often it's a misunderstanding of what "auto" actually means — and nobody has put the auto command path side by side with the local path.
I'm a quality/brand compliance manager at an industrial automation distributor. Every drive that leaves my desk before it reaches a customer — roughly 200 drives and related configurations a year — passes through my review. In 2024, we rejected about 11% of first deliveries due to documentation or parameter mismatches. The number-one reason: auto mode failures.
Here's the comparison I actually use: auto mode vs. local mode, side by side. Not "check the drive, then check the PLC." Every dimension gets a direct comparison.
Dimension 1: Where the Control Comes From — PLC vs. Keypad
In local mode, control is obvious. You're looking at the LCP (local control panel). You see "Hand On" or "Off/Reset." You press start, it runs. If it doesn't run, the problem is inside the drive — output, wiring, motor.
In auto mode, control comes from somewhere else. Could be fieldbus (Profibus, Profinet, Modbus), could be a 4-20mA analog signal from a PLC, could be a digital input. If you've done Allen Bradley PLC training, you learned ladder logic and handshake. You probably didn't learn how the drive side interprets that signal.
Here's the comparison most people skip: local mode working only proves the drive hardware is fine. It does not prove the auto signal is reaching the drive.
In March 2023, that distinction cost half a shift. An FC 302 ran perfectly on local test. In auto, it wouldn't start. The electrician checked motor wiring, insulation, thermal overload — all good. Eight hours later, we found the digital input terminal on the fieldbus side was miswired with a shield. The PLC thought it was sending "start," but the drive never got a clean signal. Two drive swaps later, someone finally put a scope on the signal.
Bottom line: if local works, stop opening the motor terminal box. Compare what the auto command looks like at the drive input vs. what the PLC output looks like.
Dimension 2: Manual Cross-Reference — Model-Specific vs. Generic Parameter Guessing
Every Danfoss VFD model has its own parameter map and its own manual. An FC 102 doesn't share a parameter set with an FC 302. The VLT AQUA and VLT HVAC share names but have different defaults. If you're treating "Danfoss defaults" as universal knowledge, you're going to get burned.
Think of a fuel filter cross reference chart PDF. The good ones tell you exactly which filter matches which engine model — and you know to look up the model. If a cross-reference told you "fits all Ford with a fuel filter," you'd throw it away. Same with VFD manuals. An FC 302 fault code 14 and an FC 102 fault code 14 are not the same test.
I've watched a customer troubleshoot an FC 102 using a VLT 2800 programming guide. They changed one parameter thinking it was the auto-start source. It was actually the automatic reset behavior on overvoltage. The server didn't come back, but the drive did learn to restart itself after every voltage dip.
The comparison is clear: auto mode failures need the exact model's manual and parameter map. Local mode failures usually just need generic motor/output inspection — no model-specific parameters required.
So before anything else, confirm your model. FC 102, FC 302, FC 202, VLT 2800, VLT Micro — each has its own chapter. The Danfoss VLT AutomationDrive FC Series Programming Guide (2024 edition, covering FC 102 and FC 302) is the one you actually need to read.
Dimension 3: Measuring Current with a Multimeter — Signal Check vs. Output Check
This is where most people get burned. They put a meter on the drive-to-motor output, see normal, and say "drive is fine." Correct. But auto mode failures are usually upstream of the drive.
Compare that: local mode failure — check motor output current (clamp meter, AC current mode). Auto mode failure — check the auto command signal itself — 4-20mA or 0-10V.
Two rules for how to measure current with a multimeter in this scenario:
- For a 4-20mA loop: measure in series with the loop or use a loop calibrator. Don't rely on a non-invasive clamp unless it's rated for low DC current.
- For a 0-10V signal: measure in parallel with a voltmeter, and disconnect the fieldbus terminal to prevent backfeeding.
If the PLC says 80% speed command (16mA) but you measure 4.2mA at the drive input on an FC 302, the problem isn't the drive — it's the wiring, the PLC output card, or a grounding loop. IEC 61800-5-1 covers safety requirements for drive systems, but it doesn't tell you how to check for signal integrity. That part comes from experience. Or at least from four hours of production time you didn't plan to spend.
Here's the counterintuitive result: auto-mode failures are rarely fieldbus problems. In my 2024 review batch, about 60% of auto-mode complaints were parameter mapping issues. About 25% were wiring. Only about 15% were genuine fieldbus or PLC problems. Most people default to checking the PLC first — which is the worst return on time.
Dimension 4: What Happens on Fault — Trip vs. Soft Reset
In local mode, when a drive faults, you can usually just reset and restart manually. You see what happened on the LCP. You can decide immediately whether to run.
In auto mode, the fault behavior is dictated by the parameter set. The P4-xx group controls fault action — trip, warning, or ignore. If P4-14 or a similar fault-behavior parameter is set to warning, the drive keeps running with a fault. If it's set to trip, it locks out auto mode even on a temporary overload.
This is the biggest comparison: local mode faults usually recover with a soft reset. Auto mode faults are sometimes parameter-driven traps that keep repeating.
If you're doing field quality inspection, look at the parameter log and compare the fault history to the PLC's timestamps. If the PLC says it issued a start at 10:03 but the drive recorded a fault at 10:04, that's a signal problem, not a fault-configuration problem. If someone changed P4-14 on that FC 302 to "warning" to "stop the annoying trips," the drive history will show warnings that nobody noticed.
When to Manual Override and When to Fix the Auto Path
Here's my actual opinion. A lot of industry advice says you should always fix the root cause. I disagree — at least, not always.
If you need the line running before end of shift, manual mode is your safety net. Flip to local, run it by hand, record the real behavior, and chase the auto path later with a clear head.
If you have two or more sites with the same drive model, same symptoms, same "auto doesn't work" complaint — that's systemic. Repair less, fix the configuration more. Check parameter sets, signal wiring, and PLC handshake. The same behavior across sites tells you it's a setup issue, not a random failure.
To be fair — manual mode is tempting. It needs no parameter set, no PLC training, no fieldbus diagnostics. But you also lose the thing automation actually gives you: repeatability, consistency, traceability. That's the whole point of the efficiency argument. Fixing the auto path isn't about being modern. It's about standard processes beating manual work at scale.
Bottom line: compare auto against local. Don't replace the drive. Don't factory reset. Find where the difference lives — parameter, signal, wiring, or PLC side — and let that comparison point you in the right direction. That's how you save four hours, and how you stop burning through replacement drives that were never broken.
Ask about this topic
Share your application conditions and the project stage so the discussion can focus on relevant ratings, interfaces, and documentation.