XY or Z axis moved more than intended

gSender ❓ Question
1

The machine intermittently makes much larger jog moves than commanded, even when using Precise mode and a single mouse click.
This has resulted in unexpected axis motion, including the Z-axis plunging into the table during jogging, not during probing or program execution.
The behavior looks like multiple jog commands are being issued or executed from one user action, creating a serious risk of crashes and lost work.

Steps already taken to eliminate the issue:

Verified steps/mm values are correct and the machine cuts accurately during normal G-code jobs.

Verified Z zero and work offsets were correct at the time of the crash.

Confirmed jog increment values for Precise and Normal modes are configured correctly.

Replaced the USB cable with a new one.

Connected the USB cable directly to the laptop (no hub or extension).

Disabled Windows sleep and power management features.

Disabled USB selective suspend and USB power saving.

Updated GSender to the latest version (1.5.7).

Verified the issue happens in Precise mode, not Rapid.

Observed the issue primarily on the Z axis, but occasionally on X and Y as well.

Confirmed this happens during jogging, not during probing or G-code execution. Although I’ve rammed the bit directly into the probe as well, trying to jog to get it close.

Determined soft limits would not prevent this, since it occurs within the valid travel envelope.

Identified that the behavior feels consistent with jog command duplication, buffering, or resend behavior rather than operator error.

2

@shreddoctor Welcome to the group.
I will move this to the gSender topic, as it will get more attention there.
You can help by posting what machine you are running, and what controller.
Also, confirm that these events are happening when using a mouse on the GUI buttons.

3

Thank you. I’m using a genmitsu 4030proverxl v2 with grbl 1.1f. I’m using a wireless mouse on a PC that has gsender on it. I’ve just now replaced the mouse with a wired one.

4

@shreddoctor Since you have just now changed to a wired mouse, can you confirm that the issue has not gone away?

5

Another config option you can look at is Continuous Jog delay - increasing the number will increase how long you need to hold until the machine starts continuous jogging. It sounds like you might consider bumping that number up (1.5.x defaults to 250ms, 1.4.x and prior versions of gSender had this set to 700

image

1 Like
6

Sorry, I could not reply last night or all day today due to a limit number of posts a new user can make. Nonetheless, I will certainly update this post on my findings. The issue is not consistent but it has happened 2 times in a week. I’ve been doing a lot of projects lately and I should see the issue come up - if it is going to.

7

Mine was set at 250ms. I bumped it to 500ms. Not sure if this is going to help though. The issue doesn’t seem to be with how quickly it apply or let go of the mouse. Even if I let go of the mouse, the jogging continues. I must hit emergency stop - if I can before it crashes.

FYI - I’m getting errors from the site stating that I’m either posting too often in one day or too much in one sitting. LOL. It just errored on me stating I must wait 6 min due to too many posts.

8

@shreddoctor Your posting issue should be fixed now.

I can’t address the tech problem, unfortunately.

1 Like
9

Nothing really to update here - other than it is working as intended. The continuous jog setting to 1/2 second is noticeable, but doesn’t seem to add much value. I’ll keep it for now and expect to just wait that extra 1/4 second more than I’m used to. :laughing:

I’ll update if anything crashes (or attempts to crash). Fingers crossed. Thanks all for the help thus far.

1 Like
10

Sooooo, I’ve run about 30 jobs with this setup and no issues. I’ve done many changes outs of the bits for each job and no issue like I saw before. There have been many cases where I need to jog in small increments (i.e. to get z height, etc…), So I think I should have seen the problem by now. I can only chalk this one up to the wireless mouse.

I believe that the wireless mouse could have had intermittent signals being sent through gSender and cutting out (i.e. not letting the PC and therefore the software - gSender know that I let go). I’d chalk this up to low battery or otherwise poor connectivity between mouse and PC.

Final thought: DON’T USE A WIRELESS MOUSE!

1 Like
11

@shreddoctor It’s good that you seem to have resolved this, Michael. I’m going to close the topic, but not mark any post as the solution.
I’m doing it this way because other users have successfully used wireless mouses (mice?) and I use an Android tablet running TouchPortal.
It seems that this issue comes and goes and there does not seem to be one perfect solution.
If your issue comes back, even using a wired mouse, please message me and I will re-open this topic.

1 Like