Re: [Emc-developers] general messaging... feedwheel inputs

[Kim L. <lu...@di...>]

On Fri, 2003-07-25 at 09:53, re...@up... wrote:
> Kim
> 
> Only one small problem here.  The GUI must wait to send the next incremental
> jog until after the last one has completed or it will increment from the position
> it was in when it received the next one.

I was thinking about that too.  There could also be several handwheel
counts between moves.  We might have to make the GUI logic a bit
smarter, like keeping track of the position when the move command will
be done, counting all the counts that happen while it is moving, then
issuing a new move command to the new (equals current plus new counts)
position. 

I suspect it could be made to work quite well, but the possibility is
there for the handwheel to move much faster than the table, so some
smarts will have to be built in.    

My neighbors lathe has both Position and Distance to Go readouts. 

> I'thought a bit about this and think that we need to keep a value for the 
> jog position separate from actual location and then issue the incremental jog 
> commands based on the difference between the real position and this jog 
> value.  

Something like that. 

> Forgive the typing,  I am working on a German keyboard.

Looks good to me.

> Ray
> 
> On 25 Jul 2003 07:08:35 -0600, emc...@li... said:
> >On Thu, 2003-07-24 at 23:35, Jon Elson wrote:
> >> >>
> >> >
> >> >The feedwheel jog does not require any changes to the underlying
> >> >structure.  A mouse may be used to capture the encoder signals and the
> >> >emc interface can process the mouse info the same way it processes a
> >> >mouse click on the +/- buttons.    
> >> >  
> >> >
> >> Yes, but does this really give you a guaranteed one pulse = one increment
> >> of movement?  The big-iron CNCs allow you to spin the jog dial 10 times
> >> and know that the table moved exactly 10.0000" (or whatever the jog
> >> increment is set for).
> >
> >No, that is the beauty of doing it in software at the GUI level.  The
> >emc GUI will intercept the mouse input, ie feedwheel movement, and do
> >with it as it wants.  If the GUI is set to move the table 1" per
> >increment, so be it.  If the GUI is set to move the table 0.0001" per
> >increment, that works too.  The "sensitivity" setting for each axis can
> >be a drop down selection box.
> >
> >Feedwheels are GUI items and that is one reason why I think they should
> >be handled at the GUI level.
> >
> >Spindle inputs for threading and speed feedback are not GUI inputs and
> >should thus be handled at a deeper level. 
> >
> >Kim     
> >
> >
> >
> >-- 
> >Kim Lux <lu...@di...>
> >
> >
> >-------------------------------------------------------
> >This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> >Data Reports, E-commerce, Portals, and Forums are available now.
> >Download today and enter to win an XBOX or Visual Studio .NET.
> >http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> >_______________________________________________
> >Emc-developers mailing list
> >Emc...@li...
> >https://lists.sourceforge.net/lists/listinfo/emc-developers
> >
> >
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Emc-developers mailing list
> Emc...@li...
> https://lists.sourceforge.net/lists/listinfo/emc-developers
-- 
Kim Lux <lu...@di...>