DCC shifting after manual alignment in multiple programs

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

  • DCC shifting after manual alignment in multiple programs

    Hello all,
    I am pretty green with the CMM but I am learning reasonably well thanks to this forum, I have no training at all so any wisdom will be appreciated. I however have a problem that persists across a few of the programs I have run, and am trying to understand what I am doing wrong.
    The scenario is pretty much the same in all instances, I start the machine (Hexagon 7.10.7 sf) home it out, touch off sphere with the master probe open my program, and touch off sphere with all probes used in program. So I am assuming the machine to be okay.

    I do the manual alignment (plane, circle, and rotate) as similar to the graphics as possible (most of the time). Then when DCC takes over the machine seems to be "looking" for the part about a quarter of an inch off of the actual position (as if the part had shifted towards me and to the left (seven o'clock). This has happened in a couple of programs before and I had gone in to change hit points manually and got around the problem. Lately though the programs are proven, and have run before and my supervisor, who wrote them ( had level one training) nor I understand the problem. Code is attached.
    Thanks in advance for the reviews and replies.






    PART NAME : 1594137 No Model
    REV NUMBER : 4
    SER NUMBER : 344
    STATS COUNT : 1

    STARTUP =ALIGNMENT/START,RECALL:USE_PART_SETUP,LIST=YES
    ALIGNMENT/END
    MODE/MANUAL
    RETRACT/0.02
    MOVESPEED/ 300
    TOUCHSPEED/ 3
    FORMAT/TEXT,OPTIONS, ,HEADINGS,SYMBOLS, ;NOM,TOL,MEAS,DEV,OUTTOL, ,
    LOADPROBE/3X40-SF
    TIP/T1A0B0, SHANKIJK=0, 0, 1, ANGLE=0
    MODE/MANUAL
    PLN1 =FEAT/PLANE,CARTESIAN,TRIANGLE
    THEO/<12.1562,15.4135,-21.7284>,<-0.0033208,-0.0024816,0.9999914>
    ACTL/<12.2283,12.2745,-21.728>,<-0.0016677,-0.0036723,0.9999919>
    MEAS/PLANE,4
    HIT/BASIC,NORMAL,<11.3127,16.6557,-21.7281>,<-0.0033208,-0.0024816,0.9999914>,<11.222,13.3956,-21.7256>,USE THEO=YES
    HIT/BASIC,NORMAL,<13.5593,16.0559,-21.7222>,<-0.0033208,-0.0024816,0.9999914>,<13.2275,13.3956,-21.7222>,USE THEO=YES
    HIT/BASIC,NORMAL,<12.8824,14.1614,-21.729>,<-0.0033208,-0.0024816,0.9999914>,<13.2275,11.1534,-21.7305>,USE THEO=YES
    HIT/BASIC,NORMAL,<10.8705,14.781,-21.7343>,<-0.0033208,-0.0024816,0.9999914>,<11.2364,11.1534,-21.7337>,USE THEO=YES
    ENDMEAS/
    CIR1 =FEAT/CIRCLE,CARTESIAN,IN,LEAST_SQR
    THEO/<12.2105,15.4561,0>,<0,0,1>,2.1263
    ACTL/<12.215,12.2871,0>,<0,0,1>,2.1254
    MEAS/CIRCLE,4,ZPLUS
    HIT/BASIC,NORMAL,<11.1787,15.7118,-22.1427>,<0.9706364,-0.2405515,0>,<11.1532,12.336,-22.1854>,USE THEO=YES
    HIT/BASIC,NORMAL,<12.2507,16.5186,-22.1427>,<-0.0377986,-0.9992854,0>,<12.2127,13.3496,-22.1854>,USE THEO=YES
    HIT/BASIC,NORMAL,<13.207,15.8266,-22.1427>,<-0.9373122,-0.3484907,0>,<13.2307,11.9739,-22.2041>,USE THEO=YES
    HIT/BASIC,NORMAL,<12.275,14.3949,-22.1427>,<-0.0606051,0.9981618,0>,<12.1016,11.2306,-22.3056>,USE THEO=YES
    ENDMEAS/
    LIN1 =FEAT/LINE,CARTESIAN,UNBOUNDED
    THEO/<12.2505,12.6124,0>,<-0.0139052,0.9999033,0>
    ACTL/<12.2275,10.2014,0>,<0.0066369,-0.999978,0>
    MEAS/LINE,2,ZPLUS
    HIT/BASIC,NORMAL,<12.2505,12.6124,-22.5343>,<0.9999033,0.0139052,0>,<12.2275,10.2014,-22.3832>,USE THEO=YES
    HIT/BASIC,NORMAL,<12.24,13.3645,-22.5343>,<0.9999033,0.0139052,0>,<12.2314,9.6101,-22.3832>,USE THEO=YES
    ENDMEAS/
    A1 =ALIGNMENT/START,RECALL:STARTUP,LIST=YES
    ALIGNMENT/LEVEL,ZPLUS,PLN1
    ALIGNMENT/TRANS,ZAXIS,PLN1
    ALIGNMENT/ROTATE,YPLUS,TO,LIN1,ABOUT,ZPLUS
    ALIGNMENT/TRANS,XAXIS,CIR1
    ALIGNMENT/TRANS,YAXIS,CIR1
    ALIGNMENT/END
    MODE/DCC
    MOVE/POINT,NORMAL,<-0.0253,-0.2568,1.0672>
    TOP OF PART=FEAT/PLANE,CARTESIAN,TRIANGLE
    THEO/<-0.0925,-0.2772,0.0001>,<0.0000766,-0.0000904,1>
    ACTL/<-0.0926,-0.2793,-0.0316>,<0.0015058,0.0388277,0.9992448>
    MEAS/PLANE,4
    HIT/BASIC,NORMAL,<-1.5565,-0.238,0.0001>,<0.0000766,-0.0000904,1>,<-1.5565,-0.2401,-0.0118>,USE THEO=YES
    HIT/BASIC,NORMAL,<0.4951,1.246,0.0002>,<0.0000766,-0.0000904,1>,<0.495,1.2438,-0.1044>,USE THEO=YES
    HIT/BASIC,NORMAL,<1.2997,-0.71,-0.0001>,<0.0000766,-0.0000904,1>,<1.2995,-0.712,0>,USE THEO=YES
    HIT/BASIC,NORMAL,<-0.6083,-1.4069,0>,<0.0000766,-0.0000904,1>,<-0.6084,-1.409,-0.01>,USE THEO=YES
    ENDMEAS/
    MOVE/POINT,NORMAL,<0.0971,-0.1843,0.6131>
    3.126 I.D. =FEAT/CYLINDER,CARTESIAN,IN,LEAST_SQR
    THEO/<-0.0767,-0.0523,-0.6269>,<0.0004858,0.0004504,-0.9999998>,2.1258,0.4275
    ACTL/<0.0201,-3.0883,-0.639>,<-0.0006023,0.0009036,-0.9999994>,2.1254,0.4264
    MEAS/CYLINDER,12
    HIT/BASIC,NORMAL,<-1.1394,-0.0192,-0.4147>,<0.9995108,-0.0312709,0.0004714>,<-1.1748,-0.0182,-0.4148>,USE THEO=YES
    HIT/BASIC,NORMAL,<-0.5669,0.8903,-0.4185>,<0.4612595,-0.8872652,-0.0001756>,<-0.5908,0.9376,-0.4186>,USE THEO=YES
    MOVE/CIRCULAR
    HIT/BASIC,NORMAL,<0.7747,0.5848,-0.422>,<-0.8006229,-0.5991682,-0.0006588>,<0.9113,0.6868,-0.422>,USE THEO=YES
    HIT/BASIC,NORMAL,<0.6493,-0.8284,-0.4184>,<-0.683213,0.7302191,-0.000003>,<0.6264,-0.8026,-0.4186>,USE THEO=YES
    HIT/BASIC,NORMAL,<-0.1547,-1.1124,-0.4153>,<0.0732709,0.997312,0.0004848>,<0.0853,-2.1465,-0.4256>,USE THEO=YES
    HIT/BASIC,NORMAL,<-0.8711,-0.7592,-0.4138>,<0.7470887,0.664724,0.0006623>,<0.7232,-2.4567,-0.4256>,USE THEO=YES
    HIT/BASIC,NORMAL,<-0.9541,-0.6521,-0.8323>,<0.8255553,0.5643209,0.0006552>,<0.7973,-2.5505,-0.8449>,USE THEO=YES
    HIT/BASIC,NORMAL,<-1.0968,0.2452,-0.8339>,<0.96003,-0.2798968,0.0003403>,<0.9293,-3.346,-0.8472>,USE THEO=YES
    HIT/BASIC,NORMAL,<0.3667,0.9137,-0.84>,<-0.4171141,-0.9088539,-0.000612>,<-0.3651,-3.9512,-0.8527>,USE THEO=YES
    HIT/BASIC,NORMAL,<0.7624,-0.7046,-0.8376>,<-0.7894473,0.6138184,-0.000107>,<-0.7303,-2.513,-0.8474>,USE THEO=YES
    HIT/BASIC,NORMAL,<0.0834,-1.1029,-0.8345>,<-0.1504897,0.9886115,0.0003722>,<-0.127,-2.1548,-0.8447>,USE THEO=YES
    HIT/BASIC,NORMAL,<-0.6765,-0.9298,-0.8325>,<0.5643336,0.8255466,0.000646>,<0.5492,-2.3053,-0.8437>,USE THEO=YES
    ENDMEAS/
    MOVE/POINT,NORMAL,<-0.015,0.0452,0.7625>
    MOVE/POINT,NORMAL,<0.4103,-2.5905,0.7675>
    FRONT OF LEFT EAR=FEAT/LINE,CARTESIAN,UNBOUNDED
    THEO/<-0.0748,-2.9494,0>,<0.0000055,1,0>
    ACTL/<-0.0012,-0.193,-0.0083>,<0.0079336,-0.9999678,-0.0012147>
    MEAS/LINE,2,ZPLUS
    HIT/BASIC,NORMAL,<-0.0748,-2.9494,-0.8484>,<1,-0.0000055,0>,<-0.1203,-0.1924,-0.8565>,USE THEO=YES
    HIT/BASIC,NORMAL,<-0.0748,-2.1109,-0.8504>,<1,-0.0000055,0>,<-0.1137,-1.0309,-0.8594>,USE THEO=YES
    ENDMEAS/
    A5 =ALIGNMENT/START,RECALL:A1,LIST=YES
    ALIGNMENT/LEVEL,ZPLUS,TOP OF PART
    ALIGNMENT/TRANS,ZAXIS,TOP OF PART
    ALIGNMENT/ROTATE,YPLUS,TO,FRONT OF LEFT EAR,ABOUT,ZPLUS
    ALIGNMENT/TRANS,XAXIS,3.126 I.D.
    ALIGNMENT/TRANS,YAXIS,3.126 I.D.
    ALIGNMENT/END

  • #2
    The vectors for the lines Theos are wrong. That being said. Clean up your vectors for the features. I am " assuming here " ... Your manual features are the same as your DCC features ? Why wouldn't your Theoretical x-y be 0.0 ? If you are following your graphics when you do the manual alignment, when you do the line it will ask for 1 hit and the 2nd hit of the line will be "shown closer to you, as in NEG Y instead of positive Y. If the manual alignment is done this way and you are rotating to Y +, It will flip you part in y and look for everything in a "negative " image of the actual part.

    Comment


    • #3
      I have a couple things that I noticed looking through the code that may cause issues.

      1) For the line in the manual alignment portion, the IJK ACTUAL vectors seem to be flipped with the THEO vectors. This also seems to be true for the second line feature as well. Make sure you measure a line in the same direction during the manual alignment or PCD will do weird things. It looks like that may be a possibility from what I'm seeing.


      2) This isn't the issue your facing but stay away from using anything besides letters, numbers, and underscore in labeling features. decimal places and spaces can cause PCD to be buggy.

      Comment


      • #4
        Technically its
        1: Level
        2:Rotate
        3:Origin

        Also Naming Your features. Don't Use Spaces Front_Of_Left_Ear <<<<Letters, underscore, and numbers. You need to fix your Hits and THEO, Vectors also

        Best Practice I tell everyone is to make an alignment after each Feature that way you can see what your Trihedron is doing.

        Make a Plane.
        Alignment - Level and Origin (Z Level and Z Origin)

        Make Your Line
        Alignment - Level, Rotate, and Origin (Z Level, Rotate your Y about Z, and Origin Plane Z) the rotation will effect everything

        Make Your Circle
        Alignment - Level, Rotate, and Origin (Z Level, Rotate Your Y about Z, and Origin Plane Z, and Origin Circle X and Y)

        A lot of people will say this is over kill (it is), But not when your new it's good practice. That way you can watch what your trihedron is doing each step of the way.

        If that arrow is pointing toward you that's YMINUS, this will rotate the part in the wrong direction, if you choose Yplus about ZPlus.
        Last edited by KIRBSTER269; 04-16-2019, 09:56 AM.
        (In Memory of my Loving wife, "Ronda" who I lost March 7, 2016. I love you baby.)
        They say "Nobody's Perfect." I must be Nobody.

        Comment


        • AndersI
          AndersI commented
          Editing a comment
          It's definitely not overkill - LEVEL is necessary before you can measure CIRCLE or LINE correctly (as they are 2D features).

        • KIRBSTER269
          KIRBSTER269 commented
          Editing a comment
          AndersI no I was talking making alignments after alignments after alignments. repeating your leveling 3 times, repeating your rotation twice, etc. instead of just recalling your prior alignment. I just think this is good practice for new people

        • AndersI
          AndersI commented
          Editing a comment
          Yeah, well, it's always good to do full (or as much as you have right now) alignments, that makes them independent of previous alignments, and they are easier to move around in the program.

      • #5
        Thank you Schlag and CodeWarrior! The problem is no longer! I payed closer attention to the manual alignment, and changed the names of the features, and it ran through the routine without missing a hit. I appreciate your help. This issue of DCC "shifting" seems of my own creation and I think I have got it whipped now.

        Comment

        Related Topics

        Collapse

        Working...
        X