
Parker Hannifin
30 Programmer’s Guide
NOTE: There are no restrictions regarding how to assign hardware
limits and homing inputs. However, you should exercise
caution because it is possible to create imaginary limit and
home inputs. This is because the controller assumes all three
inputs are in the same multiple of 32 bits. The assignment of
inputs does not roll over to the next block of 32 bits. For
example, if the positive hardware limit is assigned to input
31, the negative hardware limit and homing inputs are not
assigned. Instead, they become imaginary inputs with a
value of zero.
End-of-Travel Limits
The ACR series controller can respond to hardware and software
end-of-travel limits, which prevent a motor’s load from traveling past
defined limits. You can use hardware and software limits regardless
of incremental or absolute positioning.
Software and hardware limits, typically, are positioned so that when
the load reaches the software limit, the motor/load starts
decelerating towards the hardware limit. This provides a smoother,
more graceful stop towards the hardware limit than if the hardware
limit, itself, were activated.
When a load reaches an end-of-travel limit (hardware or software),
the ACR controller stops the master and all attached axes. The stop
is made using the hardware or software deceleration rate—HLDEC or
SLDEC, respectively.
Hardware Limits
For each axis, you can set a pair of inputs to act as positive and
negative limits for hardware travel. Parameters 4600-4615 provide
Control and Status bits for software limits. You can enable the
individual positive and negative limits and set the active level for
each, as well as check the current and previous states of the limits.
NOTE: When a hardware limit is a hit, the KAMR (Kill All Motion
Request) Bit is also set. Before motion can resume, you must
clear the KAMR Bits for the affected master and its attached
axes.
Commentaires sur ces manuels