On 2/13/2014 11:34 AM, Chris Radek wrote: > On Thu, Feb 13, 2014 at 10:14:24AM -0800, David Bagby wrote: > >> In contrast, a rapid G0 move is "go from A to B by spinning up the >> motors as fast as they will go and end up at B". >> The _only _thing guaranteed for a rapid move is that the machine will >> end up at B. >> >> An important difference is that this does not say that the straight line >> from A to B will be followed. > In LinuxCNC, this is wrong, and G0 is and has always been done with > coordinated linear motion, documented here: So in LCNC, G0 is actually "coordinated" motion. Given that, I could see that it is a technical possibility to blend two coordinated motions from different modes (a G1 and a G0).
However, it seems wise to make this an option that defaults to Off. My thinking is that existing gcode programs effectively assume a full stop between blocks with mode changes. I'd like not to violate that implicit assumption. If we blended G1/G0 we would be creating different motions between G0 and G1 (or vise versa) blocks than we get today, thereby altering the physical motion of a current gcode program. Hence my desire to see the default value of such an option be "no blending between G1 and G0". This seems the safest, backward compatible approach. Dave ------------------------------------------------------------------------------ Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
