Limit switches triggered on machine off

Another question: in my machine (a 3d printer) i configured the vertical axis as W to obtain better smoothness during printing, but this way I can't jog the vertical axis using the keyboard anymore. Do you have a hint to find what part of the source of axis/gmoccapy I should edit to change the key bindings, so that I can move the W axis usig page up /down?

If using AXIS I think you could use the .axisrc option to redirect keybinding.
These seem to set the bindings for jogging:
bind_axis("Left", "Right", 0)
bind_axis("Down", "Up", 1)
bind_axis("Next", "Prior", 2)
bind_axis("KP_Left", "KP_Right", 0)
bind_axis("KP_Down", "KP_Up", 1)
bind_axis("KP_Next", "KP_Prior", 2)
bind_axis("KP_4", "KP_6", 0)
bind_axis("KP_2", "KP_8", 1)
bind_axis("KP_3", "KP_9", 2)
bind_axis("bracketleft", "bracketright", 3)

The number represents the axis 012345678 = XYZABCUVW

So maybe
bind_axis("Next", "Prior",
bind_axis("KP_Next", "KP_Prior",,
bind_axis("KP_3", "KP_9",

Great, i'll try that tomorrow.
I actually used gmoccapy on the machine, but I switched to axis recently as it seems more stable and light ( but lacks the industrial look of gmoccapy) .

I want to fix the jog issue because I already crashed the machine once as the interface got stuck during jogging from the gui, and i'd like to avoid that

I managed to solve the main problem using AND2 and timedelay components.

Using axisrc with those commands instead didn't make a difference for the key bindings.