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.

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

drive parameters dedicated to this function (these keywords all start with the text MOTORBRAKE). It’s important to consider

where the 24Vdc supply for the brake will come from. This should be from a separate isolated power supply from that which is

used to supply logical devices such as the drive control card, and other control equipment.