Min/Max Capability?

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

  • Min/Max Capability?

    Hi there! We have a callout that we're trying to figure out how to make happen in PC-DMIS. They are asking for 12 points along a plane and want the highest and the lowest of the 12 points reported, relative to Z. Sounds simple enough, BUT is there any way to create a dimension in such a way as to report ONLY the highest and lowest points? Thank you in advance for your help!

  • #2
    Have you tried F10 and marking the MinMax box?
    sigpic
    Originally posted by AndersI
    I've got one from September 2006 (bug ticket) which has finally been fixed in 2013.

    Comment


    • #3
      We did, but with the reporting system that we use, that's just not going to work. We export a .CSV for reporting purposes. Just wondering if there is an option in the feature itself, that might work? Like if you were to make a plane out of those 12 points, is there a feature that might look at all of the points in that plane and be able to output a min and a max?

      Comment


      • #4
        it will take coding, use an array, then have code pick the highest and lowest point. check the CODE section here.
        sigpic
        Originally posted by AndersI
        I've got one from September 2006 (bug ticket) which has finally been fixed in 2013.

        Comment


        • #5
          Thank you, Matthew! That's kind of what I was thinking.

          Comment


          • #6
            You can do something like this. Credit goes to JEFMAN

            Code:
            ASSIGN/V5=MAXINDEX(PLN_BURR.HIT[1..PLN_BURR.NUMHITS].Z)
                        ASSIGN/V6=PLN_BURR.HIT[V5].XYZ
            BURR_PNT_MAX=GENERIC/POINT,DEPENDENT,CARTESIAN,$
                        NOM/XYZ,<0+0,0+0,0+0>,$
                        MEAS/XYZ,<V6.X,V6.Y,V6.Z>,$
                        NOM/IJK,<0+0,0+0,1+0>,$
                        MEAS/IJK,<0+0,0+0,1+0>
                        FORMAT/TEXT,OPTIONS, ,HEADINGS,SYMBOLS, ;MEAS, , , , , ,
            DIM BURR_MAX= LOCATION OF POINT BURR_PNT_MAX  UNITS=MM ,$
            GRAPH=OFF  TEXT=OFF  MULT=50.00  OUTPUT=BOTH  HALF ANGLE=NO
            AX       MEAS
            X       15.297 ----#---
            Y       36.948 ----#---
            Z        0.051 ----#---
            PR      39.989 ----#---
            PA      67.509 ----#---
            END OF DIMENSION BURR_MAX
                        ASSIGN/V8=MININDEX(PLN_BURR.HIT[1..PLN_BURR.NUMHITS].Z)
                        ASSIGN/V9=PLN_BURR.HIT[V8].XYZ
            BURR_PNT_MIN=GENERIC/POINT,DEPENDENT,CARTESIAN,$
                        NOM/XYZ,<0+0,0+0,0+0>,$
                        MEAS/XYZ,<V9.X,V9.Y,V9.Z>,$
                        NOM/IJK,<0+0,0+0,1+0>,$
                        MEAS/IJK,<0+0,0+0,1+0>
            DIM BURR_MIN= LOCATION OF POINT BURR_PNT_MIN  UNITS=MM ,$
            GRAPH=OFF  TEXT=OFF  MULT=50.00  OUTPUT=BOTH  HALF ANGLE=NO
            AX       MEAS
            X       39.650 ----#---
            Y       -5.227 ---#----
            Z       -0.048 ---#----
            PR      39.993 ----#---
            PA      -7.509 ---#----
            END OF DIMENSION BURR_MIN
            Then report out your Z measurements into your CSV. Optional: You can report out the location of the max and min points as well!
            Last edited by bfire85; 07-25-2019, 03:43 PM.
            Whatever a man sows, he shall reap.

            Comment


            • #7
              Similar to above, but an alternative if you only care about what the z values are, not necessarily where they are is:


              Code:
              PLN1       =FEAT/CONTACT/PLANE/DEFAULT,CARTESIAN,OUTLINE,LEAST_SQR
                          THEO/<0,0,30>,<0,0,1>
                          ACTL/<0,0,30>,<0,0,1>
                          TARG/<0,0,30>,<0,0,1>
                          ANGLE VEC=<0.7071068,-0.7071068,0>,RADIAL
                          SHOW FEATURE PARAMETERS=NO
                          SHOW CONTACT PARAMETERS=YES
                            NUMHITS=12,NUMRINGS=3
                            SPACER=0
                            AVOIDANCE MOVE=NO,DISTANCE=10
                          SHOW HITS=NO
                          ASSIGN/ZVALS=PLN1.HIT[1..PLN1.NUMHITS].Z
                          ASSIGN/ZMAX=MAXINDEX(ZVALS)
                          ASSIGN/ZMIN=MININDEX(ZVALS)
              DIM DIM_1= LOCATION OF POINT PLN1.HIT[ZMIN]  UNITS=MM ,$
              GRAPH=OFF  TEXT=OFF  MULT=10.00  OUTPUT=BOTH  HALF ANGLE=NO
              AX       MEAS    NOMINAL       +TOL       -TOL        DEV     OUTTOL
              Z       30.000     30.000      0.010      0.010      0.000      0.000 ----#----
              END OF DIMENSION DIM_1
              DIM DIM_2= LOCATION OF POINT PLN1.HIT[ZMAX]  UNITS=MM ,$
              GRAPH=OFF  TEXT=OFF  MULT=10.00  OUTPUT=BOTH  HALF ANGLE=NO
              AX       MEAS    NOMINAL       +TOL       -TOL        DEV     OUTTOL
              Z       30.000     30.000      0.010      0.010      0.000      0.000 ----#----
              END OF DIMENSION DIM_2
              Or you could add the X and Y (with huge tolerances) to the report. This saves you from creating generic points.

              Comment


              • A-machine-insp
                A-machine-insp commented
                Editing a comment
                Could you do what you said except use a constructed scan set from the required points the OP needs to measure?

                I could see this as being helpful to me on certain parts but using a constructed scan set instead of an auto plane.

              • louisd
                louisd commented
                Editing a comment
                use sortup array for the scan set's z value, then use another assign to extract the first index, and report the value. do the same for the last array index and report the value

            • #8
              ASSIGN/ZMAX=SCN1.HIT[MAXINDEX(SCN1.HIT[1..SCN1.NUMHITS].Z)].XYZ should give directly the coordinates of the hit.
              Happy week-end, all !

              Comment

              Related Topics

              Collapse

              Working...
              X