Bent tube style routes are often manufactured by NC tube bending machines. With tube and pipe you can save your route in two formats used in programming NC tube bending machines.
The Bending Machine (XYZ or YBC/.LRA) file is an ASCII text file that describes the tube route to manufacture. View and edit the file content in a text editor if needed.
By default, the bending machine file is named <AssemblyNameRunNameComponentName> .lra (for .ybc type files) or .xyz (for .xyz type files) . In the default name, AssemblyName is the name of the open document, RunName is the browser display name for the run that contains the segment to save, and ComponentName is the browser display name for the active tube segment.
By default, the file is saved to the workspace. You can change the name and location of the bending machine files as needed.
Use the bending machine file to transfer the tube route content from Autodesk Inventor Tube & Pipe into the CNC programs that drive the tube bending equipment.
You can also paste bending machine data into detail drawings created to document individual tube segments. For example, you can paste bending machine data from a formatted spreadsheet onto the appropriate drawing sheet.
Bending machine output files are not automatically collected by selecting a top-level assembly during a Pack-and-Go operation.
To take advantage of vault functionality when working in a vaulted environment, manually associate the bending machine files to other vaulted documents.
Unlike other Autodesk Inventor files, bending machine files are not associative to the model data and do not automatically update when changes are made. You must save the model changes, and then select Bending Machine Output from the context menu to save the data again.
Bending machine data pasted into drawing files is also not associative to the model data and requires a manual update. Autodesk recommends that you establish a manual process for updating the files that is specific to the workflow at your site.
Bending Machine and ISOGEN format files are not associated with model data and require a manual update process. Use these tips to limit the frequency of updates and plan for efficient updates when required: