ABB AN00250 Motion Control Products Tuning drives for servo motors using Mint Workbench

Introduction

The purpose of this application note is to explain the steps required to get an ABB motion drive operating in conjunction with an

AC servo motor and ‘tuned’ to achieve the best possible performance. Although some references are made to induction motor

parameters, setup and tuning of induction motors is covered by a separate application note.

MicroFlex e190 and MotiFlex e180 motion drives

The MicroFlex e190 and MotiFlex e180 are sophisticated servo drives which have been designed to meet the requirements of

both de-centralised single axis intelligent solutions and centralised multi-axis systems, providing high performance in an

economically priced device.

They provide an ideal solution to many machine applications and are ideal components for machine builders and system

integrators.

In this application note we will describe the commissioning process for a MotiFlex e180. The process is almost identical for a

MicroFlex e190 drive so references in this document to MotiFlex e180 are generally interchangeable with MicroFlex e190 unless

stated otherwise.

Equipment required:

- MotiFlex e180 servo drive running the latest firmware, with the correct feedback option module fitted

- BSM motor with either Incremental encoder, SSi, EnDat, SinCos, Hiperface, SmartAbs, Resolver1

 or BiSS feedback

- PC running Windows 7 or later

- Motor feedback cable terminated with suitable connectors at both ends

- Motor power cable with a suitable connector at the motor end

- Mains supply to the MotiFlex e180 (3 phase 200-480VAC or 1 phase 230VAC is also possible with frame sizes A and B

providing the PHASELOSSMODE parameter is set to 0)2

- Ethernet Cable

Overview

1.1 Recommended I/O connections

If there is any kind of safety requirement in the process then use of the two Safe Torque Off (STO) inputs on the drive which

provide a TUV certified SIL 3 STO functionality should be made. Apart from these STO connections it is not essential to add any

additional control connections although it is common to include a drive enable input when using the drive in combination with a

motion controller providing hardwired analog and/or digital control connections (e.g. NextMove ESB-2).

The digital inputs on the drive allow connection of devices such as a home sensor or limit switches. Two of these inputs (1 and

2) can be used for high speed registration, capturing position in the order of nS to μS (depending on feedback type). Digital

outputs can be configured for functions such as ‘drive ready’ and the relay output (DO4) can be used for functions such as

motor brake control (remembering to follow the instructions in the installation manual to use an isolated 24Vdc supply for the

motor brake circuit via this relay).

Drive enable signal:

The drive will need to be enabled to allow it to control the motor. The source of this enable signal can be defined during the

commissioning wizard and can also be set using the Mint keyword ‘DRIVEENABLEMODE’ which defines if the drive is enabled

via a hardware input only or whether some form of software interlock (e.g. a Mint program or a communications control word) is

also included. If DRIVEENABLEMODE will be set to include a hardware input (other than the STO inputs) then the

DRIVEENABLEINPUT keyword should be used to specify which input channel is used for this function during the

commissioning process (described later). Drives running as intelligent single axis systems (i.e. running a Mint program) and

Real-time Ethernet controlled drives (i.e. EtherCAT or Ethernet Powerlink) do not typically use a dedicated drive enable input

and tend to rely only on the STO inputs for the hardware control of the drive’s power stage.

Motor brake control output:

If the motor you are using has a brake then the drive has the ability to control a motor brake via any of the available digital

outputs (Note that by default output 0 is pre-configured as a GLOBALERROROUTPUT – i.e. a drive status output – so it is

common to use an alternative output for brake control). The OUTPUTACTIVELEVEL keyword should be used to ensure the

specific output channel selected to control the motor brake is configured to be active low. Motor brake control is configured via