Hi to all! Is it possible to import native solid works models and assemblies?
Unfortunately, no (as far as I know). But there are 3rd party converters which can (extra few $$$$). Otherwise, since SW is parasolid (*.x_t or *.x_b (unix)), the best option for WF or WF2 should be Parasolid (the x_t or x_b import option should be available?) and the next option would be STEP (I'd prefer/suggest ap214). ...
I believe you can, if you simply mean exporting from within SolidWorks so files can be opened with Pro-E. You won't be able to parametrically modify dimensions, but you can make cuts and add protrusions, and assemble them in Pro-E assemblies. I don't currently have SolidWorks installed so I can't verify this but I have done this previously, I believe you can do a Save As and pick the appropriate type you wish to save it as. I have opened these files with Pro-E and worked with them myself.
Is it possible to import native solid works models and assemblies? Just to avoid confusion; I'd interpret "native" as meaning .sldprt, ..sldasm... in which case it's a no go. Paul's export suggestions are probably the best bet for neutral translations, though I can't say from experience if there's any benefit to using Parasolid vs. STEP. General curiosity question; Is it possible to export curve and surface / quilt entities from SW or it it "solids" only? If it's possible, are there limitations in one or other of the neutral translation protocols?
: > > Is it possible to import native solid works models and assemblies? : : > I believe you can, if you simply mean exporting from within SolidWorks so : > files can be opened with Pro-E. You won't be able to parametrically modify : > dimensions, but you can make cuts and add protrusions, and assemble them : in : > Pro-E assemblies. I don't currently have SolidWorks installed so I can't : > verify this but I have done this previously, I believe you can do a Save : As : > and pick the appropriate type you wish to save it as. I have opened these : > files with Pro-E and worked with them myself. : : Just to avoid confusion; I'd interpret "native" as meaning .sldprt, : .sldasm... in which case it's a no go. Paul's export suggestions are : probably the best bet for neutral translations, though I can't say from : experience if there's any benefit to using Parasolid vs. STEP. : I was surprised to see that SW exports to Pro/e assembly/part. I was more surprised at the balls of SW to call this exporting to PE when you open it in Pro/e and find a neutral file, single feature solid. SW, come on, who are these cheap ass monkey shines fooling!?! Pro/e exports Parasolid data. Does SW export/import Granite data? If you don't, then quit saying you export Pro/e part and assembly files. David Janes
Jeff, Correct, native sldprt/sldasm is not possible (as far as I know, which btw should be, because the parasolid data is there ..for example, SW can read UG files (bodies only)) but as Dan said, if Jean has SolidWorks,.. then yes, he can do a Pro/e export which is only a body or bodies of the SW data, not curve/sketch data. As for experience/benefits with parasolid over STEP files,.. parasolid is the best for me so far but there are times parasolid import (this could be a version or ptc programming issue) does not always have good results so STEP is the alternative. And, it makes sense, parasolid is sldprt native (no conversion needed) and the x_t may not be something ptc is reading correctly..(may also be a parasolid import toler/gap issue) and STEP is a two + conversion process (interpretation issues) but the data should be common from the conversions? But, the odds are STEP could have more problems with interpretation, such as, nurbs surface topology, boundary tolerances/gaps. As for Parasolid/STEP export of curve data,.. parasolid still does not support this (last I checked) and STEP is suppose to but it may not be supported by SW or Pro/e on the export/import? The alternative,.. IGES for curve export/import. ...
