hexagon logo
Register Sign in
  • Replies 4 replies
  • Subscribers 221 subscribers
  • Views 56 views
  • Users 0 members are here
Options
Related

Why Is My Machine Erring????

The Rook
Hello, hope all is well with everyone. I'm kinda losing it over here. Programming a part and everything started off fine. The issue started when it would make a hole I programmed. It was stopping .300" before the feature and trying to probe there. My coordinates matched print, but it just couldn't get to the hole. So I tried a few things and now when I set my Yminus clearplane to .-25 to come out of the readpoint hole and probe the plane...the machine just keeps traveling back until its out of limit.

Any ideas as to what is going on??? I'm going mad. It's a simple part but things are goofy. any insight would be greatly appreciated.
Parents
  • complete blind guesses:

    is void detection on? It does some weird things to me on compound angle holes.

    Is your starting offset and ending offset correct? If I do a DEEP hole where I have to not check the last inch due to short stylus, next hole I go to, it has hits outside the actual part based on remembering the ending offset previously used, I set that back to .04/.04 and hits are golden.

    Did someone at some point get the popup about no hole do you want to read machine's location, the location happened to be .300 above the part, god knows why, when they clicked yes, then asked if you want to remember that forever they clicked yes again, so your TARG XYZ are not actually IN the hole?

    Weird vector with weird start/end values AND "FIND HOLE" is turned on, so it "thinks" it is IN the hole .300 above and is looking for the hole BEFORE going to your actual hits?
Reply
  • complete blind guesses:

    is void detection on? It does some weird things to me on compound angle holes.

    Is your starting offset and ending offset correct? If I do a DEEP hole where I have to not check the last inch due to short stylus, next hole I go to, it has hits outside the actual part based on remembering the ending offset previously used, I set that back to .04/.04 and hits are golden.

    Did someone at some point get the popup about no hole do you want to read machine's location, the location happened to be .300 above the part, god knows why, when they clicked yes, then asked if you want to remember that forever they clicked yes again, so your TARG XYZ are not actually IN the hole?

    Weird vector with weird start/end values AND "FIND HOLE" is turned on, so it "thinks" it is IN the hole .300 above and is looking for the hole BEFORE going to your actual hits?
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement