Path Jerk For Real-Time Events (Channel-Specific); General Information - Siemens SINUMERIK 840D Function Manual

Application:
● Part program
● Static synchronized action
12.2.14

Path jerk for real-time events (channel-specific)

12.2.14.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
● Changing the feedrate override
● Changing the velocity default for "safely reduced velocity" within the context of the "Safety
Integrated" function
for the real-time events mentioned, the path jerk can be specified using a channel-specific
system variable:
$AC_PATHJERK =
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.
Effectiveness
Effective
Not effective
Axes and spindles
Function Manual, 06/2019, A5E47437747B AA
path jerk
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 changes
● Changing the velocity default for "safely reduced velocity" within the context of the
"Safety Integrated" function
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.
B2: Acceleration and jerk
12.2 Functions
369