EasyTune Module

The EasyTune module automatically does a series of axis identification and servo parameter optimization steps on the selected axis with minimum user input necessary. You can find this module in the Servo Topic of the Configure workspace in Automation1 Studio. Make sure that you are in Basic Editing mode.

The output of EasyTune is equivalent to the servo optimization that is done by an experienced controls engineer. If EasyTune completes successfully, it is not necessary for you to use the other tuning tools unless your application requires very low tracking errors for high-dynamic motion. When you use EasyTune, it is not necessary for the selected axis to be stable or enabled.

If the EasyTune module shows a message that tells you EasyTune does not support the selected axis, move directly to the Repeated Failures path of the Servo Tuning Workflows flowchart.

Each time that you run EasyTune, a log file is automatically saved to the EasyTune directory in your User Files directory.

IMPORTANT: For more information about the EasyTune module and servo tuning, see the Servo Tuning user guide.

EasyTune Recipe Files

The EasyTune module can also run custom-tuning recipes that Aerotech supplies with the .etr extension. For conditions where the default EasyTune behavior is not satisfactory, these files will supply an alternative behavior.

IMPORTANT: Aerotech supplies EasyTune recipe files only for specific conditions. If you do not have one or more EasyTune recipe files (.etr), do not enable this setting.

Recipe files can define behavior for one or more axes. In the Configure workspace, a recipe will run on the selected axis only if that axis is defined in the recipe file. EasyTune will behave normally on a selected axis that is not defined in the recipe file.

Recipe files can run on two or more axes at the same time. If you have a recipe file with two or more defined axes, the EasyTune module will show each axes that has motion commanded on it when the recipe operates on that selected axis.

Troubleshoot EasyTune

EasyTune does not always complete successfully. The table that follows shows common issues that might occur and how you can try to correct them.

Table: Troubleshoot EasyTune

Error Message Solution

EasyTune cannot identify the axis.

Before you start EasyTune, make sure that you are getting valid position feedback from the selected axis.

EasyTune cannot complete because the controller generated an axis fault.

If the axis fault is an End-Of-Travel Limit fault or a Software Limit fault, make sure the axis is away from all the limits. Then click the Start button to do EasyTune again.

If the axis fault is a Maximum Velocity Command Fault, increase the values of the VelocityCommandThreshold and VelocityCommandThresholdBeforeHome parameters. Then click the Start button to do EasyTune again.

If the axis fault is a Position Error Fault and it is safe to continue, increase the value of the PositionErrorThreshold Parameter or use a more conservative performance target. Then click the Start button to do EasyTune again.

If the axis fault is an Over Current Fault, use a more conservative performance target. Then click the Start button to do EasyTune again.

EasyTune cannot optimize the axis.

If it is safe to continue, click the Start button to do EasyTune again. During the procedure, make sure that you multiply the Travel Distance (primary units) and Travel Speed (primary units / second) by two.

Related Help Pages 

Servo Topic

Axes Category Overview