On 3 August 2010 13:20, Erik Christiansen dva...@internode.on.net wrote:
Oh ... yes, I forgot about aligning the INT30 dogs when inserting the
toolholder. Still, that could at worst be done by running the spindle at
inching speed over a springloaded toolholder until it engages the
socket, as
On Mon, Aug 02, 2010 at 07:44:06PM +0100, Andy Pugh wrote:
On 2 August 2010 17:50, Schooner schoone...@tiscali.co.uk wrote:
I wrote a G Code sub routine called m6 which takes 2 parameters,
current_tool and required_tool.
Using G Code overcomes all the problems of trying to move a
On 3 August 2010 09:41, Erik Christiansen dva...@internode.on.net wrote:
On Mon, Aug 02, 2010 at 07:44:06PM +0100, Andy Pugh wrote:
I can't help thinking that using a G-code routine (and, in fact,
having the ATC defined as an axis) is sub-optimal.
What's the basis for that Andy? The method
On Tue, Aug 03, 2010 at 10:44:44AM +0100, Andy Pugh wrote:
On 3 August 2010 09:41, Erik Christiansen dva...@internode.on.net wrote:
On Mon, Aug 02, 2010 at 07:44:06PM +0100, Andy Pugh wrote:
I can't help thinking that using a G-code routine (and, in fact,
having the ATC defined as an axis)
Hi Again,
Just an update to the thread with the solution adopted.
I hate searching threads and never finding how it ended up being done.
I wrote a G Code sub routine called m6 which takes 2 parameters,
current_tool and required_tool.
This is no problem, as when you do a tool change you will
On 2 August 2010 17:50, Schooner schoone...@tiscali.co.uk wrote:
I wrote a G Code sub routine called m6 which takes 2 parameters,
current_tool and required_tool.
Using G Code overcomes all the problems of trying to move a previously
defined axis during a M6 command.
I can't help thinking
On Mon, 2010-08-02 at 19:44 +0100, Andy Pugh wrote:
... snip
I think that the comp file was the right approach. One useful and easy
modification to that would have been a pin that could be linked to the
X-axis homing state, so that it would do a full rotation while
watching a micoswitch linked
Hi again
I have spent a few days reading all the manuals etc and studying the
various links you all passed on.
I decided that Kirks solution of a component written in C was most
viable for me.
In the interim I have written a G Code sub routine called m6 which does
the tool change and I just
On 29 July 2010 16:32, Schooner schoone...@tiscali.co.uk wrote:
Below is my idea of how I could achieve the tool change with a component
and the associated .hal entries.
I have been thinking about this a bit, and your solution (not
unexpectedly) differs from mine.
One thing that I don't like
I really can't understand why they use a stepper for this task. There is
no need for expensive stepper drivers and mucking about with allowing
for lost pulses. A DC motor works easily as well if not better. Here is
a video of an Emco conversion I did.
http://www.youtube.com/watch?v=D4PrCejPbZ8
Hi again
Thanks for the various links and info, I will have to sit down and try to get
my head around them and work out the best strategy
John and Steve are correct about the way it operates.
It is a Boxford 240F and really it does not matter whether the motor loses
steps when locking back.
On 26 July 2010 04:40, Chris Morley chrisinnana...@hotmail.com wrote:
I wouldn't think this matters. Tool movement is relative not absolute.
You ask the stepgen to move +130 from where ever you are, then -40
till it hits a stop. The stop sets a new position and then you move relative
to
Hi Guys,
I have been searching the lists for info on setting up an ATC under EMC2.
I have found some references but nothing concrete as to how it is achieved.
This must be quite a common requirement, but can see nothing in the
wikis etc about doing it.
I have an 8 station revolving tool
On Sun, 2010-07-25 at 14:53 +0100, Schooner wrote:
Hi Guys,
I have been searching the lists for info on setting up an ATC under EMC2.
I have found some references but nothing concrete as to how it is achieved.
This must be quite a common requirement, but can see nothing in the
wikis etc
On 25 July 2010 14:53, Schooner schoone...@tiscali.co.uk wrote:
The ATC is currently assigned to axis A, so I could just write GCode to
achieve the same result, but would rather it responded properly to M6.
Can anyone point me to some info or tell me the secret?!
Toolchanging seems to be
On Sun, Jul 25, 2010 at 05:11:19PM +0100, Andy Pugh wrote:
Alternatively, you could do it all in G-code. (I think). Linking the
tool-change pin to an MDI_COMMAND pin (see
http://linuxcnc.org/docs/2.3/html/gui_halui.html#sub:MDI ) should
allow you to execute a G-code subroutine automatically
- Original Message -
From: Chris Radek ch...@timeguy.com
snip
I admit that I don't quite see how these tool changers are supposed to
work. When the stepper backs up against the stop, doesn't it stall
and lose position? Is there some kind of feedback available? When
you start up,
A separate Stepgen configured in Hal, setup in position mode, which is
driven by Classic Ladder should work.
ClassicLadder can monitor hal pins set by an Mcode (you can access the
M6 tool change hal pins via classic ladder and the hal configuration
file) and then respond by swinging the tool
On 25/07/2010 20:14, Dave wrote:
A separate Stepgen configured in Hal, setup in position mode, which is
driven by Classic Ladder should work.
yep this is how i did one for someone else the other weekend its very
crude what they did (this was a boxford) same changer as you are talking
On Sun, Jul 25, 2010 at 06:44:31PM +0100, John Prentice wrote:
For an 8 position turret you have a ratchet with 8 teeth and a spring-loaded
pawl. Assuming you know where you are now (say tool 2) and each click needs
100 steps.
To move to tool 5 you output 330 steps. You now know that
I don't know the physical requirements. If the pawl is not needed for
rigidity but is only used for positioning then with an encoder the pawl can
be removed.
On Sun, Jul 25, 2010 at 5:10 PM, Chris Radek ch...@timeguy.com wrote:
On Sun, Jul 25, 2010 at 06:44:31PM +0100, John Prentice wrote:
for such a simple
design. They were used by Southbend, Emco Maier,
and many others.
Steve Stallings
-Original Message-
From: Stuart Stevenson [mailto:stus...@gmail.com]
Sent: Sunday, July 25, 2010 6:33 PM
To: Enhanced Machine Controller (EMC)
Subject: Re: [Emc-users] Lathe ATC
On Sun, 2010-07-25 at 12:10 -0500, Chris Radek wrote:
I think the changer might be like this one:
http://www.youtube.com/watch?v=njRvzHUuL1I
--
Kirk Wallace
http://www.wallacecompany.com/machine_shop/
http://www.wallacecompany.com/E45/index.html
California, USA
If an encoder is being considered, this absolute encoder might be worth
a look:
http://www.avagotech.com/pages/en/motion_control_encoder_products/magnetic_encoders/aeat-6010/
(Short URL) http://alturl.com/aya7s
I don't think the resolution is high enough for final tool position, but
certainly
emc-users-requ...@lists.sourceforge.net wrote:
On 25 July 2010 14:53, Schooner schoone...@tiscali.co.uk wrote:
The ATC is currently assigned to axis A, so I could just write GCode to
achieve the same result, but would rather it responded properly to M6.
Can anyone point me to some info
On Sun, 25 Jul 2010 18:32:40 -0500, you wrote:
I don't know the physical requirements. If the pawl is not needed for
rigidity but is only used for positioning then with an encoder the pawl can
be removed.
The pawl and the and the worm gear work in combination are essential to
the rigidity.
OK, that's kind of what I was afraid of. Sounds like you need a
position mode stepgen, so you can issue the particular number of steps
you want. But when you are done with your +130 and -40, your position
mode stepgen doesn't know the position anymore because the motor has
stalled.
I
27 matches
Mail list logo
