cticalmachinist cnc forum too.
-- Ralph
From: andy pugh [bodge...@gmail.com]
Sent: Monday, May 19, 2014 2:06 AM
To: Enhanced Machine Controller (EMC)
Subject: Re: [Emc-users] Lathe Threading
On 19 May 2014 08:27, Dave Caroline wrote:
> The ramps are es
On 19 May 2014 08:27, Dave Caroline wrote:
> The ramps are essential for full strength as they remove the need for
> a safety groove
You don't need a safety groove anyway with a conventional threading
operation, the retract move seems consistent.
I am prepared to believe that a taper-out might gi
The ramps are essential for full strength as they remove the need for
a safety groove
Dave Caroline
On 19/05/2014, Steve Blackmore wrote:
> On Sun, 18 May 2014 12:45:08 -0700, you wrote:
>
>>I'm still not seeing why G76 has a entry and exit ramp. I believe the
>>intent was to deal with Z acceler
On Sun, 18 May 2014 12:45:08 -0700, you wrote:
>I'm still not seeing why G76 has a entry and exit ramp. I believe the
>intent was to deal with Z acceleration time where the helix is not valid
>at the start (and I assume the end) of synchronized motion. Normally,
>one would start the thread off
I'm still not seeing why G76 has a entry and exit ramp. I believe the
intent was to deal with Z acceleration time where the helix is not valid
at the start (and I assume the end) of synchronized motion. Normally,
one would start the thread off the part enough to have the Z and spindle
locations
jumpers on the Mesa card has to correspond to the encoder type
> >>>> (differential line driver or TTL) otherwise nothing will work right.
> >>>>
> >>>> Dave
> >>>>
> >>>>
> >>>>
> >>>> On 6/9/2012
TTL
>>>> outputs.
>>>>
>>>> The jumpers on the Mesa card has to correspond to the encoder type
>>>> (differential line driver or TTL) otherwise nothing will work right.
>>>>
>>>> Dave
>>>>
>>>>
>>>
s on the Mesa card has to correspond to the encoder type
>>>> (differential line driver or TTL) otherwise nothing will work right.
>>>>
>>>> Dave
>>>>
>>>>
>>>>
>>>> On 6/9/2012 3:08 PM, Peter C. Wallace wrote:
>&
rs on the Mesa card has to correspond to the encoder type
>>> (differential line driver or TTL) otherwise nothing will work right.
>>>
>>> Dave
>>>
>>>
>>>
>>> On 6/9/2012 3:08 PM, Peter C. Wallace wrote:
>>>> On Sat, 9 Ju
hing will work right.
>>
>> Dave
>>
>>
>>
>> On 6/9/2012 3:08 PM, Peter C. Wallace wrote:
>>> On Sat, 9 Jun 2012, Brian May wrote:
>>>
>>>
>>>> Date: Sat, 9 Jun 2012 12:21:08 -0600
>>>> From: Brian May
>>>
9 Jun 2012 12:21:08 -0600
> >> From: Brian May
> >> Reply-To: "Enhanced Machine Controller (EMC)"
> >>
> >> To: "Enhanced Machine Controller (EMC)" >
> >> Subject: Re: [Emc-users] Lathe Threading
> >>
> >> Low
. Wallace wrote:
> On Sat, 9 Jun 2012, Brian May wrote:
>
>
>> Date: Sat, 9 Jun 2012 12:21:08 -0600
>> From: Brian May
>> Reply-To: "Enhanced Machine Controller (EMC)"
>>
>> To: "Enhanced Machine Controller (EMC)"
>> Subject:
e: Sat, 9 Jun 2012 12:21:08 -0600
>>> From: Brian May
>>> Reply-To: "Enhanced Machine Controller (EMC)"
>>>
>>> To: "Enhanced Machine Controller (EMC)"
>>> Subject: Re: [Emc-users] Lathe Threading
>>>
>>> Low
anced Machine Controller (EMC)"
> >
> > To: emc-users@lists.sourceforge.net
> > Subject: Re: [Emc-users] Lathe Threading
> >
> > On Saturday, June 09, 2012 04:11:29 PM Brian May did opine:
> >
> >> Low Level is 220mv
> >> High
On Sat, 9 Jun 2012, gene heskett wrote:
> Date: Sat, 9 Jun 2012 16:15:45 -0400
> From: gene heskett
> Reply-To: "Enhanced Machine Controller (EMC)"
>
> To: emc-users@lists.sourceforge.net
> Subject: Re: [Emc-users] Lathe Threading
>
> On Saturday, June
an May
> > > Reply-To: "Enhanced Machine Controller (EMC)"
> > >
> > >
> > >
> > > To: "Enhanced Machine Controller (EMC)"
> > > > >
> > > Subject: Re: [Emc-users] Lathe Threading
> > >
> > >
I do not have anything connected to classicladder now.
I can see the index (In hal scope) when jogging the axis slowly. (By
slowly I mean 4RPM). Any faster, the index is not consistent.
On Sat, Jun 9, 2012 at 1:48 PM, andy pugh wrote:
> On 9 June 2012 18:00, Brian May wrote:
>
> > So now I h
On 9 June 2012 18:00, Brian May wrote:
> So now I have the encoder using the hostmot driver and also the Z Pulse
> being read by the encoder component. I turned the spindle on at 120RPM and
> expected to read the counter of the encoder component counting 2 counts
> every second. It did not, It
ly-To: "Enhanced Machine Controller (EMC)"
>>
>> To: "Enhanced Machine Controller (EMC)"
>> Subject: Re: [Emc-users] Lathe Threading
>>
>> Low Level is 220mv
>> High Level 3.12 Volts
>
> Well thats valid TTL so OK (as long as the 7I3
On Sat, 9 Jun 2012, Brian May wrote:
> Date: Sat, 9 Jun 2012 12:21:08 -0600
> From: Brian May
> Reply-To: "Enhanced Machine Controller (EMC)"
>
> To: "Enhanced Machine Controller (EMC)"
> Subject: Re: [Emc-users] Lathe Threading
>
> Low Level i
> >
> > To: "Enhanced Machine Controller (EMC)" >
> > Subject: Re: [Emc-users] Lathe Threading
> >
> > I looked at the configuration CHNC and it looks the same.
> >
> > I followed andy's advice and found that the z-pulse is on pin 4. So
> Reply-To: "Enhanced Machine Controller (EMC)"
> >
> > To: "Enhanced Machine Controller (EMC)" >
> > Subject: Re: [Emc-users] Lathe Threading
> >
> > I looked at the configuration CHNC and it looks the same.
> >
> > I followed
On Sat, 9 Jun 2012, Brian May wrote:
> Date: Sat, 9 Jun 2012 11:00:22 -0600
> From: Brian May
> Reply-To: "Enhanced Machine Controller (EMC)"
>
> To: "Enhanced Machine Controller (EMC)"
> Subject: Re: [Emc-users] Lathe Threading
>
> I looked at
Sounds like you need a new encoder.
I've seen encoders break like that - they get intermittent. I have no
idea why.
Dave
On 6/9/2012 1:00 PM, Brian May wrote:
> I looked at the configuration CHNC and it looks the same.
>
> I followed andy's advice and found that the z-pulse is on pin 4. So I
I looked at the configuration CHNC and it looks the same.
I followed andy's advice and found that the z-pulse is on pin 4. So I
connected pin 4, (Z Pulse) to an encoder component A phase (encoder.0).
Then set the encoder component to counter mode.
So now I have the encoder using the hostmot driv
I have my CHNC lathe converted using 5i20 7i33 7i77 and all the wiring
of the cards and my config files are here if you want to compare notes.
http://gnipsel.com/shop/hardinge/hardinge.xhtml
John
On 6/8/2012 8:39 PM, Brian May wrote:
> I am having trouble setting up threading on my lathe. At t
Ok i will try that tomorrow...
Sent from my iPod
On Jun 8, 2012, at 8:58 PM, andy pugh wrote:
> On 9 June 2012 03:23, Brian May wrote:
>
>> I do not see in hal a index pin for the 5i20 component.
>
> You won't see it as a named pin, but all the function pins are also
> available as gpio.
> S
Brian,
You might want to change the mode of the counter in the Mesa card to a
single channel counter (non quadrature) and hook the index pulse to that
channel. Then see if the Index pulse is counting reliably - 1 count
per rev.
(I think you can change that Mesa card to a single channel counte
On 9 June 2012 03:23, Brian May wrote:
> I do not see in hal a index pin for the 5i20 component.
You won't see it as a named pin, but all the function pins are also
available as gpio.
So, in dmesg after booting into the config you will see a list of all
the function pins, and their corresponding
On Friday, June 08, 2012 10:21:38 PM Brian May did opine:
> I am having trouble setting up threading on my lathe. At this point I
> am thinking my spindle encoder is bad. I have the following setup in
> my HAL File:
>
> net spindle-revs hm2_[HOSTMOT2](BOARD).0.encoder.01.position
> motion.spind
It is wired up. I don't really know how to see if it is working.. I tried
connectimg it to a io port and create a latching circuit in classicladder to
see if it was sending a signal. I turned the encoder by hand and it would
latch the circuit every few turns. I may have had a timing issue...
On 9 June 2012 02:39, Brian May wrote:
> Am I missing something simple?
Is the encoder index channel wired up and working?
--
atp
If you can't fix it, you don't own it.
http://www.ifixit.com/Manifesto
--
Live Security
I am having trouble setting up threading on my lathe. At this point I am
thinking my spindle encoder is bad. I have the following setup in my HAL
File:
net spindle-revs hm2_[HOSTMOT2](BOARD).0.encoder.01.position
motion.spindle-revs
net spindle-vel-fb scale.0.in motion.spindle-speed-in
hm2_[HOST
>>battled with other "popular and cheap" software for many years (of
frustration)
I was waiting on lathe threading with Brand M software for a couple of years.
Many are still waiting. But when version 4 of Brand M software comes out, the
earth will quake, biblical revelations will occur, and
Andy
Thanks very much for the info on setup for lathe threading, and for the link
to a lot more info on the subject.
I got the setup going within a few minutes after reading your proposals.
The only extra thing I did was to put the input pin from my one-pulse-per-
rev sensor on both the phase-A a
Kirk Wallace wrote:
> If it makes any difference, I was cutting air, but I can imagine that
> there are other hardware load sources.
Ok, well, that excuses the spindle. It seems that the peak error was
.0005", so I wouldn't get too concerned about it.
You could look to see if the INPUT to the Z d
On Sun, 2009-04-26 at 11:33 -0500, Jon Elson wrote:
> Kirk Wallace wrote:
> > This is what I got with 2.3.0 and the previous threading sample with
> > 4=0.08333 at 400 RPM:
> >
> > http://www.wallacecompany.com/machine_shop/HNC/HALscope_2.3_threading.png
> >
> > Previous (2.2.8):
> >
> > http://ww
Kirk Wallace wrote:
> This is what I got with 2.3.0 and the previous threading sample with
> 4=0.08333 at 400 RPM:
>
> http://www.wallacecompany.com/machine_shop/HNC/HALscope_2.3_threading.png
>
> Previous (2.2.8):
>
> http://www.wallacecompany.com/machine_shop/HNC/4at08-2.png
>
> 2.3.0 seems
On Wed, 2009-04-22 at 18:38 -0500, Chris Radek wrote:
> On Wed, Apr 22, 2009 at 02:04:55PM -0700, Kirk Wallace wrote:
> >
> > I tend to think my threading problem is due to the "relay runner"
> > effect
>
> I think so too - sure looks nasty though. I bet you will have much
> better luck with 2.3
Kirk Wallace wrote:
> I tend to think my threading problem is due to the "relay runner"
> effect, but just in case it might be helpful. I tried the above on my
> HNC. This didn't seem to change much.
>
> This is the before, with 4=0.08333:
> http://www.wallacecompany.com/machine_shop/HNC/4at08
On Wed, 2009-04-22 at 18:38 -0500, Chris Radek wrote:
> On Wed, Apr 22, 2009 at 02:04:55PM -0700, Kirk Wallace wrote:
> >
> > I tend to think my threading problem is due to the "relay runner"
> > effect
>
> I think so too - sure looks nasty though. I bet you will have much
> better luck with 2.3
On Wed, Apr 22, 2009 at 02:04:55PM -0700, Kirk Wallace wrote:
>
> I tend to think my threading problem is due to the "relay runner"
> effect
I think so too - sure looks nasty though. I bet you will have much
better luck with 2.3 (this effect is why I rewrote the threading
sync.)
--
On Mon, 2009-04-20 at 20:56 -0500, Jon Elson wrote:
... snip
> That is in the univpwm_load.hal file, the line I have reads :
>
> loadrt [EMCMOT]EMCMOT base_period_nsec=[EMCMOT]BASE_PERIOD
> servo_period_nsec=[EMCMOT]SERVO_PERIOD
> traj_period_nsec=[EMCMOT]SERVO_PERIOD key=[EMCMOT]SHMEM_KEY
>
> Yo
Kirk Wallace wrote:
>
> I wonder if Harris' rapid is fast enough to get across the thread, where
> in my tests I got half way (4=0.08333) before the HNC tried to correct
> the rate? If I used 4=0.120 I might have gotten the same result, since
> decreasing 4 also reduced the effect.
>
As I mentio
On Mon, 2009-04-20 at 20:56 -0500, Jon Elson wrote:
... snip
> One other thing We found this change
> to be MOST helpful for rigid tapping, but I believe it ALSO is very
> helpful in any threading operation. That was to increase the trajectory
> planner's dispatch rate (TRAJ_PERIOD) to equ
Kirk Wallace wrote:
>
>
> I think in my case at least, I'm asking for impossible accelerations.
> When I looked at this before:
>
> http://www.wallacecompany.com/cnc_lathe/HNC/emc2/spindle_sync_surge-1b.png
>
> I decided to allow enough lead-in to have the Z settle before cutting.
>
>
Well, the
On Fri, 2009-04-17 at 11:38 -0500, Jon Elson wrote:
> Kirk Wallace wrote:
> > Whatever it is, it looks like I have it too. I ran the long version four
> > times with #4=0.050 without any problems. Then before shutting down for
> > the night, I ran one part at #4=0.08. At the start of the thread
Kirk Wallace wrote:
>
> Whatever it is, it looks like I have it too. I ran the long version four
> times with #4=0.050 without any problems. Then before shutting down for
> the night, I ran one part at #4=0.08. At the start of the thread the
> Z would aggressively move then almost come to a s
On Thu, 16 Apr 2009 22:40:07 -0700, you wrote:
>> which sets up for 20 TPI. I ran it like that first, then changed the
>> value to .08333 to get 12 TPI.
Just a thought - try changing that 0.08333 to 0.084 and see if it still
misbehaves.
Steve Blackmore
--
---
Kirk Wallace wrote:
> Whatever it is, it looks like I have it too. I ran the long version four
> times with #4=0.050 without any problems. Then before shutting down for
> the night, I ran one part at #4=0.08. At the start of the thread the
> Z would aggressively move then almost come to a stop
On Wed, 2009-04-15 at 11:20 -0500, Jon Elson wrote:
> Kirk Wallace wrote:
> > On Tue, 2009-04-14 at 20:57 -0500, Jon Elson wrote:
> > ... snip
> >
> >> problem, but I made the final fix at the 2007 EMC-Fest, and the driver
> >> fixes were in the July 2007 release of EMC2. So, I wanted to see i
Kirk Wallace wrote:
> On Tue, 2009-04-14 at 20:57 -0500, Jon Elson wrote:
> ... snip
>
>> problem, but I made the final fix at the 2007 EMC-Fest, and the driver
>> fixes were in the July 2007 release of EMC2. So, I wanted to see if
>> anyone else was seeing similar problems. Also, I don't se
On Tue, 2009-04-14 at 20:57 -0500, Jon Elson wrote:
... snip
> problem, but I made the final fix at the 2007 EMC-Fest, and the driver
> fixes were in the July 2007 release of EMC2. So, I wanted to see if
> anyone else was seeing similar problems. Also, I don't see why the
> spindle sync would
On Tue, Apr 14, 2009 at 08:57:36PM -0500, Jon Elson wrote:
> My real concern is Mr. Harris' problem with the encoder counter
> sometimes missing the reset on index, while it sets the bit saying that
> it has done so. An earlier version of the firmware/driver had this
> problem, but I made the
Steve Blackmore wrote:
> On Tue, 14 Apr 2009 12:28:48 -0500, you wrote:
>
>
>
>>> Have you tried with plain Gcode? That is a horribly complex piece of
>>> code and it's possible the error may be associated with the math
>>> involved.
>>>
>>>
>>>
>> But, It woks FINE for me!
>>
>
On Tue, 14 Apr 2009 12:28:48 -0500, you wrote:
>> Have you tried with plain Gcode? That is a horribly complex piece of
>> code and it's possible the error may be associated with the math
>> involved.
>>
>>
>But, It woks FINE for me!
I thought YOU said
>One interesting quirk I did see was t
Steve Blackmore wrote:
> On Mon, 13 Apr 2009 21:48:40 -0500, you wrote:
>
>
>
>> I just ran several pieces at 12 TPI, using a program derived from the
>> EMC sample program threading.ngc
>>
>
> Have you tried with plain Gcode? That is a horribly complex piece of
> code and it's possible th
On Mon, 13 Apr 2009 21:48:40 -0500, you wrote:
>I just ran several pieces at 12 TPI, using a program derived from the
>EMC sample program threading.ngc
Have you tried with plain Gcode? That is a horribly complex piece of
code and it's possible the error may be associated with the math
involved.
On Mon, Apr 13, 2009 at 09:48:40PM -0500, Jon Elson wrote:
> richard harris wrote:
> > Jon,
> >
> > i got a chance to run halscope today and on coarse threads <13 tpi it
> > will occasionally not reset the encoder count, count is numerically
> > low when it does reset 25k. I do not see this when
I'm quoting a message from an EMC user to see if anyone else has seen
any signs of this problem.
richard harris wrote:
> Jon,
>
> i got a chance to run halscope today and on coarse threads <13 tpi it
> will occasionally not reset the encoder count, count is numerically
> low when it does reset
On Fri, 2009-03-20 at 23:42 -0500, Jon Elson wrote:
... snip
> have such a problem. Kirk Wallace is also using a UPC board on a lathe,
> but I don't know if he is doing a lot of threading. Maybe you should
> send me your threading program and I will try it here on the minimill.
> Is your mach
richard harris wrote:
> I am running Elson's servo system and
> EMC 2.2.6.
>
> Over the last few days I have run
> several hundred parts single point threading a M22x1.5 threads
> without a single bad thread. Yesterday I switched to cutting a
> M20x2.5 and suddenly on ever other part the lathe w
On Fri, Mar 20, 2009 at 03:15:41PM -0700, richard harris wrote:
>
> I am running Elson's servo system and
> EMC 2.2.6.
>
> Over the last few days I have run
> several hundred parts single point threading a M22x1.5 threads
> without a single bad thread. Yesterday I switched to cutting a
> M20x2
I am running Elson's servo system and
EMC 2.2.6.
Over the last few days I have run
several hundred parts single point threading a M22x1.5 threads
without a single bad thread. Yesterday I switched to cutting a
M20x2.5 an
On Fri, 2008-08-15 at 23:13 +0200, josep M. giili freixa wrote:
> i have a lathe retrofited whit servos. I tried to run it whit Mach3
> but i have problems when threading. Now testing Emc2 but when
> configuring it whit Stepwizard all run fine except threading. Gcode
> stops in g76 line waithing f
i have a lathe retrofited whit servos. I tried to run it whit Mach3 but i have
problems when threading. Now testing Emc2 but when configuring it whit
Stepwizard all run fine except threading. Gcode stops in g76 line waithing for
spindle sincro.
I`m unable the get a explanation in the manuals o
On Wed, Oct 10, 2007 at 10:24:31AM -0700, Kirk Wallace wrote:
>
> I meant to have the process running in the background, all the time so
> that if you are making a part, it can detect the fault before it is
> finished.
With hardware counting, it would be only for very slow speeds that emc
would s
On Wed, 2007-10-10 at 12:06 -0500, Jon Elson wrote:
> Kirk Wallace wrote:
> > On Mon, 2007-10-08 at 21:52 -0500, Jon Elson wrote:
> > ... snip
... snip
> > count against the index. If index doesn't appear when the count predicts
> > it, a warning could be issued.
> >
>
> You could pretty easily
Kirk Wallace wrote:
> On Mon, 2007-10-08 at 21:52 -0500, Jon Elson wrote:
> ... snip
>
>>>problem? Maybe missing pulses or noise adding pulses? Thanks for any
>>>replies.
>>
>>It could be anything, so you have to investigate. First, put
>>halmeter on the HAL pin ppmc.0.encoder.2.count, rotate t
On Mon, 2007-10-08 at 21:52 -0500, Jon Elson wrote:
... snip
> > problem? Maybe missing pulses or noise adding pulses? Thanks for any
> > replies.
> It could be anything, so you have to investigate. First, put
> halmeter on the HAL pin ppmc.0.encoder.2.count, rotate the
> spindle to a known pos
On Mon, 2007-10-08 at 15:12 -0500, Chris Radek wrote:
> 1250 seems like a strange number. Are you sure? (If that is right,
> your 5000 setting is correct)
I believe I ordered the U. S. Digital one inch 1250 cpr disk, but now
that you mention it, I should check it to make sure. They have
twenty-
Chris Radek wrote:
> On Mon, Oct 08, 2007 at 12:31:42PM -0700, Kirk Wallace wrote:
>
>
>>My thinking is that INPUT_SCALE should not need to be adjusted by cut
>>and try, so if the thread tpi is not correct, it must be an encoder
>>problem? Maybe missing pulses or noise adding pulses? Thanks for
Jon Elson wrote:
>[snipped good debugging information]
>
>If you haven't done the servo tuning yet, you have no business
>putting a cutter and workpiece in the machine, it could be half
>an inch out of position and you wouldn't know.
>
>
I don't think this is the case. Since there's encoder f
Kirk Wallace wrote:
> I did my first CNC lathe thread today. I actually got a thread which, on
> a first try, I didn't expect. I entered parameters for a 20 tpi thread
> and got something like 23 tpi. When I setup the spindle parameters in
> the ini file, I assumed that the encoder input scale shou
On Mon, Oct 08, 2007 at 12:31:42PM -0700, Kirk Wallace wrote:
> My thinking is that INPUT_SCALE should not need to be adjusted by cut
> and try, so if the thread tpi is not correct, it must be an encoder
> problem? Maybe missing pulses or noise adding pulses? Thanks for any
> replies.
I agree, y
I did my first CNC lathe thread today. I actually got a thread which, on
a first try, I didn't expect. I entered parameters for a 20 tpi thread
and got something like 23 tpi. When I setup the spindle parameters in
the ini file, I assumed that the encoder input scale should equal the
number of pulse
m: [EMAIL PROTECTED]
> > To: emc-users@lists.sourceforge.net
> > Date: Fri, 29 Jun 2007 11:23:36 -0500
> > Subject: [Emc-users] Lathe Threading
> >
> > First of all, thank you developers for EMC and thank you John Kasunich
> > for getting the m5i20 threading working
re at
all-if you are careful. It all really depends on how good a fit you need and
how much time you want to spend and what you have for tools!
Cheers
Chris Morley
> From: [EMAIL PROTECTED]> To: emc-users@lists.sourceforge.net> Date: Fri, 29
> Jun 2007 11:23:36 -0500> Subjec
Andre' Blanchard wrote:
> At 11:23 AM 6/29/2007, you wrote:
>> trial and error. I have a project of machining a back plate for an L&W
>> dividing head, the thread is 2-1/4 10tpi. I dread test fitting the
>> dividing head to the back plate!
>>
>> Roger Neal
>>
>
> Make up a few simple rings from
At 11:23 AM 6/29/2007, you wrote:
>trial and error. I have a project of machining a back plate for an L&W
>dividing head, the thread is 2-1/4 10tpi. I dread test fitting the
>dividing head to the back plate!
>
>Roger Neal
>
Make up a few simple rings from scrap and do a trial run or three. Then
First of all, thank you developers for EMC and thank you John Kasunich
for getting the m5i20 threading working. I loaded the pre 2.1.7 version
and built it on my pc, the threading worked first try, I only had to
change my old latch-index to index-enable and then tested it out, I now
have a lat
Isak Levinson wrote:
> Hi All,
>
> Is it possible to make threads in EMC2?
> In the user manual it says that it is possible, but I can't figure out how to
> do it.
Of course, you have to have an encoder on the spindle.
And, you have to provide a way to feed this encoder information
back to the co
On Thu, May 24, 2007 at 05:46:02AM -0700, Isak Levinson wrote:
> Does the index output need to be one pulse per revolution?
> Can it be similar to what there is in mach2 program: several pulses per rev
> with one pulse wider than the others.
Right now, only a spindle with encoder and index pulse
TED]>
To: Isak Levinson <[EMAIL PROTECTED]>; Enhanced Machine Controller (EMC)
Sent: Thursday, May 24, 2007 3:37:16 PM
Subject: Re: [Emc-users] Lathe Threading in EMC
Yes, it is possible. You need a spindle with encoder and index pulse
output. The sample configuration "nist-lath
Yes, it is possible. You need a spindle with encoder and index pulse
output. The sample configuration "nist-lathe" shows the necessary HAL
configuration when the encoder is connected to parport pins 11, 12, and
13.
The sample ngc file "threading.ngc" uses a bunch of G33 (spindle
synchronized mot
On Thu, May 24, 2007 at 04:10:52AM -0700, Isak Levinson wrote:
> Hi All,
>
> Is it possible to make threads in EMC2?
Yes, there's a basic threading move (G33) and a threading cycle with
many features (G76).
> In the user manual it says that it is possible, but I can't figure out how to
> do it.
Hi All,
Is it possible to make threads in EMC2?
In the user manual it says that it is possible, but I can't figure out how to
do it.
Thanks, Isak.
Boardwalk
for $500? In 2007? Ha! Play Monopoly Here an
87 matches
Mail list logo
