Interroll DriveControl 20 vs MultiControl: A Field Guide to Choosing the Right Drive Control (Based on Mistakes I've Made)

Why This Comparison Matters (and Why I'm the One Making It)

I handle drive control orders for a mid-sized systems integrator. Been doing it for about six years now. In that time, I've made my share of costly mistakes—ones I'd rather not repeat, and ones you definitely don't need to make yourself.

A few years back, I specced a DriveControl 20 for a multi-zone sorter application. It looked fine on paper. The budget was tight, and the DC20 was the cost-effective choice. We installed it, commissioned it, and guess what? It struggled. The logic couldn't keep up with the zoning demands. We ended up ripping it out and replacing it with a MultiControl. That mistake cost us about $3,200 in labor, downtime, and reorder fees. Plus a week of project delay. The client wasn't thrilled.

That's when I started keeping a detailed comparison checklist. Since then, I've tracked 47 potential mismatches using that list. So I'm not writing this from a spec sheet. I'm writing it from the school of hard knocks.

Here's the core question: When should you pick the Interroll DriveControl 20 versus the MultiControl? It's not a simple one-size-fits-all answer. It depends on the application complexity, the control architecture, and frankly, how much troubleshooting you're willing to do. Let's break it down dimension by dimension.

Dimension 1: Application Complexity & Control Logic

This is the big one. The dimension where most of the confusion—and most of my past mistakes—lives.

DriveControl 20: Think of this as a smart relay. It's designed for simpler, point-to-point conveyor zones. It handles start/stop, basic speed control, and can interface with a PLC via digital I/O. It's excellent for straightforward accumulation or transportation zones where you need reliable, no-fuss control. It's also the go-to for retrofits where you're swapping out a motor and don't need to rewire the whole cabinet.

MultiControl: This is a full-featured decentralized controller. It has its own logic processing, multiple I/O configurations, and can handle complex zone control, including zero-pressure accumulation, merging, and even some basic sorting logic. It's designed to take orders directly from a higher-level system via fieldbus (like Profinet, EtherNet/IP, or Interroll's own Fieldbus Interface). It essentially acts as a mini-PLC for each drive zone.

The mistake I made? I treated a DC20 like a MultiControl for a complex job. The DC20 just doesn't have the processing power or the I/O count for that. It's like using a bicycle to tow a trailer. It can technically move, but it's not going to end well.

I don't have hard data on the exact processing limits of the DC20's microcontroller versus the MultiControl's (I wish I had tracked that more carefully), but based on the specs and my experience, the rule of thumb is: if a zone needs more than one sensor input (e.g., a photo eye plus a limit switch) or needs to execute conditional logic (e.g., "if zone 3 is full AND zone 4 is empty, release the load"), you should be looking at the MultiControl.

Quick verdict: For simple start/stop zones, the DC20 is often perfect. For any zone requiring conditional logic or sensor fusion, step up to the MultiControl.

Dimension 2: Ease of Commissioning & Setup

This was another painful lesson. In my first year (2017), I ordered a batch of DC20s for a new line. I assumed the setup would be plug-and-play. I was wrong.

DriveControl 20: It's simpler, but it's not simple. The manual (yes, the Interroll DriveControl 20 manual—I've read it cover to cover) has a specific sequence for setting parameters. You need to set the DIP switches correctly for the motor type. You need to wire the sensors (if any) properly. And you need to configure the acceleration and deceleration profiles. A single mistake in the wiring can cause the drive to fault out immediately. The DIP switch settings can be confusing, especially for people (like me) who aren't used to binary encoding.

MultiControl: Paradoxically, the more complex device is often easier to commission for complex jobs. Why? Because the configuration is done via software. You can set up parameters, define logic, and test I/O in a virtual environment before you even connect it to the conveyor. The Interroll MultiControl manual is a beast (it's like 150 pages), but the software wizard for initial setup is surprisingly good. Once you've set the IP address and the bus parameters, the rest is mostly configuration through a web interface.

To be fair, the DC20 is faster to set up for a single, simple drive. You can have it running in 15 minutes. The MultiControl might take an hour for the initial config. But if your system has 30 zones, and 20 of them need unique logic, that DC20 simplicity will turn into a nightmare. You'll be back and forth to the control cabinet, flipping DIPs and testing. With the MultiControl, you just flash the config to each device.

I've never fully understood why some people still insist on DIP switches for complex setups. I suspect it's force of habit. But the time I wasted doing field config on 20 DC20s (roughly 8 hours of labor) more than paid for the upgrade to MultiControls on the next project.

Quick verdict: Single, simple zone? DC20 is faster to set up. Multiple zones or complex logic? MultiControl's software-based configuration saves time.

Dimension 3: System Integration & Scalability

This dimension is where you need to think about the future. What happens when the line needs to expand? What if you need to add a divert? Or integrate a new pallet mover?

DriveControl 20: It's a bit of an island. It can be controlled via simple PLC I/O, but scaling up means more wiring, more I/O modules, and more complexity in the PLC program. It's not designed for a truly distributed control architecture.

MultiControl: This is its superpower. It's built for distributed control. It communicates directly on a real-time fieldbus. You can daisy-chain multiple controllers. You can interface with other Interroll products (like the EC310 drum motor controller or a pallet mover) seamlessly. The control logic is decentralized—each MultiControl makes its own zone decisions based on sensor inputs and commands from the line controller. This makes the system inherently scalable. Adding a zone just means adding a MultiControl, plugging it into the network, and configuring it.

People think cheaper components (like the DC20) always mean a cheaper system. Actually, the opposite is often true at the system level. The assumption is that hardware cost is the biggest factor. The reality is that installation, wiring, and programming labor often dwarf component costs. The MultiControl, despite being 2-3x the price of a DC20, can easily lead to a 10-15% lower total installed cost on a medium-to-large project because it slashes wiring and panel space.

I recall a project for a large e-commerce warehouse. They wanted a modular, expandable system. We proposed MultiControls. The client's internal engineer, who was used to centralized control, pushed back. We eventually compromised by using DC20s on the simple buffer lines and MultiControls on the main sortation and merge zones. It worked, but the integration was a mess. The DC20s were harder to interface with the line control system. If I had to do it again, I'd push harder for a fully distributed MultiControl architecture from the start.

Don't hold me to this, but in my experience, the breakeven point where MultiControl becomes more economical is around 10-15 zones. Below that, DC20s might win on a pure cost-per-point basis. Above that, the labor savings from distributed control start to dominate.

Quick verdict: For fixed, small lines (under 10 zones) that won't change, DC20 is viable. For any scalable or complex system, the MultiControl's integration capabilities are the clear winner.

So, Which One Should You Pick?

I'm not going to give you a simple "A is better" answer, because that's the kind of advice that gets people into trouble (like I was). It depends on your specific project context. Here's my scenario-based guide:

• Scenario 1: Simple point-to-point transport, fixed configuration. You have a straight conveyor moving boxes from point A to point B. No accumulation, no merging, no divert. Budget is tight. Pick the DriveControl 20. It's reliable, simple, and cost-effective.
• Scenario 2: Zero-pressure accumulation line. You need the conveyor to stop accumulating boxes without jamming. Pick the MultiControl. The DC20 simply doesn't have the logic for that. Trying to make it work will lead to frustration and downtime.
• Scenario 3: Complex merge or sortation zone. You need to read multiple sensors, communicate with a host system, and execute conditional logic. Pick the MultiControl. It's the only choice that makes sense.
• Scenario 4: Future expansion is likely. You're building a line that might need to grow or change in the next 3 years. Pick the MultiControl. The scalability it provides is worth the upfront cost.
• Scenario 5: Cost-constrained, but simple project. If the budget is absolutely capped and you can stick to a simple design, the DC20 can work. But (note to self: this is the scenario where I've been burned the most) be ruthless about not letting the scope creep. If they ask for one more feature, push for the MultiControl.

The 12-point checklist I created after my third mistake has saved us an estimated $8,000 in potential rework. If you're an integrator or engineer reading this, take the time to map out the zone logic before you order the controls. That 30 minutes of planning will save you days of trouble. 5 minutes of verification beats 5 days of correction.

And one last thing—always, always verify your IP addresses and bus settings before commissioning. I've seen a $3,000 line come to a halt because someone (me, once) set two MultiControls to the same Profinet device name. That's an embarrassing hour of troubleshooting you don't want.