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
  • Yeah I've never even tried to use one, but I'm the same in that I wouldn't like not being able to see where there is a move. Most programmers I've met don't even like clearance planes because the move/clearplane command doesn't show what level it's at. I think it would be cool if it showed which work plane and what value it's at each time the command is entered. I.E. move/clearplane, ZPLUS, 0.05


    I hear ya.

    Thats why i usually probe a plane on the top of my part (or even a point) and I will make PLN_TOP.Z+0.5 my clearance plane and as long as the part isn't too complex thats the one and only clearance plane I have to set and I won;t have to worry about any other movepoints. If you look at it like this, really simplifies stuff
Reply
  • Yeah I've never even tried to use one, but I'm the same in that I wouldn't like not being able to see where there is a move. Most programmers I've met don't even like clearance planes because the move/clearplane command doesn't show what level it's at. I think it would be cool if it showed which work plane and what value it's at each time the command is entered. I.E. move/clearplane, ZPLUS, 0.05


    I hear ya.

    Thats why i usually probe a plane on the top of my part (or even a point) and I will make PLN_TOP.Z+0.5 my clearance plane and as long as the part isn't too complex thats the one and only clearance plane I have to set and I won;t have to worry about any other movepoints. If you look at it like this, really simplifies stuff
Children
No Data