phtaylor
commented
3 years ago ok, thanks.
11:00
so KEY_MET_18X11X50 > KEY_MET > KEY_MET_18X11X50
11:01
but if the asm file is loaded in isolation, KEY_MET would be missing, and not reported.
New
P
damian.rafferty 11:02 AM
KEY_MET is the generic, KEY_MET_18X11X50 is the instance. Spatial 3DInterOP should report the component name something like KEY_MET
Translate Creo 3D files, including XPR (part family table instance) and XAS (assembly family table instance) files without the need to have all external subassembly and part files present, including missing XPR and XAS.
damian.rafferty 9:38 AM Creo has a concept called family tables for creating variants of similar models. A bolt for example. In Creo you model up your bolt, you would add features that vary for an other instance of the bolt to a table, the threaded shaft of the bolt for example. In the table you then create different instances/models of the bolt by defining different lengths without the need to create new models. When you assemble a bolt, you choose the instance of the bolt and Creo creates the parametric model "on the fly". But this is a problem because there is no actual .prt file for all the different bolt instances, just the one bolt.prt with the definition information for all the instances. XPR files are the way around this where Creo creates physical files for these instances in the family table. Xpr and xam files are known as instance accelerator files and are heavily used in Creo
damian.rafferty 10:23 AM Here is a sample assembly that contains some family table instances. The highlighted items are family table instances. For example, KEY_MET_18X11X50 is an instance in KEY_MET. When the assembly is translated in isolation and you read the list of components, you should get something in Spatial that tells you both these names. My issue in the past was that when reading assembly TS027-006-S-006 in isolation, it only reported KEY_MET if KEY_MET_18X11X50.xpr was missing from the directory.