I am trying to create a journal that can scan and return the tool length adjust register each tool in a part. I am having very mad effects on a couple machines that use different register values so I need to be able to scan an NC file to make sure this doesn't happen. I know you can call it using MOM_tool_length_adjust_register in the post builder but I need a stand alone journal to do this. Does anyone know how to go about doing so? Any help is much appreciated thank you.
Are you sure you want the register defined in the tool? Since the operation inherits the register from the tool, and can override it, I would cycle through the operations. For example, you could have a tool with register 5, but change that to 51 in one operation and 52 in another operation.
FYI OOTB, the operation inherits from the tool, which inherits from the pocket.
The problem is that we do not use the tool library that comes with NX so we copy them in form out own library (which happens to be a part file). Essentially it is like the tool is being created as the program is. We have one machine that need the register to be 1 while another needs it to be 0 and if ether of the machines receive the incorrect register value the machine will crash due to the tool offset. Thank you for the reply.
Why not have a template part for the tools of each machine?
This will make sure the tools always have the correct values for that particular machine.
Production: NX10.0.3, VERICUT 8.1, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk Testing: NX12.0 Preparing: NX12.0
Employees of the customers, together we are strong
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide
The problem with that is that the post builder uses the libraries we created and if we created multiple ones we would have hundreds of duplicate tools just for the register value.
Thank you for the ideas though.