On Wed, 2007-08-22 at 09:36 -0500, Jeff Epler wrote: > On Wed, Aug 22, 2007 at 02:02:39PM +0000, ben lipkowitz wrote: > > > > > The first couple of cuts I was using a chord length of about 100mm, > > > meaning that my g-code statements around the leading edge where about > > > 0.1mm apart or less, which caused the feedrate to slow down for some > > > reason, which caused too much heat to build up in the leading edge. > > > > If you use G64 P0.1 the trajectory planner *should* automatically blend > > out the unnecessary segments and give you full speed over the entire shape. > > Unfortunately, G64 P- only simplifies nearly-colinear segments when they > are purely XYZ movement. If there is any movement on the other axes > (ABC or UVW) then the simplification doesn't take place.
Ahhh, ok. After reading the description of G64, I am realizing that the reduction in feed rate is probably due to my acceleration limits. I have not really tuned those parameters and they are probably still very conservative. Does that make sense? A question about radius cuts. I would like to be able to command a circular cut simultaneously in XY and UV (to cut a cylinder). G01 x10 y10 u10 v10 G17 G2 x10 y10 u10 v10 i0 y2 I assume that this will cut a circle in the XY plane with a radius of 2 and start/end at x10 y10, but it seems from the description that uv will remain stationary causing me to end up with a cone, is that correct? Or is there a way to tell it to use both xy and uv for the circle? Ryan ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
