G-code typo nearly scrapped a $900 part yesterday

Running a job on the Haas in Reno and fat-fingered a decimal in the finish pass, took 0.075 off instead of 0.0075. Caught it on the first part check with the mics before it ran the whole batch of 40. Spent 20 mins rewriting the line and re-probing, part came out dead on. Anyone else triple check their decimals after a close call like that?

1 comments

Log in to join the discussion

Log In

1 Comment

thomasgonzalez13h ago

Man, decimal errors are sneaky because the machine just does what you tell it, no complaints. I started putting the finish pass depth in a comment line right above the move so my eyes catch the mismatch before cycle start.

4