Difference between revisions of "Speed Picker Y Limit"
m |
|||
| (11 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | == Speed | + | == Speed Picker "Singularity" == |
| + | At J2 angle of 90 degrees, where Y reaches its maximum, the Speed Picker robot (Traverse Arm kinematics) behaves like in a vicinity of a singular point. | ||
| + | Typically this can occur when the motion interpolation is Cartesian mode, which means that the robot is actuated by MOVES or CIRCLE command or the robot | ||
| + | is tracking conveyor (slave = 5). | ||
| + | In such cases when the robot is close to the point #{X,± L1, Z, R} velocity and acceleration of all joints increase drastically. | ||
| + | And the position limit protection mechanism that is fired takes the initial values of velocity and acceleration which are far above their maximal values. | ||
| + | This cause the generation of a stopping profile that is too long, i.e. an coasting of the robot occurs. | ||
| + | |||
| + | The issue was resolved in firmware versions 4.5.24 and later, in which values of initial acceleration are limited to '''Sys.MotMargin*vmax''' value. | ||
== Recommended Limits == | == Recommended Limits == | ||
| − | See Also: [[ | + | It is recommended to limit the workspace of Cartesian motion to L-T×VmaxTran where T is the motion sample period and VmaxTran is the maximum translational velocity robot reaches. |
| + | |||
| + | In a real application it means reducing Ymax by about 5 mm. | ||
| + | |||
| + | See Also: [[Sys.MotionMargin]] | ||
| + | |||
| + | <!-- , Bugzilla: [http://bugzilla.manz-automation.com/show_bug.cgi?id=4037] --> | ||
| + | |||
| + | |||
| + | [[Category:Motion Control]] | ||
| + | |||
| + | <!-- --[[User:Miborich|Mirko]] 13:13, 5 October 2010 (CEST) --> | ||
Latest revision as of 12:37, 22 May 2014
Speed Picker "Singularity"
At J2 angle of 90 degrees, where Y reaches its maximum, the Speed Picker robot (Traverse Arm kinematics) behaves like in a vicinity of a singular point. Typically this can occur when the motion interpolation is Cartesian mode, which means that the robot is actuated by MOVES or CIRCLE command or the robot is tracking conveyor (slave = 5). In such cases when the robot is close to the point #{X,± L1, Z, R} velocity and acceleration of all joints increase drastically. And the position limit protection mechanism that is fired takes the initial values of velocity and acceleration which are far above their maximal values. This cause the generation of a stopping profile that is too long, i.e. an coasting of the robot occurs.
The issue was resolved in firmware versions 4.5.24 and later, in which values of initial acceleration are limited to Sys.MotMargin*vmax value.
Recommended Limits
It is recommended to limit the workspace of Cartesian motion to L-T×VmaxTran where T is the motion sample period and VmaxTran is the maximum translational velocity robot reaches.
In a real application it means reducing Ymax by about 5 mm.
See Also: Sys.MotionMargin