Stuart Stevenson wrote:
> Gentlemen,
> Thank you very much for including this function.
> After updating the emc2-head I am unable to start the axis display
> on my machine. The updated version will start the tkemc display. I
> have the configuration file tested for the axis display. I will
Gentlemen,
Thank you very much for including this function.
After updating the emc2-head I am unable to start the axis display
on my machine. The updated version will start the tkemc display. I
have the configuration file tested for the axis display. I will work
on this today with tkemc but
Stuart Stevenson wrote:
> Gentlemen,
> On one machine I have a handwheel without lines or
> detents. It holds position with a friction device.
I see why you aren't so worried about losing position then.
> Would someone write this and commit it?
Done. (In CVS head.)
I don't have a jogwheel
Gentlemen,
My definition of running is everything complete and turned over to
the shop. I have run the EMC2 AXIS program and used a grease pencil on
the quill to draw it on a piece of aluminum. I watched the machine
retrace this for more than an hour. It was so nice to see the machine
move on i
Stuart Stevenson wrote:
> Gentlemen,
> I think this debate is very interesting, fun to read, and
> educational but I didn't ask the original question to see what
> everyone thought or to try to bring someone around to my way of
> thinking. I would just like to have this functionality on my mach
Gentlemen,
I think this debate is very interesting, fun to read, and
educational but I didn't ask the original question to see what
everyone thought or to try to bring someone around to my way of
thinking. I would just like to have this functionality on my machine.
The machines I own and the ma
Mark Pictor wrote:
>> However, the basic principle of a jogwheel is that movement of
>> the table is DIRECTLY proportional to movement of the wheel.
>> Therefore there must always be some increment of motion per
>> count of the jogwheel.
>
> I should have said velocity mode. Spin the wheel, it m
> However, the basic principle of a jogwheel is that movement of
> the table
> is DIRECTLY proportional to movement of the wheel. Therefore
> there must
> always be some increment of motion per count of the jogwheel.
> "Continuous" mode only makes sense for pushbutton jogs, not for
> wheel jog
Mark Pictor wrote:
> If you jog via the GUI (i.e. Axis), you can select between
> Continuous and one of several increments. Why not have jogwheels
> behave the same way? Mode selection could be via pyVCP buttons, or
> physical buttons on the control panel.
EMC2's jogwheel support already has pr
If you jog via the GUI (i.e. Axis), you can select between
Continuous and one of several increments. Why not have jogwheels
behave the same way? Mode selection could be via pyVCP buttons, or
physical buttons on the control panel. In continuous mode, the
rate at which the wheel is spun could have
On Mon, Mar 19, 2007 at 09:25:27AM -0700, Kirk Wallace wrote:
>
> On the other hand, there may be a better way for doing setups than using
> the jog wheel.
Yes, John's preference for a precision handwheel is easy to share. :-)
However, positional tracking is really only useful within a single
rev
I'm not sure I understand what you mean by handle not in sync with movement
when talking about moving fast and long distances.
If I was moving 24.005 inches I would add 24.005 inches to the distance on
the readout and start cranking till it was close to that position. I would
expect the machin
On Monday 19 March 2007, Matthew Glenn Shaver wrote:
>On Mon, 2007-03-19 at 10:54 -0400, John Kasunich wrote:
>> Other people don't like that "unwinding", and would rather have the
>> wheel "slip" when you spin it too fast. If we make the wheel slip,
>> you don't have to worry about overrun, but y
If the machine is a Fadal with a Fanuc control it is a relatively
new machine. The machine keeping up with the handwheel is possible on
machines with fast feed/rapid capabilities. I have one machine that I
think will keep up with the handwheel. A Mori Seiki MV-JR. It is a
very light machine wit
This may be a lot slower on a Sherline, but it argues for only slipping
when max axis acceleration is exceeded.
On Mon, 2007-03-19 at 11:49 -0500, Ray Henry wrote:
> On Mon, 2007-03-19 at 11:27 -0500, Stuart Stevenson wrote:
>
> > Any time I want to keep the handwheel dial position synchroniz
On Mon, 2007-03-19 at 10:54 -0400, John Kasunich wrote:
> Other people don't like that "unwinding", and would rather have the
> wheel "slip" when you spin it too fast. If we make the wheel slip, you
> don't have to worry about overrun, but you also can't trust the dial
> on the wheel anymore.
longs at
the machine only.
Regards,
Steve Stallings
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Ray Henry
> Sent: Monday, March 19, 2007 11:50 AM
> To: Enhanced Machine Controller (EMC)
> Subject: Re: [Emc-users] handwheel over run
On Mon, 2007-03-19 at 11:27 -0500, Stuart Stevenson wrote:
> Any time I want to keep the handwheel dial position synchronized
> with the axis positon I have to move the handwheel slower than the
> machine will move the axis.
A friend with a couple of fanuc controlled machines told me that he'
Gentlemen,
I will go to the irc to see what is there.
I have been runniing NC and then CNC machines since 1979. I now
own machines with Fanuc, MDSI, Fadal, Haas, Okuma, Mitsubishi and
Leblond Makino and Cincinatti controls. Each of these machines act in
the same manner with the handwheel. Y
Caveat Emptor, my CNC user experience is rather limited, but I feel
compelled to add my voice here. This issue may become a source of
feature creep. I prefer a system that does what I _need_ it to do in a
predictable, consistent fashion. I hate having to try to compensate for
a system that thinks i
Matthew Glenn Shaver wrote:
> On Mon, 2007-03-19 at 08:04 -0500, Stuart Stevenson wrote:
>> I would end up with a control display for every operator. How fun
>> would that be?
>
> A lot of fun! ;)
>
>
> ;Jog wheel algorithm
>
> ;Initial state
> accumulated_clicks = jog_
On Mon, 2007-03-19 at 08:04 -0500, Stuart Stevenson wrote:
> I would end up with a control display for every operator. How fun
> would that be?
A lot of fun! ;)
;Jog wheel algorithm
;Initial state
accumulated_clicks = jog_wheel_position
direction = 0
while (jog_wheel_e
On Mon, Mar 19, 2007 at 10:54:04AM -0400, John Kasunich wrote:
> Stuart Stevenson wrote:
> > Gentlemen,
> > In my limited experience with the handwheel control on this machine I see
> > what I consider over run. I know it is the accumulated pulses the machine
> > has not completed. When the handw
Stuart Stevenson wrote:
> Gentlemen,
> In my limited experience with the handwheel control on this machine I see
> what I consider over run. I know it is the accumulated pulses the machine
> has not completed. When the handwheel is turned faster than the machine is
> able to respond the actual po
Hi Stuart
Okay. Okay. I think I understand where you're coming from now. The
MDSI control hint helps me a lot because all of the commercial controls
I've worked with, and that does NOT include MDSI, work their handwheels
as fixed increment. What you turn is exactly what you get.
When I'm retr
RogerN wrote:
> An approach that may work good for something like this might be to limit the
> following error for handwheel moves, and it could be a parameter that could
> be set by the user. Just a thought.
Following error is the difference between EMC's commands to the motors
and the actual
Gentlemen,
I don't see following error as the answer. The tuning should keep the
following error within spec regardless of the commanded position.
If I could specify a maximum delta from the actual position for the
commanded position I think that may work. IOW, the commanded position could
n
How about:
IFÂ following error is large (set by user?)
AND handwheel counts have stopped increasing/decreasing for a short time (1/4 second? user set?)
THEN stop the axis.
Then slower hand moves will still move exactly (because small follow error) and very fast moves will stop before trouble arrive
quot;Enhanced Machine Controller (EMC)"
Sent: Sunday, March 18, 2007 10:01 PM
Subject: Re: [Emc-users] handwheel over run
> This is just the beginning of the questions that would need to be
> answered to implement your approach. I don't want to dismiss it, but
> you'll n
Stuart Stevenson wrote:
> Gentlemen,
>In my limited experience with the handwheel control on this machine I
> see what I consider over run. I know it is the accumulated pulses the
> machine has not completed. When the handwheel is turned faster than the
> machine is able to respond the actua
Gentlemen,
In my limited experience with the handwheel control on this machine I see
what I consider over run. I know it is the accumulated pulses the machine
has not completed. When the handwheel is turned faster than the machine is
able to respond the actual position lags behind the commanded
31 matches
Mail list logo
