blocked movements in assemblies

[exxon]

when you leave constraints free in a set, you can try the movements, this is one of the strengths of the modelers and we exploit it all.

If you have a set (.iam) formed by yourself parts (.ipt), there are no problems, but when in a set you enter another set, the movements of this sub-assieme are blocked.

so far I have simulated the movements always at the level of the general axieme (for example by inserting a pneumatic actuator like two separate parts, body and rod). now, however, having need to generate the material list, this system creates problems, showing me two parts (the body and the auction, in fact) where in reality the part is unique (the actuator).

It seems strange to me that there is this limitation and certainly the problem is due to my poor knowledge of the program. Can anyone help me?

 

[mula]

you must make the axieme (cylinder) flexible: dx button on the half-aisle of the flexible selection window. . .
so also applies to the assemblies that you create in other assemblies.. .
to the cylinder for example put the pin/hole constraint inserting also the min/max limits, so the cylinder does exactly the stroke...
Try!
Hi.

 

[stefanobruno]

the cylinder must be an iam with the constraints as it says mule or as you will see in the attached file.
for the material list, the cylinder assembly must be "inseparable " and the two components " normal ".

 

[exxon]

Thank you!

for constraints, limits, and inseparability was already clear. what was missing was just the check on flexibility.

very kind and very fast!

 

[exxon]

I add a question related to the previous one.

when assemblies are a single mechanical component (as is in the case of the pneumatic actuator of the previous example), in the component list you mark the sets as "inseparable" on the first page, so in the other two you see as a single object.

when the component used is however a library file, on the first page of the component list appears as unchangeable, with the inherited property (in some way) from its same file.

how do you define the "inseparable" parameter at the library assembly level, so that it remains such when that detail is used in all other assemblies?

 

[exxon]

In the meantime, I found it.

to those interested:

tool/options/document settings/bill of materials/default bom structure

(I'm sure they couldn't hide it better... )