On Monday 13 March 2017 15:46:06 andy pugh wrote: > On 13 March 2017 at 19:36, Gene Heskett <ghesk...@shentel.net> wrote: > >> axis.L.jog-enable and joint.N.jog-enable need to be set. > > > > Both, or just the latter? > > Depends what you want to jog.
Well, halshow won't let me set joint.0.jog-enable, but setting the axis.x.jog-enable sets both. But still no machine response, and I note that both axis.x.jog-scale and joint.0.jog-scale are zero. Can, since I've already done the math in my own code, assume that a jog-scale setting of one (to whichever one I am allowed to set, axis.x.jog-scale I expect) would be correct? Or is there yet another "guard dog" to be fed & petted here, and under what conditions? In the event it works, and the timer times out, zeroing the encoder etc, and the data being sent to jog-counts drops to zero when that occurs since the timeout resets the encoder, I assume I should drop the enable before the jog-counts drops to zero at the end of the timedelay? Or should I not clear the encoder because motion remembers it and acts only on the new difference. That would get rid of 4 or 6 lines of hal code. Thanks Andy. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
