Updated to latest Calypso, getting alarms for no clearance plane.

[[Ja...]]

On many of our programs, we do not use clearance planes in certain areas, such as when in a deep stepped counterbore, using Z+ for the first feature, adn then no clearance plane for the following features until the last feature on which it gets a Z+ Clearance Plane. 

I just recently updated on of my Contura G2 CMMs to 7.8.0801, and now I am getting stop light action with a message of "No Clearance Plane" when doing this type of measuring.

The program works fine on the 7.6 versions on the other 2 CMMs.

Any Ideas?

[[No...]]

Am I misunderstanding something here? How exactly do you set up a feature with "no clearance plane" ? Isn't there always a clearance plane or group set?

What you can do is to run with position points only, but then Calypso shouldn't care about clearance planes at all.

 

Have you tried using a clearance group with sub-clearance planes?

 

 

Edited November 26, 2024

[[Th...]]

Please sign in to view this quote.

It is possible to assign no clearance plane. The very first option under the clearance plane dropdown in the feature definition window is a blank entry. More than once I have crashed a machine because the next feature to measure is assigned this null plane and the probe drives straight at it, usually into a wall. Happens when I change a theoretical feature back to a measured one and forget to update its clearance.

You're probably right about using sub-clearance, I think using them for features like stepped bores is the example Zeiss gives in training.

[[No...]]

Please sign in to view this quote.

😲 I remember having an empty CP entry some time ago, but that was when something went wrong while experimenting with parametrized clearance planes. I never imagined this could be an intentional setting.

[[Ja...]]

Here is an example of a program ran for several years with no issues on older versions of Calypso. (<= ver. 7.6)

 

 

[[No...]]

That's something you'd typically solve with a clearance group.

I know for sure that they added new checks for the existence of defined path elements prior to CNC start in version 2023. Maybe they now also check for a proper clearance plane. I may be wrong, but I can't remember that an empty CP field was ever officially suppported. So maybe it worked in the past, but now they decided check for it. I had a similar issue with a very old program from which a park position was deleted long ago. It worked for many years, but now the new checks caused a red light.

[[Ma...]]

I agree you would want to solve this another way. I always use the SCP(whatever parent group) this returns a value of zero. It means it will not move out of the part but move directly to the next feature. The problem with this is if someone reorders the program or runs it from the characteristic list where before it ran from the Feature list you may have issues. So, in the above case create a Sub-Clearance plane and you will have no issues.