On Thu, Sep 29, 2016, at 10:48 AM, Florian Rist wrote: > Hi John > > > Do you need/intend to use g-code at all for this installation? > > Yes.
In that case you want the LinuxCNC motion planner. It will handle all the jogging, homing, etc, for you. > > And I'm now just trying to modify it quickly to do a manual > demonstration. > > Could I do something with the axis jog pins: > > axis.0.jog-vel-mode > axis.0.jog-enable > axis.0.jog-scale Those are for using a jogwheel. See http://linuxcnc.org/docs/2.7/html/config/core-components.html I just read that using halui didn't work because the axes don't track perfectly (not really a surprise, since halui is a non-realtime component). You could use a stepgen in quadrature mode to fake the jogwheel counts, and use two buttons to make that stepgen go up or down. If you send the "jogwheel" counts to all axes, set the axis.N.jog-scale the same for all axes, and turn on axis.N.jog-enable for all axes, they WILL move the same distance. > > I have a few custom HAL components that I could share if useful. > > For example, one lets you switch from manually controlling each > > motor (for "homing") to coordinated control. > > Oh, sounds very interesting. As long as you are using LinuxCNC's motion controller and g-code you don't need my components. -- John Kasunich [email protected] ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
