Delayed keyboard jogging

[alfalfa]

Well, I am back from the box and finally getting back into the swing of things here at the shop.

An issue that I have noticed for a long time with both Camsoft installs I have done is that there is a noticable lag between the time the operator hits <ctrl><arrow> until the axis starts to move. Then there is another lag from the time the keys are released until the motion stops. This is becoming more than a nuisance as the operator is crashing tools and shields. Have any of you wise guys experienced this and/or know of a way around it? I am guessing that it is some sort of buffer in Windows/Camsoft, but what to do?

AL

[camsoft]

alfalfa,

We know what you're talking about and can tell you there are several reasons for this. There are also several solutions for this as well, but any advise we would give would need to be offered once the reason was researched. It would be best to contact us directly for help.


Tech Support
CamSoft Corp.
support@camsoftcorp.com
PH 951-674-8100
Fax 951-674-3110
www.cnccontrols.com

[HuFlungDung]

My 2 cents: windows is slow at polling the keyboard, and moreso if it is busy. I experience the same thing with my cadcam software, if I go too fast. But, mouse action by comparison is much faster. But then, the mouse is a USB device.

I wonder if a USB keyboard would 'run' faster?

[alfalfa]

Camsoft - thanks for the quick reply. You guys have been good to me, even when I am out of maintenance (which is the current situation), so I don't want to abuse that. That's why I started here to see if any of these guys had a suggestion.

HFD - I suppose that is a consideration, will have to look into that.

Thanks,
AL

[Karl_T]

I've started with keyboard jog on every machine when first debugging. No two ways about it, keyboard jog sux. I've seen the same issue.

OTOH when you install jog button inputs to the Galil board, or opto 22, Camsoft jogs just like any professional control. Include a handwheel and your operator will love you. Makes setting up your part and tooling go so much faster and more accurate.

Karl

[keithorr]

Karl has the best solution. Just bypass camsoft and hardwire jog buttons to the card. And HuFuDu, it's not windows slow polling. I run galil hardware from a vb application and jogging reaction is as fast as letters appearing on the screen when you type. I get faster reaction times using speech recognition to galil dmc commands than I ever did with camsoft keyboard commands.

[HuFlungDung]

Keithorr,
You may well be correct. I know the standard reply is always to put in hardware buttons to jog with.
Its a shame that Camsoft cannot clean up their keyboard jog code. I don't know what all it is doing, but part of it may have to do with loading that corny joystick graphic, whether that is visible or not, I don't know if that makes a difference. The thing is, the software has to check if a mouse command was received from the graphic, or if a keyboard command came in. So in my mind, if windows gets busy, it seems to buffer the keystrokes, which instantly puts the user out of sync with his own fingertips.

[Karl_T]

alfalfa,

If you don't have time for a custom install of jug buttons and and handwheel, you may want to look at Camsoft's pendant. All the hardwiring is done. Its a sure bet that they have a .cbk for this unit also.

Karl