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

Single nozzle, Multi Materials Klipper Gcode Issue #1195

Open
kackle1998 opened this issue May 28, 2021 · 2 comments
Open

Single nozzle, Multi Materials Klipper Gcode Issue #1195

kackle1998 opened this issue May 28, 2021 · 2 comments

Comments

@kackle1998
Copy link

SuperSlicer_2.2.53
Windows 10 64-bit

I'm running a custom I3 style machine on Klipper that uses a "false extruder" of sorts, where I run multiple materials through the same stepper motor. I understand that makes very little sense, so it's easier to show. Here is someone else's setup using the same principle for two materials. https://www.youtube.com/watch?v=0F38WQUEaGs&t=2s Mine uses eight.

When slicing, I set up each color of my filament as a different filament, and assign each to their own extruder. The problem is, all of these are technically running under the same motor, so the line ACTIVATE_EXTRUDER EXTRUDER=extruder2 causes a print failure, as I truly only have one motor.

If the line ACTIVATE_EXTRUDER EXTRUDER=extruder could use the same convention as Marlin "T0, T1, T2" etc..., I could easily get around this using an empty Klipper macro, such as the following:

[gcode_macro T0]
gcode:

This would also be easily solved with an option within the SuperSlicer extruder tab under Printer Settings that allows me to link the false Extruder 2,3, and so on to what klipper knows as "Extruder." "

I noticed a commit that referenced an extremely similar issue here, #276, but don't see the fix anywhere in SS. If I am just missing an option, could someone direct me to it? Thank you

@supermerill
Copy link
Owner

supermerill commented May 28, 2021

I'll trash the current check and will replace it by "if there is something in custom toolchange gcode, I'll output nothing"

supermerill pushed a commit that referenced this issue Jun 23, 2021
…real

#1195
milling PP : now doesn't trigger a toolchange. use mill custom gcode to change tool.
#1329
@Roycinger
Copy link

Is this still ongoing? I'm basically still running into the same issue

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

No branches or pull requests

3 participants