Understand offset alignments

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

  • Understand offset alignments

    I am having to do a program for a forge with no datum structure. its all profile to it self. I have no idea how the last programmer got his info but it worked. My respects to him and RIP. from what I am told he did it all with no help from Engineering.
    I see the offsets but I don't know how he got it or why he chose that direction. All of the programs were done by him. i know there are different ways of doing it but i like to learn and understand this one because all the programs are like this. I understand the Level, and translations.. I DONT understand the rotate offset number he got (how he got it) and how its working. For A3, READ_POINT ALNM.

    Sorry, I am having problems uploading pictures. but if you willing I can email them.

    Code:
    PNT1 =FEAT/POINT,CARTESIAN
    THEO/<-57.71,-3.8,4.4>,<0,0,1>
    ACTL/<0,0,0>,<0,0,1>
    READPOINT/
    A1 =ALIGNMENT/START,RECALL:STARTUP,LIST=YES
    ALIGNMENT/TRANS,XAXIS,PNT1
    ALIGNMENT/TRANS,YAXIS,PNT1
    ALIGNMENT/TRANS,ZAXIS,PNT1
    ALIGNMENT/END
    PNT2 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<0.01,0,-0.12>,<-0.1093883,-0.4880256,0.8659476>
    ACTL/<0.01,0,-0.12>,<-0.1093883,-0.4880256,0.8659476>
    TARG/<0.01,0,-0.12>,<-0.1093883,-0.4880256,0.8659476>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    A2 =ALIGNMENT/START,RECALL:A1,LIST=YES
    ALIGNMENT/TRANS,XAXIS,PNT2
    ALIGNMENT/TRANS,YAXIS,PNT2
    ALIGNMENT/TRANS,ZAXIS,PNT2
    ALIGNMENT/END
    PNT3 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<0.05,0.44,0.05>,<-0.1253261,0,0.9921156>
    ACTL/<0.05,0.44,0.05>,<-0.1253261,0,0.9921156>
    TARG/<0.05,0.44,0.05>,<-0.1253261,0,0.9921156>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    PNT4 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<-0.41,0.94,-0.01>,<-0.1253261,0,0.9921156>
    ACTL/<-0.41,0.94,-0.01>,<-0.1253261,0,0.9921156>
    TARG/<-0.41,0.94,-0.01>,<-0.1253261,0,0.9921156>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    PNT5 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<0.03,1.29,0.04>,<-0.1253261,0,0.9921156>
    ACTL/<0.03,1.29,0.04>,<-0.1253261,0,0.9921156>
    TARG/<0.03,1.29,0.04>,<-0.1253261,0,0.9921156>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    PNT6 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<-0.4,3.39,-0.01>,<-0.1253261,0,0.9921156>
    ACTL/<-0.4,3.39,-0.01>,<-0.1253261,0,0.9921156>
    TARG/<-0.4,3.39,-0.01>,<-0.1253261,0,0.9921156>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    PNT7 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<-0.41,6.48,-0.01>,<-0.1253261,0,0.9921156>
    ACTL/<-0.41,6.48,-0.01>,<-0.1253261,0,0.9921156>
    TARG/<-0.41,6.48,-0.01>,<-0.1253261,0,0.9921156>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    PNT8 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<0.22,6.57,0.07>,<-0.1253261,0,0.9921156>
    ACTL/<0.22,6.57,0.07>,<-0.1253261,0,0.9921156>
    TARG/<0.22,6.57,0.07>,<-0.1253261,0,0.9921156>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    PNT9 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<0.06,6.94,0.05>,<-0.1253261,0,0.9921156>
    ACTL/<0.06,6.94,0.05>,<-0.1253261,0,0.9921156>
    TARG/<0.06,6.94,0.05>,<-0.1253261,0,0.9921156>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    PLN1 =FEAT/PLANE,CARTESIAN,OUTLINE,NO,LEAST_SQR
    THEO/<-0.12,3.72,0.02>,<-0.1253261,0,0.9921156>
    ACTL/<-0.12,3.72,0.02>,<-0.1253261,0,0.9921156>
    CONSTR/PLANE,BF,PNT3,PNT5,PNT4,PNT6,PNT8,PNT9,PNT7,,
    OUTLIER_REMOVAL/OFF,3
    FILTER/OFF,WAVELENGTH=0
    A3 =ALIGNMENT/START,RECALL:A2,LIST=YES
    ALIGNMENT/TRANS,ZAXIS,PLN1
    ALIGNMENT/LEVEL,ZPLUS,PLN1
    ALIGNMENT/ROTATE_OFFSET,7.2,ABOUT,YPLUS
    ALIGNMENT/END
    MOVE/POINT,NORMAL,<-1,6.94,0.35>
    PNT10 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<-0.8,6.39,-0.42>,<-0.9958619,0,0.0908798>
    ACTL/<-0.8,6.39,-0.42>,<-0.9958619,0,0.0908798>
    TARG/<-0.8,6.39,-0.42>,<-0.9958619,0,0.0908798>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    A4 =ALIGNMENT/START,RECALL:A3,LIST=YES
    ALIGNMENT/TRANS,XAXIS,PNT10
    ALIGNMENT/END
    PNT11 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<0,6.12,-0.37>,<-0.9958619,0,0.0908798>
    ACTL/<0,6.12,-0.37>,<-0.9958619,0,0.0908798>
    TARG/<0,6.12,-0.37>,<-0.9958619,0,0.0908798>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    PNT12 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<-0.01,4.56,-0.53>,<-0.9958619,0,0.0908798>
    ACTL/<-0.01,4.56,-0.53>,<-0.9958619,0,0.0908798>
    TARG/<-0.01,4.56,-0.53>,<-0.9958619,0,0.0908798>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    PNT13 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<-0.1,3.12,-1.49>,<-0.9958619,0,0.0908798>
    ACTL/<-0.1,3.12,-1.49>,<-0.9958619,0,0.0908798>
    TARG/<-0.1,3.12,-1.49>,<-0.9958619,0,0.0908798>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    PNT14 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<-0.13,2.13,-1.83>,<-0.9958619,0,0.0908798>
    ACTL/<-0.13,2.13,-1.83>,<-0.9958619,0,0.0908798>
    TARG/<-0.13,2.13,-1.83>,<-0.9958619,0,0.0908798>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    PNT15 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<-0.02,3.02,-0.58>,<-0.9958619,0,0.0908798>
    ACTL/<-0.02,3.02,-0.58>,<-0.9958619,0,0.0908798>
    TARG/<-0.02,3.02,-0.58>,<-0.9958619,0,0.0908798>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    PNT17 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<-0.01,1.66,-0.58>,<-0.9958619,0,0.0908798>
    ACTL/<-0.01,1.66,-0.58>,<-0.9958619,0,0.0908798>
    TARG/<-0.01,1.66,-0.58>,<-0.9958619,0,0.0908798>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    PLN2 =FEAT/PLANE,CARTESIAN,OUTLINE,NO,LEAST_SQR
    THEO/<-0.04,3.43,-0.9>,<-0.9958619,0,0.0908798>
    ACTL/<-0.04,3.43,-0.9>,<-0.9958619,0,0.0908798>
    CONSTR/PLANE,BF,PNT11,PNT12,PNT17,PNT14,PNT13,PNT15,,
    OUTLIER_REMOVAL/OFF,3
    FILTER/OFF,WAVELENGTH=0
    LIN1 =FEAT/LINE,CARTESIAN,UNBOUNDED,NO
    THEO/<0.03,3.58,-0.08>,<0,1,0>
    ACTL/<0.03,3.58,-0.08>,<0,1,0>
    CONSTR/LINE,INTOF,PLN2,PLN1
    MOVE/POINT,NORMAL,<-0.34,-0.5,-0.55>
    PNT18 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<0.86,-0.17,-0.48>,<0,-1,0>
    ACTL/<0.86,-0.17,-0.48>,<0,-1,0>
    TARG/<0.86,-0.17,-0.48>,<0,-1,0>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    PNT19 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<0.98,-0.17,-0.68>,<0,-1,0>
    ACTL/<0.98,-0.17,-0.68>,<0,-1,0>
    TARG/<0.98,-0.17,-0.68>,<0,-1,0>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    PNT20 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<0.89,-0.17,-1.54>,<0,-1,0>
    ACTL/<0.89,-0.17,-1.54>,<0,-1,0>
    TARG/<0.89,-0.17,-1.54>,<0,-1,0>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    PNT21 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
    THEO/<1.03,-0.17,-1.64>,<0,-1,0>
    ACTL/<1.03,-0.17,-1.64>,<0,-1,0>
    TARG/<1.03,-0.17,-1.64>,<0,-1,0>
    SNAP=NO
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=YES
    AVOIDANCE MOVE=NO,DISTANCE=0.2
    SHOW HITS=NO
    PLN3 =FEAT/PLANE,CARTESIAN,OUTLINE,NO,LEAST_SQR
    THEO/<0.94,-0.17,-1.08>,<0,-1,0>
    ACTL/<0.94,-0.17,-1.08>,<0,-1,0>
    CONSTR/PLANE,BF,PNT18,PNT19,PNT20,PNT21,,
    OUTLIER_REMOVAL/OFF,3
    FILTER/OFF,WAVELENGTH=0
    LIN2 =FEAT/LINE,CARTESIAN,UNBOUNDED,NO
    THEO/<0.03,3.58,-0.08>,<0,1,0>
    ACTL/<0.03,3.58,-0.08>,<0,1,0>
    CONSTR/LINE,INTOF,PLN2,PLN1
    LIN3 =FEAT/LINE,CARTESIAN,UNBOUNDED,NO
    THEO/<-0.05,-0.17,-0.94>,<-0.0908798,0,-0.9958619>
    ACTL/<-0.05,-0.17,-0.94>,<-0.0908798,0,-0.9958619>
    CONSTR/LINE,INTOF,PLN3,PLN2
    PNT22 =FEAT/POINT,CARTESIAN,NO
    THEO/<0.03,-0.17,-0.08>,<0,1,0>
    ACTL/<0.03,-0.17,-0.08>,<0,1,0>
    CONSTR/POINT,INT,LIN2,LIN3
    READ_POINT =ALIGNMENT/START,RECALL:A4,LIST=YES
    ALIGNMENT/TRANS,XAXIS,PNT22
    ALIGNMENT/TRANS,YAXIS,PNT22
    ALIGNMENT/TRANS,ZAXIS,PNT22
    ALIGNMENT/LEVEL,ZPLUS,PLN1
    ALIGNMENT/LEVEL,YMINUS,PLN3
    ALIGNMENT/LEVEL,XMINUS,PLN2
    ALIGNMENT/ROTATE_OFFSET,-6.21,ABOUT,YPLUS
    ALIGNMENT/END
    Last edited by ProbFlex; 02-22-2021, 11:32 AM.

  • #2
    I suspect those rotations are just in there to square the alignment up with the CMM axis. I like to do that so it is easier to program moves and so the job box works properly regardless of if is set to use the machine or the part coordinate system.

    The easy way to get this value in CAD is to use the "Rotate to Cad Surface or Edge" button shown in the attached picture. Click the button, then click a Cad feature that you know is square(ish) to the machine axis. It will find the rotation value you need to use for you.

    Rotation Button.png

    Comment


    • ProbFlex
      ProbFlex commented
      Editing a comment
      Ill give it a try. thank you!

    • ProbFlex
      ProbFlex commented
      Editing a comment
      this worked. I have use the F1 and not much info on it. would you have a link or PDF?

      Thank you.

    • ProbFlex
      ProbFlex commented
      Editing a comment
      oops. found it. spoke to soon. haha

  • #3
    That last alignment makes my head hurt.

    Comment


    • ProbFlex
      ProbFlex commented
      Editing a comment
      it's the same as Level, rotate, with 3 translate. but back words and an extra level.
      pls. explain how the level two level works in the alignment? I though it could only be one level per alignment.

    • Cris_C
      Cris_C commented
      Editing a comment
      I saw the unconventional order of alignment steps, but I didn't notice that it is being leveled 3 times in one alignment. I have no idea what that does. It seems like each consecutive level would just override the previous ones.

  • #4
    Code:
    ALIGNMENT/LEVEL,ZPLUS,PLN1
    ALIGNMENT/LEVEL,YMINUS,PLN3
    ALIGNMENT/LEVEL,XMINUS,PLN2
    YMINUS level will override the ZPLUS level and the last (XMINUS) will override the YMINUS level... So the only effective level here is the last one.
    PC-DMIS CAD++ 2o19 R1 SP11

    Comment


    • ProbFlex
      ProbFlex commented
      Editing a comment
      I understand the overtight (and I don't understand) but is it helping anything by
      ALIGNMENT/LEVEL,ZPLUS,PLN1
      ALIGNMENT/LEVEL,YMINUS,PLN3
      ALIGNMENT/LEVEL,XMINUS,PLN2

      for example:
      ZPLUS, PLN1 then YMINUS,PLN3 = 90 DEG to each other
      YMINUS,PLN3 then XMINUS,PLN2 = 90 DEG to each other

      or is this the same as just Leveling to XMINUS,PLN2.

      what the idea/concept behind this and does it even work?

  • #5
    Originally posted by vpt.se View Post
    Code:
    ALIGNMENT/LEVEL,ZPLUS,PLN1
    ALIGNMENT/LEVEL,YMINUS,PLN3
    ALIGNMENT/LEVEL,XMINUS,PLN2
    YMINUS level will override the ZPLUS level and the last (XMINUS) will override the YMINUS level... So the only effective level here is the last one.
    Those guys on the other side of planet beat me to it.

    Comment


    • ProbFlex
      ProbFlex commented
      Editing a comment
      I understand the overtight (and I don't understand) but is it helping anything by
      ALIGNMENT/LEVEL,ZPLUS,PLN1
      ALIGNMENT/LEVEL,YMINUS,PLN3
      ALIGNMENT/LEVEL,XMINUS,PLN2

      for example:
      ZPLUS, PLN1 then YMINUS,PLN3 = 90 DEG to each other
      YMINUS,PLN3 then XMINUS,PLN2 = 90 DEG to each other

      or is this the same as just Leveling to XMINUS,PLN2.

      what the idea/concept behind this and does it even work?

  • #6
    ProbFlex

    When you level to a plane or cylinder, that's the only leveling you need. It levels the part. An additional leveling cancels out the first one. You would need to rotate to a plane, a line, or point-to-point in order to lock down that degree of freedom.

    If you open your alignment dialog box and the trihedron is still moving around, you do not have all degrees of freedom locked down.

    Comment


    • ProbFlex
      ProbFlex commented
      Editing a comment
      Question 1:
      as the levels cancel each other out leaving XMINUS,PLN2 active, do they also cancel the DOF that would of been locking by ALIGNMENT/LEVEL,ZPLUS,PLN1 and YMINUS,PLN3 or do they stay constrain?

      bfire85 : I think you answer this with the statement above? just so i am totally clear.

      I have been fooled by the trihedron before. It would look locked, when it is really not haha...
      But I see what you mean "If you open your alignment dialog box and the trihedron is still moving around, you do not have all degrees of freedom locked down."

      Question 2:
      Is there a PDF that could give me a good visual image hoe the trihedron or plane level looks like when it is rotating to a certain axis.

  • #7
    ProbFlex

    Here's a good read:

    Attached Files

    Comment


    • ProbFlex
      ProbFlex commented
      Editing a comment
      thank you, thank you!!

  • #8
    ProbFlex

    In the PC-DMIS help file, search for "Creating and Using Alignments: Introduction". This will help you understand alignments more.

    If you have not gone to Level 1 class, please contact your rep about signing up and attending the week long class. I think it's like $1800.

    Comment


    • #9
      thank you. level 1 class was very simple that didn't help me with real word work. The lecture to me was based on direction/driven of datum structure. I have to program PROFILE to it self with out datums/ target points to a forge. see attached.
      Attached Files

      Comment


      • #10
        Originally posted by ProbFlex View Post
        thank you. level 1 class was very simple that didn't help me with real word work. The lecture to me was based on direction/driven of datum structure. I have to program PROFILE to it self with out datums/ target points to a forge. see attached.
        Put all those points into a feature set and dimension profile. If you have a solid alignment down, this won't cause issues.

        Comment


        • ProbFlex
          ProbFlex commented
          Editing a comment
          yes your right, once i have a solid alignment the rest is easy.
          without datums/target datums how would you approach this part for a solid alignment?

      • #11
        ProbFlex



        This would just be form. You create the points, create the set, measure profile without any datums. With datums is Form and Location, without datums, it's just form.

        Are you using Xact or Legacy?

        Comment


        • ProbFlex
          ProbFlex commented
          Editing a comment
          I am having to use Legacy, because we are dimensioning each T-value on its own. Its how it was agreed by the customer.

          [CODE]
          DIM PRFL_1= LOCATION OF POINT PRFL_PNT1 UNITS=IN ,$
          GRAPH=OFF TEXT=OFF MULT=10.00 OUTPUT=BOTH HALF ANGLE=NO
          AX NOMINAL +TOL -TOL MEAS DEV OUTTOL
          T 0.0000 0.0900 0.0300 0.0000 0.0000 0.0000 --#---------
          END OF DIMENSION PRFL_1
          [CODE]

        • ProbFlex
          ProbFlex commented
          Editing a comment
          Q: When reporting a T-value ( IN Legacy), I don't have the form check. should i have the form and T being reporting? how do this two work together?

      • #12
        Quote from ProbFlex's comment
        "I am having to use Legacy, because we are dimensioning each T-value on its own. Its how it was agreed by the customer.

        [CODE]
        DIM PRFL_1= LOCATION OF POINT PRFL_PNT1 UNITS=IN ,$
        GRAPH=OFF TEXT=OFF MULT=10.00 OUTPUT=BOTH HALF ANGLE=NO
        AX NOMINAL +TOL -TOL MEAS DEV OUTTOL
        T 0.0000 0.0900 0.0300 0.0000 0.0000 0.0000 --#---------
        END OF DIMENSION PRFL_1
        [CODE]"


        That's tough. Others may have better ideas. I’m thinking a good route to go is a 3D Best Fit alignment to all the points you need to report as a set. Then report the individual profile values. I’m not quite sure if that works if you report them as T-values though. I know It would work just fine with individual points reported as legacy profiles.
        Last edited by Cris_C; 02-23-2021, 11:26 PM.

        Comment


        • Cris_C
          Cris_C commented
          Editing a comment
          I just verified, It works just the same with T-Values.

        • ProbFlex
          ProbFlex commented
          Editing a comment
          Cool! ill give that a try. thank you Chris.

      • #13
        From comment from ProbFlex :
        "I am having to use Legacy, because we are dimensioning each T-value on its own. Its how it was agreed by the customer. "

        Do you know why the customer is requiring this? Is it simply that they want to see a list of all the profile values, or do they have specific requirements that require you to report the profile of each point as a separate dimension?

        If the customer just wants to see all the deviation values for each point, you can report the profile just like bfire85 suggested and turn on textual analysis. That will list the deviations of all the points. The only problem with that is it won't tell you which point refers to each value, it just lists the values in the order in which the set was constructed.

        If the customer has you using a specific point map and needs a report with point labels, or wants to see screenshots/snapshots with diminfo boxes for each point, or is just used to seeing the report a certain way and will freak out if you change anything, you may want to explore best fit alignments.

        Comment


        • ProbFlex
          ProbFlex commented
          Editing a comment
          Its for data collection. we have to show we have control of our process. Senses all we do is profiling we need all the points of the PRFL to create graphs/charts in order to get a clear picture/understanding. It will let us know how we can improve our process once we understand what is happing to the part when being forge. Once we prove we have a good process we can convert to sampling inspection, then 100% inspection which is what we are doing now. Once this is done, we can keep it simple with reporting max and mid with Xact.

      • #14
        Whilst the order of the alignment looks horrible (and makes me question the understanding and competence of the original programmer) it's maybe not as bad as it looks.


        Originally posted by vpt.se View Post
        Code:
        ALIGNMENT/LEVEL,ZPLUS,PLN1
        ALIGNMENT/LEVEL,YMINUS,PLN3
        ALIGNMENT/LEVEL,XMINUS,PLN2
        YMINUS level will override the ZPLUS level and the last (XMINUS) will override the YMINUS level... So the only effective level here is the last one.

        So whilst I agree with vpt.se in one respect, that each subsequent Level will supersede the previous one, I have to point out that the previous one will act as rotations.

        So in proper order this alignment would be the same as...


        ALIGNMENT/ROTATE,XMINUS,PLN2
        ALIGNMENT/LEVEL,YMINUS,PLN3


        And although he origins on the point first in XYZ, as this point is in effect a corner point, the incorrect order doesn't actually have any impact.


        Automettech - Automated Metrology Technology

        Comment

        widgetinstance 190 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
        Working...
        X