hexagon logo

long program run times

I just made a program that has 43 minutes run time. That's the longest I have ever done for a single part. I did a Zeiss program that was 9 hours but it was for 20 parts at the same time. What is some of your run times?
Parents
  • I suppose you all spend lots of time planning and review the probe path and such. but we are not perfect. How do you all handle unexpected probe hits and things of that nature. Or a scenario where your measurements are so far off you decide to re calibrate your probes. Do you just have to start over? Print the report in sections

    Biggest machine I have is a 7107 and the longest run time was probably about 30 mins.


    Those are some good questions... the fact that you're thinking of these things without experience tells me you're a sharp one. People finding out that my ~18hr cmm cycle run had to be re-ran made me sharp. Every program made use of the ONERROR function and NOCENTER on holes to name a few... plenty of "what if" logic too - to prevent stopping and re-starting a 2 shift CMM cycle run. These parts were huge and very detailed.
Reply
  • I suppose you all spend lots of time planning and review the probe path and such. but we are not perfect. How do you all handle unexpected probe hits and things of that nature. Or a scenario where your measurements are so far off you decide to re calibrate your probes. Do you just have to start over? Print the report in sections

    Biggest machine I have is a 7107 and the longest run time was probably about 30 mins.


    Those are some good questions... the fact that you're thinking of these things without experience tells me you're a sharp one. People finding out that my ~18hr cmm cycle run had to be re-ran made me sharp. Every program made use of the ONERROR function and NOCENTER on holes to name a few... plenty of "what if" logic too - to prevent stopping and re-starting a 2 shift CMM cycle run. These parts were huge and very detailed.
Children
No Data