joint parts in different assemblies

[genesis1975]

hi to everyone, I'm new in the forum, this is my first discussion.
I use solidworks for a year and a half, so I have a still limited experience...I still use the 2012 version, so my question could be influenced by the dated version. .I am a little firm on work because of the question that I will tell you...I did not find anyone who knows how to do...I created various assemblies with many parts in common and I gave them names that are a little short description...I made each together a pack and go with suffix so they are assemblies to stagnants; Now I would like to go to a more open vision, having come the time to replace the old names with codes for each part, i.e. I would like the many parts in common that will have the same code are connected to each other, i.e. if I change a part in a set, I also change the equal parts in the other assemblies...how can I do this? Thank you for the answer

 

[MassiVonWeizen]

the version has no relevance. that is 2012 or 2019.
if you have made pack&go with suffixes, but you have not modified what are common parts is a situation, if instead you have made the pack&go but then suffix 1 has a change, suffix 2 another the situation is quite different and practically unresolvable.

other thing to know is if you have references between these parts. and by reference I mean sketches, functions, variables... .

if the situation is the simple one in which the parties have not undergone changes and there are no external references that have undergone modifications of the procedure to be done is this:
keep the file open to replace
open the axieme with the part to replace
select the part to replace
menu file> replace components
in the property manager, having opened the master file, should already appear everything set. if so it wasn't and in the pane with this blank was select browse and go look for the affected file
repeat n thousand times for n thousand assemblies
from the online guidehttp://help.solidworks.com/2012/ita...ks/hidd_dve_replace_comps.htm?verredirect=1=1

 

[genesis1975]

but, given my little experience, I didn't understand much....they are cinematisms, mechanisms for sofa-beds, formed by so many infulcrate levers of which I made the historian going to detect the measurements of each lever with ruler and caliber, but then I don't guarantee that I didn't come back on, to correct the measures and improve the design... but I changed the measures in a part of a joint but I didn't understand the other part. . .

 

[MassiVonWeizen]

I'm trying to make it simple. . .
you have a part that will be used on multiple assemblies
so far you have worked doing this part to various copies calling them a1,a2,a3.... .
If all these copies are always the same you can replace them with the part quite easily.
If these copies are no longer the same then replace them, but you will find yourself with a false set.
It goes without saying that there must be only one part shared by more assemblies and not n copies of the same part for n assiemi

if after a year and a half using the program you still don't know what references are between the files I recommend you to do the internal tutorials. From what you write, you seem to miss the basics

 

[genesis1975]

Okay thank you, but to rename the use files pack and go or solidworks explorer....in any case I have to resign myself to having closed assemblies, ponds... is it serious?

 

[genesis1975]

I tried with small assemblies to test with sw rename, I was entitled to rename a part in common but it was not so...

 

[genesis1975]

I imagine why the equal parts have already lost the references... to keep them what they have to do and especially not to do?

 

[genesis1975]

in any case the pack and go also of equal parts does lose the links between the parts always or only with the suffix?

 

[MassiVonWeizen]

Okay thank you, but to rename the use files pack and go or solidworks explorer....in any case I have to resign myself to having closed assemblies, ponds... is it serious?

you need to plan your job well and manage files. the pack$go and rename are fine, but make copies of assemblies only because it changes a part or assembles the parts differently leads to confusion.

I tried with small assemblies to test with sw rename, I was entitled to rename a part in common but it was not so...

You have to understand what you mean by part in common.
that you have 10 equal files that are called to and reside the 10 different folders is not having a common file; the file must be one only and all the axioms that use the part to refer to u no only.

I imagine why the equal parts had already lost the references... to keep them what to do and above all not to do?

for references the sharing of function, sketches, equations that connects one file to another. if I do a sketch on the part by binding it to the geometry of the part b this sketch will only work if I maintain the reference between a and b. by making the pack&go of the only part to solidworks recognizes this reference and also includes the part b. these references if they are lost or interrupted are difficult to recover
Is that what you mean by references?

in any case the pack and go also of equal parts does lose the links between the parts always or only with the suffix?

I don't know what you mean.

in my opinion you have to do an analysis of the organizational structure of your storage system.
define which parts will be, or assign if you have subaxis that you use on multiple jobs, used in multiple assemblies
define how to manage these parts: make a folder dedicated to shared parts, leave the shared parts in the folder of the first job that use it
have always and only a side file or together if this is shared.

done this you can start fixing the modeling.
a method to replace files is what I explained in the first post (this method works independently from the file name and I can replace the part to with the k part which is completely different)
another is to delete all parts except one that will be loaded by all the assemblies that contain it. as solidworks, if you find an open file with the same name as a content in a set, from priority to this it is enough to keep the part open to share to replace it automatically. (this method implies that within the axieme there is a part that is called as the shared one; if you have side files with suffixes you have to rename them otherwise it does not work. )

 

[genesis1975]

At this point I wonder if it is the case of putting me in the company immediately of the parts in common with substitution and so on or in the meantime rename and see if it can be good like this, i.e. without links between the parts in common, i.e. to stagnant compartments. I agree that if I put myself in the enterprise I have to choose a single file to replace with that provided that, but after the pack and go you do not delete the link with the equal part of the other set...that is, it is not also what makes me the set closed.

 

[MassiVonWeizen]

I agree that if I put myself in the enterprise I have to choose a single file to replace with that provided that, but after the pack and go I do not cancel the connection with the equal part of the other together

What does that have to do with it? you know you make a pack&go do that single together or part or drawing; if one part is used by another together, the latter is not involved in the pack&go. pack&go makes copies of files, does not transfer or delete them

That's not what makes me the whole thing closed.

bho... I don't understand what you mean. if a system is closed (does not share files?) or open (shares files?) depends on how you impose modeling.
I'm sure you're using the pack&go as a super bowl hazelnut and I think you're looking for the scapegoat for confusing file management.

What do you say, while I could just rename the files?

You're the one who needs to understand how to handle the situation based on how you work.
you can also just rename files and have 20 parts to in your database if this method is functional at work.

 

[genesis1975]

no, I meant that if I make a pack and go for each different set, and I have parts in common in each set, if I change a part in common, it continues to change the other correspondent in the other assemblies... I think, unless I put a suffix and then it doesn't change anymore... that's how it works, right?

 

[genesis1975]

I mean, as a whole, that if there are some parts in common between the axioms, showing a common part in a whole, the change does not extend the other axioms. ..however I do not have 20 parts called to a set, I only have one...

 

[genesis1975]

Maybe I have another part to another together, but I called b, and from here the problem

 

[MassiVonWeizen]

no, I meant that if I make a pack and go for each different set, and I have parts in common in each set, if I change a part in common, it continues to change the other correspondent in the other assemblies... I think, unless I put a suffix and then it doesn't change anymore... that's how it works, right?

only if in the pack&go do not insert the common part.
a shared part, common is a wrong term, must be one and only file, I have already said it. but you keep thinking that as you have ten files that are called changing one will change the others too... It's not like that. if you have ten side files in yellow color and at one change the red color you will have 9+1 side files to.

I mean, as a whole, that if there are some parts in common between the axioms, showing a common part in a whole, the change does not extend the other axioms. ..however I do not have 20 parts called to a set, I only have one...

That's what I said. if you change a shared part all the collection they contain will change. but in your archive works must exist only, and I repeat only, a part that is called a.
I didn't talk about 20 parts in a set, but in a database or if you prefer to call it " folder where I have work files."

Maybe I have another part to another together, but I called b, and from here the problem

if you have a part called b is a dverse file from what is called a.

That's how it works, right?

look to be sketched is better if you take a course of a couple of days because from what you write gives the impression that you have no idea how a parametric cad works.

 

[MassiVonWeizen]

here is a pattern of file operation

 

[genesis1975]

Well, we didn't understand much, I know that if I rename a file, even if the content is equal, it becomes another file, which is not shared, as you say.
then the file I have to share with others I have to leave it out of the pack and go? So it's like he's out of the house together.

 

[MassiVonWeizen]

then the file I have to share with others I have to leave it out of the pack and go? So it's like he's out of the house together.

Wrong. the files contained in the axieme is not deleted, suspended or anything else, simply the sharing one will be loaded.
the pack&go is simply handling (copy or displacement) files regarding a particular set, part or design. but you talk about the files within the windows folders and do not change the internal content of the modeling files. a set containing 10 parts when the pack&go is made, and of those 10 parts exclude 2, at the opening will always have 10 parts of which 8 in the folder where the pack&go and 2 was made in the original folder

 

[genesis1975]

So if the pack and go does a copy of the parts, you have to leave out the shared part because if not it would become another file to all effects other than that of the other assemblies... I ask a last question, but in the pack and go how to exclude for example a component?I usually open the whole axieme and I make copy of everything. . .

 

[MassiVonWeizen]

in the box of the pack&go left there are the spunte i components included. by default they are all activated, but just turn them off manually.