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

M600 Q parameter enhancement #1608

Closed
wants to merge 17 commits into from
Closed

Conversation

@guykuo
Copy link

@guykuo guykuo commented Mar 9, 2019

Added new, optional Q parameter to M600 Gcode.
Q parameter suppresses M600's first MSG_PRESS_TO_UNLOAD.

Why? Support for easier filament color change.
I have written this patch to support rainersc's nifty manual color change technique as described at
https://schlosshan.eu/blog/2019/03/02/prusa-i3-mk3-real-multicolour-prints-without-mmu/

He has an open issue describing the need for this enhancement.
#1471

Rainer has already tested a compiled firmware with this M600 Q parameter, and reports it works well.
https://shop.prusa3d.com/forum/user-mods-octoprint-enclosures-nozzles--f65/simple-way-to-print-in-real-multi-color-without-mm-t28186-s10.html

The new Q parameter allows message displayed by M117 to remain on screen rather than being immediately erased by M600's first MSG_PRESS_TO_UNLOAD. Without the ability to suppress the 1st message, users attempting his technique cannot see the message indicating which filament should be be inserted. The 1st M600 prompt destroys the message.

Follow up prompts by M600 are not suppressed. Omitting Q lets M600 work as normal. This does NOT affect MMU function.

Usage:
M117 Change to yellow filament
M600 Q

Although this is Rainer's issue, I have written this to get support of his elegant way of limited multi-color printing in official firmware. I view Rainer's technique as a fun, gateway to multi-color printing. Once a user becomes enamored with multicolor, an MMU is in their future.

MulticolorMK3-Samples

guykuo added 10 commits Mar 9, 2019
Added Q parameter to M600. Adding a Q parameter to end of M600 command suppresses M600's first MSG_PRESS_TO_UNLOAD.

This is desirable when using rainersc's nifty manual color change technique as described at
https://schlosshan.eu/blog/2019/03/02/prusa-i3-mk3-real-multicolour-prints-without-mmu/
and his github issue describing the need for this enhancement
prusa3d#1471

This enhancement allows message displayed by M117 to remain on screen rather than being immediately erased by M600's first MSG_PRESS_TO_UNLOAD. The follow up prompts by M600 are not suppressed. Omitting Q lets M600 work as normal. So this should not affect MMU function.

Usage:
M117 Change to yellow filament
M600 Q
pull current mk3 to guykuo fork
@guykuo
Copy link
Author

@guykuo guykuo commented Mar 13, 2019

Updated to be once more mergeable with head MK3 repository

@Eenie75
Copy link

@Eenie75 Eenie75 commented May 30, 2019

This is awesome! How do we get some traction?

@guykuo
Copy link
Author

@guykuo guykuo commented May 30, 2019

@rainersc
Copy link

@rainersc rainersc commented May 30, 2019

i am still using thie compiled fw i got from guykuo without any problems, but no progress on getting this merged/reviewed unluckily :(

@Panayiotis-git
Copy link
Contributor

@Panayiotis-git Panayiotis-git commented May 30, 2019

This is great! I've tried once such a multi-color print and all my messages were lost.
Even now I use the mmu2, this is a nice feature.

@guykuo
Copy link
Author

@guykuo guykuo commented May 31, 2019

@guykuo guykuo closed this Aug 31, 2019
@guykuo guykuo deleted the M600-Q-Parameter-Enhancement branch Aug 31, 2019
@Matrixrs
Copy link

@Matrixrs Matrixrs commented May 8, 2020

Sorry to see this was not having attention from PRUSA, It's a good way to do small color print and see the possibility it offer! And it seems to change nothing to MMU. I will buy an MMU at some point but this is just should be seens as bringing people into color print ... Is there a way to have this in the latest firmware ''prusa3d_fw_MK3S_3_9_0-RC3_3401'' ? I am not "ready" to start compile my own firmware... :O)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

5 participants