profile of a bell shape?

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

  • profile of a bell shape?

    So I have a part it looks like a 1/4 th of a bell.I need to do a profile of the outside14bell.PNG
    Is it possible using the PH10M head to do a profile of complex shape like a bell all at once? Or do I have to break it down into sections of recognized shapes, Like create a torus ,cone , cylinder, and planes. Then do a profile for each feature?

  • #2
    Post the print . Without seeing it, I would take as many single vector points as you feel are needed. Create a SET from all those points and dimension that. Using different features in a set doesnt give you the individual hit point data of those features.

    Comment


    • DAN_M
      DAN_M commented
      Editing a comment
      unless he captured the features into a set and then hardcoded the set to pull the ".numhits" values of the individual features

    • Schlag
      Schlag commented
      Editing a comment
      Can you do that to multiple feature in 1 set ? I suppose..... I only do 1 feature per set for simplicity and then I would add those sets together.

    • DAN_M
      DAN_M commented
      Editing a comment
      yup, you can add sets together & get really advanced with it. i have some ridiculously big ones. standby for some annoying code lol

      my best advise I could give is to keep your naming convention consistent or you'll get horribly lost in all of the code
      Last edited by DAN_M; 01-13-2021, 11:50 AM.

  • #3
    Yeah as Schlag said. You will want to create points all over your complex surface and then create a set out of the points. You can then create a profile from your set.

    Comment


    • #4
      Even with a TTP probe like TP20, you can do scans. It will just take longer than a scanning head. You can try playing with patch scans or UV scans with the CAD model. Otherwise, as mentioned, do vector points constructed into a feature set.
      PC-DMIS 2016.0 SP8

      Jeff

      Comment


      • #5
        Not to hijack this thread but I have a question. Why do you construct a feature set from the points to output profile?
        I have always only used the individual points in the output.
        Time for the Trolls to leave.

        Comment


        • Schlag
          Schlag commented
          Editing a comment
          Sometimes the number of features or hits would dictate how you would handle that I guess.

      • #6
        Originally posted by William Johnson View Post
        Not to hijack this thread but I have a question. Why do you construct a feature set from the points to output profile?
        I have always only used the individual points in the output.
        It makes the output smaller. If you have specific gage points you want to keep track of separately, then individual points is the way to go.
        PC-DMIS 2016.0 SP8

        Jeff

        Comment


        • #7
          Schlag

          I don't have scanning.

          This is what we call "ghetto-scanning".

          The annoying thing about this method of programming (aside from how long it is) is that you run into line-length-error BS from the software so you have to split it all up like this in order to get it to work. If Hexagon eliminated the max line length requirement for feature sets we'd be in business!

          Code:
          GRP_FEATURES_OUTSIDEPROFILE_ABC=GROUP/SHOWALLPARAMS=NO
          ENDGROUP/ID=GRP_FEATURES_OUTSIDEPROFILE_ABC
          FEATSET_Z_1=FEAT/SET,CARTESIAN
          THEO/<3.68649,-1.79571,0.08>,<0,0,1>
          ACTL/<3.68644,-1.79609,0.07997>,<0,0,1>
          CONSTR/SET,BASIC,Z1.HIT[1..Z1.NUMHITS],Z2.HIT[1..Z2.NUMHITS],Z3.HIT[1..Z3.NUMHITS],Z4.HIT[1..Z4.NUMHITS],Z5.HIT[1..Z5.NUMHITS],Z6.HIT[1..Z6.NUMHITS],Z7.HIT[1..Z7.NUMHITS],Z8.HIT[1..Z8.NUMHITS],Z9.HIT[1..Z9.NUMHITS],,
          FEATSET_Z_2=FEAT/SET,CARTESIAN
          THEO/<10.26361,-0.76696,0.111>,<0,0,1>
          ACTL/<10.26361,-0.76718,0.11098>,<0,0,1>
          CONSTR/SET,BASIC,Z10.HIT[1..Z10.NUMHITS],Z11.HIT[1..Z11.NUMHITS],Z12.HIT[1..Z12.NUMHITS],Z13.HIT[1..Z13.NUMHITS],Z14.HIT[1..Z14.NUMHITS],Z15.HIT[1..Z15.NUMHITS],Z16.HIT[1..Z16.NUMHITS],Z17.HIT[1..Z17.NUMHITS],,
          FEATSET_Z_3=FEAT/SET,CARTESIAN
          THEO/<12.2863,3.22605,0.08>,<0,0,1>
          ACTL/<12.28685,3.2262,0.07998>,<0,0,1>
          CONSTR/SET,BASIC,Z18.HIT[1..Z18.NUMHITS],Z19.HIT[1..Z19.NUMHITS],Z20.HIT[1..Z20.NUMHITS],Z21.HIT[1..Z21.NUMHITS],Z22.HIT[1..Z22.NUMHITS],Z23.HIT[1..Z23.NUMHITS],Z24.HIT[1..Z24.NUMHITS],Z25.HIT[1..Z25.NUMHITS],,
          FEATSET_Z_4=FEAT/SET,CARTESIAN
          THEO/<10.12619,7.14821,0.08>,<0,0,1>
          ACTL/<10.1268,7.14878,0.08>,<0,0,1>
          CONSTR/SET,BASIC,Z26.HIT[1..Z26.NUMHITS],Z27.HIT[1..Z27.NUMHITS],Z28.HIT[1..Z28.NUMHITS],Z29.HIT[1..Z29.NUMHITS],Z30.HIT[1..Z30.NUMHITS],Z31.HIT[1..Z31.NUMHITS],Z32.HIT[1..Z32.NUMHITS],Z33.HIT[1..Z33.NUMHITS],,
          FEATSET_Z_5=FEAT/SET,CARTESIAN
          THEO/<6.47691,7.55462,0.08>,<0,0,1>
          ACTL/<6.47665,7.55483,0.08>,<0,0,1>
          CONSTR/SET,BASIC,Z34.HIT[1..Z34.NUMHITS],Z35.HIT[1..Z35.NUMHITS],Z36.HIT[1..Z36.NUMHITS],Z37.HIT[1..Z37.NUMHITS],Z38.HIT[1..Z38.NUMHITS],Z39.HIT[1..Z39.NUMHITS],Z40.HIT[1..Z40.NUMHITS],Z41.HIT[1..Z41.NUMHITS],,
          FEATSET_Z_6=FEAT/SET,CARTESIAN
          THEO/<1.20596,6.49097,0.08>,<0,0,1>
          ACTL/<1.20582,6.49084,0.08>,<0,0,1>
          CONSTR/SET,BASIC,Z42.HIT[1..Z42.NUMHITS],Z43.HIT[1..Z43.NUMHITS],Z44.HIT[1..Z44.NUMHITS],Z45.HIT[1..Z45.NUMHITS],Z46.HIT[1..Z46.NUMHITS],Z47.HIT[1..Z47.NUMHITS],Z48.HIT[1..Z48.NUMHITS],Z49.HIT[1..Z49.NUMHITS],,
          FEATSET_Z_7=FEAT/SET,CARTESIAN
          THEO/<-3.49075,1.55208,0.08>,<0,0,1>
          ACTL/<-3.49069,1.55166,0.07998>,<0,0,1>
          CONSTR/SET,BASIC,Z50.HIT[1..8],Z51.HIT[1..7],Z52.HIT[1..7,Z53.HIT[1..4],Z54.HIT[1..4],Z55.HIT[1..5],Z56.HIT[1..6],Z57.HIT[1..7],Z58.HIT[1..8],Z59.HIT[1..11],,
          SCN_238_SUB1=FEAT/SET,CARTESIAN
          THEO/<8.74692,1.73416,0.08795>,<0,0,1>
          ACTL/<8.74717,1.73416,0.08793>,<0,0,1>
          CONSTR/SET,BASIC,FEATSET_Z_1.HIT[1..FEATSET_Z_1.NUMHITS],FEATSET_Z_2.HIT[1..FEATSET_Z_2.NUMHITS],FEATSET_Z_3.HIT[1..FEATSET_Z_3.NUMHITS],FEATSET_Z_4.HIT[1..FEATSET_Z_4.NUMHITS],,
          SCN_238_SUB2=FEAT/SET,CARTESIAN
          THEO/<0.80429,4.77597,0.08>,<0,0,1>
          ACTL/<0.8042,4.77582,0.07999>,<0,0,1>
          CONSTR/SET,BASIC,FEATSET_Z_5.HIT[1..FEATSET_Z_5.NUMHITS],FEATSET_Z_6.HIT[1..FEATSET_Z_6.NUMHITS],FEATSET_Z_7.HIT[1..FEATSET_Z_7.NUMHITS],,
          SCN_238 =FEAT/SET,CARTESIAN
          THEO/<4.86675,3.22016,0.08407>,<0,0,1>
          ACTL/<4.86684,3.22009,0.08405>,<0,0,1>
          CONSTR/SET,BASIC,SCN_238_SUB1.HIT[1..SCN_238_SUB1.NUMHITS],SCN_238_SUB2.HIT[1..SCN_238_SUB2.NUMHITS],,
          FORMFEED/
          DIM IMS_238= PROFILE OF SURFACE OF SET SCN_238 FORMANDLOCATION UNITS=IN ,$
          GRAPH=OFF TEXT=OFF MULT=30.00 ARROWDENSITY=100 OUTPUT=BOTH
          AX MEAS NOMINAL +TOL -TOL DEV OUTTOL
          M 0.00774 0.00000 0.00984 0.00984 0.00774 0.00000 ---#|--#-
          ANALYSISVIEW/IMS_238,,
          Last edited by DAN_M; 01-13-2021, 11:53 AM.
          Beep beep beep..

          Comment


          • DAN_M
            DAN_M commented
            Editing a comment
            Nope!

            My current company uses all TP20/TESASTAR_MP stuff and is running PC DMIS CAD (not "CAD ++").

            I have had CAD++ w/ scanning at previous companies but I am not so lucky here.

          • DeWain Hodge
            DeWain Hodge commented
            Editing a comment
            Try working with PC-DMIS PRO after working with CAD & CAD ++ for years.

          • DAN_M
            DAN_M commented
            Editing a comment
            DeWain Hodge that must have been rough! I've been trying like h3ll to get my company to upgrade but its like trying to squeeze grapejuice out of a rock with these people

        Related Topics

        Collapse

        Working...
        X