how to increase speed?

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

  • how to increase speed?

    Hi All
    I use PC-DMIS CAD++ 2019 R1 on B&S 5.7.5, its absolute speed is 700 (this is what I see when I open F5 ). Most of our programs run with speed 200-300mm/s. I changed it to 500 in program edit window but didn't see any difference.
    I searched forum and found information that I can change speed in machine interface setup, so I did, under "Params" tab I changed x,y,z max speed to 500. But I couldn't run any program. Right after I start it gives me execution error "move absolute to...." no even error#. Is this speed limited somewhere else?
    Please help
    Thanks,
    Ewa
    Last edited by ewadora; 10-29-2019, 03:18 PM.

  • #2
    please be careful when changing your speeds on your machine.

    you could risk false triggers and significant damage in the event of a crash.

    Go to Edit > Preferences > Machine Interface Setup > Motion (Tab) - Here you will find a max speed setting.
    Ex-Hex

    Comment


    • #3
      Originally posted by ewadora View Post
      I searched forum and found information that I can change speed in machine interface setup, so I did, under "Params" tab I changed x,y,z max speed to 500. But I couldn't run any program.
      This is the acceleration parameters. That value should be significantly higher than 500, but this isn't going to speed up your routine by much at all. here's a link related to accel parameters https://www.pcdmisforum.com/forum/pc...ion-parameters

      Comment


      • #4
        also, per anthony.alfaro 's post above, there's an option checkbox to use absolute speeds, rather than the default % of the CMM's hard-coded MAX speed (hard-limited by the device controller firmware).
        Some people prefer the % of max default, it works best if you are using multiple CMM's with varying speeds, to measure the same product.
        Otherwise, the absolute speeds would be ideal if you only have 1 CMM or don't share routines between CMM's.

        -When you select use ABSOLUTE speeds, that value is limited by the value that the controller forces. if you set it to 1000 and your CMM's linear max speed is 500, it will only run at 500, regardless of the higher value. If you set it to 400, it will run at 80% of max (400/500=0.8).

        -When you deselect use ABSOLUTE speeds, the max value you can input is 100, which is now a percentage of the hard-coded max speed.

        Comment


        • #5
          additionally, within each routine, you can define MOVESPEED and TOUCHSPEED, which are values also relative to that "use ABSOLUTE speeds" checkbox (100=max value if you are using %of max).

          Touchspeed is a whole different monster, do not change your touchspeed unless you know what you are doing, or are assessing/learning what affect it has on your equipment and measurement accuracy. You should calibrate all your probes at the same touchspeed as you are using to measure the product. Some people have done studies and found that for their application a touchpseed of 6mm/sec is safe and fastest for TP200's, but it is completely dependent upon your sensor, and the accuracy you expect to receive from said sensor. Default with PCDMIS is 2mm/sec.

          Comment


          • #6
            Depending on the controller you have, there's a button or dial that controls the speed as well...

            Comment


            • #7
              Lesson learned in ABSOLUTE vs. PERCENT, if you share programs you will see a better correlation between CMMs if you use ABSOLUTE for TOUCHSPEED. Another thing to think about when trying to increase your speeds is that unless there is ample distance between move points you may not see much of an increase because of acceleration and deceleration limits of the controller. When I'm sending the probe to and from the rack for changes I'm usually maxing out the MOVESPEED of the controller
              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


              • anthony.alfaro
                anthony.alfaro commented
                Editing a comment
                Bingo.

                If you run the same programs on multiple machines, its always better to run them in absolute rather than percent or relative.

              • louisd
                louisd commented
                Editing a comment
                Unless you need higher throughput over extreme precision. Almost all of my product has the tightest tolerance range ~0.007", and we can barely keep up even though we are 24/7 operation with >96% utilization rates on the three CMM's... crank em up!

            • #8
              ONLY if the machines are the 'same' machine. Old Validator (35+ years old) vs new Global. Global runs all day at absolute 6 touch speed, the Validator would bust tips & TP20 units at that speed. BUT, you will get correlation between machines IF:
              (1) Your calibration touch speed and your program touch speed ARE THE SAME (no matter what they are)
              (2) You are not driving faster than the machine hardware should use.

              I get correlation all day, day after day, within the machine specs of the Validator between the machines. Validator at 150 move, 2.5 touch, Global at 500 move, 6 touch. I write 1 program, but an operator input tells the program which machine it is on and it sets the move/touch speed for the machine. ALL done in absolute
              sigpic
              Originally posted by AndersI
              I've got one from September 2006 (bug ticket) which has finally been fixed in 2013.

              Comment


              • anthony.alfaro
                anthony.alfaro commented
                Editing a comment
                fair enough.

                I'll do you one better: (I saw this at a customer once)
                Bury a .txt file on the hard drive that has machine parameters in it (Touch, move, etc. etc.) and write in a few I/O lines for the program to detect what machine it's on automatically rather than have the operators do it.

            • #9
              Yeah, that won't work (been suggested many times) but I have 3 options, (1) Validator, (2) Global, and (3) Global with correct touch speed but much slower move speed for testing the program.
              sigpic
              Originally posted by AndersI
              I've got one from September 2006 (bug ticket) which has finally been fixed in 2013.

              Comment

              Related Topics

              Collapse

              Working...
              X