Re: [CAD_CAM_EDM_DRO] Re: translation utillities and CAM
Posted by
Marcus & Eva
on 2002-01-12 08:37:22 UTC
Hi All:
To get from a solid modeller to a CAM program requires a translation
utility unless you have one of the add-on packages that Jeff describes.
The most common translator is IGES; it works reasonably well in translating
a solid model into trimmed surfaces and edge curves that can then be used by
the CAM program to create toolpaths.
Another is Parasolid, and I've heard of people using STL.
The native Pro-E or Solidworks format cannot be used to create toolpaths
without a dedicated module to do so.
I don't care much for these anyway, because they tend to generate
inefficient code that requires lots of processing power to run, and robs you
of tool control.
My current approach is to go from Solidworks via Parasolid to Mastercam.
I import as trimmed surfaces and edge curves (although Mastercam does
support solids).
I like to be able to manipulate entities individually and have full control
of the toolpaths.
Cheers
Marcus
To get from a solid modeller to a CAM program requires a translation
utility unless you have one of the add-on packages that Jeff describes.
The most common translator is IGES; it works reasonably well in translating
a solid model into trimmed surfaces and edge curves that can then be used by
the CAM program to create toolpaths.
Another is Parasolid, and I've heard of people using STL.
The native Pro-E or Solidworks format cannot be used to create toolpaths
without a dedicated module to do so.
I don't care much for these anyway, because they tend to generate
inefficient code that requires lots of processing power to run, and robs you
of tool control.
My current approach is to go from Solidworks via Parasolid to Mastercam.
I import as trimmed surfaces and edge curves (although Mastercam does
support solids).
I like to be able to manipulate entities individually and have full control
of the toolpaths.
Cheers
Marcus
----- Original Message -----
From: "jeffswayze" <jswayze@...>
To: <CAD_CAM_EDM_DRO@yahoogroups.com>
Sent: Friday, January 11, 2002 8:09 PM
Subject: [CAD_CAM_EDM_DRO] Re: JeffSwayze (and others)
> --- In CAD_CAM_EDM_DRO@y..., "Patrick Alleven" <
> alleven@m...> wrote:
> > Jeff, (and others)
> >
> > as a user of both Pro-E and Vector, could you comment on the
> feasibility of using Pro-E, combined with code generating
> software as a "home use" CAD -CAM system? i understand that
> Pro-E is a complex and powerful program aimed at industry, and
> Vector is a CAD-CAM package aimed at the home user (at least
> that's what i gather). do you use Vector at home because it is
> easier and faster on the less complicated parts?
>
> =============
> I use Pro/Engineer at work (along with I-DEAS, but that's another
> topic ;) ) and I certainly consider it the best CAD package I've ever
> used. However, I also hear great things about SolidWorks.
>
> To your point: as far as I know, there's no good working link
> between Pro/E and Vector (I can't speak for the other packages.)
> The output of Pro/E is a solid model. From that you need to
> generate NC code. There is a CAM module for Pro, but I'm not
> familiar with it. I'm sure it does an adequate job, but like the rest
> of the Pro/ series I'm sure it's very expensive. Vector allows you
> to generate 2D geometry and then helps you create the NC
> code. This code you run through stepper driver software (in my
> case CNCPro) that actually moves your machine to make your
> part. I think the only way you could use the two together is to
> export DXF entities from Pro and bring them into Vector, using
> the various Vector commands to create a tool path.