I have submitted a ticket on this today but I’m curious if others have experienced the same issue. When loading a large program (100,000+ lines, lots of adaptive roughing) if a commanded move exceeds the machine’s travels, I get the usual error message on the info tab to that effect. The issue is that the error message is entirely unhelpful, telling me the problem is on “line 0” and giving me a goal position that seems to be expressed in G53 coordinates rather than the active WCS.
Loading progressively smaller chunks of the program eventually gets me a valid line number but still in G53. Anyone else run into this sort of behavior yet?
Was running a Zprobe and set origin and had to hit escape right before the second touch off and when I tried to probe again I got an error.
Please reference the machine or check that the code doesn’t travel outside of the machine’s limits
14:42:20 | probe move on line 1 would exceed the z axis’s negative limit by 0.056124 (goal position is -16.306124)
Had to E-stop, re-reference to probe again.
Saved the log data if someone wants it let me know. I put it in my hub machine folder.