Cancel
Showing results for 
Search instead for 
Did you mean: 

Reference Sets, and use of JT's in Visualization on Teamcenter

Valued Contributor
Valued Contributor

Hi

 

we are heavily into Reference Sets here for defining what we see in an assembly in terms of Datums, Sketches, and more importantly parts that have been deformed (springs, Washers, Flexible PCB’s, etc). We have been using NX/UG for 25 years hence how we work.

 

Moving forward we want to use Teamcenter for viewing JT assemblies, but owing to the way they are constructed (JT’s)i.e. from TC BOM, the Reference sets cause us an issue as all of the data gets dragged in. So our Teamcenter generated JTs can contain multiple representations of our models, Flat, Formed, Long, short, etc.

 

Has anyone else come accross similar issues, and how did they resolve?

 

Is it:

 

Reference Sets

AltReps

Deformable parts

 

or something else

 

Also what about our legacy data? How can we correct?

 

Regards

Martyn, Snr CAE Engineer, Renishaw PLC
NX10 Tc10
2 REPLIES

Re: Reference Sets, and use of JT's in Visualization on Teamcenter

Valued Contributor
Valued Contributor

Is anyone actually using Visualization in teamcenter to view JT assemblies?

Martyn, Snr CAE Engineer, Renishaw PLC
NX10 Tc10

Re: Reference Sets, and use of JT's in Visualization on Teamcenter

Valued Contributor
Valued Contributor

If you send the assembly to Vis then you can RMB on the assembly and use Replace Reference Set. I presume you have your tessUG.config file set up to export all reference sets.

 

We use Vis Mock-up but don't use multiple reference sets.

Mike

NX 12.0.0 TC11.3 VMU 11.3