import nx files in teamcenter engin.... .

[Spy]

Hello everyone, I am a brand new user with a small problem: Does anyone know the import procedure nx files (created in unintegrated ambient) in teamcenter engineering? ?

Thank you very much

alex

 

[lostico]

Hello everyone, I am a brand new user with a small problem: Does anyone know the import procedure nx files (created in unintegrated ambient) in teamcenter engineering? ?

Thank you very much

alex

from nx integrated:
tools-> nx managers -> import together

and choose the aid to import, however it is not so easy. . .
a good speech on the use of part-family (to be imported individually and then made to generate children from within tc), and then all criteria should be established to understand how to behave if a component, recalled in the native aid is already in tc (and therefore potentially more updated).

are a bit delicate operations, I suggest you talk to your tc administrator, or some expert colleague.

via forum, even wanting is a little difficult. . .

 

[Spy]

Thank you so much!!
Unfortunately I have no one to be able to ask for clarifications....we work in nx6 and we must import a set on the teamcenter of a customer (who does not know the procedure).

but could you tell me the basic steps? I have to go to the client and try... .

Thanks again

alex

 

[stefano.garbin]

importing a set in tc can really become an adventure.. .
where I work often happens to do it but every time there are several difficulties.
the mode recommended by siemens is to use nx in tc environment, menu "file" -> "import together in teamcenter".
opens a window like the "clona" command.
1-in the main window "main" select the default action for all components (maintain existing or overwritten). if there are already existing components in tc can be preserved or overwritten.
2-go to the "load options" (load options), select the interest option and click on "add assembly" (add assembly) by selecting the axieme to import
3-go to "numbering" (numbering), select the default item type that will be assigned to the components. if the file names perfectly reflect the name that will be assigned in tc then select in the window "convert automatically" (auto translate)
4-the other options you can leave them as they are (unless exceptions)
5-Return to "main", click on "set defaults" and (unless you have selected "auto translate" before) enter one by one the names of the components to be assigned
6-select "dry run" and then "execute" to see that there are no errors
7-if there are no deselect "dry run" errors and click nuivamente on "execute".
8-pray that everything goes well (usually never happens).

alternative
1-creates one by one items in tc
2-in each item creates a ugmaster type dataset and imports the solid model of its component
3- possibly create one or more dateset ugpart to import boards
4-after creating and importing each component, subaxieme and together open all subaxiemi and axiemi and replace one by one components so as to load the newly imported ones

In any case I take the opportunity to reiterate that the import of axes in tc is often a bloodbath.
I think that in the mode recommended by siemens it is necessary to ask for the names of parts not more existing or renamed in the initial axieme... here really should study something more decent!

 

[Spy]

Hello stefano I don't know how to thank you, you were very kind! !

I'll try... who's tough on winning!! maybe... .

alex

 

[The_Matrix]

importing a set in tc can really become an adventure.. .
where I work often happens to do it but every time there are several difficulties.
the mode recommended by siemens is to use nx in tc environment, menu "file" -> "import together in teamcenter".
opens a window like the "clona" command.
1-in the main window "main" select the default action for all components (maintain existing or overwritten). if there are already existing components in tc can be preserved or overwritten.
2-go to the "load options" (load options), select the interest option and click on "add assembly" (add assembly) by selecting the axieme to import
3-go to "numbering" (numbering), select the default item type that will be assigned to the components. if the file names perfectly reflect the name that will be assigned in tc then select in the window "convert automatically" (auto translate)
4-the other options you can leave them as they are (unless exceptions)
5-Return to "main", click on "set defaults" and (unless you have selected "auto translate" before) enter one by one the names of the components to be assigned
6-select "dry run" and then "execute" to see that there are no errors
7-if there are no deselect "dry run" errors and click nuivamente on "execute".
8-pray that everything goes well (usually never happens).

alternative
1-creates one by one items in tc
2-in each item creates a ugmaster type dataset and imports the solid model of its component
3- possibly create one or more dateset ugpart to import boards
4-after creating and importing each component, subaxieme and together open all subaxiemi and axiemi and replace one by one components so as to load the newly imported ones

In any case I take the opportunity to reiterate that the import of axes in tc is often a bloodbath.
I think that in the mode recommended by siemens it is necessary to ask for the names of parts not more existing or renamed in the initial axieme... here really should study something more decent!

at the present time, the import in tc:
- It's a formality if you worked well.
- It's a mess if you worked wrong.
... then you start laughing at "you worked badly," of course.
- Did you change model names on file system?
Did you change the product structure on file system?
- You eliminated branches of the structure outside tc?
Did you use "standard parts" that aren't in tc?
- You changed parts that were out of tc and now you don't know what the updated ones are?
- etc.

If you go out of tc, you have to understand the drawbacks well to return.
I believe it is common to all integrations cad if cads are sophisticated (interpart link, part family, etc)

then that it would need a method + intuitive for import/export that helps especially in cases where something is wrong: agree. :finger:
the integration tc/catia for example, in this is more powerful