how to handle new releases

[Kannon]

With toolpath and software upgrades....how do you handle your previously programmed toolpaths?

 

I have some from previous versions I run..and now am in the process of re-programming do to better toolpaths along with knowledge...granted I am still in 9. how do you handle previously programmed toolpaths.

 

 

At what point are you sayin...I need to re-program a previous job due to new options available?

or do you leave it alone?

[crazy^millman]

Really no set thing I use. It really depends on if I got the time, if we are losing our buts on it, if the documentation is no good or there is none. If we are running it is a different machine and it has to be approached different. A lot of factors go into every job and each one is a case by case bases. If I have the old file I will most time just update it to the newest version I am using. Keep the old tool group make a new one take what is good and copy it and then add to that as I need to.

 

HTH

[Tim Johnson]

I update the jobs as they run across my desk. If the current style of programming is better on certain parts for the operators they'll bring the program folder in to me. Other than that I update the parts as they're revised. (quite often here)

[Guest]

Have to agree with what's been said.

 

If an older job comes across your desk and you look at it and you just "know" it could be done better at this point, then it's likely time.

 

However, I would open the job and save it into the latest version at that point in time as a MINIMUM.