Does anyone know why? When setting z manually when you double pump the z button down it suddenly drives it straight into the part and then I have to reset the machine.
what setting am I missing ? Z is in precision mode @. 004” yet it dives down like an inch.
That is the question of the ages … quiite a few people have experienced this (me included)
On the Altmill there is a setting to configure the time-out for the system to recognize how long the button needs to be depressed for the mill to interpret it as a ‘long’ click and go into continuous feed.
I do not know if this would fix the issue … it didn’t eliminate the issue for me but I haven’t tried to make that delay really long …
I cannot seem to figure if it is because repeated pushes of the button causes it or repeated pushes then push it again causes it. It literally it makes no sense what it’s doing and it’s only the z-axis.
It’s a good thing that I have learned to do this off pattern.
I guess they just want us to buy the new block 
@mborgardt It’s weird how these issues crop up for some users but not others. And it’s really hard to pinpoint the issue of you can’t reproduce it at will. Luckily, I’ve never had the issue. Then again it’s rare that I keep pressing on a button. I typically just do a series of button presses.
Try a larger number for “Continues Jog Delay” in CONFIG tab
So that spaces out the time interval even if your quick jogging with your finger??? Because it does seem that the main trigger is like a double pulse.
Also very strangely and I don’t see how this has any bearing to this. I set up the soft trigger and I hadn’t done that before and now it’s acting a little less twitchy.
I have a pet theory … let’s say you have the delay set for 250ms, you press the mouse button to jog one step (or more). If at any point your mouse button is pressed as you cross the 250ms mark, I wonder if gSender interprets that as ‘oh, the button is still pressed, I should go into continuous jogging mode’
As I said, it’s only a pet theory.
@Jens I don’t know anything about how electron handles input but recalling your recent post on CPU usage I wonder if that could be a factor. If gSender suddenly uses 95% of your CPU is it more likely to miss the space between clicks and decide it’s been down the whole time?
I don’t know anything about Electron either so I can’t comment one way or another. Stranger things have happened …
Good news if you said it for a tad bit longer on The jog delay it works like a charm and so far I’ve had no issues