assembly configurations

[cacciatorino]

it would be convenient to have a subaxieme in two configurations, to be able to load one in a parent set in "a" configuration, and another parent set in "b" configuration.

I make an example:

I and my colleague are working on different machines, but they share a subaxieme, subaxieme that would be identical on the two machines except for the fact that in my vendor list there are the cracked cylinders, and in its smc cylinders. we created two identical groups but as different files.
the problem is that we are still in the design phase with continuous modifications, so we lose a lot of time repeating the changes on the two groups, identical to less than the cylinders.

Wouldn't it be possible to work on a single set, so as to have the automatic propagation of the changes, and tell osd to charge it in "festo" mode for the "a" machine, and in "smc" mode for the "b" machine?

 

[Er Presidente]

it would be convenient to have a subaxieme in two configurations, to be able to load one in a parent set in "a" configuration, and another parent set in "b" configuration.

I make an example:

I and my colleague are working on different machines, but they share a subaxieme, subaxieme that would be identical on the two machines except for the fact that in my vendor list there are the cracked cylinders, and in its smc cylinders. we created two identical groups but as different files.
the problem is that we are still in the design phase with continuous modifications, so we lose a lot of time repeating the changes on the two groups, identical to less than the cylinders.

Wouldn't it be possible to work on a single set, so as to have the automatic propagation of the changes, and tell osd to charge it in "festo" mode for the "a" machine, and in "smc" mode for the "b" machine?

would be a variant to the problem of "save by name"?

I've been "holding your eye" for a while, but I'm still not sure if I have to turn on the club or not.
:smile:
If the two groups use identical parts, these must be shared and will change together.
structure more the large group and tries to have changes on "simple" subgroups, so that the whole machine is shared.

two subgroups, one shared with everything that does not change, one with what changes.

But how do you save? with mm? or "hand"?

 

[cacciatorino]

would be a variant to the problem of "save by name"?

I've been "holding your eye" for a while, but I'm still not sure if I have to turn on the club or not.
:smile:
If the two groups use identical parts, these must be shared and will change together.
structure more the large group and tries to have changes on "simple" subgroups, so that the whole machine is shared.

two subgroups, one shared with everything that does not change, one with what changes.

But how do you save? with mm? or "hand"?

No, "Save with Nom" and it's another problem... .

Except with mm, even if I can take a coffee break every time....
Sometimes I'd be tempted to save locally in 3d-data and then upload from there and save on the pdm only when I'm done, but I'm afraid it explodes the whole company... .

I would say that making the assembly even more granular than that is impossible, we have come to groups of 3-4 components...

the solution would have been to tell the customer smc that for now the machine we had to see it with festo, except to change all cylinders at the end of the design, but did not want..... :biggrin:

ah, today as I expected to load the axieme I gave a read to those old discussions about id etc. etc. I didn't understand anything, but it's very interesting! :tongue:
One thing I didn't understand is when you say the id is unique (and in fact it is generated by mm with px#################################################################################################################################################################################################################################### but what if another cocreate designer sends me a project that randomly has equal id parts even if related to different geometries? I think the id is unique until I stay inside the same sql server.
or mm has an algorithm for which it associates a random and unrepeatable string to each part created?

a

 

[Er Presidente]

No, "Save with Nom" and it's another problem... .

Except with mm, even if I can take a coffee break every time....
Sometimes I'd be tempted to save locally in 3d-data and then upload from there and save on the pdm only when I'm done, but I'm afraid it explodes the whole company... .

I would say that making the assembly even more granular than that is impossible, we have come to groups of 3-4 components...

the solution would have been to tell the customer smc that for now the machine we had to see it with festo, except to change all cylinders at the end of the design, but did not want..... :biggrin:

ah, today as I expected to load the axieme I gave a read to those old discussions about id etc. etc. I didn't understand anything, but it's very interesting! :tongue:
One thing I didn't understand is when you say the id is unique (and in fact it is generated by mm with px#################################################################################################################################################################################################################################### but what if another cocreate designer sends me a project that randomly has equal id parts even if related to different geometries? I think the id is unique until I stay inside the same sql server.
or mm has an algorithm for which it associates a random and unrepeatable string to each part created?

a

much more simply osd uploads the first set and when charging the "alien" axieme, if it finds duplicates, it does not charge anything and shares a copy of what you already have in memory.
with mm loads a "version" and blocks it waiting for you to decide "who wins".
if you use version management you can do it without mm.

 

[Kaji]

If the two subgroups are, as the word same children of a parent, the same or different is not important, you can upload them into two "different configurations, even if in this case the word configuration is used to unproposed, thanks to selective instances.
the only thing that gets hurt is to load two shared groups "out of everything" so in this case you can not have them mounted differently without making conflicts with versions etc.

 

[cacciatorino]

If the two subgroups are, as the word same children of a parent, the same or different is not important, you can upload them into two "different configurations, even if in this case the word configuration is used to unproposed, thanks to selective instances.
the only thing that gets hurt is to load two shared groups "out of everything" so in this case you can not have them mounted differently without making conflicts with versions etc.

I'm studying this now. I had already looked at the help regarding these selective instances, but it seemed to me that it was related to the possibility of having a subaxieme shared several times inside the father, plus the possibility of having the underarms in a relative position different from each other. example: the classic shared pneumatic cylinder open or closed around the machine, but always as unique id.

so can I use selective instances also to have different components within shared subaxis?

 

[Kaji]

selective instances serve to have the parts mounted differently in two "shared" groups but the components must be the same.
once I realized I was in a situation in a group with selective instances there was an extra component, but I repeat the thing was not wanted and I found it by chance and I don't even know how I did it.
So I wouldn't want to waste your time trying to do something that isn't provided by the software.