hexagon logo

"Cannot find Nominals"

Hi,

I am having an issue when running a programme on PCDMIS 2014 SP4. A "cannot find nominals" text box is popping up when running certain programmes.

What I would really appreciate is, what exactly is causing this to pop up and are there any consequences for ignoring the message.

For Example if I click yes and update previous scans or if I say ignore and don't update scans, will this have an effect on the results?

I am not the one who writes the programmes (Guys in the US do this O am from Ireland!) and our programmers don't seem to know how to resolve the issue nor do they know what are the consequences for selecting yes or no on the text box.

A fix for this and some insight into how and why it comes up would be seriously appreciated!
Thanks,

Cian
Parents
  • You have the option to select a new FINDNOMS tolerance and then an option to define if this new tolerance will apply just to that particular run or will become a permanent change to the program. You need to increase the tolerance until you stop getting the error. If you select "For This Program" and then save the program when you are done with the run it should become a permanent update to the program. Whether you want to do that or not, and whether you are authorized to do that or not, is for you to determine.

    What is sure is that you can not continue to run as-is. You must either modify the program yourself by responding appropriately to the dialogs or wait for your counterparts to modify it for you.

    The FINDNOMS tolerance is a radial value from ball center so it must be equal to the radius of your stylus ruby plus the maximum deviation from nominal that you anticipate that you could have on each particular surface. The trick is that if you set it too large it could start finding nominals on the wrong surface.

    The reason you are having trouble could be as simple as you are using a larger diameter ruby than the original programmer expected or it could be that your parts are deviating from nominal more than the original programmer expected. It could also be that the original programmer didn't pay any attention to it at all and just set the tolerance way too low.

    There are also other, more subtle issues that can cause this. For example, if the original programmer selected a group of CAD surfaces for the scan but missed a very small surface somewhere in the middle of the group you could get this error due to the software's inability to find a nominal value for the few points that fall on the surface that was skipped.

    And to your first question: Yes, changing the tolerance will affect the results because it will cause more or fewer points to be included in the scan results. The points that get included/excluded first as the tolerance changes are the points that are furthest from nominal so this will very directly drive the value of any profile of line or profile of surface evaluation.
Reply
  • You have the option to select a new FINDNOMS tolerance and then an option to define if this new tolerance will apply just to that particular run or will become a permanent change to the program. You need to increase the tolerance until you stop getting the error. If you select "For This Program" and then save the program when you are done with the run it should become a permanent update to the program. Whether you want to do that or not, and whether you are authorized to do that or not, is for you to determine.

    What is sure is that you can not continue to run as-is. You must either modify the program yourself by responding appropriately to the dialogs or wait for your counterparts to modify it for you.

    The FINDNOMS tolerance is a radial value from ball center so it must be equal to the radius of your stylus ruby plus the maximum deviation from nominal that you anticipate that you could have on each particular surface. The trick is that if you set it too large it could start finding nominals on the wrong surface.

    The reason you are having trouble could be as simple as you are using a larger diameter ruby than the original programmer expected or it could be that your parts are deviating from nominal more than the original programmer expected. It could also be that the original programmer didn't pay any attention to it at all and just set the tolerance way too low.

    There are also other, more subtle issues that can cause this. For example, if the original programmer selected a group of CAD surfaces for the scan but missed a very small surface somewhere in the middle of the group you could get this error due to the software's inability to find a nominal value for the few points that fall on the surface that was skipped.

    And to your first question: Yes, changing the tolerance will affect the results because it will cause more or fewer points to be included in the scan results. The points that get included/excluded first as the tolerance changes are the points that are furthest from nominal so this will very directly drive the value of any profile of line or profile of surface evaluation.
Children
No Data