Feature has not been measured - but has been

[[Lu...]]

Hi folks

I start a plan. Whole measurement plan is executed and in comes to the result print out. get a message "Feature 'RH_A1_center' has not been measured"

But it has

 

When I choose Yes, machine keeps on measuring RH_A1_center and other presumably missing Features and won't stop

RH_A1_Center is a part of Alignment I utilize for Profile 1. The Alignment is with a loop with condition "differenceSystem().valueA<0.005"

 

What's the problem?

[[Ke...]]

Sounds like the deviation between loops is not getting below 0.005. You should be able to see the loop results in the Default Printout(?)

[[Da...]]

Are you running on a network? I have seen this when someone opens the same program that I am running.

[[Th...]]

I'm pretty sure that secondary alignment loops don't self-adjust like the base alignment does.

[[Mi...]]

That definitely sounds like a network issue. I have seen and experienced this many times over the years. If you have the program open on two separate computers, you'll see this message. It is trying to read and write to the file from two different locations. It will want to go back through the entire program and re-inspect every feature, even though it has already inspected them. Best thing to do is to stop the program, make sure it isn't opened anywhere else and run it again.

[[To...]]

Please sign in to view this quote.

Please sign in to view this username.

  Can you elaborate? 

[[Th...]]

Please sign in to view this quote.

My recollection is that Calypso will only iterate the base alignment's stored coordinate system between loops to bring it closer to measured actuals. Loops applied to secondary alignments don't do that, so if the valueA of a secondary is 0.008 relative to the base alignment, it will be 0.008 in every loop because it's locked in place. I remembered this thread from a few years ago: 

 

[[Lu...]]

Please sign in to view this quote.

not the case; once computer only

[[Pa...]]

This happens to us several times per year.  We are isolated from any network.  Can't be certain right now but I THINK It's happened in programs with no loops.  I'll watch for this.  A former programmer here was fond of writing a 3-loop base alignment with a .00005" break condition (yep.  50 millionths in 3 loops.  SMH) so maybe with this information I'll finally find it. 

It is not isolated to specific programs.  It isn't always an alignment feature that shows up in the first prompt.  Can be any feature.  Click ok and it WILL ALWAYS then run down through every.  Single.  Feature with the same message.  All features are green until I interact with the prompt, at which time each feature in turn goes back to grey.  If I stop right away and go look for actuals (the files), I can see they're all there.  Any interaction with the prompt from Calypso disappears all actual files.  Try to save measured points?  Behavior is exactly as though I never ran.

Start from the beginning, and run 30 parts back to back; never see the problem again.  Two months later on different product it will come back.

Anecdotally, I'd say it tends to happen on programs over 2 hours long.  Can't say definitively.

I've found no way around it.  When this pops up, there's nothing for it but to re-run the entire program from start.  Swearing isn't required but it helps.

I'm running Calypso 2022. 

Edited October 12

[[Ch...]]

Sounds like definitely a case of 'gremlins in the machine'   😅😄  ... j/k I have seen this on occasion as well, and feel your pain.

Great post, thanks for keeping it fun.

 

Maybe Calypso does it anytime we even 'think about running from characteristic list' ??   😃😅😄

 

 

[[Ri...]]

I feel like this has been posted before. I thought it had something to do with a very specific condition regarding masking or mini-plans. Idk - it's a little fuzzy. 

[[Ni...]]

It happens to us here occasionally. We utilize Autorun with 6 of our CMMs.  It's not uncommon for two CMMS to be running the same program from our server. 

What I have found is that if two CMMs are started at the same time, one of the CMMs seems to get confused and pop this error. If they are started even a minute apart, it usually doesn't happen, however. 

It also occurs if I open a program (from my desk) that is actively running on a CMM, the CMM will ask to rerun multiple features at the end of the program.  I haven't figured out if it asks to rerun every feature that was complete when I opened the program at my desk, or if it's just a few features that were probed during the time it took my computer to load? I usually just stop the CMM and rerun the program. 

I personally haven't correlated the use of mini plans or masking to this error, but anything is possible. 

We also loop every 99% of our base alignments. 

I have also attributed this to the overlap of reading and writing to the same program folder from two different instances of Calypso. 

Edited October 17

[[Lu...]]

Please sign in to view this quote.

You are right

I checked a non-base alignment with 1mm condition and the loop went five times, as programmed

differenceSystem().valueA<1