.toleranceState wrong sometimes?

[[Ra...]]

I'm curious if anyone has ever had getActual(char).toleranceState be flat out incorrect? I'm testing something offline, could it be because of that? 

 

Calypso 2025

[[Ri...]]

Explain what you mean by wrong.

Maybe show a snippet of your code.

[[Ra...]]

In the post settings of the characteristic.

[[Ra...]]

Edit: It seems like the calculation only occurs after an entire CNC run with clear existing results is checked. If you rerun just the feature or update the tolerance, the tolerance state does not update. If anyone happens to know the exact parameters of the triggering of the calculation, I'd really appreciate it.

[[Ra...]]

2nd Edit: It actually seems to just be wrong sometimes, even when completing a new run. Maybe it bugs out when placing in the post settings of the characteristic in question?

Edited Monday at 01:53 PM

[[Ri...]]

For gits and shiggles, place the same code in a Result Element and see if it is correct all the time.

My initial thought is this in the Post settings may not get the new value until the program is completed, which is after Post settings have been run.

Using a Result element may show us something, and it may not.

[[Ra...]]

It works correctly in the result element if said result element is below the characteristic it is evaluating. Unfortunately, this won't work for what I need.

I ended up just grabbing the actual, upper limit, and lower limit and writing an If statement. With this method, I couldn't just use read a PCM file, because some characteristics behave differently with grabbing actuals. So, I had to copy and paste because those certain characteristics (caliper distance, angles, etc) needed modified code.

I'll probably look back into it later in the future, but as of now I found an okay way around it.

[[He...]]

I usually use getActual().inTolerance and from what I have seen it works great.

[[Ra...]]

And you use that in the post settings of the characteristic in question? I still seem to have the same issue.

[[He...]]

Please sign in to view this quote.

 

Very strange. I have never seen that happen. What version are you one? Maybe it is a bug you can report to the Zeiss support.

[[Ra...]]

Please sign in to view this quote.

Version 8.0.08. I haven't done a super deep dive on it, but it seems to work on all characteristics under Form and Location, and characteristics under size is hit or miss. But X,Y,Z values seem to always be incorrect. 

[[Ri...]]

Can you use the Result element in your post settings?

You should be able to Mask/mark the Result Element, so it has no effect on the report but call it in the Post settings like you call the feature.

The Result Element would return True or False.

Edited 5 minutes ago