Discussion:
Special config for a lathe, practical?
(too old to reply)
Gene Heskett
2017-06-29 14:31:26 UTC
Permalink
Raw Message
Greetings All;

Because the G5.x stuff hasn't had much TLC (probably from lack of general
use by the artisticly inclined among us) since it was intro'd back in
the mists of time, and is locked to x/y only motions, the thought has
come to mind of creating a special config where x is carriage motion on
the bed, and y is crossfeed. Essentially duplicating a milling
machine's xy motions. This is the easy part. What might be surprises
are the g7-g8 effects, which work on the x axis, and that would not be
ideal. So G8 s/b hard coded somehow.

Next of course would be touch-offs, but if the config is done right,
should not be a problem.

What surprise gotcha's would I be likely to find?

Was there some overriding reason the default lathe configs weren't done
this way in the first place?

Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Les Newell
2017-06-29 14:43:05 UTC
Permalink
Raw Message
Hi Gene,

G8 is hard coded to work on X axis. It doesn't really make sense for any
other axis. Could you swap the axes in your config?

Lathe uses X-Z because lathes are essentially treated as milling
machines on their side. By convention Z is parallel to the spindle axis.

Les
Post by Gene Heskett
Greetings All;
Because the G5.x stuff hasn't had much TLC (probably from lack of general
use by the artisticly inclined among us) since it was intro'd back in
the mists of time, and is locked to x/y only motions, the thought has
come to mind of creating a special config where x is carriage motion on
the bed, and y is crossfeed. Essentially duplicating a milling
machine's xy motions. This is the easy part. What might be surprises
are the g7-g8 effects, which work on the x axis, and that would not be
ideal. So G8 s/b hard coded somehow.
Next of course would be touch-offs, but if the config is done right,
should not be a problem.
What surprise gotcha's would I be likely to find?
Was there some overriding reason the default lathe configs weren't done
this way in the first place?
Cheers, Gene Heskett
Gene Heskett
2017-06-29 16:55:43 UTC
Permalink
Raw Message
Post by Les Newell
Hi Gene,
G8 is hard coded to work on X axis. It doesn't really make sense for
any other axis. Could you swap the axes in your config?
With a separate config, yes, no problem that I am aware of. I'd have to
remove the lathe=1 in the ini file of course.
Post by Les Newell
Lathe uses X-Z because lathes are essentially treated as milling
machines on their side. By convention Z is parallel to the spindle axis.
Les
Should this not have been y/z in that case? :)
Post by Les Newell
Post by Gene Heskett
Greetings All;
Because the G5.x stuff hasn't had much TLC (probably from lack of
general use by the artisticly inclined among us) since it was
intro'd back in the mists of time, and is locked to x/y only
motions, the thought has come to mind of creating a special config
where x is carriage motion on the bed, and y is crossfeed.
Essentially duplicating a milling machine's xy motions. This is the
easy part. What might be surprises are the g7-g8 effects, which
work on the x axis, and that would not be ideal. So G8 s/b hard
coded somehow.
Next of course would be touch-offs, but if the config is done right,
should not be a problem.
What surprise gotcha's would I be likely to find?
Was there some overriding reason the default lathe configs weren't
done this way in the first place?
Cheers, Gene Heskett
----------------------------------------------------------------------
-------- 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
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Les Newell
2017-07-01 14:54:21 UTC
Permalink
Raw Message
Here are a couple of patches for mb2hal. One fixes the excessive CPU
load. On my machine it took CPU load from 60% to 0%. The other adds an
option to give pins names rather than numbers.

Les
Sebastian Kuzminsky
2017-07-01 16:13:59 UTC
Permalink
Raw Message
Post by Les Newell
Here are a couple of patches for mb2hal. One fixes the excessive CPU
load. On my machine it took CPU load from 60% to 0%. The other adds an
option to give pins names rather than numbers.
Thanks for this patch set.

I tried to apply it with "git am", but something must have gone wrong,
Post by Les Newell
Patch format detection failed.
I'm using git 2.11.0, I see you're using 2.7.4.

How did you generate these patch files? How did they get from git into
your email client?

As a fallback if we can't get the patch/email thing to work, do you have
a public git repo somewhere that I can pull from?
--
Sebastian Kuzminsky
Sebastian Kuzminsky
2017-07-01 16:18:24 UTC
Permalink
Raw Message
Post by Sebastian Kuzminsky
Post by Les Newell
Here are a couple of patches for mb2hal. One fixes the excessive CPU
load. On my machine it took CPU load from 60% to 0%. The other adds an
option to give pins names rather than numbers.
Thanks for this patch set.
I tried to apply it with "git am", but something must have gone wrong,
Post by Les Newell
Patch format detection failed.
I'm using git 2.11.0, I see you're using 2.7.4.
How did you generate these patch files? How did they get from git into
your email client?
Ah, it looks like maybe you generated them with "git log -p"? The
preferred method for packaging commits for email is "git format-patch",
as briefly mentioned here:

http://linuxcnc.org/docs/devel/html/code/contributing-to-linuxcnc.html#_overview_of_the_process

If you want i can apply your patches with "git apply", which will
preserve the diff but will not preserve your authorship information (and
i'll have to copy your commit message by hand).

Or if you don't mind, re-generate the patches with "git format-patch"
and email them to me, and I'll apply them with "git am" and it will
preserve everything.
--
Sebastian Kuzminsky
Loading...