Jon Elson wrote on 28/11/2007 04:05:
I think the above quoted text should read Only one offset word
is required. You definitely can have two. I think with the
in-plane only arcs that EMC does, you can't have 3. Some
controls allow arcs in arbitrary planes, and you can have an arc
move
Chris Radek wrote on 08/11/2007 21:05:
Hi all, I don't want to distract everyone from EMC2.2 but I've done
some fun stuff in TRUNK (pre-2.3) with probing. I don't think many
people are using probes but I know some are, and they might like to
try it. I'd appreciate any reports of success or
Dale schrieb:
have you tried Eagle PCB from cadsoftusa.com there is a free for
non-comercial use. There may be a User Language Program or a built in
Greber converter. If you can get it into eagle then milling a PCB is easy.
At least there is pcb-gcode which outputs nice gcode from layouts.
Hi.
A nice feature my previous cnc software (PC/NC from lewetz.de) had was
the option to limit the rate at which Z travelled down (on
non-G00/non-Homing moves only). This made sure that even if I accidently
programmed a too high feed rate, I still wouldn't break the tool just by
sinking it into
Jeff Epler schrieb:
On Wed, Aug 15, 2007 at 03:16:35PM +0200, Sven Mueller wrote:
Ask user to define minimum and maximum X, Y and Z positions by moving
the tooltip to the relevant positions manually or by entering the values
numerically. Then use a procedural (possibly recursive) approach
Jeff Epler schrieb:
AXIS can automatically execute a filter program when loading a
machinable file. You can also use the NML messages for issuing MDI
commands to feed your program in line-by-line. (I just verified that,
at least in the development version of emc 2, this doesn't kill blending
Kenneth Lerman schrieb:
What is it that you imagined? Other than the fact that o-words are numeric
(on my list of work to do is allowing them to be alphanumeric), what else
would you like?
I don't know what Fenn would like to see, but here is a use case for
such a language which I currently
Alex Joni schrieb:
Ask user to define minimum and maximum X, Y and Z positions by moving
the tooltip to the relevant positions manually or by entering the values
numerically. Then use a procedural (possibly recursive) approach to scan
the work pieces surface with a touch probe.
Not the most
Hi.
I really don't know why this isn't working as it should, so I really
need some help here. I have taken the default stepper.ini and pinout.hal
files (both from the stepper directory) and adjusted them to my machine.
The files contain test in them since I intentionally didn't configure
homing
Thomas Powderly wrote on 01/07/2007 22:13:
Sven, you may want to boot the live cd and try the latency tests before
going further. If the on board video can be defeated, try a pci video
cardf and re-run the tests. Best of luck! let us know how it works,
Last weekend, we finally got around to
Hi.
I'm implementing my machine control on a ALIX.1b board from
pcengines.ch[0]. This board uses an AMD Geode LX and provides both a
standard parallel port and GPIO pins (exported from the Winbond W83627hf
Super I/O Controller). The driver for this chip in
drivers/hwmon/w83627hf.c provides access
Michael M. Butler wrote on 05/06/2007 18:24:
On 6/5/07, Jeff Epler [EMAIL PROTECTED] wrote:
The correct md5sum for that file is
2b99a5eb6b38d6bebcc1fa1b37ba7075 emc2-ubuntu6.06-desktop-i386.iso
and the size is 692107264 bytes. I just verified this, both on a copy
on my local system
Hi.
I'm a bit puzzeled about 23.4.12 (step over (pixels)).
What exactly does the step over distance specify? I'm not a native
speaker, so perhaps I don't understand the explanation good enough.
(Hint: Graphics explaining the parameters would be great at some places)
So, the explanation
John Kasunich wrote on 03/05/2007 22:56:
The general approach when using one parport pin to drive multiple
motion controller pins is to have the one pin drive a single signal
which then connects to multiple pins. One pin cannot drive multiple
signals, each of which drives a single pin.
Chris Radek schrieb:
Hi Sven, I've added this scheme to the emc2 cvs trunk. I can't test
it right now but maybe I can set up something one of these days.
Cool thanks.
It will probably take another week or two until I have a controller for
my machine that EMC2 could work with. And probably
Chris Radek wrote:
[probe moves]
It would be nice to be able to set tool length offset this way - but
currently there is no way to do that, since lengths need to come
from the tool table.
Hmm, I'm still mostly a newbie regarding EMC. But does the above mean
that EMC can't automatically
Chris Radek wrote:
Even if G43 can take a tool length directly, I couldn't come up with a
straightforward way for the user to use that in gcode. Imagining the
mill case first because it's simpler: maybe you'd store in a gcode
variable the Z coordinate you get when you probe your reference
Chris Radek schrieb:
On Sun, Apr 29, 2007 at 10:03:29AM -0500, Chris Radek wrote:
I don't know what the reference tool would be, and with no
reference tool I don't know what you'd use to touch-off the work.
Replying to myself! Is it as simple as
G49
insert any tool, touch off, set work
Dave Engvall schrieb:
Really tool length is just part of the problem. A tool number is
associated with both a tool length and
a tool diameter which may or may not be nominal.
Right, but a tools diameter doesn't change, no matter what you do while
you insert it. However, it's felt length
19 matches
Mail list logo
