[HuFlungDung]

I beg to disagree with you guys, but from a state of ignorance about keyboards, I'll admit. A keyboard can typically be set to repeat at up to 30 chars per second, which BTW, exceeds the speed at which I can type or tap. This seems to be nowhere near the response I get in jog mode.

BTW, the Bandit is about 25 years ancient now, so I really doubt that their keyboard polling rate was any better than what a modern PC can muster.

I can easily outjog anyone running a Camsoft handwheel in Bandit's general purpose 3 axis jog. The reason you guys look down your nose at keyboard jog is the same reason as I do: the keyboard jogging sucks so bad in the Camsoft gui, that it might as well not even be in there. I'd gladly trade enhanced functionality in jogging for mid program start with the mouse, which I cannot see why the effort was made to create such a function. I just would never trust it. But that is another topic.

Do you even stop and consider what I've said about the Bandit jog? Safety is not the issue, in fact, thanks to the two-key combo in Camsoft's jog, I've made blunders that would never happen on Bandit. So, I quit using it, if at all possible.

For another thing, there is some kind of a flicker across the CRT screen (version14.7), whenever the jog buttons are pressed and released, as though there is some substantial calculations or logic being run in the background, which must be loaded and unloaded every time a key is pressed. I wonder what could be the cause of this? Does it have anything to do with the jog file being read when both entering and leaving jog mode?

But, I will try modifying the accel-decel rates in the jog file because I had not thought about that. That still does not address my main gripes about the whole keyboard jogging issue. I don't like it, and I am willing to figure out how to change it, but it needs to be part of the configurable gui. Like I said, why should I have to spend $1500 for jog function by using third party hardware? It doesn't make sense to me.