ouch, I think I just hit a bug
here's the sequence that I think did it:
G28 (moves X, Y, Z)
the 'XY-only' move goes to its destination, and then Z moves back down towards -2
hm .. it did it twice based on an mdi sequence like the above one .. but not a third time
aren't you on vacation?
jmkasunich: no, I got back yesterday evening
are you unwittingly issuing a command G28 X-2 Y1 on the third line?
G28 isn't a modal motion command, is it?
I don't know
that would be somewhat astonishing
does it show in the "active modal codes" box?
no, it doesn't
whatever it was, I saw it happen twice -- but now it doesn't.
G28/G28.1/G30/G30.1 are group 0; G0 is group 1
I'm trying to figure out whether I could have written that bug when I wrote the new G28/G30
I'm not seeing this problem (with only minimal testing) in trunk
did you see it on 2.2.5? (or is jeff the only one to see it at all?)
I haven't tried 2.2 yet
no I'm not getting it, argh
I am pretty sure that these are the last mdi I did before I saw the behavior I'm talking about:
x-2y1 (I recall that it went at g0 speed?!)
it sure sounds like it was doing "g28 x-2y1"
no; going to machine z0 would have been OK
g28 position was fine .. z<small> in g54 was a position for tool-breaking
so when you issued G28, it rapided to machine home?
G28 did what I expected
then I commanded an XY move
and then when you issued x-2y1 (with an implied G1), it rapided first in XY, then in Z?
g28x-2y1 (if that got issued) would have gone to x-2y1 in the currently active coordinate system and then moved x,y only to machine origins
it went to the commanded XY then down towards g54's z<small>
sadly I'm not seeing it here
Of all the number of times I could see this problem, two is about the worst
two is the loneliest number
one you can write off as a typo
many you can debug
hope you/we can reproduce that.
I was hoping to forget it :-P
but it already cost you $7
you will remember, out of spite
pcb routing big?
no, a .0292 drill
I have additional motivation to figure out how to do pc boards
what motivation is that?
I found about 5 square feet of single sided board stock in the dumpster
how big are the pieces?
nice. often it's double which is a pain
if you can stand to learn eagle and learn their programming language a tiny bit you can generate gcode for it pretty easily
3 pieces ~24" x ~8", one about 8 x 12
and you are better than me at being careful
any progress on your fast spindle yet?
why is double sided a pain?
* jmkasunich likes ground planes
it's more than twice as hard to do
because you have to flip it over to cut out the lead holes even if it's single sided artwork
(only solder on the traces side, clear the metal around the holes on the plane side with the c'sink)
right, still it's more effort than using single sided
more effort yes
better grounding is a good thing
i've heard of people peeling the copper off but not sure i believe it
whether you actually need better grounding depends on the project
SWPadnos_ is now known as SWPadnos
.. and good night
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/quickstart/stepper_quickstart.lyx: Changed to a worksheet for using Stepconf
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/ (Master_Integrator.lyx Submakefile): added file stepper_quickstart.lyx
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/examples/gcode.lyx: short description of sample g code files
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/Submakefile: added file gcode.lyx
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/Master_User.lyx: Added g code examples
EMC: 03bigjohnt 07v2_2_branch * 10emc2/docs/src/ (Master_User.lyx Submakefile): Added gcode example descriptions
EMC: 03bigjohnt 07v2_2_branch * 10emc2/docs/src/examples/gcode.lyx: Added gcode example descriptions
EMC: 03bigjohnt 07v2_2_branch * 10emc2/nc_files/comp-g1.ngc: Added G1 comp example
EMC: 03bigjohnt 07v2_2_branch * 10emc2/docs/src/ (Master_Integrator.lyx Submakefile): Added stepper quickstart
EMC: 03bigjohnt 07v2_2_branch * 10emc2/docs/src/quickstart/stepper_quickstart.lyx: Added stepper quickstart