Thanks John! On 08/20/2010 12:02 PM, John Kasunich wrote: > On Fri, 20 Aug 2010 10:57 -0600, "Sebastian Kuzminsky"<[email protected]> > wrote: > >> I think i can see how to disconnect Axis and connect a couple of rotary >> switches instead. The axis selection switch would make the selected >> axis.*.jog-enable True and make the others False. The jog increment >> switch would address a mux to output the desired jog increment to all >> the axis.*.jog-scale pins. The jogwheel stays connected just like now. >> >> But i'm not sure how Axis will behave if I hook things up like this... >> >> Can i still jog with Axis, using the keyboard? >> > Yes. > > >> Will Axis jog the axis it selects with the jog increment it selects, and >> the jogwheel jog with the axis and jog increment selected by the rotary >> switches on the control panel? >> > Yes. > > >> Does Axis not use the axis.* pins to jog? What's going on here? I'm >> confused... >> > Axis doesn't use the axis.* pins. Inside the motion controller there > are two kinds of jogs. One consists of commands coming from user > space - that is what Axis uses. The commands are visible in the big > switch that is part of command.c - there is one for incremental jogging, > and one for continuous jogging. Search for JOG_CONT and JOG_INCR to > see the code. Axis sends one or the other of those commands when you > hit the relevant keys. In the case of a continuous jog, Axis also > sends an ABORT when you release the key. > > Jogwheel jogs come from a completely different place - HAL pins on > the motion controller. Code in control.c reads the jog-scale, jog- > enable, and jog-counts pins, and moves the axis accordingly. Search > for handle_joghweel to see the code. There is also code in control.c > to manage the case where you start turning a wheel while a keyboard > jog is already in progress. The two jog sources are interlocked so > that if the axis is moving from one source, the other is ignored. > The interlocking is done on a per-axis basis, you could be jogging > X from the keyboard while jogging Y with a wheel. > > The original design of the jogwheel code was based on exactly your > setup - physical switches that tell the motion controller what to do > with the jogwheel counts. Jeff or Chris later added the HAL pins to > Axis that let Axis export the currently selected axis and increment. > That works very well for people who don't have or need the physical > switches, and has pretty much become the default setup. > > John Kasunich >
-- Sebastian Kuzminsky ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
