Aerotech UNIDEX 600 Series, Руководство пользователя

Страница: 265 / 354

Parameters U600 User’s Guide
C-40
Aerotech, Inc.
Version 1.4
C.2.93. SIMULATION
To facilitate easy debugging of parts programs, this axis parameter allows the user to
place an axis into a simulation mode. While in this mode, the motor’s torque remains
steady (holding the axis in position), but no motion occurs. This axis parameter is used to
implement Simulation mode (parameter value=1). While this parameter’s value is non-
zero, the motor's torque remains steady (holding the axis in position), but no axis motion
occurs. While executing a CNC program on a simulated axis, the controller performs all
calculations normally, but the torque command never reaches the motor. Instead, the
torque serves as the feedback for this axis, effectively creating a system free from velocity
error. While moving an axis in simulation mode, the velocity and position commands
behave normally, but the position remains constant, and the velocity is zero. All other
features, such as data acquisition, continue to function normally.
Setting this parameter to zero disables the simulation mode, while a one enables it. The
default is to disable the simulation mode. You should not modify the simulation axis
parameter while the axis is in motion.
Setting this parameter to two activates machine lock, which updates the machines internal
positions for the new current position.
Alternatively, an axis may be configured as a virtual axis for debugging purposes. In this
mode, SIMULATION has no effect.
C.2.94. SOFTLIMITMODE
This axis parameter sets the active mode for the software limits (defined by the CWEOT
and CCWEOT parameters), as well as the safe zones (defined by the SAFEZONECW,
SAFEZONECCW, and SAFEZONEMODE parameters). In many systems, the current
absolute position of an axis is unknown until after the axis reaches its home position.
Therefore, the user should not activate a software limit or a safe zone until the system
successfully completes the homing process. However, the mechanics of some systems do
not permit execution of a normal homing sequence. Therefore, the user must use an
alternate method to determine the absolute position. In this case, it may be logical to
permit software limits and safe zones to be active at all times.
Setting this parameter to a one (1) causes software limits and safe zones to become active
only after successfully homing the axis. The default value is zero (0), which causes
software limits and safe zones to be active before and after homing the axis. Software
limits and safe zones are never active during a homing cycle.