nx 9: assembly loading and cloning problem

[alulecia]

Good evening to all,
I've been a nx user for about two years and recently I've been to version nx9.

I would need support from more experienced users on two issues trying to be as clear as possible:

1) how to manage the cloning of complex axioms:

my typical work solution is as follows:

I work by splitting the files of model 3d and 2d therefore for each component (assieme) I have to manage two files.

typical situation is: together1 + table with 2 (content together 1) with relative table

I have no problem at the time of cloning axieme 2 and its table, but I would like to know whether there is the possibility or another strategy which allows me to clone axieme 2 with its table (and therefore also together 1), bringing me also the table of axieme 1 which is clearly not directly read by the axieme1

I hope I've been clear.

2) Has anyone of you noticed that nx9 does not allow to replace in the reading folders of a file together with the same name?

in previous versions often happened to me that by necessity I was forced or needed to modify a single component and after doing so, I simply replaced the file in the folder; having kept the same name the tree of assembly was updated quietly and I had no problems

Now with nx9 this game fails me and although the new file has the same name I am not read by the assieme.

someone knows whether it is a editable setting or if the new version tracks in some other way the origins of the files.

Thank you very much

 

[ceschi1959]

Good evening to all,
I've been a nx user for about two years and recently I've been to version nx9.

I would need support from more experienced users on two issues trying to be as clear as possible:

1) how to manage the cloning of complex axioms:

my typical work solution is as follows:

I work by splitting the files of model 3d and 2d therefore for each component (assieme) I have to manage two files.

typical situation is: together1 + table with 2 (content together 1) with relative table

I have no problem at the time of cloning axieme 2 and its table, but I would like to know whether there is the possibility or another strategy which allows me to clone axieme 2 with its table (and therefore also together 1), bringing me also the table of axieme 1 which is clearly not directly read by the axieme1

I hope I've been clear.

2) Has anyone of you noticed that nx9 does not allow to replace in the reading folders of a file together with the same name?

in previous versions often happened to me that by necessity I was forced or needed to modify a single component and after doing so, I simply replaced the file in the folder; having kept the same name the tree of assembly was updated quietly and I had no problems

Now with nx9 this game fails me and although the new file has the same name I am not read by the assieme.

someone knows whether it is a editable setting or if the new version tracks in some other way the origins of the files.

Thank you very much

1) I am not completely clear about the use of the term 'cloning' because if you adopt the clone assembly command the problem you already have at the first level in the sense that, if you do not have a management, you can clone the model but not the table. You have to reassociate it by hand.
2) I do not understand, even if when you say at the end of the sentence 'it keeps track of theorigin of the file, I think more about load options.

 

[ceschi1959]

1) is not completely clear to me the use of the term 'cloning' because if you adopt the clone assembly command the problem you already have at the first level in the sense that, if you do not have a Management, you can clone the model but not the table. You have to reassociate it by hand.
2) I do not understand, even if when you say at the end of the sentence 'it keeps track of theorigin of the file, I think more about load options.

this to correct my previous post: instead of management read plm or pdm.

 

[The_Matrix]

If you replace a component with another, you are creating a problem because nx takes into account the uid that is different for every "new file" you do...
therefore 2 components "almost equal" are not for nx because they have different uid.
Instead 2 components could be completely different, but have the same uid because they come from a save as, or from a template if you created it.
try to activate the "allow replacement" option in load options.

Alternatively, put the new component in the same directory, maybe with r2 in the name and then use the comanto replace component with the option mantain relationship.

to keep matings, you have to use names on the faces.

 

[The_Matrix]

With regard to the problem of cloning, I link a part of the documentation. . .
I didn't have any comfort in testing.
- in the import main dialog pick add assembly and then the model part.
- in main pick add part and add the drawing part
- on the numbering tab select 'username' and then press 'exceptions'
- pick the model part and ok the dialog.
- give it a name and use the mouse to copy the name. set the rev and ok the dialog ok the attributes dialog
- on the numbering tab select 'username' and then press 'exceptions'
- select the drawing and ok the dialog
- paste the name of the model in the name
- set the type to 'specification and give the specification a name.
- ok the dialog.
- on the main tab press execute without checking dry run.

 

[alulecia]

Good evening to all

Thanks for the answers.

to respond to "ceschi1959" I would like to invite everyone to use the clone command for which there is no management (plm that is) as unlike the save as keeps the associated tables and allows to change the name (soever as the save as) to all the files that you want to pull into play.

the save as works well when in the same prt is built both 3d and 2d.

I did several tests and with the clone command I managed to get what I wanted.
I try to explain myself better with an example:

in general on the plm the management of the 3d and of the 2d is associated with each component two files with almost equal names (usually same numerical and sigle to differentiate them type 1_cad and 1_drw) and in the same way if it is axiemi ....to which are associated progressive revision numbers that can change according to the requirements for all or only for gaps of the components.

to make a haze

1_cad file (3d of a wheel)
file 1_drw -----> assembly reading file 1_cad ------> on this file is produced the 2d of the wheel 3d

file 2_cad------> 3d of wheel circle 1 (no 2d required)

file 4_cad------> assembly content different 1_cad and 2_cad
file 4_drw------>assembly content with file 4 (soever all 3d ) on which I produce its 2d


So I have the 4-drw which is an assembly that reads all files less than 1_drw

the clone command allows in only operation to change all the names to the files in play with 4_drw , then to carry out the revision indices without altering ties and association of the board.

and now I have discovered that if in the same cloning operation of the 4_drw I also add the 1_drw I can with a single operation clone all the files that interest me.

with the only save as I could not do it: I would need to save as different and distinct more different replace in assembly that would lead to losing bond relationships and board associations.

the clone command then has very useful options that allow automatically to exclude components from the operation or to replace them with others.

try to believe... it is very useful

I doubted my 1) question somehow managed to answer me.


I haven't been able to answer the question two yet:
the option allowed replacement of load options does not work.

in version 8 it didn't happen but comparing the settings of the two versions I couldn't find the differences,
unless it is an evolution of the version and that there is nothing to do.

I hope someone finds the answer

thanks to all

 

[ceschi1959]

Good evening to all

Thanks for the answers.

to respond to "ceschi1959" I would like to invite everyone to use the clone command for which there is no management (plm that is) as unlike the save as keeps the associated tables and allows to change the name (soever as the save as) to all the files that you want to pull into play.

the save as works well when in the same prt is built both 3d and 2d.

I did several tests and with the clone command I managed to get what I wanted.
I try to explain myself better with an example:

in general on the plm the management of the 3d and of the 2d is associated with each component two files with almost equal names (usually same numerical and sigle to differentiate them type 1_cad and 1_drw) and in the same way if it is axiemi ....to which are associated progressive revision numbers that can change according to the requirements for all or only for gaps of the components.

to make a haze

1_cad file (3d of a wheel)
file 1_drw -----> assembly reading file 1_cad ------> on this file is produced the 2d of the wheel 3d

file 2_cad------> 3d of wheel circle 1 (no 2d required)

file 4_cad------> assembly content different 1_cad and 2_cad
file 4_drw------>assembly content with file 4 (soever all 3d ) on which I produce its 2d


So I have the 4-drw which is an assembly that reads all files less than 1_drw

the clone command allows in only operation to change all the names to the files in play with 4_drw , then to carry out the revision indices without altering ties and association of the board.

and now I have discovered that if in the same cloning operation of the 4_drw I also add the 1_drw I can with a single operation clone all the files that interest me.

with the only save as I could not do it: I would need to save as different and distinct more different replace in assembly that would lead to losing bond relationships and board associations.

the clone command then has very useful options that allow automatically to exclude components from the operation or to replace them with others.

try to believe... it is very useful

I doubted my 1) question somehow managed to answer me.


I haven't been able to answer the question two yet:
the option allowed replacement of load options does not work.

in version 8 it didn't happen but comparing the settings of the two versions I couldn't find the differences,
unless it is an evolution of the version and that there is nothing to do.

I hope someone finds the answer

thanks to all

clone command, with all its exceptions, has been working for at least 20 years (it has not changed since then!!!) and I repeat the concept that clone command is not used for a massive operation of save as, with boards included, but for other purposes. the first question I asked you, maybe it was wrong: the correct question is: what do you have to do? Why do you need to 'clonate' a set?
for the second question: It could be what the_matrix says, and in what case you get a message that says (memory vade) the part is not the original (or something similar), I find it more likely a speech of load options.

Hi.

 

[alulecia]

Good morning to all,

I didn't want to be presumptuous, on the contrary.

the need to clone a set with its boards comes from the fact that the advancement of the table revsion indices is also reflected in the file nomenclature: to make the save as of a table of a big set is easy but when besides the save as of the prt of the table I have to replace one or more components or change the names to all the composts of the axieme becomes complicated with the save as; even more if then the individual components soo in turn tied to the prts of their 2d, at that point with the saveas to me personally it is very difficult and I happened to make mistakes.

I take advantage of it to ask you also what is the correct use of the clone command.

for the second problem also I believe it is linked to the set of load options buta I still found the right one.

Thank you.

 

[ceschi1959]

Suppose you have a set with n models (single parts and/or subaxiemi) each of which associated with its drafting that can have any name (usually name-parte_dwg or name_parte_drf or whatever you want), how do you clone everything, parts, assemblies and subaxiemi while maintaining the same association (eventual links, assemblies and so on) sure you can do it with the clone assembly command but you have to do it more or less to set handle and load each single file... certainly not an error-proof procedure.
a 'correct' use of commands does not exist in my opinion: a command you can use it as you want if you reach the desired result in the desired time.
last, also the load options: indicates which you used.

Hi.

 

[The_Matrix]

Actually I use clone command just for the reasons that list @alulecia.
I have an assembly with certain components and want to make a new product keeping 90% of the same, making some from scratch and others as revision ....
I always have the perfect command.

ps. the clone command remade it in nx10. (if I don't remember badly)

 

[ceschi1959]

Actually I use clone command just for the reasons that list @alulecia.
I have an assembly with certain components and want to make a new product keeping 90% of the same, making some from scratch and others as revision ....
I always have the perfect command.

ps. the clone command remade it in nx10. (if I don't remember badly)

hi beppe, I didn't see the command in nx10 so on this heel. I also use clone for the same reasons. but how do you do the tables? That's the question if I don't go out.

 

[The_Matrix]

hi beppe, I didn't see the command in nx10 so on this heel. I also use clone for the same reasons. but how do you do the tables? That's the question if I don't go out.

I don't make the boards. :biggrin:
So I auto-solve the problem.

 

[ceschi1959]

I don't make the boards. :biggrin:
So I auto-solve the problem.

but vaffe.... :wink: and I who did not sleep at night!

 

[Claudio M]

Hello everyone

I do not have Moldovawizard (nx7.5) use clone command massively with tablets included. for the selection I solved creating a set containing the 3d axieme and all the tables.
in the command clone seleziono add together (use it in Italian) and select a single file.

 

[ciciu]

with multiple 2d boards in master model and a 2d set of the same files, I use the clone first on the single boards, then I delete the prts of the new 3d created (because children of the 2d) then clone the axieme 2d
so doing in the same folder I have all clones and single boards find ex novo 3d elements