Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] JOG state remains active after JOG command with invalid gcode #492

Closed
Paciente8159 opened this issue Sep 13, 2023 · 0 comments · Fixed by #493
Closed

[BUG] JOG state remains active after JOG command with invalid gcode #492

Paciente8159 opened this issue Sep 13, 2023 · 0 comments · Fixed by #493
Labels
bug Something isn't working core: parser core: command and gcode parsing

Comments

@Paciente8159
Copy link
Owner

Describe the bug
After a JOG command with invalid gcode or simply empty the JOG state remains "sticky" until it's cleared by a Hold command or a reset.

What is your hardware
Tested on virtual environment

What was the GCode running
For example send a simple $J= will make the state remain in a permanent JOG state
@Paciente8159 Paciente8159 added bug Something isn't working core: parser core: command and gcode parsing labels Sep 13, 2023
@Paciente8159 Paciente8159 linked a pull request Sep 13, 2023 that will close this issue
fix JOG sticky state on cmd error #493
Merged
Paciente8159 added a commit that referenced this issue Sep 13, 2023
@Paciente8159
fixed #492
b1f9763 
- fixed #492
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working core: parser core: command and gcode parsing
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix JOG sticky state on cmd error Paciente8159/uCNC
1 participant
@Paciente8159