Import JT files from MultiCAD
Import JT files from MultiCAD
(OP)
Hi.
I'm not sure where is the right place for the question - here or in the NX forum...
We recently get NX files from Daimler.
For example, one delivery has the following files:
A1234.prt (assembly)
A1234_1.jt (geometry)
If we open the assembly on the Daimler Supplier Package, it creates a file called A1234_i_jt.prt, and it appears in the assembly navigator, but not on the hard drive.
When we close the files, and save them, we don't see the _jt.prt file, and when we try to "import assembly into teamcenter" for A1234.prt , it shows error that it doesn't find the file A1234_1_jt.prt
Failed to find file using current search options, part left unloaded
If we open the A1234.prt on the "native" NX 10.0 , it shows the same error as in the TeamCenter.
If we open the JT file by drag-drop, and then open the A1234.prt, on the NX 10.0 native , then it shows up, but if we "save all" it created the A1234_1_jt.prt in the folder.
Next time we open the A1234.prt, we get the error:
Part is not a valid version of component part
We don't know what to do.
I'm not sure where is the right place for the question - here or in the NX forum...
We recently get NX files from Daimler.
For example, one delivery has the following files:
A1234.prt (assembly)
A1234_1.jt (geometry)
If we open the assembly on the Daimler Supplier Package, it creates a file called A1234_i_jt.prt, and it appears in the assembly navigator, but not on the hard drive.
When we close the files, and save them, we don't see the _jt.prt file, and when we try to "import assembly into teamcenter" for A1234.prt , it shows error that it doesn't find the file A1234_1_jt.prt
Failed to find file using current search options, part left unloaded
If we open the A1234.prt on the "native" NX 10.0 , it shows the same error as in the TeamCenter.
If we open the JT file by drag-drop, and then open the A1234.prt, on the NX 10.0 native , then it shows up, but if we "save all" it created the A1234_1_jt.prt in the folder.
Next time we open the A1234.prt, we get the error:
Part is not a valid version of component part
We don't know what to do.
RE: Import JT files from MultiCAD
Change "From Search Folders" to "As Saved..." and see if that helps.
The same will hold true when you Import Assembly into Teamcenter. That menu will have a Load option tab/field, as well.
I suggest making a 'clean' assembly in native before importing into TC.
Could try:
Open A1234_1.jt and save (to the same folder) and close. Open A1234.prt and replace A1234_1.jt component with A1234_1_jt.prt and save A1234.prt. Close all and reopen. If successful with no errors, then Import A1234.prt into Teamcenter (it will take the sub-components).
Gary Bangs
www.flowserve.com
RE: Import JT files from MultiCAD
Opening and saving to the folder, and then replacing component, issues another error, shown on another picture...
And the assembly navigator looks like this:
RE: Import JT files from MultiCAD
Replacement looks like it already renamed to .._jt.prt. Try, adding the component in again (on top of and in the same location), then, delete the original instance of the component. Save and reopen.
Valid version - meaning having a 'linear heritage' from the original file (Save As...). Typically, if you have a new file, with the same name, you'll get this error.
Gary Bangs
www.flowserve.com
RE: Import JT files from MultiCAD
As for my local computer, this specific file is in D:\ , in the root directory.
Your "solution" may be relevant for a single file.
What if we get 5000 files, with 15 JT files located in 100 different positions? (for example - screws, washers, nuts).
We are looking for an "automatic" or "semi-automatic" solution for this.
Opening each JT and manipulating it with "save as" is not a good solution for us. Takes too much efforts, and can cause mistakes.
Thank you
RE: Import JT files from MultiCAD
Not being there and seeing what you are dealing with, puts us at a disadvantage - and leaves us shooting in the dark. The issues you describe is not the behavior I expected to see, and have not encountered in my travels. Perhaps someone else has?
What do we do next? We may have to start from the beginning...
How are the files sent to you? zipped?
Let me try some .jt file on my end and see what I can discover...
Gary Bangs
www.flowserve.com