hexagon logo

program getting errors

We have been checking parts with a short program. We have checked about 8 parts and then we started getting "out of limit 10" errors when taking a point on a circle.
So we tried to figure out what happened. I started taking point in an opposite pattern and the machine took the points but the results were way off. Why is this machined acting this way when we did not change anything in our work and point taking sequence and pattern before we started getting errors?
We do not know why all of a sudden the machine changed the point pattern. Now we can not continue because the results are way off.
Has anyone seen this behavior on their ARM before?
If so, how do we recover from this without creating a whole new program?
Parents
  • We have been checking parts with a short program. We have checked about 8 parts and then we started getting "out of limit 10" errors when taking a point on a circle.
    So we tried to figure out what happened. I started taking point in an opposite pattern and the machine took the points but the results were way off. Why is this machined acting this way when we did not change anything in our work and point taking sequence and pattern before we started getting errors?
    We do not know why all of a sudden the machine changed the point pattern. Now we can not continue because the results are way off.
    Has anyone seen this behavior on their ARM before?
    If so, how do we recover from this without creating a whole new program?


    You haven't turned off your Any Order Execution.

    Hit F5.

    Go to the bottom of the dialog box. Change "any order execute tolerance" to 0.

    Problem goes away.
Reply
  • We have been checking parts with a short program. We have checked about 8 parts and then we started getting "out of limit 10" errors when taking a point on a circle.
    So we tried to figure out what happened. I started taking point in an opposite pattern and the machine took the points but the results were way off. Why is this machined acting this way when we did not change anything in our work and point taking sequence and pattern before we started getting errors?
    We do not know why all of a sudden the machine changed the point pattern. Now we can not continue because the results are way off.
    Has anyone seen this behavior on their ARM before?
    If so, how do we recover from this without creating a whole new program?


    You haven't turned off your Any Order Execution.

    Hit F5.

    Go to the bottom of the dialog box. Change "any order execute tolerance" to 0.

    Problem goes away.
Children
No Data