Another *.STEP file export query
Another *.STEP file export query
(OP)
Morning all,
I'm having trouble exporting assembly structure and part numbers from a Teamcenter managed assembly to send to a supplier. If memory serves me correctly, in previous versions of NX, when you file/open a step file, it came in as bodies, whereas if you opened a blank model, and file/import the structure and filenames would come in. This doesn't seem to be the case in NX9 unless I'm missing something.
I can't see any detailled options either on the step import or export, and I've tried 203 and 214 types
One last question, is that the supplier would like the descriptions as the STEP - I don't think this would be possible, so have prepped them to recieve an excel document exported from structure manager within Teamcenter.
Oh, and I'm working in NX9.0, managed by Teamcenter 9.
Thanks
Tom
I'm having trouble exporting assembly structure and part numbers from a Teamcenter managed assembly to send to a supplier. If memory serves me correctly, in previous versions of NX, when you file/open a step file, it came in as bodies, whereas if you opened a blank model, and file/import the structure and filenames would come in. This doesn't seem to be the case in NX9 unless I'm missing something.
I can't see any detailled options either on the step import or export, and I've tried 203 and 214 types
One last question, is that the supplier would like the descriptions as the STEP - I don't think this would be possible, so have prepped them to recieve an excel document exported from structure manager within Teamcenter.
Oh, and I'm working in NX9.0, managed by Teamcenter 9.
Thanks
Tom
Contract Mechanical Design Engineer.





RE: Another *.STEP file export query
This makes importing things a bit more difficult , say you open a single step file which is an assembly , all the components needs to have Items/ item revisions etc etc created.
We ( "my" company ) have the rule to always do the import in native mode since you never know what the import will produce.
We had one case where a guy imported a step assembly, he then ticked the "flatten Assembly" option( which converts all the components into bodies in one partfile) the problem was that NX, before converting the component->body, produced all the separate partfiles. These separate partfiles stays as partfiles under Teamcenter Named References. this single item got very big/heavy.
Your memory regarding assembly/ multiple bodies is somewhat correct, correct when working with parasolid files but incorrect when Step. ( Step depends on the settings.)
Regards,
Tomas
RE: Another *.STEP file export query
Regards
Tom
Contract Mechanical Design Engineer.
RE: Another *.STEP file export query
The whole process seems very hit and miss - all I'm after is an assembly file structure and part numbers to be exported with the STEP, rather than dumb bodies.
Contract Mechanical Design Engineer.
RE: Another *.STEP file export query
www.nxjournaling.com
RE: Another *.STEP file export query
Cowski, that looks to be it!
Thank you very much
Contract Mechanical Design Engineer.