Problems with converting .step assemblies

[AlecMataloni]

Currently I'm having an issue whenever I try to use any recently saved assembly that has been converted from .step to .sldasm.
First, I download any step file with more than one part involved (let's just use the vexpro ball shifter as an example).

Then, I unzip the folder and open the model. It generates with no issues, and everything works great. I save everything in the model to a folder on my desktop, then completely exit my session of Solidworks. No problems yet.

This is where things get strange. I open a new session of Solidworks, and select the recently closed assembly file. The file opens, and suddenly every component in the assembly is permanently suppressed. I try unsuppressing each of the components but it simply doesn't work. I can access each individual piece of the assembly through the feature tree (as long as it's a .sldprt), but they won't display themselves in the assembly for some unknown reason.

When my cursor hovers over each suppressed part, solidworks says that "the file for this component cannot be located", even though when I open the part through the feature tree, it opens with no problems.

Has anyone else had this issue before? It's been happening to me every time I've tried to do this, including when I had Solidworks 2011 installed (I've since upgraded to 2012). If so, would you recommend any course of action?

[nathan_hui]

Hmm. I can't replicate the issue with the 3 Stage 60:24 with US Digital Encoder (STEP) (http://content.vexrobotics.com/cad/S...oder-STEP.zip).

One thing though, when you first save the model, make sure you explicitly tell SW to save all the parts at the same time. I'll keep trying to replicate the problem.

[nathan_hui]

Actually, what program are you using to unzip the zip file? Just to cover every possible problem.

[nathan_hui]

Originally Posted by AlecMataloni

When my cursor hovers over each suppressed part, solidworks says that "the file for this component cannot be located", even though when I open the part through the feature tree, it opens with no problems.

Are you able to locate the sldasm and sldprt files in Windows Explorer?

[AlecMataloni]

I used the windows-native "extract all" function. I also just tried using winrar and it didn't make a difference. Yes, I can find them in windows explorer as well.

[AdamHeard]

Did you save the assembly in a different folder than the .step is in?

I get this error if I open the step somewhere, and save the assembly somewhere else.

When I move the .step into the folder I want the assembly to be saved in, then save there, it works fine for me.

[nathan_hui]

Hmm. I'm not getting that issue. I'm wondering right now if there's a difference in our SW installations...

I can save the freshly converted assembly to anywhere and still open it without problems.

[AlecMataloni]

Adam, that might be my issue. I'll try it.

EDIT: Nope, no luck.

[nathan_hui]

So another possibility: the step file you're trying to convert is corrupt. Are you getting this with all of your step files, or is it one particular step file?

[AlecMataloni]

Every single .step assembly that I try to save has this problem, from vexpro assemblies to entire robot assemblies.

[nathan_hui]

Are the sldprt files in the same directory as the sldasm files?

[roystur44]

Limitation of the education version you are using???

[nathan_hui]

Originally Posted by roystur44

Limitation of the education version you are using???

Likely not. I'm running SW 2012 Educational, without those problems.

[roystur44]

Then check the security on the folder. Make sure it's not set to read only

[nathan_hui]

OP's problem indicates SW isn't able to recognize that the sldprt files linked in the sldasm are part of the model. He says he's able to open them from the Feature Manager, which says SW knows which file is which, but the assembly view shows nothing, and all the parts are permanently suppressed, and saying that the original files can't be accessed. The files are all where they're supposed to be - sldasm and sldprt in the same directory. SW appears to be really confused about the sldprt files in the directory. To me, this says SW either has some really screwed up settings or the installation is corrupted, since this is common across multiple step files (so isn't limited to a single file being corrupted, unless every single step file he touches is corrupted, which is unlikely, yet possible).