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.


    I don't spend lots of time planning to be honest. All of my programs follow the same flow when it comes to "finding the part" and setting up base alignments.

    When it comes to actually driving around the part...I write a section of code and don't move on until I am entirely confident that it won't crash. Do that from start to finish, you're good!

    I am a big fan of using clearance planes that are tied to a feature (is nice if you're changing your alignments a lot)
           CLEARP/ZPLUS,PLN_C.Z+1,ZPLUS,PLN_C.Z+1,ON
    
  • Never thought about hardcoding a feature into the clearance plane command. I'll keep that in mind!
Reply Children
No Data