Imagine pouring water over the part. That's projection. now turn the part as you pour. That's wrap

I guess I'm somewhat immune to this since I machine HPDC parts and we have our own foundry and die casting in-house. Customers send us a cast and machined models. We source dies for the customer, to ensure they fit our die casting machines and verify them once they arrive. If any cast features are out of spec. when we PPAP the parts the whole die goes back to the manufacturer to be fixed or replaced. As dies age, they will inevitably get less consistent, but we run in-process CMM checks on every part. If we see dimensions going out of spec. we will stop production and pull the die out to repair it. We do simple repairs in-house. and major repairs go back to the manufacturer. We try to make sure the parts are good throughout the process and not just when they leave our dock.

That is correct. The cantext$ number can be any unused number on the list. If you look at the Crazy^millman's posting you will see his list is grouped together. You don't have to do the same as his but it makes it easier to find if you need to make additional edits or additions.

My ghetto way of doing this (using a chip fan) is to use a point toolpath somewhere safe above your clearance plane at 1500 RPM. Then a manual entry stepping up the RPM, then a face toolpath to clear coolant/chips. I like the idea of a custom macro to do this.....

Sorry, but that is a very specific error and will need to get a hold of your dealer and see what they can find out for you.

That's the ones they used to build the egyptian pyramids. I think you're both referring to FARO Arms.

Thats a good idea. So one M code that references a macro with ramp-up S commands and dwells? Could you then just build it into the machine def as a coolant command?

They tell me the size of the material they are going to buy. Then they buy something completely different forcing me to redo my program.