practical advice creation of large assemblies.

[New Rider]

Thank you guys for the attention. Thanks kakisan of the example (just a second I look at it )
But I wanted to understand... We talked about axioms and axioms. the main idea is to group more components in an orderly manner to facilitate the identification.
what you advise in a proportionate way is to work with more sub-axis or try to group by e.g. the vice, bearings, seggers, rings etc... in "folders".
for es = classic toothed wheel reference tree to be inserted in a very "macro" consisting of 2 supports, 2 bearings,2 segger,2 spacers and toothed wheel and tree. should you create a subset and call it (referral) in which it will be in the newly cited components and insert it into the "macro" or insert each component into the macro axieme and then move the components into your folders?

Thank you. .

p.s = recently in my personal pc I installed a ssd and from that point on the performance in terms of sw time is improved a lot. It is possible that slow coupling rather than difficulty opening files depend on the fact that all axioms and files are written on external servers (like a kind of lag? ).

 

[meccanicamg]

no I also use faces; but everything starts from the plans or better if I can first use the plans then the faces or points etc.
- - - updated - - - -assembling and automation machines in general.... .

It seems a professional deformation of the sector, because unfortunately it is an area where changes are continuous and often necessary to change radically solution. it seems that fixing to the planes allows to diminish the geometry without losing consistency in the axieme.

 

[meccanicamg]

if you weigh from servers must have ultra-fast disks and the network must be 1gbit if not fiber optics. otherwise it changes little if you have a ssd or not on the pc....for loading I mean.

 

[tekno]

I'm also trying to do the most sub-assisted possible. while for trade as you behave if you have two stations in different directories and each has a subdir. Trade, e.g. station 1 in c\1\commercio and station 2 in c\2\commercio, in each trade there is a cylinder 3, when you go to make a macro set with stations 1 and 2 with cylinder 3 what happens having the same component in two different dir..
I hope I explained.

while other problem already asked a long time ago and I found no solution.
working on the server the loading via network is obviously slow, to avoid the problem shifting the whole machine on the premises but, when I open it some components always go fishing from the server even if they are all within the working directory that is located on the premises. This happens even if I move it with the pack and go, I must always rename the directory on the server so as not to let it find.
with the 2009 version this did not happen, for us this is a big problem.

 

[Max-C]

I'm also trying to do the most sub-assisted possible. while for trade as you behave if you have two stations in different directories and each has a subdir. Trade, e.g. station 1 in c\1\commercio and station 2 in c\2\commercio, in each trade there is a cylinder 3, when you go to make a macro set with stations 1 and 2 with cylinder 3 what happens having the same component in two different dir..
I hope I explained.

while other problem already asked a long time ago and I found no solution.
working on the server the loading via network is obviously slow, to avoid the problem shifting the whole machine on the premises but, when I open it some components always go fishing from the server even if they are all within the working directory that is located on the premises. This happens even if I move it with the pack and go, I must always rename the directory on the server so as not to let it find.
with the 2009 version this did not happen, for us this is a big problem.

I didn't understand much.
I use the various subaxial configurations with actuators as I give for useless the phase of shifting the stem.

if with 2009 it did not happen the problem can be given by various factors. for this kind of problem I recommend assistance.. .

 

[Kakisan]

Thank you guys for the attention. Thanks kakisan of the example (just a second I look at it )
But I wanted to understand... We talked about axioms and axioms. the main idea is to group more components in an orderly manner to facilitate the identification.
what you advise in a proportionate way is to work with more sub-axis or try to group by e.g. the vice, bearings, seggers, rings etc... in "folders".
for es = classic toothed wheel reference tree to be inserted in a very "macro" consisting of 2 supports, 2 bearings,2 segger,2 spacers and toothed wheel and tree. should you create a subset and call it (referral) in which it will be in the newly cited components and insert it into the "macro" or insert each component into the macro axieme and then move the components into your folders?

folders do not serve anything from a performance point of view.
they order the tree together, but they don't speed it up.

 

[tekno]

I didn't understand much.
I use the various subaxial configurations with actuators as I give for useless the phase of shifting the stem.

I realize it's not easy.
I try to explain:
I have two stations in different folders, these stations use e.g. a stool cylinder ø50x200, in each folder there is this cylinder.
when I go to create a general set with these stations, swx finds the same cylinder in two different folders, sometimes not knowing which of the two take suspends the components.

 

[Kakisan]

I realize it's not easy.
I try to explain:
I have two stations in different folders, these stations use e.g. a stool cylinder ø50x200, in each folder there is this cylinder.
when I go to create a general set with these stations, swx finds the same cylinder in two different folders, sometimes not knowing which of the two take suspends the components.

Hi.
I think what you wrote could be considered heresy by more than 99% of the forum.
If you have a model, used equal on two axioms you do not have to duplicate it, you have to create a specific folder for shared components on multiple axioms.
How do you do with the vice?

 

[tekno]

I fully agree with what you say, in fact time ago you worked so, we had and we still have a folder with all the trade where each station went to fish the component, but unfortunately we work with external customers to which we have to deliver the finished job, for a fact of order to me it does not go to make a pack and go of the folder flattening it, and in addition my boss has a laptop where to the need copy the works and if you do not miss the whole folder.
over time we had to pass to this, if not logical, solution.
the same speech for the customer, if we had to give a pack and go flattened of a station, and between 6 mei must set up a new line with an existing station and a new one would be in the same situation and we can not go to the customer to say how to manage the works in his house.

 

[Kakisan]

Why do you flatten the folder?
Keep the structure... it seems to me that you do everything to complicate your life.

 

[tekno]

I know that I may not flatten the folder, but in this case it would create a structure with external folders that the customer does not use.

x:\machine
x:\sw-parts (with trade)
x:\solidworks date (the customer may have date(1) or date(2) etc..
x:\equipped

While the toolbox for the viteria has abandoned it, it is an unusable thing, it weighs in an absurd way all the assemblies, we use our specially created wine library.

 

[Kakisan]

I know that I may not flatten the folder, but in this case it would create a structure with external folders that the customer does not use.

x:\machine
x:\sw-parts (with trade)
x:\solidworks date (the customer may have date(1) or date(2) etc..
x:\equipped

While the toolbox for the viteria has abandoned it, it is an unusable thing, it weighs in an absurd way all the assemblies, we use our specially created wine library.

Okay.
but clonate every time all the screws you use?

 

[tekno]

Unfortunately, yes, we say that the one and the men of the evils, a caterpillar a washer and a vasation.

 

[Kakisan]

then fasteners used them as a part family that has all possible configurations inside.
the commercials instead duplicate them for each subgroup. . .
to me the system does not like and, as you have already experienced, you create conflicts.. .
So on two feet though I don't have a solution to your problem... did you try to ask for assistance?

 

[Max-C]

then fasteners used them as a part family that has all possible configurations inside.
the commercials instead duplicate them for each subgroup. . .
to me the system does not like and, as you have already experienced, you create conflicts.. .
So on two feet though I don't have a solution to your problem... did you try to ask for assistance?

I have the length commercial bars from the seller. Copio in my project->"cut" the useful lengths as configurations.
at the end of the pack and go project... How would you handle these things?
for example if they sold you polyethylene bars (or hiwin guides) from 2000 mm and then every time you have to make new cuts?

 

[teseo]

Sorry, but I disagree; the pack and go creates an exact double that is independent of the customer structure, stands alone not in need of anything, and made to mail....so if I were you I would make a pack and go as kakisan says without flattening the structure and you solved your problems.
the customer does not notice anything will have a folder that will call itself as your project and inside the whole project with its folders.

and then give a customer a native well that's how to say...... I would never give it.... then it depends on the situations though....


Hi.

 

[Max-C]

Sorry, but I disagree; the pack and go creates an exact double that is independent of the customer structure, stands alone not in need of anything, and made to mail....so if I were you I would make a pack and go as kakisan says without flattening the structure and you solved your problems.
the customer does not notice anything will have a folder that will call itself as your project and inside the whole project with its folders.

and then give a customer a native well that's how to say...... I would never give it.... then it depends on the situations though....


Hi.

I don't give the projects to customers. I do pack and go to have backups...

 

[Kakisan]

I have the length commercial bars from the seller. Copio in my project->"cut" the useful lengths as configurations.
at the end of the pack and go project... How would you handle these things?
for example if they sold you polyethylene bars (or hiwin guides) from 2000 mm and then every time you have to make new cuts?

Here you enter a minefield.
the management of the commercial details to "meter" has always been complex.
You could model the purchased part and create a set of internal configurations, or cut together. . .
the problem is, however, linked to how you want to see the distinct cad, pdm, erp...
we have this problem on the ropes or.
We import a concise of 5mm long or every meter of rope we use, then we modleliamo all the ropes or on a part of support that will not go separately, but will go so many meters as we have been inserted.

 

[tekno]

In fact, as I teseo says, if I give the project with pack and go with its subfolders and the trade is in the business folder, when this customer or even I, within six months must assemble a line with inside two different projects and these have the same business folder and inside one component but with a different root what happens?

 

[tekno]

Here you enter a minefield.
the management of the commercial details to "meter" has always been complex.
You could model the purchased part and create a set of internal configurations, or cut together. . .
the problem is, however, linked to how you want to see the distinct cad, pdm, erp...
we have this problem on the ropes or.
We import a concise of 5mm long or every meter of rope we use, then we modleliamo all the ropes or on a part of support that will not go separately, but will go so many meters as we have been inserted.

but in this case you would have rope or with different configurations but the name of the part is always that, as happens with the vines.