lability of a set inserted in another set

[bruno85]

friendly users,
I ask you this problem that made me draw not a few blasphemies against solidworks.
I create a "pipe" set of parts. This provides for degrees of freedom, which I leave ocme such.
I put it in another "topolino" set. in the axieme mouse, it is fundamental that I pippo with serve that lability, to carry out the coupling between the general axieme pippo and the imported axieme mouse.

Specifically: I create a joint with the organs of a suspension. the main axieme of the vehicle is centered on the chassis, and there I assemble slowly the vehicle with the various assemblies. suspensions are connected to the frame by means of spherical joint heads, which I leave free to rotate to assemble them with suspension supports on the frame. When the axieme suspended in the vehicle, however, the spherical axle heads are blocked, making me impossible to coupling.

Could you help me with the problem of blocked spherical snodes (which instead should be free to move)?

for now I have solved by assembling all the mobile components in the main axieme, but it is absurd!

 

[re_solidworks]

friendly users,
I ask you this problem that made me draw not a few blasphemies against solidworks.
I create a "pipe" set of parts. This provides for degrees of freedom, which I leave ocme such.
I put it in another "topolino" set. in the axieme mouse, it is fundamental that I pippo with serve that lability, to carry out the coupling between the general axieme pippo and the imported axieme mouse.

Specifically: I create a joint with the organs of a suspension. the main axieme of the vehicle is centered on the chassis, and there I assemble slowly the vehicle with the various assemblies. suspensions are connected to the frame by means of spherical joint heads, which I leave free to rotate to assemble them with suspension supports on the frame. When the axieme suspended in the vehicle, however, the spherical axle heads are blocked, making me impossible to coupling.

Could you help me with the problem of blocked spherical snodes (which instead should be free to move)?

for now I have solved by assembling all the mobile components in the main axieme, but it is absurd!

in the main axieme you have to click with the dx the subaxieme and then check "flexible".

 

[bruno85]

in the main axieme you have to click with the dx the subaxieme and then check "flexible".

I'll be a little ignorant... but I can't find it! use sldwrks 2010 premium.

 

[bruno85]

Thank you so much re_solidworks!!!! ! ! !
thanks to you I solved the problem that had caused me more working days than necessary!! ! ! !

just for completeness, if someone had my own problem, I better describe what to do:
the subaxioms in larger axioms in solidworks are set up and treated ocme rigid bodies, and therefore all the lability present at the opening of the single subaxis are cancelled. But just click on the right mouse button on the subaxieme to make it labile again, click on component property, and, under "resolve component", check "flexible".

at the base of my dilemma is the wrong use of the word "flexible", I would have used labile! It's technically more correct!

 

[Mike1967]

Thank you so much re_solidworks!!!! ! ! !
thanks to you I solved the problem that had caused me more working days than necessary!! ! ! !

just for completeness, if someone had my own problem, I better describe what to do:
the subaxioms in larger axioms in solidworks are set up and treated ocme rigid bodies, and therefore all the lability present at the opening of the single subaxis are cancelled. But just click on the right mouse button on the subaxieme to make it labile again, click on component property, and, under "resolve component", check "flexible".

at the base of my dilemma is the wrong use of the word "flexible", I I would have used labile! is technically more correct!

Unfortunately, as in all the software translated, there are straphalcions
who really think if who translated it meant the sense
of a technical term of the original language.

 

[bruno85]

Unfortunately, as in all the software translated, there are straphalcions
who really think if who translated it meant the sense
of a technical term of the original language.

sisi, and also make it impossible to search "at attempts"! I would never have thought of looking flexible!!!

 

[re_solidworks]

I already tell you to pay attention if you have more instances of the same flexible subaxis active at the same time (also repeated) becauseswx suffers a little.
in the past I had solved I think creating + configurations, but often having more flexible instances creates problems in the axieme.

 

[SolidUser]

Unfortunately, as in all the software translated, there are straphalcions
who really think if who translated it meant the sense
of a technical term of the original language.

the command in English is 'flexible', so those who translated into Italian had to maintain a translation in tune with the original.

 

[Mike1967]

the command in English is 'flexible', so those who translated into Italian had to maintain a translation in tune with the original.

but in fact I meant that there is no need for a literal but technical translation.

 

[SolidUser]

but in fact I meant that there is no need for a literal but technical translation.

the translations follow common libraries, derived from the English ones.
it is not always easy to get rid of and I also remember that there is the help that if well done should follow the common libraries.
solidworks is translated into all languages of the world.
even if it was wrong, according to you, to reduce it after millions of users know this option as 'flexible', would not cause a bit of discomfort, just because a new and inexperienced sw user has struggled to find the command?
to me this translation has never created confusion.

 

[marcof]

sisi, and also make it impossible to search "at attempts"! I would never have thought of looking flexible!!!

Let's say that in the help part dedicated to "subassiemi" there are four or five voices, including "flexible syndromes". the attempts were not so many