Well, I finally got to test out the rigid tapping on real material, and
it works great!
I did 96 2-56 holes. Since it was thick material, I couldn't use the
combined drill-taps,
they are rated for 2 X the major diameter, and will do a little more if
you are careful.
You have to drill at a low f
John Kasunich wrote:
>
> The only way I know of would be with a custom M1xx code. It
> would invoke a script that does "helcmd setp the-param the-value"
>
> The value could come from a g-code and be passed to M1xx as a P or
> Q word. I don't see any way to pass the name though - each M1xx
> comma
On 30 April 2010 20:28, John Kasunich wrote:
> The only way I know of would be with a custom M1xx code. It
> would invoke a script that does "helcmd setp the-param the-value"
It seems odd that we can read DIO, write DIO and write AIO. There is
an asymmetry there.
Would it be difficult to add an
On Fri, 30 Apr 2010 11:00 -0500, "Jon Elson"
wrote:
> Kirk Wallace wrote:
> > Being able to set the ramp for different operations would be nice, maybe
> > in g-code?
> >
> Is there a way to set an arbitrary HAL parameter from G-code? I guess
> with macros you can do it.
>
The only way I k
Kirk Wallace wrote:
> Being able to set the ramp for different operations would be nice, maybe
> in g-code?
>
Is there a way to set an arbitrary HAL parameter from G-code? I guess
with macros you can do it.
Jon
--
__
John Kasunich wrote:
> 1) The lowpass component generates an exponential response, with the
> speed
> changing rapidly at the beginning of the transition and slowly at the
> end.
> If you use a limit2 block, the speed ramp rate will be constant.
Yes, I am aware of this, it was pointed out to me aft
On Fri, 2010-04-30 at 10:42 -0400, John Kasunich wrote:
... snip
> 2) Most VFDs let you set a ramp rate as a configuration parameter, so
> you don't need either the lowpass or the limit block in HAL.
... snip
Being able to set the ramp for different operations would be nice, maybe
in g-code?
--
K
On Thu, 29 Apr 2010 23:33 -0500, "Jon Elson"
wrote:
> My first cut at rigid tapping just jammed the VFD from forward to
> reverse command, which was so abrupt it caused Z-axis following errors
> at higher spindle speeds. I have a lowpass component in there also to
> make the speed change
I have wired up one of the PPMC DAC channels to control the VFD, and
added an abs HAL component to get the unipolar spindle speed command.
My first cut at rigid tapping just jammed the VFD from forward to
reverse command, which was so abrupt it caused Z-axis following errors
at higher spindle
RogerN wrote:
> I use speed feedback on my lathe, filtered it using existing Hal functions.
> On threading my counter gets reset (spindle encoder) and would be an
> enormous negative speed, I limited the rate of change of speed to be
> realistic, I don't allow it to go from 800rpm forward to mil
- Original Message -
From: "Jon Elson"
To: "Enhanced Machine Controller (EMC)"
Sent: Friday, April 23, 2010 11:23 AM
Subject: Re: [Emc-users] Bridgeport spindle encoder
> Andy Pugh wrote:
>> As for speed signal noise, my speed signal is fairly random,
Andy Pugh wrote:
> As for speed signal noise, my speed signal is fairly random, (it is a
> home-made encoder ring with slot-sensors) but using the right PID
> values seems to filter that effect adequately.
>
Well, I guess I will have to try this out.
> I have just thought of another way of doing
On 23 April 2010 04:00, Jon Elson wrote:
>
> Andy Pugh wrote:
>> ... with closed-loop spindle control you will automatically get the
>> spindle speed you ask for in the G-code regardless of which pulley and
>> back-gear combination you have selected,
> I understand the concept, but I'm not sure
Stephen Wille Padnos wrote:
> I think Jon's original comment was meant to say that a spindle encoder
> without index is no use at all for rigid tapping. Not that there is no
> use whatsoever for a spindle encoder without index.
>
Yup, that is my mindset right now, getting rigid tapping workin
Andy Pugh wrote:
> I seem to be failing to express myself clearly. What I am saying is
> that with closed-loop spindle control you will automatically get the
> spindle speed you ask for in the G-code regardless of which pulley and
> back-gear combination you have selected, as long as the speed
> re
Andy Pugh wrote:
> [snip]
> And this was only ever meant to be a throwaway comment aimed at the
> earlier statement that an encoder with no index is no use at all. ie
> that you can still use such an encoder to control and measure spindle
> speed.
>
I think Jon's original comment was meant to s
On 22 April 2010 17:19, Jon Elson wrote:
>
> Andy Pugh wrote:
>> Thing is, once you are doing that HAL-fiddling you might as well just
>> be running closed loop on the spindle speed
> I've had a tach on my Bridgeport for some time. I have noticed a drop
> of about 3 RPM under heavy load. So, I
Andy Pugh wrote:
> Thing is, once you are doing that HAL-fiddling you might as well just
> be running closed loop on the spindle speed which also automatically
> increases the slip speed as the load increases.
>
I've had a tach on my Bridgeport for some time. I have noticed a drop
of about 3 R
On 22 April 2010 04:16, Jon Elson wrote:
> I have 8 "gears", really 4 belt positions and direct-drive or
> back-gear. I've been thinking of putting a microswitch on the backgear
> handle and some long-distance photo detectors to sense the belt
> position. Then this would feed into a HAL mux to
Andy Pugh wrote:
> On 21 April 2010 16:48, Jon Elson wrote:
>
>
>> It is worthless without the index.
>>
>
> Not entirely worthless, you could still use if for closed-loop spindle
> speed control. This actually makes some sense with a geared head like
> the Bridgeport. My mill has two gear
On 21 April 2010 16:48, Jon Elson wrote:
> It is worthless without the index.
Not entirely worthless, you could still use if for closed-loop spindle
speed control. This actually makes some sense with a geared head like
the Bridgeport. My mill has two gears, but it doesn't matter which one
I enga
Kirk Wallace wrote:
> Good job. I'm looking forward to your write up. Is there an index on
> your spindle encoder?
>
It is worthless without the index. See
http://pico-systems.com/bridge_spindle.html
for the pics and info.
Jon
--
On Tue, 2010-04-20 at 22:43 -0500, Jon Elson wrote:
> Hey,
>
> I have just gotten a spindle encoder working on a Bridgeport 1J (step
> pulley) head.
... snip
Good job. I'm looking forward to your write up. Is there an index on
your spindle encoder?
--
Kirk Wallace
http://www.wallacecompany.com
Hey,
I have just gotten a spindle encoder working on a Bridgeport 1J (step
pulley) head. There's no sane way to couple to the spindle, the only
way is to install gear tooth sensors that read the teeth of the bull
gear. I am going to write up a web page on it in the next couple days.
I just g
24 matches
Mail list logo
