B2: Acceleration and jerk
12.3 Examples
Part program instruction SOFTA / BRISKA / DRIVEA
The part program instruction SOFTA(<axis1>,<axis2>, ...) is also effective in JOG
mode, i.e. the maximum axis-specific jerk from MD32430 $MA_JOG_AND_POS_MAX_JERK
is effective for the specified axes when traversing in JOG mode (exactly as when setting
MD32420 $MA_JOG_AND_POS_JERK_ENABLE [<axis>] == TRUE).
Note
On the other hand, the SOFT part program instruction has no effect on JOG mode.
As with SOFTA, the part program instructions BRISKA and DRIVEA are also effective in JOG
mode, i.e. the acceleration is without jerk limitation, even when MD32420
$MA_JOG_AND_POS_JERK_ENABLE is set to "TRUE" for the relevant machine axes.
Note
Manual traversing of orientation axes is not affected by BRISKA/SOFTA/DRIVEA.
See also
Acceleration without jerk limitation (BRISK/BRISKA) (channel/axis-specific) (Page 349)
Jerk limitation with single-axis interpolation (SOFTA) (axis-specific) (Page 366)
12.3
Examples
12.3.1
Acceleration
12.3.1.1
Path velocity characteristic
The following example shows the path velocity characteristic, based on programmed traversing
motion and the actions initiated in a part program segment.
Part program extract
Program code
; Synchronized action: Acceleration switchover depending on fast input 1
($A_IN[1]):
N53 ID=1 WHEN $A_IN[1] == 1 DO $AC_PATHACC = 2.*$MA_MAX_AX_ACCEL[X]
; Synchronized action: Test override profile (simulation of external
interventions):
N54 ID=2 WHENEVER ($AC_TIMEC > 16) DO $AC_OVR=10
N55 ID=3 WHENEVER ($AC_TIMEC > 30) DO $AC_OVR=100
;Approach
N1000 G0 X0 Y0 BRISK
390
Axes and spindles
Function Manual, 06/2019, A5E47437747B AA