On 9/28/15 10:51 AM, EBo wrote: > On Sep 28 2015 8:37 AM, Sebastian Kuzminsky wrote: >> On 9/28/15 12:41 AM, Chris Morley wrote: >>> Personally I think if we really want this included in linuxcnc in a >>> reasonably >>> amount of time we should create a 2.8 branch now and then merge >>> Joints_Axes >>> into master. >>> Based on the past, that puts Joints_Axes into the two years + >>> position for release. >>> >>> It seems to me the only way to get it done is to 'force' more >>> developers to fix the issues. >>> eg I'm not going to fix stepconf or pncconf to work with Joints >>> until I know it will be released. >>> >>> Merge it and lets get it done. >> >> I think we should merge JA into master before the 2.8 branch. We >> just >> released 2.7, so this is a fine time for big experimental features. >> >> But i strongly disagree that we should merge it while it has such >> glaring known problems. JA does not not currently work on lathes, or >> on >> other machines with non-consecutive axes! That's unacceptable in >> master, IMO. >> >> When someone volunteers their time and fixes this bug, it will be >> closer >> to mergeable. But "forcing" has no place in a volunteer >> organization. > > non-consecutive axes? I am not aware of that term. I probably know > what you mean, but not by that name...
It's a term I just made up. I mean machines with multiple axes from the list "XYZABCUVW" but with gaps. For example, lathes have axes "XZ", so the missing Y makes X and Z non-consecutive. Try running the sim/axis/lathe config on joints_axes to see the error i'm talking about. -- Sebastian Kuzminsky ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
