I apologize if this has been asked before, but I searched on here without any luck to my dilemma with a intersection issue. I do gauge points now by constructing a plane and offset to the height needed then construct a circle with that plane and a cone created from the program. I recently ran into an issue trying to create an intersection point so any help or guidance is appreciated and I am PCDmis for dummies, my apologies. Also, why I am asking for help is there good way to check wall thickness and it be accurate (the red circled dimension is the one I am curious about, not trying to insult anyone) I have uploaded some pictures to try and help the questions, thank you in advance again for any help.
Measure your diameter as a cylinder. Conical feature as a cone. Then construct a circle at the intersection of the cone and the cylinder.
For wall thickness:
Origin off the top. Then offset your Z down to the desired gage point height. From here....
Easiest: Make an auto vector point in the ID. Then, copy and paste that point around the origin with like 7 points or so. Then, on the outside wall, do the same thing. Then all the way around, report the distance between each opposing point.
Option 2: Make an autocircle in the ID and one on the OD. Both at the same Z height. Then, report the diameter of each of the features. Then, write a variable that says V1= LOC1.D.MEAS-LOC2.D.MEAS
Then make a generic circle, feed V1 into the diameter of that circle, then report the diameter of your generic circle.
DAN_M Hi Dan,
Just a thought for the thickness :
In your first solution, you measure a "real" thickness, so you can get a min and a max value (including the drifting defect)
Using PNT1.PR- PNT8.PR (if you measured 7 points by side) allow ignoring the drifting defect (if the alignement is the good one !).
In the second, you assume that centers are the same...
You can obtain the difference of diameters without dimension them (CIRC1.D-CIRC2.D).
Here, it should be the radius, so CIR1.R-CIR2.R, or (CIR1.D-CIR2.D)/2 ....
Nice solutions anyway !
Maybe "drifting" is not the good word for a portable cmm I mean accuracy of position of hits.
