Loading…
16
Tool offset mixup ruined a batch, now I double check with a test ring
Running a production job in Dayton last week, I loaded a new tool and typed the offset from memory. Got 30 parts out before checking and found the height was off by 0.012 inches. Every bore was undersized, so I had to scrap the whole run, probably $400 in material and 2 hours of cycle time. My fix is simple now: after any tool change, I cut a quick test ring on scrap stock and mic it before running the real program. Anyone else have a better habit to catch this before it gets past the first part?
1 comments
Log in to join the discussion
Log In1 Comment
the_fiona1mo ago
Honestly, the test ring is just adding extra time to every change. If you're typing offsets from memory, that's the real screwup. Program the offsets in, double check the screen, and run one part before you commit to a full batch. That catches everything without making extra scrap rings.
1