Jump to content

Why does Calypso make this X axis move?


---
 Share

Recommended Posts

Calapso 2021.
I am plagued by this X axis move, nearly every feature I create, Clearance Plane Z+ (or any clearance plain) the CMMs first move is X+.
This has caused minor collisions when you aren't expecting it.
See attached file. KVID0932.mp4.zip
Rename to KVID0932.mp4

KVID0932.mp4.zip

Link to comment
Share on other sites

Please sign in to view this quote.

Curious. From the current ending position, jog the Z up a little bit, i.e. 1/4". Then, run it. I believe it thinks it is still within the clearance cube and you're seeing an evacuation move first. Should it do that? I think it shouldn't, as long as it moved to the +Z clearance plane at the end of program.
Link to comment
Share on other sites

Is there something in your clearance data, Strategy > Clearance Data > Clearance Distance? I've seen goofy stuff when there is a value there.
Link to comment
Share on other sites

Please sign in to view this quote.

From your response, I'm not sure you understood what I asked you to do.

At the end of the run, I understand the tip of the probe should be at the +Z CP, or 1" in your case. What I wanted you to try, was after the run, jog the Z up from where it stopped. Let's say 1/4" for the sake of discussion, but the amount is not important. Execute the program and tell me if it makes the same move.
Link to comment
Share on other sites

This looks similar to an issue we've had with measuring inside bores with circles, except we load parts in the ZY Plane so our movements were happening in Z, not X

For whatever reason, flipping the space axis of the circle fixes it for us +X to -X, Z in your case.

No idea why. It's completely random and may be a product of the varied and older versions we have.
Link to comment
Share on other sites

I sometimes observe similar movements in certain features, but I can't put my finger on why it happens. The probe moves in from +Y (usually after probe change) and should measure a circle in the X/Z plane at the +Y side of the part. But the first thing it does, it stays above CP +Z and moves about half the part length in -Y and out again behind CP +Y. Only then it goes to the feature it was meant to measure. It never caused a collision, yet there's nothing in the program to explain the extra move, not even a safety distance.
Link to comment
Share on other sites

Please sign in to view this quote.

No, nothing at all.
I'm starting to think this has to do with a multi sensor system.
I have a ViScan 1x, it always makes this same weird move.
Link to comment
Share on other sites

 Share

×
×
  • Create New...