Variable Auto Features not updating

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

  • Variable Auto Features not updating

    I have a part family that I am creating a variable program for, and am running into issues with the values not updating in the auto features. I've assigned variables at the top of the program, and then use those variables in Auto Circles. The problem I have is that when I type in a new value for the variable, the hits in the auto features don't update. Example. I assign ID=1, and then set the diameter on my auto circle to "ID". The first time through it runs fine for that part. Then when I change it to ID=2, and rerun the program, it tries to measure a 1" ID still. Is there a setting to force the hits to be updated every time a program is ran? I did this same thing 10-15 years ago and have programs that have been running flawlessly ever since, but can't seem to get it to work now.
    2 Brown & Sharpe ONE CMM's
    2 454 SF CMM's
    Brown & Sharpe MicroXcel Pfx
    Brown & Sharpe Profile 50
    PC-Dmis vs 2012

  • #2
    Are you executing the program from the beginning or just from the feature itself?
    Whatever a man sows, he shall reap.

    Comment


    • #3
      Executing from the top of the program.
      2 Brown & Sharpe ONE CMM's
      2 454 SF CMM's
      Brown & Sharpe MicroXcel Pfx
      Brown & Sharpe Profile 50
      PC-Dmis vs 2012

      Comment


      • #4
        Where are you inserting the variable names at:
        Code:
        CIR1       =FEAT/CONTACT/CIRCLE/DEFAULT,CARTESIAN,OUT,LEAST_SQR
                    THEO/<v1.x,v1.y,v1.z>,<v1.i,v1.j,v1.k>,v1.d,0 [COLOR=#FF0000]<< here?[/COLOR]
                    ACTL/<1,2,3>,<0,0,1>,1,0
                    TARG/<v1.x,v1.y,v1.z>,<v1.i,v1.j,v1.k>  [COLOR=#FF0000]<< and here?[/COLOR]
                    START ANG=0,END ANG=360
                    ANGLE VEC=<1,0,0>
                    DIRECTION=CCW
                    SHOW FEATURE PARAMETERS=NO
                    SHOW CONTACT PARAMETERS=YES
                      NUMHITS=4,DEPTH=-0.1,PITCH=0
                      SAMPLE METHOD=SAMPLE_HITS
                      SAMPLE HITS=0,SPACER=0.1
                      AVOIDANCE MOVE=NO,DISTANCE=0.2
                      FIND HOLE=NOCENTER,ONERROR=NO,READ POS=NO
                    SHOW HITS=NO
        Last edited by Kp61dude!; 06-13-2019, 02:01 PM.
        PcDmis 2015.1 SP10 CAD++
        Global 7-10-7 DC800S

        Comment


        • #5
          Correct, we are placing the variable names in the places shown.
          2 Brown & Sharpe ONE CMM's
          2 454 SF CMM's
          Brown & Sharpe MicroXcel Pfx
          Brown & Sharpe Profile 50
          PC-Dmis vs 2012

          Comment


          • #6
            What is loading those variables and where? It's probably best if you posted your code or pieces/snipets of concern to better help you.
            PcDmis 2015.1 SP10 CAD++
            Global 7-10-7 DC800S

            Comment


            • #7
              I just tried it on a simple routine, using 2012MR1, and it works fine offline.

              v5 at 1.875
              Code:
                     ASSIGN/V5=1.875
              CIR2       =FEAT/CONTACT/CIRCLE/DEFAULT,CARTESIAN,IN,LEAST_SQR
                          THEO/<0,0,0.005>,<0,0,-1>,V5
                          ACTL/<0,0,0.005>,<0,0,-1>,1.875
                          TARG/<0,0,0.005>,<0,0,-1>
                          START ANG=0,END ANG=360
                          ANGLE VEC=<0,1,0>
                          DIRECTION=CCW
                          SHOW FEATURE PARAMETERS=NO
                          SHOW CONTACT PARAMETERS=YES
                            NUMHITS=5,DEPTH=0,PITCH=0
                            SAMPLE HITS=0,SPACER=0
                            AVOIDANCE MOVE=NO,DISTANCE=0
                            FIND HOLE=DISABLED,ONERROR=NO,READ POS=NO
                          SHOW HITS=YES
                            HIT/BASIC,<0,0.9375,0.005>,<0,-1,0>,<0,0.9375,0.005>
                            HIT/BASIC,<0.89162,0.2897,0.005>,<-0.9510565,-0.309017,0>,<0.89162,0.2897,0.005>
                            HIT/BASIC,<0.55105,-0.75845,0.005>,<-0.5877853,0.809017,0>,<0.55105,-0.75845,0.005>
                            HIT/BASIC,<-0.55105,-0.75845,0.005>,<0.5877853,0.809017,0>,<-0.55105,-0.75845,0.005>
                            HIT/BASIC,<-0.89162,0.2897,0.005>,<0.9510565,-0.309017,0>,<-0.89162,0.2897,0.005>
                          ENDMEAS/
              V5 at 0.875
              Code:
                 ASSIGN/V5=0.875
              CIR2       =FEAT/CONTACT/CIRCLE/DEFAULT,CARTESIAN,IN,LEAST_SQR
                          THEO/<0,0,0.005>,<0,0,-1>,V5
                          ACTL/<0,0,0.005>,<0,0,-1>,0.875
                          TARG/<0,0,0.005>,<0,0,-1>
                          START ANG=0,END ANG=360
                          ANGLE VEC=<0,1,0>
                          DIRECTION=CCW
                          SHOW FEATURE PARAMETERS=NO
                          SHOW CONTACT PARAMETERS=YES
                            NUMHITS=5,DEPTH=0,PITCH=0
                            SAMPLE HITS=0,SPACER=0
                            AVOIDANCE MOVE=NO,DISTANCE=0
                            FIND HOLE=DISABLED,ONERROR=NO,READ POS=NO
                          SHOW HITS=YES
                            HIT/BASIC,<0,0.4375,0.005>,<0,-1,0>,<0,0.4375,0.005>
                            HIT/BASIC,<0.41609,0.13519,0.005>,<-0.9510565,-0.309017,0>,<0.41609,0.13519,0.005>
                            HIT/BASIC,<0.25716,-0.35394,0.005>,<-0.5877853,0.809017,0>,<0.25716,-0.35394,0.005>
                            HIT/BASIC,<-0.25716,-0.35394,0.005>,<0.5877853,0.809017,0>,<-0.25716,-0.35394,0.005>
                            HIT/BASIC,<-0.41609,0.13519,0.005>,<0.9510565,-0.309017,0>,<-0.41609,0.13519,0.005>
                          ENDMEAS/
              Are you sure your assignment is functioning? you can test it with a report or operator comment and put something like "Assignment result = " + V5 in the comment. it will populate with the actual assignment value.

              Is it a comment and not an assignment? if it's an input comment, you need to use ".input" at the end of the comment name (generally starts with C1) so C1.Input would produce the value for C1.

              Comment


              • #8
                Here is the code for variable assignment:
                Code:
                ASSIGN/V10=1.44
                            ASSIGN/V11=0
                            ASSIGN/V15=4.205
                            ASSIGN/V20=5.04
                            ASSIGN/V30=4.6685
                            ASSIGN/V50=4.47
                            ASSIGN/V60=.4355
                            ASSIGN/V70=.692
                            ASSIGN/V80=.145
                            ASSIGN/V90=.05
                            ASSIGN/V100=20
                And here is an auto feature using that code:
                Code:
                ID         =FEAT/CONTACT/CIRCLE/DEFAULT,CARTESIAN,IN,LEAST_SQR
                            THEO/<V11,V11,V11>,<0,0,1>,V15
                            ACTL/<0,0,0>,<0,0,1>,4.205
                            TARG/<V11,V11,V11>,<0,0,1>
                            START ANG=0,END ANG=360
                            ANGLE VEC=<1,0,0>
                            DIRECTION=CCW
                            SHOW FEATURE PARAMETERS=YES
                              VOID DETECTION=NO
                              REMEASURE=NO
                              SURFACE=THEO_THICKNESS,0
                              MEASURE MODE=NOMINALS
                              RMEAS=NONE,NONE,NONE
                              CIRCULAR MOVES=CIRCULAR
                              GRAPHICAL ANALYSIS=NO
                              FEATURE LOCATOR=NO,NO,""
                            SHOW CONTACT PARAMETERS=YES
                              NUMHITS=4,DEPTH=0.125,PITCH=0
                              SAMPLE METHOD=SAMPLE_HITS
                              SAMPLE HITS=0,SPACER=0
                              AVOIDANCE MOVE=NO,DISTANCE=0
                              FIND HOLE=DISABLED,ONERROR=NO,READ POS=NO
                            SHOW HITS=YES
                              HIT/BASIC,<2.1025,0.003,-0.125>,<-0.999999,-0.0014443,0>,<2.1025,0.003,-0.125>
                              HIT/BASIC,<-0.003,2.1025,-0.125>,<0.0014443,-0.999999,0>,<-0.003,2.1025,-0.125>
                              HIT/BASIC,<-2.1025,-0.003,-0.125>,<0.999999,0.0014443,0>,<-2.1025,-0.003,-0.125>
                              HIT/BASIC,<0.003,-2.1025,-0.125>,<-0.0014443,0.999999,0>,<0.003,-2.1025,-0.125>
                            ENDMEAS/
                2 Brown & Sharpe ONE CMM's
                2 454 SF CMM's
                Brown & Sharpe MicroXcel Pfx
                Brown & Sharpe Profile 50
                PC-Dmis vs 2012

                Comment


                • #9
                  Just my two cents should it be v1.tx, v1.ty, v1.tz and etc. or does that matter. Theos.
                  sigpic

                  Comment


                  • #10
                    The variable are all assignments, and are not passed in from a comment. When I hover over the variable in the auto feature, it returns the correct value, it just doesn't go to the correct points. If I edit something such as the number of hits in the auto feature, it then recalculates the hits, and everything works fine. But I have to force a recalculation of the hits after changing the variable value, otherwise it will just run at whatever the original value was.
                    2 Brown & Sharpe ONE CMM's
                    2 454 SF CMM's
                    Brown & Sharpe MicroXcel Pfx
                    Brown & Sharpe Profile 50
                    PC-Dmis vs 2012

                    Comment


                    • #11
                      What they mean is that the variables for the assignments should be entered by a input comment at the beginning of the program. Comment asks whey part are you going to run? and depending on what is entered, it fills in the assignments for your variables instead editing the program for every part change.

                      Comment


                      • #12
                        why would your theoretical need to be V11? if V11 equals zero, then your at 0,0,0.

                        Comment


                        • #13
                          It doesn't have to be, this was just done to try and help resolve an issue with positions not being correct.
                          2 Brown & Sharpe ONE CMM's
                          2 454 SF CMM's
                          Brown & Sharpe MicroXcel Pfx
                          Brown & Sharpe Profile 50
                          PC-Dmis vs 2012

                          Comment


                          • #14
                            Originally posted by metalquest1 View Post
                            Here is the code for variable assignment:
                            Code:
                            ASSIGN/V10=1.44
                            ASSIGN/V11=0
                            ASSIGN/V15=4.205
                            ASSIGN/V20=5.04
                            ASSIGN/V30=4.6685
                            ASSIGN/V50=4.47
                            ASSIGN/V60=.4355
                            ASSIGN/V70=.692
                            ASSIGN/V80=.145
                            ASSIGN/V90=.05
                            ASSIGN/V100=20
                            And here is an auto feature using that code:
                            Code:
                            ID =FEAT/CONTACT/CIRCLE/DEFAULT,CARTESIAN,IN,LEAST_SQR
                            THEO/<V11,V11,V11>,<0,0,1>,V15
                            ACTL/<0,0,0>,<0,0,1>,4.205
                            TARG/<V11,V11,V11>,<0,0,1>
                            START ANG=0,END ANG=360
                            ANGLE VEC=<1,0,0>
                            DIRECTION=CCW
                            SHOW FEATURE PARAMETERS=YES
                            VOID DETECTION=NO
                            REMEASURE=NO
                            SURFACE=THEO_THICKNESS,0
                            MEASURE MODE=NOMINALS
                            RMEAS=NONE,NONE,NONE
                            CIRCULAR MOVES=CIRCULAR
                            GRAPHICAL ANALYSIS=NO
                            FEATURE LOCATOR=NO,NO,""
                            SHOW CONTACT PARAMETERS=YES
                            NUMHITS=4,DEPTH=0.125,PITCH=0
                            SAMPLE METHOD=SAMPLE_HITS
                            SAMPLE HITS=0,SPACER=0
                            AVOIDANCE MOVE=NO,DISTANCE=0
                            FIND HOLE=DISABLED,ONERROR=NO,READ POS=NO
                            SHOW HITS=YES
                            HIT/BASIC,<2.1025,0.003,-0.125>,<-0.999999,-0.0014443,0>,<2.1025,0.003,-0.125>
                            HIT/BASIC,<-0.003,2.1025,-0.125>,<0.0014443,-0.999999,0>,<-0.003,2.1025,-0.125>
                            HIT/BASIC,<-2.1025,-0.003,-0.125>,<0.999999,0.0014443,0>,<-2.1025,-0.003,-0.125>
                            HIT/BASIC,<0.003,-2.1025,-0.125>,<-0.0014443,0.999999,0>,<0.003,-2.1025,-0.125>
                            ENDMEAS/

                            Yep that should work.

                            Try this:

                            Code:
                                        ASSIGN/V1=54
                                        COMMENT/OPER,NO,FULL SCREEN=NO,AUTO-CONTINUE=NO,
                                        "This is the value of V1: " + V1
                            PcDmis 2015.1 SP10 CAD++
                            Global 7-10-7 DC800S

                            Comment


                            • #15
                              so either your feature is glitching out some way, or you have something else in your code, contributing to the issue that we haven't seen... loops? goto label jumps? are all 6 degrees of freedom controlled via alignment and in correct order (Level/Rotate/Origin)? current workplane is in Z Axis?

                              Comment

                              Related Topics

                              Collapse

                              Working...
                              X