Hello Guest it is July 21, 2019, 03:49:49 PM

Author Topic: Jog HotKey gets stucked!  (Read 6676 times)

0 Members and 1 Guest are viewing this topic.

Jog HotKey gets stucked!
« on: February 24, 2008, 10:18:56 PM »
Hi I hope you can help me

I'm using a USB numeric keypad, as a pendant for jogging and other functions.

On MACH3screen designer I assigned keys to buttons that jog the axes by means of
the set hot key feature.

When I load the screen in MACH3 and press a jog key the correct axes moves in the right
direction but keeps moving even when i release the key!

What I am doing wrong?

Thanks in advance!

Gilbert.
Re: Jog HotKey gets stucked!
« Reply #1 on: February 24, 2008, 11:00:25 PM »
Hey Gilbert,
Instead of using Screen Designer, just go to Config.. Hotkeys...and click on the jog hotkey for the axis you want and it will prompt you to hit the key you want to use.
Give it a try... it works well here,
RC
« Last Edit: February 24, 2008, 11:24:41 PM by Overloaded »
Re: Jog HotKey gets stucked!
« Reply #2 on: February 24, 2008, 11:10:06 PM »
Thanks!
 I will try that.

Appreciated!

Gilbert.
Re: Jog HotKey gets stucked!
« Reply #3 on: February 24, 2008, 11:27:24 PM »
RC:
It did not do it for me.

Let me explain, I'm working on a 4 axes foam cutting machine, X,Y,A,B axes.

I'm using the 2&4axisFoam.set screen i down loaded, there you have the normal jogging buttons for each axis independently
but the ones i wanted to jog on the pendant are the ones that jog two axes at the same time, sort of chaining the X and A 

and the Y with the B axes.

I try ed to do it the way you suggested, and setting the same key for X- and A- and the same key for X+ and A+ and so on
but when i press the key only X moves or Y, not A or B.

do you have any other suggestion?

Thanks!

Gilbert.
Re: Jog HotKey gets stucked!
« Reply #4 on: February 24, 2008, 11:45:13 PM »
Ahhh.. I understand your problem. But I am not sure how to fix it.
I guess the hotkey will only work 1 axis at a time. Hmmm ...But I assume that it did stop when you let off of the key.
I will tinker with mine a bit and let you know if I find a solution.
I'm learning along with you.
Thanks,
RC
Re: Jog HotKey gets stucked!
« Reply #5 on: February 25, 2008, 10:52:48 AM »
Hey Gil,
I've tried everything I know of (limited).
I either get the continuous running, or 1 axis then the other....not simultaneously.
We need further help.
Are you using an emulator ? Have you read chapter 5 in the Mill manual ?
RC

Offline Hood

*
  •  25,849 25,849
  • Carnoustie, Scotland
    • View Profile
Re: Jog HotKey gets stucked!
« Reply #6 on: February 25, 2008, 01:48:28 PM »
Can you attach the screen so we can have a look. Do the axis jog correctly when pressing them onscreen with the mouse?
Hood
Re: Jog HotKey gets stucked!
« Reply #7 on: February 25, 2008, 08:09:06 PM »
Yes the jogging of X+A and Y+B works fine on the screen buttons.

But when you press the assigned key
in the numeric USB keypad it keeps on running, It only stops if you reset or hit stop.

By the way as a temporary solution i assigned #5 key in the keypad to stop, so i start the
jogging on the corresponding key and stop the movement pressing the central key(#5), it "works"
but is never the less not compared to just release the key to terminate the motion.

Attached is the screen file.

Thanks for your time!

Gilbert.
Re: Jog HotKey gets stucked!
« Reply #8 on: February 25, 2008, 08:29:55 PM »
Hey Hood

I forgot to point out that the buttons I'm  talking about are located in the right upper corner of
page1.

The Captions are X-FB++,X-FB--,Y-FB++,Y-FB--.

They have the corresponding hot keys from the numeric keypad assigned.

Thanks again!

Gilbert.

Offline Bodini

*
  •  216 216
    • View Profile
Re: Jog HotKey gets stucked!
« Reply #9 on: February 25, 2008, 09:01:51 PM »
When I load the screen in MACH3 and press a jog key the correct axes moves in the right
direction but keeps moving even when i release the key!

I used to have that problem all the time on the keyboard, I never figured it out, and it hasnt happened in months.  Somebody told me it was 'StickyKeys' but those [Windows] settings didnt fix it at that time either.