Access Official Technical PDF

Share Summary:LinkedInEmail

Effective servo drive selection starts with the requirements of the complete motion system, not a single drive specification. Motor type, feedback device, command method, communications network, installation format, and operating environment all influence compatibility and integration effort. Considering these factors together helps engineers and system integrators narrow options before detailed commissioning begins.

Start with the motor and motion requirements

Servo systems may use brushed DC or brushless AC and DC motors, as well as linear and rotary motors, AC induction motors, and voice coils. Commutation may be trapezoidal or sinusoidal. Some drives support several motor technologies, with configuration changes determining how a particular drive operates with a selected motor.

Define the application’s control needs early. The required command may come over a network, through a ±10 V analog signal, through PWM and direction, or through another supported method such as step and direction or encoder following. Available operating modes vary by drive family. Analog drives, for example, may provide current, velocity, or duty-cycle operation, while digital drives can offer configurable current, velocity, and position loops.

Power and current requirements also need to be checked against the drive’s ratings and the system supply. Compare both peak and continuous requirements rather than relying on a single power figure. These values are listed differently across product families, so consult the applicable drive documentation when comparing candidate models.

Match feedback to the control architecture

Feedback selection affects both compatibility and control capability. Common options include Hall sensors, incremental encoders, resolvers, tachometers, and sine/cosine encoders. Some digital drive families also support absolute encoders, including specified Heidenhain EnDat and Stegmann Hiperface interfaces. Availability depends on the drive model and, in some cases, the selected firmware.

For a single feedback loop, the primary feedback device may provide the information needed for control. Some digital drives also support auxiliary feedback for dual-loop control. This can be relevant when the system design calls for feedback from more than one point, but the required devices and configuration should be verified against the selected drive’s documentation.

It is also important to identify where feedback processing takes place. In a sinusoidal analog-drive arrangement, the external controller tracks motor rotor position and supplies the drive with specialized sinusoidal command signals. Other drive configurations handle commutation and feedback within the drive. That architectural difference affects controller requirements, wiring, and commissioning.

Choose a communications network for the application

Network choice is a system-level decision. Supported options include CANopen, EtherCAT, RS-232, and RS-485. The appropriate option depends on factors such as required bandwidth, update rate, performance, and cost, as well as the controller and other devices already used in the machine.

CANopen and EtherCAT provide standardized communication approaches for drive networks. The described EtherCAT interfaces use CoE and the CiA 402 drive profile. RS-232 and RS-485 options use a proprietary serial protocol for drive commands. Custom digital-drive configurations may also be developed for other communication types, such as Ethernet TCP/IP or Ethernet Powerlink; availability should be confirmed for the specific application.

For multi-axis systems, consider the network topology and the amount of control and I/O required at each axis. Some EtherCAT drive configurations support a node and sub-node arrangement, allowing multiple axes to connect through a single network node. The exact configuration and supported axis count depend on the drive family and system design.

Consider controller placement and integration

Motion control can be distributed between a PC, a dedicated motion automation controller, and the drives themselves. A PC-based controller may run motion and automation programs, while an embedded controller can handle time-critical tasks closer to the drive network. Programs may also be divided so that faster control runs on the embedded controller while an HMI or slower functions run on a PC.

Function-block programming based on IEC 61131-3 is one approach to developing motion and automation programs in a graphical environment. The controller arrangement should be evaluated alongside update-rate needs, application complexity, I/O requirements, and the desired location of machine logic. These considerations help determine whether networked drives, analog-command drives, or a combination is the appropriate fit.

Select a mounting format and environmental rating

Panel-mount drives are enclosed for installation in a control system, while PCB-mount drives are designed for embedded integration. Board-level drives can reduce wiring between the drive and the host system, and mounting cards can simplify connections during prototyping or final installation. Vehicle-mounted controllers are another option for mobile electric platforms, with rugged enclosures and application-oriented I/O.

Environmental conditions can narrow the selection further. Extended-environment drive families are designed for wider ambient temperature ranges and enhanced resistance to shock and vibration. The stated limits differ between product families, so engineers should check the model-specific ratings rather than treating an extended-environment designation as a universal specification. Compliance-related design considerations and testing to listed standards should likewise be confirmed for the intended product and project.

A practical servo drive selection checklist

  • Motor: Identify motor type, commutation, and required operating mode.
  • Electrical requirements: Check supply voltage and peak and continuous current needs.
  • Feedback: Confirm the primary device, any auxiliary feedback, and compatibility with the drive.
  • Command and control: Specify network commands, analog signals, PWM, step and direction, or other required inputs.
  • Communications: Select a network that fits the system’s update-rate, performance, and integration requirements.
  • Installation: Choose panel, PCB, or vehicle mounting and account for connectors and I/O.
  • Environment: Verify temperature, shock, vibration, and any project-specific compliance needs.

After these requirements are established, use product family tables, selection tools, and model-specific datasheets to compare candidates. Installation manuals and product drawings are important for confirming wiring, mounting, and configuration details before design release.

Conclusion

Sound servo drive selection connects electrical ratings and control functions with the practical realities of feedback, networking, installation, and operating conditions. A system-level requirements list gives engineering teams a clearer basis for comparing digital and analog drives, planning multi-axis architectures, and identifying configuration questions early. The final choice should always be checked against the exact model documentation and the needs of the complete motion system.

Access Official Technical PDF

About The Author