Hi everyone,
I’ve encountered a problem with repeated moveL instructions between close points.
Problem is:
The rapid manual states:
“If it is not possible to attain the programmed velocity for the reorientation or for the external
axes, the velocity of the TCP will be reduced.”
on page 244 under MoveL.
Question is:
How do I know when exactly the TCP speed is being reduced? Is there any flag in RAPID that can be read? Or, better, can the true TCP speed be detected by RAPID in any way?
some Background information (if you’re interested)
we’re trying to make the robot follow a specific path that is described with points in a NC-file. While this is generally working well, we experience problems with using the moveL command when the distance between two points is too little for the TCP speed given.
Basicly it’s looking like this
moveL point,vExecuteV:=40,z1, toolwobj
with point is continually read from the nc-file looking like this:
…
77.6393,95.6992,0.0000,orientation
86.4886,90.9937,0.0000,orientation
97.6393,88.1516,0.0000,orientation
…
making the path look like this in the end. the thick blue line is the TCP.
Now i’m trying to find the best suiting distance between two points. If the point density is getting too high, the TCP feed rate (in my example above 40 mm/s) is dropping low, probably because the restrictive zone z1 in combination with moveL.
I hope my description is clear and I’m looking forward to hearing from anyone.
Best regards,
Michael Fink