hexagon logo

Intersection point and wall thickness please help

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.

Attached Files
Parents

  • 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 Disappointed
    I mean accuracy of position of hits.
Reply

  • 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 Disappointed
    I mean accuracy of position of hits.
Children
No Data