Session 10
Post-Processing & Troubleshooting
A Clean Simulation Isn't the Finish Line
OnShape's simulation shows the toolpath. Your machine needs its own language to actually run it.
The Post-Processor
Translates CAM Studio's generic toolpath into the specific code your exact machine's controller understands.
Different Machines, Different Language
A ShopBot and a Makera don't read the same code — the wrong post-processor produces code your machine can't run correctly, even from an identical simulated toolpath.
Your Machine
[VERIFY] — confirm the exact post-processor selection for your specific machine with your instructor before running anything for real.
The Diagnostic Clinic
From here on, most problems show up as a symptom first — you work backward to the cause.
Symptom: Didn't Cut All the Way Through
Likely cause: stock thickness entered wrong, or final depth set short.
Symptom: Part Came Out Undersized
Likely cause: wrong profile offset — Session 7's exact problem.
Symptom: Part Shifted or Came Loose Mid-Job
Likely cause: no tabs, or tabs too small — Session 8's exact problem.
Symptom: Bit Broke
Likely cause: step-down too aggressive for the material.
Symptom: Machine Errored or Moved Strangely at Startup
Likely cause: wrong post-processor, or zero point not actually verified — Session 4's protocol.
Notice the Pattern
Every one of today's symptoms traces back to something already taught — nothing here is a brand-new idea, just the same ideas showing up as real-world failures.
Two Things to Remember
A symptom rarely has just one possible cause.
Check the most likely explanation first, but don't stop looking if it turns out wrong.
Two Things to Remember
A pre-cut checklist beats fixing mistakes after material's already ruined.
Everything on today's list is cheaper to check before pressing start than after.
Next Up
Week 4: The Practice Build.
Design a small item, program it, actually cut it — everything from these four weeks, in one small project.