On Tue, Mar 14, 2017, at 10:56 AM, Gene Heskett wrote: > Greetings all; > > I threw out quite a few lines of code, but while its now working, its > working at 4x the movement I am asking it for. > > I am now sending my distance increment to the axis.x.scale and > joint.0.scale inputs. > > and sending the hm2...encoder.count to axis.x.counts and joint.0.counts > > It seems that regardless of what I > setp hm2_[HOSTMOT2](BOARD).0.encoder.01.scale at,from 1 to 16 tested, one > click is a count of 4 at the count output. So I am getting 4x the > movement I want. So sending a .0002", gets me .0008" rad change > and .0016" dia change. > > Is there a fix for this unwanted 4 per click? Or am I getting a 4x > multiplier because I am feeding both axis and joint the encoder count? > > Thanks all; > > Cheers, Gene Heskett > --
The jog scale inputs are "distance you want to travel per jogwheel count". Your wheel sends four counts for one detent. If you want one detent to be 0.001" set jog-scale to 1/4 of that, 0.00025". If you want one detent to be 0.010", set jog-scale to 0.0025". And so on... hm2_[HOSTMOT2](BOARD).0.encoder.01.scale has nothing to do with it. That is used INSIDE the encoder driver to scale the floating point output of the encoder. Wheel jogging doesn't use the floating point output of the encoder, it uses the raw counts. The reason for that is so that you can change the jog-scale any time you want. -- John Kasunich [email protected] ------------------------------------------------------------------------------ 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
