We use NX but not with data stored inside of Teamcenter. So we load our local data into native NX and then use File > Export > JT (with As NX option) and we get our jt files created. We can then load them as an assembly into Teamcenter Lifecycle Visualization but there is no refset info in the jt files. We need this info for our different user groups and customers.
So we ran ugtopv with Multicad as the structure option and we can create jt files, but when we load the top level jt file into Teamcenter Lifecycle Visualization it doesn't bring in the rest of the assembly.
At the end of the day we want to export a jt assembly from NX with jt files for each part (not monolithic) and have refset or layer info in the jt files that we can in turn load in Teamcenter Lifecycle Visualization and change the way the parts are viewed.
So our workaround is to rename the top level jt file created from File > Export so that when we run ugtopv it is not overwritten. Then we discard the new top level jt file and reverts the old one back and now we can load our data into Teamcenter Lifecycle Visualization as an assembly and get the refset info.
Is there another way to do this?
Solution
Yes, instead you can use the following settings in tessUG.config along with the -honour_structure (this is equivalent to File > Export > JT) option and it will give you what you are looking for:
structureOption = "MULTICAD"
writeWhichFiles = "JTPARTS,PLMXML"
useRefsets = "ALL"
By doing this the translator will produce a top level PLMXML file with assembly structure and JT for parts. Part JT will contain all reference sets which can be filtered in Teamcenter Lifecycle Visualization using "Reference Sets" capability. You can see assembly structure by loading the PLMXML in Teamcenter Lifecycle Visualization too.
Notes and References
Hardware/Software Configuration
Platform: INTEL
OS: window
OS Version: XP32_SP3
Product: NX
Application: TRANSLATOR
Version: V11.0.2
Function: NX_JT
Ref: 001-9439005