Gcode optimization
Posted by
Mark
on 2003-03-09 20:52:00 UTC
Think again about corel and DXF exports. ACE Converter from Yeager
does a wonderful job of optimization, starting with even line segments.
Allows you to specify the error in a segmented (exploded) line path,
and stays on the job to execute.
There was a troublesome Harley Davidson logo that produced fits in
another program, but which executed about 10x as fast when ACE generated
the gcode.
Go thru the archives looking for harley, and I'm sure you'll find it.
Only problem with ACE that I'm aware of is an error in interpretation
of "bulge" arc notation in dxf - Visio is the only program that I know
that generates this - all the others I've seen are ok.
/mark
does a wonderful job of optimization, starting with even line segments.
Allows you to specify the error in a segmented (exploded) line path,
and stays on the job to execute.
There was a troublesome Harley Davidson logo that produced fits in
another program, but which executed about 10x as fast when ACE generated
the gcode.
Go thru the archives looking for harley, and I'm sure you'll find it.
Only problem with ACE that I'm aware of is an error in interpretation
of "bulge" arc notation in dxf - Visio is the only program that I know
that generates this - all the others I've seen are ok.
/mark
Discussion Thread
Mark
2003-03-09 20:52:00 UTC
Gcode optimization
forumtvm
2003-03-09 21:26:23 UTC
Re: Gcode optimization
RichD
2003-03-09 22:04:23 UTC
Re: [CAD_CAM_EDM_DRO] Re: Gcode optimization
RichD
2003-03-09 22:09:22 UTC
Re: [CAD_CAM_EDM_DRO] Re: Gcode optimization
Tim Goldstein
2003-03-09 22:17:03 UTC
RE: [CAD_CAM_EDM_DRO] Re: Gcode optimization
caudlet
2003-03-10 06:21:03 UTC
Re: Gcode optimization (rethinking>>>)
Mark Thomas
2003-03-10 06:58:28 UTC
Re: [CAD_CAM_EDM_DRO] Re: Gcode optimization (rethinking>>>)
stevenson_engineers
2003-03-10 07:08:23 UTC
Re: Gcode optimization (rethinking>>>)
caudlet
2003-03-10 07:25:20 UTC
Re: Gcode optimization (rethinking>>>)
CL
2003-03-10 09:12:59 UTC
Re: [CAD_CAM_EDM_DRO] Re: Gcode optimization (rethinking>>>)