Due to a needed shift in my company's direction it has become necessary for us to shift away from PostBuilder to a 3rd party posting solution (in our case ICAM). Our training on this is scheduled for next week but I am looking into some the foreseeable issues. One of the things we have done for a long time is to use the Tool Attributes to define additional needed information that is not handled by the cutter definition. Our Siemens controls can use an alpha-numeric for a tool number and to control this we use a Tool Attribute Variable to pass the information to PostBuilder since NX is incapable of utilizing this feature of Siemens controls. Is there a way to customize the CL File Output to read these variables or will we need to convert to using UDE's. I looked at the documentation but I am not finding a lot of information, of course I could just be looking in the wrong place. Any help would be appreciated.
Solved! Go to Solution.
The CLS files are generated with a specially crafted post, so everything you do with a post can be done to enhance the CLS output.
See "%UGII_BASE_DIR%\MACH\resource\tool_path" for the Tcl files to output CLS files.
I would suggest to create your own CLS output Tcl file.
It should source in the standard CLS Tcl file that best matches your desired output.
You can then overwrite procedures to enhance the output.
Production: NX10.0.3, VERICUT 8.0, FBM, MRL 3.1.4 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk Testing: NX11.0 EAP, NX12.0 EAP
How to Get the Most from Your Signature in the Community