Prehit and Clearplane funny business

[TK_Fire]

something funny is happening on one of the CMMs, The probe is moving to the clearplane then moving up what appears to be the Prehit before probing.
prehit and clearplane are both set the same at .1.
Maybe it is only happening on Planes...
checked DCC Alignment, manual alignment theoreticals, and avoidance moves off.

Any other ideas what could be causing this?

[Mike Ruff]

Clearplane is set off the center of the ruby, and prehit is from the edge. If you have the prehit and Clearplane both set to the same value, this is the behavior I would expect

[NinjaBadger]

This! Good skills Mike.

[DAN_M]

Please post your code so we can really dig into this for you.

Also, ensure you don't have the "avoidance moves" turned on or the "void detection toggle" accidentally clicked on.

One thing I've learned about PC DMIS..sometimes it acts funky with clearance planes AFTER you rotate your probe. The work around for this is once you rotate, even if its the same clearance plane value and everything that you want to use, add another clearance plane command AFTER your rotation and then immediately after that add a "move/point" or "move/increment". This movepoint or moveincrement "clears" something in the background of PC DMIS and stops it from being confused and the clearance planes will work properly after that.

[A-machine-insp]

When it does that to me (happened just yesterday) I add a MOVE/INCREMENT (0,0,0). That has always done the trick for me.

[Kp61dude!]

Please post your code so we can really dig into this for you.

Also, ensure you don't have the "avoidance moves" turned on or the "void detection toggle" accidentally clicked on.

One thing I've learned about PC DMIS..sometimes it acts funky with clearance planes AFTER you rotate your probe. The work around for this is once you rotate, even if its the same clearance plane value and everything that you want to use, add another clearance plane command AFTER your rotation and then immediately after that add a "move/point" or "move/increment". This movepoint or moveincrement "clears" something in the background of PC DMIS and stops it from being confused and the clearance planes will work properly after that.

What does the trick for me is I move the CLEARP command up above the TIP command and all goes away, it acts as a normal move command. I used to do all kinds of extra moves to make it work....temporarily due to operators 'going thru' programs and 'clean code up' before executing causing the CMM to move 'funny' again.