What you say is not completely accurate regarding the conversion of the cut
data (being only for a single material).
If you are in a sequence and add a tool to the Tool Manager, then yes, it
only reads the data from the material defined in the Operation.
However, if you load the tools from outside a sequence you can read in each
material's cut data from the pull-down menu in succession and then do a
File>Save from the Tool Manager and the XML file will be created with the
cut data for all the materials. A bit cumbersome, I know, but you do get
all your data. A mapkey would be handy here. Also, when you read this XML
file into another .mfg file, all the material cut data gets loaded without
having to cycle through each material.
Note though, that once you have written the XML file, Pro will no longer
look at the 'old' .tpm file for that tool. Therefore, when converting your
cut data you need to read in all the various materials the very first time
you access the tool or you will - essentially - lose the cut data for all
the other materials. It's not really lost, the .tpm still exists, so you
could delete the (incomplete) XML file and re-read the .tpm file again if
Another issue is the mfg_param_auto_copy_from_tool config option. I find
that there is no sense as to how PTC decided to use rough and finish data.
It was very arbitrary. Don't quote me, but I think Volume, Rough, Re-rough
used 'rough' values and everything else used 'finish' values. Who is to say
that a drilling operation is rough or finish? What about a trajectory?
Anyway, we rarely use the same tool for roughing and finishing, we have
different tools for each type of operation (insert mill for rough, solid
carbide for finishing). All of our cut data resided as 'rough' (even for
finishing tools) just because that is the first menu pick. To use the new
config option would invalidate almost all of my cut data anyway.
NC Programming Manager
Jarvis Products Corporation