I’m going to try a total re-install of all software and reset the mill back to defaults. Then I’ll try again and investigate exactly when the mishap occurs and try to narrow it down from there.
Thanx for all the suggestions so far.
I’ve had issues with gSender running away during commanded moves on a fairly consistent basis using the mouse on the PC and with a wireless Xbox controller. Looking through this forum, it seems that this is not uncommon and I’ve found no answer as to why or how to avoid the issue. I just upgraded to a Super Longboard but the issue happened with both boards. Is there anything built into the SLB that would preclude its use with another sender software like ioSender. Has anyone got experience using this sender or another sender with a SLB? Frustrated and fishing,
I have seen this question many times. I am not sure of an exact solution for the run away problem. But what I did was to program the the buttons on my Xbox controller instead of using the stick for jogging. I programed mine like this:
Y = Goes backward on the Y
A = Goes forward on the Y
X = Goes left on the X
B = Goes right on the X
Right Trigger = Spindle Down
Left Trigger = Spindle Up
DPAD = Precise, Normal, Rapid speeds
I don’t even use the sticks since they are very very unreliable.
You mentioned using a controller, so I’m wondering if it might be stick drift. That’s when the joystick doesn’t return fully to center and the controller thinks you’re pushing it even when you’re not. Wear or debris in the mechanism can cause it, and in a shop with sawdust and chips that’s pretty easy to happen.
Does gSender support controller settings like dead zones? For example, if the deadzone is set to 5–10%, the joystick has to move past that threshold before the input is registered.
Although I’ve never used a controller with my CNC and gSender, I have experienced the runaway jogging problem a few times. Thankfully, I haven’t had that issue in a long time. I’m still using gSender v1.4.12. I did update after that, but the problem soon returned, so I went back to 1.4.12 and haven’t had it happen since.
Issue happens with controller or the mouse. It acts like it gets the signal to move but doesn’t stop once it’s off to the races. Moving mouse or joystick and trying different inputs has no effect. It will only stop if I click the Stop button on the screen or hit the e-stop. I don’t know if the new version has been optimized to run with the SLB or how well the old version will work with the new board. Oh well, I’ll keep plugging away and see what happens.
@j_a_wolfe I wonder if multiple jog commands are being sent to the SLB.
There a setting in gSender called Continouous Jogging Delay which might address your issue. Don’t know for sure but it may be worth a try increasing the delay.
Do you have the same issues with say a wired mouse and/or keybord with shortcuts for jogging?
I have had the problem with runaways primarily using a handheld running remote mode and deleted that way of jogging out of my workflow entirely. I, like anyone, need, 100% reliable jogging and cannot have a runaway machine. So I get that you like to replace gsender, but maybe you might want to change the oil first before buying a new car?
I have found a wired keyboard fully 100 points reliable. I would start there and see if that mitigates the problem, so that you can look deeper into the jogging problem with your mous and controller while having a save way to do the joggs that matter.
Any gcode sender capable of connecting to your machine can replace gsender. You are not stuck on it, but.. you might return to it anyway because it’s awesome in all other aspects. Might aswell look a wee under the hood before calling a total loss.
I have had the issue with a wired keyboard, wired mouse, wireless mouse and the Xbox wireless controller. It happened with the original board and the SLB. Since everyone seems to be happy with gSender, I have to think it’s a problem with my application. I have found no parameters that seem off and there doesn’t seem to be an errant switch in the config. It’s happened using a laptop and a desktop. The only reason I would dump gSender for an alternative is that I need to find a way to stop running the gantry against the stops or driving the bit into the workpiece. My last try is a complete reinstall and see if it starts acting up. A lot of people seem to have had the issue but I’ve found no common cause or resolution. Stumped and frustrated.
@j_a_wolfe Did you look at the Continuous Jogging Delay setting?
Since you mentioned upgrading to the SLB, I assume you have a Longmill. Do you have the limit switches too?
And when you say you have runaway issues when doing commanded moves, what are you doing exactly? Just pressing the jog buttons on the gSender console? And using rapid, normal, or precise movements? One, or all of them?
Does it ever happen when the dust collector is off?
When I had this problem, I could not answer that question. I think it was always on, but I really couldn’t remember since it didn’t always happen in bunches.
If it is happening only when it is on, do you have your dust collection grounded?
This won’t be a solution to the issue but it might give you some clues. With the mouse at a known position, when you move it (let’s say to the right), do you leave the pointer in the new position? At this point the gantry would be moving to the right. If you bring the mouse back to the point where it originally was does the gantry stop?
I’m mentioning this because I had a problem in some unrelated software where I didn’t realize that the mouse was behaving like a joystick except that it didn’t have a spring to return it back to the center position which is where it would need to be to stop the movement. In that software, I had to disable the mouse so that only the Joystick inputs were being actioned.
I’m going to try a total re-install of all software and reset the mill back to defaults. Then I’ll try again and investigate exactly when the mishap occurs and try to narrow it down from there.
I have been able to produce runaway consistently with an XBox Controller (Logitech F310 wired USB). Moving the joystick in both the X and Y directions simultaneously triggers runaway. I initially tried the Continuous Jogging Delay setting to no avail, before realizing the X+Y action was the issue.
My solution was to program the “B” button to “global stop”. This is much faster than trying to fumble with the trackpad to click “STOP” and doesn’t have the PITA aspects of an emergency stop. I may need to try Karver_One’s solution of just using the XBox buttons to jog instead.
My full setup for reference:
gsender v1.5.7
SLB
LongMill 2.5
Windows 11
And the aforementioned Logitech F310 wired USB XBox controller/gamepad
I definitely feel for you. I found that solution I gave above to be the only solution that works at the moment. But I am sure someone someday will find the work around. If you do ever solve it, I also would like to know how you did it.
I have had this problem as well, using a wireless Mouse on a Genmitsu 4030 Ver2. It seems to happen mostly in the Z axis when moving with PRECISE control when clicking the mouse several times in rapid succesion, is there perhaps a buffer that is being exceeded in the software? I havn’t tried changing the delay timer yet, just being more careful with my clicking finger. It has driven the cutter into the job on several occasions, not a happy situation.