On 7 October 2011 09:34, Peter Georgi <[email protected]> wrote: > I think that the set speed is for the X/Y > axis and the U/V axis try to follow the X/Y axis > to be at the same time in place when the X/Y axis > reache their position.
Yes, unfortunately this is how it works. There is no easy solution to this, as EMC2 has no way to know how your UV relate to your XY. (this is also why you can't do arcs in UV space) I assume that your G-code is produced by a CAM package, and has an X, Y, U, V on each line? The solution in your particular case is probably a simple filter (You can get EMC2 to automatically filter all input files) which converts the G-code to inverse-time mode and works out a cut-time on the basis of the larger of the XY and UV moves http://www.linuxcnc.org/docview/html/gcode_main.html#sub:G93,-G94:-Set -- atp "Torque wrenches are for the obedience of fools and the guidance of wise men" ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
