Movement Planning
When a movement is commanded, for example with MC_MoveLinearAbsolute
, the resulting velocity of the robot depends on the following factors:
The maximum velocity, acceleration, and jerk configured for each axis of the axis group. (configured in the axis configuration).
The upper bounds define for each axis how fast it is allowed to move. The other limits which are explained below can only reduce the effective limits. They cannot increase them beyond these bounds.
The maximum velocity, acceleration, and jerk which are provided as inputs to the movement function block. These upper bounds define how fast the TCP can move along the path. They apply in addition to the limits of the individual axes.
The current override (see
MC_GroupSetOverride
) and the ancillary limits for an axis groupFor a description of how all these limits are combined to compute the effective path and axis limits, see the help for
SMC_GroupSetAncillaryAxisLimits
,SMC_GroupSetAncillaryPathLimits
, andSMC_GroupSetAxisLimitFactors
.The programmed path of the robot
For example, when blending between movements results in a very small curvature radius, the robot has to move slowly in order not to exceed the axis limits.
Together, these factors determine the effective maximum velocity on the path. However, there is one more factor that can limit the achievable velocity: the performance of the PLC. If the performance is not sufficient for planning the movement, then the robot moves at a slower velocity. If, due to performance reasons, the planning algorithm cannot verify that it is safe to accelerate, then it will move at a slower velocity instead. For more information, see: Performance