jmkasunich_ is now known as jmkasunich
cradek: for lathes, is it G43 that enables the X and Z offset from the tool table, and G41/G42 that enables radius compensation?
jepler: yes, it works just like a mill
what happens if the next move after G43 is an arc?
"it probably won't work"?
I didn't try it, but I think the endpoint would be adjusted. If you consider that when you pick the center/radius, it would be fine
jepler: are you writing docs again?
you're my hero
ha, the sample tool table in the spec has a '1/2" spot drill' with length of 173.740 units (inches?)
huh -- pwmgen doesn't have "offset"?
is this simply an oversight? I have an "offet" to pluto's pwm based on the canonical analog output spec
scale / sum ...
I guess it's an oversight then
I guess it's a little different from standard analog anyway since there's a fixed maximum limit (100%)
I'm thinking of adding "G42 R-" and "G43 R-" to do compensation with dynamic tool radius
I think that would be great
but then again, I have no experience using G-code, so I could be missing something :)
hmmm. there's a link to fix
the wiki home page still points as unpy.net for the quick ref (which then points back at linuxcnc ...)
fix it then
stop your whining
coffee time here, bbl
I am :P
where is the source for that doc? there's a typo
(the quick ref)
ah - it's only in the PDF version - the HTML is correct
the PDF version was simply generated by doing a "print to file" from firefox, then running ps2pdf
it's never updated because there's not a convenient way to automate that process
cradek: any opinions on G42 R- / G43 R-? I think I have it ready to check in.
do you mean 41/42?
I think it's a great idea, and pretty safe since R is never sticky
while we're at it, I'd like to do one more change to G43 - without an H word it defaults to the loaded tool
41/42 do that, but 43 doesn't, which I think is strange
I recall some discussions, but don't remember if we can't use L with G43 for length
for dynamic tool lengths, it's G43 I- L- or something like that
43 uses I[J]K currently
ah - right
bbl, work is calling
hm, the tool table uses diameters, using R for a diameter is going to be confusing, using radius when the tool table uses diameter is going to be confusing
I could use a different letter
(I wrote it to take a radius in R-)
sadly I think it would be best to take diameter instead
I can accept that -- but what letter?
I dunno, this sucks
except that D's an integer now (I think)
yeah I'm sure it is
there's at least one letter that can be an integer or float - D could be that way too
maybe we should have G41.1 42.1 and 43.1
43.1 I- [J-] K-
seems like they ought to work the same as much as possible
OK, I'll do it that way
don't take my word as gospel or anything - do you think it's any good?
I notice nobody else is chiming in
I had already proposed that G43.1 might be better than G43 H-1
what do you think about bare G43, should it work like bare 41/42
Is G43 without H an error now?
sure, it makes sense but doesn't change the meaning of valid programs
wonder what tool change does to g43 now
it should probably set the new offset if you change wiht g43 in effect (if we allow g43 without H)
sorry I don't intend to shovel more onto your project, we can sure monkey with g43 later
huh I thought we got rid of these
what is it?
CHK(((block->g_modes > G_80) && (block->g_modes < G_90)),
I'm not sure they're not useful - for instance I can see using the peck drill cycle for parting
(not sure how serious I am about that)
we never define LATHE so they're always available
you could definitely use peck drilling with a tailstock
that's not even perverse
wonder if anyone has ever tried the cycles in other planes (I remember seeing there's code to handle it)
I also know there's code for it
strange, either g83 doesn't work, or I can't figure out how to use it
OK I think I just hit a proverbial brick wall
you're on a lathe. You use G42.1 D.01
what is the tool orientation?
hmm, good question
xtrans and ytrans refer to orientation and diameter from the tool table
int o = settings->tool_table[settings->tool_table_index].orientation;
double r = settings->tool_table[settings->tool_table_index].diameter / 2.0;
seems like you have to let that be specified too
if it's not, it defaults to 0, like a mill
any idea why xtrans and ztrans use settings->tool_table.diameter / 2.0 instead of settings->cutter_comp_radius?
what letter do you want for tool orientation?
no, I don't remember
maybe just 'cause
L? E? one of the ints
I'll use L for now
so you might write: G42.1 D.01 L3
let me see if all this compiles...
now you just have to fix up a dozen error detections...
G410 requires D word to be a whole number
well I got something wrong...
yeah g83 is broken
ah, it's not seriously broken, it just has a bug
not fatal? just a flesh wound?
you can call it an F word
err, without an F word
and it runs with feed 0 (never going anywhere)
so, I made the change to PWMgen - adding in an offset param
I haven't committed it yet because I'm not sure if there's any unexpected interaction with min_dc
will the behavior be the same if offset=0?
if so, it's safe to commit for everyone who isn't using offset
yes, it just subtracts offset from the pwm setting before going through all the other checks
I say check it in
ok. will do
I only have it in TRUNK - any thoughts about 2_1_branch?
start with TRUNK
it smells like a new feature to me
cradek: the docs say about G41/G42 "It is an error if ... the XY plane is not active"
cradek: is the limitation now to the XY or XZ plane?
YZ is not OK
hmmm. I think it may be a bad idea to start working on computers just after you've been working on cars
it makes it harder to judge how much torque you're putting on things
'hand me the 13mm memory socket.'
I never put more screws in than I take out..
how many foot-pounds to I tighten that memory to?
SWPadnos: remind me .. what was your altium licence?
err - full?
quite a bit :P
what machine do you run it on?
is this with the 9MP monitor?
no - Windoes has issues with the 9MP monitor
ahh.. ok, too bad ;)
I run it in this computer: an Athlon 1800 q/1.5G RAM and a Matrox Parhelia (3 monitors)
I've gotten Wine installed on my dual Opteron machine, and I'll try it there at some point
what's the 9MP monitors resolution again?
err - 9MP ;)
3840x2400, 204 DPI
yep. you should see Google maps with that
can you still see it?
yeah, and you can read street names with a magnifying glass ;)
but it's especially nice in hybrid or satellite mode
the color is actually quite good. It's not up to par with the Eizo monitors or a Barco, but it's definitely on the high end
cradek: there's no fundamental reason that cutter radius compensation can't be extended to the remaining plane, is there?
does it work in one vertical plane and not the other (now)?
SWPadnos: I think that's right -- since it can be used on lathes, and you're in the XZ plane there
the docs do say it's an error if plane is not XY though
a lathe is only XZ by convention, the Y and Z are interchangeable since the part is rotating
I don't know if that matters
jepler: well I think it's complicated. gene would want to cut an arc in XZ even though his tool is along Z. On a lathe the tool is "along" "Y" so it's all different
I tried to draw a picture and the only thing I saw is that you'd need to set something like a lathe tool orientation, so that the coordinates are for the tip of the tool and not somewhere up inside the tool
I also haven't figured out in what way the lathe tool is along "Y"
think of the radiused end of the tool as an end mill
the cutting occurs on the top edge of the circle
the pretend end mill is perp to XZ
maybe if I could see why trying to use XZ compensation mode on a mill would not work