Jump to content

Intersection not working as expected


---
 Share

Recommended Posts

Anybody run into this before? Circle intersected with the shell of a cylinder, so you have result 1 and result 2. In this case I want Result 2 as it puts the nominal in the correct spot. Looking at the X values here.

But no matter which I pick, the Actual is Result 1.

What is interesting is this worked correctly before I had to mirror the program.
3535_7f27564f4ddd5c6f6df9a514cc18bc76.png
3535_89e316fbdbc356f5be08c07811975acf.png
Link to comment
Share on other sites

Did you run the program, or just select the different results? You may have to run the program to get new results. (the nominals changed but the actuals didn't)
Link to comment
Share on other sites

Yes. Program ran and produced incorrect results, There is a distance callout to that intersection point that is off by the amount that is shown in the photos.
Link to comment
Share on other sites

Please sign in to view this quote.

Why measure another line when I have to measure the cylinder anyway? Waste of programming effort and cycle time.


I did find the answer, weird as it is. I had to recreate the circles, then everything started working correctly again. I'll guess it was some kind of space axis error, even though the new circles are all the same.
Link to comment
Share on other sites

Please sign in to view this quote.

After mirroring, the axis of the feature was probably inversed. Most of the time program works fine but sometimes it gives goofy results and redoing the features with the new current axis fixes the issue.

Another thing you can do is create a blank line feature and just recall feature points of the cylinder. Then create a thin rectangle using "select actual points via mouse cursor" making sure it crosses through both circles of the cylinder on one side only. That will create a line so you don't have to rescan again.
Link to comment
Share on other sites

 Share

×
×
  • Create New...