-
Notifications
You must be signed in to change notification settings - Fork 10
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
need help getting multicolors to work ,,, fresh install of octoprint and cura #33
Comments
Some details could be useful |
i am running cura 3.1, and octoprint latest version, im wondering if the latest update to octoprint is the issue , as it worked great for me up until then ? |
And now? Does it give an error ? Message? |
ERROR: Injecting GCODE failed. Replaced 0 out of 1 needed. |
The regular expression used? |
hi, same error her .. ERROR: Injecting GCODE failed. Replaced 0 out of 1 needed. |
thats a problem with the regular expression matching the line from the slicer. you need to make sure the expression is right for your slicer |
From https://www.thingiverse.com/groups/anycubic-i3-mega/forums/general/topic:27062 (you have also the procedure to print in multicolor) On Octoprint go to settings and then "GCODE Scripts" insert this code into the mentioned fields: After print job is paused: M117 Print Paused Before print job is resumed: M117 Print Resumed Hit save. Then also in settings go to "Plugin Manager" and click "Get more..." In the search box type "colors" and install the Multi Colors plugin. You will find the plugin by clicking on the 4 bars / arrow down next to "Timelapse" in your Octoprint menu. Now you are good to go. Just use "GCode Viewer" in Octoprint to find the layers at which you want to change color. Then go back to Multi Colors and type them in separated by space. Like 125 127 to change color at layer 125 and then again at layer 127 :) |
For Cura, use ;LAYER:{layer} instead. |
Try this as your regex statement. .([LAYER])\w+.*([layer]). |
No description provided.
The text was updated successfully, but these errors were encountered: