Master Slave Motor Control with VFDs: Troubleshooting Zero Speed Sync
In many industrial applications, coordinating multiple motors to run at synchronized speeds is essential. This is often achieved through a master-slave control configuration using variable frequency drives (VFDs). A common setup involves one drive acting as the master, setting the pace, while one or more slave drives follow its command. However, achieving flawless synchronization isn’t always straightforward, especially when mixing different brands or models. A typical issue arises when the master drive’s frequency command drops to zero, but the slave drive continues running or does not immediately stop. This article dives into the technical reasons behind this behavior and provides practical solutions, using the example of a Danfoss FC302 as the master and a Siemens V20 as the slave.
Key Takeaway: When a slave VFD fails to stop at zero speed in a master-slave setup, the root cause often lies in parameter configuration, signal scaling, or electrical noise—not necessarily brand incompatibility.
Understanding Master-Slave Control in VFDs
Master-slave control is a method where one drive (the master) generates a speed reference that is transmitted to one or more slave drives. This can be done via analog signals (0-10V or 4-20mA), pulse trains, or digital communication protocols like Modbus RTU, PROFIBUS, or CANopen. The slave drive then adjusts its output frequency to match the master’s command, ensuring synchronized operation of multiple motors. This is widely used in conveyors, hoists, printing presses, and textile machinery where precise speed matching is critical.
In the scenario described, the Danfoss FC302 is configured as the master, and the Siemens V20 as the slave. The master’s analog output (typically terminal 42 on FC302) is connected to the slave’s analog input (e.g., terminal AI1 on V20). When the master’s frequency is set to 0 Hz, the analog output should drop to 0V (or 4mA), and the slave should interpret this as a zero-speed command. If the slave does not stop, several factors could be at play.
Common Causes for Slave Drive Not Stopping at Zero Speed
1. Analog Signal Scaling and Offset
The most frequent culprit is incorrect scaling of the analog input on the slave drive. Even if the master outputs 0V, the slave might interpret a small residual voltage as a non-zero command. For example, the Siemens V20 analog input might have a default offset or a minimum frequency setting that prevents it from reaching 0 Hz. Check parameters like P0757-P0760 (analog input scaling) on the V20. Ensure that 0V corresponds to 0% speed and that the minimum frequency (P1080) is set to 0 Hz. Similarly, on the Danfoss FC302, verify that the analog output (parameter 6-50) is configured to output 0-10V proportional to 0-100% speed, and that the minimum speed limit (parameter 4-12) is 0 Hz.
| Parameter | Danfoss FC302 (Master) | Siemens V20 (Slave) |
|---|---|---|
| Analog Output/Input Scaling | 6-50 (Terminal 42 Output) | P0757-P0760 (Analog Input) |
| Minimum Reference | 3-02 (Minimum Reference) | P1080 (Min. Frequency) |
| Start/Stop Command | Digital Input or Bus | P0700-P0704 (Command Source) |
2. Start/Stop Logic Configuration
In many master-slave setups, the slave drive’s run command is independent of the speed reference. The slave might be configured to start via a digital input or communication command, and it will continue running as long as that command is active, even if the speed reference is zero. To achieve a true “follow the master” behavior, the slave should be set to start/stop based on the speed reference level. Some drives offer a “flying start” or “speed threshold” function that automatically stops the motor when the reference falls below a certain value. On the V20, you can use the “minimum frequency” setting (P1080) combined with the “skip frequency” or “standby” function. Alternatively, wire a relay output from the master that opens when the master stops, and use it to disable the slave’s run command.
3. Electrical Noise and Grounding Issues
Mixing brands can introduce grounding and noise problems. VFDs generate high-frequency switching noise that can couple into analog signal cables. If the 0-10V signal from the FC302 picks up noise, the slave might see a fluctuating voltage that never truly reaches 0V. Use shielded twisted-pair cables for analog signals, ground the shield at one end only (usually the master side), and ensure proper grounding of both drives. A common-mode choke or ferrite bead on the signal cable can also help. Check that the analog common (0V) of both drives are tied together to avoid ground loops.
4. Parameter Mismatch: Ramp Times and Stop Mode
If the master decelerates quickly to 0 Hz but the slave has a long deceleration ramp, the slave may still be coasting down when the master has already stopped. Ensure that the ramp-down times (P1121 on V20, 3-42 on FC302) are matched or that the slave is set to “coast to stop” when the reference disappears. Also, check the stop mode: if the slave is set to “DC brake” at stop, it might hold the motor at zero speed with current, which can be misinterpreted as still running.
Step-by-Step Troubleshooting Guide
- Verify Analog Signal with a Multimeter: Measure the voltage at the slave’s analog input terminals when the master is at 0 Hz. It should be 0.00V. If it’s above 0.05V, check the master’s analog output calibration and cable shielding.
- Check Slave’s Analog Input Scaling: On the V20, set P0757 to 0V, P0758 to 0%, P0759 to 10V, P0760 to 100%. This ensures a linear 0-10V mapping. Also set P0761 (dead zone) to 0 to avoid ignoring small voltages.
- Set Minimum Frequency to 0: Ensure P1080 = 0.0 Hz on the V20. On the FC302, set 4-12 to 0 Hz.
- Configure Stop Behavior: On the V20, set P0700 to 2 (terminal control) and wire a run command from the master’s relay output. Alternatively, use the “standby” function (P2390) to stop the motor when the speed reference is below a threshold.
- Match Ramp Times: Set P1120 (ramp-up) and P1121 (ramp-down) on the V20 to match the FC302’s ramp times (3-41 and 3-42).
- Improve Grounding and Shielding: Use a dedicated 0V reference wire between the drives, and ensure the motor cables are separated from signal cables.
Advanced Configuration: Using Communication Protocols
For more reliable master-slave control, consider using a digital communication protocol. Both the Danfoss FC302 and Siemens V20 support Modbus RTU. By connecting them on the same RS485 network, the master can send speed commands and start/stop signals digitally, eliminating analog signal issues. This requires setting up the FC302 as a Modbus master (using its built-in PLC or an external controller) and the V20 as a slave. Parameters like baud rate, parity, and address must match. This method ensures precise synchronization and allows for monitoring of slave status.
Pro Tip: When using Modbus, you can implement a heartbeat signal: the master periodically writes a value to the slave. If the slave doesn’t receive an update within a timeout, it automatically stops, providing a fail-safe mechanism.
Real-World Example: Conveyor System Synchronization
In a packaging line, two conveyors must start and stop together. The master conveyor is driven by a Danfoss FC302, and the slave by a Siemens V20. Initially, the slave would continue running for a few seconds after the master stopped. The issue was traced to the V20’s analog input dead zone (P0761) set to 0.2V, which ignored the master’s 0V signal. After setting P0761 to 0 and adjusting the ramp-down time to match, the slave stopped within 100ms of the master. Additionally, a shielded cable with the shield grounded at the FC302 end eliminated sporadic noise-induced movements.
Conclusion
Master-slave control with VFDs from different manufacturers is entirely feasible with careful parameterization and wiring. The key to solving the “slave not stopping at zero speed” problem lies in meticulous analog signal scaling, proper start/stop logic, and robust electrical installation. By following the troubleshooting steps outlined above, you can achieve reliable synchronization and avoid production downtime. Always consult the drive manuals for specific parameter details, and consider digital communication for mission-critical applications.
