hexagon logo

2D or 3D Dimensions

Hello,

I'm quite new to the CMM universe and I have a measuring task where I'm unsure if I evaluate it correctly.

The task is the distance between MP_D2 and D2_DOM8.25_P2.

I read that the 2D distance is a projection of the measuring points on a plane referring to the coordinate system.

And that the 3D is the distance referring to the part?

I dont know how I should evaluate it and the differ of both results is really high.

Thanks in advance!

Best regards, Brad.
  • Could you tell us a little more ?
    I can't see what type of features there are... And the answer could depends on it !
    In addition, you shouldn't use "." in the feature names, replace them by a "_".
  • A 2D distance 2 dimensional distance, ignoring the 3rd dimension. If you are in the Z workplane it will only measure the distance relative to the X and Y axis. Any distance in Z will be ignored. If you view it as vision and you are looking at two points staring down the Z axis you can't see any change in height in the Z axis. CMM software is the same it only "sees" 2D distances that aren't in the workplane.

    a 3D distance takes all 3 axes into account when measuring distance.
  • Thank you very much for your help, my evaluation was not in the correct workplane. So in generall you can say that points are measured in 2 dimension becuase they have to be reflected on the same plane and a distance between 2 planes are measured in all 3 dimensions?
  • Hello please can you help I have a confusion in 2d and 3d measurements can you clarify.I am checking a angle between two line it is giving different values in 2d and 3d
  • 2D is the angle between 2 lines projcted in the actual workplane, 3D is the angle measured between lines without any projection, along a vector perp to both vectors.
    In Z workplane, it should be :
    ASSIGN/V1=UNIT(LN1.IJK*MPOINT(1,1,0))
    ASSIGN/V2=UNIT(LN2.IJK*MPOINT(1,1,0))
    ASSIGN/ANGLE_2D=RAD2DEG(ACOS(DOT(V1,V2)))

    ASSIGN/ANGLE_3D=RAD2DEG(ACOS(DOT(LN1.IJK,LN2.IJK)))
    It's measured along
    ASSIGN/V3=CROSS(LN1.IJK,LN2.IJK)
  • First:

    Think of a workplane as the "eyes" of the software.

    PC DMIS can only "see" 2d features if it is "looking at it" correctly.

    Imagine if you will a line in three dimensional space... It is a straight line that is following the Y+ axis of your alignment and it has no slope it is just a straight line. You could "see" the line if your workplane was ZPLUS (looking down at it), if your workplane was ZMINUS (standing below it looking up, if your workplane was XPLUS (standing on the right side), and also if your workplane was XMINUS (standing on the left side). You would NOT be able to "see" the line if your workplane was YPLUS or YMINUS because from those perspectives all the software can "see" in 3d space is a point (start point or end point of line).

    SO....

    When creating a program in PC DMIS, you must pay attention to your workplane. When you are measuring 3D features (planes, cylinders, cones, etc) you can be in any workplane you want because the software can "see" them...BUT...when you are probing 2d features OR constructing things & 2d features are being used, you MUST be in a workplane that will allow the software to "see" what it is constructing or you will get junk features/results that make no sense.

    Second:

    We would be happy trouble-shoot your program but would have to see it first. There are too many variables here for us to suggest a fix especially since you are so new to this.