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
  • Turns out that when running a program that gets stuck and you chose to do the short cut control U, this will create errors in your program.
    I was told the control U goes into a buffer and when the buffer is filled the machined gets lost.
    The way to recover is shut down everything for some time then restart.
    That seemed to work for us. THe advice was from tech support.
Reply
  • Turns out that when running a program that gets stuck and you chose to do the short cut control U, this will create errors in your program.
    I was told the control U goes into a buffer and when the buffer is filled the machined gets lost.
    The way to recover is shut down everything for some time then restart.
    That seemed to work for us. THe advice was from tech support.
Children
No Data