I think here is a bug in the home command.
After finishing a job, my router stays in the last cut position above the board. If I then press the home icon, one of two things may happen:
The router returns to the defined home position which is ok, BUT: if I press home again, I would think that the router should stay where it is because it is already at home, but it performs another move again, same as the last move to the home position. If I press home again, it moves again, even further away from home.
The router moves away from home along the line from the home position to the end-of-job position. It performs the exact inverse of what it should be doing.
Mine does this too sometimes. (If it’s same problem).
But no matter if I push jog or home, it travels a small distance approx 100mm in a weird position (and very fast) and then keeps travelling to “some spot” until it gets to where it wants to go… Usually with kinda slack belts… And then once it arrives where it wants to be… It starts jogging normally, or if I click home it will now go to it’s proper home.
I’ve thought of reporting previously… But I don’t have it recreatable. Next time maybe I’ll film.
I’ve been trying to replicate this bug, but this is exactly what I see happening. When I press home a second time the machine doesn’t move at all because it’s already home.
Which firmware and index.html version are you running?
I have seen this behavior when I was playing with the movement controls on the first tab (fluidnc) and then hitting maslow tab home. (also noted that home on the fluid tab sends $H which we don’t seem to grok).
I’m using V0.79.
It did not happen 100% of the time, if I remember correctly. (I don’t use the Home-command anymore, because the last time I used it the sled went off the board…)