Re: Problem in Mar 15 build?

[Fred Proctor <proctor-at-cme.nist.gov>]

Tim Goldstein asked if anyone else had these problems:

>
The per axis MAX_VELOCITY setting is only working in one direction with
jogs.
<

and

>
In auto mode the feed override is boosting the G0 rapid moves from the
value set on the per axis MAX_VELOCITY parameter
<

I'm sure you all do since I tracked down the problem, at least the first
one. I'll fix it. The fix for the first is to look at the functions
emcAxisJog(), emcAxisIncrJog() in emc/src/emctask/bridgeporttaskintf.cc
(or minimilltaskintf.cc if you're running that), and see the obvious
one-side-only comparison.

--Fred