Nominal not lying on CAD model

[[Me...]]

I got a message from Calypso saying that "Nominal not lying on CAD model" after measure a free form surface. Anyone know what might cause this. I believe that the actual part is pretty close with the cad model. Thanks in advance

[[Jo...]]

I also got this message ("Nominals not lying on CAD") when attempting to measure a Free Form surface using CT data. Does anyone know what this means? Thanks

[[Me...]]

This can happen when the CAD model becomes disassociated with the surface. For example, if you change the CAD model, reimport it, etc.

[[No...]]

It might also happen (but I'm not sure) when you use a CAD surface space point, which is exclusive for the freeform option and is the default there. It's calculated a bit differently from the normal space point.

[[Ch...]]

Question :

What can be done, if we get the dreaded "Nominals not lying on CAD model" message?

It was because I had to re-import an updated CAD. Even deleting the features and creating new FFS still throws the error message.

Thank you !

[[Ke...]]

I never seen any resolution to this thread. Any thoughts anyone? I am having the same issue.

[[Ni...]]

I am also getting this error. This only happens when the cmm is run thru the automation software. When I run the CMM in "real" calypso it runs and calculates profiles just fine.

Any ideas? Thanks

[[Ni...]]

When this program is run thru Basic Automation software it fails to calculate results for my freeform scans
See below


However, when I close the automation software and open "normal" calypso 2021 and run the same program the results from my freeform scans can then be calculated and reported. This is shown in qc-calc. They are represented by the white dots in qc calc in the background of the second photo.

I have adjusted scan speed and point density, removed filters and outliers, made new freeform scans, turned scan optimization on and off, changed and/or removed best fit alignments, among countless other things.

This cell has sat empty with no work for almost a year, since last running any shop orders thru it we have updated to calypso 2021. I have calypso communicating with the automation cell using Basic Automation and since I have saved the program in 2021 my IT department is reluctant to reload 2017 as a troubleshooting step. Currently waiting for Zeiss to call back but I thought I would refresh this with hopes someone might have any ideas.

Thanks, ❓

[[Je...]]

Hello Nick
I did see your request for assistance this afternoon. An AE from my team should be in contact with you tomorrow at first opportunity.

In the interim, I would advise opening the "AutoRun" interface and select "Tools > Always Leave CAD window Open" to see if this eliminates the problem.

Also, within the main CALYPSO interface select "File > Load Settings.." and ensure "Load CAD Model > Model" is selected.

Further things to review are if PCM files exist that are modifying the existence of the CAD model (Freeform requires the model be present to calculate).

I do have a PCM solution (if you have that license) that forces the model to load in the event it is failing during AutoRun execution that has proven to resolve certain IT related issues and with PCs that do not fully meet required hardware requirements.

[[Da...]]

Was the solution to the dreaded "Nominals Not Lying on CAD model" message ever resolved?

I'm getting this on a few freeform surfaces, even after re-associating the CAD model to the freeform surface (I've had to re-import CAD models several times due to part changes, but I went back through each time and 're-attached' the freeform surfaces).

The program uses a load alignment from a thread on the granite (not my preference, but I'm stuck doing it), so the actual part is off almost .125" in one direction from the CAD based on how well the operators load it. Could this cause the dreaded message, and if so, is there a way to re-position the CAD with PCM code to the actual position of the part during the run?

[[Ky...]]

Hello Darrell,

I dug around in our call history and I was able to find Nick's ticket that was put in. It looks like a couple things were tried, including an update to the CALYPSO service pack, an update of the NVIDIA drivers and an option under extras>settings>CMM>AAI menu (display in Calypso User desk, if you want to know), but that last one might not be applicable to you if you are not using some form of automation.

I've ran into this issue a few times before, though I can't remember any in great detail. I do seem to remember distance from nominal playing an important role, though. I believe there is a range that the software will look for the points away from the nominal surface, but there isn't a way to effect that to my knowledge like there is for curve. If possible, I might try to make a secondary alignment in the program that is a bit closer to the physical set up of the part and try measuring the freeform in that.