Jump to content

.toleranceState wrong sometimes?


Recommended Posts

---

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.

  • Like! 1
---

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.

---

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.

  • Like! 2
×
×
  • Create New...