I am using sw2010 2.1 and noticed that in an assembly that have few sub-assemblies included , only 1 sub-assembly is free to move with its mates ,althogh I made all needed sub's flexible .
for example : I have a door with 2 hinges and only 1 is working with its mates (and this is the same hinge multipled) , i am getting crazy from this .
any one have an idea?
Shay,
I seem to recall that you have to use different configurations for the subassemblies that you want to be flexible.That is, each flexible subassembly needs to be a different configuration from any other flexible or normal subassembly in the assembly. Since I'm not very sure about that, you might want to try searching this forum on "flexible subassembly configurations". Or just search on "flexible"; you're bound to find the answer in there somewhere!
Jerry Steiger
Yep Jerry's right. I found this out when flexible assemblies were first introduced (2001/2001+?) when dealing with linear slides in an assembly. You need a configuration for each instance of the sub-assembly you want flexible. ie Flex1, Flex2, Flex3......
Jerry ,
Thanks for your reply , I searched for some ideas under "flexible" etc' ,no sucess.
I will try to discribe the problem more clear .
in an assembly I normaly use stndard accesories/parts such as hinges,looks,door handles etc' which are built as an assemblies with its movments restrictions ,
however when I insert more then 1 item (hinge,look etc') as sub-assemblies and set all of their "solve as" to flexible, only 1 does realy become active ,all the rest remain rigid.
there isnt any configuration issue.
thanks
Here is a simple example of a pair of doors with a pair of flexible hinges. The requirement for all unique configs changed a few versions ago. I built this example on SW2009 SP5.1 and then also tried it on SW2010 SP3.0. I don't still have SW2010 SP 2.1 loaded so I can't test that version.
As you can see, the movable door is in fact, free to move by way of both instances of the same hinge subassy being flexible in the upper assy. Maybe you can look at this example and compare it to your model and figure out what's different. If not, post the models here and we can take a look.
WT
Wayne,
Thank you very much for the attached files , I made some tests with it and find out that the problem seems to be with the extreme sensativity of the SW2010 to file names with CAPS and/or foreign charecters .one extension of a part name was in Hebrew charecters.
I am using a non English native OS and some times I save some parts under files/libraries with capital letters or Hebrew charecters , I never had these problems with older versions 2007,2009 and eversince I installed the 2010 I incountered too many system crashes and strange unexplaned situations ( like the above ) that I didnt have any problems with it in the 2009 version.
The thing is that there is no error massage or any indication saying that file name is wrong .
I duplicated all my files and digged into every extension changing names to lower English charecters (imagine the time it cost me ,as I have thousands of files ).
I disscused these with our local support team and hope it will be fixed in the future (I don't have these kind of problems with any other softwere we use : AutoCad,Photoshop,etc')
Capital letters have never been a problem at our place that I know of, but with a different language version, strange things may happen. Where are you? Hebrew letters makes me suspect Israel. I wonder what would happen with your assy if it were opened in an English version - would it work fine? The answer to that may provide a clue.
WT
Hi Wayne,
yes you are right ,I am in Israel .
Normally with SW 2009 there wasnt any problem with files contained Hebrew charecters ,but with the 2010 it is unexpectedly crashes or behaving straingly .
few weeks ago I had a problem opening an assembly with PhotoView 360 ,and after digging for information in the forum ,i found one thread with the same problem and the solution suggested was look for capital letters in the file name / library .After checking it ,I found out that the library name was with a capital letter (I often use capital letters to make it easy to spot ),I changed the name to lower case letters and the file did opened perfectly.
I do have one computer running English XP OS and have the same problems.
First, flexible subs came out in 2005. I remember that well because I had immediate needs for it then. Since then, I have worked with assemblies that have multiple instances of a flexible sub-assembly. I never had any problems with one not moving except for one thing, similar to your two-hinges problem. I found that one would move, but the other wouldn't appear to move until I rebuild the assembly (ctrl-Q). I haven't experienced that problem for a while now. Have you tried doing a full rebuild (perhaps a couple times) after moving your assembly?
Another thought... did you do a clean (new) install, or did you do an upgrade installation of 2010 from 2009? I've had many problems in the past doing upgrade installs (from one version to another - 2009 to 2010). If so, then you should completely uninstall SolidWorks, clean your system of the residual SolidWorks files (see https://forum.solidworks.com/docs/DOC-1014, and https://forum.solidworks.com/thread/29679), then install SolidWorks again. As Wayne said, it may still come down to a non-english intall that is causing the problems.
I hope this helps, Shay. Good luck.
Tom
thanks for the review , my SW 2010 was a clean installation not an upgrade from 2009 (the 2009 is still instaled).
however i did found the problem ,it was one of the part configurations name that was writen in Hebrew charecters .
As I changed it to lower case English it works well .
thanks for the information anyway
Here is a simple example of a pair of doors with a pair of flexible hinges. The requirement for all unique configs changed a few versions ago. I built this example on SW2009 SP5.1 and then also tried it on SW2010 SP3.0. I don't still have SW2010 SP 2.1 loaded so I can't test that version.
As you can see, the movable door is in fact, free to move by way of both instances of the same hinge subassy being flexible in the upper assy. Maybe you can look at this example and compare it to your model and figure out what's different. If not, post the models here and we can take a look.
WT