When converting a job the robot simply does the math. If you get the "/OV" at the end of a move instruction it means the robot is trying to move beyond it's limits or Over Value of an axis or movement.
When converting a job the robot simply does the math. If you get the "/OV" at the end of a move instruction it means the robot is trying to move beyond it's limits or Over Value of an axis or movement.
That is correct.
These programs run fine daily when they are in RELATIVE. Technically they should run fine when converted into PULSE too. But for some reason the conversion is flipping the R and T axis way passed soft limits causing the OV errors on most lines.
These are very long jobs with thousands of lines (3-4hr run time) and it would be incredibly tedious to fix these points individually. We have hundreds of jobs too.
Did this eventually get resolved? I have this problem to at point in the program. A few pulses between points gives an extreme movement on R and T. Can happen an hour into a long program with just repetative movements, Long programs converted from xyz gcodes posted as pulses from robodk.
Hello,
This looks like that the robot go by singularity position, because the robot change of the configuration (front,up,no flip.)
You can verify this position right arrow + direct open.
