JT Files - using nx3.0/windows

[jackley]

Anyone have any experience with .jt?

We recently got some from a customer. An assembly (Engine, oil pan, transmission, some oil lines, etc. A lot of information) and component level. On the component level the models are at 0,0, not vehicle position. In the assembly, it's vehicle position.

Now I know how to get to the properties --> jt file --> extract exact data, but the assembly file takes over a day to attempt to extract it and it failed. Now on the component level I can do it with just a little bit of time, but positioning some of the components is going to be very difficult.

I have tried deleting certain components out of the .jt file I opened and extracting just those, but it looks like it re-reads the .jt file and wants to extract all of it.

Any information, help?

Thank you

Justin Ackley
Designer

 

[hudson888]

Justin,

I have tested using JT2Go creating and opening assemblies as your described. Your customer should have sent you an assembly file and all the components. Perhaps you don't have precisely what you need or the customer needs to give you better structured data or more information. To that end my testing was as follows.

Using UG I selected File>Export>Teamcenter Visualization. I ran NX-3 for the test, under XP-Pro. Normal windows dialogs allow you to save your output to a directory, and name the output assembly. I name that assembly "TEST" which resulted in a file called TEST.jt and a new directory called TEST with all the components in named for their original name with the suffix PART_SOLIDS.jt There was also one extra part called TEST_PART_SOLIDS.jt

This assembly opens okay in JT2Go, as it was only a small one. You should also find if you use Teamcenter Vizualization, or VisView as it was known, then you can open the assembly structure a bit at a time.

I have used entire vehicle assemblies in the automotive industry regardless of whether I open the .jt files via teamcenter or not the system works just fine.

Doing what you're doing is brilliant if you can get it to work, but for big assemblies I think that you'll have to break up the data into bite sized chunks.

JT2Go is a free trial download from UGS easily googled on the internet. It appears to be a cut down version of temcenter visulization and works quite similarly.

Hope this helps,

Hudson

 

[jackley]

The work around I was looking for was right underneath my nose. Just delete out the components in the directory so the .jt file doesn't pull them up.

I think we have vismockup or visview (I do not use either so I am not certain).

Thank you.

Justin Ackley
Designer