[ 499.645461] timedelta: module license 'unspecified' taints kernel.
didn't jeff write that one?
if so, its just an oversight, easily fixed
fixed in rev 188.8.131.52 of timedelta.comp -- but not in 2.2.2
SWPLinux_ is now known as SWPLinux
I worry about G-X... I hope he can do this safely
that's a good point
cradek: speaking of which, do you think you could write a Python function that takes machine XYZUVWABC and returns the tooltip XYZ, roll, and pitch?
cradek: for a specific mill, that is
do you mean "you" (me) or "one"?
if you mean "me" then probably, if I knew what roll and pitch are
what I mean is that if I thought someone would give me that code, I'd try improving the preview to be more useful for 5-axis machining
well, two angles that give the orientation of the tool in a well-defined way
for max, I think it's virtually the same as the kins
B,C already are that, I think
let's go to lunch
it would be nice if TLO and tool diameter compensation, and tool were in UVW always
except for one detail
and canon/task/GUI would know where UVW is rotated translated (based on the machines XYZABC)
well, at least one detail
jepler: I know it can't work for the general case..
that's why I said it would be nice..
what detail did you have in mind?
the one I had in mind -- and I know chris has mentioned this before -- is that length compensation isn't applied until the axis it's applied to is moved again
introducing the requirement to move W in 3-axis programs would be .. weird
well.. W would move if any of XYZABC would be commanded to move
(I know at the moment the requirement is to command W to move..)
but it's probably a PITA to mix RT and non-RT code
imagine: go to top of travel, insert longer tool and activate length comp. now go to some XY, now go down to safety height, now cut
(kins is obviously RT, and the TLO and whatnot is not)
you can't apply the length comp on the XY move, because you'll go out of limits
cradek: then it's an program error :)
well, I suspect this is by far the usual case, actually
* alex_joni draws the same conclusion as last time
g-code is too strange to be used for a real robot
could be. I want to use it for real mills instead, where it's always used :-)
yes, it might just work for most of those ;P
in posemath, how do I rotate a point (PM_CARTESIAN) around an axis?
there doesn't seem to be a version of this in the C++ code
EMC: 03jepler 07TRUNK * 10emc2/share/axis/tcl/axis.tcl: show version number in title bar