ExactMeasure reversing axes

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • ExactMeasure reversing axes

    What am I missing?
    Notice the values for the Y and Z axes in the following screen capture:
    Y and Z reversed.jpg

    This is offline. I needed to reprogram this job for a shorter machine so the Y and Z axes became reversed on the shorter machine.
    The Alignment is created before I define the Datums.
    The long axis should be the 30 inch dimension, so the bottom segment is correct.
    I have tried various approaches to get this to come out making some sense, but to no avail.
    So, I am posting it here to see if any of you folks can shed some light on this for me.

    I restarted the program completely when I started the re-programing project. I used the existing program and then deleted all of the code except for the custom Header and some setup stuff.
    Code for the feature and dimension below.
    Notice that the code for the cylinder has the "correct" axes, that is Y is 30.7403 and Z is 12.1546 (opposite of what is in the dimension).


    Code:
    
    
    CYL_SH_LEG_SMALL=FEAT/CONTACT/CYLINDER/DEFAULT,CARTESIAN,IN,LEAST_SQR
                THEO/<0.597,-30.7403,12.1546>,<-1,0,0>,0.9995,0.326
                ACTL/<0.597,-30.7403,12.1546>,<-1,0,0>,0.9995,0.326
                TARG/<0.597,-30.7403,12.1546>,<-1,0,0>
                START ANG=0,END ANG=360
                ANGLE VEC=<0,0.9299461,-0.3676959>
                DIRECTION=CCW
                REPORT VEC=<-1,0,0>
                SHOW FEATURE PARAMETERS=NO
                SHOW CONTACT PARAMETERS=YES
                  NUMHITS=5,NUMLEVELS=3,DEPTH=0.05,END OFFSET=0.05,PITCH=0
                  SAMPLE METHOD=SAMPLE_HITS
                  SAMPLE HITS=0,SPACER=0.1
                  AVOIDANCE MOVE=BOTH,DISTANCE=2
                  FIND HOLE=DISABLED,ONERROR=NO,READ POS=NO
                SHOW HITS=YES
                  HIT/BASIC,<0.873,-30.2756,11.9708>,<0,-0.9299461,0.3676959>,<0.873,-30.2756,11.9708>
                  HIT/BASIC,<0.873,-30.7714,11.6558>,<0,0.0623304,0.9980556>,<0.873,-30.7714,11.6558>
                  HIT/BASIC,<0.873,-31.2243,12.0301>,<0,0.9684684,0.2491364>,<0.873,-31.2243,12.0301>
                  HIT/BASIC,<0.873,-31.0083,12.5764>,<0,0.536216,-0.8440808>,<0.873,-31.0083,12.5764>
                  HIT/BASIC,<0.873,-30.4219,12.5398>,<0,-0.6370687,-0.770807>,<0.873,-30.4219,12.5398>
                  HIT/BASIC,<0.76,-30.4219,12.5398>,<0,-0.6370687,-0.770807>,<0.76,-30.4219,12.5398>
                  HIT/BASIC,<0.76,-31.0083,12.5764>,<0,0.536216,-0.8440808>,<0.76,-31.0083,12.5764>
                  HIT/BASIC,<0.76,-31.2243,12.0301>,<0,0.9684684,0.2491364>,<0.76,-31.2243,12.0301>
                  HIT/BASIC,<0.76,-30.7714,11.6558>,<0,0.0623304,0.9980556>,<0.76,-30.7714,11.6558>
                  HIT/BASIC,<0.76,-30.2756,11.9708>,<0,-0.9299461,0.3676959>,<0.76,-30.2756,11.9708>
                  HIT/BASIC,<0.647,-30.2756,11.9708>,<0,-0.9299461,0.3676959>,<0.647,-30.2756,11.9708>
                  HIT/BASIC,<0.647,-30.7714,11.6558>,<0,0.0623304,0.9980556>,<0.647,-30.7714,11.6558>
                  HIT/BASIC,<0.647,-31.2243,12.0301>,<0,0.9684684,0.2491364>,<0.647,-31.2243,12.0301>
                  HIT/BASIC,<0.647,-31.0083,12.5764>,<0,0.536216,-0.8440808>,<0.647,-31.0083,12.5764>
                  HIT/BASIC,<0.647,-30.4219,12.5398>,<0,-0.6370687,-0.770807>,<0.647,-30.4219,12.5398>
                ENDMEAS/
    FCFLOC3 =POSITION : CYL_SH_LEG_SMALL
                FEATCTRLFRAME/SHOWNOMS=NO,SHOWPARAMS=YES,SHOWEXPANDED=YES
                CADGRAPH=OFF,REPORTGRAPH=OFF,TEXT=OFF,MULT=100.00,ARROWDENSITY=100,OUTPUT=BOTH,UNITS=IN
                COMPOSITE=YES,FIT TO DATUMS=YES,DEV PERPEN CENTERLINE=ON,OUTPUT ALIGNMENT=Datum Reference Frame
                CUSTOMIZED DRF=NO
                STANDARDTYPE=ASME_Y14_5
                  SIZE TOLERANCES/1,DIAMETER,0.9995,0.0005,0
                  PRIMARY DIMENSION/POSITION,DIAMETER,0.002,MMC,<PZ>,<len>,A,B,MMC,<size>,C,MMC,<size>
                  SECONDARY DIMENSION/,DIAMETER,0.0005,MMC,<PZ>,<len>,<dat>,<dat>,<dat>
                  NOTE/FCFLOC3
                FEATURES/CYL_SH_LEG_SMALL,,
    Lately, it occurs to me
    What a long, strange trip it's been.

    2017 R1 (Offline programming)

  • #2
    It looks like your alignment is rotated 90° to you FCF.

    Comment


    • #3
      Exactly, but why is the FCF rotated like that?
      Is there a way to control that?
      I changed to "Current Alignment" in the Advanced Tab, and got the nominals to match what it looks like when measuring...but I still don't understand why I need to do that.
      Lately, it occurs to me
      What a long, strange trip it's been.

      2017 R1 (Offline programming)

      Comment


      • KIRBSTER269
        KIRBSTER269 commented
        Editing a comment
        What workplane is your Datum A? and what workplane is datum B? It says PC-DMIS requires the primary datum be leveled to Z+ and secondary be rotated to X+, So If your thinking your rotating to Y Xact may be rotating to X. Without seeing the whole picture, that is my best guess

    • #4
      I have found that 99% of the time when using FCFs, it changes the trihedron to something different than your current alignment. If you put your cursor in the FCF code, you should see a second trihedron pop up in your graphics window. As far as I know, there is no way to change this other than clicking the current alignment box.

      Comment


      • John Riggins
        John Riggins commented
        Editing a comment
        Thanks, yes, the FCF trihedron is changed and it looks like I will be clicking that "current alignment" box.

    • #5
      I'm not totally following. Is Xact calculating the alignment 2 different ways on 2 different machines with the same features chosen?
      PC-DMIS 2015.1, SP10, CAD++
      Global 7/10/7, 5/5/5
      Renishaw PH10MQ, PH10M, TP200

      Comment


      • #6
        Originally posted by Max Tasty View Post
        I'm not totally following. Is Xact calculating the alignment 2 different ways on 2 different machines with the same features chosen?
        Yes.
        Sort of.
        What I am working on now is creating a program with the Y and Z axes reversed.
        The first program was also written offfline (all programs are written offline).
        As you can see in the OP, Y and Z get switched in the second segment.
        They looked the same in the first program.

        I have just gotten used to the "Start Point" and "End Point" getting reversed in Xact, now I need to get used to the axes switching?
        ???
        No, I think I am about ready to ignore the XactMeasure option unless I absolutely need it on a surface profile callout.
        Profile +/-.001" surfaces can really use that datum shift.
        Lately, it occurs to me
        What a long, strange trip it's been.

        2017 R1 (Offline programming)

        Comment


        • #7
          Originally posted by Max Tasty View Post
          I'm not totally following. Is Xact calculating the alignment 2 different ways on 2 different machines with the same features chosen?
          No. When Xact is calculating the DRF it assumes primary datum Z, secondary X, and there is no way for us to change that. If your current alignment does it different, you see a difference in the two trihedrons.

          The dimension calculation in the FCF is always done in the same way - the alignment (DRF or Current alignment) you select on the Advanced tab doesn't affect that. It only affects the numbers you see in the summary table.
          AndersI
          SW support - Hexagon Metrology Nordic AB

          Comment


          • John Riggins
            John Riggins commented
            Editing a comment
            Thanks Anders,
            That is reassuring. Since I have been using the "Current Alignment" option I have not see any issues.

        • #8
          Originally posted by John Riggins View Post

          Yes.
          Sort of.
          What I am working on now is creating a program with the Y and Z axes reversed.
          The first program was also written offfline (all programs are written offline).
          As you can see in the OP, Y and Z get switched in the second segment.
          They looked the same in the first program.

          I have just gotten used to the "Start Point" and "End Point" getting reversed in Xact, now I need to get used to the axes switching?
          ???
          No, I think I am about ready to ignore the XactMeasure option unless I absolutely need it on a surface profile callout.
          Profile +/-.001" surfaces can really use that datum shift.
          You can select Customized DRF in Feature Control Frame. This will allow you to choose which degree of freedom is controlled by which datum.

          Comment


          • AndersI
            AndersI commented
            Editing a comment
            Just remember that if you do that you *must* create a current alignment first in exactly the same way. See the Help on Custom DRF.

        • #9
          It sometimes does this even if you are in the same alignment as the FCF.

          Comment


          • vpt.se
            vpt.se commented
            Editing a comment
            Then doublecheck your positive and negative nominals so they are correct, so the alignment created by Xact isn't rotated 90/180 degrees. The easiest way to "see" if you messed up when entering the nominals is to uncheck "fit to datums". Then you will (probably) get a large deviation in one of the axises evaluated as Xact won't best-fit the alignment.

        • #10
          I just came to say.......how is "current alignment" not a default setting at this point?

          Silly.

          Comment

          Related Topics

          Collapse

          Working...
          X