In a 6-axis robot, each joint has different velocity and acceleration limits. When configuring the Maximum Path Velocity in MpRoboticsFlex, what value should be specified?
The MappMotion System calculates the Velocity Limit always in consideration to the active Limits (Axes, Path, …). The Mechanical Parameters are considered in this calculation. This limitation is active for all Group Movements and is done in backround, to save the mechanic.
This input “Velocity” in the MpRoboticsFlexParType is used to define the Maximum Movement Speed for a Jog/Move - Command started by this Functionblock.
It is descriped as a Maximum Path Velocity, because if the RobotLimits in the Configuration are lower it can happen that this Velocity is not reached. The real velocity could be lower due to other limits. But if this limit is the lowest, the Movement is limited by this Parameter.
If your Process is fine with the Robot moving very fast you can use the Velocity from the PathDefinition Feature.
Only the Jog, MoveDirect, MoveLinear are using this Parameter. The MoveProgram does always use the Feedrate in the Program and not this Input.
Based on your previous explanations, I would like to confirm my understanding.
The final motion speed (real velocity) is always determined by the lowest value among all active limit such as:
The path velocity defined in MpRoboticsFlexParType.
Individual joint velocity, acceleration limits
kinematics or mechanical constraints
Robotlimits defined in the configuration
and so on..
Therefore, the path velocity paramter can be freely defined by the user as the desired maximum process speed, as long as it makes sense for the application, since the system will automatically ensure that the actual motion never exceeds the mechanical or configuration limits.
Could you please check it if this understanding is correct?