axious versions

[TECNOMODEL]

Good morning.
I need a suggestion.

I have a set of a product that will have 2 versions depending on the tree you mount.

Is it better to use visual representations or detail levels in my set?

in short, create 2 views or 2 levels of detail?

naturally taking into account that then everything has to be put on the table with its distinct components.

Thank you.

 

[MauroM]

The subject was dealt with in this debate.http://www.cad3d.it/forum1/threads/...i-non-visualizzare-nelle-tabelle-delle-tavole

 

[TECNOMODEL]

Yes, I had followed that discussion.

But there is no clear answer to my question.

which of the 2 tools is more suitable to create different configurations of a set in which only some parts are different?

 

[MauroM]

on the graphic level are suitable both, the trouble is the distinct components in the table that does not take into account the elements that are rendered invisible or suppressed, inventor always counts everything in memory.

 

[TECNOMODEL]

on the graphic level are suitable both, the trouble is the distinct components in the table that does not take into account the elements that are rendered invisible or suppressed, inventor always counts everything in memory.

So doing the 2 versions with one or other tool is indifferent?

 

[MauroM]

I still prefer the levels of detail because at least they download a little memory.

 

[TECNOMODEL]

I don't know what, but I'm definitely wrong.

I have some visual representations, in 2 of them I did copy in detail.
But now to have a correct visualization I have to activate both the view and the level of detail.

How do you usually do?
I should like to say that you have to start creating a level of detail right away, before entering the first part.
otherwise you will see various pieces together when you activate the master view and do not change by activating a level of detail or the other... .

 

[TECNOMODEL]

Helpful.

in a group where I had already created some visual representations I created a new one.

suppressing a component automatically creates a level of detail when I created others did not.

I've got to go change the level of detail.

Where's the mistake?

 

[MauroM]

Forget about the views for a moment, work only with the levels of detail "by suppressing or not suppressing" what you want.

 

[pagnotz]

However, the representations serve to create multiple preset views or positions, to hide, suppress or display components quickly, not to manage multiple versions of a set that have different parts within them.
If I'm not mistaken, it would be iassembly. However, even very simply, once you create a version of the axieme, you save a copy with other name where you go to replace the parts that vary (the tree in your case). the only "sadvantage" is that, if you replace on a set a part that all variants have in common, you must remember to do so on all others because it will not happen automatically. However in the case of two versions, it is not a big problem.

 

[Tarkus]

:finger:quote

 

[TECNOMODEL]

However, the representations serve to create multiple preset views or positions, to hide, suppress or display components quickly, not to manage multiple versions of a set that have different parts within them.
If I'm not mistaken, it would be iassembly. However, even very simply, once you create a version of the axieme, you save a copy with other name where you go to replace the parts that vary (the tree in your case). the only "sadvantage" is that, if you replace on a set a part that all variants have in common, you must remember to do so on all others because it will not happen automatically. However in the case of two versions, it is not a big problem.

I agree with you, also because each version will have a different code so I am obliged to do so.
the representations I am using now that I am still studying the project and the coding has not yet been made.

 

[Zac69]

Hi, definitely in your case an iassembly. In theory it's like making a new view, but the iassembly makes you the right distinct.
Good day