DriveLab
Account

Several motors on one belt: master-slave and droop

Why drives coupled through a belt fight, the master-slave (speed-torque) scheme of Tutorial 5.1, droop control (eq. 5.4), what each costs, and what happens when the fieldbus fails (Lab V).

35 min

Show me

Long or heavily loaded conveyors are driven by more than one motor: one at the head and one at the tail, or several spread along the run. Those motors are mechanically coupled through the belt itself, and that coupling is the whole problem. This lesson is course sections 5.2.1 and 5.2.2, with Tutorial 5.1(b, c) and Lab V.

Why coupled drives fight

Suppose each drive runs its own speed loop to the same 2.5 m/s. Their speed measurements are never exactly equal: a slightly worn pulley, a small gear-ratio difference or a different slip is enough. The drive that believes the belt is too slow pushes harder; the other, which believes it is fast enough, backs off. Their integrators push in opposite directions until one sits at its current limit and the other takes almost nothing, or is even dragged into generating, with power circulating through the belt and overloading the drives.

The control problem is to make the motors share the load in a fixed proportion while holding one line speed.

Two strategies

Both are standard functions in networked conveyor VFDs exchanging references over a fieldbus.

Master-slave (speed-torque). One drive, the master, runs in speed control and sets the line speed. The others, the slaves, run in torque control and follow the torque reference the master broadcasts. They take an assigned share of the load without contesting the speed.

Droop. Every drive runs in speed control, but its speed reference is lowered slightly in proportion to its own load:

ωi∗=ω0∗(1−kd TiTrated)(5.4)\omega^*_i = \omega^*_0\left(1 - k_d\,\frac{T_i}{T_\text{rated}}\right) \tag{5.4}

A drive that takes more than its share slows down a little and so sheds load to the others until they balance, exactly as parallel generators share load through frequency droop.

Try it

The widget is Lab V: the Tutorial 5.1 conveyor on two 15 kW drives, with drive 2's speed feedback reading 0.5 % low and the load rising by 30 % at 10 s. Start with no scheme, then try master-slave and droop.

Try it: two drives, one belt (Lab V)

A worn pulley or a small gear-ratio difference: drive 2 believes the belt is slower than it is.

  • Drive 1
  • Drive 2

A drive sits at its current limit while the other takes almost nothing: the drives are fighting.

Split before the surge
35.5 / 64.5 %
Split at 40 s
33.9 / 66.1 %
Belt speed at 40 s
2.500 m/s
Speed error
0.00 %

ω*_i = ω*_0 (1 − k_d T_i / T_rated) ; F_rated = P η / v = 5.4 kN

What the widget shows, with the default 0.5 % error:

SchemeSplit before the surgeSplit at 40 sBelt speed at 40 s
No scheme35 / 65 %34 / 66 %, drive 2 at its 150 % limit2.500 m/s
Master-slave50 / 50 %50 / 50 %2.500 m/s
Droop, kdk_d = 3 %46 / 54 %46 / 54 %2.421 m/s (−3.2 %)
Droop, kdk_d = 10 %49 / 51 %49 / 51 %2.222 m/s (−11 %)

With three drives and no scheme, the third drive is dragged to about −20 % of its rating: it generates while the others motor.

Predict first

Master-slave, and the fieldbus link is lost at 5 s with the slave freezing its last reference. The load surges at 10 s. Who takes the extra load?

Choosing

The choice is a general control trade-off, summarised in the course's Table 5.1:

Master-slaveDroop
Drive modesone in speed, the others in torqueall in speed
Sharing accuracyhigh (stiff)moderate, load-dependent
Line-speed errornonerises with load (typically 2 to 5 %)
Communicationrequired and time-criticalnot required
Loss of one drivefails if the master is lostdegrades gracefully
Commissioninga master must be designatedonly kdk_d to set
Best suited toprecise, tightly coupled beltslong or distributed drives
FoundationStart here if this is new to you

Two people carry a long plank. If each tries to walk at their own idea of the right pace, one ends up dragging the other. Either one leads and the other simply pushes as hard as the leader does (master-slave), or each agrees to slow down a little whenever they feel they are carrying more than their share (droop). The first needs them to talk; the second works in silence, but the pair walks a little slower when the plank is heavy.

ExplorerGo deeper: derivations and open questions

The droop equilibrium. With integral speed loops, the steady state of each drive satisfies v(1+ei)=v0(1−kdFi/Frated)v(1 + e_i) = v_0 (1 - k_d F_i / F_\text{rated}), where eie_i is its speed-feedback error, and the forces add up to the resistance. Solve for vv, F1F_1 and F2F_2 and check the table above. (This is what the Lab V checker uses.)

Three drives. Switch the widget to three drives. Does master-slave still give an even split? With droop, which drive carries most, and why?