Functions
2.14 Path jerk for real-time events (channel-specific)
Basic logic functions: Acceleration (B2)
Function Manual, 11/2006, 6FC5397-0BP10-2BA0
35
2.14 Path jerk for real-time events (channel-specific)
2.14.1 Detailed Description
2.14.1.1 General Information
Overview
So that no compromise has to be made between machining-optimized jerk on the one hand
and time-optimized jerk in connection with the following real-time events on the other:
• NC-STOP/NC-START
• Feedrate override modifications
• Modification of the velocity default for "safely reduced velocity" within the context of the
"Safely Integrated" function
the path jerk can be set for the real-time events specified above using a channel-specific
system variable:
$AC_PATHJERK =
path jerk
Path jerk for real-time events will only be active for the duration of the change in velocity in
respect of one of the real-time events specified above.
Limitation
As the jerk is not a physical variable of any relevance to the drive, no limit is imposed on the
jerk set.
Effective
Effective Path jerk for real-time events is only enabled in AUTOMATIC and MDA operating
modes in conjunction with the following real-time events:
• NC-STOP/NC-START
• Override modifications
• Modification of the velocity default for "safely reduced velocity" within the context
of the "Safely Integrated" function
Ineffective Path jerk for real-time events is ineffective for changes in the path velocity that are
attributable to path planning during preprocessing for the channel, such as contour
curvatures, corners, kinematic transformation limitations, etc.
Path jerk for real-time events is ineffective if the programmed value is smaller than
the path jerk calculated during preprocessing for the path section concerned.
To Next Page
Loading...
Need help?
General
