Using variables in move points

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

  • Using variables in move points

    Has anyone ever tried this? V3.2063, Mistral 7-7-5.
    I have parts that I need numerous move points that I have to type in. They use similar moves. I wanted to use variables, but it didn't seem to work. Any ideas?

    Ex.

    ASSIGN/V1=1
    ASSIGN/V2=2
    ASSIGN/V3=3
    MOVE/POINT,V1,-V2,-V3
    When in doubt, post code. A second set of eyes might see something you missed.
    sigpic

  • #2
    I can't say it works but try this:

    Code:
    MOVE/POINT,V1,-1 * V2,-1 * V3
    <internet bumper sticker goes here>

    Comment


    • #3
      Would INCREMENT move work for you? They are based ONLY on the current location of the head, not an absolute location related to your alignment.
      sigpic
      Originally posted by AndersI
      I've got one from September 2006 (bug ticket) which has finally been fixed in 2013.

      Comment


      • #4
        It doesn't even recognize all positive variables

        MOVE/POINT,V1,V2,V3

        Is seen as 0,0,0

        Oh well.
        When in doubt, post code. A second set of eyes might see something you missed.
        sigpic

        Comment


        • #5
          This works for me:

          Code:
                      ASSIGN/V20 = 1
                      ASSIGN/V21 = 20
                      ASSIGN/V22 = 3
                      MOVE/POINT,NORMAL,V20,-V21,V22

          Jan.
          ***************************
          PC-DMIS/NC 2010MR3; 15 December 2010; running on 18 machine tools.
          Romer Infinite; PC-DMIS 2010 MR3; 15 December 2010.

          Comment


          • #6
            Increment would work. I was just trying to eliminate some typing and remembering of the positions. Thought it'd be cool to use. In the long term I wanted to create a program for 10 different diameter parts. Other dimensions are the same. I was thinking of creating a variable table. Then the operator would be prompted for the part #. the variables would be based on the part #. Someday I'll have time to figure that code out.
            When in doubt, post code. A second set of eyes might see something you missed.
            sigpic

            Comment


            • #7
              Copy paste
              <internet bumper sticker goes here>

              Comment


              • #8
                Interesting, When I place the cursor in the movepoint variable, it sees the variable number. But when I execute, it goes to 0,0,0.....
                When in doubt, post code. A second set of eyes might see something you missed.
                sigpic

                Comment


                • #9
                  Originally posted by craiger_ny View Post
                  Copy paste
                  That is how I usually do it. Just toying with other ideas.
                  When in doubt, post code. A second set of eyes might see something you missed.
                  sigpic

                  Comment


                  • #10
                    I Got It!!!!

                    DUH, I was adding the variables before the feature and executing from the feature. NOT EXECUTING THE VARIABLE.
                    Cool, this will cut some programming time out.

                    Must've been the lack of beer drinking this weekend.......

                    Thanks for the help guys!
                    Last edited by John Kingston; 12-18-2006, 09:31 AM.
                    When in doubt, post code. A second set of eyes might see something you missed.
                    sigpic

                    Comment

                    Related Topics

                    Collapse

                    Working...
                    X