Also, when this happens, the machine just keeps on going but gSender does not register that, making it lose the coordinate.
Last time this happened, it was after I tried to position the router, and I was clicking multiple times (not nearly as fast as double clicking fast, but you get the idea) as I had it in precise jogging speed.
@NCNC would you be able to provide more information so we can help you more? For instance if you can re-create the behaviour then generate a Diagnostic File from the Stats tab, or show a video or the Console
I tried to replicate this, to record it, but it happens seldom and at random, but it happens.
I also downgraded to the latest 1.4.x and it doesnât happen anymore.
But it happened about 4 times total when I was using 1.5.0 and 1.5.1, the machine just kept on going, as if I had kept the jogging button pressed, again, noticed the coordinates didnât change, so it felt more like an issue with the longboard maybe?
Thatâs definitely odd. If you can ever get it to happen again then that would be very useful to find where it might be coming from.
When you were jogging were you clicking with a mouse on the screen, using a touchscreen, using keyboard jogging, or gamepad?
Also youâre definitely right that typically if it was jogging away it would show on both the visualizer as well as the coordinates, youâre sure that those werenât changing and the machine was just moving on itâs own?
I was clicking with a mouse on the screen when this happened.
And yup, I noticed the coordinates didnât update as the machine moved, actually the machine moved fortunately at a slower rate, similarly to when the mouse cursor moves by itself, like thereâs something weirdly triggering it even though the physical mouse is not moving but the cursor moves by itself slowly, thatâs how it felt
@NCNC Weâve made some fixes and improvements to jogging since v1.5.1. Could you update to the latest version, v1.5.3, and let me know if this issue persists for you?
I can confirm this is still happening using 1.5.3:
Happened to me today while using my laser, I notice the one way it has always happened is when I click fast in consecutive clicks, almost double click fast, when Iâm trying to jog-place the bit (using the a V bit to pin point the starting point and then offsetting the laser) and clicking rapidly on the jogging buttons, usually happens on the Z axis (which can be annoying as itâll keep going down pushing the laser encasing against the spoilboard surface), but seen it with X-axis as well.
I noticed the coordinates do update on g-sender, previously I mentioned they didnât, today I paid attention to see if they did, and indeed they do, as if the consecutive rapid clicking gets the jogging stuck as if still pressing down on the jog button.
Iâm using my mouse, not a controller or keyboard keys or touch screen.
I also changed from Windows 11 (when last happened to me) to Windows 10, so different PC/OS, same bug as before.
As mentioned in another thread, I have seen the same thing happening. There is a configuration setup that controls how long gSender waits before going into continuous jog mode. Default is 250 ms. After changing to 500 ms I have not had another incident.
I have not noticed that the position displayed did not reflect the movement (but then I didnât look for that)
It is my understanding that the delay used to be 500ms before 1.5.x which is why it didnât happen in the older versions.
Thank you Jens, I was unaware of this feature, hopefully this will solve this issue.
However, if I understand this feature correctly, thatâs for when the jog goes on continuously when leaving the button pressed down.
I donât get why, for any reason, the CNC would continue moving/jogging when the mouse button is not pressing down on the screen jog buttons, which is my issue.
In the case of this âghost joggingâ, only way to stop it is via stop button (yup, full circle to that from that other thread), which shouldnât be.
I donât quite understand why things are they way they are either. All I know was that, after switching to 1.5.3, when lowering the bit to the spoilboard for a paper test, I did several down steps in quick succession and before I knew it the bit was firmly implanted on the spoilboard. This repeated on several occasions until I figured out a way to fix it.
In regard to why this is even an issue, I can take a wild guess âŠ. letâs say you press the mouse button, the controller performs a single step but at the 250 ms mark it says to itself âI wonder if I need to switch to continuous stepping mode, I better check if the mouse button is still pressedâ. Now say you are Speedy Gonzales and you had already pressed the mouse button again. Would the controller say to itself âthe mouse button is still pressed, I better go into continuous modeâ? How long after a mouse button is released does the controller say âI better stop what I am doingâ. There is a lag which is why it is notoriously difficult to stop a rapid motion at precisely the right point.
None of this explains âghost joggingâ which likely is an entirely different issue. While there might be a fraction of a second of movement after the mouse button is released causing you to move further than expected, there is no reason I can think of (hardware or software errors are possible) that would have the motion continued basically forever until you hit the stop button.