[Emc-developers] jog question

[Gene Heskett]

Greetings all;

I now have my jogging working well except for one minor detail.

That detail is that from a powerup state of linuxcnc, I have to do a
keyboard jog, destroying the position restored from the position.txt
file, before these jog dials work.

What do I have to do to make them work from the gitgo as long as focus is
on linuxcnc's window?

All the signals are being given to motion, at jog-enable, jog-counts and
jog-scale are all there for that axis, and I can watch the jog-counts
changing as I turn the dials but nothing happens until I jog with the
keyboard once, on each axis I think.

Cheers, Gene Heskett

[Jon Elson]

Post by Gene Heskett
Greetings all;
I now have my jogging working well except for one minor detail.
That detail is that from a powerup state of linuxcnc, I have to do a
keyboard jog, destroying the position restored from the position.txt
file, before these jog dials work.
What do I have to do to make them work from the gitgo as long as focus is
on linuxcnc's window?
All the signals are being given to motion, at jog-enable, jog-counts and
jog-scale are all there for that axis, and I can watch the jog-counts
changing as I turn the dials but nothing happens until I jog with the
keyboard once, on each axis I think.

When I first start up LinuxCNC, I do a home operation. I
don't care about the last position, what I do care about,
sometimes, is the offset between machine and G54
coordinates. After I home, then the offset between these is
restored, and so whatever position is shown on the DRO is
the same, RELATIVE to the PART, as it was when LinuxCNC was
shut down. So, in the case where I had to go back and
perform more operations on a part machined yesterday, I
don't have to touch off to the fixture or part, it is all
restored the the previous setting. (Of course, whatever
fixture was used before must be in the same position.)

I don't do this all that often, but sometimes I am using the
same setup two days in a row, or need to redo something
after LinuxCNC has been shut down.

And, if you have not set up sensors to do machine homing,
you are missing a VERY useful feature of LinuxCNC.

Jon

[Gene Heskett]

Post by Jon Elson

Post by Gene Heskett
Greetings all;
I now have my jogging working well except for one minor detail.
That detail is that from a powerup state of linuxcnc, I have to do a
keyboard jog, destroying the position restored from the position.txt
file, before these jog dials work.
What do I have to do to make them work from the gitgo as long as
focus is on linuxcnc's window?
All the signals are being given to motion, at jog-enable, jog-counts
and jog-scale are all there for that axis, and I can watch the
jog-counts changing as I turn the dials but nothing happens until I
jog with the keyboard once, on each axis I think.

When I first start up LinuxCNC, I do a home operation.

Since amazon is killing me with slow delivery of the countershaft
bearings, and I need to order some hacksaw blades for my big bandsaw,
home switches are about the next thing on the agenda Jon. Currently its
not running motors to home, just accepting where its at.

Post by Jon Elson
I
don't care about the last position, what I do care about,
sometimes, is the offset between machine and G54
coordinates. After I home, then the offset between these is
restored, and so whatever position is shown on the DRO is
the same, RELATIVE to the PART, as it was when LinuxCNC was
shut down. So, in the case where I had to go back and
perform more operations on a part machined yesterday, I
don't have to touch off to the fixture or part, it is all
restored the the previous setting. (Of course, whatever
fixture was used before must be in the same position.)

Agreed, done that many times myself. Works well I find if I don't screw
up and do a touch off.

I wonder, once I have it searching for homes, is that enough to "cock"
the motion so my jog wheels work without priming the pump with a short
tap on the arrow keys?

I know where I'm putting the X home switch, but haven't concocted a Z
location yet. Someplace near the chuck, rigged so it can overrun it and
come back over it w/o damaging the switch. That was a bit of a bear on
TLM. Wrecked a couple switches getting it just right.

Post by Jon Elson
I don't do this all that often, but sometimes I am using the
same setup two days in a row, or need to redo something
after LinuxCNC has been shut down.
And, if you have not set up sensors to do machine homing,
you are missing a VERY useful feature of LinuxCNC.

Absolutely. I find them handier than bottled beer on the G0704 too.

Post by Jon Elson
Jon
----------------------------------------------------------------------
-------- Check out the vibrant tech community on one of the world's
most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Emc-developers mailing list
https://lists.sourceforge.net/lists/listinfo/emc-developers

Cheers, Gene Heskett

[Jon Elson]

Post by Gene Heskett
I wonder, once I have it searching for homes, is that
enough to "cock" the motion so my jog wheels work without
priming the pump with a short tap on the arrow keys?

Not sure. I know that right after coming out of E-stop
(even if still homed) that the first jog keyboard key I hit
is ignored.
Hit it again and it jogs. I do NOT believe that this
affects the jog MPG, or that the jog MPG clears whatever it
is that prevents the first jog key from being accepted.
(But, maybe I need to try all possible sequences of that.)

Jon

[Gene Heskett]

Post by Jon Elson

Post by Gene Heskett
I wonder, once I have it searching for homes, is that
enough to "cock" the motion so my jog wheels work without
priming the pump with a short tap on the arrow keys?

Not sure. I know that right after coming out of E-stop
(even if still homed) that the first jog keyboard key I hit
is ignored.
Hit it again and it jogs. I do NOT believe that this
affects the jog MPG, or that the jog MPG clears whatever it
is that prevents the first jog key from being accepted.
(But, maybe I need to try all possible sequences of that.)
Jon

Its quite repeatable here. I must tap a keyboard arrow key, before the
jogwheel can move an axis, any axis. (at least on a lathe)

But like you said, I need to go and double check to see if its that
axis's arrow key, or any axis arrow key that enables it.. I'll try and
do that yet today, but I have a bigger problem. TLM's configuration is
all fouled up. Discovered when I chucked up that pulley to carve the
taper for the taperlock hub.

I hadn't run it for anything since the axis/joint merge, and my files
look all confused, and still are after I've spent about 3 hours trying
to sort that out.

And I just did, having fixed my lady some late lunch, I went out, ran it,
enabled it, touched the Z button, ran it up to 5 thou per click, but no
motion when I released the button, which leaves it live for 30 seconds,
hit the in button on the keyboard, it ran X in for .5000" and the z dial
worked until it timed out 8 or 9 seconds later. So its any motion, and
its possible the homing when active would qualify to raise the crossbar
& let it move. I am inclined to call it a bug, but what do I know? Maybe
someone thought it was a good safety feature.

Thanks Jon.

Cheers, Gene Heskett