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

Creality K2 plus profile does not include Change Filament G-Code #7607

Closed
3 tasks done
brandonfhall opened this issue Nov 28, 2024 · 2 comments
Closed
3 tasks done

Creality K2 plus profile does not include Change Filament G-Code #7607

brandonfhall opened this issue Nov 28, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@brandonfhall
Copy link
Contributor

Is there an existing issue for this problem?

  • I have searched the existing issues

OrcaSlicer Version

2.2.0

Operating System (OS)

Windows

OS Version

Windows 11

Additional system information

No response

Printer

Creality K2 Plus

How to reproduce

Open the Creality K2 plus printer profile
Machine G-code
Scroll down to "Change Filament G-code"

The change Filament G-code is blank for this printer, this results in a filament clog when trying to print a sliced object with color changes present.

Adding the following G code resolves the issue, this is taken from Creality's own slicer

"G2 Z{z_after_toolchange + 0.4} I0.86 J0.86 P1 F10000 ; spiral lift a little from second lift
G1 X0 Y245 F30000
G1 Z{z_after_toolchange} F600"

Actual results

If the filament G-Code is not present it will result in a filament clog when trying to print an object with color changes present.

Expected results

The Filament G-code would be present in the default profile available for the printer.

Project file & Debug log uploads

N/A for this issue is it is present in the default profile for the Creality K2 plus.

Checklist of files to include

  • Log file
  • Project file

Anything else?

no.

@brandonfhall brandonfhall added the bug Something isn't working label Nov 28, 2024
@brandonfhall
Copy link
Contributor Author

PR addressing this has been created at #7713

@brandonfhall
Copy link
Contributor Author

This should be resolved now that the PR has been merged. going to close it out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant