Hi,
I proposed the problem of manual tool change and offset determination some
time ago, I have a small mill (always an MF70) without tool holders, so I'm
very interested.
I'm happy to see there is a first solution for the problem now.
Maybe I will be able to test it in a couple of days.
thanks
Gentlemen,
A lights out machine using probing will have XY registers for each
tool's probing position. This will allow any tool to be probed. They
will usually probe the tool after every tool change to detect broken
tools.
This will also verify the correct tool is in the spindle. An
operato
Greetings Guys;
Dean, I have that probe built, many thanks for the idea, and now waiting on
digikey for the optical stuff, I bought 5 of them so I can make some limit
switches too.
Here I'm working from memory, the printout is out in the shop, so I could have
the numbers wrong.
One concern I
On Mon, Apr 30, 2007 at 10:12:33AM -0400, Gene Heskett wrote:
> What strikes me as a rather severe limitation to this concept is the apparent
> lack of just using a logfile for the results
See page 140 of the user manual
-
> S#101
> (debug,Set knob to #101)
> M0
Not with 2.14, which is what I normally use, but it's fine
in CVS Head. I'd puzzled out the debug "comment" from your
examples while fiddling with those stepper glitches, but
found it didn't work with 2.14 and (sigh) forgot it.
Minor quibble: It Would Be
On Monday 30 April 2007, Chris Radek wrote:
>On Mon, Apr 30, 2007 at 10:12:33AM -0400, Gene Heskett wrote:
>> What strikes me as a rather severe limitation to this concept is the
>> apparent lack of just using a logfile for the results
>
>See page 140 of the user manual
Duh, that will teach me to
Hello,
I started tuning my new system using halscope and plotting ferror, commanded
position, and feedback position. Things are going well, however I can not
decipher the units of the vertical scale. It shows ferror in m/div this can
not be meters.
Thanks
Richard
---
richard harris wrote:
> Hello,
>
> I started tuning my new system using halscope and plotting ferror,
> commanded position, and feedback position. Things are going well,
> however I can not decipher the units of the vertical scale. It shows
> ferror in m/div this can not be meters.
it is mill
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 an
On Mon, Apr 30, 2007 at 07:15:33PM +0200, Sven Mueller wrote:
> BTW: Can I tell EMC2 to automatically go to a specified position on M06
> execution so that I could change the tool manually, waiting for
> confirmation from me? I might have overlooked it, but I couldn't find
> this information in the
Jon Elson wrote:
> richard harris wrote:
>> Hello,
>>
>> I started tuning my new system using halscope and plotting ferror,
>> commanded position, and feedback position. Things are going well,
>> however I can not decipher the units of the vertical scale. It shows
>> ferror in m/div this can n
On Sun, 2007-04-29 at 21:05 +0800, 杜少华 wrote:
> Every time I start the emc2,it reports that unexpected time delay.
I has this problem as well & fixed it by replacing the video card.
The system was a 400MHz P2 on an Intel Seattle2 motherboard with an AGP
bus S3 VGA card. I replaced the S3 card wi
Gene, I think what you want to do now is generate a g-code file
that moves to all the points on the grid of the region that you want to
scan.
The fragment below shows raster in y direction at .1 unit intervals, from a
rapid height of .5 in z
(PROBEOPEN probefile.txt)
G00 X 1.0 Y 1.0 Z 0.5
G38.
On Monday 30 April 2007, Dean Hedin wrote:
>Gene, I think what you want to do now is generate a g-code file
>that moves to all the points on the grid of the region that you want to
>scan.
>
>The fragment below shows raster in y direction at .1 unit intervals, from a
>rapid height of .5 in z
>
>(PR
> And something that would be better done, and with fewer mistakes, with
> a filter program of some sort. If I have to write it, well, my C is a
> little
> rusty but I think I could come up with something that works eventually.
This is basically what my emcprobe program did in EMC1:
You told it
15 matches
Mail list logo
