Thanks for the info. If I disconnect spindle-speed-in, G76 and G33 stop working too, so they seem to need both signals somehow, but from what you say that still does not necessarily mean that G95 must work as well. I rather suspect the motion planner. Maybe someone can verify if G95 works in the non-machinekit linuxcnc version? I will post to the machinekit list as well. Am 09.12.2014 um 12:24 schrieb andy pugh: > On 9 December 2014 at 08:53, Karl Jacobs <[email protected]> wrote: > >> I can rule out hardware problems of an encoder by using a hal siggen >> component to drive the hal encoder inputs (Phase A and Z, counter mode) >> to simulate the spindle speed signal. That must be working correctly >> because G76 and G33 both give the right result (my X and Z axis >> components drive a real lathe so I can watch and check the motions). >> > > G76 and G33 use motion.spindle-revs, and G95 uses motion.spindle-speed-in > So, it is possible to have a fully functional G76 and G33 but not have a > working G95. > > It is possible that this is due to the new motion planner. > > It is also possible that this is a Machinekit-only problem. Machinekit has > now diverged considerably from LinuxCNC, and your query should probably be > directed to the Machinekit mailing list. >
------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
