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.

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

Add "cancel" command in order to cancel print on Prusa / Marlin based Printers #1414

Merged
merged 1 commit into from
Feb 26, 2024

Conversation

bkerler
Copy link
Contributor

@bkerler bkerler commented Feb 17, 2024

On printing via Printrun on Prusa and Marlin based printers, if the user stops the print on the printer, Printrun will continue to print and doesn't recognize that the print run was canceled. The Prusa / Marlin based printers are sending the "action:cancel" (see here and here) command via serial port, but Printcore seems to expect "!!". This commit adds the "action:cancel" command support.

I'm not sure if pause is the right command, but I couldn't see any stop implementation.

@bkerler bkerler changed the title Add "cancel" command in order to cancel print on Prusa Printers Add "cancel" command in order to cancel print on Prusa / Marlin based Printers Feb 17, 2024
@rockstorm101
Copy link
Collaborator

I'm not sure if pause is the right command, but I couldn't see any stop implementation.

Agreed, I don't think there is a do_cancel function or similar so re-using do_pause sounds fair. I'm happy to merge this. Even if it is just for Prusa firmware, it seems harmless for everyone else anyway. Any objections @DivingDuck?

@DivingDuck
Copy link
Collaborator

Hi @bkerler and @rockstorm101,
I totally forgot to answer this PR. I'm happy with this too.

@rockstorm101 rockstorm101 merged commit d378321 into kliment:master Feb 26, 2024
@bkerler bkerler deleted the Prusa_support branch February 26, 2024 09:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants