Hello everyone,
In order to use a single format for my subcontractors and colleagues, I would like to know what would be the most suitable file format to share my 3D sets.
I am currently using the . STEP, but this one is very long when opened.
I would like to know if you use special formats, and if you have ever had this case where you shared the same files between your subcontractors and your colleagues?
(I have Solidworks 2014 Pro).
Thank you very much, have a good day!
Hello
For me, it's the most used WWTP.
Apart from the STEP, IGES or parasolid formats are also quite widespread, but I'm not sure it's faster when opened!
Otherwise for simple visualization, you can also extract in edrawings format, and even make an edrawings executable, so people who want to visualize don't need to install Edrawings on their computer.
For me, it depends on the software used to open the file.
If the file is subsequently opened on a CAD or CAM software based on the same modeler as SW, the parasolid format should be preferred (faster, less heavy, geometry cleaner to aperture).
The step is, by far, the most used but I rarely have a clean result after importing. In addition, there is no versioning in the evolution of the encoding. With your SW 2014, you may have trouble opening steps created by newer software.
Okay, I was also thinking that the ParaSolid was faster.
Then I avoid eDrawing, I find it super cumbersome, plus my goal is to have an identical file for my subcontractor and my colleagues (this way we are sure that the file is the one that will be made).
Thank you for your answers;)
Hello
The step is the most common.
STEP, IGES, Parasolid in order
Hello
Although it takes longer to open, the WWTP is still the best because it is voluminous. It creates volumes when the IGES makes surfaces and therefore generates more problems with surface connections (I don't use it anymore).
The most important point is the compression rate of the step (around 4x) which is not negligible for mail transfers!
Parasolid is the native kernel (or modeler) format of solidworks, solidedge, and topsolid. So if your subcontractors use one of these formats then you will have the best transfer in terms of export/import quality.
For exchanges to Catia/solidworks, I recommend the .sat because like the parasolid for solidworks, it is the modeling of the Catia kernel.
Hope I helped you
rom's
Hello
SAT engine from Catia? I don't think it's the engine of Audodesk products but Catia uses its own engine if I'm not mistaken (but I could be wrong).
@+
Hi Coyote
Indeed you're right, I went a little fast. as much for me ;-)
It is indeed the core of the autodesk logs, but Catia integrates it particularly well. Even for exports from Catia to solidworks I recommend it instead of the step. On the other hand, I have never had too many problems.
Re
To be very precise, I actually learn that Dassault bought Spatial (creator of the SAT) in 2000....
http://www.01net.com/actualites/cao-dassault-systemes-rachete-acis-de-spatial-technology-114059.html
http://www.spatial.com/products/3d-acis-modeling
@+
I don' t entirely agree with you on the WWTP.
It's a volumetric format, yes; but he passes through surfaces which he sews together to make a volume.
To export parts, it works well, but when it comes to exporting an assembly it has a harder time. There are even cases where it can be planted for sure (two different pieces with an identically shaped contact side).
The iges works in the same way (sewn surfaces transformed into volume)
In the list of software with a parasolid core, we can add NX from siemens and Visicad.