Req: The ability to set different distances and feedrates for the Z axis vs XY Axis

[timm052]

Having the jogging distances and feed rates be a universal setting for all axises makes it very easy to crash your Z-axis into stock by accident when jogging into position. Other g code senders address this by allowing different settings for the z-axis so you can keep your z-axis on 1mm while the x and y can be jogged at 10mm+ I think this would be a useful addition particularly for people using gamepads to jog the machine around.

[terjeio]

ioSender has continuous jogging when using the cursor keys except when the <CTRL> modifier is pressed for step jogging. Step jogging distance is typically 1mm or less (can be changed on the fly), other jogging distances should typically be set to at least the length of the longest axis. If the controller is grblHAL based and the machine is homed (and proper travel distances are configured) you may also set $40 to limit jogging to always be within machine limits.

Continuous jogging = only a single jog command with a long distance is issued on key down, and a jog cancel is issued on a key up. This means that the distance is in practice not limited by the settings but rather by how long they key is pressed.

I assume the gamepad simulates pressing the cursor keys to jog, so the same applies to that.

The wiki lists keyboard shortcuts available.

[timm052]

Ahh I see I still think it would be nice to be able to set separate feedrates ie. I might want to jog my machine at 2000 mm/min on the X and Y but a fast move on the Z would never need to be that high.

[terjeio]

I might want to jog my machine at 2000 mm/min on the X and Y but a fast move on the Z would never need to be that high.

Have you tried keyboard jogging with and without the shift key to modify the feed rate? In the Settings: App tab Fast feedrate is used when the shift key is pressed, Slow feedrate when not.

Since ioSender supports N-key rollover (all three axes can be jogged simultaneousely if it is a capable keyboard) having different settings for the Z-axis might only complicate the code and perhaps also user perception of how it should work.