Error Nominal Position Not in Measurement Range

[[Pa...]]

I just finished a new program and did the first manual alignment. Everytime I try to run it I get the error Nominal position not in measurement range. This is the first time I have ever seen this so I am unsure if there is a way to fix this without repositioning the CAD and starting all over or if that is what it is even talking about.

[[Ri...]]

(2) things that typically cause this:

1) The part does not match the CAD at all, so the nominal points deviate outside the normal search distance (10mm)

2) You manually programmed the part on the CAD model before the manual alignment was performed. Ensure that the nominal strategies lie on the CAD model correctly.

[[Ro...]]

Create 3 points, call them point X Point Y, and Point Z. click on your datum surfaces.
Create a start alignment and just fill in the XY&Z points, leave the rotation and Planer empty.
Run the program using the Manual start alignment, see if your machine likes that better.
After the you run once, you should be able to go back and run like normal after that.

[[No...]]

Also check if your alignment is flipped or otherwise misplaced. Errors like this may also occur when the program tries to move the machine to a coordinate that is outside of its measurement volume. This often happens with flipped alignments.

[[Pa...]]

Thank you for everyone's answers I was able to get it to run without having to recreate the whole program so very thankful for that. I have been through alot of the Zeiss classes and I must have missed it or something but I know the alignment has to be done before programming the rest but does the manual alignment actually have to be done on the actual part before you continue, I've never done it this way I usually create the whole program then do the manual alignment before the whole thing is ran.

[[Ro...]]

I have never had to do a manual alignment on a physical part during programming.
I program on an offline seat, and typically write programs a week prior to the parts being completed.
Your case may have just been a glitch or a bug, hopefully it does not continue.

[[No...]]

Please sign in to view this quote.

The worst thing you can do is to mix CAD/theoretical programming with probed data from a physical part, especially on features used for alignment. As long as you program everything on the real part or everything on the CAD, there should be no big issues. However, depending on how you align the part, you can still end up with a flipped alignment in special situations. I even noticed a bug in older Calypso versions, where I got flipped alignments on certain parts when I did the manual alignment at CNC start. Since then I always align from the base alignment window and start the run afterwards.

[[Pa...]]

We do run an older version of Calypso, 2016 to be exact so this could have been a glitch. I did the manual alignment a few more times and the program finally started running as it should.

[[Ke...]]

Please sign in to view this quote.

After I started using simple Start Alignments (3 points, or circle & 1 point, for xyz origins only... no rotations (in space or planar), I never had this issue again.

[[Ri...]]

Please sign in to view this quote.

I teach new programmers this. 3-2-1 for Base Alignments, and then never use any feature from the Base Alignment.
Create a CNC Alignment (a naming convention I coined) and use all your iterative methods there.

[[Pa...]]

How is this done when building off of blueprints with specific datums to use? We have 4 datums to use on every program so simple 321's aren't an option here when that is what they are requesting be used. Plus when the CAD is imported it is automatically put in what we call ''car position'' so the XYZ coordinates do not match the cmm XYZ at all and cannot be changed to do so, they must remain in car position. What is the best route?