On Wednesday 15 March 2017 09:23:47 andy pugh wrote: > On 15 March 2017 at 00:35, Gene Heskett <[email protected]> wrote: > > And, while they do have a scale, my attempts to set it to a value > > that returns an additional 1 per click, have been ignored, without > > reporting any error. > > The scale setting does not affect the counts. The scale affects how > the counts are converted into position. > In theory you could use an encoder.scale of 4 then pass the the float > position to an S32 converter then use that for jog counts. > > But that would be stupid when there is a jog-scale pin to convert > counts to machine-units offset. > > Are you actually using the jog-scale pins?
Yes. I only have axis.x. sort of working, but here is that line. net jogxsize <= mux8jogspeedx.out => axis.x.jog-scale That is the size of the jog, in machine units, inch in this case, so min=0.0001", & max is 0.0200" per count on a 1,2,5 progression. And I haven't experimented with G7-G8 to see if the jog distance is modified by that, ATM its radius. I'll check that G7-G8 thing today. This I don't need to gate, but I do need to gate the derived encoder count so it doesn't also move when I am selecting the jog-scale in the mux8. So when the button is held down, counts is zeroed by this new mux2s32. Only active when the time delay hasn't expired. Humm, crazy idea. I develop the updown counts independent of the encoder's count. Thats by and2ing the AB phases so its true at the detent crossover point, and thats steered and counted in an updown, clamped at 0 and 7. A bitslice converts that to sel lines for the mux8, which in turn selects the jog-scale. The timedelay output is available in either polarity, and I am using an xor to do something else, but I could just as easily hold the encoder in reset with that same signal, or its inverted case. That would disable the jog unless the button has been released and the timedelay has not yet timed out. That would remove the need for this particular mux2s32 entirely. I like it when I can simplicate this stuff. :) I can also see where the mux_generic, doing internal data conversions, has got to be marginally faster than 3 separate hal calls. Writing it down sure helps to visualize what needs to be done. Is my coffee kicking in? Another cup might to do it... 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 [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
