Hello, this question has probably been asked many times on
this forum, but I can not seem to find it anywhere. So, I thought I
would ask.
I need to export assemblies (200-300 parts) into .step and/or .iges files to be viewed in other software packages. If I use "Folders" in SolidWorks to organize the parts, the "Folders" do not export with the parts. The parts export but they are in 200 random pieces, with no organizational structure. "Display States" seem to function the same way, they work well inside of SolidWorks, but they do not export.
To work around this situation, I have been using 'sub-assemblies' to organize the parts. The 'sub-assemblies' do export and control the data when opened in other software. The problem with the 'sub-assemblies' is that it hard to use some of the SmartComponent, SmartFeatures, and Mating Tools. I seem to use a lot of the functionality of SolidWorks when tied up in assembly structure.
(The "Flexable" sub-assembly helps a little.)
Any ideas, input or workarounds on this would be very helpful. I am sure there is something that I am missing. It would be great if when exporting an assembly, SolidWorks would convert Folders into sub-assemblies.
Thank you for your time and assistance.
Michael
I need to export assemblies (200-300 parts) into .step and/or .iges files to be viewed in other software packages. If I use "Folders" in SolidWorks to organize the parts, the "Folders" do not export with the parts. The parts export but they are in 200 random pieces, with no organizational structure. "Display States" seem to function the same way, they work well inside of SolidWorks, but they do not export.
To work around this situation, I have been using 'sub-assemblies' to organize the parts. The 'sub-assemblies' do export and control the data when opened in other software. The problem with the 'sub-assemblies' is that it hard to use some of the SmartComponent, SmartFeatures, and Mating Tools. I seem to use a lot of the functionality of SolidWorks when tied up in assembly structure.
(The "Flexable" sub-assembly helps a little.)
Any ideas, input or workarounds on this would be very helpful. I am sure there is something that I am missing. It would be great if when exporting an assembly, SolidWorks would convert Folders into sub-assemblies.
Thank you for your time and assistance.
Michael
Sub Assemblies do move.
So when people are sending assemblies from SolidWorks, they are just getting a big pile of parts?
Thanks
Michael
I don't understand what folders and display states have to do with your assembly. As Josh noted, they are SW specific and won't be translated with any of the neutral formats.
I also don't understand how it is that subassemblies seem to come across organized properly when the final assembly doesn't. It should be all or nothing, since they are all just assemblies.
I have sent assemblies to a number of other CAD packages in Parasolid, STEP and IGES formats. I remember some people telling me that IGES files came in without any assembly structure. I don't remember that happening with STEP or Parasolid files, but that may say more about my memory than it does about the sucess of the file transfers.
It just seems difficult to make some of the SolidWork Tools function properly when working with subassemblies. Using folders in SolidWorks seems easier and more user friendly.
Finding the flexable assemblies has help some of the mating issues, but has not helped with using the SmartFeatures and SmartComponents.
I want the exportability of a Assembly/SubAssembly, with the ease of use of a SolidWorks Folder.
I don't use SmartFeatures or SmartComponents, so I'm afraid I can't help much. I still don't understand what you are using Folders for. Are you just using them to organize the parts in your assembly without setting up any subassemblies? This could lead to problems and speed issues with mates, since the assembly will have to solve all the mates. With subassemblies, the assembly only has to solve the top level mates and each subassembly solves only its own mates.