tolerance between tables in family table

[Mauri:66]

Bye to all,
I have a rough model plus a configuration (table) of the work, the rough is connected to its technical table and the worked respectively to its.
until this is all clear, the problem arises when I have to change the quotas on the table of the work because having been created taking the table of the crude and renamed, at the moment of the modification single quota nothing happens while if I change or gate a quota with annexed a tolerance of position, it also cancels it in the drawing of the crude.
Is there a possibility to unleash the connection of position tolerances between the two drawings?

Thank you

 

[DANI-3D]

Hi, Mauri.

I don't know the solution to your problem, I hope others can help you.
However, I take advantage of this discussion to ask you, but in general, in the raw-finished management with family tables, how are you?
I use another method, I make a .asm where first I insert the crude and then I do the work, each of course has its .drw
I would like to compare the two methods to evaluate pros and cons

Thank you.

 

[mamobono]

.........

I would like to compare the two methods to evaluate pros and cons

Thank you.

Hi.
I instead create another part and amount the crude as inheritance so I proceed to work the piece and create the drw
even in this way everything remains tied
If the same crude work in a different way I proceed in the same way to create another part and amount as inheritance the crude etc.

How come you're using asm? You don't feel like you're missing some functions to work on the piece you'd have?

Hi.

 

[Parametric_Ozzy]

On the assumption that the best solution would be to use the inheritance function, which exists only if you own the advanced axiemic license, I say:
being run with family table, you can't get rid of his real father, so the tolerance and positioning references already created in the father can't just be eliminated, the only solution is to move from an intermediate axieme as dani-3d says, using the paste copy of the solid surface of the crude, at that point you can actually put new refs and do all the new work that needs the case.

If you manage it only with the family tables on the part level you don't come out anymore.

If you have so many such cases I highly recommend you to evaluate the option of buying the license, which serves this but to many other things.

I hope I've been clear

greetings

 

[DANI-3D]

I use a .asm because most times the raw pieces are already carpentry assemblies.

but your method

I instead create another part and amount the crude as inheritance so I proceed to work the piece and create the drw

is it also applicable to these?

 

[Mauri:66]

the answer to my discussion I found it and as usual it was easier than expected, in practice it is to delete the quotas from the worked drw through the right mouse button deletes and not with the keyboard button or with the right mouse button deletes.
I performed the work through the family table so as to have a general control of every single workmanship, which in case it no longer needed in the future, just the release from the derivative. I think it's just a subjective choice of how you want to set the job. definitely also the system with asm is fine, many customers ns. use it.

hello and thank you all

 

[mamobono]

I use a .asm because most times the raw pieces are already carpentry assemblies.

but your method

is it also applicable to these?

it is because the parts insert them as in a set placing them with the usual allline constraints etc.
in practice you create a set in a prt file

Hi.

 

[DANI-3D]

interesante.

you would be so kind to detail the various steps, because it is a method I do not know.

 

[Parametric_Ozzy]

interesante.

you would be so kind to detail the various steps, because it is a method I do not know.

I repeat that this method is the best but it only works if you own aax license... otherwise it is worth trying, the function is not active.

 

[DANI-3D]

ozzy excuse, but the inheritance function is what is activated by doing:
insert > shared data > union/heritance ?
If that's it, I got it.

 

[mamobono]

interesante.

you would be so kind to detail the various steps, because it is a method I do not know.

Hi.
I'm sorry, but I did a little rush.
of course by changing a part of the inheritance you change it also in the file in which it is brought

 

[DANI-3D]

Okay.
Clearly, I'm doing some evidence now.
Thank you.

 

[DANI-3D]

I did a set using the inheritance function, but there is a problem, the individual details that amount lose the original colors and assume all the same color making them little distinguishable between them.
Is there any parameter to set for them to retain their appearance?

Thank you.

 

[Parametric_Ozzy]

you don't have to do a set, that's exactly the advantage of inheritance, you need to enter shared data in part.

 

[DANI-3D]

oops

Sorry I explained badly, I meant that I created a .prt to make a carpentry with the inheritance function and then do the work.
However the problem of colors remains