Machine Runs Away After Jogging

[IShaLinI]

I just got my limit switches setup and homing works exactly as intended. However now there is an issue with jogging. Whenever i send a jog command the machine runs in the Y- Direction and will not stop. Pressing the stop button doesn't work because it is spamming the console with gcode. The only way to stop it is by unplugging the comm or power cable. Ive never had this happen before.

[breiler]

What OS are you running on?
Which version of UGS and what type and version of controller are you using?

Have you mapped any keyboard shortcut or connected a gamepad?

Logs may also be helpful:
https://github.com/winder/Universal-G-Code-Sender/wiki/Configuration#log-files

[IShaLinI]

I can get a specific one tomorrow but im almost positive it was something like

Jog: (Y-) -1.667

but in gcode of course. the console was flooded with that and ok.

[IShaLinI]

hitting stop didnt work because it was being spammed it wasnt just one big jog command

[IShaLinI]

Also to clarify the machine will run the sent jog command before running to Y-, and you can even send jogs between the spam and they run fine

[IShaLinI]

Apparently the ghost in my machine is gone because after going to get the exact gcode for you the issue is no longer present. If it shows up again ill come back but for now the issue is solved. Do you have any idea what might have caused this in the first place?

[breiler]

No, no idea. =/

[pixelwaster]

Not to hijack the thread, I had the same thing happen to me. UGS 2.0.15, WIN 10, Woodpecker Board running grblr 1.1f. The command before trying run off the X axis was "cls". I know that cls isn't a real command, but I thought I was using a different sender. I tried to jog X -10mm, but as soon as it was done (10mm), it was back to running the other way. Stop didn't work, but pause did pause the runaway X-axis until any other command (even a carriage return) was entered or button pushed.

The line in the log after 'cls' and every good command was '... responding to an unknown command'. I would post the log but it isn't there anymore. I also cannot reproduce the effect.

[breiler]

Keep a lookout and post the console log if this happens again. I am "hoping" that this is caused by interferrence on the usb serial line and not a program error in UGS. If this does happen again, check your USB cable and make sure it is shielded and of good quality.