Running someone else's programs

Hello all, I have recently started running a cmm again after not touching one for 5 years. My manager has told me to run through all the pcdmis programs that already exist and says that none can be trusted as the previous operator was not the best and crashed several times.
What are some good habits for running someone else's programs that cant be trusted?I could rewrite them but i feel i should be able to work through what is already there. I will be using breakpoints before Tip changes in the program and running it super slow. Any other tips for someone jumping back on a machine and dealing with a mess like this

Thanks.

Parents

bfire85 over 1 year ago

Run those programs slow, holding onto the controller just in case you need to hit the E-Stop. Double check all alignments.

When I moved into the CMM role, I ended up re-writing most of the programs from the previous operator. It is a time consuming process, but the production floor needs to have confidence in the numbers.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

bfire85 over 1 year ago

Run those programs slow, holding onto the controller just in case you need to hit the E-Stop. Double check all alignments.

When I moved into the CMM role, I ended up re-writing most of the programs from the previous operator. It is a time consuming process, but the production floor needs to have confidence in the numbers.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

No Data