Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations waross on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

JT - Exporting with attributes from Components in UGS NX 6.0

Status
Not open for further replies.

adra

Computer
May 20, 2010
3
HI!
Brief description of our needs:
We export models from .prt to .jt. Later, we use .jt in our application. In order to connect single elements of a model with out data base, we use attribute: DNV_UID. Attributes are set in Root assembly in NX, and are unique for all elements (including instances). E.g. Instance 'A' of assembly 'B' will have its unique id, and all its children will have its unique ids.

Problem:
After exporting to JT, our attributes are no longer unique. You can see, that Instance A and Assembly B will have an unique DNV_UID, however all children of A, will have exactly the same DNV_UID as children of B!

Answers I am looking for:
How can I fix the problem?

What are my options here? Please note that there is also a requirement on the model, to be able to alter the model, with preservation of all DNV_UID's that where defined earlier.

Additional info:
We are not using TeamCenter. Just plane NX modeling license.

Thx for any help!

 
Replies continue below

Recommended for you

log into your nx log file(->help) after a jt export
in the jt translation process a tess.config file is used.
sSearch for *.config file in the nx log file.
Look where the config file is located - open that file in text editor,look in the ug_config section set the
getAttributes =false -> to true
hih
 
Thx for the answer. However this is not the problem. I have allready set getAttributes to true as you can see in attachment. I have attached config that was use for exporting.

Attributes ARE present in JT file after exporting.

As I am sure You know, there are 2 types of user-defined attribues attached to Components. One can be a part attribute, which you can set directly on part by making Displayed part from component and setting it. The other way, is adding attributes to components in an assembly. And here is the problem.
I add such attributes in my root assembly for all children components. NX is capable of knowing, that instance of a Part has different attribute in some assembly, that other instnance of the same part in that assembly. The same with instances of assemblies.
However, that changes AFTER you export to JT. Exporter seems to drop my attributes, and export only those user-defined attributes specified for part, AND those specified for LAST instnace occurence of all instances of all components inserted. To sum up. JT exporter in NX does not seem to realize, that children of instances of assemblies can differ, as far as user-defined attributes are concerned.

Any other ideas? I guess, the attachment I attached could be helpful, to understand my problem.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor