Combining two circle scans

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

  • Combining two circle scans

    We make a lot of camshafts here, where I need to scan an OD from two directions. I've created one Adaptive Circle Scan (FEAT_98_A) which goes from say 0° - 90° and another Adaptive Circle Scan (FEAT_98_B) which goes from say 90° to 180°. I want to merge these two features into one Constructed Circle, however i'm getting some pushback from PC DMIS. Now, I know that I could probably just use two Linear Open Scans, but I find those to be clunky, where an Adaptive Circle Scan is much more user friendly for making adjustments. I'm not familiar (yet) with extracting the HITS from a feature, but I have a hunch that I should be going that route.

    Can anyone lead me in the right direction on the best practice to accomplish this? This is NOT a one time deal, as I will have to do this for many journals on many cams. Your feedback is much appreciated. Screenshot 2021-03-17 094531.png
    Attached Files
    "Try not to be a dick"

  • #2
    ncsteinb

    Measure both arcs

    Switch to Command Mode if you don't already use it

    CONSTRUCT a FEATURESET, click the two arcs, click OK.

    Now that the featureset is in your edit window, you'll have to do some manual typing. You have to tell PC DMIS to use the .numhit values. This is called "hardcoding".

    Now that the featureset is hardcoded, CONSTRUCT a circle out of the featureset. Now you have your full circle.

    Code:
    CIR1 =FEAT/CONTACT/CIRCLE/DEFAULT,CARTESIAN,IN,LEAST_SQR
    THEO/<3.1496,2.3622,0>,<0,0,1>,2.3622
    ACTL/<3.1496,2.3622,0>,<0,0,1>,2.3622
    TARG/<3.1496,2.3622,0>,<0,0,1>
    START ANG=0,END ANG=180
    ANGLE VEC=<1,0,0>
    DIRECTION=CCW
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=NO
    CIR2 =FEAT/CONTACT/CIRCLE/DEFAULT,CARTESIAN,IN,LEAST_SQR
    THEO/<3.1496,2.3622,0>,<0,0,1>,2.3622
    ACTL/<3.1496,2.3622,0>,<0,0,1>,2.3622
    TARG/<3.1496,2.3622,0>,<0,0,1>
    START ANG=180,END ANG=360
    ANGLE VEC=<1,0,0>
    DIRECTION=CCW
    SHOW FEATURE PARAMETERS=NO
    SHOW CONTACT PARAMETERS=NO
    SCN1 =FEAT/SET,CARTESIAN
    THEO/<3.1496,2.3622,0>,<0,0,1>
    ACTL/<3.1496,2.3622,0>,<0,0,1>
    CONSTR/SET,BASIC,CIR1.HIT[1..CIR1.NUMHITS],CIR2.HIT[1..CIR2.NUMHITS],,
    CIR_A =FEAT/CIRCLE,CARTESIAN,IN,LEAST_SQR,NO
    THEO/<3.1496,2.3622,0>,<0,0,1>,2.3622
    ACTL/<3.1496,2.3622,0>,<0,0,1>,2.3622
    CONSTR/CIRCLE,BF,2D,SCN1,,
    OUTLIER_REMOVAL/OFF,3
    FILTER/OFF,UPR=0
    Last edited by DAN_M; 03-17-2021, 09:57 AM.
    SF7107(PCD), SF454(PCD), 152614(Quindos), 9159(Quindos), 7107(Quindos), B&S Manual, M&M Gear Checker

    Comment


    • #3
      DAN_M Sweet! I will give this a shot. Thanks for the quick reply!!
      Last edited by ncsteinb; 03-17-2021, 10:17 AM.
      "Try not to be a dick"

      Comment


      • #4
        Originally posted by ncsteinb View Post
        DAN_M Sweet! I will give this a shot. Thanks for the quick reply!!
        Happy to help!

        Just so you know, the reason PCD makes you do this: When constructing things together, PCD looks at the XYZ and IJK of each feature & uses those six inputs to compute the position/direction of the feature you're making. If two features you're construct together share a centroid, the software will be mad and not let you proceed because its a violation of one it's rules.
        What we have done here is honored that rule and instead told PCD to use the "hits" instead of centroid, which it "understands" and allows us to do.
        Last edited by DAN_M; 03-17-2021, 10:13 AM.
        SF7107(PCD), SF454(PCD), 152614(Quindos), 9159(Quindos), 7107(Quindos), B&S Manual, M&M Gear Checker

        Comment


        • #5
          DAN_M So, does this look about right?

          Code:
          FEAT_98_A =FEAT/CONTACT/CIRCLE/ADAPTIVE_CIRCLE_SCAN,CARTESIAN,OUT,LEAST_SQR
          THEO/<0,455.3,0>,<0,-1,0>,46.5,0
          ACTL/<0,455.3,0>,<0,-1,0>,46.5,0
          TARG/<0,455.3,0>,<0,-1,0>
          START ANG=270,END ANG=345
          ANGLE VEC=<0,0,-1>
          DIRECTION=CCW
          SHOW FEATURE PARAMETERS=NO
          SHOW CONTACT PARAMETERS=NO
          
          FEAT_98_B =FEAT/CONTACT/CIRCLE/ADAPTIVE_CIRCLE_SCAN,CARTESIAN,OUT,LEAST_SQR
          THEO/<0,455.3,0>,<0,-1,0>,46.5,0
          ACTL/<0,455.3,0>,<0,-1,0>,46.5,0
          TARG/<0,455.3,0>,<0,-1,0>
          START ANG=190,END ANG=270
          ANGLE VEC=<0,0,-1>
          DIRECTION=CCW
          SHOW FEATURE PARAMETERS=NO
          SHOW CONTACT PARAMETERS=NO
          
          FEAT_98_FEATSET=FEAT/SET,CARTESIAN
          THEO/<-16.471,456.8,-11.509>,<0,1,0>
          ACTL/<-16.471,456.8,-11.509>,<0,0,1>
          CONSTR/SET,BASIC,FEAT_98_A.HIT[1..FEAT_98_A.NUMHITS],FEAT_98_B.HIT[1..FEAT_98_B.NUMHITS],,
          
          FEAT_98 =FEAT/CIRCLE,CARTESIAN,OUT,LEAST_SQR,NO
          THEO/<0,456.8,0>,<0,1,0>,46.5
          ACTL/<0,456.8,0>,<0,1,0>,46.5
          CONSTR/CIRCLE,BF,2D,FEAT_98_FEATSET,,
          OUTLIER_REMOVAL/OFF,3
          FILTER/OFF,UPR=0
          Attached Files
          Last edited by ncsteinb; 03-17-2021, 10:31 AM.
          "Try not to be a dick"

          Comment


          • KIRBSTER269
            KIRBSTER269 commented
            Editing a comment
            Hey why don't you go to EDIT/Graphic Display Window/OpenGL in there you'll see Tessellation Multiplier Value: change that number to 0.01 hit OK twice. That will make your CAD model a little less square looking.

        • #6
          Originally posted by ncsteinb View Post
          DAN_M So, does this look about right?

          Code:
          FEAT_98_A =FEAT/CONTACT/CIRCLE/ADAPTIVE_CIRCLE_SCAN,CARTESIAN,OUT,LEAST_SQR
          THEO/<0,455.3,0>,<0,-1,0>,46.5,0
          ACTL/<0,455.3,0>,<0,-1,0>,46.5,0
          TARG/<0,455.3,0>,<0,-1,0>
          START ANG=270,END ANG=345
          ANGLE VEC=<0,0,-1>
          DIRECTION=CCW
          SHOW FEATURE PARAMETERS=NO
          SHOW CONTACT PARAMETERS=NO
          
          FEAT_98_B =FEAT/CONTACT/CIRCLE/ADAPTIVE_CIRCLE_SCAN,CARTESIAN,OUT,LEAST_SQR
          THEO/<0,455.3,0>,<0,-1,0>,46.5,0
          ACTL/<0,455.3,0>,<0,-1,0>,46.5,0
          TARG/<0,455.3,0>,<0,-1,0>
          START ANG=190,END ANG=270
          ANGLE VEC=<0,0,-1>
          DIRECTION=CCW
          SHOW FEATURE PARAMETERS=NO
          SHOW CONTACT PARAMETERS=NO
          
          FEAT_98_FEATSET=FEAT/SET,CARTESIAN
          THEO/<-16.471,456.8,-11.509>,<0,1,0>
          ACTL/<-16.471,456.8,-11.509>,<0,0,1>
          CONSTR/SET,BASIC,FEAT_98_A.HIT[1..FEAT_98_A.NUMHITS],FEAT_98_B.HIT[1..FEAT_98_B.NUMHITS],,
          
          FEAT_98 =FEAT/CIRCLE,CARTESIAN,OUT,LEAST_SQR,NO
          THEO/<0,456.8,0>,<0,1,0>,46.5
          ACTL/<0,456.8,0>,<0,1,0>,46.5
          CONSTR/CIRCLE,BF,2D,FEAT_98_FEATSET,,
          OUTLIER_REMOVAL/OFF,3
          FILTER/OFF,UPR=0
          Almost! But no. Lets take a closer look..

          I'm happy that FEAT_98 "looks correct" (XYZIJK is the same the the two input features & the dia is correct). Great job!

          I don't like that the featureset has different vectors as the input features. No bueno. Not exactly sure why that happened to you but it shouldn't have & needs to be addressed.

          1) Ensure you're OFFLINE

          2) Make sure you're using the correct workplane. If we're looking down at these arcs you should be in Z+ or Z- for the software to "see" the construction. This is especially important for circles because a circle is 2D.

          3) Fix the IJK of the feature set. Manually type over it. <0,-1,0> is what we wanna see.

          4) Hit Operation/Features/Reset Measured Values to Nominals/All to zero out your entire program (this code obv included in that) (pro tip...I have a custom toolbar with a lot of different buttons and this is one of them). This might take a minute because its literally going through your entire program, let the demon think.

          5) If things don't look zeroed out still, highlight the code & execute the block & all should clean up
          Last edited by DAN_M; 03-17-2021, 10:45 AM.
          SF7107(PCD), SF454(PCD), 152614(Quindos), 9159(Quindos), 7107(Quindos), B&S Manual, M&M Gear Checker

          Comment


          • #7
            Cool. I will repeat this with some other features I have to create, and then I'll try it out on the machine.

            Will report back today. Cheers!
            "Try not to be a dick"

            Comment


            • #8
              Originally posted by ncsteinb View Post
              Cool. I will repeat this with some other features I have to create, and then I'll try it out on the machine.

              Will report back today. Cheers!
              Goodluck!
              SF7107(PCD), SF454(PCD), 152614(Quindos), 9159(Quindos), 7107(Quindos), B&S Manual, M&M Gear Checker

              Comment


              • #9
                I use linear open scans quite often for measuring broken surface circles and will use often 2 or 3 scans to construct a circle. I have found that circle construction using this method works very well.

                Code:
                SCA1 =FEAT/SCAN,LINEAROPEN,SHOW HITS=NO,SHOWALLPARAMS=NO
                MEAS/SCAN
                BASICSCAN/LINE,SHOW HITS=NO,SHOWALLPARAMS=NO
                ENDSCAN
                ENDMEAS/
                SCA2 =FEAT/SCAN,LINEAROPEN,SHOW HITS=NO,SHOWALLPARAMS=NO
                MEAS/SCAN
                BASICSCAN/LINE,SHOW HITS=NO,SHOWALLPARAMS=NO
                ENDSCAN
                ENDMEAS/
                SCA3 =FEAT/SCAN,LINEAROPEN,SHOW HITS=NO,SHOWALLPARAMS=NO
                MEAS/SCAN
                BASICSCAN/LINE,SHOW HITS=NO,SHOWALLPARAMS=NO
                ENDSCAN
                ENDMEAS/
                CIR157_1 =FEAT/CIRCLE,CARTESIAN,IN,LEAST_SQR,NO
                THEO/<10,0,0>,<-1,0,0>,157.301
                ACTL/<10,0,0>,<-1,0,0>,157.301
                CONSTR/CIRCLE,BFRE,SCA1.HITS[1..12],SCA2.HITS[1..12],SCA3.HITS[1..12],,
                OUTLIER_REMOVAL/OFF,3
                FILTER/OFF,UPR=0
                Xcel & MicroVal Pfx & Global 37mr4 thru 2012mr1sp3
                Contura Calypso 5.4

                Lord, keep Your arm around my shoulder and Your hand over my mouth. Amen.

                Comment


                • #10
                  DAN_M Worked beautifully!

                  dwade I'm not a fan of the Linear Open scans, as I cannot easily adjust start and end point, or offsets. I just find the Adaptive Circle Scan to be much more user friendly for modifications/tweaks down the road. Unless there's a good reason I'm not aware of?
                  "Try not to be a dick"

                  Comment


                  • #11
                    Originally posted by ncsteinb View Post
                    DAN_M Worked beautifully!

                    dwade I'm not a fan of the Linear Open scans, as I cannot easily adjust start and end point, or offsets. I just find the Adaptive Circle Scan to be much more user friendly for modifications/tweaks down the road. Unless there's a good reason I'm not aware of?
                    Happy to help!
                    SF7107(PCD), SF454(PCD), 152614(Quindos), 9159(Quindos), 7107(Quindos), B&S Manual, M&M Gear Checker

                    Comment


                    • #12
                      Could not get it to work offline for an adaptive plane scan. I have rectangle face left after milling some other features and I combine them using patch scans. Tried it offline using the adaptive perimeter scan. It jeot saying the features were not defined previously or something like that, Ill get on the pc today and post again.
                      sigpicTAU ALPHA PI INDIANA DELTA CHAPTER
                      "Due to the highly confidential nature of my job, I am not allowed to know what I am doing" - author unknown

                      Comment


                      • #13
                        Originally posted by DAN_M View Post

                        Happy to help!

                        Just so you know, the reason PCD makes you do this: When constructing things together, PCD looks at the XYZ and IJK of each feature & uses those six inputs to compute the position/direction of the feature you're making. If two features you're construct together share a centroid, the software will be mad and not let you proceed because its a violation of one it's rules.
                        What we have done here is honored that rule and instead told PCD to use the "hits" instead of centroid, which it "understands" and allows us to do.
                        Now... If we could just get Hexagon to allow this option while constructing the features instead of hardcoding so we can save time and not run into the dreaded "Line Too Long error"...
                        Remembering my beautiful wife Taz who's life was lost on 6-13-2020. I love you and I miss you.

                        Comment


                        • #14
                          Originally posted by A-machine-insp View Post

                          Now... If we could just get Hexagon to allow this option while constructing the features instead of hardcoding so we can save time and not run into the dreaded "Line Too Long error"...
                          I suggested it on Idea Center, has like 15+ likes thanks to you guys! Hopefully Hex sees it and incorporates it into a future release.
                          SF7107(PCD), SF454(PCD), 152614(Quindos), 9159(Quindos), 7107(Quindos), B&S Manual, M&M Gear Checker

                          Comment


                          • #15
                            Originally posted by DAN_M View Post

                            I suggested it on Idea Center, has like 15+ likes thanks to you guys! Hopefully Hex sees it and incorporates it into a future release.
                            I am one of those votes.
                            Remembering my beautiful wife Taz who's life was lost on 6-13-2020. I love you and I miss you.

                            Comment

                            Related Topics

                            Collapse

                            Working...
                            X