Adding a JT file straight in Teamcenter w/o NX Manager

[n2design]

I need to add a JT straight in Teamcenter without interfacing with NX Manager. Does anyone have a simple approach? I received the instructions below from GTAC that suppose to work with older versions of Teamcenter but I can seem to get them to work TC 8.


Guide to configuring Teamcenter [TCEng 2005 SR1 or TC2007] and NX [4.0.4.x ,
5.0.x , and 6.0.x] to work with Multi-CAD assemblies using JT:

To quickly create a test 'Multi-CAD' assembly:

In the Teamcenter Portal Navigator create a new item (File->New->Item). Then
select the Item revision, and create a new dataset (File->new->dataset). In
the dataset dialog, select DirectModel from the row of icons on the left, and
next to the Import field, select the three dots (...) to browse to a local JT
file. OK the dialog and you have your Item containing the DirectModel dataset
that contains the imported JT.

Now create a second new item. MB3 on it and select 'Send to->PSE'. Back in
Navigator, copy the Item Revision that you created the JT dataset in, and in
PSE, paste it under the second Item. Save the assembly and close PSE.

To open Multi-CAD assemblies in NX using JT:

In order to open this JT assembly in NXManager, you will have to add one
setting in the Teamcenter Edit->Options dialog. This will make NXManager
aware of these datasets.

 

[n2design]

Here is the entire instruction write up but nothing addressing TC 8.3. This is too confusing. Is there anyone that can help?

Guide to configuring Teamcenter [TCEng 2005 SR1 or TC2007] and NX [4.0.4.x ,
5.0.x , and 6.0.x] to work with Multi-CAD assemblies using JT:

To quickly create a test 'Multi-CAD' assembly:

In the Teamcenter Portal Navigator create a new item (File->New->Item). Then
select the Item revision, and create a new dataset (File->new->dataset). In
the dataset dialog, select DirectModel from the row of icons on the left, and
next to the Import field, select the three dots (...) to browse to a local JT
file. OK the dialog and you have your Item containing the DirectModel dataset
that contains the imported JT.

Now create a second new item. MB3 on it and select 'Send to->PSE'. Back in
Navigator, copy the Item Revision that you created the JT dataset in, and in
PSE, paste it under the second Item. Save the assembly and close PSE.

To open Multi-CAD assemblies in NX using JT:

In order to open this JT assembly in NXManager, you will have to add one
setting in the Teamcenter Edit->Options dialog. This will make NXManager
aware of these datasets.

In Teamcenter, log in as infodba, and select Edit->Options. In the dialog
box, select the Index button at the bottom. In the search field, type

TC_NX_Foreign_Datasets

If no preference exists already, in the right hand pane create a new
preference:

Name - TC_NX_Foreign_Datasets
Scopes - Site
Type - String
Multiple Values - True
Values - DatasetType="DirectModel" NamedReference="JTPART"
NamedReferenceFormat="BINARY" NamedReferenceTemplate="jt"

To add the Value, copy the text following 'Values -' above and paste it (all
one line) into the field at the bottom, and hit the + button.

Then hit Create, and OK or Cancel out of the options dialog.

Additionally, in order to see this preference, you need to set:

NX_Interop_Type=plmxml

This uses plmxml instead of the older bkm bookmarks to send structure from PSE
to NX, and allows us to send Multi-CAD assemblies to NX, as well as pure NX
assemblies. The OOTB default is bkm.

Restart TCEng and NX. When you next go into NX Manager, select
Preferences->NX Manager and go to the Multi-CAD tab, and if you don't see the
DirectModel option in the Multi-CAD Part Types Order list, go back to the
General tab and select 'Restore all Defaults'. Then check the Multi-CAD tab
again. You should now see Direct Model in the list.

Set the required customer defaults below, restart NX, and open the test
Multi-CAD assembly you created above in NX to confirm your settings are
correct.

NX4.0.4 , NX5.0.x , and NX6.0.x Multi-CAD Customer Defaults & Preferences:

* Set 'Structure Update on Load' to Complete in

NX 4.0.4
Preferences-> NX Manager->Assembly or
Customer Defaults->NX Manager->General->Assembly

NX 5.0.x and NX 6.0.x
Preferences->Teamcenter Integration->Assembly or
Customer Defaults->Teamcenter Integration for NX->General->Assembly

This will use the structure stored in Teamcenter (in the BVR) to generate the
assembly structure of Multi-CAD assemblies.

* Set 'Structure Update on Save' on in

NX 4.0.4
Preferences-> NX Manager->Assembly or
Customer Defaults->NX Manager->General->Assembly

NX 5.0.x and NX 6.0.x
Preferences->Teamcenter Integration->Assembly or
Customer Defaults->Teamcenter Integration for NX->General->Assembly

This will update the structure stored in Teamcenter (in the BVR) with changes
made to assembly structure of Multi-CAD assemblies in NX.

Structure changes such as repositions, addition and removal of components,
substitutions will not require UGMaster datasets to be created to persist in
Teamcenter.

WAVE links, mating conditions, promotions etc. will require assembly level
UGMasters to be persisted (see the 'Add NX datasets' option below).

* Set 'Add NX datasets' to Never or If User Modifies Part - Prompt in

NX 4.0.4
Preferences-> NX Manager->Parts without NX datasets or
Customer Defaults->NX Manager->Extras-> Parts without NX datasets

NX 5.0.x and NX 6.0.x
Preferences->Teamcenter Integration-> Parts without NX datasets or
Customer Defaults->Teamcenter Integration for NX->General-> Parts without NX
datasets

This will either never, or on modification give the user the option to create
UGMaster datasets in components or assemblies that do not contain them
currently.

This setting will depend on your workflows and on what you consider to be the
master CAD data in the Item Revision.

If the Multi-CAD dataset that originally creates the JT is always to be the
Master, then set this option to Never.

If NX can take ownership and modify data and save a UGMaster derived from the
JT, then set this option to If User Modifies Part - Prompt.

* Set Display Seed Part Dialog to No and select a default seed part in

NX 4.0.4
Preferences-> NX Manager-> Parts without NX datasets or
Customer Defaults->NX Manager->General->Seed Parts

NX 5.0.x and NX 6.0.x
Preferences->Teamcenter Integration-> Parts without NX datasets or
Customer Defaults->Teamcenter Integration for NX->General-> Parts without NX
datasets

To avoid the display of the Seed part dialog for each part that does not
contain a UGMaster. Choose a metric or Inch seed part to match the units of
the assemblies you are working with.

If you wish to use an NX5 template part as a Seed part, as infodba copy the
template from the

infodba:NX5 Templates folder to the
infodba:Unigraphics seed parts folder.

Then add it to the NX Default Seed Part customer default.

* Set your JT tessellation options to create XT JTV9 datasets. These are

faster to extract exact data from, and have a range of other advantages - In
the tessUG.config file that defines JT translation options the following
lines need to be set:

multiCADJT = true (NX 5 only - not set OOTB - creates JTV9 data)
JtFileFormat = "9" (NX 6 only - set OOTB - creates JTV9 data)
XTbrep = true (NX4, 5 and 6 - should be set OOTB - creates XT Brep)

* For improved performance loading JTs, set 'Initially Extract exact data
from JT parts' to:

NX 4.0.4
Preferences-> NX Manager->Multi-CAD or
Customer Defaults->NX Manager->Extras->Multi-CAD

Set to off

NX 5.0.x
Preferences->Teamcenter Integration-> Multi-CAD or
Customer Defaults->Gateway->JT Files->Extract Exact Data

Set to off

NX 6.0.x
Preferences->Teamcenter Integration-> Multi-CAD or
Customer Defaults->Gateway->JT Files->Extract Exact Data
Set to All JT Files Except Files with JT Brep

This will load JTs as Faceted geometry rather than precise. In NX 6,
improvements have been made to the performance of extraction of XT Brep that
mean this only needs to be set for the slower performing JT Brep.

* Set Layer to Work (or Original if all your parts are created with the
same layer options) in

NX 4.0.4
Customer Defaults->Assemblies->General->Add Component

NX 5.0.x
Customer Defaults->Assemblies->General->Component Operations->Add Component
To show imported geometry on the same work layer as the rest of the assembly.

Caveats:

NX does not support opening Ideas (or any other multi-CAD system's) assembly
level datasets - Solid Edge, Catia V5, etc. Instead, we read the structure
information from the BVR and use that to build assemblies. Only Multi-CAD
part datasets are read by NX (Catia V4, V5, Solid Edge, JT,etc.) A JT dataset
containing geometry at the assembly level will be read as assembly level
geometry.

Some CAD integrations, for example Ideas Manager, when asked to create JTs in
Teamcenter for an Ideas Assembly, will create JT datasets in all parts and
assemblies. However, if there is no geometry in the assembly, the JT dataset
created does not have any named references (i.e. is empty). This can also
occur if a translation fails.

NX has always treated opening a JT without a named reference as an error (it
would only have resulted from an error creating that JT), and so stops and
informs the user that there is a problem.

A solution would be to have a process that scans the database for these empty
JT datasets and deletes them. A fix is present in NX5 upwards that allows NX
to process any children of an assembly containing JT datasets with no named
references to be processed as empty parts without raising an error.

 

[JurgenKreisel]

This is my solution.

In TC
Create a new item.
Open the item and select the item revision.
File-New-Dataset or CTRL-D
Select the More button and select DirectModel.
Select the ... on import.
Select your jt file.
You may need to select Directmodel from the list on the left again.
Select OK.
Your jt file will be imported into the item revision.
I just double click the jt data set and it opens my viewer externally.

Regards
Jurgen
NX8 TCUA 8.3

 

[n2design]

I tried your steps and when it opens the structure tree is there but no geometry. All the parts in the assembly boxes are checked with white check marks. How do I get the geometry to appear?