Subsequent [draft] tables different from together

[cacciatorino]

I would like to do this:

In a draft, I have the table of a set including several sub-axis. then I realized a first view with the complete axieme and its table with subgroups non Expulsive.

I then made other views for each subgroup, but I generated by putting on the table the main axieme and not ciascu subgroup, then hiding what I don't need, but showing the frame of the machine to facilitate the assembly operation to the assemblers ("show as reference").

for each of these detailed views, I generated the list table parts, but the problem is that when I go to break it to delete from the list the hidden parts and explode the subgroup that interests me, these changes are also reported on the first table, the one generated for the main axieme, which I would instead leave at the first level, without any explosion.

Is there a method of solving the problem without creating false fictitious assemblies?

 

[vespa_83]

we having faced this problem 2 years ago, and having not found the solution, I convinced the office with an analysis of feasibility, times and costs, not to explode the subasms.
that is, everything becomes fragmented but eventually also + ordered:
each code has its own table, every table only a list.
the number of drawings you have to do is always the same, just do multiple dft files.

 

[radio]

Is there a method of solving the problem without creating false fictitious assemblies?

the only system I found, but it is horrible, is to transform as text the table "partial"; in practice you create the view table that interests you with included only the components you want and then use the command "transform as text".
Bye.

 

[cacciatorino]

Hey, guys and radio,
I finally "resolved" putting on the table the only subgroup concerned, and then I made another table of the rest of the car without that group and put it under.... now I just have to remember that if I have to move them I have to procure them both!

 

[brex]

I also solved it as a hunter. But it would be something to ask if... If I have different tables on the same dft, I need that there is no interaction between the same.. .

 

[Focus]

you could insert the axis you want to be referenced and "seal" with the properties occurrence, so that it becomes reference in the draft but does not end in the main axieme or in separate (in your case the frame).


Hi.

 

[cacciatorino]

you could insert the axis you want to be referenced and "seal" with the properties occurrence, so that it becomes reference in the draft but does not end in the main axieme or in separate (in your case the frame).


Hi.

I'm not sure I understand what you mean.

My problem was having two views of the same together in one draft, and the table referring to each of them exploded differently. It seems that this is not possible.

 

[Tequila]

I'm not sure I understand what you mean.

My problem was having two views of the same together in one draft, and the table referring to each of them exploded differently. It seems that this is not possible.

It is not possible, I had your same problem years ago, I had to solve by doing more functional tables, complete set on a table that listed the various subaxes and then the subaxis tables with their complete table.

 

[Focus]

Unfortunately not only very good, to express myself or to write Italian :smile:
However, returning to the problem I suggest you to put in the draft not always the main aid, but the main aid and subgroups, inserting within the subgroups the parts or assemblies you want to display as reference and make sure that the references do not appear separately (through the properties occurrence), in this way the list tables parts should remain disconnected.

Hi.

 

[Marco74]

but if you create a dft like the example image I posted you can't make a component table for each set?

 

[cacciatorino]

Unfortunately not only very good, to express myself or to write Italian :smile:
However, returning to the problem I suggest you to put in the draft not always the main aid, but the main aid and subgroups, inserting within the subgroups the parts or assemblies you want to display as reference and make sure that the references do not appear separately (through the properties occurrence), in this way the list tables parts should remain disconnected.

Hi.

Now I understand, you told me to enter the subaxieme also the frame with the clause "hide in the upper level".

But it's a good job.

 

[cacciatorino]

but if you create a dft like the example image I posted you can't make a component table for each set?

Yes, but I would like to show in the view of the subaxieme also the frame of the machine (show as reference) that is not contained in the subaxieme.

 

[Focus]

I and my colleagues use this system directly in the design phase, in the end without extending the time we find ourselves with the "references" already present in the sub-axis, doing it back is definitely a good job.

Hi.

 

[cacciatorino]

found the solution, thanks to the response of a user on the American forum.

That's what it is.

1) put the first view on the table
2) create the table parts by dividing the "connect in active" box
3) dismantle the table as needed

4) put on the table the second view
5) hide/show what you need
6) create the table parts by dividing the "connect in active" box
7) right click on the table --> enable
8) Expand the table: changes will not be reflected on the table of the first view.

9) if I have to change options on one of the two tables, always remember to make "dx key on the table --> enabled" on the table you want to change.

 

[Calsifer]

Caccatorino, tomorrow I try, if it works with my version of solid edge you are a great...:biggrin::finger:



hi, I'm new to the forum, I'm a designer (if I can cut this title) for 4 years who's been cuffing a thousand with the solid edge drafts for explosives, manuals, etc.... I currently use version 19, I hope to move early to st2...