hexagon logo

CMM Programming Good Practices

I'm training a CMM Operator to become a beginner CMM programmer and he's making the same mistakes I did when starting out and it got me wondering: what are some of the standard CMM programming practices you all follow (either instructed to or from experience)?

I'll share a few of mine:

- Way prior to a new project kickoff, make sure to review all of the documentation (mainly CAD models and prints) to ensure everything on them is clarified by the designer/customer to avoid frustration and confusion down the line.

- After writing and running a program for the first time, check the reported measurements. If all is good, go back and refine the program to make it faster and more efficient, especially for high production parts.

- Create a rock solid manual and DCC alignment so that any operator can open the program and understand how to align it with minimal supervision, especially if the machine is in Operator mode.
Parents
  • Here are some of the things I had done starting out.

    I always review my print and create a plan for each dimension that I need to measure and the general flow of the program. I used to makes notes on the print for my plan but over time I stopped doing that. Then I ensure my setup will allow me to reach as many of the dims as possible if not all of them.

    I calibrate all of my probes before I run my program unless I have a whole lot. In that case I rely on my not calibrated in the last 30 days notification.

    If I had a physical part I would run each feature as I created it to ensure it did exactly as intended. Prevents any surprises when running the whole program.

    When running a program I wasn't familiar with or just created I would put a break point on each Tip articulation to ensure the probe wouldn't slam into the part or table.

    When setting my part up manually 90% of the time I use an iterative alignment due to simplicity and it removes any need to transform the CAD. I then follow up with a level rotate origin DCC alignment.

    Make sure you fully understand what measurements are being requested and if you don't... ask. Never assume.

    Once the program is complete and you have data take time to review it and make sense of it. Understand why each value was reported (mainly profiles/positions/parallelism etc.) This step is a huge in becoming an effective programmer.
Reply
  • Here are some of the things I had done starting out.

    I always review my print and create a plan for each dimension that I need to measure and the general flow of the program. I used to makes notes on the print for my plan but over time I stopped doing that. Then I ensure my setup will allow me to reach as many of the dims as possible if not all of them.

    I calibrate all of my probes before I run my program unless I have a whole lot. In that case I rely on my not calibrated in the last 30 days notification.

    If I had a physical part I would run each feature as I created it to ensure it did exactly as intended. Prevents any surprises when running the whole program.

    When running a program I wasn't familiar with or just created I would put a break point on each Tip articulation to ensure the probe wouldn't slam into the part or table.

    When setting my part up manually 90% of the time I use an iterative alignment due to simplicity and it removes any need to transform the CAD. I then follow up with a level rotate origin DCC alignment.

    Make sure you fully understand what measurements are being requested and if you don't... ask. Never assume.

    Once the program is complete and you have data take time to review it and make sense of it. Understand why each value was reported (mainly profiles/positions/parallelism etc.) This step is a huge in becoming an effective programmer.
Children
No Data