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 use a clearance plane in every program, and I almost always only use it at the top of the program to clear the part, set the first probe rotation and check the first point/feature. After that it is AUTOMOVES and move/points. I also won't use move/increment in a program BECAUSE, if you get a false trigger during a move/increment for whatever reason, when you tell it to continue, it will try to move the entire increment from it's current position. Nope. I'll use them when making and proving out a program ('cause I'm too lazy to get up and walk over to the machine and jogbox a move). but once I get the probe where I want it, BANG! Move/point and increment is GONE!


    HMMMM thats crazy I have never had that issue with false triggering and the move/increment happen to me before but I will keep an eye out for that/keep it in mind, Thanks for that!
  • just do a quick test without even a part. Simply make a bogus program, move/point to X0Y0Z0, then increment to Y200 or something. Set the speed low, and simply touch the probe while it is moving that increment. Tell it to continue and see where it ends up.
Reply Children
No Data